Re: [Sip] Re: URI comparison rules - IPv6 addresses

Dale.Worley@comcast.net Wed, 21 November 2007 23:43 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuzDn-0004rJ-3P; Wed, 21 Nov 2007 18:43:07 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IuzDl-0004qy-Cp for sip-confirm+ok@megatron.ietf.org; Wed, 21 Nov 2007 18:43:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuzDl-0004qk-2k for sip@ietf.org; Wed, 21 Nov 2007 18:43:05 -0500
Received: from qmta01.westchester.pa.mail.comcast.net ([76.96.62.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuzDh-0003M0-UT for sip@ietf.org; Wed, 21 Nov 2007 18:43:05 -0500
Received: from OMTA05.westchester.pa.mail.comcast.net ([76.96.62.43]) by QMTA01.westchester.pa.mail.comcast.net with comcast id Fbiy1Y0020vyq2s0500100; Wed, 21 Nov 2007 23:43:01 +0000
Received: from dragon.ariadne.com ([24.34.79.42]) by OMTA05.westchester.pa.mail.comcast.net with comcast id Fbj11Y0050umElk0300000; Wed, 21 Nov 2007 23:43:01 +0000
X-Authority-Analysis: v=1.0 c=1 a=a641SQi2628A:10 a=3JPcM4IzsFwy4_BOV3wA:9 a=eVKkyKUIdOYYdu1NV_0A:7 a=RExMb4gvKHjsakjjPmdLtlCaRkcA:4 a=3FZX-ydVlcEA:10 a=8y7tGHue6YMA:10
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id lALNh1SV006915 for <sip@ietf.org>; Wed, 21 Nov 2007 18:43:01 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id lALNh17e006911; Wed, 21 Nov 2007 18:43:01 -0500
Date: Wed, 21 Nov 2007 18:43:01 -0500
Message-Id: <200711212343.lALNh17e006911@dragon.ariadne.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <47448C1B.7000603@alcatel-lucent.com> (vkg@alcatel-lucent.com)
Subject: Re: [Sip] Re: URI comparison rules - IPv6 addresses
References: <0JRV00ABOC070460@jes-fe1.zx.nl> <47448C1B.7000603@alcatel-lucent.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

   From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>

   Jeroen van Bemmel wrote:
   > Vijay,
   > It's not only IPv6: what about 127.0.0.1 versus 127.000.000.1?

   Jeroen: Pedantically speaking, you are probably right.  But
   in practice we do not generally see leading zeros in an IPv4
   octet.

Even worse, in some places, including some early RFCs, the leading
zero is used to indicate that the octet is represented in octal!

But I think Jeroen's point is actually well-taken, when comparing
representations of IP addresses (not DNS names), the comparison is
implicitly of the address represented, not the textual
representation.  And this applies in IPv4 as well as IPv6.

In regard to loop detection, there are two approaches:  (1) Whatever
attempts to detect loops can canonicalize the addresses before
comparing them or whatever.  (2) Since there are a limited number of
likely representations of any address, having different entities use
different representations will only delay loop detection, not prevent
it.  And loops will be detected even if address comparisons have
occasional false negatives.

Dale


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip