IETF Logo Mail Archive

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

Jakob Heitz <jakob.heitz@ericsson.com> Mon, 14 November 2011 02:45 UTC

Return-Path: <jakob.heitz@ericsson.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 56E8A1F0C90 for <idr@ietfa.amsl.com>; Sun, 13 Nov 2011 18:45:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.262
X-Spam-Level:
X-Spam-Status: No, score=-6.262 tagged_above=-999 required=5 tests=[AWL=0.337, BAYES_00=-2.599, 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 rlInwy-nqR0u for <idr@ietfa.amsl.com>; Sun, 13 Nov 2011 18:45:22 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id B43B01F0C8F for <idr@ietf.org>; Sun, 13 Nov 2011 18:45:22 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pAE2jLDs009834 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 13 Nov 2011 20:45:21 -0600
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.111]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Sun, 13 Nov 2011 21:45:20 -0500
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Enke Chen <enkechen@cisco.com>
Date: Sun, 13 Nov 2011 21:46:01 -0500
Thread-Topic: [Idr] Accept draft-wkumari-idr-as0-01.txt ?
Thread-Index: Acyid3MDhUmGykAjQjKpa+DsneRKBw==
Message-ID: <493C1D64-07EE-4FCD-8F75-1FEA233C329D@ericsson.com>
References: <7E27D7DD-8A61-43E8-904E-DEDB3B2D2C92@kumari.net> <14DD6B3A-B114-4F42-B6D0-37CC377D28C5@juniper.net> <4EC06F20.9020906@cisco.com>
In-Reply-To: <4EC06F20.9020906@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "idr@ietf.org" <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: Mon, 14 Nov 2011 02:45:23 -0000

+1 (Enke's suggestion)

--
Jakob Heitz.


On Nov 13, 2011, at 5:28 PM, "Enke Chen" <enkechen@cisco.com<mailto:enkechen@cisco.com>> wrote:


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<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr


_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr



_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email