[Sip] Re: URI comparison rules - IPv6 addresses

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Wed, 21 November 2007 16:23 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 1IusLy-0004Q7-QE; Wed, 21 Nov 2007 11:23:06 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IusLw-0004Nn-LQ for sip-confirm+ok@megatron.ietf.org; Wed, 21 Nov 2007 11:23:04 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IusLw-0004Ll-5T for sip@ietf.org; Wed, 21 Nov 2007 11:23:04 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IusLv-0006z9-Cf for sip@ietf.org; Wed, 21 Nov 2007 11:23:04 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id B0D382111B; Wed, 21 Nov 2007 17:23:02 +0100 (CET)
X-AuditID: c1b4fb3e-b0ea3bb00000459d-98-47445b66bade
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id A0C3F2109B; Wed, 21 Nov 2007 17:23:02 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Nov 2007 17:23:02 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Nov 2007 17:23:02 +0100
Received: from [131.160.126.193] (rvi2-126-193.lmf.ericsson.se [131.160.126.193]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 10044234E; Wed, 21 Nov 2007 18:23:02 +0200 (EET)
Message-ID: <47445B65.7010608@ericsson.com>
Date: Wed, 21 Nov 2007 18:23:01 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
References: <BBE61D1553D8A34F812FF87377B2935F01CCDE6A@ATL1VEXC020.usdom003.tco.tc> <4743F62A.8040903@ericsson.com> <4743F78D.4070705@ericsson.com> <474450B2.1020907@alcatel-lucent.com>
In-Reply-To: <474450B2.1020907@alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Nov 2007 16:23:02.0415 (UTC) FILETIME=[C9C949F0:01C82C5A]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: sip <sip@ietf.org>, Brett Tate <brett@broadsoft.com>
Subject: [Sip] Re: URI comparison rules - IPv6 addresses
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

Hi Vijay,

if this document becomes a WG item, I agree it would be the perfect 
place to document this issue.

Cheers,

Gonzalo


Vijay K. Gurbani wrote:
> Gonzalo Camarillo wrote:
>> Hi,
>>
>> Brett brought this up in the SIP Implementors mailing list. The
>> following IPv6 addresses are supposed to be equivalent:
>>
>> [::ffff:192.0.2.128] and [::ffff:c000:280]
>> [2001:db8::9:1] and [2001:db8::9:01]
>> [0:0:0:0:0:FFFF:129.144.52.38] and [::FFFF:129.144.52.38]
>>
>> Now, let's say I need to compare sip:user1@[::ffff:192.0.2.128] and
>> sip:user1@[::ffff:c000:280]. Should we consider these URIs to be
>> equivalent or not?
>>
>> My proposal is that we clarify that IPv6 address comparison happens at
>> the binary level, not at the textual level. We could log a bug against
>> RFC3261, and try and add such a clarification to the IPv6 transition
>> document (I will need to ask the ADs whether or not we can add this in
>> AUTH48).
> 
> Gonzalo: My only concern that I had mentioned to Brett as
> well was that this should not be construed as endorsing the
> notion of multiple representations of the IPv6 address in
> SIP signaling.  This may cause problems in normal SIP operations.
> 
> Consider a proxy that uses the sent-by address in a loop detection
> mechanism.  If it gets a looped request but the upstream proxy
> had now put a different representation of the IP address, then
> the proxy will not recognize that as a loop.  Admittedly, the
> upstream proxy should not be inserting different representations
> of the same IP address in each request (unless, of course it is
> malicious; but then if it is malicious, it could probably do
> damage by other means.)
> 
> Now, regarding where to put it: in v6-transition or in a SIP
> essential fix, here are some thoughts.  Insofar as we are talking
> about URI comparison, this clarification is probably best put
> in S19.1.4 (URI Comparison) of rfc3261.  We already have a
> SIP essential fix document that fixes the IPv6 ABNF in rfc3261
> (http://tools.ietf.org/html/draft-gurbani-sip-ipv6-abnf-fix-00);
> this clarification could be tacked on in that draft if the WG
> agrees.  Thoughts?
> 
> Thanks,
> 
> - vijay



_______________________________________________
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