> From: Paul Kyzivat [[email protected]] > > [...] > But the point remains - it is in theory possible that the same o-line > could be used in different sessions, in association with other content > that is not the same. According to 4566, > [message ends here]
Well, what I see in RFC 4566 is: In general, the "o=" field serves as a globally unique identifier for this version of this session description, and the subfields excepting the version taken together identify the session irrespective of any modifications. Of course there is almost no algorithmic way to *ensure* uniqueness, but it's easy enough to achieve to very high probability. E.g., we do it with Call-Id's. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
