"ext Vijay K. Gurbani" <[EMAIL PROTECTED]> writes: >RFC 3261 has ambiguities - this is one of them, probably the >most benign, but an ambiguity nonetheless. With a little work, >this can be easily sorted out in one of the following ways:
> (1) Have the sipping IPv6 torture test document update the > IPv6 ABNF (although, this will require it to be a standards- > track document, and not an informational). > (2) Open and maintain a bug in bugs.sipit.net, pointing new > developers to the appropriate behavior. What is the bug there? Should we have 1) via-received = "received" EQUAL (IPv4address / IPv6reference) 2) via-received = "received" EQUAL (IPv4address / IPv6address / IPv6reference) 3) gen-value /= IPv6address 4) both 2 and 3 above? > (4) Agree that we will leave the representation of the > received parameter as-is in RFC 3261, but put leniency torture > tests around this in the sipping IPv6 torture test document. Hm, meaning that everyone should accept both IPv6address and IPv6reference in the via-received? --Pekka _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
