[SIPForum-techwg] IPv6 Text for SIPconnect 1.1
fluffy at cisco.com
Thu Feb 12 02:02:53 EST 2009
I generally try to not get to wrapped up in the political posturing
around v4 address completion but just as one point ... I think the
2014 date is the date the RIR may not be able to get new address from
IANA (i.e. some time between now and 2014 we will have "v4 address
completion"). That is hugely different issue than enterprises won't be
able to get new v4 addresses. You might want to check your first few
paragraphs have the tone you want.
On Feb 1, 2009, at 6:19 PM, Eric Burger wrote:
> Between now and 2014, we expect to run out of IPv4 addresses for new
> allocations. What this means for new enterprises is they cannot get
> service or they cannot be added to the global IPv4 network,
> rendering them unable to be globally accessible, except through
> their service provider. Moreover, this situation inhibits the
> enterprise from directly connecting to other enterprises in the same
> situation. For existing enterprises, as they add IPv4 addresses for
> endpoints, they may find they are unable to expand their allocation
> of IPv4 addresses.
> The SIPconnect task group recognizes the immanent danger from the
> depletion of IPv4 addresses. However, we also recognize that at the
> time of the publication of SIPconnect 1.1, not all equipment
> manufacturers have IPv6 in their products and few service providers
> are ready to offer IPv6 service. Therefore, the task group did not
> reach a consensus to mandate IPv6 support for either the SIP-PBX or
> the SP-SSE.
> There is a consensus for us to publish guidelines so the transition
> to IPv6 occurs with the least impact on compliant SIPconnect 1.1
> implementations. Guidelines include the following.
> · Do not hard-code IP addresses in configuration files. Use
> DNS instead.
> · Expect IPv6 addresses whenever one receives an IP address in
> a message, per IETF and ITU-T procedures. By message, we mean not
> only SIP and SDP, but DNS, HTTP, TLS, and so on.
> The reader will notice that nowhere does the SIPconnect 1.1
> specification mandate the use of an explicit IPv4 address. Moreover,
> nowhere will you find a recommendation to use static IPv4 addresses.
> Rather, the SIPconnect 1.1 specification suggests using hostnames
> and fully qualified domain names.
> A result of following these guidelines is a SIPconnect 1.1 SIP-PBX
> and a SIPconnect 1.1 SP-SSE that both implement IPv6 and the
> configuration uses no hard-coded IPv4 addresses should work out of
> the box. However, since this document allows hard-coded IPv4
> addresses, an implementation that has explicit IPv4 addresses will
> fail. Moreover, IPv6-unaware SIP-PBXen and SP-SSEs will fail in an
> IPv6 environment.
> One can expect future versions of the SIPconnect specification will
> mandate the support of IPv6, more especially so in light of immanent
> IPv4 address exhaustion.
> techwg mailing list
> Send mail to: techwg at sipforum.org
> Unsubscribe or edit options at: http://sipforum.org/mailman/listinfo/techwg
More information about the techwg