[zeromq-dev] PGM TSI : Global Source ID and Source Port

[Annapurna Bikkina]

Hello,


We have a basic question on “Global Source ID and Source Port”. From reading the PGM documentation it says that the id should be unique. I was not able to find the code that generates the id in the pgm code source. In our application stack, all applications on the same subnet are having the same “GlobalSourceID”. Yesterday we had 2 sources have the same source port and one of them could not connect to the subscriber. We were wondering if the uniqueness of these 2 fields could have caused the issue. Any input into how this ID is generated will be helpful.





“



         A globally unique source identifier.  This ID MUST NOT change

         throughout the duration of the transport session.  A

         RECOMMENDED identifier is the low-order 48 bits of the MD5 [9<https://datatracker.ietf.org/doc/html/rfc3208#ref-9>]

         signature of the DNS name of the source.  Global Source ID

         together with Data-Source Port forms the TSI.

“

Thanks,
Anna.

________________________________

This e-mail (including any attachments) is confidential and may contain sensitive or legally privileged information. It is for the intended recipient only. Do not, directly or indirectly, copy, reproduce, print or disclose any part of this e-mail without the prior written consent of OTC Markets Group Inc. If you receive this message in error, please delete it and any attachments, and notify OTC Markets Group of misdelivery by return e-mail. View the OTC Markets Group Privacy Policy here.<https://www.otcmarkets.com/privacy-statement>
---------------------------------------------------------------------------------------
 This email has been scanned for email related threats and delivered safely by Mimecast.
 For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20220308/e4102228/attachment.htm>