Re: [Idr] WG Last Call on draft-ietf-idr-as4bytes-11.txt

Ran Liebermann <ranmails@gmail.com> Mon, 10 October 2005 12:28 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOwlJ-0007T8-Ph; Mon, 10 Oct 2005 08:28:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOwlI-0007SS-5t for idr@megatron.ietf.org; Mon, 10 Oct 2005 08:28:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05662 for <idr@ietf.org>; Mon, 10 Oct 2005 08:28:10 -0400 (EDT)
Received: from qproxy.gmail.com ([72.14.204.198]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOwvB-0003Os-3I for idr@ietf.org; Mon, 10 Oct 2005 08:38:26 -0400
Received: by qproxy.gmail.com with SMTP id a39so1096126qbd for <idr@ietf.org>; Mon, 10 Oct 2005 05:27:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Scqg1Dz2dHmrqUVbZ4Gpx+n/GGnr4XDnyhoPEt4rFagFmiZaqoZd8I7DfZVx+tTT16k2uu/ne4JvAFxDG44cZ7ljk1MKuiDawQ/wmDfe9kNk2hXSxsD6dNHIQhEPy7AMhAlGdBk6kGVjLVnHxrw8tGWGVsCKX/JQknmqDyQK7eA=
Received: by 10.65.123.9 with SMTP id a9mr3237092qbn; Mon, 10 Oct 2005 05:27:54 -0700 (PDT)
Received: by 10.65.147.9 with HTTP; Mon, 10 Oct 2005 05:27:54 -0700 (PDT)
Message-ID: <8c19328e0510100527l71e68cfdv@mail.gmail.com>
Date: Mon, 10 Oct 2005 14:27:54 +0200
From: Ran Liebermann <ranmails@gmail.com>
To: idr@ietf.org
Subject: Re: [Idr] WG Last Call on draft-ietf-idr-as4bytes-11.txt
In-Reply-To: <200510071641.j97GfgG21459@merlot.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200510071641.j97GfgG21459@merlot.juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: quoted-printable
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On 07/10/05, Yakov Rekhter <yakov@juniper.net> wrote:
> Folks,
>
> This is to start the WG Last Call on advancing draft-ietf-idr-as4bytes-11.txt
> to a Proposed Standard. The implementation report is
> draft-huston-idr-as4bytes-survey-00.txt.

A couple of things:

1.
Just one cosmetic thing.  In my not-fully-English OS I see some funky
characters at the end of section 5.2.2 (last paragraph of page 3, 2nd
line from the top of the paragraph), between "Autonomous System" and
"AS number".

2.
There wasn't any mentioning as to the reserved AS numbers (RFC 1930
section 10).  I think it should be explicitly mentioned that a NEW BGP
speaker peering with an OLD speaker must not insert a reserved AS
number to the NEW_AS_PATH attribute.

Cheers,
--
Ran.

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr