The draft changes the SDP offer/answer model so that an answer has to use the same protocol family (ipv4/ipv6) as the offer, which makes sense.
Two things remain unclear to me: - If I get an offer for media based on an address family I can not understand - what's the valid response? If it's only one media stream with codecs I don't support, I use 488. But in this case that doesn't seem like a valid response to me. - Is there a way to compose an offer with two media streams - one in IPv4 and one in IPv6 - for dual stack agents. I can't find examples of this, but SDP syntax seems to allow it. The draft propably should go a bit deeper in this area. With the text on ICE it seems to recommend sending an offer with both networks, then using ICE to find the optimal path for media. Any thoughts? Regards, /Olle http://www.ietf.org/id/draft-ietf-sipping-v6-transition-07.txt _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors