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

"Vijay K. Gurbani" <vkg@alcatel-lucent.com> Wed, 21 November 2007 21:42 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 1IuxLT-0000BV-Hd; Wed, 21 Nov 2007 16:42:55 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IuxLR-0000BP-NF for sip-confirm+ok@megatron.ietf.org; Wed, 21 Nov 2007 16:42:53 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuxLR-0000BH-CZ for sip@ietf.org; Wed, 21 Nov 2007 16:42:53 -0500
Received: from ihemail1.lucent.com ([135.245.0.33]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuxLQ-0002xL-MR for sip@ietf.org; Wed, 21 Nov 2007 16:42:53 -0500
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id lALLggV2020212; Wed, 21 Nov 2007 15:42:42 -0600 (CST)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90]) by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id lALLgfj07418; Wed, 21 Nov 2007 15:42:41 -0600 (CST)
Message-ID: <4744A651.9010306@alcatel-lucent.com>
Date: Wed, 21 Nov 2007 15:42:41 -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: Michael Thomas <mat@cisco.com>
Subject: Re: [Sip] Re: URI comparison rules - IPv6 addresses
References: <0JRV00ABOC070460@jes-fe1.zx.nl> <47448C1B.7000603@alcatel-lucent.com> <4744A284.9040009@cisco.com>
In-Reply-To: <4744A284.9040009@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: sip <sip@ietf.org>, Brett Tate <brett@broadsoft.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
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

Michael Thomas wrote:
> Doesn't this sort of slide down the slippery slope of understanding 
> the semantics of the URI for comparison? For example, why can't you
> make the same kind of argument for www.example.com and example.com
> since they're pretty much synonymous these days? And for that matter
> what about comparing example.com and, oh say, its A(AAA) record?
> They're the "same", FSVO "same".

Mike: Our domain is restricted to SIP URIs.  In other words,
while DNS-wise, www.example.com = example.com, this does not carry
into SIP; i.e., sip:user@sip.example.com != sip:user@example.com.

I suppose the rules for SIP URI comparisons are a bit more stringent
than DNS equivalence of names, aliases, and their resulting addresses.

> Maybe I missed the first post, but is it realistic that something(s) 
> producing URI's for the same target would create their name in 
> different manners?

No, not realistic, but entirely probable.

> And if it is, why wouldn't it be as much of a problem with the IP
> address name and a real fqdn?

Because, SIP URI wise, sip:user@example.com != sip:user@192.0.2.128
even though DNS_lookup("example.com") = "192.0.2.128".

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs


_______________________________________________
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