On Sat, Mar 28, 2009 at 6:25 AM, Hadriel Kaplan <hkap...@acmepacket.com> wrote:
> Would people prefer that? yup. Also: [OPEN ISSUE: should we make this a fixed format, defined randomization mechanism to avoid detecting the vendor type from the Call-ID format?] How about defining it to be a v5 uuid (rfc4122), which: - is well defined (including generating) in RFC 4122 - has many libraries for generating and parsing - a v5 uuid can be detected (by looking at bits 4-7 == 0101) and thus knows if it's secure - is "almost" unique across a four dimensional space-time continuum - certainly a _very_ low chance of any collision, even when we're communicating with alpha centauri over SIP/2.0. ~ Theo Sent from: Bicester Oxfordshire United Kingdom. _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implement...@cs.columbia.edu for questions on current sip Use sipp...@ietf.org for new developments on the application of sip
