[SIPForum-techwg] SIPconnect 1.1 baseline - IPv6

[Spencer Dawkins]

>I would offer we not forget we run out of new IPv4 addresses in the
> next 2-4 years. We publish in the next year. I would also offer that
> it is more likely for new enterprises (greenfields) to be installing
> SIP communication solutions. Thus, an IPv4-only spec limits our market
> to either legacy enterprises with existing IPv4 addresses or gives a
> huge incentive for both legacy and new enterprises to NOT upgrade to
> SIP communication solutions.
>
> Thus I would be hard pressed to say the specification should be IPv4-
> only.
>
> I would also be hard pressed to say the specification should be IPv6-
> only, as there are a lot of people upgrading their circa-2000 IP
> PBXen, which means they already have IPv4 connectivity and may not be
> upgrading their networks to IPv6.
>
> Thus the focus should not be, "Do we mandate IPv6 only or IPv6 only,"
> but "How do we sensibly specify both IPv4 and IPv6?"

I agree that neither IPv4-only nor IPv6-only would be the right thing to say 
in a 2009 specification, and remaining silent on IP versions isn't helping 
anybody.

So, we're going to have to have normative text at some point on this 
topic...

The issue with dual-stack is that you have to have an IPv4 address - that's 
what's driving the IETF nuts now, because it's fairly obvious that 
dual-stack ALSO hits the wall when we reach the point where IPv4 addresses 
are either technically or economically unavailable. Dual stack is a 
transition mechanism, not a continued coexistence mechanism.

But if this is the first time we say anything about IPv6, and if we have 
another opportunity to say something stronger after a couple of years, I 
would be OK with MUST IPv4, and MAY dual-stack, in a specification with a 
two-year shelf life.

Does anyone substantially disagree with this?

Thanks,

Spencer