Re: [Idr] draft-ietf-idr-as0-00 ?
Warren Kumari <warren@kumari.net> Thu, 01 December 2011 21:50 UTC
Return-Path: <warren@kumari.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D90E41F0CB7 for <idr@ietfa.amsl.com>; Thu, 1 Dec 2011 13:50:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y7plbubbk0aA for <idr@ietfa.amsl.com>; Thu, 1 Dec 2011 13:50:53 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 17F2A1F0C91 for <idr@ietf.org>; Thu, 1 Dec 2011 13:50:52 -0800 (PST)
Received: from dhcp-172-19-119-228.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id C89001B40424; Thu, 1 Dec 2011 16:50:51 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAL9jLaYgu-OFgF2LOKCQXJ+GuYJKEaGRrpfH-ViRzOwW68+Rtg@mail.gmail.com>
Date: Thu, 01 Dec 2011 16:50:49 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A106376-42BC-404B-8460-BBF415049943@kumari.net>
References: <7E27D7DD-8A61-43E8-904E-DEDB3B2D2C92@kumari.net> <14DD6B3A-B114-4F42-B6D0-37CC377D28C5@juniper.net> <4EC06F20.9020906@cisco.com> <4897DDFA-095B-45BA-82F1-2FBC45747BA0@kumari.net> <CAL9jLaYgu-OFgF2LOKCQXJ+GuYJKEaGRrpfH-ViRzOwW68+Rtg@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: idr@ietf.org
Subject: Re: [Idr] draft-ietf-idr-as0-00 ?
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 21:50:54 -0000
[ Changed subject to reflect new title ] On Dec 1, 2011, at 3:38 PM, Christopher Morrow wrote: > On Sat, Nov 19, 2011 at 5:57 PM, Warren Kumari <warren@kumari.net> wrote: >> >> On Nov 13, 2011, at 8:30 PM, Enke Chen wrote: >> >>> Support, but with the following suggestions: >>> >>> 1) Nit: change "bgp listener" to "bgp speaker". >> >> Thank you, done. >> >>> >>> 2) The following language is not very precise. Due to the incremental nature, we will need to remove the existing route too. >>> >>> ----- >>> a BGP >>> listener MUST NOT accept an announcement which has an AS number of >>> zero in the AS-PATH attribute, and SHOULD log the fact that it has >>> done so. >>> ----- >>> >>> How about the following: >>> >>> An UPDATE message that contains the AS number of zero in the AS-PATH attribute >>> MUST be considered as malformed, and be handled by the procedures specified in >>> >>> draft-ietf-idr-optional-transitive-04.txt >>> >>> 3) If this draft is adopted, we should also add AS 0 as one of the error conditions in >>> rfc4893bis. >> >> John also provided some text for that section and Keyur suggested that we log and treat as a WITHDRAW. >> >> This would read as: >> "This document specifies that a BGP speaker MUST NOT originate or propagate a route with an AS number of zero. If a BGP speaker receives a route which has an AS number of zero in the AS_PATH attribute, it SHOULD be logged and treated as a WITHDRAW." >> > > a question came up recently (today) on nanog about how AS0 should be > treated wrt AGGREGATOR attributes... Should this say use of AS0 > anywhere (make a list perhaps?) is verboten? (or was that assumed > already?) Actually Keyur Patel already pointed out the Aggregator (and AS4 Aggregator) attribute issue, and I included text in the WG version of the doc, which I posted recently (although I have just realized that I entered the text as "Aggregator" and not "AGGREGATOR", same for AS4...) Which reminds me -- would folk please review draft-ietf-idr-as0-00 ( http://tools.ietf.org/html/draft-ietf-idr-as0-00 ) and provide feedback? I *think* that I incorporated everyones comments, although I accidentally overwrote the changed version with an older version (never edit a file in two editors at once :-)) and so may have missed some... W > >> This avoids having a normative reverence to the optional-transitive draft and is (IMO) a little clearer. It also saves optional-transitive from referencing this, and so we avoid the deadlock... >> >> Thoughts? >> >> W >> >> >>> >>> Thanks. -- Enke >>> >>> >>> On 10/28/11 1:51 PM, John Scudder wrote: >>>> Folks, >>>> >>>> Please send comments to the list prior to the IDR meeting on November 15. >>>> >>>> Thanks, >>>> >>>> --John >>>> >>>> On Oct 27, 2011, at 9:29 AM, Warren Kumari wrote: >>>> >>>> >>>>> Hello IDRites, >>>>> >>>>> I would like to draw your attention to draft-wkumari-idr-as0-01.txt ( >>>>> http://tools.ietf.org/html/draft-wkumari-idr-as0-01 >>>>> ) - I am asking that this draft be considered for WG adoption. >>>>> >>>>> >>>>> I have already received some feedback, mainly suggesting: >>>>> >>>>> - Add a text for AS number 0 as a reserved in Aggregator and AS4 >>>>> Aggregator attribute >>>>> >>>>> - Add text for AS number 0 as a reserved value in communities and >>>>> extended communities. (RFC 1997 and Four-octet AS Specific Extended >>>>> Communities) >>>>> >>>>> Also suggested was providing a little more information on what to do it you do receive a route containing AS0 (more descriptive than just "MUST NOT accept" (for example, stating that it should be "excluded from the Phase 2 decision function")). >>>>> >>>>> Anyway, I would value your feedback and input. >>>>> >>>>> W >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Idr mailing list >>>>> >>>>> Idr@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/idr >>>> _______________________________________________ >>>> Idr mailing list >>>> >>>> Idr@ietf.org >>>> https://www.ietf.org/mailman/listinfo/idr >>> >>> >>> _______________________________________________ >>> Idr mailing list >>> Idr@ietf.org >>> https://www.ietf.org/mailman/listinfo/idr >> >> _______________________________________________ >> Idr mailing list >> Idr@ietf.org >> https://www.ietf.org/mailman/listinfo/idr >
- [Idr] Accept draft-wkumari-idr-as0-01.txt ? Warren Kumari
- Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ? Robert Raszuk
- Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ? John Scudder
- Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ? Brian Dickson
- Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ? Christopher Morrow
- Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ? Enke Chen
- Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ? Jeff Tantsura
- Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ? Arturo Servin
- Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ? Jakob Heitz
- Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ? Warren Kumari
- Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ? Christopher Morrow
- Re: [Idr] draft-ietf-idr-as0-00 ? Warren Kumari
- Re: [Idr] draft-ietf-idr-as0-00 ? Enke Chen
- Re: [Idr] draft-ietf-idr-as0-00 ? Warren Kumari
- Re: [Idr] draft-ietf-idr-as0-00 ? Jakob Heitz
- Re: [Idr] draft-ietf-idr-as0-00 ? Jeff Tantsura
- Re: [Idr] draft-ietf-idr-as0-00 ? Danny McPherson
- [Idr] draft-ietf-idr-rfc4893bis-00.txt / draft-ie… bruno.decraene
- Re: [Idr] draft-ietf-idr-as0-00 ? bruno.decraene
- Re: [Idr] draft-ietf-idr-as0-00 ? Jakob Heitz
- Re: [Idr] draft-ietf-idr-as0-00 ? Enke Chen