Re: [Sipping] Question on draft-ietf-sipping-v6-transition-07

"Vijay K. Gurbani" <vkg@alcatel-lucent.com> Thu, 28 January 2010 19:42 UTC

Return-Path: <vkg@alcatel-lucent.com>
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00CF83A6844 for <sipping@core3.amsl.com>; Thu, 28 Jan 2010 11:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GFHpFd07rRqA for <sipping@core3.amsl.com>; Thu, 28 Jan 2010 11:42:21 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id DFA123A67D4 for <sipping@ietf.org>; Thu, 28 Jan 2010 11:42:20 -0800 (PST)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id o0SJgcMY020775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jan 2010 13:42:38 -0600 (CST)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17]) by umail.lucent.com (8.13.8/TPES) with ESMTP id o0SJgcsn012128; Thu, 28 Jan 2010 13:42:38 -0600 (CST)
Message-ID: <4B61E8AE.6090309@alcatel-lucent.com>
Date: Thu, 28 Jan 2010 13:42:38 -0600
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
References: <A444A0F8084434499206E78C106220CAB4EC49D8@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CAB4EC49D8@MCHP058A.global-ad.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: "sipping@ietf.org" <sipping@ietf.org>
Subject: Re: [Sipping] Question on draft-ietf-sipping-v6-transition-07
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2010 19:42:22 -0000

Elwell, John wrote:
> " 1.  In some cases, especially those dealing with third party call 
> control (see Section 4.2 of [12]), there arises a need to specify the
> IPv6 equivalent of the IPv4 unspecified address (0.0.0.0) in the SDP
> offer.  For this, IPv6 implementations MUST use a domain name within
> the .invalid DNS top-level domain instead of using the IPv6
> unspecified address (i.e., ::)."
> 
> Can somebody recall the reason for this? Both "0.0.0.0" and "::" mean
> "unspecified" in their respective IP versions.

John: Right; so I went back to my email archives to when
Gonzalo and I had a conversation about this (on April 27, 2006.)

We favored an .invalid over :: because the Application folks had
indicated this to be their preference in the past.  For IPv4,
0.0.0.0 was supported for backwards compatibility, but it appears
that a move to IPv6 can be handled cleanly with using only .invalid
instead of having two alternative solutions.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/