From idr-bounces@ietf.org Sun Dec 03 13:13:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gqvly-0004Wv-9Y; Sun, 03 Dec 2006 13:09:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gqvlx-0004Wd-0e
	for idr@ietf.org; Sun, 03 Dec 2006 13:09:05 -0500
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gqvlv-0004GY-MT
	for idr@ietf.org; Sun, 03 Dec 2006 13:09:04 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id kB3I93X56817
	for <idr@ietf.org>; Sun, 3 Dec 2006 10:09:03 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id kB3I8wB89699
	for <idr@ietf.org>; Sun, 3 Dec 2006 10:08:58 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200612031808.kB3I8wB89699@merlot.juniper.net>
To: idr@ietf.org
Subject: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <70697.1165169337.1@juniper.net>
Date: Sun, 03 Dec 2006 10:08:57 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
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

Folks,

May I suggest that before adopting this as a WG document the authors
would produce a revised document that would reflect the comments
they received.

Yakov.
------- Forwarded Message

Date:    Mon, 20 Nov 2006 08:57:56 -0800
From:    Yakov Rekhter <yakov@juniper.net>
To:      idr@ietf.org

Folks,

Please comment on the attached. The deadline for comments is
Dec 1, 2006.

Yakov.
- ------- Forwarded Message

Date:    Fri, 17 Nov 2006 12:47:36 -0500
From:    Eric Rosen <erosen@cisco.com>
To:      idr@ietf.org
Subject: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt

At  the  IDR  WG  meeting  last  week,  we  discussed  draft-lefaucheur-idr-
v4nlri-v6nh.  I would like to propose now  that this be adopted as an IDR WG
document.  Your feedback is invited. 

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

- ------- End of Forwarded Message


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

------- End of Forwarded Message


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



From idr-bounces@ietf.org Thu Dec 07 06:34:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsHSG-0003A8-Mj; Thu, 07 Dec 2006 06:30:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsHSF-0003A0-PX; Thu, 07 Dec 2006 06:30:19 -0500
Received: from kremlin.juniper.net ([207.17.137.120])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GsHSD-0008Rx-H7; Thu, 07 Dec 2006 06:30:19 -0500
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by kremlin.juniper.net with ESMTP; 07 Dec 2006 03:27:06 -0800
X-IronPort-AV: i="4.09,508,1157353200"; 
	d="scan'208"; a="621170687:sNHT29392508"
Received: from emailwf1.jnpr.net ([10.10.2.33]) by proton.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Dec 2006 06:30:16 -0500
Received: from 172.28.13.14 ([172.28.13.14]) by emailwf1.jnpr.net
	([10.10.2.33]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu,  7 Dec 2006 11:30:15 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Thu, 07 Dec 2006 06:30:11 -0500
From: Bruno Rijsman <brijsman@juniper.net>
To: <idr@ietf.org>
Message-ID: <C19D6573.4FC5%brijsman@juniper.net>
Thread-Topic: New "BFD session down" error sub-code for the BGP Cease
	NOTIFICATION message.
Thread-Index: AccZ8w49TLmdYIXmEduHKAAX8sK9Uw==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 07 Dec 2006 11:30:16.0765 (UTC)
	FILETIME=[11AD0ED0:01C719F3]
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: rtg-bfd@ietf.org
Subject: [Idr] New "BFD session down" error sub-code for the BGP Cease
 NOTIFICATION message.
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

I would like to propose to allocate a new "BFD session down" error subcode
(value 9) for the BGP Cease NOTIFICATION message.
 
Since BGP error subcodes are allocated using the "early IANA allocation"
process [RFC4020] which requires a proposed standards I-D, I have posted a
very small draft at
http://tools.ietf.org/wg/bfd/draft-rijsman-bfd-down-subcode-00.txt
 
Comments on the subcode itself or on the procedure for allocating it are
welcome.
 
-- Bruno

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



From idr-bounces@ietf.org Thu Dec 07 11:33:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsM98-00065M-Hx; Thu, 07 Dec 2006 11:30:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsM97-00063J-GA
	for idr@ietf.org; Thu, 07 Dec 2006 11:30:53 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsM8Q-0005Ct-7g
	for idr@ietf.org; Thu, 07 Dec 2006 11:30:53 -0500
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 07 Dec 2006 17:30:09 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kB7GU9U3024029; 
	Thu, 7 Dec 2006 17:30:09 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kB7GU9AJ011275; 
	Thu, 7 Dec 2006 17:30:09 +0100 (MET)
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Dec 2006 17:30:08 +0100
Received: from [144.254.53.120] ([144.254.53.120]) by xfe-ams-332.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Dec 2006 17:30:08 +0100
In-Reply-To: <200612031808.kB3I8wB89699@merlot.juniper.net>
References: <200612031808.kB3I8wB89699@merlot.juniper.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <684C1548-76C1-449A-9913-6583D36BE314@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
Date: Thu, 7 Dec 2006 17:28:36 +0100
To: Yakov Rekhter <yakov@juniper.net>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 07 Dec 2006 16:30:08.0783 (UTC)
	FILETIME=[F5C121F0:01C71A1C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1422; t=1165509009;
	x=1166373009; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20draft-lefaucheur-idr-v4nlri-v6nh-00.txt
	|Sender:=20; bh=GooY6SZRbxLMdN3jWjlyHqshdqZ6/U9RGPk/w9CUu7M=;
	b=lyyP7ugjWvddOcCUx6/SmHzZ08SU2b+5FDkFiAATXh9zIMDB76ApEWDZr0genQcY9sNxTQ8M
	KJsmSEFNR64p+ZSfGYK0Y/MJFaDmSlAxStxAxi0nH4hRxF+InWS2M+Ui;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: idr@ietf.org, Francois Le Faucheur IMAP <flefauch@cisco.com>
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

Yes, will do Yakov.

On 3 Dec 2006, at 19:08, Yakov Rekhter wrote:

> Folks,
>
> May I suggest that before adopting this as a WG document the authors
> would produce a revised document that would reflect the comments
> they received.
>
> Yakov.
> ------- Forwarded Message
>
> Date:    Mon, 20 Nov 2006 08:57:56 -0800
> From:    Yakov Rekhter <yakov@juniper.net>
> To:      idr@ietf.org
>
> Folks,
>
> Please comment on the attached. The deadline for comments is
> Dec 1, 2006.
>
> Yakov.
> - ------- Forwarded Message
>
> Date:    Fri, 17 Nov 2006 12:47:36 -0500
> From:    Eric Rosen <erosen@cisco.com>
> To:      idr@ietf.org
> Subject: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
>
> At  the  IDR  WG  meeting  last  week,  we  discussed  draft- 
> lefaucheur-idr-
> v4nlri-v6nh.  I would like to propose now  that this be adopted as  
> an IDR WG
> document.  Your feedback is invited.
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr
>
> - ------- End of Forwarded Message
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr
>
> ------- End of Forwarded Message
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr

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



From idr-bounces@ietf.org Thu Dec 07 12:07:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsMgW-0006ey-94; Thu, 07 Dec 2006 12:05:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsMgU-0006et-UN
	for idr@ietf.org; Thu, 07 Dec 2006 12:05:22 -0500
Received: from mailout12.yourhostingaccount.com ([65.254.253.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsMgP-0002BW-E2
	for idr@ietf.org; Thu, 07 Dec 2006 12:05:22 -0500
Received: from scan02.yourhostingaccount.com ([10.1.1.232]
	helo=scan02.yourhostingaccount.com)
	by mailout12.yourhostingaccount.com with esmtp (Exim)
	id 1GsMgP-00027k-0o for idr@ietf.org; Thu, 07 Dec 2006 12:05:17 -0500
Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8] ident=exim)
	by scan02.yourhostingaccount.com with spamscanlookuphost (Exim)
	id 1GsMgO-0006CG-Lj for idr@ietf.org; Thu, 07 Dec 2006 12:05:16 -0500
Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8]
	helo=authsmtp08.yourhostingaccount.com)
	by scan02.yourhostingaccount.com with esmtp (Exim)
	id 1GsMgN-0006CD-Ow for idr@ietf.org; Thu, 07 Dec 2006 12:05:15 -0500
Received: from 108.114.2.81.in-addr.arpa ([81.2.114.108] helo=[192.168.0.43])
	by authsmtp08.yourhostingaccount.com with esmtpa (Exim)
	id 1GsMgN-0007KS-BO for idr@ietf.org; Thu, 07 Dec 2006 12:05:15 -0500
Message-ID: <457849C3.1000609@abelon.com>
Date: Thu, 07 Dec 2006 17:05:07 +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: idr@ietf.org
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: d6b246023072368de71562c0ab503126
Subject: [Idr] draft-ietf-idr-as-pathlimit-02 - Private ASes
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 Folks

Why does the draft indicate that private AS numbers should not be 
counted when determining the path length?

In order to facilitate the decision process BGP already maintains a 
count that satisfies the other requirements (counting AS_SET as one, 
ditching confederation ASes).  Does explicitly referring to private ASes 
imply another counter?

Setting aside the validity of mixing private and public ASes, what 
happens if an AS_SET contains one or more private ASes?  Does this still 
count as 1 or is it 0?

Cheers


Neil


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



From idr-bounces@ietf.org Thu Dec 07 18:27:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsSb9-0001dc-5G; Thu, 07 Dec 2006 18:24:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsSb7-0001cE-1A; Thu, 07 Dec 2006 18:24:13 -0500
Received: from elasmtp-junco.atl.sa.earthlink.net ([209.86.89.63])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GsSb5-0002Yr-CP; Thu, 07 Dec 2006 18:24:13 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
	b=s5egFlPUDcyP044Io/cHUrp1WpfL7bSkJB4K/vnvTnWSOtAt0xhmiG8ZjgmzgG0x;
	h=Received:Message-ID:Date:From:X-Sender:X-Mailer:X-Accept-Language:MIME-Version:To:CC:Subject:References:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.153.179] (helo=earthlink.net)
	by elasmtp-junco.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1GsSb4-0000iY-N1; Thu, 07 Dec 2006 18:24:10 -0500
Message-ID: <4578A0D6.2EE3DB9B@earthlink.net>
Date: Thu, 07 Dec 2006 15:16:38 -0800
From: Erblichs <erblichs@earthlink.net>
X-Sender: "Erblichs" <erblichs@earthlink.net@smtpauth.earthlink.net>
	(Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruno Rijsman <brijsman@juniper.net>
Subject: Re: [Idr] New "BFD session down" error sub-code for the BGP 
	CeaseNOTIFICATION message.
References: <C19D6573.4FC5%brijsman@juniper.net>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec79f161a5af9976e99312be50a54c8bd39c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.153.179
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: idr@ietf.org, rtg-bfd@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

Bruno,

	Can I ask "1" stupid question? 

	Does this mean that the state variable "bfd.SessionState"
	is Down or AdminDown? Or both?

	Mitchell Erblich
	-------------------

	

Bruno Rijsman wrote:
> 
> I would like to propose to allocate a new "BFD session down" error subcode
> (value 9) for the BGP Cease NOTIFICATION message.
> 
> Since BGP error subcodes are allocated using the "early IANA allocation"
> process [RFC4020] which requires a proposed standards I-D, I have posted a
> very small draft at
> http://tools.ietf.org/wg/bfd/draft-rijsman-bfd-down-subcode-00.txt
> 
> Comments on the subcode itself or on the procedure for allocating it are
> welcome.
> 
> -- Bruno
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr

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



From idr-bounces@ietf.org Fri Dec 08 10:07:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GshGL-0000dZ-1Q; Fri, 08 Dec 2006 10:03:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GshGI-0000c5-SU; Fri, 08 Dec 2006 10:03:42 -0500
Received: from kremlin.juniper.net ([207.17.137.120])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GshGG-0008Qw-3P; Fri, 08 Dec 2006 10:03:42 -0500
Received: from unknown (HELO pi-smtp.jnpr.net) ([10.10.2.36])
	by kremlin.juniper.net with ESMTP; 08 Dec 2006 07:00:27 -0800
X-IronPort-AV: i="4.09,514,1157353200"; 
	d="scan'208"; a="621889303:sNHT35193544"
Received: from emailwf1.jnpr.net ([10.10.2.33]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Fri, 8 Dec 2006 10:03:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Idr] New "BFD session down" error sub-code for the BGP
	CeaseNOTIFICATION message.
Date: Fri, 8 Dec 2006 10:03:36 -0500
Message-ID: <B7C1105A5EF44D45B334B2FB0B86C9DB397372@emailwf1.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] New "BFD session down" error sub-code for the BGP
	CeaseNOTIFICATION message.
Thread-Index: AccaVtaZS9zJiX09T96EFhkMFHhK7wAgpFFA
From: "Bruno Rijsman" <brijsman@juniper.net>
To: "Erblichs" <erblichs@earthlink.net>
X-OriginalArrivalTime: 08 Dec 2006 15:03:38.0667 (UTC)
	FILETIME=[0A9E07B0:01C71ADA]
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: idr@ietf.org, rtg-bfd@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

MitchellErblich> Does this mean that the state variable
"bfd.SessionState" is Down or AdminDown? Or both?

That is actually a very good question.

The cease notification with subcode "BFD session down" should be sent
when the BFD session transitions from "Up" to "Down".

In other words, the notification indicates that the session *went*
operationally "Down" and not that the session *is* operationally "Down".

I should probably rename the subcode to "BFD session lost" or "BFD
session went down" to clarify this.

Just to give some background information: all BFD for BGP
implementations which I am familiar with (include one from another major
vendor) work as follows:

(1) When the BGP session reaches state established (or sometimes
earlier), a BFD session is initiated to the address of the BGP neighbor.

(2) If the BFD session fails to come up (e.g. because BFD is not
configured on the remote side) the BGP session is still allowed to stay
in state established. So, the fact that the BFD session is "Down" at
this point does *not* trigger BGP to send a notification.

(3) Let's assume that the BFD session does come "Up" at some point in
time.

(4) If the BFD session goes "Down" after that, the BGP session will be
terminated, and BGP will send a notification with the new error subcode
"BFD session (went) down".

(5) We should not send the notification when BFD goes from "Up" to
"AdminDown" (e.g. when BFD is unconfigured) because this transition does
not indicate a failure.

Someone (*) pointed out that if the BFD session went down because of a
real link failure, it is unlikely that the notification will make it to
the other side. The new error subcode is still useful:

- To detect false failures: BFD session went down despite the fact that
the link is still up (e.g. BFD timers too aggressive for a given
implementation).

- For local side debugging: even though the notification would not make
it to the other side, many CLI and MIB implementations report the error
code and subcode of the most recently sent notification.

(*) =3D The reason I don't credit the person by name is that I assume =
that
person doesn't want his name on a public mailing list since he sent the
comment only to me.

-- Bruno=20

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



From idr-bounces@ietf.org Fri Dec 08 14:19:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GslCp-0000Yw-Ly; Fri, 08 Dec 2006 14:16:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GslCn-0000Yh-Mm
	for idr@ietf.org; Fri, 08 Dec 2006 14:16:21 -0500
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GslCl-0002nj-DW
	for idr@ietf.org; Fri, 08 Dec 2006 14:16:21 -0500
Received: from yxu1a17.hopcount.ca ([199.212.90.17])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.63 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1GslDF-00095J-Jj; Fri, 08 Dec 2006 19:16:49 +0000
In-Reply-To: <457849C3.1000609@abelon.com>
References: <457849C3.1000609@abelon.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A2E0C2DF-04A1-4239-8181-A857F5F15E68@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Subject: Re: [Idr] draft-ietf-idr-as-pathlimit-02 - Private ASes
Date: Fri, 8 Dec 2006 14:15:48 -0500
To: Neil Matthew <neil@abelon.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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 Neil,

On 7-Dec-2006, at 12:05, Neil Matthew wrote:

> Why does the draft indicate that private AS numbers should not be  
> counted when determining the path length?
>
> In order to facilitate the decision process BGP already maintains a  
> count that satisfies the other requirements (counting AS_SET as  
> one, ditching confederation ASes).  Does explicitly referring to  
> private ASes imply another counter?
>
> Setting aside the validity of mixing private and public ASes, what  
> happens if an AS_SET contains one or more private ASes?  Does this  
> still count as 1 or is it 0?

These are excellent questions, but since that text was Tony's, I'd  
prefer to leave him to address your questions. He's a little tied up  
right now, but tells me that he will be back on-deck in the next  
little while, with more time to spend on IETF stuff.


Joe

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



From idr-bounces@ietf.org Mon Dec 11 16:00:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtsES-0001fW-6W; Mon, 11 Dec 2006 15:58:40 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtsER-0001fI-5j; Mon, 11 Dec 2006 15:58:39 -0500
Received: from elasmtp-mealy.atl.sa.earthlink.net ([209.86.89.69])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GtsE0-0008OO-W4; Mon, 11 Dec 2006 15:58:39 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
	b=oy5HvsFwhJUrfOjZkKr0G2IZPlXC25N0bYDHMEeSnBNPuJ4BednZUUE2d5ao+1KH;
	h=Received:Message-ID:Date:From:X-Sender:X-Mailer:X-Accept-Language:MIME-Version:To:CC:Subject:References:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.154.60] (helo=earthlink.net)
	by elasmtp-mealy.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1GtsE0-0000rp-3f; Mon, 11 Dec 2006 15:58:12 -0500
Message-ID: <457DC48A.D4EC6C9C@earthlink.net>
Date: Mon, 11 Dec 2006 12:50:18 -0800
From: Erblichs <erblichs@earthlink.net>
X-Sender: "Erblichs" <erblichs@earthlink.net@smtpauth.earthlink.net>
	(Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruno Rijsman <brijsman@juniper.net>
Subject: Re: [Idr] New "BFD session down" error sub-code for the BGP  
	CeaseNOTIFICATION message.
References: <B7C1105A5EF44D45B334B2FB0B86C9DB397372@emailwf1.jnpr.net>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec792bab93b14e9feb0d10d721f83c05f6f5350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.154.60
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: idr@ietf.org, rtg-bfd@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

Bruno Rijsman,

	You seem to separate the message notfication from the
	actual  status of the link....

> The cease notification with subcode "BFD session down" should be sent
> when the BFD session transitions from "Up" to "Down".
> 
> In other words, the notification indicates that the session *went*
> operationally "Down" and not that the session *is* operationally "Down".
> 
	
	Which seems to be opposite of
	6.7.5. Detecting Failures with the Echo Function.

	IMO,,

	1) If the local BFD doesn't see an echo, it should somehow
	   generate a local BFD session down and get the error sub-code
	   to the local BGP. This is a guranteed deliverable msg.

	2) It would seem here that if the session "went" operationally
	   down then it "is" operationally down. At least until we see
	   a new echo / hello / alive type pkt.


	--
	This is when the endpoint can only REALLY state that I am here, by
	the sending of echos / hellos / alive pkts.

	So, the problem I see is that if you timers are functionally correct
	the message is only generate locally. So, we already have that in
	6.7.5 and the non-recievable message is not sent as you already
	stated.

	And that if your timers are too agressive you will take down the
	BFD and the BGP session / connections..

	Thus, I don't know why you just don't determine the session condition
	and notification locally by section 6.7.5.


	Mitchell Erblich
	

Bruno Rijsman wrote:
> 
> MitchellErblich> Does this mean that the state variable
> "bfd.SessionState" is Down or AdminDown? Or both?
> 
> That is actually a very good question.
> 
> The cease notification with subcode "BFD session down" should be sent
> when the BFD session transitions from "Up" to "Down".
> 
> In other words, the notification indicates that the session *went*
> operationally "Down" and not that the session *is* operationally "Down".
> 
> I should probably rename the subcode to "BFD session lost" or "BFD
> session went down" to clarify this.
> 
> Just to give some background information: all BFD for BGP
> implementations which I am familiar with (include one from another major
> vendor) work as follows:
> 
> (1) When the BGP session reaches state established (or sometimes
> earlier), a BFD session is initiated to the address of the BGP neighbor.
> 
> (2) If the BFD session fails to come up (e.g. because BFD is not
> configured on the remote side) the BGP session is still allowed to stay
> in state established. So, the fact that the BFD session is "Down" at
> this point does *not* trigger BGP to send a notification.
> 
> (3) Let's assume that the BFD session does come "Up" at some point in
> time.
> 
> (4) If the BFD session goes "Down" after that, the BGP session will be
> terminated, and BGP will send a notification with the new error subcode
> "BFD session (went) down".
> 
> (5) We should not send the notification when BFD goes from "Up" to
> "AdminDown" (e.g. when BFD is unconfigured) because this transition does
> not indicate a failure.
> 
> Someone (*) pointed out that if the BFD session went down because of a
> real link failure, it is unlikely that the notification will make it to
> the other side. The new error subcode is still useful:
> 
> - To detect false failures: BFD session went down despite the fact that
> the link is still up (e.g. BFD timers too aggressive for a given
> implementation).
> 
> - For local side debugging: even though the notification would not make
> it to the other side, many CLI and MIB implementations report the error
> code and subcode of the most recently sent notification.
> 
> (*) = The reason I don't credit the person by name is that I assume that
> person doesn't want his name on a public mailing list since he sent the
> comment only to me.
> 
> -- Bruno

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



From idr-bounces@ietf.org Tue Dec 12 06:57:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gu6Cq-0007xx-PQ; Tue, 12 Dec 2006 06:53:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gu6Cp-0007w8-DJ
	for idr@ietf.org; Tue, 12 Dec 2006 06:53:55 -0500
Received: from giss7a.seg-social.es ([194.179.55.135] helo=smtp.seg-social.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gu6Cl-0005uh-Uo
	for idr@ietf.org; Tue, 12 Dec 2006 06:53:55 -0500
Received: from GWSalida2.correo.portal.ss ([10.99.1.190]) by
	smtp.seg-social.es (Netscape Messaging Server 4.15) with ESMTP
	id JA5T1F02.E83 for <idr@ietf.org>; Tue, 12 Dec 2006 12:53:39 +0100 
From: JUAN-JOSE.ADAN@giss.seg-social.es
X-Priority: 1 (High)
To: idr@ietf.org
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OF6B667ECC.1E22D2E0-ONC1257242.002B0644-C1257242.004160BE@tgss.seg-social.es>
Date: Tue, 12 Dec 2006 12:53:35 +0100
X-MIMETrack: Serialize by Router on GWSalida2/SRV/SEG-SOCIAL(Release
	6.5.5|November 30, 2005) at 12/12/2006 12:53:09
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: [Idr] Draft on "Tunneled Inter-domain Routing", version 01
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,

I have sent a new version of the draft on "Tunneled Inter-domain
Routing" (TIDR): draft-adan-idr-tidr-01.txt.

TIDR allows us to classify prefixes into "identifier prefixes"
and "locator prefixes". Considering that in a full TIDR-aware
Internet transit packet forwarding would be based only on locators
the need to make sure that an autonomous system is authorized
to announce a "locator prefix" is crucial. In my proposal, I
show a way to achieve this by using (1) a specific IP address
range assigned per AS; (2) the LOCATOR attribute to digitally
sign the announcement; and (3) the AS_PATH.

I have included in a new section on "Security Considerations"
these ideas on the authentication of identifier prefixes and
locator prefixes.

Any comments will be appreciated.

Thanks,
Juanjo




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



From idr-bounces@ietf.org Tue Dec 12 15:53:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuEaa-0006N0-Ne; Tue, 12 Dec 2006 15:51:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuEaX-0006JD-Vp; Tue, 12 Dec 2006 15:50:57 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GuEaX-0005Hr-OO; Tue, 12 Dec 2006 15:50:57 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id B21B132B2C;
	Tue, 12 Dec 2006 20:50:57 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GuEaW-00088c-R6; Tue, 12 Dec 2006 15:50:57 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GuEaW-00088c-R6@stiedprstage1.ietf.org>
Date: Tue, 12 Dec 2006 15:50:56 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: idr@ietf.org
Subject: [Idr] I-D ACTION:draft-ooms-v6ops-bgp-tunnel-07.txt 
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title		: Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge Routers (6PE)
	Author(s)	: J. De Clercq, et al.
	Filename	: draft-ooms-v6ops-bgp-tunnel-07.txt
	Pages		: 14
	Date		: 2006-12-12
	
This document explains how to interconnect IPv6 islands over a Multi-
   Protocol Label Switching (MPLS)-enabled IPv4 cloud.  This approach
   relies on IPv6 Provider Edge routers (6PE) which are Dual Stack in
   order to connect to IPv6 islands and to the MPLS core which is only
   required to run IPv4 MPLS.  The 6PE routers exchange the IPv6
   reachability information transparently over the core using the Multi-
   Protocol Border Gateway Protocol (MP-BGP) over IPv4.  In doing so,
   the BGP Next Hop field is used to convey the IPv4 address of the 6PE
   router so that dynamically established IPv4-signaled MPLS Label
   Switched Paths (LSPs) can be used without explicit tunnel
   configuration.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ooms-v6ops-bgp-tunnel-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ooms-v6ops-bgp-tunnel-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ooms-v6ops-bgp-tunnel-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-12-12142417.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ooms-v6ops-bgp-tunnel-07.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ooms-v6ops-bgp-tunnel-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-12-12142417.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From idr-bounces@ietf.org Wed Dec 13 04:22:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuQFv-0004Jt-Ft; Wed, 13 Dec 2006 04:18:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuQFu-0004Jn-4r
	for idr@ietf.org; Wed, 13 Dec 2006 04:18:26 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuQFr-0004en-RL
	for idr@ietf.org; Wed, 13 Dec 2006 04:18:26 -0500
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 13 Dec 2006 10:18:20 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kBD9II3x019858
	for <idr@ietf.org>; Wed, 13 Dec 2006 10:18:18 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kBD9I9AV009138
	for <idr@ietf.org>; Wed, 13 Dec 2006 10:18:18 +0100 (MET)
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 10:18:10 +0100
Received: from [144.254.53.139] ([144.254.53.139]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 10:18:10 +0100
Mime-Version: 1.0 (Apple Message framework v752.3)
To: idr@ietf.org
Message-Id: <0495CEC1-0444-4412-86CB-3846A435270E@cisco.com>
References: <E1GuEaW-00088c-R6@stiedprstage1.ietf.org>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Fwd: [Idr] I-D ACTION:draft-ooms-v6ops-bgp-tunnel-07.txt 
Date: Wed, 13 Dec 2006 10:16:34 +0100
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 13 Dec 2006 09:18:10.0630 (UTC)
	FILETIME=[9BCF5660:01C71E97]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=21503; t=1166001498;
	x=1166865498; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Fwd=3A=20[Idr]=20I-D=20ACTION=3Adraft-ooms-v6ops-bgp-tunnel-0
	7.txt=20 |Sender:=20;
	bh=eNR9BdKhh7xz6T2np4V6Jc24GDrsPVbJQIrIMZG8K3w=;
	b=wjBHwjZRgjNVFQsWQhwHQfmt+4TpeeK4a2AEB9PkHqUOuf9QOHWA2YTZ31CgpFxxm3etJaEe
	nBLtOjnMSejM2suWkp1rUOFtUTe82AyBTyw0Un0oaJbs4WsYxtpuIDbg;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 1df8e4abc9851cb4adb45bd64d8514ae
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>
Content-Type: multipart/mixed; boundary="===============1339077037=="
Errors-To: idr-bounces@ietf.org


--===============1339077037==
Content-Type: multipart/alternative; boundary=Apple-Mail-1-863117380


--Apple-Mail-1-863117380
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hello

Just FYI a new version of the 6PE I-D (draft-ooms-v6ops-bgp-tunnel)  
has just been posted.

This version addresses the comments received during IESG Eval and  
IETF Last Call. Main changes are:

- added paragraph on rationale for 6PE approach (second paragraph of  
the introduction)
- added deployment note (last paragraph of the introduction)
- adjusted some wording in section 2 to make it inline with latest  
version of RFC2858bis
- added MUST requirement for LDP support to guarantee  
interoperability across all implementations
- added MTU considerations (last 3 paragraphs in section 3)
- typos, references, ...

Cheers

Francois

Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: 12 December 2006 21:50:56 GMT+01:00
> To: i-d-announce@ietf.org
> Cc: idr@ietf.org
> Subject: [Idr] I-D ACTION:draft-ooms-v6ops-bgp-tunnel-07.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Inter-Domain Routing Working Group  
> of the IETF.
>
> 	Title		: Connecting IPv6 Islands over IPv4 MPLS using IPv6  
> Provider Edge Routers (6PE)
> 	Author(s)	: J. De Clercq, et al.
> 	Filename	: draft-ooms-v6ops-bgp-tunnel-07.txt
> 	Pages		: 14
> 	Date		: 2006-12-12
> 	
> This document explains how to interconnect IPv6 islands over a Multi-
>    Protocol Label Switching (MPLS)-enabled IPv4 cloud.  This approach
>    relies on IPv6 Provider Edge routers (6PE) which are Dual Stack in
>    order to connect to IPv6 islands and to the MPLS core which is only
>    required to run IPv4 MPLS.  The 6PE routers exchange the IPv6
>    reachability information transparently over the core using the  
> Multi-
>    Protocol Border Gateway Protocol (MP-BGP) over IPv4.  In doing so,
>    the BGP Next Hop field is used to convey the IPv4 address of the  
> 6PE
>    router so that dynamically established IPv4-signaled MPLS Label
>    Switched Paths (LSPs) can be used without explicit tunnel
>    configuration.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ooms-v6ops-bgp-tunnel-07.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-ooms-v6ops-bgp-tunnel-07.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ooms-v6ops-bgp-tunnel-07.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2006-12-12142417.I-D@ietf.org>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr


--Apple-Mail-1-863117380
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Hello<DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Just FYI a new version of =
the 6PE I-D (draft-ooms-v6ops-bgp-tunnel) has just been =
posted.</DIV><DIV><BR class=3D"khtml-block-placeholder"></DIV><DIV>This =
version addresses the comments received during IESG Eval and IETF Last =
Call. Main changes are:</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">- added paragraph on rationale =
for 6PE approach (second paragraph of the introduction)</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- added deployment note (last paragraph of the =
introduction)</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">- adjusted some wording in =
section 2 to make it inline with latest version of RFC2858bis</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- added MUST requirement for LDP support to =
guarantee interoperability across all implementations</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- added MTU considerations (last 3 paragraphs in =
section 3)</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">- typos, references, =
...</DIV><DIV><BR><DIV>Cheers</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Francois</DIV><DIV><BR><DIV>B=
egin forwarded message:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>From: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><A =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A></FON=
T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" =
color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>Date: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica">12 December 2006 21:50:56 =
GMT+01:00</FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>To: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica"><A =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A></FONT></DI=
V><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>Cc: </B></FONT><FONT =
face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px Helvetica"><A =
href=3D"mailto:idr@ietf.org">idr@ietf.org</A></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>Subject: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><B>[Idr] I-D ACTION:draft-ooms-v6ops-bgp-tunnel-07.txt<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></B></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV> <DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A New =
Internet-Draft is available from the on-line Internet-Drafts<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">directories.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">This draft is a work item of the =
Inter-Domain Routing Working Group of the IETF.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Title<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge =
Routers (6PE)</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Author(s)<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>: J. De =
Clercq, et al.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Filename<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>: =
draft-ooms-v6ops-bgp-tunnel-07.txt</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Pages<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: 14</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Date<SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>: 2006-12-12</DIV><P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></P><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">This document =
explains how to interconnect IPv6 islands over a Multi-</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>Protocol Label Switching (MPLS)-enabled IPv4 cloud.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>This approach</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>relies on IPv6 Provider Edge routers (6PE) which are Dual Stack =
in</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>order to connect to IPv6 islands and to the MPLS core which is =
only</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>required to run IPv4 =
MPLS.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>The 6PE routers =
exchange the IPv6</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>reachability information =
transparently over the core using the Multi-</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>Protocol Border Gateway Protocol (MP-BGP) over IPv4.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>In doing so,</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>the BGP Next Hop field is used to convey the IPv4 address of the =
6PE</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>router so that dynamically =
established IPv4-signaled MPLS Label</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>Switched Paths (LSPs) can =
be used without explicit tunnel</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>configuration.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A URL =
for this Internet-Draft is:</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"http://www.ietf.org/internet-drafts/draft-ooms-v6ops-bgp-tunnel-07=
.txt">http://www.ietf.org/internet-drafts/draft-ooms-v6ops-bgp-tunnel-07.t=
xt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">To remove yourself from the I-D Announcement list, =
send a message to<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DI=
V style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.or=
g</A> with the word unsubscribe in the body of<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the =
message.<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">You can also visit <A =
href=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.=
ietf.org/mailman/listinfo/I-D-announce</A><SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to =
change your subscription settings.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts are also =
available by anonymous FTP. Login with the<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">username =
"anonymous" and a password of your e-mail address. After<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">logging =
in, type "cd internet-drafts" and then<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">"get =
draft-ooms-v6ops-bgp-tunnel-07.txt".</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">A list of Internet-Drafts =
directories can be found in</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
A><SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">or <A =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf=
/1shadow-sites.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts can also be =
obtained by e-mail.</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Send a message to:</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><A =
href=3D"mailto:mailserv@ietf.org">mailserv@ietf.org</A>.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">In the body type:</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>"FILE =
/internet-drafts/draft-ooms-v6ops-bgp-tunnel-07.txt".</DIV><P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></P><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">NOTE:<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>The mail =
server at ietf.org can return the document in</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>MIME-encoded form by using the =
"mpack" utility.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To use =
this</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>feature, insert the command =
"ENCODING mime" before the "FILE"</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>command.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To =
decode the response(s), you will need "munpack" or</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>a MIME-compliant mail =
reader.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>Different =
MIME-compliant mail readers</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>exhibit =
different behavior, especially when dealing with</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>"multipart" MIME messages (i.e. =
documents which have been split</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>up into =
multiple messages), so check your local documentation on</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>how to manipulate these =
messages.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Below is the data which will enable a MIME compliant =
mail reader</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">implementation to automatically =
retrieve the ASCII version of the</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Internet-Draft.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-Type: =
text/plain</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-ID: &lt;<A =
href=3D"mailto:2006-12-12142417.I-D@ietf.org">2006-12-12142417.I-D@ietf.or=
g</A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Idr mailing list</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:Idr@ietf.org">Idr@ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/idr">https://www1.ietf.org/=
mailman/listinfo/idr</A></DIV> =
</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>=

--Apple-Mail-1-863117380--


--===============1339077037==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1339077037==--




From idr-bounces@ietf.org Fri Dec 15 17:36:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GvLdD-0007Z0-4n; Fri, 15 Dec 2006 17:34:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GvLdC-0007Yv-47
	for idr@ietf.org; Fri, 15 Dec 2006 17:34:18 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GvLdA-0005mG-P0
	for idr@ietf.org; Fri, 15 Dec 2006 17:34:18 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 15 Dec 2006 14:34:16 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id kBFMYGbL030558; 
	Fri, 15 Dec 2006 14:34:16 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id kBFMXpAE017022;
	Fri, 15 Dec 2006 14:34:09 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 15 Dec 2006 14:33:58 -0800
Received: from [171.71.55.60] ([171.71.55.60]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 15 Dec 2006 14:33:58 -0800
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F18A20CD-BAB7-4D36-9943-B4321201C34E@cisco.com>
Content-Transfer-Encoding: 7bit
From: Tony Li <tli@cisco.com>
Subject: FW: [Idr] draft-ietf-as-pathlimit-02
Date: Fri, 15 Dec 2006 14:33:54 -0800
To: Neil Matthew <neil@abelon.com>, Joe Abley <jabley@ca.afilias.info>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 15 Dec 2006 22:33:58.0224 (UTC)
	FILETIME=[1C6B7D00:01C72099]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2817; t=1166222056;
	x=1167086056; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tli@cisco.com;
	z=From:=20Tony=20Li=20<tli@cisco.com>
	|Subject:=20FW=3A=20[Idr]=20draft-ietf-as-pathlimit-02
	|Sender:=20; bh=ILk6vS8k4jXX6bsHFXYaV/L0M7N+zQhoATiS1NSY23Y=;
	b=YPmNA8P/jfVavtg5riv1xF1xQBR/1z+VD365K2VQRNSWfMMkhEIS9XamvpWKu9S/u8gz9ZGm
	SEc0iTgdjsLUcUajBahmrm55lJMGp0xdOH3/pMTnebYKI0tct9f+Wcii;
Authentication-Results: sj-dkim-7; header.From=tli@cisco.com; dkim=pass (sig
	from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
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 all,

Sorry about the long response time.


>>> I have a couple of questions regarding this draft.
>>>
>>> 1. Section 5.1 states that the route's AS_PATHLIMIT MUST NOT be
>>> modified.  Section 5.2 talks about attaching an AS_PATHLIMIT
>>> attribute but doesn't say anything about being permitted
>>>
> to remove
>
>>> it.  Am I permitted to 'change' a received AS_PATHLIMIT by
>>> deleting and re-adding?  Some email exchanges in the
>>>
> archive would
>
>>> seem to suggest the answer to this is yes.
>>>
>
> My personal view is that it ought to be possible to remove an
> AS_PATHLIMIT attribute as part of the normal application of local
> policy within an AS, and that the draft should be modified to make
> this more clear.
>
> [If you can do it with other, similar attributes (e.g. the
> NO_ADVERTISE and NO_EXPORT community string attributes) it makes no
> sense to me to prohibit this with AS_PATHLIMIT.]
>
> It follows that removing an AS_PATHLIMIT attribute which is already
> present and then adding a replacement AS_PATHLIMIT attribute
> ought to
> be possible.


I'm fine with this approach.  Unless there are objections, I'll add  
explicit text in -03 to this effect.  If anyone care to propose text,  
please email me.


>>> 2. With respect to the use of the ATOMIC_AGGREGATE.  Maybe I'm
>>> missing something here and I think that this has already been
>>> mentioned on the list before but it appears that the specified
>>> behaviour matches the old BGP RFC and not the latest RFC?  Are
>>> folks happy with the path-limit specification adopting the old
>>> style behaviour?  Actually I'd really appreciate it if someone
>>> could explain why this is required at all! :)
>>>
>
>     BGP requires that a BGP speaker that advertises a less specific
>     prefix, but not a more specific prefix that it is using, must
>     advertise the less specific prefix with the ATOMIC_AGGREGATE
>     attribute.  BGP speakers that do not advertise a more specific
> prefix
>     based on the AS_PATHLIMIT must comply with this rule and advertise
>     the less specific prefixes 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
>     attribute on all less specific covering prefixes.
>
> I think I'd be happy with removing this paragraph altogether,
> although it's before 9am and I have not yet reached my preferred
> caffeine levels so I reserve the right to disagree with myself at
> some later date. :-)


Well, my reading of 4271 is that ATOMIC_AGGREGATE is not yet  
deprecated, and that deaggregation is still permissible if  
ATOMIC_AGGREGATE is not set.  Am I confused?

Tony

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



From idr-bounces@ietf.org Mon Dec 18 05:40:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwFse-0002Ce-SD; Mon, 18 Dec 2006 05:38:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwFsd-0002CG-5n
	for idr@ietf.org; Mon, 18 Dec 2006 05:37:59 -0500
Received: from mailout17.yourhostingaccount.com ([65.254.253.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwFsb-00080h-TA
	for idr@ietf.org; Mon, 18 Dec 2006 05:37:59 -0500
Received: from scan08.yourhostingaccount.com ([10.1.1.238]
	helo=scan08.yourhostingaccount.com)
	by mailout17.yourhostingaccount.com with esmtp (Exim)
	id 1GwFsb-00034l-IE for idr@ietf.org; Mon, 18 Dec 2006 05:37:57 -0500
Received: from authsmtp11.yourhostingaccount.com ([10.1.18.11] ident=exim)
	by scan08.yourhostingaccount.com with spamscanlookuphost (Exim)
	id 1GwFsb-0007kh-B0 for idr@ietf.org; Mon, 18 Dec 2006 05:37:57 -0500
Received: from authsmtp11.yourhostingaccount.com ([10.1.18.11]
	helo=authsmtp11.yourhostingaccount.com)
	by scan08.yourhostingaccount.com with esmtp (Exim)
	id 1GwFsa-0007kb-NZ for idr@ietf.org; Mon, 18 Dec 2006 05:37:56 -0500
Received: from 108.114.2.81.in-addr.arpa ([81.2.114.108] helo=[192.168.0.43])
	by authsmtp11.yourhostingaccount.com with esmtpa (Exim)
	id 1GwFsa-0000CN-3C; Mon, 18 Dec 2006 05:37:56 -0500
Message-ID: <45866F7E.50000@abelon.com>
Date: Mon, 18 Dec 2006 10:37:50 +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 <tli@cisco.com>
Subject: Re: FW: [Idr] draft-ietf-as-pathlimit-02
References: <F18A20CD-BAB7-4D36-9943-B4321201C34E@cisco.com>
In-Reply-To: <F18A20CD-BAB7-4D36-9943-B4321201C34E@cisco.com>
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: a8a20a483a84f747e56475e290ee868e
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

I'll see if I can think of some replacement text.

As far as the ATOMIC_AGGREGATE is concerned, regardless of the intent, 
the draft is incorrect since RFC 4271 does not state the requirement as 
currently worded.  If this is a requirement for this draft then I guess 
the wording should be along the lines of "Section 5.1.6 of [RFC 4271] is 
replaced with the following text".  Except the "following text" will 
basically be a cut and paste of RFC 1771.  I wasn't working on BGP back 
then but I guess the text was altered for a reason?

Also, is the intent that this is really a 'MUST'?  I ask because RFC 
1771 uses a lower case 'shall'.  Is the use of this attribute more of a 
safeguard than anything else and if so then could we use MAY?

Cheers


Neil

Tony Li wrote:

>>>>
>
> Hi all,
>
> Sorry about the long response time.
>
>
>>>> I have a couple of questions regarding this draft.
>>>>
>>>> 1. Section 5.1 states that the route's AS_PATHLIMIT MUST NOT be
>>>> modified.  Section 5.2 talks about attaching an AS_PATHLIMIT
>>>> attribute but doesn't say anything about being permitted
>>>>
>> to remove
>>
>>>> it.  Am I permitted to 'change' a received AS_PATHLIMIT by
>>>> deleting and re-adding?  Some email exchanges in the
>>>>
>> archive would
>>
>>>> seem to suggest the answer to this is yes.
>>>>
>>
>> My personal view is that it ought to be possible to remove an
>> AS_PATHLIMIT attribute as part of the normal application of local
>> policy within an AS, and that the draft should be modified to make
>> this more clear.
>>
>> [If you can do it with other, similar attributes (e.g. the
>> NO_ADVERTISE and NO_EXPORT community string attributes) it makes no
>> sense to me to prohibit this with AS_PATHLIMIT.]
>>
>> It follows that removing an AS_PATHLIMIT attribute which is already
>> present and then adding a replacement AS_PATHLIMIT attribute
>> ought to
>> be possible.
>
>
>
> I'm fine with this approach.  Unless there are objections, I'll add  
> explicit text in -03 to this effect.  If anyone care to propose text,  
> please email me.
>
>
>>>> 2. With respect to the use of the ATOMIC_AGGREGATE.  Maybe I'm
>>>> missing something here and I think that this has already been
>>>> mentioned on the list before but it appears that the specified
>>>> behaviour matches the old BGP RFC and not the latest RFC?  Are
>>>> folks happy with the path-limit specification adopting the old
>>>> style behaviour?  Actually I'd really appreciate it if someone
>>>> could explain why this is required at all! :)
>>>>
>>
>>     BGP requires that a BGP speaker that advertises a less specific
>>     prefix, but not a more specific prefix that it is using, must
>>     advertise the less specific prefix with the ATOMIC_AGGREGATE
>>     attribute.  BGP speakers that do not advertise a more specific
>> prefix
>>     based on the AS_PATHLIMIT must comply with this rule and advertise
>>     the less specific prefixes 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
>>     attribute on all less specific covering prefixes.
>>
>> I think I'd be happy with removing this paragraph altogether,
>> although it's before 9am and I have not yet reached my preferred
>> caffeine levels so I reserve the right to disagree with myself at
>> some later date. :-)
>
>
>
> Well, my reading of 4271 is that ATOMIC_AGGREGATE is not yet  
> deprecated, and that deaggregation is still permissible if  
> ATOMIC_AGGREGATE is not set.  Am I confused?
>
> Tony
>


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



From idr-bounces@ietf.org Mon Dec 18 12:20:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwM9L-00089q-I8; Mon, 18 Dec 2006 12:19:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwM9K-00083U-9I
	for idr@ietf.org; Mon, 18 Dec 2006 12:19:38 -0500
Received: from sccrmhc14.comcast.net ([63.240.77.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwM4f-0004Wx-Pz
	for idr@ietf.org; Mon, 18 Dec 2006 12:14:51 -0500
Received: from [192.168.0.101]
	(c-24-6-155-154.hsd1.ca.comcast.net[24.6.155.154])
	by comcast.net (sccrmhc14) with SMTP
	id <2006121817144301400434e9e>; Mon, 18 Dec 2006 17:14:49 +0000
In-Reply-To: <45866F7E.50000@abelon.com>
References: <F18A20CD-BAB7-4D36-9943-B4321201C34E@cisco.com>
	<45866F7E.50000@abelon.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <27404B08-CC60-4BEE-B0A3-221375A8D499@tony.li>
Content-Transfer-Encoding: 7bit
From: Tony Li <tony.li@tony.li>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02
Date: Mon, 18 Dec 2006 09:14:47 -0800
To: Neil Matthew <neil@abelon.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
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


Neil,

On Dec 18, 2006, at 2:37 AM, Neil Matthew wrote:

> I'll see if I can think of some replacement text.


Thanks.


> As far as the ATOMIC_AGGREGATE is concerned, regardless of the  
> intent, the draft is incorrect since RFC 4271 does not state the  
> requirement as currently worded.  If this is a requirement for this  
> draft then I guess the wording should be along the lines of  
> "Section 5.1.6 of [RFC 4271] is replaced with the following text".   
> Except the "following text" will basically be a cut and paste of  
> RFC 1771.  I wasn't working on BGP back then but I guess the text  
> was altered for a reason?


Maybe I'm missing something.  I'm not trying to change overall  
behavior with AS_PATHLIMIT.  Where do you see the inconsistency?  The  
point of that paragraph was to remind folks that are dropping paths  
due to AS_PATHLIMIT that they need to be careful.


> Also, is the intent that this is really a 'MUST'?  I ask because  
> RFC 1771 uses a lower case 'shall'.  Is the use of this attribute  
> more of a safeguard than anything else and if so then could we use  
> MAY?


At least as of 1771, using ATOMIC_AGGREGATE was intended to be a  
strict requirement.  I don't think that case has ever been the sole  
indication that something was strictly required or not.  Case was  
added just to highlight the requirements.  1777 certainly uses  
'shall' liberally and the intent was that it was semantically  
equivalent to 'must'.

AFAIK, ATOMIC_AGGREGATE is still a hard requirement.  If an aggregate  
with a truncated AS path is subsequently deaggregated, then it  
generates a longer prefix.  If one of those truncated prefixes is  
distributed back across the AS path of the aggregate, in the portion  
that was truncated, then it could easily be selected and you have a  
static forwarding loop.

The only difference is that 4271 has explicitly called out the  
requirement that the AS path be truncated before there's an issue.   
This is a good clarification.  I can certainly add that, if that  
would be help.

Tony


>
> Cheers
>
>
> Neil
>
> Tony Li wrote:
>
>>>>>
>>
>> Hi all,
>>
>> Sorry about the long response time.
>>
>>
>>>>> I have a couple of questions regarding this draft.
>>>>>
>>>>> 1. Section 5.1 states that the route's AS_PATHLIMIT MUST NOT be
>>>>> modified.  Section 5.2 talks about attaching an AS_PATHLIMIT
>>>>> attribute but doesn't say anything about being permitted
>>>>>
>>> to remove
>>>
>>>>> it.  Am I permitted to 'change' a received AS_PATHLIMIT by
>>>>> deleting and re-adding?  Some email exchanges in the
>>>>>
>>> archive would
>>>
>>>>> seem to suggest the answer to this is yes.
>>>>>
>>>
>>> My personal view is that it ought to be possible to remove an
>>> AS_PATHLIMIT attribute as part of the normal application of local
>>> policy within an AS, and that the draft should be modified to make
>>> this more clear.
>>>
>>> [If you can do it with other, similar attributes (e.g. the
>>> NO_ADVERTISE and NO_EXPORT community string attributes) it makes no
>>> sense to me to prohibit this with AS_PATHLIMIT.]
>>>
>>> It follows that removing an AS_PATHLIMIT attribute which is already
>>> present and then adding a replacement AS_PATHLIMIT attribute
>>> ought to
>>> be possible.
>>
>>
>>
>> I'm fine with this approach.  Unless there are objections, I'll  
>> add  explicit text in -03 to this effect.  If anyone care to  
>> propose text,  please email me.
>>
>>
>>>>> 2. With respect to the use of the ATOMIC_AGGREGATE.  Maybe I'm
>>>>> missing something here and I think that this has already been
>>>>> mentioned on the list before but it appears that the specified
>>>>> behaviour matches the old BGP RFC and not the latest RFC?  Are
>>>>> folks happy with the path-limit specification adopting the old
>>>>> style behaviour?  Actually I'd really appreciate it if someone
>>>>> could explain why this is required at all! :)
>>>>>
>>>
>>>     BGP requires that a BGP speaker that advertises a less specific
>>>     prefix, but not a more specific prefix that it is using, must
>>>     advertise the less specific prefix with the ATOMIC_AGGREGATE
>>>     attribute.  BGP speakers that do not advertise a more specific
>>> prefix
>>>     based on the AS_PATHLIMIT must comply with this rule and  
>>> advertise
>>>     the less specific prefixes 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
>>>     attribute on all less specific covering prefixes.
>>>
>>> I think I'd be happy with removing this paragraph altogether,
>>> although it's before 9am and I have not yet reached my preferred
>>> caffeine levels so I reserve the right to disagree with myself at
>>> some later date. :-)
>>
>>
>>
>> Well, my reading of 4271 is that ATOMIC_AGGREGATE is not yet   
>> deprecated, and that deaggregation is still permissible if   
>> ATOMIC_AGGREGATE is not set.  Am I confused?
>>
>> Tony
>>
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr


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



From idr-bounces@ietf.org Mon Dec 18 14:14:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwNuw-0005bL-Fc; Mon, 18 Dec 2006 14:12:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwNut-0005a7-MU
	for idr@ietf.org; Mon, 18 Dec 2006 14:12:51 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GwNun-0005O9-DI for idr@ietf.org; Mon, 18 Dec 2006 14:12:51 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 18 Dec 2006 11:12:44 -0800
X-IronPort-AV: i="4.12,185,1165219200"; 
	d="scan'208"; a="451894824:sNHT196779512"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id kBIJChfR017087; 
	Mon, 18 Dec 2006 11:12:43 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id kBIJCWjc012141;
	Mon, 18 Dec 2006 11:12:41 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Dec 2006 11:12:37 -0800
Received: from [171.70.225.251] ([171.70.225.251]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Dec 2006 11:12:37 -0800
In-Reply-To: <45866F7E.50000@abelon.com>
References: <F18A20CD-BAB7-4D36-9943-B4321201C34E@cisco.com>
	<45866F7E.50000@abelon.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <34FA9413-F72D-4C57-8DE8-4F74B5AD3180@cisco.com>
Content-Transfer-Encoding: 7bit
From: Tony Li <tli@cisco.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02
Date: Mon, 18 Dec 2006 11:12:31 -0800
To: Neil Matthew <neil@abelon.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 18 Dec 2006 19:12:37.0601 (UTC)
	FILETIME=[7B0BF510:01C722D8]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5205; t=1166469163;
	x=1167333163; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tli@cisco.com;
	z=From:=20Tony=20Li=20<tli@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20draft-ietf-as-pathlimit-02
	|Sender:=20; bh=ta7SteRwaZNbWEoQCF1okRlK8uM5GzfpfTYaQAAyZl0=;
	b=a0xbSmCV7dx5vxOFyoOVCnYUFGrUw6wSaIP9gLZB4d1HrAir9OpuWBtRl8TtMUoeEIpzXSYN
	vL58x5bje58bWZPc4xBOhEz90RMPPkGHRrq9YtAZjIsWSJ34OZIDlLD9;
Authentication-Results: sj-dkim-3; header.From=tli@cisco.com; dkim=pass (sig
	from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
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


Neil,

On Dec 18, 2006, at 2:37 AM, Neil Matthew wrote:

> I'll see if I can think of some replacement text.


Thanks.


> As far as the ATOMIC_AGGREGATE is concerned, regardless of the  
> intent, the draft is incorrect since RFC 4271 does not state the  
> requirement as currently worded.  If this is a requirement for this  
> draft then I guess the wording should be along the lines of  
> "Section 5.1.6 of [RFC 4271] is replaced with the following text".   
> Except the "following text" will basically be a cut and paste of  
> RFC 1771.  I wasn't working on BGP back then but I guess the text  
> was altered for a reason?


Maybe I'm missing something.  I'm not trying to change overall  
behavior with AS_PATHLIMIT.  Where do you see the inconsistency?  The  
point of my paragraph was to remind folks that are dropping paths due  
to AS_PATHLIMIT that they need to be careful.


> Also, is the intent that this is really a 'MUST'?  I ask because  
> RFC 1771 uses a lower case 'shall'.  Is the use of this attribute  
> more of a safeguard than anything else and if so then could we use  
> MAY?


At least as of 1771, using ATOMIC_AGGREGATE was intended to be a  
strict requirement.  I don't think that case has ever been the sole  
indication that something was strictly required or not.  Case was  
added just to highlight the requirements.  1777 certainly uses  
'shall' liberally and the intent was that it was semantically  
equivalent to 'must'.

AFAIK, ATOMIC_AGGREGATE is still a hard requirement.  If an aggregate  
with a truncated AS path is subsequently deaggregated, then it  
generates a longer prefix.  If one of those truncated prefixes is  
distributed back across the AS path of the aggregate, in the portion  
that was truncated, then it could easily be selected and you have a  
static forwarding loop.

The only difference is that 4271 has explicitly called out the  
requirement that the AS path be truncated

Tony


>
> Cheers
>
>
> Neil
>
> Tony Li wrote:
>
>>>>>
>>
>> Hi all,
>>
>> Sorry about the long response time.
>>
>>
>>>>> I have a couple of questions regarding this draft.
>>>>>
>>>>> 1. Section 5.1 states that the route's AS_PATHLIMIT MUST NOT be
>>>>> modified.  Section 5.2 talks about attaching an AS_PATHLIMIT
>>>>> attribute but doesn't say anything about being permitted
>>>>>
>>> to remove
>>>
>>>>> it.  Am I permitted to 'change' a received AS_PATHLIMIT by
>>>>> deleting and re-adding?  Some email exchanges in the
>>>>>
>>> archive would
>>>
>>>>> seem to suggest the answer to this is yes.
>>>>>
>>>
>>> My personal view is that it ought to be possible to remove an
>>> AS_PATHLIMIT attribute as part of the normal application of local
>>> policy within an AS, and that the draft should be modified to make
>>> this more clear.
>>>
>>> [If you can do it with other, similar attributes (e.g. the
>>> NO_ADVERTISE and NO_EXPORT community string attributes) it makes no
>>> sense to me to prohibit this with AS_PATHLIMIT.]
>>>
>>> It follows that removing an AS_PATHLIMIT attribute which is already
>>> present and then adding a replacement AS_PATHLIMIT attribute
>>> ought to
>>> be possible.
>>
>>
>>
>> I'm fine with this approach.  Unless there are objections, I'll  
>> add  explicit text in -03 to this effect.  If anyone care to  
>> propose text,  please email me.
>>
>>
>>>>> 2. With respect to the use of the ATOMIC_AGGREGATE.  Maybe I'm
>>>>> missing something here and I think that this has already been
>>>>> mentioned on the list before but it appears that the specified
>>>>> behaviour matches the old BGP RFC and not the latest RFC?  Are
>>>>> folks happy with the path-limit specification adopting the old
>>>>> style behaviour?  Actually I'd really appreciate it if someone
>>>>> could explain why this is required at all! :)
>>>>>
>>>
>>>     BGP requires that a BGP speaker that advertises a less specific
>>>     prefix, but not a more specific prefix that it is using, must
>>>     advertise the less specific prefix with the ATOMIC_AGGREGATE
>>>     attribute.  BGP speakers that do not advertise a more specific
>>> prefix
>>>     based on the AS_PATHLIMIT must comply with this rule and  
>>> advertise
>>>     the less specific prefixes 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
>>>     attribute on all less specific covering prefixes.
>>>
>>> I think I'd be happy with removing this paragraph altogether,
>>> although it's before 9am and I have not yet reached my preferred
>>> caffeine levels so I reserve the right to disagree with myself at
>>> some later date. :-)
>>
>>
>>
>> Well, my reading of 4271 is that ATOMIC_AGGREGATE is not yet   
>> deprecated, and that deaggregation is still permissible if   
>> ATOMIC_AGGREGATE is not set.  Am I confused?
>>
>> Tony
>>
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr

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



From idr-bounces@ietf.org Tue Dec 19 04:18:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gwb68-0007vb-8i; Tue, 19 Dec 2006 04:17:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwb66-0007tO-Tx
	for idr@ietf.org; Tue, 19 Dec 2006 04:17:18 -0500
Received: from mail18.yourhostingaccount.com ([65.254.253.235])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gwb65-0001vM-Gi
	for idr@ietf.org; Tue, 19 Dec 2006 04:17:18 -0500
Received: from scan01.yourhostingaccount.com ([10.1.1.231]
	helo=scan01.yourhostingaccount.com)
	by mail18.yourhostingaccount.com with esmtp (Exim)
	id 1Gwb64-0008Dx-Rl for idr@ietf.org; Tue, 19 Dec 2006 04:17:17 -0500
Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8] ident=exim)
	by scan01.yourhostingaccount.com with spamscanlookuphost (Exim)
	id 1Gwb64-0007OX-KH for idr@ietf.org; Tue, 19 Dec 2006 04:17:16 -0500
Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8]
	helo=authsmtp08.yourhostingaccount.com)
	by scan01.yourhostingaccount.com with esmtp (Exim)
	id 1Gwb63-0007OS-OW for idr@ietf.org; Tue, 19 Dec 2006 04:17:15 -0500
Received: from 108.114.2.81.in-addr.arpa ([81.2.114.108] helo=[192.168.0.43])
	by authsmtp08.yourhostingaccount.com with esmtpa (Exim)
	id 1Gwb63-0002B3-7A; Tue, 19 Dec 2006 04:17:15 -0500
Message-ID: <4587AE12.3050902@abelon.com>
Date: Tue, 19 Dec 2006 09:17:06 +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>
In-Reply-To: <27404B08-CC60-4BEE-B0A3-221375A8D499@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: 16c9da4896bf5539ae3547c6c25f06a0
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

OK, can we agree that the text in section 5.1.6 ATOMIC_AGGREGATE as it 
appears in RFC 4271 is different to the text found in the same section 
of RFC 1771?  Further can we agree that section 5.1 of the AS_PATHLIMIT 
draft refers to the earlier text?  From section 5.1 of the AS_PATHLIMIT 
draft:

   "BGP requires that a BGP speaker that advertises a less specific
   prefix, but not a more specific prefix that it is using, must
   advertise the less specific prefix with the ATOMIC_AGGREGATE
   attribute. "


This is not what appears in section 5.1.6 of the latest BGP draft but 
words to this effect do appear in RFC 1771.  This is a tad confusing.

In the latest BGP RFC the focus is on the node performing the 
aggregation - this is a controlled point with configured aggregation 
policy.  This is referred to in the AS_PATHLIMIT draft in the following 
text (the end of the last paragraph of section 5.1):

   To help ensure compliance with this, sites that choose to advertise the
   AS_PATHLIMIT path attribute should advertise the ATOMIC_AGGREGATE
   attribute on all less specific covering prefixes.


Cool.  What concerns me is the bit that comes before:

   BGP speakers that do not advertise a more specific prefix
   based on the AS_PATHLIMIT must comply with this rule and advertise
   the less specific prefixes with the ATOMIC_AGGREGATE attribute.

This seems to reference the earlier BGP RFC.  So the idea is that if the 
originating node 'forgot' to attach the ATOMIC AGGREGATE then it is a 
'must' requirement that some later node 'fix' up the situation?  I am 
concerned this is a non-trivial and processor intensive requirement 
hence my labouring of the point!  I'd just like clarification.


Cheers


Neil

Tony Li wrote:

>
> Neil,
>
> On Dec 18, 2006, at 2:37 AM, Neil Matthew wrote:
>
>> I'll see if I can think of some replacement text.
>
>
>
> Thanks.
>
>
>> As far as the ATOMIC_AGGREGATE is concerned, regardless of the  
>> intent, the draft is incorrect since RFC 4271 does not state the  
>> requirement as currently worded.  If this is a requirement for this  
>> draft then I guess the wording should be along the lines of  "Section 
>> 5.1.6 of [RFC 4271] is replaced with the following text".   Except 
>> the "following text" will basically be a cut and paste of  RFC 1771.  
>> I wasn't working on BGP back then but I guess the text  was altered 
>> for a reason?
>
>
>
> Maybe I'm missing something.  I'm not trying to change overall  
> behavior with AS_PATHLIMIT.  Where do you see the inconsistency?  The  
> point of that paragraph was to remind folks that are dropping paths  
> due to AS_PATHLIMIT that they need to be careful.
>
>
>> Also, is the intent that this is really a 'MUST'?  I ask because  RFC 
>> 1771 uses a lower case 'shall'.  Is the use of this attribute  more 
>> of a safeguard than anything else and if so then could we use  MAY?
>
>
>
> At least as of 1771, using ATOMIC_AGGREGATE was intended to be a  
> strict requirement.  I don't think that case has ever been the sole  
> indication that something was strictly required or not.  Case was  
> added just to highlight the requirements.  1777 certainly uses  
> 'shall' liberally and the intent was that it was semantically  
> equivalent to 'must'.
>
> AFAIK, ATOMIC_AGGREGATE is still a hard requirement.  If an aggregate  
> with a truncated AS path is subsequently deaggregated, then it  
> generates a longer prefix.  If one of those truncated prefixes is  
> distributed back across the AS path of the aggregate, in the portion  
> that was truncated, then it could easily be selected and you have a  
> static forwarding loop.
>
> The only difference is that 4271 has explicitly called out the  
> requirement that the AS path be truncated before there's an issue.   
> This is a good clarification.  I can certainly add that, if that  
> would be help.
>
> Tony
>
>
>>
>> Cheers
>>
>>
>> Neil
>>
>> Tony Li wrote:
>>
>>>>>>
>>>
>>> Hi all,
>>>
>>> Sorry about the long response time.
>>>
>>>
>>>>>> I have a couple of questions regarding this draft.
>>>>>>
>>>>>> 1. Section 5.1 states that the route's AS_PATHLIMIT MUST NOT be
>>>>>> modified.  Section 5.2 talks about attaching an AS_PATHLIMIT
>>>>>> attribute but doesn't say anything about being permitted
>>>>>>
>>>> to remove
>>>>
>>>>>> it.  Am I permitted to 'change' a received AS_PATHLIMIT by
>>>>>> deleting and re-adding?  Some email exchanges in the
>>>>>>
>>>> archive would
>>>>
>>>>>> seem to suggest the answer to this is yes.
>>>>>>
>>>>
>>>> My personal view is that it ought to be possible to remove an
>>>> AS_PATHLIMIT attribute as part of the normal application of local
>>>> policy within an AS, and that the draft should be modified to make
>>>> this more clear.
>>>>
>>>> [If you can do it with other, similar attributes (e.g. the
>>>> NO_ADVERTISE and NO_EXPORT community string attributes) it makes no
>>>> sense to me to prohibit this with AS_PATHLIMIT.]
>>>>
>>>> It follows that removing an AS_PATHLIMIT attribute which is already
>>>> present and then adding a replacement AS_PATHLIMIT attribute
>>>> ought to
>>>> be possible.
>>>
>>>
>>>
>>>
>>> I'm fine with this approach.  Unless there are objections, I'll  
>>> add  explicit text in -03 to this effect.  If anyone care to  
>>> propose text,  please email me.
>>>
>>>
>>>>>> 2. With respect to the use of the ATOMIC_AGGREGATE.  Maybe I'm
>>>>>> missing something here and I think that this has already been
>>>>>> mentioned on the list before but it appears that the specified
>>>>>> behaviour matches the old BGP RFC and not the latest RFC?  Are
>>>>>> folks happy with the path-limit specification adopting the old
>>>>>> style behaviour?  Actually I'd really appreciate it if someone
>>>>>> could explain why this is required at all! :)
>>>>>>
>>>>
>>>>     BGP requires that a BGP speaker that advertises a less specific
>>>>     prefix, but not a more specific prefix that it is using, must
>>>>     advertise the less specific prefix with the ATOMIC_AGGREGATE
>>>>     attribute.  BGP speakers that do not advertise a more specific
>>>> prefix
>>>>     based on the AS_PATHLIMIT must comply with this rule and  
>>>> advertise
>>>>     the less specific prefixes 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
>>>>     attribute on all less specific covering prefixes.
>>>>
>>>> I think I'd be happy with removing this paragraph altogether,
>>>> although it's before 9am and I have not yet reached my preferred
>>>> caffeine levels so I reserve the right to disagree with myself at
>>>> some later date. :-)
>>>
>>>
>>>
>>>
>>> Well, my reading of 4271 is that ATOMIC_AGGREGATE is not yet   
>>> deprecated, and that deaggregation is still permissible if   
>>> ATOMIC_AGGREGATE is not set.  Am I confused?
>>>
>>> Tony
>>>
>>
>>
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www1.ietf.org/mailman/listinfo/idr
>
>
>


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



From idr-bounces@ietf.org Tue Dec 19 12:00:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwiIB-0000Ed-Ay; Tue, 19 Dec 2006 11:58:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwiIA-0000EY-8u
	for idr@ietf.org; Tue, 19 Dec 2006 11:58:14 -0500
Received: from sccrmhc12.comcast.net ([204.127.200.82])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwiI9-0006uQ-12
	for idr@ietf.org; Tue, 19 Dec 2006 11:58:14 -0500
Received: from [192.168.0.101]
	(c-24-6-155-154.hsd1.ca.comcast.net[24.6.155.154])
	by comcast.net (sccrmhc12) with SMTP
	id <20061219165806012004j2jne>; Tue, 19 Dec 2006 16:58:12 +0000
In-Reply-To: <4587AE12.3050902@abelon.com>
References: <F18A20CD-BAB7-4D36-9943-B4321201C34E@cisco.com>
	<45866F7E.50000@abelon.com>
	<27404B08-CC60-4BEE-B0A3-221375A8D499@tony.li>
	<4587AE12.3050902@abelon.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <759E57E8-B549-47BE-984F-630F30F3E203@tony.li>
Content-Transfer-Encoding: 7bit
From: Tony Li <tony.li@tony.li>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02
Date: Tue, 19 Dec 2006 08:58:00 -0800
To: Neil Matthew <neil@abelon.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
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


Neil,


> OK, can we agree that the text in section 5.1.6 ATOMIC_AGGREGATE as  
> it appears in RFC 4271 is different to the text found in the same  
> section of RFC 1771?


Of course.


> Further can we agree that section 5.1 of the AS_PATHLIMIT draft  
> refers to the earlier text?


Well, it wasn't meant to.  It was meant to be consistent with both  
1771 and 4271, but wasn't meant to refer specifically to either.


> From section 5.1 of the AS_PATHLIMIT draft:
>
>   "BGP requires that a BGP speaker that advertises a less specific
>   prefix, but not a more specific prefix that it is using, must
>   advertise the less specific prefix with the ATOMIC_AGGREGATE
>   attribute. "
>
> This is not what appears in section 5.1.6 of the latest BGP draft  
> but words to this effect do appear in RFC 1771.  This is a tad  
> confusing.


Sorry.


> In the latest BGP RFC the focus is on the node performing the  
> aggregation - this is a controlled point with configured  
> aggregation policy.  This is referred to in the AS_PATHLIMIT draft  
> in the following text (the end of the last paragraph of section 5.1):
>
>   To help ensure compliance with this, sites that choose to  
> advertise the
>   AS_PATHLIMIT path attribute should advertise the ATOMIC_AGGREGATE
>   attribute on all less specific covering prefixes.
>
> Cool.  What concerns me is the bit that comes before:
>
>   BGP speakers that do not advertise a more specific prefix
>   based on the AS_PATHLIMIT must comply with this rule and advertise
>   the less specific prefixes with the ATOMIC_AGGREGATE attribute.
>
> This seems to reference the earlier BGP RFC.  So the idea is that  
> if the originating node 'forgot' to attach the ATOMIC AGGREGATE  
> then it is a 'must' requirement that some later node 'fix' up the  
> situation?  I am concerned this is a non-trivial and processor  
> intensive requirement hence my labouring of the point!  I'd just  
> like clarification.


Got it, thanks for clarifying your concern.

 From my reading of 4271, I'm not sure that you can transfer all  
responsibility to the node that originated the aggregate.  Recall  
Postel's robustness principle: "Be conservative in what you do; be  
liberal in what you accept from others."

This implies that a node other than the originating node that saw  
both the aggregate and the more specific should, in being liberal,  
accept both regardless of ATOMIC_AGGREGATE.  Since that same node can  
(albeit painfully) detect that it has an aggregate without  
ATOMIC_AGGREGATE, it has a responsibility, in being conservative, to  
rectify the situation or at least not propagate the error.

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?

Ob. overhead: I currently have a draft out to my co-editors.   
Assuming that you agree to this and my co-editors have no objections,  
this can get rolled into -03.

Tony


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



From idr-bounces@ietf.org Tue Dec 19 12:54:58 2006
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



From idr-bounces@ietf.org Wed Dec 20 04:03:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwxKg-00062R-BW; Wed, 20 Dec 2006 04:01:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwxKe-00061a-NL
	for idr@ietf.org; Wed, 20 Dec 2006 04:01:48 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwxKb-0006T9-M6
	for idr@ietf.org; Wed, 20 Dec 2006 04:01:48 -0500
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 20 Dec 2006 10:01:42 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kBK91flH016919
	for <idr@ietf.org>; Wed, 20 Dec 2006 10:01:41 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kBK91atD019345
	for <idr@ietf.org>; Wed, 20 Dec 2006 10:01:41 +0100 (MET)
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Dec 2006 10:01:36 +0100
Received: from [10.0.0.9] ([10.61.81.38]) by xfe-ams-332.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Dec 2006 10:01:34 +0100
Mime-Version: 1.0 (Apple Message framework v752.3)
To: idr@ietf.org
Message-Id: <F9B66484-06D3-496C-B397-3D92B7893987@cisco.com>
References: <E1GwluU-0007cg-1s@stiedprstage1.ietf.org>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Wed, 20 Dec 2006 09:59:56 +0100
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 20 Dec 2006 09:01:34.0863 (UTC)
	FILETIME=[732D99F0:01C72415]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=23223; t=1166605301;
	x=1167469301; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20Fwd=3A=20I-D=20ACTION=3Adraft-lefaucheur-idr-v4nlri-v6nh-01.t
	xt=20 |Sender:=20;
	bh=pdml76HGBjUzpUaeyrfnT88lblYteemPz/Pms9PSmH8=;
	b=aj47JW8vRkUykS2EUpxRCizhw0RjF+sCufMpCOWv6VNzxKbJBndccak+BPTjjKdL0kxe2ibL
	/RdR9p26BoaEDAUcFwBR8LwofN1mAHzkxd0yoNReWLqckG6BfuzXYLez;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9178bae9f85419fdc08e9f2c86e345d0
Subject: [Idr] Fwd: I-D ACTION:draft-lefaucheur-idr-v4nlri-v6nh-01.txt 
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>
Content-Type: multipart/mixed; boundary="===============1867153370=="
Errors-To: idr-bounces@ietf.org


--===============1867153370==
Content-Type: multipart/alternative; boundary=Apple-Mail-6--680564532


--Apple-Mail-6--680564532
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hello,

As promised, here is the updated version that we'd like to be  
accepted as Working Group document.

It addresses comments received on the list as well as off-lists  
comments. The main changes are:
	- clarifications that the extension is not to be used where existing  
solutions exist (such as 6PE, 6VPE, 2547bis)
	- clarification that the extension is not expected to be used with  
new AFI/SAFIs, whose definition can include multiple next hop formats  
from the onset
	- discussed relationship bw AFI/SAFI values between included in the  
new Capability vs AFI/SAFI value included in existing MP_BGP cap
	- statement about possible use of Dynamic Capability with the new  
Capability

Cheers

Francois

Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: 19 December 2006 21:50:02 GMT+01:00
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-lefaucheur-idr-v4nlri-v6nh-01.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title		: Advertising an IPv4 NLRI with an IPv6 Next Hop
> 	Author(s)	: F. Le Faucheur, E. Rosen
> 	Filename	: draft-lefaucheur-idr-v4nlri-v6nh-01.txt
> 	Pages		: 12
> 	Date		: 2006-12-19
> 	
> MultiProtocol-BGP (MP-BGP) specifies that the set of Network Layer
>    protocols to which the address carried in the Next Hop field may
>    belong is determined by the Address Family Identifier (AFI) and the
>    Subsequent Address Family Identifier (SAFI).  The current AFI/SAFI
>    definitions for the IPv4 address family only have provisions for
>    advertising a Next Hop address that belongs to the IPv4 protocol  
> when
>    advertising an IPv4 Network Layer Reachability Information  
> (NLRI) or
>    a VPN-IPv4 NLRI.  This document specifies the extensions  
> necessary to
>    allow advertising an IPv4 NLRI or a VPN-IPv4 NLRI with a Next Hop
>    address that belongs to the IPv6 protocol.  This comprises an
>    extension of the AFI/SAFI definitions to allow the address of the
>    Next Hop for an IPv4 NLRI or VPN-IPv4 NLRI to also belong to the  
> IPv6
>    protocol, the encoding of the Next Hop in order to determine  
> which of
>    the protocols the address actually belongs to, and a new BGP
>    Capability allowing MP-BGP Peers to dynamically discover whether  
> they
>    can exchange IPv4 NLRI and VPN-IPv4 NLRI with an IPv6 Next Hop.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-lefaucheur-idr-v4nlri- 
> v6nh-01.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> "get draft-lefaucheur-idr-v4nlri-v6nh-01.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-lefaucheur-idr-v4nlri-v6nh-01.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2006-12-19131309.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce


--Apple-Mail-6--680564532
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; "><DIV>Hello,</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>As promised, here is the =
updated version that we'd like to be accepted as Working Group =
document.</DIV><DIV><BR class=3D"khtml-block-placeholder"></DIV><DIV>It =
addresses comments received on the list as well as off-lists comments. =
The main changes are:</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>- =
clarifications that the extension is not to be used where existing =
solutions exist (such as 6PE, 6VPE, 2547bis)</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>- clarification that the =
extension is not expected to be used with new AFI/SAFIs, whose =
definition can include multiple next hop formats from the =
onset</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>- discussed relationship bw =
AFI/SAFI values between included in the new Capability vs AFI/SAFI value =
included in existing MP_BGP cap</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>- =
statement about possible use of Dynamic Capability with the new =
Capability</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Cheers</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Francois</DIV><DIV><BR><DIV>B=
egin forwarded message:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>From: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><A =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A></FON=
T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" =
color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>Date: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica">19 December 2006 21:50:02 =
GMT+01:00</FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><B>To: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica"><A =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A></FONT></DI=
V><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>Subject: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><B>I-D ACTION:draft-lefaucheur-idr-v4nlri-v6nh-01.txt<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></B></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><B>Reply-To: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><A =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</A></FON=
T></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; min-height: 14px; "><BR></DIV> <DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">A New Internet-Draft is available from the on-line =
Internet-Drafts<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">directories.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Title<SPAN class=3D"Apple-tab-span"=
 style=3D"white-space:pre">	</SPAN><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>: Advertising an IPv4 NLRI with =
an IPv6 Next Hop</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Author(s)<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>: F. Le =
Faucheur, E. Rosen</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>Filename<SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>: draft-lefaucheur-idr-v4nlri-v6nh-01.txt</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>Pages<SPAN class=3D"Apple-tab-span"=
 style=3D"white-space:pre">	</SPAN><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>: 12</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>Date<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>: =
2006-12-19</DIV><P style=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: =
14.0px"><SPAN class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN><BR class=3D"khtml-block-placeholder"></P><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">MultiProtocol-BGP (MP-BGP) specifies that the set of Network =
Layer</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>protocols to which the =
address carried in the Next Hop field may</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>belong is determined by =
the Address Family Identifier (AFI) and the</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>Subsequent Address Family =
Identifier (SAFI).<SPAN class=3D"Apple-converted-space">=A0 </SPAN>The =
current AFI/SAFI</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>definitions for the IPv4 =
address family only have provisions for</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>advertising a Next Hop =
address that belongs to the IPv4 protocol when</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>advertising an IPv4 Network Layer Reachability Information (NLRI) =
or</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>a VPN-IPv4 NLRI.<SPAN class=3D"Apple-converted-space">=A0 =
</SPAN>This document specifies the extensions necessary to</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0=A0 =
</SPAN>allow advertising an IPv4 NLRI or a VPN-IPv4 NLRI with a Next =
Hop</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>address that belongs to =
the IPv6 protocol.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>This =
comprises an</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>extension of the AFI/SAFI =
definitions to allow the address of the</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>Next Hop for an IPv4 NLRI =
or VPN-IPv4 NLRI to also belong to the IPv6</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>protocol, the encoding of =
the Next Hop in order to determine which of</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>the protocols the address =
actually belongs to, and a new BGP</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>Capability allowing MP-BGP =
Peers to dynamically discover whether they</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0=A0 </SPAN>can exchange IPv4 NLRI and =
VPN-IPv4 NLRI with an IPv6 Next Hop.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">A URL for this Internet-Draft =
is:</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"http://www.ietf.org/internet-drafts/draft-lefaucheur-idr-v4nlri-v6=
nh-01.txt">http://www.ietf.org/internet-drafts/draft-lefaucheur-idr-v4nlri=
-v6nh-01.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">To remove yourself from the I-D Announcement list, =
send a message to<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DI=
V style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.or=
g</A> with the word unsubscribe in the body of<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the =
message.<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">You can also visit <A =
href=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.=
ietf.org/mailman/listinfo/I-D-announce</A><SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to =
change your subscription settings.</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts are also =
available by anonymous FTP. Login with the<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">username =
"anonymous" and a password of your e-mail address. After<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">logging =
in, type "cd internet-drafts" and then<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">"get =
draft-lefaucheur-idr-v4nlri-v6nh-01.txt".</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A list of =
Internet-Drafts directories can be found in</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
A><SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">or <A =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf=
/1shadow-sites.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts can also be =
obtained by e-mail.</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Send a message to:</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN><A =
href=3D"mailto:mailserv@ietf.org">mailserv@ietf.org</A>.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">In the body type:</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>"FILE =
/internet-drafts/draft-lefaucheur-idr-v4nlri-v6nh-01.txt".</DIV><P =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px; min-height: 14.0px"><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN><BR =
class=3D"khtml-block-placeholder"></P><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">NOTE:<SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>The mail =
server at ietf.org can return the document in</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>MIME-encoded form by using the =
"mpack" utility.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To use =
this</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>feature, insert the command =
"ENCODING mime" before the "FILE"</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>command.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>To =
decode the response(s), you will need "munpack" or</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>a MIME-compliant mail =
reader.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>Different =
MIME-compliant mail readers</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>exhibit =
different behavior, especially when dealing with</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>"multipart" MIME messages (i.e. =
documents which have been split</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</SPAN>up into =
multiple messages), so check your local documentation on</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>how to manipulate these =
messages.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Below is the data which will enable a MIME compliant =
mail reader</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">implementation to automatically =
retrieve the ASCII version of the</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Internet-Draft.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-Type: =
text/plain</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-ID: &lt;<A =
href=3D"mailto:2006-12-19131309.I-D@ietf.org">2006-12-19131309.I-D@ietf.or=
g</A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">I-D-Announce mailing list</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/i-d-announce">https://www1.=
ietf.org/mailman/listinfo/i-d-announce</A></DIV> =
</BLOCKQUOTE></DIV><BR></BODY></HTML>=

--Apple-Mail-6--680564532--


--===============1867153370==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1867153370==--




From idr-bounces@ietf.org Wed Dec 20 07:45:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx0n2-00025O-U8; Wed, 20 Dec 2006 07:43:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx0n1-00023j-Jf
	for idr@ietf.org; Wed, 20 Dec 2006 07:43:19 -0500
Received: from astro.systems.pipex.net ([62.241.163.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx0mz-0006Bm-4g
	for idr@ietf.org; Wed, 20 Dec 2006 07:43:19 -0500
Received: from pc6 (1Cust57.tnt104.lnd4.gbr.da.uu.net [213.116.56.57])
	by astro.systems.pipex.net (Postfix) with SMTP id 338AEE0000BF;
	Wed, 20 Dec 2006 12:43:10 +0000 (GMT)
Message-ID: <00f601c7242b$fb539120$0601a8c0@pc6>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "Tony Li" <tony.li@tony.li>,
	"Neil Matthew" <neil@abelon.com>
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>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02
Date: Wed, 20 Dec 2006 12:07:48 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
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

Sorry to be late for this particular party but I think the text still misses the
point; see below.

Tom Petch


----- Original Message -----
From: "Tony Li" <tony.li@tony.li>
To: "Neil Matthew" <neil@abelon.com>
Cc: <idr@ietf.org>
Sent: Tuesday, December 19, 2006 5:58 PM
Subject: Re: [Idr] draft-ietf-as-pathlimit-02


>
> Neil,
>
> > OK, can we agree that the text in section 5.1.6 ATOMIC_AGGREGATE as
> > it appears in RFC 4271 is different to the text found in the same
> > section of RFC 1771?
>
> Of course.
>
> > Further can we agree that section 5.1 of the AS_PATHLIMIT draft
> > refers to the earlier text?
>
> Well, it wasn't meant to.  It was meant to be consistent with both
> 1771 and 4271, but wasn't meant to refer specifically to either.
>
> > From section 5.1 of the AS_PATHLIMIT draft:
> >
> >   "BGP requires that a BGP speaker that advertises a less specific
> >   prefix, but not a more specific prefix that it is using, must
> >   advertise the less specific prefix with the ATOMIC_AGGREGATE
> >   attribute. "
> >
> > This is not what appears in section 5.1.6 of the latest BGP draft
> > but words to this effect do appear in RFC 1771.  This is a tad
> > confusing.
>
> Sorry.
>
> > In the latest BGP RFC the focus is on the node performing the
> > aggregation - this is a controlled point with configured
> > aggregation policy.  This is referred to in the AS_PATHLIMIT draft
> > in the following text (the end of the last paragraph of section 5.1):
> >
> >   To help ensure compliance with this, sites that choose to
> > advertise the
> >   AS_PATHLIMIT path attribute should advertise the ATOMIC_AGGREGATE
> >   attribute on all less specific covering prefixes.
> >
> > Cool.  What concerns me is the bit that comes before:
> >
> >   BGP speakers that do not advertise a more specific prefix
> >   based on the AS_PATHLIMIT must comply with this rule and advertise
> >   the less specific prefixes with the ATOMIC_AGGREGATE attribute.
> >
> > This seems to reference the earlier BGP RFC.  So the idea is that
> > if the originating node 'forgot' to attach the ATOMIC AGGREGATE
> > then it is a 'must' requirement that some later node 'fix' up the
> > situation?  I am concerned this is a non-trivial and processor
> > intensive requirement hence my labouring of the point!  I'd just
> > like clarification.
>
> Got it, thanks for clarifying your concern.
>
>  From my reading of 4271, I'm not sure that you can transfer all
> responsibility to the node that originated the aggregate.  Recall
> Postel's robustness principle: "Be conservative in what you do; be
> liberal in what you accept from others."
>
> This implies that a node other than the originating node that saw
> both the aggregate and the more specific should, in being liberal,
> accept both regardless of ATOMIC_AGGREGATE.  Since that same node can
> (albeit painfully) detect that it has an aggregate without
> ATOMIC_AGGREGATE, it has a responsibility, in being conservative, to
> rectify the situation or at least not propagate the error.
>
> 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?

No!  RFC4271 does NOT talk about truncated AS paths, it says
"  If an aggregate excludes at least some of the AS numbers present in
   the AS_PATH of the routes that are aggregated as a result of dropping
   the AS_SET ..."

that is, it is not specific to truncation, it is whenever as AS number is
omitted and the thrust of RFC4271 is that may occur due to an AS_SET being
omitted.

Your text is about truncation only and that I think is wrong.

So I think you need text along the lines of

To ensure loop prevention, BGP recommends {SHOULD not MUST} that when an
aggregated route does not include all the AS numbers that were present in the
more specific routes, then the ATOMIC_AGGREGATE attribute SHOULD be present.

Tom Petch

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


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



From idr-bounces@ietf.org Wed Dec 20 16:19:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx8pA-0002gf-UC; Wed, 20 Dec 2006 16:18:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx8pA-0002ga-9J
	for idr@ietf.org; Wed, 20 Dec 2006 16:18:04 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx8p8-0007GV-Ps
	for idr@ietf.org; Wed, 20 Dec 2006 16:18:04 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 20 Dec 2006 13:18:02 -0800
X-IronPort-AV: i="4.12,193,1165219200"; 
	d="scan'208"; a="93440147:sNHT214128846"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id kBKLI2HU030148; 
	Wed, 20 Dec 2006 13:18:02 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kBKLHfZs011344;
	Wed, 20 Dec 2006 13:18:00 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Dec 2006 13:17:53 -0800
Received: from [171.71.55.60] ([171.71.55.60]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Dec 2006 13:17:53 -0800
In-Reply-To: <00f601c7242b$fb539120$0601a8c0@pc6>
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>
	<00f601c7242b$fb539120$0601a8c0@pc6>
Mime-Version: 1.0 (Apple Message framework v752.3)
X-Priority: 3
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <710D2BA6-41A9-4638-8B1B-0FEC406522B0@cisco.com>
Content-Transfer-Encoding: 7bit
From: Tony Li <tli@cisco.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02
Date: Wed, 20 Dec 2006 13:17:45 -0800
To: "tom.petch" <cfinss@dial.pipex.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 20 Dec 2006 21:17:53.0425 (UTC)
	FILETIME=[4FA73010:01C7247C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2122; t=1166649482;
	x=1167513482; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tli@cisco.com;
	z=From:=20Tony=20Li=20<tli@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20draft-ietf-as-pathlimit-02
	|Sender:=20; bh=fYfU+R4OQehUG0bCKFQAwfEzrgpmSoylhHpIVkiwYo0=;
	b=br/I2Zfqq4p5l3QeOTBJiqQI5VnhDL423q4CeYrnZJG+W7EmMH99wb//A67fYNqiuWGEA1EG
	culNEl8r7oM/OeCT6jIXRxrw3B//+QjgqE5i9sZ3GtbPeOFUtuuTdBG5;
Authentication-Results: sj-dkim-4; header.From=tli@cisco.com; dkim=pass (sig
	from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
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



Tom,

> Sorry to be late for this particular party but I think the text  
> still misses the
> point; see below.


Welcome to the party.  Better late than never.  Don't worry, the  
food's not gone...  ;-)


>> 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?
>
> No!  RFC4271 does NOT talk about truncated AS paths, it says
> "  If an aggregate excludes at least some of the AS numbers present in
>    the AS_PATH of the routes that are aggregated as a result of  
> dropping
>    the AS_SET ..."


So, dropping an AS_SET is one mechanism for truncating the AS_PATH,  
yes?  It's certainly the most likely one to happen at aggregation  
time, but you can imagine that there might be a host of other  
(possibly future) mechanisms that truncate the AS path.


> that is, it is not specific to truncation, it is whenever as AS  
> number is
> omitted and the thrust of RFC4271 is that may occur due to an  
> AS_SET being
> omitted.
>
> Your text is about truncation only and that I think is wrong.


I'm trying to think more generally than what 4271 says.  The problem  
that ATOMIC_AGGREGATE 'fixes' is a combination of truncation of the  
AS_PATH in conjunction with deaggregation.


> So I think you need text along the lines of
>
> To ensure loop prevention, BGP recommends {SHOULD not MUST} that  
> when an
> aggregated route does not include all the AS numbers that were  
> present in the
> more specific routes, then the ATOMIC_AGGREGATE attribute SHOULD be  
> present.


By the rules on aggregation, shouldn't the only way that AS number  
might not be present in the aggregate's AS path be due to dropping  
the AS_SET?  In other words, isn't your text semantically identical  
to what I proposed?

Tony



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



From idr-bounces@ietf.org Fri Dec 22 08:08:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxk5q-0008UN-DL; Fri, 22 Dec 2006 08:05:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxk5o-0008UF-Mi
	for idr@ietf.org; Fri, 22 Dec 2006 08:05:44 -0500
Received: from ranger.systems.pipex.net ([62.241.162.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxk5n-0003NO-AC
	for idr@ietf.org; Fri, 22 Dec 2006 08:05:44 -0500
Received: from pc6 (1Cust85.tnt106.lnd4.gbr.da.uu.net [213.116.60.85])
	by ranger.systems.pipex.net (Postfix) with SMTP id A671DE00022A;
	Fri, 22 Dec 2006 13:05:38 +0000 (GMT)
Message-ID: <01e701c725c1$71b74320$0601a8c0@pc6>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "Tony Li" <tli@cisco.com>
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>
	<00f601c7242b$fb539120$0601a8c0@pc6>
	<710D2BA6-41A9-4638-8B1B-0FEC406522B0@cisco.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02
Date: Fri, 22 Dec 2006 12:52:00 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
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

No:-( see inline

Tom Petch

----- Original Message -----
From: "Tony Li" <tli@cisco.com>
To: "tom.petch" <cfinss@dial.pipex.com>
Cc: "Neil Matthew" <neil@abelon.com>; <idr@ietf.org>
Sent: Wednesday, December 20, 2006 10:17 PM
Subject: Re: [Idr] draft-ietf-as-pathlimit-02


> Tom,
>
> > Sorry to be late for this particular party but I think the text
> > still misses the
> > point; see below.
>
> Welcome to the party.  Better late than never.  Don't worry, the
> food's not gone...  ;-)
>
> >> 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?
> >
> > No!  RFC4271 does NOT talk about truncated AS paths, it says
> > "  If an aggregate excludes at least some of the AS numbers present in
> >    the AS_PATH of the routes that are aggregated as a result of
> > dropping
> >    the AS_SET ..."
>
> So, dropping an AS_SET is one mechanism for truncating the AS_PATH,
> yes?  It's certainly the most likely one to happen at aggregation
> time, but you can imagine that there might be a host of other
> (possibly future) mechanisms that truncate the AS path.
>
>
> > that is, it is not specific to truncation, it is whenever as AS
> > number is
> > omitted and the thrust of RFC4271 is that may occur due to an
> > AS_SET being
> > omitted.
> >
> > Your text is about truncation only and that I think is wrong.
>
> I'm trying to think more generally than what 4271 says.  The problem
> that ATOMIC_AGGREGATE 'fixes' is a combination of truncation of the
> AS_PATH in conjunction with deaggregation.
>
> > So I think you need text along the lines of
> >
> > To ensure loop prevention, BGP recommends {SHOULD not MUST} that
> > when an
> > aggregated route does not include all the AS numbers that were
> > present in the
> > more specific routes, then the ATOMIC_AGGREGATE attribute SHOULD be
> > present.
>
> By the rules on aggregation, shouldn't the only way that AS number
> might not be present in the aggregate's AS path be due to dropping
> the AS_SET?  In other words, isn't your text semantically identical
> to what I proposed?
>

I think not.  Truncation in my vocabulary is about lopping off the end so
1, 3, (345, 324, 319), 2, 29, 416
might be truncated to
1, 3, (345, 324, 319), 2
but changing it to
1, 3, 345, 2, 29, 416
does not come within the semantics of truncation.

So I agree that we should allow for more cases than RFC4271 does but see
truncation as the wrong word.  Omit, remove, excise, drop, exclude ... lots of
alternatives but not truncation.

> Tony
>
>


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



From idr-bounces@ietf.org Fri Dec 22 11:15:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxn2U-0006jt-9U; Fri, 22 Dec 2006 11:14:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxn2T-0006jo-NE
	for idr@ietf.org; Fri, 22 Dec 2006 11:14:29 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxn2S-0002Aj-Dt
	for idr@ietf.org; Fri, 22 Dec 2006 11:14:29 -0500
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-6.cisco.com with ESMTP; 22 Dec 2006 08:14:27 -0800
X-IronPort-AV: i="4.12,205,1165219200"; 
	d="scan'208"; a="94213777:sNHT89661258"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id kBMGERLv009479; 
	Fri, 22 Dec 2006 08:14:27 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id kBMGEMUH018126;
	Fri, 22 Dec 2006 08:14:23 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 08:14:22 -0800
Received: from [192.168.0.101] ([10.21.147.56]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 08:14:21 -0800
In-Reply-To: <01e701c725c1$71b74320$0601a8c0@pc6>
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>
	<00f601c7242b$fb539120$0601a8c0@pc6>
	<710D2BA6-41A9-4638-8B1B-0FEC406522B0@cisco.com>
	<01e701c725c1$71b74320$0601a8c0@pc6>
Mime-Version: 1.0 (Apple Message framework v752.3)
X-Priority: 3
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9DEAC602-A41A-4227-8EDD-EEB25CB3D257@cisco.com>
Content-Transfer-Encoding: 7bit
From: Tony Li <tli@cisco.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02
Date: Fri, 22 Dec 2006 08:14:21 -0800
To: "tom.petch" <cfinss@dial.pipex.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 22 Dec 2006 16:14:21.0891 (UTC)
	FILETIME=[3D8F2130:01C725E4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=760; t=1166804067;
	x=1167668067; c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tli@cisco.com;
	z=From:=20Tony=20Li=20<tli@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20draft-ietf-as-pathlimit-02
	|Sender:=20; bh=utGXeRBRkV47oW8d40eacuSFyBJqB3F6padTulO6nUA=;
	b=IscwSRaT3zhkBQZTb/lIf5MEZhXQVJCapETno0F7niGPYeuSv9mCRvwZWWPCpoKIZqvdBwzW
	9a+feV0fFkocJF1sN4GX+Tbc+h5opo9Jq8jMTdE/T+qdYwr+B2A+9TDv;
Authentication-Results: sj-dkim-5; header.From=tli@cisco.com; dkim=pass (sig
	from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
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

Tom,

> I think not.  Truncation in my vocabulary is about lopping off the  
> end so
> 1, 3, (345, 324, 319), 2, 29, 416
> might be truncated to
> 1, 3, (345, 324, 319), 2
> but changing it to
> 1, 3, 345, 2, 29, 416
> does not come within the semantics of truncation.


Ok, I don't want to quibble here.  Revised text:

	To ensure loop prevention, BGP requires that all aggregate routes
	with AS paths that omit any AS number from the AS_PATHs being
         aggregated 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?

Tony



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



From idr-bounces@ietf.org Fri Dec 22 11:15:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxn1m-0006ak-SB; Fri, 22 Dec 2006 11:13:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxn1l-0006ad-4m
	for idr@ietf.org; Fri, 22 Dec 2006 11:13:45 -0500
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxn1k-00024c-FL
	for idr@ietf.org; Fri, 22 Dec 2006 11:13:45 -0500
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	kBMGCXMQ040043; Fri, 22 Dec 2006 11:12:33 -0500 (EST)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200612221612.kBMGCXMQ040043@workhorse.brookfield.occnc.com>
To: "tom.petch" <cfinss@dial.pipex.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02 
In-reply-to: Your message of "Fri, 22 Dec 2006 12:52:00 +0100."
	<01e701c725c1$71b74320$0601a8c0@pc6> 
Date: Fri, 22 Dec 2006 11:12:33 -0500
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: Tony Li <tli@cisco.com>, idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
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


In message <01e701c725c1$71b74320$0601a8c0@pc6>
"tom.petch" writes:
>  
> No:-( see inline
>  
> Tom Petch


Let me just check on my understanding of ATOMIC_AGGREGATE, legal AS
Path changes, and de-aggregation.  See below.


> ----- Original Message -----
> From: "Tony Li" <tli@cisco.com>
> To: "tom.petch" <cfinss@dial.pipex.com>
> Cc: "Neil Matthew" <neil@abelon.com>; <idr@ietf.org>
> Sent: Wednesday, December 20, 2006 10:17 PM
> Subject: Re: [Idr] draft-ietf-as-pathlimit-02
>  
>  
> > Tom,
> >
> > > Sorry to be late for this particular party but I think the text
> > > still misses the
> > > point; see below.
> >
> > Welcome to the party.  Better late than never.  Don't worry, the
> > food's not gone...  ;-)
> >
> > >> 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?
> > >
> > > No!  RFC4271 does NOT talk about truncated AS paths, it says
> > > "  If an aggregate excludes at least some of the AS numbers present in
> > >    the AS_PATH of the routes that are aggregated as a result of
> > > dropping
> > >    the AS_SET ..."
> >
> > So, dropping an AS_SET is one mechanism for truncating the AS_PATH,
> > yes?  It's certainly the most likely one to happen at aggregation
> > time, but you can imagine that there might be a host of other
> > (possibly future) mechanisms that truncate the AS path.
> >
> >
> > > that is, it is not specific to truncation, it is whenever as AS
> > > number is
> > > omitted and the thrust of RFC4271 is that may occur due to an
> > > AS_SET being
> > > omitted.
> > >
> > > Your text is about truncation only and that I think is wrong.
> >
> > I'm trying to think more generally than what 4271 says.  The problem
> > that ATOMIC_AGGREGATE 'fixes' is a combination of truncation of the
> > AS_PATH in conjunction with deaggregation.
> >
> > > So I think you need text along the lines of
> > >
> > > To ensure loop prevention, BGP recommends {SHOULD not MUST} that
> > > when an
> > > aggregated route does not include all the AS numbers that were
> > > present in the
> > > more specific routes, then the ATOMIC_AGGREGATE attribute SHOULD be
> > > present.
> >
> > By the rules on aggregation, shouldn't the only way that AS number
> > might not be present in the aggregate's AS path be due to dropping
> > the AS_SET?  In other words, isn't your text semantically identical
> > to what I proposed?
> >
>  
> I think not.  Truncation in my vocabulary is about lopping off the end so
> 1, 3, (345, 324, 319), 2, 29, 416
> might be truncated to
> 1, 3, (345, 324, 319), 2
> but changing it to
> 1, 3, 345, 2, 29, 416
> does not come within the semantics of truncation.
>  
> So I agree that we should allow for more cases than RFC4271 does but see
> truncation as the wrong word.  Omit, remove, excise, drop, exclude ... lots of
> alternatives but not truncation.



Please excuse me for also joining late and maybe not paying enough
attention to this thread up to now.

My read of RFC4271 concludes:

  1.  De-aggregation MUST NOT be done under any circumstance.

     In 9.1.4:

       With the elimination of IP routing protocols that do not
       support classless routing, and the elimination of router and
       host implementations that do not support classless routing,
       there is no longer a need to de-aggregate.  Routes SHOULD NOT
       be de-aggregated.  In particular, a route that carries the
       ATOMIC_AGGREGATE attribute MUST NOT be de-aggregated.

     Since there hasn't been a classfull host or router sighted in
     nearly 10 years (I had a Cisco IGS in my basement but that got
     recybcled :), this is effectively a MUST NOT.

  2.  The only time it is legal to truncate an AS path is when forming
      an ATOMIC_AGGREGATE.  RFC4271 is not clear about what changes to
      the AS_PATH is legal at this point, just that things can be
      omitted.

  3.  The common procedure for truncating the AS path when forming an
      ATOMIC_AGGREGATE is to drop the whole thing and advertise it out
      with only the AS of the aggregator in the AS Path.

  4.  The only other legal changes to the AS_PATH (besides prepending
      your own AS) are information reduction, forming AS_SET as
      described in 9.2.2.1 and aggregation as described in 9.2.2.2.

Also important but not in RFC4271 (me thinks):

  5.  In practice, forming an ATOMIC_AGGREGATE from a set of routes
      which include one or more that is as specific as the aggregate
      has proven to be potentially harmful.  Maybe this should have
      been noted in RFC4271 but it is not (unless I missed it).

Since the common practice is "drop the whole AS_PATH", leaving some
information on the AS_PATH when forming an ATOMIC_AGGREGATE should be
fine.  I think you'll have the same potential looping problems with or
without AS_PATHLIMIT if you ignore item #5 above.

Now back to the subject line (which is wrong, the draft name is
draft-ietf-idr-as-pathlimit-02.txt, note that the idr is missing).

The draft specifies limiting the scope of the more specific routes.
(Seems like a good idea.  Why all the fuss? :)

In this draft, Section "5.1.  Operations" warns to add
ATOMIC_AGGREGATE when forming an aggregate containing AS_PATHLIMIT.

If an aggregate is formed, limiting the more specific has no adverse
effect in terms of reachability as long as the more specific can reach
the aggregator.

If no aggregate is formed, which might be the case for anycast, then
the scope of the anycast address is limited, which besides information
reduction is the purpse of doing as-pathlimit for anycast.

If an aggregator drops the AS_PATH or any part of it, adds
ATOMIC_AGGREGATE, but does not form a less specific prefix, then a
loop is possible, but that was always the case with or without
AS_PATHLIMIT.

Whether to do creative AS_PATH manipulations and which ones are legal
and/or safe is not directly relevant to the draft (unless as is
sometimes the case and could be again, I'm missing something due to
skimming a long thread without reading every word).  It seems to me
that creative uses of AS_PATHLIMIT and ATOMIC_AGGREGATE and AS_PATH
changes beyond what is described in the draft is interesting but
should be out of scope and better saved for a new "creative uses"
draft to follow if we want to pursue it further.

So should we move forward with this draft, or did I miss something?

Curtis

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



From idr-bounces@ietf.org Fri Dec 22 12:43:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxoOq-0001Oj-GE; Fri, 22 Dec 2006 12:41:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxoOp-0001Mt-EC
	for idr@ietf.org; Fri, 22 Dec 2006 12:41:39 -0500
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxoOo-0007U0-2y
	for idr@ietf.org; Fri, 22 Dec 2006 12:41:39 -0500
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	kBMHeGVn041507; Fri, 22 Dec 2006 12:40:16 -0500 (EST)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200612221740.kBMHeGVn041507@workhorse.brookfield.occnc.com>
To: Tony Li <tli@cisco.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02 
In-reply-to: Your message of "Fri, 22 Dec 2006 08:14:21 PST."
	<9DEAC602-A41A-4227-8EDD-EEB25CB3D257@cisco.com> 
Date: Fri, 22 Dec 2006 12:40:15 -0500
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
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


In message <9DEAC602-A41A-4227-8EDD-EEB25CB3D257@cisco.com>
Tony Li writes:
>  
> Tom,
>  
> > I think not.  Truncation in my vocabulary is about lopping off the  
> > end so
> > 1, 3, (345, 324, 319), 2, 29, 416
> > might be truncated to
> > 1, 3, (345, 324, 319), 2
> > but changing it to
> > 1, 3, 345, 2, 29, 416
> > does not come within the semantics of truncation.
>  
>  
> Ok, I don't want to quibble here.  Revised text:
>  
> 	To ensure loop prevention, BGP requires that all aggregate routes
> 	with AS paths that omit any AS number from the AS_PATHs being
>          aggregated 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?
>  
> Tony


   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.


Add to that "without changing the AS_PATH when adding
ATOMIC_AGGREGATE.  Just truncating and advertising the same prefix
adding ATOMIC_AGGREGATE is already known to cause loops.

Curtis

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



From idr-bounces@ietf.org Sat Dec 23 07:30:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gy5yi-0002rv-Vp; Sat, 23 Dec 2006 07:27:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gy5yh-0002rO-BK
	for idr@ietf.org; Sat, 23 Dec 2006 07:27:51 -0500
Received: from blaster.systems.pipex.net ([62.241.163.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gy5yf-0007zX-Sn
	for idr@ietf.org; Sat, 23 Dec 2006 07:27:51 -0500
Received: from pc6 (1Cust100.tnt102.lnd4.gbr.da.uu.net [213.116.52.100])
	by blaster.systems.pipex.net (Postfix) with SMTP id 79FE5E0002C7;
	Sat, 23 Dec 2006 12:27:44 +0000 (GMT)
Message-ID: <002701c72685$4f424f00$0601a8c0@pc6>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "Tony Li" <tli@cisco.com>
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>
	<00f601c7242b$fb539120$0601a8c0@pc6>
	<710D2BA6-41A9-4638-8B1B-0FEC406522B0@cisco.com>
	<01e701c725c1$71b74320$0601a8c0@pc6>
	<9DEAC602-A41A-4227-8EDD-EEB25CB3D257@cisco.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02
Date: Sat, 23 Dec 2006 12:14:11 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
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

----- Original Message ----- 
From: "Tony Li" <tli@cisco.com>
To: "tom.petch" <cfinss@dial.pipex.com>
Cc: "Neil Matthew" <neil@abelon.com>; <idr@ietf.org>
Sent: Friday, December 22, 2006 5:14 PM
Subject: Re: [Idr] draft-ietf-as-pathlimit-02


> Tom,
> 
> > I think not.  Truncation in my vocabulary is about lopping off the  
> > end so
> > 1, 3, (345, 324, 319), 2, 29, 416
> > might be truncated to
> > 1, 3, (345, 324, 319), 2
> > but changing it to
> > 1, 3, 345, 2, 29, 416
> > does not come within the semantics of truncation.
> 
> 
> Ok, I don't want to quibble here.  Revised text:
> 
> To ensure loop prevention, BGP requires that all aggregate routes
> with AS paths that omit any AS number from the AS_PATHs being
>          aggregated 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, that works for me (but I am still digesting Curtis's message)

Tom Petch
> Tony
> 
> 

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



From idr-bounces@ietf.org Sat Dec 23 10:58:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gy9Eb-0006Id-Jv; Sat, 23 Dec 2006 10:56:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gy9EZ-0006IX-UH
	for idr@ietf.org; Sat, 23 Dec 2006 10:56:27 -0500
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gy9EY-0008Lp-H3
	for idr@ietf.org; Sat, 23 Dec 2006 10:56:27 -0500
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	kBNFrJqU051413; Sat, 23 Dec 2006 10:53:19 -0500 (EST)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200612231553.kBNFrJqU051413@workhorse.brookfield.occnc.com>
To: "tom.petch" <cfinss@dial.pipex.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02 
In-reply-to: Your message of "Sat, 23 Dec 2006 12:14:11 +0100."
	<002701c72685$4f424f00$0601a8c0@pc6> 
Date: Sat, 23 Dec 2006 10:53:19 -0500
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Tony Li <tli@cisco.com>, idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
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


In message <002701c72685$4f424f00$0601a8c0@pc6>
"tom.petch" writes:
>  
> > Tom,
> > 
> > > I think not.  Truncation in my vocabulary is about lopping off the  
> > > end so
> > > 1, 3, (345, 324, 319), 2, 29, 416
> > > might be truncated to
> > > 1, 3, (345, 324, 319), 2
> > > but changing it to
> > > 1, 3, 345, 2, 29, 416
> > > does not come within the semantics of truncation.
> > 
> > 
> > Ok, I don't want to quibble here.  Revised text:
> > 
> > To ensure loop prevention, BGP requires that all aggregate routes
> > with AS paths that omit any AS number from the AS_PATHs being
> >          aggregated 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, that works for me (but I am still digesting Curtis's message)
>  
> Tom Petch
> > Tony


Tony, Tom,

I think we are all in agreement here with the addition of the caveat
that you can't safely stuff a ATOMIC_AGGREGATE on a prefix and drop
part of the AS_PATH.  If routes with AS_PATHLIMIT are originated with
both AS_PATHLIMIT and ATOMIC_AGGREGATE then any aggregate formed has
to have ATOMIC_AGGREGATE.  

If routes with AS_PATHLIMIT are originated with ATOMIC_AGGREGATE then
no AS is lost from the path unless someone uses this prefix to form
another ATOMIC_AGGREGATE aggregate with the same prefix length and
drops all or part of the AS_PATH in doing so.  That we could agree is
a problem but out of scope for this document since it relates to the
general harmfulness of this sort of "aggregation".

Curtis

ps - If you keep adding capabilities such as this to BGP you'll
someday catch up to the functionality defined for the IRR in the RPS
WG about 10 years ago, and largely implemented (the aggregation limits
were defined but not implemented though, but they were more functional
indicating which set of AS a prefix should be limited to, not just
distance).  The difference was that it is here a local matter and
carried by protocol bits (bloating the advertisements) and there (IRR)
it was for the world to see in the registry (allowing others to
identify problems) and enforced by machine generated configuration.
To each his own preference.  Keep up the good work.  :-)

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



From idr-bounces@ietf.org Sat Dec 23 12:53:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyB2K-0001yF-0J; Sat, 23 Dec 2006 12:51:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyB2I-0001n8-BJ
	for idr@ietf.org; Sat, 23 Dec 2006 12:51:54 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyB2G-0004YR-2B
	for idr@ietf.org; Sat, 23 Dec 2006 12:51:54 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 23 Dec 2006 12:51:51 -0500
X-IronPort-AV: i="4.12,208,1165208400"; 
	d="scan'208"; a="110191523:sNHT46527916"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id kBNHppY1003689; 
	Sat, 23 Dec 2006 12:51:51 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kBNHppgT016359; 
	Sat, 23 Dec 2006 12:51:51 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 12:51:51 -0500
Received: from [192.168.0.101] ([10.82.208.6]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 12:51:50 -0500
In-Reply-To: <200612231553.kBNFrJqU051413@workhorse.brookfield.occnc.com>
References: <200612231553.kBNFrJqU051413@workhorse.brookfield.occnc.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0B252636-ED28-4197-B58F-89A0F1EF91F6@cisco.com>
Content-Transfer-Encoding: 7bit
From: Tony Li <tli@cisco.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02 
Date: Sat, 23 Dec 2006 09:51:50 -0800
To: curtis@occnc.com
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 23 Dec 2006 17:51:50.0745 (UTC)
	FILETIME=[06292C90:01C726BB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1520; t=1166896311;
	x=1167760311; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tli@cisco.com;
	z=From:=20Tony=20Li=20<tli@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20draft-ietf-as-pathlimit-02=20
	|Sender:=20 |To:=20curtis@occnc.com;
	bh=n9/587xyfiVy9J2HPNgE5Ys8RYdWyp4D7ktaJ9docYc=;
	b=nxOEUsE5T6139HCUw5HJP2LBrI13oxRGfHwP8yqQ5fUzblAPjeczCQfOCpeqbXZdLolxme+y
	/5YKpZWcYo/rqGUedCJOhamneJ2E2RY2OEj78/AaWJWTxCi9aiOv/3AM;
Authentication-Results: rtp-dkim-1; header.From=tli@cisco.com; dkim=pass (si
	g from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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


Curtis,

>>> To ensure loop prevention, BGP requires that all aggregate routes
>>> with AS paths that omit any AS number from the AS_PATHs being
>>>          aggregated 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.


So are you on-board with this text or not?


> ps - If you keep adding capabilities such as this to BGP you'll
> someday catch up to the functionality defined for the IRR in the RPS
> WG about 10 years ago, and largely implemented (the aggregation limits
> were defined but not implemented though, but they were more functional
> indicating which set of AS a prefix should be limited to, not just
> distance).  The difference was that it is here a local matter and
> carried by protocol bits (bloating the advertisements) and there (IRR)
> it was for the world to see in the registry (allowing others to
> identify problems) and enforced by machine generated configuration.
> To each his own preference.  Keep up the good work.  :-)


As I believe the text of the draft says itself, I was very hopeful  
that this functionality would not be necessary as a general sense of  
cleanliness.  I was wrong.  Having the functionality implement in the  
IRR clearly hasn't sufficed either.  As a practical matter, I'm  
simply trying to find something that works.

Regards,
Tony

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



From idr-bounces@ietf.org Sat Dec 23 14:30:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyCWZ-0005QQ-DJ; Sat, 23 Dec 2006 14:27:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyCWX-0005Pl-C6
	for idr@ietf.org; Sat, 23 Dec 2006 14:27:13 -0500
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyCWW-0004bL-0B
	for idr@ietf.org; Sat, 23 Dec 2006 14:27:13 -0500
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	kBNJPjxT053660; Sat, 23 Dec 2006 14:25:45 -0500 (EST)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200612231925.kBNJPjxT053660@workhorse.brookfield.occnc.com>
To: Tony Li <tli@cisco.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02 
In-reply-to: Your message of "Sat, 23 Dec 2006 09:51:50 PST."
	<0B252636-ED28-4197-B58F-89A0F1EF91F6@cisco.com> 
Date: Sat, 23 Dec 2006 14:25:45 -0500
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
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


In message <0B252636-ED28-4197-B58F-89A0F1EF91F6@cisco.com>
Tony Li writes:
>  
>  
> Curtis,
>  
> >>> To ensure loop prevention, BGP requires that all aggregate routes
> >>> with AS paths that omit any AS number from the AS_PATHs being
> >>>          aggregated 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.
>  
>  
> So are you on-board with this text or not?


Not quite strong enough.  IMHO.

You should put ATOMIC_AGGREGATE on any prefix that has AS_PATHLIMIT so
that any downstream aggregator is forced to form an aggregate with
ATOMIC_AGGREGATE by virtue of the rule in BGP that if a component of
the aggregate has ATOMIC_AGGREGATE then any less specific aggregate
formed using it must have ATOMIC_AGGREGATE.

I suppose the reason for using SHOULD is that eventually aggregators
that don't understand AS_PATHLIMIT should go away and with it the need
for these extra ATOMIC_AGGREGATE.

We're being a bit pedantic about this whole topic if we look at this
from a practical standpoint since a long time ago we concluded that
providers were all using ATOMIC_AGGREGATE and tossing the entire
AS_PATH when forming an aggregate.  Since ATOMIC_AGGREGATE is
informational in the absense of de-aggregation this is not terribly
important.

The only thing that people were doing that was potentially dangerous
was combining a /x and /y where x<y and forming a new /x and tossing
the AS_PATH and adding ATOMIC_AGGREGATE.  That was safe in some
topologies but generally a vary bad practice.

Do you agree with that?

Curtis

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



From idr-bounces@ietf.org Sat Dec 23 15:15:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyDH0-0006yo-Tz; Sat, 23 Dec 2006 15:15:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyDGy-0006ya-KO
	for idr@ietf.org; Sat, 23 Dec 2006 15:15:12 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyDGx-0004go-CN
	for idr@ietf.org; Sat, 23 Dec 2006 15:15:12 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 23 Dec 2006 12:15:11 -0800
X-IronPort-AV: i="4.12,208,1165219200"; 
	d="scan'208"; a="49313621:sNHT45307496"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kBNKFBUl030034; 
	Sat, 23 Dec 2006 15:15:11 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kBNKFAgT010765; 
	Sat, 23 Dec 2006 15:15:10 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 15:15:10 -0500
Received: from [192.168.0.101] ([10.82.208.6]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 23 Dec 2006 15:15:09 -0500
In-Reply-To: <200612231925.kBNJPjxT053660@workhorse.brookfield.occnc.com>
References: <200612231925.kBNJPjxT053660@workhorse.brookfield.occnc.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7A0A7AE9-FC3A-401C-ADA3-8A565288F3E9@cisco.com>
Content-Transfer-Encoding: 7bit
From: Tony Li <tli@cisco.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02 
Date: Sat, 23 Dec 2006 12:15:10 -0800
To: curtis@occnc.com
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 23 Dec 2006 20:15:09.0919 (UTC)
	FILETIME=[0BAAFEF0:01C726CF]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1644; t=1166904911;
	x=1167768911; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tli@cisco.com;
	z=From:=20Tony=20Li=20<tli@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20draft-ietf-as-pathlimit-02=20
	|Sender:=20 |To:=20curtis@occnc.com;
	bh=dsvlAeanzFzO4PvXhXXNImariev6O0aisR0yrxvFDhs=;
	b=gdxTSDCke/t1KNGeSkCyPBaGKuI9OssH/u/NwN8sFqFbSvJzMCaJTpEpYMfUaMqhuvuKlE/B
	4SsRB86CvGknch+Mxj5Kjklm00FeKkdqSzx49wAQcimXj8ekw0hRsN4h;
Authentication-Results: rtp-dkim-2; header.From=tli@cisco.com; dkim=pass (si
	g from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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



> Not quite strong enough.  IMHO.
>
> You should put ATOMIC_AGGREGATE on any prefix that has AS_PATHLIMIT so
> that any downstream aggregator is forced to form an aggregate with
> ATOMIC_AGGREGATE by virtue of the rule in BGP that if a component of
> the aggregate has ATOMIC_AGGREGATE then any less specific aggregate
> formed using it must have ATOMIC_AGGREGATE.


Ok, next try:

	To ensure loop prevention, BGP requires that all aggregate routes
	with AS paths that omit any AS number from the AS_PATHs being
         aggregated 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 as  
well as
         the more specific prefixes.


> We're being a bit pedantic about this whole topic if we look at this
> from a practical standpoint since a long time ago we concluded that
> providers were all using ATOMIC_AGGREGATE and tossing the entire
> AS_PATH when forming an aggregate.  Since ATOMIC_AGGREGATE is
> informational in the absense of de-aggregation this is not terribly
> important.


Agreed.


> The only thing that people were doing that was potentially dangerous
> was combining a /x and /y where x<y and forming a new /x and tossing
> the AS_PATH and adding ATOMIC_AGGREGATE.  That was safe in some
> topologies but generally a vary bad practice.


Yes.  I'm much rather see people generate the AS_SET properly, and  
not drop AS's.  To me, loop avoidance is paramount.

Tony

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



From idr-bounces@ietf.org Sat Dec 23 17:58:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GyFmI-0001Li-5h; Sat, 23 Dec 2006 17:55:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GyFmG-0001Je-W9
	for idr@ietf.org; Sat, 23 Dec 2006 17:55:41 -0500
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GyFmF-0005Fg-LR
	for idr@ietf.org; Sat, 23 Dec 2006 17:55:40 -0500
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	kBNMsICJ055352; Sat, 23 Dec 2006 17:54:18 -0500 (EST)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200612232254.kBNMsICJ055352@workhorse.brookfield.occnc.com>
To: Tony Li <tli@cisco.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02 
In-reply-to: Your message of "Sat, 23 Dec 2006 12:15:10 PST."
	<7A0A7AE9-FC3A-401C-ADA3-8A565288F3E9@cisco.com> 
Date: Sat, 23 Dec 2006 17:54:17 -0500
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
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


In message <7A0A7AE9-FC3A-401C-ADA3-8A565288F3E9@cisco.com>
Tony Li writes:
>  
>  
> Ok, next try:
>  
>    To ensure loop prevention, BGP requires that all aggregate routes
>    with AS paths that omit any AS number from the AS_PATHs being
>    aggregated 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 as well as
>    the more specific prefixes.


Fine.  If this it the only thing that needs fixing the draft is in
great shape.  Seems simple enough.

Curtis

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



From idr-bounces@ietf.org Wed Dec 27 13:38:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gzdcr-0004KQ-5t; Wed, 27 Dec 2006 13:35:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gzdcp-0004KL-H9
	for idr@ietf.org; Wed, 27 Dec 2006 13:35:39 -0500
Received: from blaster.systems.pipex.net ([62.241.163.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gzdco-0006rm-7l
	for idr@ietf.org; Wed, 27 Dec 2006 13:35:39 -0500
Received: from pc6 (1Cust45.tnt106.lnd4.gbr.da.uu.net [213.116.60.45])
	by blaster.systems.pipex.net (Postfix) with SMTP id 3AA4AE0003BF;
	Wed, 27 Dec 2006 18:35:30 +0000 (GMT)
Message-ID: <006701c729dd$56493ce0$0601a8c0@pc6>
From: "tom.petch" <cfinss@dial.pipex.com>
To: <curtis@occnc.com>, "Tony Li" <tli@cisco.com>
References: <200612232254.kBNMsICJ055352@workhorse.brookfield.occnc.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02 
Date: Wed, 27 Dec 2006 18:15:18 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
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

I am ok with the original issue but a related one I have yet to get my mind
around.

RFC4271 9.1.4 says

" If a BGP speaker receives overlapping routes, the Decision Process
   MUST consider both routes based on the configured acceptance policy.
   If both a less and a more specific route are accepted, then the
   Decision Process MUST install, in Loc-RIB, either both the less and
   the more specific routes or aggregate the two routes and install, in
   Loc-RIB, the aggregated route, provided that both routes have the
   same value of the NEXT_HOP attribute."

cf this I-D

"If the number of ASes in the AS_PATH exceeds the value of
   the AS_PATHLIMIT attribute, then the route MUST be ignored without
   further processing."

so what happens if the more specific NEXT_HOP is different?  Presumably this I-D
wins but what is the risk that 9.1.4 seeks to forestall?

In theory, by the time AS_PATHLIMIT bites, the NEXT_HOP should be the same but I
do not think we should be relying on that.

Tom Petch

----- Original Message -----
From: "Curtis Villamizar" <curtis@occnc.com>
To: "Tony Li" <tli@cisco.com>
Cc: <curtis@occnc.com>; "tom.petch" <cfinss@dial.pipex.com>; <idr@ietf.org>
Sent: Saturday, December 23, 2006 11:54 PM
Subject: Re: [Idr] draft-ietf-as-pathlimit-02


>
> In message <7A0A7AE9-FC3A-401C-ADA3-8A565288F3E9@cisco.com>
> Tony Li writes:
> >
> >
> > Ok, next try:
> >
> >    To ensure loop prevention, BGP requires that all aggregate routes
> >    with AS paths that omit any AS number from the AS_PATHs being
> >    aggregated 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 as well as
> >    the more specific prefixes.
>
>
> Fine.  If this it the only thing that needs fixing the draft is in
> great shape.  Seems simple enough.
>
> Curtis


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



From idr-bounces@ietf.org Wed Dec 27 17:13:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gzh03-0004G0-7e; Wed, 27 Dec 2006 17:11:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gzh01-0004FG-TZ
	for idr@ietf.org; Wed, 27 Dec 2006 17:11:49 -0500
Received: from [69.37.59.173] (helo=workhorse.brookfield.occnc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gzh00-0008Ge-Ha
	for idr@ietf.org; Wed, 27 Dec 2006 17:11:49 -0500
Received: from workhorse.brookfield.occnc.com (localhost [127.0.0.1])
	by workhorse.brookfield.occnc.com (8.13.4/8.13.4) with ESMTP id
	kBRMDVaY011403; Wed, 27 Dec 2006 17:13:32 -0500 (EST)
	(envelope-from curtis@workhorse.brookfield.occnc.com)
Message-Id: <200612272213.kBRMDVaY011403@workhorse.brookfield.occnc.com>
To: "tom.petch" <cfinss@dial.pipex.com>
Subject: Re: [Idr] draft-ietf-as-pathlimit-02 
In-reply-to: Your message of "Wed, 27 Dec 2006 18:15:18 +0100."
	<006701c729dd$56493ce0$0601a8c0@pc6> 
Date: Wed, 27 Dec 2006 17:13:31 -0500
From: Curtis Villamizar <curtis@occnc.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: Tony Li <tli@cisco.com>, idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
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


In message <006701c729dd$56493ce0$0601a8c0@pc6>
"tom.petch" writes:
>  
> I am ok with the original issue but a related one I have yet to get my mind
> around.
>  
> RFC4271 9.1.4 says
>  
> " If a BGP speaker receives overlapping routes, the Decision Process
>    MUST consider both routes based on the configured acceptance policy.
>    If both a less and a more specific route are accepted, then the
>    Decision Process MUST install, in Loc-RIB, either both the less and
>    the more specific routes or aggregate the two routes and install, in
>    Loc-RIB, the aggregated route, provided that both routes have the
>    same value of the NEXT_HOP attribute."
>  
> cf this I-D
>  
> "If the number of ASes in the AS_PATH exceeds the value of
>    the AS_PATHLIMIT attribute, then the route MUST be ignored without
>    further processing."
>  
> so what happens if the more specific NEXT_HOP is different?
> Presumably this I-D wins but what is the risk that 9.1.4 seeks to
> forestall?

Same thing that happens if policy does not accept the route.

> In theory, by the time AS_PATHLIMIT bites, the NEXT_HOP should be the
> same but I do not think we should be relying on that.

Not necessarily true.  The more specific could produce a more optimal
next hop and the less specific gets you there.  If the less specific
doesn't get you there, then AS_PATHLIMIT has to be increased.

> Tom Petch

An example might be a route to the far east or australia where an
aggregate and some more specifics are multihomed.  There might be a
slight advantage to a provider from Europe taking one US provider or
another but both should get there.

Curtis

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



