Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ?

Warren Kumari <warren@kumari.net> Sun, 20 November 2011 14:02 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 119F421F8672 for <idr@ietfa.amsl.com>; Sun, 20 Nov 2011 06:02:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.103
X-Spam-Level:
X-Spam-Status: No, score=-106.103 tagged_above=-999 required=5 tests=[AWL=-0.496, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, 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 Q6NXOJpZXQgA for <idr@ietfa.amsl.com>; Sun, 20 Nov 2011 06:02:27 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 53FC821F85FF for <idr@ietf.org>; Sun, 20 Nov 2011 06:02:27 -0800 (PST)
Received: from [192.168.0.12] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 08CF31B404CC; Sun, 20 Nov 2011 09:02:24 -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: <4EC06F20.9020906@cisco.com>
Date: Sat, 19 Nov 2011 17:57:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4897DDFA-095B-45BA-82F1-2FBC45747BA0@kumari.net>
References: <7E27D7DD-8A61-43E8-904E-DEDB3B2D2C92@kumari.net> <14DD6B3A-B114-4F42-B6D0-37CC377D28C5@juniper.net> <4EC06F20.9020906@cisco.com>
To: Enke Chen <enkechen@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: idr@ietf.org
Subject: Re: [Idr] Accept draft-wkumari-idr-as0-01.txt ?
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: Sun, 20 Nov 2011 14:02:28 -0000

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."

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