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

Enke Chen <enkechen@cisco.com> Mon, 14 November 2011 01:28 UTC

Return-Path: <enkechen@cisco.com>
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 BC6D721F85A1 for <idr@ietfa.amsl.com>; Sun, 13 Nov 2011 17:28:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.078
X-Spam-Level:
X-Spam-Status: No, score=-6.078 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 AsBNhBtv6n69 for <idr@ietfa.amsl.com>; Sun, 13 Nov 2011 17:28:37 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id E266021F858C for <idr@ietf.org>; Sun, 13 Nov 2011 17:28:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=enkechen@cisco.com; l=5607; q=dns/txt; s=iport; t=1321234117; x=1322443717; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=Pw6JzWlP7GE0Mit48cWoaTMcq4vRXn5PkhnlUVUxHNw=; b=VoIsO1YNFa/1EtMWU/I9mkUt1i22SxgWqb5Q8xRhUrcGgNIxFV7KWyEA q51fm/Neo0jbHOQ9gWhTJsgW1vSYQoK8EEJKr2S33jizbdWVOh6knsaNa Nfe5YmjVTbg4nkLfBjw5IPyiQBTXkeOWXjH9221Ccj7hPd8eB6ZWMug/d M=;
X-IronPort-AV: E=Sophos; i="4.69,504,1315180800"; d="scan'208,217"; a="14014717"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 14 Nov 2011 01:28:37 +0000
Received: from sjc-vpn7-1185.cisco.com (sjc-vpn7-1185.cisco.com [10.21.148.161]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAE1SaIO021875; Mon, 14 Nov 2011 01:28:36 GMT
Message-ID: <4EC06F20.9020906@cisco.com>
Date: Sun, 13 Nov 2011 17:30:08 -0800
From: Enke Chen <enkechen@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: idr@ietf.org
References: <7E27D7DD-8A61-43E8-904E-DEDB3B2D2C92@kumari.net> <14DD6B3A-B114-4F42-B6D0-37CC377D28C5@juniper.net>
In-Reply-To: <14DD6B3A-B114-4F42-B6D0-37CC377D28C5@juniper.net>
Content-Type: multipart/alternative; boundary="------------080800060405000805030007"
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: Mon, 14 Nov 2011 01:28:38 -0000

Support, but with the following suggestions:

1) Nit: change "bgp listener" to "bgp speaker".

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.

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