Re: [Sip] draft-ietf-sip-ipv6-abnf-fix-04

"Dale Worley" <dworley@avaya.com> Fri, 29 January 2010 17:52 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A10F3A67D3 for <sip@core3.amsl.com>; Fri, 29 Jan 2010 09:52:45 -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 T0eDk6+NZUzx for <sip@core3.amsl.com>; Fri, 29 Jan 2010 09:52:44 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 2A7DB3A6784 for <sip@ietf.org>; Fri, 29 Jan 2010 09:52:43 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,369,1262581200"; d="scan'208";a="1843195"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 29 Jan 2010 12:53:06 -0500
Received: from unknown (HELO zcars04f.nortel.com) ([47.129.242.57]) by co300216-co-erhwest-out.avaya.com with ESMTP; 29 Jan 2010 12:53:05 -0500
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id o0THqis01869; Fri, 29 Jan 2010 17:52:44 GMT
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id o0THqgM14031; Fri, 29 Jan 2010 17:52:42 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 29 Jan 2010 12:52:41 -0500
From: Dale Worley <dworley@avaya.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
In-Reply-To: <4B6317F3.6050702@alcatel-lucent.com>
References: <1264783287.4057.9.camel@khone.us.nortel.com> <4B6317F3.6050702@alcatel-lucent.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Fri, 29 Jan 2010 12:52:41 -0500
Message-Id: <1264787561.4057.16.camel@khone.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Jan 2010 17:52:41.0709 (UTC) FILETIME=[DA9069D0:01CAA10B]
Cc: sip@ietf.org
Subject: Re: [Sip] draft-ietf-sip-ipv6-abnf-fix-04
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2010 17:52:45 -0000

On Fri, 2010-01-29 at 11:16 -0600, Vijay K. Gurbani wrote:
> Are you suggesting that we mandate that all IPv4 addresses
> written in dotted-decimal form be really decimal?  Or just that the
> SIP addresses behave so?
> 
> I doubt we can do the former through sip-ipv6-abnf-fix; I suspect
> we can do the latter if the WG (which one?  sipcore?) or sponsoring
> AD agrees on it, although this particular draft is limited to
> fixing the IPv6 ABNF.

I'm sure that everybody thinks that dotted-decimal strings in SIP URIs
are to be interpreted as decimal.  And for that matter, that series of
HEXDIG's are to be interpreted as hexidecimal.  Whether that is,
strictly speaking, syntax or not, I don't know.  But it appears that
neither of these facts has been stated in plain words, and in an
unpleasantly large number of situations, code may not follow that
convention.

As long as we're explicating the syntax, it seems reasonable to
enunciate what "everybody knows" about its interpretation.

Dale