IETF Logo Mail Archive

Re: [Sip] Last Call: draft-ietf-sip-ipv6-abnf-fix (Essential correction for IPv6 ABNF and URI comparison in RFC3261) to Proposed Standard

Adam Roach <adam@nostrum.com> Tue, 27 April 2010 13:34 UTC

Return-Path: <adam@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 5F4583A6880 for <sip@core3.amsl.com>; Tue, 27 Apr 2010 06:34:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.775
X-Spam-Level:
X-Spam-Status: No, score=-1.775 tagged_above=-999 required=5 tests=[AWL=-0.665, BAYES_05=-1.11, SPF_PASS=-0.001, WEIRD_PORT=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 XzG3u7LrhBAj for <sip@core3.amsl.com>; Tue, 27 Apr 2010 06:34:14 -0700 (PDT)
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 C728B3A6A60 for <sip@ietf.org>; Tue, 27 Apr 2010 06:33:31 -0700 (PDT)
Received: from hydra-3.local (ppp-70-249-147-216.dsl.rcsntx.swbell.net [70.249.147.216]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o3RDXGGo045061 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Apr 2010 08:33:16 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4BD6E79C.4040907@nostrum.com>
Date: Tue, 27 Apr 2010 08:33:16 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <20100305233033.8662628C400@core3.amsl.com> <4B919F23.7030502@cisco.com> <4BD60D89.3070902@bell-labs.com> <4BD61B92.8080708@cisco.com>
In-Reply-To: <4BD61B92.8080708@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.249.147.216 is authenticated by a trusted mechanism)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Last Call: draft-ietf-sip-ipv6-abnf-fix (Essential correction for IPv6 ABNF and URI comparison in RFC3261) to Proposed Standard
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: Tue, 27 Apr 2010 13:34:15 -0000

On 4/26/10 18:02, Apr 26, Paul Kyzivat wrote:
>
>> Writing leading zeroes for IPv4 address is not prevalent; by the
>> same token, representing ports in octal base is not prevalent either.
>> So I am inclined to let sleeping dogs lie.
>>
>> However, if the sponsoring AD or anyone monitoring this list feels
>> strongly, I don't mind adding a sentence or two to this effect in
>> the draft.
>
> I don't feel strongly about it. But now that you mention it, I think I 
> remember some question about octal ports coming up on one of the 
> mailing lists some time in the past.
>
> I also don't feel *strongly* about it. Lets see if anybody else has 
> something to say about it.

For what it's worth, typing "http://www.ietf.org:080/" into Firefox, 
Safari, and MSIE all takes me to the IETF's web page (interpreting "080" 
as 80, not 64). So, at least for HTTP URLs, there's a de facto 
interpretation of leading zeros in a port as padding, not an indication 
of octal.

/a

v2.8.7 | Report a Bug | By Email