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

Dale.Worley@comcast.net Fri, 23 November 2007 17:21 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 1IvcDE-0000R7-S8; Fri, 23 Nov 2007 12:21:08 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IvcDD-0000Qy-FY for sip-confirm+ok@megatron.ietf.org; Fri, 23 Nov 2007 12:21:07 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvcDD-0000Qo-5L for sip@ietf.org; Fri, 23 Nov 2007 12:21:07 -0500
Received: from qmta05.emeryville.ca.mail.comcast.net ([76.96.30.48]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IvcDC-0008UR-OJ for sip@ietf.org; Fri, 23 Nov 2007 12:21:07 -0500
Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by QMTA05.emeryville.ca.mail.comcast.net with comcast id GDAY1Y0060FhH240A0DV00; Fri, 23 Nov 2007 17:21:09 +0000
Received: from dragon.ariadne.com ([24.34.79.42]) by OMTA08.emeryville.ca.mail.comcast.net with comcast id GHM71Y00B0umElk0800000; Fri, 23 Nov 2007 17:21:09 +0000
X-Authority-Analysis: v=1.0 c=1 a=a641SQi2628A:10 a=FO4_DPHR8zsQfEvtuP0A:9 a=aPY_TtD8OT17jqWuRq4Y2b1toJQA:4 a=JfD0Fch1gWkA: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 lANHL3SV027365 for <sip@ietf.org>; Fri, 23 Nov 2007 12:21:03 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id lANHL35M027361; Fri, 23 Nov 2007 12:21:03 -0500
Date: Fri, 23 Nov 2007 12:21:03 -0500
Message-Id: <200711231721.lANHL35M027361@dragon.ariadne.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <474700D9.7090809@cisco.com> (pkyzivat@cisco.com)
Subject: Re: [Sip] Re: URI comparison rules - IPv6 addresses
References: <0JRV00ABOC070460@jes-fe1.zx.nl> <47448C1B.7000603@alcatel-lucent.com> <200711212343.lALNh17e006911@dragon.ariadne.com> <474700D9.7090809@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
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: Paul Kyzivat <pkyzivat@cisco.com>

   > (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.

   While the number is *limited*, the limit is pretty large.

True, but I expect in practice there will be no cases with more than 3
representations of the same address used by any one SIP agent unless
it's deliberately trying to defeat loop detection.  That case is
ameliorated by (1) a malicious agent would have to handle the message
"every time around the loop", which would place a high burden on it,
and (2) loops will eventually be detected by Max-Forwards in any case.

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