IETF Logo Mail Archive

Re: [Idr] draft-ietf-as-pathlimit-02

Neil Matthew <neil@abelon.com> Tue, 19 December 2006 17:54 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwjAm-0003li-GG; Tue, 19 Dec 2006 12:54:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwjAk-0003lX-KX for idr@ietf.org; Tue, 19 Dec 2006 12:54:38 -0500
Received: from mailout20.yourhostingaccount.com ([65.254.253.163]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwjAj-0000gK-EG for idr@ietf.org; Tue, 19 Dec 2006 12:54:38 -0500
Received: from scan05.yourhostingaccount.com ([10.1.1.235] helo=scan05.yourhostingaccount.com) by mailout20.yourhostingaccount.com with esmtp (Exim) id 1GwjAj-0002UB-04 for idr@ietf.org; Tue, 19 Dec 2006 12:54:37 -0500
Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] ident=exim) by scan05.yourhostingaccount.com with spamscanlookuphost (Exim) id 1GwjAc-0005k4-Qh for idr@ietf.org; Tue, 19 Dec 2006 12:54:31 -0500
Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] helo=authsmtp10.yourhostingaccount.com) by scan05.yourhostingaccount.com with esmtp (Exim) id 1GwjAV-0005jN-7n for idr@ietf.org; Tue, 19 Dec 2006 12:54:25 -0500
Received: from 108.114.2.81.in-addr.arpa ([81.2.114.108] helo=[192.168.0.43]) by authsmtp10.yourhostingaccount.com with esmtpa (Exim) id 1GwjAU-0003Cq-QP; Tue, 19 Dec 2006 12:54:23 -0500
Message-ID: <4588274A.8030403@abelon.com>
Date: Tue, 19 Dec 2006 17:54:18 +0000
From: Neil Matthew <neil@abelon.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02
References: <F18A20CD-BAB7-4D36-9943-B4321201C34E@cisco.com> <45866F7E.50000@abelon.com> <27404B08-CC60-4BEE-B0A3-221375A8D499@tony.li> <4587AE12.3050902@abelon.com> <759E57E8-B549-47BE-984F-630F30F3E203@tony.li>
In-Reply-To: <759E57E8-B549-47BE-984F-630F30F3E203@tony.li>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-EN-UserInfo: e65bfd3d72dfaaaf5ffb0de99fd01ea2:0d98aba8e5f6749be2df7f931a889135
X-EN-AuthUser: neilrm
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: idr@ietf.org
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>
Errors-To: idr-bounces@ietf.org

Hi Tony

<snip>

>
> That said, that's all about 4271 and is completely orthogonal to  
> AS_PATHLIMIT.  As I said before (and I really meant), I'm not trying  
> to change the semantics of 4271.  What I'd like to do then is to  
> morph the AS_PATHLIMIT text to address your concern.  Let me propose  
> a replacement to the entire paragraph:
>
>     To ensure loop prevention, BGP requires that all aggregate routes  
> with truncated
>     AS paths be originated with the ATOMIC_AGGREGATE attribute.  To 
> help  ensure
>     compliance with this, sites that choose to advertise the  
> AS_PATHLIMIT path attribute
>     should advertise the ATOMIC_AGGREGATE on all less specific 
> covering  prefixes.
>
> Does that work for you?

Yes.  Thanks.

Cheers

Neil


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

v2.23.0 | Report a Bug | By Email