Re: [sipcore] IPv6 in the sip core wg

[Paul Kyzivat <[e-mail]>]

On 12/16/13 2:30 PM, Cullen Jennings wrote:
>
> On Dec 13, 2013, at 9:17 AM, Olle E. Johansson <[e-mail]> wrote:
>
>> The problem is really that RFC 3263 repeats "A or AAAA" - which means that if we follow RFC 3263 verbatim we won't have both IPv4 and IPv6 addresses to connect to. I have not claimed that it talks about how we connect.
>
> A or B does not mean you are not allowed to do both

English is vague about this.
It can be read as either OR or XOR.
And that is just when considering use by native English speakers.
When you factor in people for whom English is not native, it is probably 
more dubious which it means.

If there is any concern then we should ensure that this is clarified.
Whether that requires an update may still be controversial. But ISTM if 
we are going to produce a standards track RFC anyway, that it would be 
better to be sure by declaring it to be an update.

If your implementation is already consistent with the clarification, 
then you can immediately claim conformance to it. But advertising it as 
an update may provoke some to discover that they aren't consistent with 
the clarified intent. That will cause them some work to conform, but 
will also fix problems.

	Thanks,
	Paul