Re: [Sip] draft-ietf-sip-ipv6-abnf-fix-04
Robert Sparks <rjsparks@nostrum.com> Fri, 29 January 2010 20:48 UTC
Return-Path: <rjsparks@nostrum.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 DDE103A683C for <sip@core3.amsl.com>; Fri, 29 Jan 2010 12:48:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level:
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, SPF_PASS=-0.001]
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 C589YGqo-lWV for <sip@core3.amsl.com>; Fri, 29 Jan 2010 12:48:24 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 40ED13A659A for <sip@ietf.org>; Fri, 29 Jan 2010 12:48:23 -0800 (PST)
Received: from [192.168.2.2] (pool-173-71-49-137.dllstx.fios.verizon.net [173.71.49.137]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o0TKmiWp008756 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Jan 2010 14:48:44 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-Id: <AD886ED2-F1A9-45DE-9A44-2D98AAEDB746@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
In-Reply-To: <4B6347D5.5040602@alcatel-lucent.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 29 Jan 2010 14:48:43 -0600
References: <1264783287.4057.9.camel@khone.us.nortel.com> <4B6317F3.6050702@alcatel-lucent.com> <1264787561.4057.16.camel@khone.us.nortel.com> <4B6347D5.5040602@alcatel-lucent.com>
X-Mailer: Apple Mail (2.936)
Received-SPF: pass (nostrum.com: 173.71.49.137 is authenticated by a trusted mechanism)
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 20:48:26 -0000
No, I don't think trying to make that syntax change is appropriate for this draft at this point in its life-cycle. RjS On Jan 29, 2010, at 2:40 PM, Vijay K. Gurbani wrote: > Robert: Please see question directed to you at the end of this > email. > > Dale Worley wrote: >> As long as we're explicating the syntax, it seems reasonable to >> enunciate what "everybody knows" about its interpretation. > > Dale: I am not being an obstructionist here, so please > do not take the comments as such. > > I believe that "everybody knows" that dotted-decimal is > well, dotted-"decimal" and not dotted-"octal". The fact > that some C libraries interpret the leftmost 0 as a > hint to enter octal mode is unfortunate, but I don't see > how putting admonitions here will solve that particular > problem. > > That said, one quick observation is that the production rule for > <IPv4address> literal defined in rfc3986 is more close > to your intent than the one defined in rfc3261. More > specifically, here they are: > > rfc3986: > > A host identified by an IPv4 literal address is represented in > dotted-decimal notation (a sequence of four decimal numbers in the > range 0 to 255, separated by "."), as described in [RFC1123] by > reference to [RFC0952]. Note that other forms of dotted notation may > be interpreted on some platforms, as described in Section 7.4, but > only the dotted-decimal form of four octets is allowed by this > grammar. > > IPv4address = dec-octet "." dec-octet "." dec-octet "." dec-octet > > dec-octet = DIGIT ; 0-9 > / %x31-39 DIGIT ; 10-99 > / "1" 2DIGIT ; 100-199 > / "2" %x30-34 DIGIT ; 200-249 > / "25" %x30-35 ; 250-255 > > rfc3261: > > IPv4address = 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT > > So, we could deprecate the existing rfc3261 syntax for IPv4address > and replace it with the one for rfc3986. > > Robert: Is this okay with you? If so, I can put the above change > in the draft as well. > > Thanks, > > - vijay > -- > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent > 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA) > Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org} > Web: http://ect.bell-labs.com/who/vkg/
- [Sip] draft-ietf-sip-ipv6-abnf-fix-04 Dale Worley
- Re: [Sip] draft-ietf-sip-ipv6-abnf-fix-04 Vijay K. Gurbani
- Re: [Sip] draft-ietf-sip-ipv6-abnf-fix-04 Dale Worley
- Re: [Sip] draft-ietf-sip-ipv6-abnf-fix-04 Vijay K. Gurbani
- Re: [Sip] draft-ietf-sip-ipv6-abnf-fix-04 Robert Sparks
- Re: [Sip] draft-ietf-sip-ipv6-abnf-fix-04 Brett Tate
- Re: [Sip] draft-ietf-sip-ipv6-abnf-fix-04 Vijay K. Gurbani
- Re: [Sip] draft-ietf-sip-ipv6-abnf-fix-04 Dale Worley