IETF Logo Mail Archive

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

"Vijay K. Gurbani" <vkg@alcatel-lucent.com> Fri, 29 January 2010 20:40 UTC

Return-Path: <vkg@alcatel-lucent.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 71A8F3A683C for <sip@core3.amsl.com>; Fri, 29 Jan 2010 12:40:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_37=0.6]
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 433IZCkez8IW for <sip@core3.amsl.com>; Fri, 29 Jan 2010 12:40:33 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 541FD3A67DA for <sip@ietf.org>; Fri, 29 Jan 2010 12:40:32 -0800 (PST)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id o0TKes4e008051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jan 2010 14:40:54 -0600 (CST)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17]) by umail.lucent.com (8.13.8/TPES) with ESMTP id o0TKer7P017045; Fri, 29 Jan 2010 14:40:53 -0600 (CST)
Message-ID: <4B6347D5.5040602@alcatel-lucent.com>
Date: Fri, 29 Jan 2010 14:40:53 -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: Dale Worley <dworley@avaya.com>, Robert Sparks <rjsparks@nostrum.com>
References: <1264783287.4057.9.camel@khone.us.nortel.com> <4B6317F3.6050702@alcatel-lucent.com> <1264787561.4057.16.camel@khone.us.nortel.com>
In-Reply-To: <1264787561.4057.16.camel@khone.us.nortel.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.35
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:40:34 -0000

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/

v2.8.7 | Report a Bug | By Email