From idr-bounces@ietf.org Mon Nov 06 11:52:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gh7eF-000060-6T; Mon, 06 Nov 2006 11:48:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gh7eD-00005j-9h; Mon, 06 Nov 2006 11:48:33 -0500
Received: from mail-red.research.att.com ([192.20.225.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gh7e6-0001qX-Al; Mon, 06 Nov 2006 11:48:33 -0500
Received: from bright.research.att.com (bright.research.att.com
	[135.207.20.189])
	by mail-blue.research.att.com (Postfix) with ESMTP id 127D8147639;
	Mon,  6 Nov 2006 11:48:16 -0500 (EST)
Received: (from fenner@localhost)
	by bright.research.att.com (8.12.11.20060308/8.12.10/Submit) id
	kA6GmFFK025823; Mon, 6 Nov 2006 08:48:15 -0800
From: Bill Fenner <fenner@research.att.com>
Message-Id: <200611061648.kA6GmFFK025823@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: routing-discussion@ietf.org, idr@ietf.org, mpls@lists.ietf.org,
	pwe3@ietf.org
Date: Mon, 6 Nov 2006 08:48:15 -0800
Versions: dmail (linux) 2.7/makemail 2.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: 
Subject: [Idr] TCP Authentication discussion: tcpm wg, Thursday 1300-1500
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'd like to draw your attention to the tcpm working group
agenda; it begins with a discussion of draft-bellovin-tcpsec,
whose abstract reads:

   The TCP-MD5 option, commonly used to secure BGP sessions between
   routers, has many serious deficiencies.  We present here
   justifications for designing a new, more capable version of that
   option; we also discuss some of the design criteria for one.

I'd encourage those with thoughts and experience in this area to attend
if you can.

Thanks,
  Bill

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



From idr-bounces@ietf.org Mon Nov 06 18:32:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GhDtH-0005CZ-VF; Mon, 06 Nov 2006 18:28:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GhDtG-00059K-LW
	for idr@ietf.org; Mon, 06 Nov 2006 18:28:30 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhDtF-0005sf-1D
	for idr@ietf.org; Mon, 06 Nov 2006 18:28:30 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-4.cisco.com with ESMTP; 06 Nov 2006 14:12:52 -0800
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPJST0WrRApY/2dsb2JhbAA
X-IronPort-AV: i="4.09,392,1157353200"; 
	d="scan'208"; a="1862385478:sNHT325582522"
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.20060308/8.12.11) with ESMTP id
	kA6MCqwe027499 for <idr@ietf.org>; Mon, 6 Nov 2006 14:12:52 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id kA6MCqbF002111
	for <idr@ietf.org>; Mon, 6 Nov 2006 14:12:52 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Nov 2006 14:12:51 -0800
Received: from [130.129.70.48] ([10.21.97.51]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Nov 2006 14:12:51 -0800
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <C0A9A3BA-E82B-492E-B4A3-89DB395DA852@cisco.com>
References: <C12E538E.8B4A5%dward@cisco.com>
	<CB1652D2-7C42-4ED3-B2E2-5BDBB6A7DDEC@cisco.com>
	<45090ABA.5010709@cisco.com>
	<60929296-4E15-4045-8CCD-4A58D7480648@cisco.com>
	<45090F83.8020202@cisco.com>
	<2441AB91-320D-4A4B-9CF5-A1028624AC47@cisco.com>
	<450918B2.6070108@cisco.com>
	<C0A9A3BA-E82B-492E-B4A3-89DB395DA852@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B64C8555-E5AD-4496-96FC-3A8264133CF4@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur <flefauch@cisco.com>
Subject: Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands over IPv4 MPLS
	using IPv6 Provider Edge Routers (6PE)' to Proposed Standard
Date: Mon, 6 Nov 2006 14:11:37 -0800
To: idr@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 06 Nov 2006 22:12:51.0101 (UTC)
	FILETIME=[B30B9CD0:01C701F0]
DKIM-Signature: a=rsa-sha1; q=dns; l=7329; t=1162851172; x=1163715172;
	c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:Francois=20Le=20Faucheur=20<flefauch@cisco.com>
	|Subject:Re=3A=20[Idr]=20Re=3A=20Last=20Call=3A=20'Connecting=20IPv6=20Islands=20
	over=20IPv4=20MPLS=20using=20IPv6=20Provider=20Edge=20Routers=20(6PE)'=20to
	=20Proposed=20Standard;
	X=v=3Dcisco.com=3B=20h=3DFFXZuFu1QpCqX+u7KiEyL38/Suc=3D;
	b=bokyDeNDBDZYYQ2ZwTPcjnkVZKFYIgyVhyx+7DSM9f6VMBJelXHMuS1+IGkwWxZXZ6DDipYL
	DEPEvHipaLXXYXFo0DUB+z0o5v5tW1EnvZelM7MASQasljbXDwFfHH7S;
Authentication-Results: sj-dkim-7.cisco.com; header.From=flefauch@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96
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

Hello,

In order to help reach closure on that one, below is a proposal (that  
a few of us converged on) for tweaking the wording of 2858bis:

Replace:
>
>       Address Family Identifier (AFI):
>
>          This field in combination with the Subsequent Address Family
>          Identifier field identifies the Network Layer protocol
>          associated with the Network Address of Next Hop and the
>          semantics of the Network Layer Reachability Information that
>          follows.

with:

>       Address Family Identifier (AFI):
>
> 	 This field in combination with the Subsequent Address
> 	 Family Identifier field identifies the set of Network Layer
> 	 protocols to which the address carried in the Next Hop field
> 	 must belong, the way in which the address of the next hop
> 	 is encoded, and the semantics of the Network Layer
> 	 Reachability Information that follows. If the Next Hop is
> 	 allowed to be from more than one Network Layer protocol,
> 	 the encoding of the Next Hop MUST provide a way to determine
> 	 its Network Layer protocol.


Replace:
>
>       Subsequent Address Family Identifier (SAFI):
>
>          This field in combination with the Address Family Identifier
>          field identifies the Network Layer protocol associated  
> with the
>          Network Address of the Next Hop and the semantics of the
>          Network Layer Reachability Information that follows.

With:

>       Subsequent Address Family Identifier (SAFI):
>
> 	 This field in combination with the Address Family Identifier
> 	 field identifies the set of Network Layer protocols to which
> 	 the address carried in the Next Hop must belong, the way
> 	 in which the address of the next hop is encoded, and the
> 	 semantics of the Network Layer Reachability Information
> 	 that follows. If the Next Hop is allowed to be from more
> 	 than one Network Layer protocol, the encoding of the Next
> 	 Hop MUST provide a way to determine its Network Layer
> 	 protocol.


Cheers

Francois




On 14 Sep 2006, at 03:21, Francois Le Faucheur wrote:

> Hi Robert,
>
> On 14 Sep 2006, at 10:54, Robert Raszuk wrote:
>
>> Hey Francois,
>>
>> Ok so you proved that the text describing AFI/SAFI is poorly  
>> written and
>> does not even reflect implementations reality (for example as you  
>> said:
>> rt-constrain).
>>
>> I don't think that adding your change will make a huge difference and
>> will make the spec perfect.
>>
>> So since you have started what do you propose ? Are you  
>> volunteering to
>> clean-up/fix rfc2858bis to reflect needs and reality a bit more -
>> provided this is not too late now :-) ?
>>
>
> Considering 2858bis is in Editor's queue, I am proposing that:
> 	* asap: if indeed needed, we do the minimum correction of current  
> wording in 2858bis to ensure it does not preclude approaches that  
> are being defined or under consideration
> 	* we continue the ongoing discussion on what is the best approach  
> we want to have in the long run (in particular for Softwires) and  
> specify those outside 2858bis. If those require BGP extensions (eg  
> new BGP capabilities, new BGP syntax,...) those don't seem to need  
> to be specified in 2858bis nor to hold 2858bis from being  
> published. I think the Softwire chairs plan to try make that happen.
>
> Let's hear other thoughts.
>
> Thanks
>
> Francois
>
>> What I would propose to make existing implementations happy would  
>> be to
>> add a paragraph that if length is equal to 255 Next Hop will be  
>> present
>> in a separate NH attribute. That should sufficiently address a  
>> couple of
>>  today's requirements.
>>
>> Cheers,
>> R.
>>
>>> On 14 Sep 2006, at 10:14, Robert Raszuk wrote:
>>>
>>>> Francois,
>>>>
>>>>> This seems to be clearly defining associations between AFI/SAFI  
>>>>> and
>>>>> Next Hop. And it seems to be implying that only one type of  
>>>>> Next Hop
>>>>> can be associated with a AFI/SAFI pair.
>>>>
>>>> And I think this is fine
>>>> as only one next hop can be present in MP_REACH
>>>>  attribute today. How can you associate set to a single next  
>>>> hop :) ?
>>>>
>>>
>>> So, first, I think we now agree that rfc2858bis does talk about
>>> association between AFI/SAFI value and Next Hop Protocol.
>>>
>>> The point is that if the Next Hop protocol is _identified_ by the
>>> AFI/SAFI value, then, for a given NLRI format , you would need to
>>> systematically standardise two different AFI/SAFI pairs: one AFI/ 
>>> SAFI to
>>> advertise that NLRI format with an IPv4 Next Hop and another AFI/ 
>>> SAFI
>>> pair to advertise that same NLRI with an IPv6 Next Hop (not in same
>>> MP_REACH of course, but possibly in different MP_REACH or simply in
>>> different networks). While this has been mentioned as potential
>>> approach, there has been arguments as to why this is not  
>>> necessarily the
>>> best approach.
>>>
>>> For example, the rt-constrain draft you co-authored currently  
>>> defines a
>>> single AFI/SAFI pair (1/132) to advertise a Route Target membership
>>> NLRI, whether it is advertised with an IPv4 Next Hop or an IPv6 Next
>>> Hop. And then you use the Length to decide whether the Next Hop  
>>> is IPv4
>>> or IPv6. It seems to me that this somewhat contradicts the  
>>> rfc2858bis
>>> statement saying that "the AFI/SAFI identifies the Next Hop  
>>> protocol".
>>> It precisely does not, since it is instead identified by the Length.
>>>
>>> Again, at this stage I am not trying close the debate as to which
>>> approach is best, I just want to make sure rfc2858bis is kept  
>>> open to
>>> the candidate/existing approaches.
>>>
>>>
>>>> Also note that the text you are proposing to edit is by itself not
>>>> perfect already in the different angle. NH length is allowed to  
>>>> be zero
>>>> - and that is good - but once we make the length = 0 a lot of  
>>>> text in
>>>> this rfc would need to be rewritten.
>>>> Cheers,
>>>> R.
>>>>
>>>>
>>>>> Hi Robert,
>>>>>
>>>>> On 14 Sep 2006, at 09:54, Robert Raszuk wrote:
>>>>>
>>>>>> Francois,
>>>>>>
>>>>>> IMHO the AFI and SAFI paragraphs from rfc2858bis you are  
>>>>>> proposing to
>>>>>> edit talk about NLRIs to AFI/SAFI associations and not indicate
>>>>>> characteristics of the next hop itself.
>>>>>>
>>>>>
>>>>> The text says:
>>>>>
>>>>> "
>>>>> Address Family Identifier (AFI):
>>>>>
>>>>>          This field in combination with the Subsequent Address  
>>>>> Family
>>>>>          Identifier field identifies the Network Layer protocol
>>>>>          associated with the Network Address of Next Hop and the
>>>>>          semantics of the Network Layer Reachability  
>>>>> Information that
>>>>>          follows.
>>>>> "
>>>>>
>>>>> so in particular AFI/SAFI "identifies the network layer protocol
>>>>> associated with the network address of Next Hop".
>>>>>
>>>>> This seems to be clearly defining associations between AFI/SAFI  
>>>>> and Next
>>>>> Hop. And it seems to be implying that only one type of Next Hop  
>>>>> can be
>>>>> asociated with a AFI/SAFI pair.
>>>>> What am I missing?
>>>>>
>>>>> Francois
>>>>>
>>>>>
>>>>>> Cheers,
>>>>>> R.
>>
>>
>

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



From idr-bounces@ietf.org Tue Nov 07 12:13:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GhURS-0003cz-U3; Tue, 07 Nov 2006 12:08:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GhURR-0003cL-OG
	for idr@ietf.org; Tue, 07 Nov 2006 12:08:53 -0500
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhURP-0004ma-5h
	for idr@ietf.org; Tue, 07 Nov 2006 12:08:53 -0500
Received: from magenta.juniper.net (magenta.juniper.net [172.17.28.122])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id kA7H8mX56717
	for <idr@ietf.org>; Tue, 7 Nov 2006 09:08:50 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id kA7H8hE66516
	for <idr@ietf.org>; Tue, 7 Nov 2006 09:08:43 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200611071708.kA7H8hE66516@magenta.juniper.net>
To: idr@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <46874.1162919323.1@juniper.net>
Date: Tue, 07 Nov 2006 09:08:43 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 187ae6c2eea74946c0ab707161f6256d
Subject: [Idr] fixing wording in 2858bis
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,

The goal of the text proposed by Francois below is to clarify the
initial intent and more accurately reflect the current use of 2858bis.
In other words the goal of this change is to eliminate a mismatch
between the current of use 2858bis (as specified in such documents
as draft-ietf-l2vpn-signaling, draft-ietf-l3vpn-rt-constrain, and
draft-ietf-l2vpn-vpls-bgp, RFC4659, and draft-ooms-v6ops-bgp-tunnel)
and the current text of 2858bis.

Please comment on the proposed wording. The deadline for comments
is Nov 17,2006.

Yakov.
------- Forwarded Message

Date:    Mon, 06 Nov 2006 14:11:37 -0800
From:    Francois Le Faucheur <flefauch@cisco.com>
To:      idr@ietf.org
Subject: Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands over IPv4 MPLS using
	   IPv6 Provider Edge Routers (6PE)' to Proposed Standard

Hello,

In order to help reach closure on that one, below is a proposal (that  
a few of us converged on) for tweaking the wording of 2858bis:

Replace:
>
>       Address Family Identifier (AFI):
>
>          This field in combination with the Subsequent Address Family
>          Identifier field identifies the Network Layer protocol
>          associated with the Network Address of Next Hop and the
>          semantics of the Network Layer Reachability Information that
>          follows.

with:

>       Address Family Identifier (AFI):
>
> 	 This field in combination with the Subsequent Address
> 	 Family Identifier field identifies the set of Network Layer
> 	 protocols to which the address carried in the Next Hop field
> 	 must belong, the way in which the address of the next hop
> 	 is encoded, and the semantics of the Network Layer
> 	 Reachability Information that follows. If the Next Hop is
> 	 allowed to be from more than one Network Layer protocol,
> 	 the encoding of the Next Hop MUST provide a way to determine
> 	 its Network Layer protocol.


Replace:
>
>       Subsequent Address Family Identifier (SAFI):
>
>          This field in combination with the Address Family Identifier
>          field identifies the Network Layer protocol associated  
>          with the
>          Network Address of the Next Hop and the semantics of the
>          Network Layer Reachability Information that follows.

With:

>       Subsequent Address Family Identifier (SAFI):
>
> 	 This field in combination with the Address Family Identifier
> 	 field identifies the set of Network Layer protocols to which
> 	 the address carried in the Next Hop must belong, the way
> 	 in which the address of the next hop is encoded, and the
> 	 semantics of the Network Layer Reachability Information
> 	 that follows. If the Next Hop is allowed to be from more
> 	 than one Network Layer protocol, the encoding of the Next
> 	 Hop MUST provide a way to determine its Network Layer
> 	 protocol.


Cheers

Francois




On 14 Sep 2006, at 03:21, Francois Le Faucheur wrote:

> Hi Robert,
>
> On 14 Sep 2006, at 10:54, Robert Raszuk wrote:
>
>> Hey Francois,
>>
>> Ok so you proved that the text describing AFI/SAFI is poorly  
>> written and
>> does not even reflect implementations reality (for example as you  
>> said:
>> rt-constrain).
>>
>> I don't think that adding your change will make a huge difference and
>> will make the spec perfect.
>>
>> So since you have started what do you propose ? Are you  
>> volunteering to
>> clean-up/fix rfc2858bis to reflect needs and reality a bit more -
>> provided this is not too late now :-) ?
>>
>
> Considering 2858bis is in Editor's queue, I am proposing that:
> 	* asap: if indeed needed, we do the minimum correction of current  
> wording in 2858bis to ensure it does not preclude approaches that  
> are being defined or under consideration
> 	* we continue the ongoing discussion on what is the best approach  
> we want to have in the long run (in particular for Softwires) and  
> specify those outside 2858bis. If those require BGP extensions (eg  
> new BGP capabilities, new BGP syntax,...) those don't seem to need  
> to be specified in 2858bis nor to hold 2858bis from being  
> published. I think the Softwire chairs plan to try make that happen.
>
> Let's hear other thoughts.
>
> Thanks
>
> Francois
>
>> What I would propose to make existing implementations happy would  
>> be to
>> add a paragraph that if length is equal to 255 Next Hop will be  
>> present
>> in a separate NH attribute. That should sufficiently address a  
>> couple of
>>  today's requirements.
>>
>> Cheers,
>> R.
>>
>>> On 14 Sep 2006, at 10:14, Robert Raszuk wrote:
>>>
>>>> Francois,
>>>>
>>>>> This seems to be clearly defining associations between AFI/SAFI  
>>>>> and
>>>>> Next Hop. And it seems to be implying that only one type of  
>>>>> Next Hop
>>>>> can be associated with a AFI/SAFI pair.
>>>>
>>>> And I think this is fine
>>>> as only one next hop can be present in MP_REACH
>>>>  attribute today. How can you associate set to a single next  
>>>> hop :) ?
>>>>
>>>
>>> So, first, I think we now agree that rfc2858bis does talk about
>>> association between AFI/SAFI value and Next Hop Protocol.
>>>
>>> The point is that if the Next Hop protocol is _identified_ by the
>>> AFI/SAFI value, then, for a given NLRI format , you would need to
>>> systematically standardise two different AFI/SAFI pairs: one AFI/ 
>>> SAFI to
>>> advertise that NLRI format with an IPv4 Next Hop and another AFI/ 
>>> SAFI
>>> pair to advertise that same NLRI with an IPv6 Next Hop (not in same
>>> MP_REACH of course, but possibly in different MP_REACH or simply in
>>> different networks). While this has been mentioned as potential
>>> approach, there has been arguments as to why this is not  
>>> necessarily the
>>> best approach.
>>>
>>> For example, the rt-constrain draft you co-authored currently  
>>> defines a
>>> single AFI/SAFI pair (1/132) to advertise a Route Target membership
>>> NLRI, whether it is advertised with an IPv4 Next Hop or an IPv6 Next
>>> Hop. And then you use the Length to decide whether the Next Hop  
>>> is IPv4
>>> or IPv6. It seems to me that this somewhat contradicts the  
>>> rfc2858bis
>>> statement saying that "the AFI/SAFI identifies the Next Hop  
>>> protocol".
>>> It precisely does not, since it is instead identified by the Length.
>>>
>>> Again, at this stage I am not trying close the debate as to which
>>> approach is best, I just want to make sure rfc2858bis is kept  
>>> open to
>>> the candidate/existing approaches.
>>>
>>>
>>>> Also note that the text you are proposing to edit is by itself not
>>>> perfect already in the different angle. NH length is allowed to  
>>>> be zero
>>>> - and that is good - but once we make the length = 0 a lot of  
>>>> text in
>>>> this rfc would need to be rewritten.
>>>> Cheers,
>>>> R.
>>>>
>>>>
>>>>> Hi Robert,
>>>>>
>>>>> On 14 Sep 2006, at 09:54, Robert Raszuk wrote:
>>>>>
>>>>>> Francois,
>>>>>>
>>>>>> IMHO the AFI and SAFI paragraphs from rfc2858bis you are  
>>>>>> proposing to
>>>>>> edit talk about NLRIs to AFI/SAFI associations and not indicate
>>>>>> characteristics of the next hop itself.
>>>>>>
>>>>>
>>>>> The text says:
>>>>>
>>>>> "
>>>>> Address Family Identifier (AFI):
>>>>>
>>>>>          This field in combination with the Subsequent Address  
>>>>> Family
>>>>>          Identifier field identifies the Network Layer protocol
>>>>>          associated with the Network Address of Next Hop and the
>>>>>          semantics of the Network Layer Reachability  
>>>>> Information that
>>>>>          follows.
>>>>> "
>>>>>
>>>>> so in particular AFI/SAFI "identifies the network layer protocol
>>>>> associated with the network address of Next Hop".
>>>>>
>>>>> This seems to be clearly defining associations between AFI/SAFI  
>>>>> and Next
>>>>> Hop. And it seems to be implying that only one type of Next Hop  
>>>>> can be
>>>>> asociated with a AFI/SAFI pair.
>>>>> What am I missing?
>>>>>
>>>>> Francois
>>>>>
>>>>>
>>>>>> Cheers,
>>>>>> R.
>>
>>
>

_______________________________________________
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 Wed Nov 08 05:36:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ghkis-0002ry-DU; Wed, 08 Nov 2006 05:31:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ghkir-0002rr-JP
	for idr@ietf.org; Wed, 08 Nov 2006 05:31:57 -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 1Ghkiq-0000h8-6L
	for idr@ietf.org; Wed, 08 Nov 2006 05:31:57 -0500
Received: from gwinternet.correo.portal.ss ([10.99.1.89]) by
	smtp.seg-social.es (Netscape Messaging Server 4.15) with ESMTP
	id J8EQKW00.L3Z for <idr@ietf.org>; Wed, 8 Nov 2006 11:31:44 +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: <OF1491C8D3.BA85E49C-ONC1257220.0035E1E6-C1257220.0039EB3B@tgss.seg-social.es>
Date: Wed, 8 Nov 2006 11:31:39 +0100
X-MIMETrack: Serialize by Router on GWINTERNET/SRV/SEG-SOCIAL(Release
	6.5.5|November 30, 2005) at 08/11/2006 11:31:44
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Subject: [Idr] Draft on "Tunneled Inter-domain Routing"
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 sent a draft in October on "Tunneled Inter-domain Routing" (TIDR):
draft-adan-idr-tidr-00.txt.

TIDR is a proposal to modify the way in which traffic is routed to
"stub networks". The meaning of "stub network" is not the same for
inter-domain routing than for intra-domain routing.

For BGP a "stub network" is simply a leaf autonomous system, whether
it be single- or multi-homed. ISPs would add a new transitive BGP
attribute called LOCATOR to a client prefix so as to specify how other
autonomous systems can send tunneled traffic for that client prefix.
The tunnel type is left open in TIDR (we can use several types), but
the best way to understand TIDR is to think on multipoint GRE tunnels.

This LOCATOR attribute will eventually allow us to move client prefixes
from the global RIB to a new table called "Tunnel Information Base" (TIB).
And this move provides many benefits, e.g. client prefixes instabilities
will affect only the TIB, not the RIB.

ISP prefixes used for TIDR tunnels endpoints will be stored in the RIB
and they will act as true locators for the client prefixes. And client
prefixes will be stored in the TIB and will be used as identifiers.

When routing a packet to a leaf AS, the TIB will be search to perform
locator imposition, and the RIB will be used for actual routing. The
ISP that added the LOCATOR attribute will de-tunnel the traffic before
delivering it to its cliet.


This is the abstract:

   In this paper we propose a new hierarchical method to enhance
   the current routing and forwarding paradigm for the Internet
   called Tunneled Inter-Domain Routing (TIDR). We will present the
   way in which TIDR permits to establish tunnels to the edge of
   the network, and how they will be used to forward traffic to
   stub networks. These tunnels will be explicitly signaled by
   using a new transitive BGP attribute called LOCATOR. This new
   routing and forwarding paradigm provides, among others, the
   following benefits: global routing table reduction, inter-domain
   routing infrastructure protection, improved multi-homing of edge
   networks, numerous forwarding decisions for a particular address
   prefix, it stops the AS number consumption, and it can be
   smoothly deployed.


Any comments will be appreciated.

Juanjo



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



From idr-bounces@ietf.org Wed Nov 08 13:47:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GhsPV-0003Uz-0u; Wed, 08 Nov 2006 13:44:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GhsPS-0003UY-Tf
	for idr@ietf.org; Wed, 08 Nov 2006 13:44:26 -0500
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhsPS-0007w0-0a
	for idr@ietf.org; Wed, 08 Nov 2006 13:44:26 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.12.11.20060614/8.12.11) with ESMTP id kA8IiJVw011538; 
	Wed, 8 Nov 2006 20:44:20 +0200
Date: Wed, 8 Nov 2006 20:44:19 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: [Idr] fixing wording in 2858bis
In-Reply-To: <200611071708.kA7H8hE66516@magenta.juniper.net>
Message-ID: <Pine.LNX.4.64.0611082043490.11418@netcore.fi>
References: <200611071708.kA7H8hE66516@magenta.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: ClamAV 0.88.6/2173/Wed Nov 8 00:13:18 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-1.0 required=5.0 tests=AWL, BAYES_40,
	NO_RELAYS autolearn=ham version=3.1.7
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 162d87dc0b780d17da9b1934777fd451
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

On Tue, 7 Nov 2006, Yakov Rekhter wrote:
> The goal of the text proposed by Francois below is to clarify the
> initial intent and more accurately reflect the current use of 2858bis.
> In other words the goal of this change is to eliminate a mismatch
> between the current of use 2858bis (as specified in such documents
> as draft-ietf-l2vpn-signaling, draft-ietf-l3vpn-rt-constrain, and
> draft-ietf-l2vpn-vpls-bgp, RFC4659, and draft-ooms-v6ops-bgp-tunnel)
> and the current text of 2858bis.
> 
> Please comment on the proposed wording. The deadline for comments
> is Nov 17,2006.

Does this require revisiting the implementation report for 2858bis?

> ------- Forwarded Message
> 
> Date:    Mon, 06 Nov 2006 14:11:37 -0800
> From:    Francois Le Faucheur <flefauch@cisco.com>
> To:      idr@ietf.org
> Subject: Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands over IPv4 MPLS using
> 	   IPv6 Provider Edge Routers (6PE)' to Proposed Standard
> 
> Hello,
> 
> In order to help reach closure on that one, below is a proposal (that  
> a few of us converged on) for tweaking the wording of 2858bis:
> 
> Replace:
> >
> >       Address Family Identifier (AFI):
> >
> >          This field in combination with the Subsequent Address Family
> >          Identifier field identifies the Network Layer protocol
> >          associated with the Network Address of Next Hop and the
> >          semantics of the Network Layer Reachability Information that
> >          follows.
> 
> with:
> 
> >       Address Family Identifier (AFI):
> >
> > 	 This field in combination with the Subsequent Address
> > 	 Family Identifier field identifies the set of Network Layer
> > 	 protocols to which the address carried in the Next Hop field
> > 	 must belong, the way in which the address of the next hop
> > 	 is encoded, and the semantics of the Network Layer
> > 	 Reachability Information that follows. If the Next Hop is
> > 	 allowed to be from more than one Network Layer protocol,
> > 	 the encoding of the Next Hop MUST provide a way to determine
> > 	 its Network Layer protocol.
> 
> 
> Replace:
> >
> >       Subsequent Address Family Identifier (SAFI):
> >
> >          This field in combination with the Address Family Identifier
> >          field identifies the Network Layer protocol associated  
> >          with the
> >          Network Address of the Next Hop and the semantics of the
> >          Network Layer Reachability Information that follows.
> 
> With:
> 
> >       Subsequent Address Family Identifier (SAFI):
> >
> > 	 This field in combination with the Address Family Identifier
> > 	 field identifies the set of Network Layer protocols to which
> > 	 the address carried in the Next Hop must belong, the way
> > 	 in which the address of the next hop is encoded, and the
> > 	 semantics of the Network Layer Reachability Information
> > 	 that follows. If the Next Hop is allowed to be from more
> > 	 than one Network Layer protocol, the encoding of the Next
> > 	 Hop MUST provide a way to determine its Network Layer
> > 	 protocol.
> 
> 
> Cheers
> 
> Francois
> 
> 
> 
> 
> On 14 Sep 2006, at 03:21, Francois Le Faucheur wrote:
> 
> > Hi Robert,
> >
> > On 14 Sep 2006, at 10:54, Robert Raszuk wrote:
> >
> >> Hey Francois,
> >>
> >> Ok so you proved that the text describing AFI/SAFI is poorly  
> >> written and
> >> does not even reflect implementations reality (for example as you  
> >> said:
> >> rt-constrain).
> >>
> >> I don't think that adding your change will make a huge difference and
> >> will make the spec perfect.
> >>
> >> So since you have started what do you propose ? Are you  
> >> volunteering to
> >> clean-up/fix rfc2858bis to reflect needs and reality a bit more -
> >> provided this is not too late now :-) ?
> >>
> >
> > Considering 2858bis is in Editor's queue, I am proposing that:
> > 	* asap: if indeed needed, we do the minimum correction of current  
> > wording in 2858bis to ensure it does not preclude approaches that  
> > are being defined or under consideration
> > 	* we continue the ongoing discussion on what is the best approach  
> > we want to have in the long run (in particular for Softwires) and  
> > specify those outside 2858bis. If those require BGP extensions (eg  
> > new BGP capabilities, new BGP syntax,...) those don't seem to need  
> > to be specified in 2858bis nor to hold 2858bis from being  
> > published. I think the Softwire chairs plan to try make that happen.
> >
> > Let's hear other thoughts.
> >
> > Thanks
> >
> > Francois
> >
> >> What I would propose to make existing implementations happy would  
> >> be to
> >> add a paragraph that if length is equal to 255 Next Hop will be  
> >> present
> >> in a separate NH attribute. That should sufficiently address a  
> >> couple of
> >>  today's requirements.
> >>
> >> Cheers,
> >> R.
> >>
> >>> On 14 Sep 2006, at 10:14, Robert Raszuk wrote:
> >>>
> >>>> Francois,
> >>>>
> >>>>> This seems to be clearly defining associations between AFI/SAFI  
> >>>>> and
> >>>>> Next Hop. And it seems to be implying that only one type of  
> >>>>> Next Hop
> >>>>> can be associated with a AFI/SAFI pair.
> >>>>
> >>>> And I think this is fine
> >>>> as only one next hop can be present in MP_REACH
> >>>>  attribute today. How can you associate set to a single next  
> >>>> hop :) ?
> >>>>
> >>>
> >>> So, first, I think we now agree that rfc2858bis does talk about
> >>> association between AFI/SAFI value and Next Hop Protocol.
> >>>
> >>> The point is that if the Next Hop protocol is _identified_ by the
> >>> AFI/SAFI value, then, for a given NLRI format , you would need to
> >>> systematically standardise two different AFI/SAFI pairs: one AFI/ 
> >>> SAFI to
> >>> advertise that NLRI format with an IPv4 Next Hop and another AFI/ 
> >>> SAFI
> >>> pair to advertise that same NLRI with an IPv6 Next Hop (not in same
> >>> MP_REACH of course, but possibly in different MP_REACH or simply in
> >>> different networks). While this has been mentioned as potential
> >>> approach, there has been arguments as to why this is not  
> >>> necessarily the
> >>> best approach.
> >>>
> >>> For example, the rt-constrain draft you co-authored currently  
> >>> defines a
> >>> single AFI/SAFI pair (1/132) to advertise a Route Target membership
> >>> NLRI, whether it is advertised with an IPv4 Next Hop or an IPv6 Next
> >>> Hop. And then you use the Length to decide whether the Next Hop  
> >>> is IPv4
> >>> or IPv6. It seems to me that this somewhat contradicts the  
> >>> rfc2858bis
> >>> statement saying that "the AFI/SAFI identifies the Next Hop  
> >>> protocol".
> >>> It precisely does not, since it is instead identified by the Length.
> >>>
> >>> Again, at this stage I am not trying close the debate as to which
> >>> approach is best, I just want to make sure rfc2858bis is kept  
> >>> open to
> >>> the candidate/existing approaches.
> >>>
> >>>
> >>>> Also note that the text you are proposing to edit is by itself not
> >>>> perfect already in the different angle. NH length is allowed to  
> >>>> be zero
> >>>> - and that is good - but once we make the length = 0 a lot of  
> >>>> text in
> >>>> this rfc would need to be rewritten.
> >>>> Cheers,
> >>>> R.
> >>>>
> >>>>
> >>>>> Hi Robert,
> >>>>>
> >>>>> On 14 Sep 2006, at 09:54, Robert Raszuk wrote:
> >>>>>
> >>>>>> Francois,
> >>>>>>
> >>>>>> IMHO the AFI and SAFI paragraphs from rfc2858bis you are  
> >>>>>> proposing to
> >>>>>> edit talk about NLRIs to AFI/SAFI associations and not indicate
> >>>>>> characteristics of the next hop itself.
> >>>>>>
> >>>>>
> >>>>> The text says:
> >>>>>
> >>>>> "
> >>>>> Address Family Identifier (AFI):
> >>>>>
> >>>>>          This field in combination with the Subsequent Address  
> >>>>> Family
> >>>>>          Identifier field identifies the Network Layer protocol
> >>>>>          associated with the Network Address of Next Hop and the
> >>>>>          semantics of the Network Layer Reachability  
> >>>>> Information that
> >>>>>          follows.
> >>>>> "
> >>>>>
> >>>>> so in particular AFI/SAFI "identifies the network layer protocol
> >>>>> associated with the network address of Next Hop".
> >>>>>
> >>>>> This seems to be clearly defining associations between AFI/SAFI  
> >>>>> and Next
> >>>>> Hop. And it seems to be implying that only one type of Next Hop  
> >>>>> can be
> >>>>> asociated with a AFI/SAFI pair.
> >>>>> What am I missing?
> >>>>>
> >>>>> Francois
> >>>>>
> >>>>>
> >>>>>> Cheers,
> >>>>>> R.
> >>
> >>
> >
> 
> _______________________________________________
> 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
> 

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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



From idr-bounces@ietf.org Wed Nov 08 13:50:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GhsVL-0001SU-2i; Wed, 08 Nov 2006 13:50:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GhsVK-0001SP-9H
	for idr@ietf.org; Wed, 08 Nov 2006 13:50:30 -0500
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhsVJ-0000Mr-Mr
	for idr@ietf.org; Wed, 08 Nov 2006 13:50:30 -0500
Received: from magenta.juniper.net (magenta.juniper.net [172.17.28.122])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	kA8IoS1Z012687; Wed, 8 Nov 2006 10:50:28 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id kA8IoSE46242;
	Wed, 8 Nov 2006 10:50:28 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200611081850.kA8IoSE46242@magenta.juniper.net>
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: [Idr] fixing wording in 2858bis 
In-Reply-To: Your message of "Wed, 08 Nov 2006 20:44:19 +0200."
	<Pine.LNX.4.64.0611082043490.11418@netcore.fi> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <72404.1163011828.1@juniper.net>
Date: Wed, 08 Nov 2006 10:50:28 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 578c2c9d0cb01ffe6e1ca36540edd070
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

Pekka,

> On Tue, 7 Nov 2006, Yakov Rekhter wrote:
> > The goal of the text proposed by Francois below is to clarify the
> > initial intent and more accurately reflect the current use of 2858bis.
> > In other words the goal of this change is to eliminate a mismatch
> > between the current of use 2858bis (as specified in such documents
> > as draft-ietf-l2vpn-signaling, draft-ietf-l3vpn-rt-constrain, and
> > draft-ietf-l2vpn-vpls-bgp, RFC4659, and draft-ooms-v6ops-bgp-tunnel)
> > and the current text of 2858bis.
> > 
> > Please comment on the proposed wording. The deadline for comments
> > is Nov 17,2006.
> 
> Does this require revisiting the implementation report for 2858bis?

No.

Yakov.

> > ------- Forwarded Message
> > 
> > Date:    Mon, 06 Nov 2006 14:11:37 -0800
> > From:    Francois Le Faucheur <flefauch@cisco.com>
> > To:      idr@ietf.org
> > Subject: Re: [Idr] Re: Last Call: 'Connecting IPv6 Islands over IPv4 MPLS u
sing
> > 	   IPv6 Provider Edge Routers (6PE)' to Proposed Standard
> > 
> > Hello,
> > 
> > In order to help reach closure on that one, below is a proposal (that  
> > a few of us converged on) for tweaking the wording of 2858bis:
> > 
> > Replace:
> > >
> > >       Address Family Identifier (AFI):
> > >
> > >          This field in combination with the Subsequent Address Family
> > >          Identifier field identifies the Network Layer protocol
> > >          associated with the Network Address of Next Hop and the
> > >          semantics of the Network Layer Reachability Information that
> > >          follows.
> > 
> > with:
> > 
> > >       Address Family Identifier (AFI):
> > >
> > > 	 This field in combination with the Subsequent Address
> > > 	 Family Identifier field identifies the set of Network Layer
> > > 	 protocols to which the address carried in the Next Hop field
> > > 	 must belong, the way in which the address of the next hop
> > > 	 is encoded, and the semantics of the Network Layer
> > > 	 Reachability Information that follows. If the Next Hop is
> > > 	 allowed to be from more than one Network Layer protocol,
> > > 	 the encoding of the Next Hop MUST provide a way to determine
> > > 	 its Network Layer protocol.
> > 
> > 
> > Replace:
> > >
> > >       Subsequent Address Family Identifier (SAFI):
> > >
> > >          This field in combination with the Address Family Identifier
> > >          field identifies the Network Layer protocol associated  
> > >          with the
> > >          Network Address of the Next Hop and the semantics of the
> > >          Network Layer Reachability Information that follows.
> > 
> > With:
> > 
> > >       Subsequent Address Family Identifier (SAFI):
> > >
> > > 	 This field in combination with the Address Family Identifier
> > > 	 field identifies the set of Network Layer protocols to which
> > > 	 the address carried in the Next Hop must belong, the way
> > > 	 in which the address of the next hop is encoded, and the
> > > 	 semantics of the Network Layer Reachability Information
> > > 	 that follows. If the Next Hop is allowed to be from more
> > > 	 than one Network Layer protocol, the encoding of the Next
> > > 	 Hop MUST provide a way to determine its Network Layer
> > > 	 protocol.
> > 
> > 
> > Cheers
> > 
> > Francois
> > 
> > 
> > 
> > 
> > On 14 Sep 2006, at 03:21, Francois Le Faucheur wrote:
> > 
> > > Hi Robert,
> > >
> > > On 14 Sep 2006, at 10:54, Robert Raszuk wrote:
> > >
> > >> Hey Francois,
> > >>
> > >> Ok so you proved that the text describing AFI/SAFI is poorly  
> > >> written and
> > >> does not even reflect implementations reality (for example as you  
> > >> said:
> > >> rt-constrain).
> > >>
> > >> I don't think that adding your change will make a huge difference and
> > >> will make the spec perfect.
> > >>
> > >> So since you have started what do you propose ? Are you  
> > >> volunteering to
> > >> clean-up/fix rfc2858bis to reflect needs and reality a bit more -
> > >> provided this is not too late now :-) ?
> > >>
> > >
> > > Considering 2858bis is in Editor's queue, I am proposing that:
> > > 	* asap: if indeed needed, we do the minimum correction of current  
> > > wording in 2858bis to ensure it does not preclude approaches that  
> > > are being defined or under consideration
> > > 	* we continue the ongoing discussion on what is the best approach  
> > > we want to have in the long run (in particular for Softwires) and  
> > > specify those outside 2858bis. If those require BGP extensions (eg  
> > > new BGP capabilities, new BGP syntax,...) those don't seem to need  
> > > to be specified in 2858bis nor to hold 2858bis from being  
> > > published. I think the Softwire chairs plan to try make that happen.
> > >
> > > Let's hear other thoughts.
> > >
> > > Thanks
> > >
> > > Francois
> > >
> > >> What I would propose to make existing implementations happy would  
> > >> be to
> > >> add a paragraph that if length is equal to 255 Next Hop will be  
> > >> present
> > >> in a separate NH attribute. That should sufficiently address a  
> > >> couple of
> > >>  today's requirements.
> > >>
> > >> Cheers,
> > >> R.
> > >>
> > >>> On 14 Sep 2006, at 10:14, Robert Raszuk wrote:
> > >>>
> > >>>> Francois,
> > >>>>
> > >>>>> This seems to be clearly defining associations between AFI/SAFI  
> > >>>>> and
> > >>>>> Next Hop. And it seems to be implying that only one type of  
> > >>>>> Next Hop
> > >>>>> can be associated with a AFI/SAFI pair.
> > >>>>
> > >>>> And I think this is fine
> > >>>> as only one next hop can be present in MP_REACH
> > >>>>  attribute today. How can you associate set to a single next  
> > >>>> hop :) ?
> > >>>>
> > >>>
> > >>> So, first, I think we now agree that rfc2858bis does talk about
> > >>> association between AFI/SAFI value and Next Hop Protocol.
> > >>>
> > >>> The point is that if the Next Hop protocol is _identified_ by the
> > >>> AFI/SAFI value, then, for a given NLRI format , you would need to
> > >>> systematically standardise two different AFI/SAFI pairs: one AFI/ 
> > >>> SAFI to
> > >>> advertise that NLRI format with an IPv4 Next Hop and another AFI/ 
> > >>> SAFI
> > >>> pair to advertise that same NLRI with an IPv6 Next Hop (not in same
> > >>> MP_REACH of course, but possibly in different MP_REACH or simply in
> > >>> different networks). While this has been mentioned as potential
> > >>> approach, there has been arguments as to why this is not  
> > >>> necessarily the
> > >>> best approach.
> > >>>
> > >>> For example, the rt-constrain draft you co-authored currently  
> > >>> defines a
> > >>> single AFI/SAFI pair (1/132) to advertise a Route Target membership
> > >>> NLRI, whether it is advertised with an IPv4 Next Hop or an IPv6 Next
> > >>> Hop. And then you use the Length to decide whether the Next Hop  
> > >>> is IPv4
> > >>> or IPv6. It seems to me that this somewhat contradicts the  
> > >>> rfc2858bis
> > >>> statement saying that "the AFI/SAFI identifies the Next Hop  
> > >>> protocol".
> > >>> It precisely does not, since it is instead identified by the Length.
> > >>>
> > >>> Again, at this stage I am not trying close the debate as to which
> > >>> approach is best, I just want to make sure rfc2858bis is kept  
> > >>> open to
> > >>> the candidate/existing approaches.
> > >>>
> > >>>
> > >>>> Also note that the text you are proposing to edit is by itself not
> > >>>> perfect already in the different angle. NH length is allowed to  
> > >>>> be zero
> > >>>> - and that is good - but once we make the length = 0 a lot of  
> > >>>> text in
> > >>>> this rfc would need to be rewritten.
> > >>>> Cheers,
> > >>>> R.
> > >>>>
> > >>>>
> > >>>>> Hi Robert,
> > >>>>>
> > >>>>> On 14 Sep 2006, at 09:54, Robert Raszuk wrote:
> > >>>>>
> > >>>>>> Francois,
> > >>>>>>
> > >>>>>> IMHO the AFI and SAFI paragraphs from rfc2858bis you are  
> > >>>>>> proposing to
> > >>>>>> edit talk about NLRIs to AFI/SAFI associations and not indicate
> > >>>>>> characteristics of the next hop itself.
> > >>>>>>
> > >>>>>
> > >>>>> The text says:
> > >>>>>
> > >>>>> "
> > >>>>> Address Family Identifier (AFI):
> > >>>>>
> > >>>>>          This field in combination with the Subsequent Address  
> > >>>>> Family
> > >>>>>          Identifier field identifies the Network Layer protocol
> > >>>>>          associated with the Network Address of Next Hop and the
> > >>>>>          semantics of the Network Layer Reachability  
> > >>>>> Information that
> > >>>>>          follows.
> > >>>>> "
> > >>>>>
> > >>>>> so in particular AFI/SAFI "identifies the network layer protocol
> > >>>>> associated with the network address of Next Hop".
> > >>>>>
> > >>>>> This seems to be clearly defining associations between AFI/SAFI  
> > >>>>> and Next
> > >>>>> Hop. And it seems to be implying that only one type of Next Hop  
> > >>>>> can be
> > >>>>> asociated with a AFI/SAFI pair.
> > >>>>> What am I missing?
> > >>>>>
> > >>>>> Francois
> > >>>>>
> > >>>>>
> > >>>>>> Cheers,
> > >>>>>> R.
> > >>
> > >>
> > >
> > 
> > _______________________________________________
> > 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
> > 
> 
> -- 
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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



From idr-bounces@ietf.org Fri Nov 10 06:31:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GiUX8-0008M6-GR; Fri, 10 Nov 2006 06:26:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GiUX7-0008M1-Bn
	for idr@ietf.org; Fri, 10 Nov 2006 06:26:53 -0500
Received: from giss7.seg-social.es ([194.179.55.129] helo=smtp.seg-social.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiUX5-0001EG-Qy
	for idr@ietf.org; Fri, 10 Nov 2006 06:26:53 -0500
Received: from gwinternet.correo.portal.ss ([10.99.1.89]) by
	smtp.seg-social.es (Netscape Messaging Server 4.15) with ESMTP
	id J8IIGG01.82N for <idr@ietf.org>; Fri, 10 Nov 2006 12:26:40 +0100 
From: JUAN-JOSE.ADAN@giss.seg-social.es
X-Priority: 1 (High)
Subject: Rm: [Idr] Draft on "Tunneled Inter-domain Routing"
To: idr@ietf.org
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OF48A9BC53.4F9624F7-ONC1257222.003C705E-C1257222.003E3652@tgss.seg-social.es>
Date: Fri, 10 Nov 2006 12:18:24 +0100
X-MIMETrack: Serialize by Router on GWINTERNET/SRV/SEG-SOCIAL(Release
	6.5.5|November 30, 2005) at 10/11/2006 12:26:39
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
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


Robert,

Thank you very much for your comments.
You can find my comments below.

Regards,
Juanjo


----- Remitido por JUAN JOSE ADAN LUENGO/GISS/SEG-SOCIAL con fecha
10/11/2006 12:01 -----

Robert Raszuk <raszuk@cisco.com> escribi=F3 el 08/11/2006 14:48:08:

> Juan,
>
> Excellent doc !!!! I must say that I with few other folks from Cisco =
are
> also actively working on a very similar idea for about last 8 months.=
 I
> am not sure if you would like to continue the individual work or woul=
d
> be willing for a joint collaboration.
>

The draft I sent to the IDR WG is based on a paper I tried to publish
in the journal of big networking company based on San Jose (California)=
,
without success. Later, I rewrote the paper for the Global Internet
Symposium of INFOCOM-2006, but it was rejected. Therefore this is my
third attempt to get it. However I must say I am new. This is my
first research paper and I don't know if it could published as an
individual submission, after it is pulished by all of your comments
of course.

The draft is a general overview of TIDR, and I left for a second
draft the specifications for the LOCATOR attribute and the
modifications for the BGP bestpath algorithm. For this second draft,
if my proposal is interesting, I will be very glad to write
it with you.

I am also preparing a third draft on "The use of TIDR with IGPs".

>
> While reading your draft I found a few opportunities which may even m=
ore
> relax the need for a separate locator advertisement. Also AS numbers =
are
> now 4 bytes not two :). I will try to spend some time this week to
> comment on it.
>
> Cheers,
> R.
>
>
> > Hi,
> >
> > I sent a draft in October on "Tunneled Inter-domain Routing" (TIDR)=
:
> > draft-adan-idr-tidr-00.txt.
> >
> > TIDR is a proposal to modify the way in which traffic is routed to
> > "stub networks". The meaning of "stub network" is not the same for
> > inter-domain routing than for intra-domain routing.
> >
> > For BGP a "stub network" is simply a leaf autonomous system, whethe=
r
> > it be single- or multi-homed. ISPs would add a new transitive BGP
> > attribute called LOCATOR to a client prefix so as to specify how ot=
her
> > autonomous systems can send tunneled traffic for that client prefix=
.
> > The tunnel type is left open in TIDR (we can use several types), bu=
t
> > the best way to understand TIDR is to think on multipoint GRE tunne=
ls.
> >
> > This LOCATOR attribute will eventually allow us to move client pref=
ixes
> > from the global RIB to a new table called "Tunnel Information Base"=

(TIB).
> > And this move provides many benefits, e.g. client prefixes
instabilities
> > will affect only the TIB, not the RIB.
> >
> > ISP prefixes used for TIDR tunnels endpoints will be stored in the =
RIB
> > and they will act as true locators for the client prefixes. And cli=
ent
> > prefixes will be stored in the TIB and will be used as identifiers.=

> >
> > When routing a packet to a leaf AS, the TIB will be search to perfo=
rm
> > locator imposition, and the RIB will be used for actual routing. Th=
e
> > ISP that added the LOCATOR attribute will de-tunnel the traffic bef=
ore
> > delivering it to its cliet.
> >
> >
> > This is the abstract:
> >
> >    In this paper we propose a new hierarchical method to enhance
> >    the current routing and forwarding paradigm for the Internet
> >    called Tunneled Inter-Domain Routing (TIDR). We will present the=

> >    way in which TIDR permits to establish tunnels to the edge of
> >    the network, and how they will be used to forward traffic to
> >    stub networks. These tunnels will be explicitly signaled by
> >    using a new transitive BGP attribute called LOCATOR. This new
> >    routing and forwarding paradigm provides, among others, the
> >    following benefits: global routing table reduction, inter-domain=

> >    routing infrastructure protection, improved multi-homing of edge=

> >    networks, numerous forwarding decisions for a particular address=

> >    prefix, it stops the AS number consumption, and it can be
> >    smoothly deployed.
> >
> >
> > Any comments will be appreciated.
> >
> > Juanjo
> >
> >
> >
> > _______________________________________________
> > 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 Nov 10 06:31:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GiUXC-0008MT-WA; Fri, 10 Nov 2006 06:26:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GiUXA-0008MO-Vn
	for idr@ietf.org; Fri, 10 Nov 2006 06:26:56 -0500
Received: from giss7.seg-social.es ([194.179.55.129] helo=smtp.seg-social.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiUX9-0001Ef-T6
	for idr@ietf.org; Fri, 10 Nov 2006 06:26:56 -0500
Received: from gwinternet.correo.portal.ss ([10.99.1.89]) by
	smtp.seg-social.es (Netscape Messaging Server 4.15) with ESMTP
	id J8IIGO01.H2O for <idr@ietf.org>; Fri, 10 Nov 2006 12:26:48 +0100 
From: JUAN-JOSE.ADAN@giss.seg-social.es
X-Priority: 1 (High)
Subject: Rm: [Idr] Draft on "Tunneled Inter-domain Routing"
To: idr@ietf.org
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OFD49734CA.999280B4-ONC1257222.0034EA45-C1257222.003EBC2D@tgss.seg-social.es>
Date: Fri, 10 Nov 2006 12:24:07 +0100
X-MIMETrack: Serialize by Router on GWINTERNET/SRV/SEG-SOCIAL(Release
	6.5.5|November 30, 2005) at 10/11/2006 12:26:47
MIME-Version: 1.0
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 4515df9441674711565101d9d5c4f63f
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="===============1740932478=="
Errors-To: idr-bounces@ietf.org

--===============1740932478==
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: base64

DQpSb2JlcnQsDQoNCkkgaGF2ZSBpbmNsdWRlZCBteSBjb21tZW50cyB0byB5b3VyIG9ic2VydmF0
aW9ucy4gSSBob3BlDQp0aGV5IHB1dCBtb3JlIGxpZ2h0IG9uIG15IHByb3Bvc2FsLg0KDQpJIHdp
bGwgYmUgb3V0IGZvciBhIHdlZWsuIEkgd2lsbCBjaGVjayBsYXRlciBhYm91dCB0aGUNCnBvc3Np
YmlsaXR5IG9mIGhhdmluZyBhIG1lZXRpbmcgc29tZXdoZXJlIGluIEV1cm9wZS4NCkkgd2lsbCBo
YXZlIHRvIGNvbnZpbmNlIG15IGJvc3MgZmlyc3QgOi0pLg0KDQpSZWdhcmRzLA0KSnVhbmpvDQoN
Cg0KLS0tLS0gUmVtaXRpZG8gcG9yIEpVQU4gSk9TRSBBREFOIExVRU5HTy9HSVNTL1NFRy1TT0NJ
QUwgY29uIGZlY2hhDQoxMC8xMS8yMDA2IDEwOjM5IC0tLS0tDQoNClJvYmVydCBSYXN6dWsgPHJh
c3p1a0BjaXNjby5jb20+IGVzY3JpYmnDsyBlbCAwOS8xMS8yMDA2IDAwOjU2OjMzOg0KDQo+IEhp
IEp1YW4sDQo+DQo+IEJlbG93IGFyZSBteSBtb3JlIGRldGFpbGVkIGNvbW1lbnRzLiBZb3UgaGF2
ZSBhIGNob2ljZSB0byBpZ25vcmUgdGhlbSBvcg0KPiBhdHRlbXB0IHRvIHdvcmsgdG9nZXRoZXIg
dG8gc2ltcGxpZnkgdGhlIGN1cnJlbnQgcHJvcG9zYWwgdG8gYmUgbXVjaA0KPiBtb3JlIGVhc3kg
dG8gZGVwbG95IGJvdGggZnJvbSB2ZW5kb3IgYXMgd2VsbCBhcyBjdXN0b21lcnMgcG9pbnQgb2Yg
dmlldy4NCj4NCj4gQ29tbWVudHM6DQo+IC0tLS0tLS0tLQ0KPg0KPiA+IEkgc2VudCBhIGRyYWZ0
IGluIE9jdG9iZXIgb24gIlR1bm5lbGVkIEludGVyLWRvbWFpbiBSb3V0aW5nIiAoVElEUik6DQo+
ID4gZHJhZnQtYWRhbi1pZHItdGlkci0wMC50eHQuDQo+DQo+ID4gMS4gSW50cm9kdWN0aW9uDQo+
ID4NCj4gPiAgICBSb3V0aW5nIHByb3RvY29scyBpbnN0YWxsIGFsbCBzdWJuZXQgcHJlZml4ZXMg
aW4gdGhlIHJvdXRpbmcgdGFibGUNCj4gPiAgICBpbiB0aGUgc2FtZSBtYW5uZXIsIHdpdGhvdXQg
dGFraW5nIGludG8gY29uc2lkZXJhdGlvbiB0aGUgcGxhY2UNCj4gPiAgICB3aGVyZSB0aGVzZSBz
dWJuZXRzIHJlc2lkZSB3aXRoaW4gdGhlIG5ldHdvcmsuIEJlY2F1c2Ugb2YgdGhpcyBmYWN0LA0K
PiA+ICAgIGV2ZXJ5IHRpbWUgdGhlcmUgaXMgYSBjaGFuZ2UgaW4gYSBzdHViIG5ldHdvcmsgdGhl
IFJJQiBpcyBhbHdheXMNCj4gPiAgICByZWJ1aWx0IGFnYWluLA0KPg0KPiBXZWxsIG1vc3Qgb2Yg
dGhlIG1vZGVybiBpbXBsZW1lbnRhdGlvbnMgZG8gbm90ICJyZWJ1aWxkIiBSSUIgYWdhaW4gb24N
Cj4gZGVsZXRlL3VwZGF0ZS9tb2RpZnkgbWVzc2FnZS4gSW5jcmVtZW50YWwgdXBkYXRpbmcgb2Yg
Ym90aCBSSUIgJiBGSUIgYXJlDQo+IHdlbGwga25vd24gdGVjaG5pY3MuDQoNCldoZW4gSSBzYXkg
InJlYnVpbGQiIEkgZG9uwrR0IG1lYW4gdG8gcmVidWlsZCB0aGUgUklCIF9mcm9tIHNjcmF0Y2hf
Lg0KDQo+DQo+ID4gdGh1cyBwb3NzaWJseSBjYXVzaW5nIGFuIGluc3RhYmlsaXR5IHRvIHRoZSBy
b3V0aW5nDQo+ID4gICAgc3lzdGVtOg0KPiA+DQo+ID4gICAgMSkgSW4gdGhlIEludGVybmV0LCBw
cmVmaXhlcyBvZiBhIG11bHRpLWhvbWVkIG5vbi10cmFuc2l0IGRvbWFpbiwNCj4gPiAgICAgICBp
LmUuIGFuIGF1dG9ub21vdXMgc3lzdGVtIG5vdCBwYXJ0aWNpcGF0aW5nIGluIHRydWUgaW50ZXIt
ZG9tYWluDQo+ID4gICAgICAgcm91dGluZywgYXJlIGdpdmVuIHRoZSBzYW1lIHRyZWF0bWVudCBh
cyB0aGUgcHJlZml4ZXMgb2YgYQ0KdHJhbnNpdA0KPiA+ICAgICAgIGRvbWFpbi4gSXJyZXNwZWN0
aXZlIG9mIHRoZSB0eXBlIG9mIGRvbWFpbiBhbGwgcHJlZml4ZXMgYXJlDQo+ID4gICAgICAgaW5z
dGFsbGVkIGJ5IEJHUCBbMV0gaW4gdGhlIHNhbWUgZ2xvYmFsIHJvdXRpbmcgdGFibGUsIGFsc28g
a25vd24NCj4gPiAgICAgICBhcyB0aGUgZ2xvYmFsIHJvdXRpbmcgaW5mb3JtYXRpb24gYmFzZSAo
UklCKS4NCj4gPg0KPiA+ICAgIDIpIFdpdGhpbiBhIHNpbmdsZSBkb21haW4sIHN0dWIgbmV0d29y
ayBwcmVmaXhlcyBhcmUgaW5zdGFsbGVkIGJ5DQo+ID4gICAgICAgaW50ZXJpb3IgZ2F0ZXdheSBw
cm90b2NvbHMgKElHUHMpLCBsaWtlIE9TUEYgWzJdIG9yIElTLUlTIFszXSwNCj4gPiAgICAgICBp
biB0aGUgc2FtZSByb3V0aW5nIHRhYmxlIChSSUIpIHdoZXJlIHRoZXkgaW5zdGFsbCB0cmFuc2l0
DQo+ID4gICAgICAgbmV0d29ya3MsIHdoZXRoZXIgc3R1YiBuZXR3b3JrIHByZWZpeGVzIGFyZSBp
bnN0YWxsZWQgYXMgYQ0KPiA+ICAgICAgIHJlc3VsdCBvZiBhIGZ1bGwgU1BGIHJ1biBvciBhIHBh
cnRpYWwgU1BGIHJ1bi4NCj4NCj4gV2VsbCB3aXRoIEJHUCB5b3UgYXJlIGNvcnJlY3QuIFdpdGgg
SUdQcyBub3Qgc28gbXVjaCA7KSBUaGUgZ2VuZXJhbA0KPiBwcmFjdGljZSBpcyB0byBpbnN0YWxs
IGp1c3QgYSBzdW1tYXJ5IHJvdXRlIHRvIGEgc3R1YiBhcmVhLiBUaGUgaXNzdWUNCj4gaGVyZSBp
cyB0aGF0IHdpdGggTVBMUyBhbmQgTVBMUyBhcHBsaWNhdGlvbnMgdGhlcmUgaXMgcmVxdWlyZW1l
bnQgZm9yDQo+IC8zMnMgdGhhdCdzIHdoeSB0aG9zZSBhcmUgbGVha2VkIGV2ZXJ5d2hlcmUgaW4g
bWFueSBNUExTIG5ldHdvcmtzLiBCdXQNCj4gdGhpcyBpcyBtb3JlIG9mIGV4Y2VwdGlvbiB0aGVu
IGEgcnVsZSBpbiBnZW5lcmFsLg0KDQpXaGVuIEkgc2F5ICJzdHViIG5ldHdvcmsiIEkgZG9uJ3Qg
bWVhbiAic3R1YiBhcmVhIi4gSWYgd2UgaGF2ZQ0KYSBiaWcgcm91dGluZyBkb21haW4gY29uZmln
dXJlZCBhcyBhIHNpbmdsZSBhcmVhLCBPU1BGIG9yIElTLUlTLA0KdGhlIG51bWJlciBvZiAic3R1
YiBuZXR3b3JrcyIgKHRob3NlIGluIHdoaWNoIHRoZSBJR1AgZG9lc27CtHQNCmVzdGFibGlzaCBh
bnkgYWRqYWNlbmNpZXMpIG1heSBiZSBfdmVyeSBiaWdfLCB0aHVzIG1ha2luZyB0aGUgUklCDQph
bmQgb2J2aW91c2x5IHRoZSBGSUIgdmVyeSBiaWcgZXZlbiBmb3IgYSBzaW5nbGUgYXJlYS4NCg0K
DQo+DQo+ID4gICAgVHVubmVsZWQgSW50ZXItRG9tYWluIFJvdXRpbmcgKFRJRFIpIG1vZGlmaWVz
IGJvdGggdGhlIHVzdWFsIHJvdXRpbmcNCj4gPiAgICBhbmQgZm9yd2FyZGluZyBwcm9jZXNzZXMg
Y3VycmVudGx5IHVzZWQgaW4gSVAgbmV0d29ya3MgYnkgdHJlYXRpbmcNCj4gPiAgICBzdHViIG5l
dHdvcmtzIGluIGEgZGlmZmVyZW50IHdheSB0aGFuIHRyYW5zaXQgbmV0d29ya3MuIFRoaXMgc3Bl
Y2lhbA0KPiA+ICAgIHRyZWF0bWVudCBpcyB0d29mb2xkOiBzdHViIG5ldHdvcmsgcHJlZml4ZXMg
d2lsbCBub3QgYmUgaW5zdGFsbGVkIGluDQo+ID4gICAgdGhlIFJJQjsgYW5kIHRyYWZmaWMgZm9y
IHN0dWIgbmV0d29ya3Mgd2lsbCBiZSBzZW50IG92ZXIgdHVubmVscw0KPiA+ICAgIGVzdGFibGlz
aGVkIHRvIHRoZSBlZGdlIG9mIHRoZSBuZXR3b3JrLiBXZSB3aWxsIHNob3cgaG93IHRoaXMNCnNw
ZWNpYWwNCj4gPiAgICB0cmVhdG1lbnQgb2Ygc3R1YiBuZXR3b3JrIHByZWZpeGVzIGlzIG5vdGhp
bmcgZWxzZSBidXQgYW4gZWFzeQ0KPiA+ICAgIHNvbHV0aW9uIHRvIHRoZSBpZGVudGlmaWVyLWxv
Y2F0aW9uIHNwbGl0IHByb2JsZW0sIGFuZCBzb21lIG9mIHRoZQ0KPiA+ICAgIG1hbnkgYmVuZWZp
dHMgdGhhdCBzdWNoIGEgc3BsaXQgcHJvdmlkZXMgaW4gdGVybXMgb2Ygc2NhbGFiaWxpdHksDQo+
ID4gICAgc3RhYmlsaXR5IGFuZCB0aGUgaW50cm9kdWN0aW9uIG9mIG5ldyByb3V0aW5nIGZlYXR1
cmVzLg0KPg0KPiBXZWxsIGxldCdzIGZvY3VzIG9uIEJHUCBwYXJ0IG9ubHkuIFlvdSBoYXZlIHRv
IHJlYWxpemUgYW5kIG9ic2VydmUgdGhhdA0KPiB0byBnZXQgbW9zdCBvZiB0aGUgYmVuZWZpdHMg
eW91IGFyZSB0YXJnZXRpbmcgdGhpcyB3b3JrIHRvIHN1Y2ggYSBzcGxpdA0KPiBpcyBub3QgYSBt
dXN0LiBBcyBsb25nIGFzIHlvdSBjYW4gaWRlbnRpZnkgaW4gdGhlIGN1cnJlbnQgc3R1Yi90cmFu
c2l0DQo+IG5ldHdvcmtzIGFuIGVsZW1lbnQgd2hpY2ggY2FuIGJlIHVzZWQgYXMgdGhlIHR1bm5l
bCBlbmRwb2ludCB3ZSBhcmUNCj4gZmluZS4gVGhlcmUgaXMgbm8gbmVlZCBmb3IgaW50cm9kdWN0
aW9uIG9mIG5ldyBMb2NhdG9yIGF0dHJpYnV0ZS4gV2UgKEkNCj4gJiBTdGVmYW5vIFByZXZpZGkp
IGhhdmUgcHJvcG9zZWQganVzdCB0aGUgdXNlIG9mIEFTIElQIGFkZHJlc3MgYXMgdGhlDQo+IGF1
dG9tYXRlZCBsb2NhdG9yLiBPZiBjb3Vyc2Uga2VlcGluZyBpbiBtaW5kIHRoYXQgZXZlbiB0aGUg
bWFwcGluZyBjb3VsZA0KPiBiZSBhdXRvbWF0ZWQuIE1vc3Qgb2YgdGhlIGdhaW5zIGFyZSB0aGUg
c2FtZSB3aGlsZSBpbXBsZW1lbnRhdGlvbiBhbmQNCj4gZGVwbG95bWVudCByZWFsaXN0aWMuIEkg
ZG8gbm90IHRoaW5rIHRoYXQgd2Ugd2lsbCBnbyBmYXIgaWYgdGhlIGFzayBmb3INCj4gaW1wbGVt
ZW50YXRpb25zIHRvIHN1cHBvcnQgVElCLiBTZWUgdGhlIGJvdHRvbSBsaW5lIGlzIHRoYXQgZXNw
ZWNpYWxseQ0KPiBpbiB0cmFuc2l0IG5ldHdvcmtzIGhhdmluZyBiaWcgQkdQIFJJQiBvbiB0aGUg
UlAgaXMgbm8gaXNzdWUuIFdoYXQgaXMNCj4gdGhlIGJpZ2dlc3Qgc2F2aW5nIGlzIHRvIGhhdmUg
YSBjb250YWluZWQgRklCLiBUaGlzIGlzIHdoeSBJIHRoaW5rIHRoYXQNCj4gdGhlcmUgaXMgYSBs
b3Qgb2YgZ2FpbiB3aXRob3V0IG11Y2ggaW1wbGVtZW50YXRpb24gY2hhbmdlcyB0byBiZQ0KcHJv
cG9zZWQuDQo+DQoNCkkgdGhpbmsgdGhlIGxvY2F0b3IvSUQgc3BsaXQgaGFzIGFwcGVhcmVkIG1h
bnkgdGltZXMgaW4NCm1hbnkgV0dzIGFzIHRoZSBwb3NzaWJsZSBzb2x1dGlvbiB0byBtYW55IHBy
b2JsZW1zIG9mIHRoZQ0KY3VycmVudCByb3V0aW5nIHBhcmFkaWdtLg0KDQo+ID4NCj4gPiAyLiBJ
ZGVudGlmaWVycyBhbmQgTG9jYXRvcnMgaW4gVElEUg0KPiA+DQo+ID4gICAgSXQgaXMgd2VsbCBr
bm93biB0aGF0IElQIGFkZHJlc3NlcyBhcmUgc2VtYW50aWNhbGx5IG92ZXJsb2FkZWQNCmJlY2F1
c2UNCj4gPiAgICB0aGV5IGNhcnJ5IGluZm9ybWF0aW9uIG9uIGJvdGggdGhlIGxvY2F0aW9uIGFu
ZCB0aGUgaWRlbnRpdHkgb2ZhDQpkZXZpY2UuDQo+ID4gICAgVGhlIG5lZWQgdG8gc3BsaXQgdGhl
c2UgdHdvIHJvbGVzIGhhcyBiZWVuIGRpc2N1c3NlZCBtYW55IHRpbWVzIGluDQptYW55DQo+ID4g
ICAgZGlmZmVyZW50IGZvcnVtcyB3aXRoIHJlZ2FyZCB0byAoYSkgdGhlIHBvc3NpYmxlIGludHJv
ZHVjdGlvbiBvZiBhDQpuZXcNCj4gPiAgICBoaWVyYXJjaGljYWwgcm91dGluZyBwYXJhZGlnbSBp
biB0aGUgSW50ZXJuZXQgWzRdIFs1XSBbNl0sIChiKSBhcyBhDQp3YXkNCj4gPiAgICB0byBwcm92
aWRlIHNjYWxhYmxlIHNpdGUgbXVsdGktaG9taW5nIFs3XSwgb3IgKGMpIHRoZSBpbnRyb2R1Y3Rp
b24NCm9mIGENCj4gPiAgICBuZXcgYWRkcmVzc2luZyBhcmNoaXRlY3R1cmUgWzhdLCBhbW9uZyBv
dGhlciBiZW5lZml0cy4NCj4NCj4gVmVyeSB0cnVlLg0KPg0KPiA+ICAgIFNvbWUgaGF2ZSBwb2lu
dGVkIG91dCB0aGF0IE5BVCBpcyB0aGUgZmVhdHVyZSB0aGF0IGZpbmFsbHkgYnJlYWtzDQp0aGUN
Cj4gPiAgICBzZW1hbnRpYyBvdmVybG9hZCBvZiB0aGUgSVAgYWRkcmVzcyBhcyBib3RoIGEgbG9j
YXRvciBhbmQgYSBnbG9iYWwNCj4gPiAgICBpZGVudGlmaWVyIFs5XSBidXQgd2hhdCBOQVQgcmVh
bGx5IGRvZXMgaXMgdG8gdHJhbnNsYXRlIGdsb2JhbA0KPiA+ICAgIGlkZW50aWZpZXJzIGludG8g
YW5vdGhlciBzZXQgb2YgaWRlbnRpZmllcnMsIG5hbWVseSBwcml2YXRlDQo+ID4gICAgaWRlbnRp
ZmllcnMsIHdoaWNoIGlzIHByZWNpc2VseSB0aGUgcmVhc29uIHdoeSB0aGUgZW5kLXRvLWVuZA0K
cHJpbmNpcGxlDQo+ID4gICAgaXMgYnJva2VuIGJ5IE5BVC4gVElEUiBjbGVhcmx5IGRpZmZlcmVu
dGlhdGVzIHRoZSB1c2Ugb2YgbG9jYXRvcnMNCmFuZA0KPiA+ICAgIGlkZW50aWZpZXJzIGFuZCBk
b2VzIG5vdCBpbXBlZGUgdGhlIHVzZSBvZiBlaXRoZXIgaWRlbnRpZmllcnMgb3IgbmV3DQo+ID4g
ICAgbWVjaGFuaXNtcyBmb3IgZW5kcG9pbnQgaWRlbnRpZmljYXRpb24gd2l0aGluIHRoZSBhcHBs
aWNhdGlvbnMuDQo+DQo+IEkgd2FzIG5ldmVyIGtlZW4gb24gdGhlIE5BVCBhcHByb2FjaCB0byBz
Y2FsZSB0aGUgbmV0IDspLg0KPg0KPiA+IDMuIFR1bm5lbGVkIEludGVyLWRvbWFpbiBSb3V0aW5n
DQo+ID4NCj4gPiAgICBEbyB3ZSByZWFsbHkgbmVlZCBzdHViIG5ldHdvcmtzIHByZWZpeGVzIGZv
ciBhY3R1YWwgSVAgcm91dGluZz8uDQpUSURSDQo+ID4gICAgcGVybWl0cyB0byBzZW5kIHRyYWZm
aWMgZm9yIHN0dWIgbmV0d29ya3Mgb3ZlciB0dW5uZWxzIGVzdGFibGlzaGVkDQp0bw0KPiA+ICAg
IHRoZSBlZGdlIG9mIHRoZSBuZXR3b3JrLiBCdXQsIHdoZXJlIGlzIHRoZSBlZGdlIG9mIGEgbmV0
d29yaz8uIEluDQpUSURSLA0KPiA+ICAgIHRoZSBlZGdlIG9mIGEgbmV0d29yayB3aWxsIGJlIHRo
ZSBwbGFjZSB3aGVyZSBzdHViIG5ldHdvcmtzDQphcmVhdHRhY2hlZC4NCj4gPiAgICBBbmQgdGhl
IGV4YWN0IG1lYW5pbmcgb2YgInN0dWIgbmV0d29yayIgd2lsbCBiZSByZWxhdGl2ZSB0byB0aGUN
Cj4gPiAgICBlbnZpcm9ubWVudCB3ZSBhcmUgYW5hbHl6aW5nOiB0aGUgSW50ZXJuZXQgb3IgYW4g
ZW50ZXJwcmlzZSBkb21haW4uDQo+ID4NCj4gPiAgICBUSURSIHByb3Bvc2VzIGEgbmV3IG1ldGhv
ZCB0aGF0IGN1cnJlbnQgcm91dGluZyBwcm90b2NvbHMgd2lsbCB1c2UNCnRvDQo+ID4gICAgbWFu
YWdlIHN0dWIgbmV0d29ya3MuIEluIFRJRFIgc3R1YiBuZXR3b3JrcyB3aWxsIG5vdCBiZSBpbnN0
YWxsZWQgaW4NCnRoZQ0KPiA+ICAgIFJJQiwgYXMgdXN1YWwsIGJ1dCBpbiBhIG5ldyB0YWJsZSBj
YWxsZWQgVHVubmVsIEluZm9ybWF0aW9uIEJhc2UNCihUSUIpLg0KPg0KPiBTZWUgYWJvdmUgY29t
bWVudC4NCj4NCj4gPiAgICBBZnRlcndhcmRzLCB3aGVuIHJvdXRpbmcgYSBwYWNrZXQgdG8gdGhl
IGRlc3RpbmF0aW9uIHByZWZpeCwgdGhlIFRJQg0Kd2lsbA0KPiA+ICAgIGJlIHNlYXJjaGVkIGZp
cnN0IHRvIHBlcmZvcm0gdHVubmVsIGltcG9zaXRpb24sIGFuZCBzZWNvbmRseSB0aGUgUklCDQpm
b3INCj4gPiAgICBhY3R1YWwgcm91dGluZy4NCj4NCj4gSWYgVElCIGhhcyB0byBiZSBzZWFyY2hl
ZCB0aGVyZSBpcyBubyBuZWVkIGZvciBzcGxpdC4gVG8gZG8gaXQgYXQgbGluZQ0KPiByYXRlIGl0
IGhhcyB0byBiZSBkb25lIGluIGhhcmR3YXJlLiBCdHcgLSBKdXN0IEZZSSBoYXJkd2FyZSBhbHJl
YWR5IGRvZXMNCj4gcmVjdXJzaW9uIGVhc2lseSBvbiB0aGUgc2FtZSB0YWJsZXMgOikuDQo+DQoN
CldoZW4gSSBzYXkgd2UgbmVlZCBhIG5ldyB0YWJsZSwgdGhlIFRJQiwgSSBhbSBub3QgcHJlY2x1
ZGluZw0KdGhlIGltcGxlbWVudGF0aW9uIG9mIHRoZSBUSUIgaW4gYSBzcGVjaWZpYyBtYW5uZXIu
IEluIGZhY3QNCml0IGNvdWxkIGJlIGluY2x1ZGVkIHdpdGhpbiB0aGUgRklCLiBUaGUgcHJvYmxl
bSBhcHBlYXJzIGlmDQp0aGUgbnVtYmVyIG9mIHR1bm5lbHMgaW4gdGhlIFRJQiBpcyB0b28gYmln
LiBCdXQgZG9uwrR0IGZvcmdldA0KdGhhdCB0aGUgVElCIGlzIG5vdCBuZWNlc3Nhcnkgb24gcHVy
ZSB0cmFuc2l0IHJvdXRlcnMgYnV0DQpvbmx5IG9mIGVkZ2Ugcm91dGVycywgdGhvc2UgZmFjaW5n
IGNsaWVudHMuDQoNClRoZSBpZGVhIG9mIGhhdmluZyBhbiBJUCBhZGRyZXNzIGZvciBhbiBBUyBp
cyBzb21ldGhpbmcgdGhhdA0KSSBhbHNvIGNvbnNpZGVyZWQgYnV0IEkgdGhpbmsgaXQgaXMgbXVj
aCBtb3JlIGludGVyZXN0aW5nIHRvDQpoYXZlIGEgcHJlZml4IHNvIHRoYXQgd2UgY291bGQgZXZl
biBzcGVjaWZ5IGEgc3BlY2lmaWMgZW50cnkNCnBvaW50IGluIHRoZSBBUyBwb3IgdHJhZmZpYyBk
aXJlY3RlZCB0byBhIHNwZWNpZmljICJpZGVudGlmaWVyDQpwcmVmaXgiLiBBbmQgYSBzcGVjaWZp
YyBsb2NhdG9yIGNvdWxkIGJlIGNvbmZpZ3VyZWQgYXMgYW4gYW55Y2FzdA0KSVAgYWRkcmVzcyBz
byB0aGF0IGluIGNhc2Ugb2YgYSBwcm9ibGVtIGluIGFuIGVudHJ5IHBvaW50LCB0aGUNCnR1bm5l
bGVkIHRyYWZmaWMgY291bGQgYmUgZGVsaXZlcmVkIHRocm91Z2ggYW5vdGhlciBlbnRyeSBwb2lu
dC4NCg0KPg0KPiA+ICAgIEFmdGVyIHRoZSBlZGdlIHJvdXRlciBwZXJmb3JtcyB0dW5uZWwgaW1w
b3NpdGlvbiwgYWxsDQo+ID4gICAgcm91dGVycyBpbiB0aGUgbWlkZGxlIHdpbGwgcm91dGUgdGhp
cyBwYWNrZXQgdW50aWwgdGhlIHJvdXRlciBiZWluZw0KdGhlDQo+ID4gICAgdGFpbC1lbmQgb2Yg
dGhlIHR1bm5lbC4NCj4gPg0KPiA+ICAgIEFsbCB3ZSBuZWVkIGlzIHRvIGZpbmQgYSB3YXkgZm9y
IGEgcm91dGVyIHRvIHRlbGwgaXQgaXMgYWJsZSB0bw0KcmVjZWl2ZQ0KPiA+ICAgIHR1bm5lbGVk
IHRyYWZmaWMgZm9yIGEgZ2l2ZW4gcHJlZml4LiBGb3IgdGhhdCBwdXJwb3NlIHdlIHdpbGwNCmFu
YWx5emUNCj4gPiAgICBjdXJyZW50IHJvdXRpbmcgcHJvdG9jb2xzIHRvIGZpbmQgb3V0IHdoYXQg
aW5mb3JtYXRpb24gY2FuIGJlIHVzZWQNCmFzIGENCj4gPiAgICBsb2NhdG9yIGZvciBhIHNwZWNp
ZmljIHN0dWIgbmV0d29yay4gT25jZSB3ZSBmaW5kIGEgcG9zc2libGUgbG9jYXRvcg0KdGhlbg0K
PiA+ICAgIHdlIHdpbGwgYmUgYWJsZSB0byBzZW5kIHR1bm5lbGVkIHRyYWZmaWMgZm9yIHRoYXQg
c3R1YiBuZXR3b3JrLA0KcHJvdmlkZWQNCj4gPiAgICB0aGF0IGJvdGggdGhlIHJvdXRlciBwZXJm
b3JtaW5nIHR1bm5lbCBpbXBvc2l0aW9uIGFuZCB0aGUgcm91dGVyDQpyZWNlaXZpbmcNCj4gPiAg
ICB0aGUgdHVubmVsZWQgcGFja2V0IGFyZSBUSURSLWF3YXJlLiBUaGVyZWZvcmUsIHRoZSByZWNl
aXZpbmcgcm91dGVyLA0KaW4NCj4gPiAgICBhZGRpdGlvbiB0byB0aGUgSVAgYWRkcmVzcyBvZiB0
aGUgdHVubmVsIGRlc3RpbmF0aW9uIChsb2NhdG9yKSx3aWxsDQpoYXZlDQo+ID4gICAgdG8gdGVs
bCB0aGUgdHlwZXMgb2YgZW5jYXBzdWxhdGlvbnMgaXQgc3VwcG9ydHMgZm9yIGEgcGFydGljdWxh
cg0KcHJlZml4LA0KPiA+ICAgIGFuZCB0aGUgcm91dGVyIHBlcmZvcm1pbmcgdHVubmVsIGltcG9z
aXRpb24gd2lsbCBoYXZlIHRvIHN1cHBvcnQNCnRoYXQNCj4gPiAgICBzcGVjaWZpYyBlbmNhcHN1
bGF0aW9uIG1ldGhvZCwgYSBtdWx0aXBvaW50IEdSRSB0dW5uZWwgZm9yIGluc3RhbmNlLg0KPg0K
PiBXZWxsIHdlIGFscmVhZHkgaGF2ZSBhIG51bWJlciBvZiBkcmFmdCBwcm9wb3NhbHMgZGVmaW5p
bmcgZm9yIHR1bm5lbA0KPiBlbmNhcHN1bGF0aW9uIGF0dHJpYnV0ZXMgb3IgZXh0IGNvbW11bml0
aWVzIGZvciB0aGF0IHB1cnBvc2UuIEkgd3JvdGUNCj4gb25lIHdpdGggUmFodWwgaW4gdGhlIHBh
c3QsIEplcmVteSBkaWQgc29tZSBvcmlnaW5hbCB3b3JrLCB0aGVuIHdlIGhhbmQNCj4gdHVubmVs
IHNhZmkgKG5vdyBjYWxsZWQgaW5mby1zYWZpKSwgYW5kIGNvbWluZyB1cCB5ZXQgYW5vdGhlciBv
bmUgc29vbg0KPiBmcm9tIG1lIDotKS4gTm90IHN1cmUgdGhlcmUgaXMgYSBuZXcgbmVlZCBmb3Ig
eWV0IGFub3RoZXIgdHVubmVsIGRlY2FwDQo+IGNhcGFiaWxpdHkgZW5jb2RpbmcuDQo+DQoNCkkg
dGhpbmsgbXkgcHJvcG9zYWwgaXMgbXVjaCBtb3JlIGdlbmVyYWwuIE1vc3Qgb2YgdGhlIHZhbHVl
LWFkZGVkDQpzZXJ2aWNlcyBhcmUgYmFzZWQgb24gdHVubmVscyAobW9iaWxpdHksIFZQTnMsIFRF
LC4uLikuIEkgdGhpbmsNCnRoZXJlIGlzIGEgbmVlZCBmb3IgYSByaWNoZXIgcm91dGluZyBwYXJh
ZGlnbSwgYW5kIGluIG15IG9waW5pb24NCnRoZSBzb2x1dGlvbiBpcyBzb21ldGhpbmcgbGlrZSBU
SURSLiBUSURSIGlzIG5vdCBhbiBvdmVybGF5IHNvbHV0aW9uDQpidXQgYSB3YXkgdG8gY29tYmlu
ZSBkaXJlY3QgYW5kIGluZGlyZWN0IHJvdXRpbmcsIHRoZSBsYXR0ZXIgYmFzZWQNCm9uIHR1bm5l
bHMuIEFuZCBJIHRoaW5rIFRJRFIgcGFyYWRpZ20gY291bGQgYWxzbyBiZSB2YWx1YWJsZSBmb3IN
Cm90aGVyIFdHcyAodjZvcHMsIHRyaWxsLCAuLi4pLiBJIHRoaW5rIHdlIG5lZWQgdGhlIGNvbWUg
b2YgYWdlDQpvZiB0dW5uZWxzIHdpdGhpbiB0aGUgSVAgYXJjaGl0ZWN0dXJlLg0KDQoNCj4gPiAg
ICBUaGlzIElQIGNvdWxkIGJlIGZvcm1lZCB1c2luZyBhIHNwYXJlIC84IHByZWZpeCBhbmQgdGhl
IEFTDQo+ID4gICAgbnVtYmVyIGZvciBzZWNvbmQgYW5kIHRoaXJkIG9jdGV0cywgYW5kIGl0IHdv
dWxkIGJlIHVzZWQgYXMNCj4gPiAgICBhbiBhbnljYXN0IGFkZHJlc3MgYXNzaWduZWQgdG8gYQ0K
Pg0KPiBXaHkgc2Vjb25kICYgdGhpcmQgb2N0ZXQgPyBTdXJlIHdlIGNhbiB1c2UgMDAwLzggd2hp
Y2ggaXMgcmVzZXJ2ZWQgYnkNCj4gSUFOQSBzaW5jZSAxOTgxIGJ1dCBub3cgd2UgaGF2ZSA0IGJ5
dGVzIEFTZXMuIFdlIGNvdWxkIHVzZSB0aHJlZSBieXRlcw0KPiBvdXQgb2YgaXQuDQo+DQoNCkkg
a25vdyB0aGF0IEFTIG51bWJlcnMgYXJlIDQtYnl0ZSBsb25nLiBJIG1lbnRpb24gMi1ieXRlIEFT
TnMNCmluIG15IGRvYyB0byBsZWF2ZSB0aGUgZm91cnRoIGJ5dGUgZm9yIGV4YW1wbGUgdG8gc3Bl
Y2lmeSBhDQpzcGVjaWZpYyBlbnRyeSBwb2ludCBpbiB0aGUgQVMuDQoNCj4gPiAgICBMZXQncyBj
b250aW51ZSB0byBsb29rIGF0IHRoZSBBU19QYXRoIGF0dHJpYnV0ZTogaWYgdGhlDQo+ID4gICAg
cGVudWx0aW1hdGUgQVMgaW4gdGhlIHBhdGggd291bGQgYmUgYWJsZSB0byBhY2NlcHQNCj4gPiAg
ICB0dW5uZWxlZCB0cmFmZmljIGZvciB0aGF0IHByZWZpeCB0aGVuIHdlIGNvdWxkDQo+DQo+IFdo
eSBkbyB5b3Ugc3RpbGwgcHJvcG9zaW5nIHRoZSBjb3VwbGluZyBvZiBsb2NhdG9yIHRvIHByZWZp
eGVzIGluIHNheWluZw0KPiAiZm9yIHRoYXQgcHJlZml4IiA/IElNSE8gd2Ugc2hvdWxkIGtlZXAg
dGhvc2UgdHdvIGluZGVwZW5kZW50LiBJbiBvdGhlcg0KPiB3b3JkcyBpZiBBU0JSIFggaXMgYWJs
ZSB0byBkZS1jYXBzdWxhdGUgdHJhZmZpYyB0byBpdCdzIEFTIChpZiBzdHViIG9yDQo+IHN0dWIt
cGVudWx0aW1hdGUpIGl0IHNob3VsZCBiZSBvayBmb3IgYW55IHByZWZpeCB0byBiZSB0dW5uZWxl
ZCB0byBzdWNoDQpBUy4NCj4NCg0KTWF5YmUgbXkgRW5nbGlzaCBpcyBub3QgY2xlYXIgZW5vdWdo
LiAiTG9jYXRvciBwcmVmaXhlcyIgYW5kDQoiSWRlbnRpZmllciBwcmVmaXhlcyIgYXJlIGtlcHQg
aW5kZXBlbmRlbnQuIFdoYXQgSSBtZWFuIGlzDQp0aGF0IHRyYWZmaWMgZm9yIGEgbGVhZiBBUyAo
c3R1YiBvciBtdWx0aS1ob21lZCkgc2hvdWxkIGJlDQpkZWNhcHN1bGF0ZWQgYnkgYW55IG9mIGl0
cyB1cHN0cmVhbSBJU1BzLiBPYnZpb3VzbHkgdGhpcw0KaXMgYWxzbyB0cnVlIGZvciB0aGUgSVNQ
IHByZWZpeGVzIHRoYXQgdGhlIElTUCB1c2VzIGZvcg0KaXRzIG93biBzZXJ2aWNlcyAoRE5TLCB3
ZWIgc2VydmVycywgLi4uKS4gSW4gb3RoZXIgd29yZHMsDQp0aGUgImlkZW50aWZpZXIgcHJlZml4
ZXMiIHdpdGhpbiB0aGUgSVNQIG5ldHdvcmsgYXJlIGFsc28NCmFzc2lnbmVkICJsb2NhdG9yIHBy
ZWZpeGVzIiB3aGVuIHRoZSBmb3JtZXIgYXJlIGFubm91bmNlZA0KYnkgQkdQLg0KDQoNCg0KPiA+
IDUuMi4gVElEUiBCYXNpYyBNZWNoYW5pc20gZm9yIGEgU2luZ2xlLUhvbWVkIFNpdGUuDQo+ID4N
Cj4gPiAgICBMZXTvv71zIGNvbnNpZGVyIGEgc2l0ZSBzaW5nbGUtaG9tZWQgdG8gdXBzdHJlYW0g
cHJvdmlkZXIgSVNQMSB0aGF0DQp1c2VzIGENCj4gPiAgICBwcm92aWRlci1pbmRlcGVuZGVudCBw
cmVmaXgsIHdoYXQgaW1wbGllcyBpdHMgcHJlc2VuY2UgaW4gdGhlDQo+ID4gICAgQkdQIGdsb2Jh
bCBSSUIuIExldCdzIHN1cHBvc2Ugbm93IHRoYXQgSVNQMSBpcyBUSURSLWF3YXJlLCB3aGljaA0K
bWVhbnMNCj4+ICAgICBpdCB3aWxsIGFkdmVydGlzZSB0aGUgcHJlZml4IHVzaW5nIGEgbmV3IHRy
YW5zaXRpdmUgQkdQIGF0dHJpYnV0ZQ0KY2FsbGVkIExPQ0FUT1INCj4NCj4gWW91IGRvIG5vdCBh
ZHZlcnRpc2UgdGhlIHByZWZpeCB1c2luZyBuZXcgYXR0cmlidXRlLiBUaGUgbmV3IGF0dHJpYnV0
ZQ0KPiBjb3VsZCBiZSBhdHRhY2ggdG8gdGhlIHVwZGF0ZSBtc2cgaWYgZXZlciByZXF1aXJlZC4N
Cj4NCg0KVGhlIHByZWZpeCBvZiB0aGUgY2xpZW50IG5ldHdvcmsgd2lsbCBiZWNvbWUgYW4gImlk
ZW50aWZpZXIgcHJlZml4Ig0Kd2hlbiBpdHMgSVNQIGFkZHMgdGhlIExPQ0FUT1IgYXR0cmlidXRl
LiBUaGUgcHJlZml4ZXMgdXNlZCBieSB0aGUgSVNQDQpmb3IgdGhlIHR1bm5lbCBlbmRwb2ludHMg
d2lsbCBiZSBhbm5vdW5jZWQgd2l0aG91dCBhZGRpbmcgYW55DQpMT0NBVE9SIGF0dHJpYnV0ZSwg
aS5lLiB0aGV5IHdpbGwgYmUgImxvY2F0b3IgcHJlZml4ZXMiLCBhcyBhcmUNCmFsbCB0aGUgcHJl
Zml4ZXMgY3VycmVudGx5IHN0b3JlZCBpbiB0aGUgZ2xvYmFsIEludGVybmV0IHRhYmxlLg0KUHJl
Zml4ZXMgaW4gdGhlIGN1cnJlbnQgZ2xvYmFsIEJHUCB0YWJsZSBhcmUgImxvY2F0b3IgcHJlZml4
ZXMiDQppbiB0aGUgc2Vuc2UgdGhhdCB0aGV5IGFyZSB1c2VkIGZvciBhY3R1YWwgcm91dGluZy4N
Cg0KDQo+ID4gICAgV2hlbiBhbGwgYXV0b25vbW91cyBzeXN0ZW1zIGluIHRoZSBJbnRlcm5ldCBh
cmUgVElEUi1hd2FyZSB0aGUNCj4gPiAgICBmaW5hbCByZXN1bHRpcyB0aGF0IGFsbCByb3V0ZXJz
IGhhdmluZyBmdWxsLXJvdXRpbmcgd2lsbCBoYXZlDQo+ID4gICAgdGhlIGN1c3RvbWVyIHByZWZp
eCBib3RoIGluIHRoZSBSSUIgYW5kIHRoZSBUSUIuIFdoZW4gYSBuZXcNCj4gPiAgICBwYWNrZXQg
aXMgc2VudCB0byB0aGUgY3VzdG9tZXIgb25seSB0aGUgZmlyc3QgVElEUi1hd2FyZSByb3V0ZXIN
Cj4gPiAgICB3aWxsIGhhdmUgdG8gbG9vayB1cCB0aGUgVElCK1JJQiB3aGVyZWFzIHRoZSByZXN0
IG9mIHRoZQ0KPiA+ICAgIHRyYW5zaXQgcm91dGVycyB3aWxsIG9ubHkgaGF2ZSB0byBsb29rIHVw
IHRoZSBSSUIuIEluIG90aGVyDQo+ID4gICAgd29yZHMsIHRoZSByb3V0ZXIgcGVyZm9ybWluZyB0
dW5uZWwgaW1wb3NpdGlvbiB3aWxsIHVzZSB0aGUNCj4gPiAgICBUSUIrUklCLCBhbmQgdGhlIG90
aGVycyB3aWxsIHVzZSB0aGUgUklCLg0KPg0KPiBIb3cgZG9lcyB0aGUgdHJhbnNpdCByb3V0ZXIg
a25vdyB0byB3aGljaCB0YWJlbCB0byBsb29rID8gWW91IHNhaWQgYWJvdmUNCj4gdGhhdCB0aGUg
bG9va3VwIGlzIFRJQiAtPiBSSUIgLi4uIEkgZG8gbm90IHNlZSBhIHdheSBmb3IgdGhlIHRyYW5z
aXQNCj4gbm9kZSB0byBleGFtaW5lIHRoZSBkc3QgYW5kIG1ha2UgYSBsb29rdXAgdGFibGUgZGVj
aXNpb24gYmFzZWQgb24gdGhpcy4NCj4NCg0KT25jZSB0aGUgZWRnZSByb3V0ZXIgcGVyZm9ybXMg
dHVubmVsIGltcG9zaXRpb24gdGhlIGZvbGxvd2luZw0Kcm91dGVycyB3aWxsIHJvdXRlIHRvd2Fy
ZHMgdGhlIHR1bm5lbCBkZXN0aW5hdGlvbi4NCg0KDQo+ID4gICAgV2hlbiB0aGVzZSB0d28gQkdQ
IGFubm91bmNlbWVudHMgYXJyaXZlIHRvIHRoZSByb3V0ZXJzIG9mIHRoZQ0KPiA+ICAgIFRJRFIt
YXdhcmUgSVNQMyB0aGV5IHdpbGwgaW5zdGFsbCB0aGUgcHJlZml4IGluIHRoZSBSSUIgYXMgdXN1
YWwsDQo+ID4gICAgYnV0IHRoZXkgd2lsbCBhbHNvIGluc3RhbGwgdGhlIHByZWZpeCBpbiB0aGUg
VElCLiBMYXRlciwgd2hlbg0KPiA+ICAgIG9uZSBvZiB0aGVzZSByb3V0ZXJzIHJlY2VpdmVzIGEg
cGFja2V0IGZvciB0aGUgbXVsdGktaG9tZWQgc2l0ZQ0KPiA+ICAgIGl0IHdpbGwgY2hlY2sgdGhl
IFRJQiBiZWZvcmUgdGhlIFJJQiBhbmQgIGl0IHdpbGwgZmluZA0KPiA+ICAgIHR3byBsb2NhdG9y
cy4NCj4NCj4gV2VsbCBhcyBvZiB0b2RheSBpdCB3aWxsIG5vdCBmaW5kIHR3byBsb2NhdG9ycyBz
aW1wbHkgZHVlIHRvIGZhY3Qgb2YNCj4gYmVzdCBwYXRoIG9ubHkgYWR2ZXJ0aXNlbWVudCBmcm9t
IGVpdGhlciBsb2NhbCBJU1AzIFJSIG9yIHNvbWUgSVB2NCBSUg0KPiBvbiB0aGUgd2F5LiBBbHNv
IHRoaW5rIHRoZXJlIGFyZSBvdGhlciBnb29kIHdheXMgdG8gYWNoaWV2ZSBtdWx0aWhvbWluZw0K
PiBidXQgaW4gZmFjdCBkbyBub3QgYXNrIElTUDIgJiBJU1AxIGZvciBhbnkgY29vcGVyYXRpb24u
IEl0IGNvdWxkIGJlIGp1c3QNCj4gY3VzdG9tZXIgd2hvIGlzIHRoZSBlbmQgcG9pbnQgdmlhIHR3
byAob3IgTikgcGVlcmluZyBJU1BzLg0KPg0KDQpZZXMuIFRoZSBCR1AgYmVzdCBwYXRoIHNlbGVj
dGlvbiBhbGdvcml0aG0gd2lsbCBoYXZlIHRvIGJlDQptb2RpZmllZCBpbiB0aGUgZm9sbG93aW50
IHNlbnNlOiBpZiBhIHJvdXRlciByZWNlaXZlcyB0d28NCmFubm91bmNlbWVudHMgZm9yIHByZWZp
eCBYLCB0aGUgZmlyc3QgYW5ub3VuY2VtZW50IGhhdmluZw0KTG9jYXRvcjEgYW5kIHRoZSBzZWNv
bmQgYW5ub3VuY2VtZW50IGhhdmluZyBMb2NhdG9yMiwgdGhlDQpCR1AgYmVzdCBwYXRoIGFsZ29y
aXRoIHdpbGwgd29yayBhcyB1c3VhbCBCVVQgaXQgd2lsbCBoYXZlDQp0byBhZGQgYm90aCBMb2Nh
dG9yMSBhbmQgTG9jYXRvcjIgdG8gdGhlIGJlc3RwYXRoLg0KDQoNCj4gPiAgICBUbyBhdm9pZCB0
aGF0IG9ubHkgb25lIG9mIHRoZSBsb2NhdG9ycyBhcnJpdmVzIHRvIElTUDMgYmVjYXVzZQ0KPiA+
ICAgIG9mIHRoZSBlZmZlY3Qgb2YgdGhlIEJHUCBiZXN0IHBhdGggc2VsZWN0aW9uIGFsZ29yaXRo
bQ0KPiA+ICAgIHNvbWV3aGVyZSBpbiB0aGUgcGF0aCwgd2Ugd2lsbCBuZWVkIHRvIHNsaWdodGx5
IG1vZGlmeSB0aGlzDQo+ID4gICAgYWxnb3JpdGhtDQo+DQo+IEkgZG8gbm90IHRoaW5rIHRoYXQg
dGhpcyBpcyBwcmFjdGljYWxseSBkb2FibGUgdG8gbW9kaWZ5IEludGVybmV0IGxpa2UNCj4gdGhp
cy4gRXNwZWNpYWxseSB3aGVyZSB0aGVyZSBhcmUgYWx0ZXJuYXRpdmVzIHdoaWNoIGRvIG5vdCBy
ZXF1aXJlIHN1Y2gNCj4gbW9kaWZpY2F0aW9ucyA7KS4NCj4NCg0KSSBkb27CtHQga25vdyBhYm91
dCB0aGUgYWx0ZXJuYXRpdmVzIHlvdSBtZW50aW9uLiBDYW4geW91IHBsZWFzZQ0KcHJvdmlkZSBt
b3JlIGluZm8/LiBUaGUgQkdQIGJlc3QgcGF0aCBhbGdvcml0aG0gd2lsbCB3b3JrIGFzDQp1c3Vh
bC4gV2Ugd2lsbCBvbmx5IG5lZWQgdG8gYXBwZW5kIGJvdGggbG9jYXRvcnMgdG8gdGhlDQphbm5v
dW5jZW1lbnQuIEJvdGggbG9jYXRvcnMgd291bGQgYmUgaW4gdGhlIHNhbWUgTE9DQVRPUiBhdHRy
aWJ1dGUsDQppLmUuIHRoZSBMT0NBVE9SIGF0dHJpYnV0ZSBwZXJtaXRzIHRvIGFubm91bmNlIHNl
dmVyYWwgbG9jYXRvcnMNCmF0IHRoZSBzYW1lIHRpbWUsIGFuZCBoYXZpbmcgZGlmZmVyZW50IHR1
bm5lbGluZyB0ZWNobmlxdWVzDQooR1JFLCBJUC1pbi1JUCwgLi4uKS4NCg0KDQo+ID4gNi4gTG9j
YXRvcnMgb2YgTG9jYXRvcnMgZm9yIGEgSGllcmFyY2hpY2FsIEludGVybmV0OiBUaGUgT25pb24g
TW9kZWwNCj4gPg0KPiAuLi4NCj4gPiAgICBMZXQnc3Mgc3VwcG9zZSBub3cgdGhhdCBJU1AtMTAx
IHN1cHBvcnRzIGhpZXJhcmNoaWNhbCBUSURSDQo+ID4gICAgKEgtVElEUiksIHdoaWNoIG1lYW5z
IHRoYXQgSVNQLTEwMSB3aWxsIGFzc2lnbiBuZXcgbG9jYXRvcnMNCj4gPiAgICB0byB0aGUgbG9j
YXRvciBwcmVmaXggdGhhdCBJU1AxIGFubm91bmNlZCB0byB0aGUgSW50ZXJuZXQuDQo+ID4gICAg
VGhlIExPQ0FUT1IgYXR0cmlidXRlIGZvciB0aGlzIGxvY2F0b3IgcHJlZml4IHdpbGwgbm93DQo+
ID4gICAgY29udGFpbiBhcyB0dW5uZWwgZGVzdGluYXRpb24gYW4gSVAgYWRkcmVzcyBvZiBJU1At
MTAxLCBhbmQNCj4gPiAgICB0aGUgTE9DQVRPUiBhdHRyaWJ1dGUgd2lsbCBtYXJrIHRoaXMgbmV3
IGxvY2F0b3IgYXMgYSBsZXZlbC0yDQo+ID4gICAgbG9jYXRvci4gV2hlbiB0aGlzIEJHUCBhbm5v
dW5jZW1lbnQgYXJyaXZlcyB0byBhIGxldmVsLTIgYXdhcmUNCj4gPiAgICBBUywgaXQgd2lsbCBu
b3QgaW5zdGFsbCB0aGUgbG9jYXRvciBwcmVmaXggaW4gdGhlIFRJQiBhcyB3aXRoDQo+ID4gICAg
YW55IGlkZW50aWZpZXIgbG9jYXRvciBidXQgaXQgd2lsbCBpbnN0YWxsIHRoZSBsb2NhdG9yIHBy
ZWZpeA0KPiA+ICAgIGluIHRoZSBSSUIgYW5kIGl0IHdpbGwgbWFyayBpdCB0byBrbm93IHRoYXQg
YSBsZXZlbC0yIGxvY2F0b3INCj4gPiAgICBpcyBhdmFpbGFibGUgZm9yIGl0LiBUaGlzIGxldmVs
LTIgbG9jYXRvciB3aWxsIGJlIGluc3RhbGxlZCBpbg0KPiA+ICAgIGEgbmV3IHRhYmxlIGNhbGxl
ZCBSSUItMi4gTGF0ZXIsIHdoZW4gSVNQLTEwMSByZWNlaXZlcyB0cmFmZmljDQo+ID4gICAgd2hp
Y2ggaXMgdHVubmVsZWQgd2l0aCB0aGUgbGV2ZWwtMSBsb2NhdG9yIGl0IHdpbGwgcGVyZm9ybQ0K
PiA+ICAgIGVpdGhlciBhIHNlY29uZCB0dW5uZWwgaW1wb3NpdGlvbiB1c2luZyB0aGUNCj4gPiAg
ICBsZXZlbC0yIGxvY2F0b3IgKHRlbGVzY29waW5nKSBvciBldmVuIGl0IGNvdWxkIHN3YXAgdGhl
IGluY29taW5nDQo+ID4gICAgbGV2ZWwtMSB0dW5uZWwgZW5jYXBzdWxhdGlvbiB3aXRoIGEgbmV3
IGxldmVsLTIgdHVubmVsDQo+ID4gICAgZW5jYXBzdWxhdGlvbiAodHVubmVsIHN3YXBwaW5nKS4N
Cj4NCj4gSSBhZ3JlZSB3aXRoIHRoZSBOIHN0YWdlIG9mIGVuY2FwLiBCdXQgYWdhaW4gYXMgaW4g
dGhlIG9yaWdpbmFsIGNhc2UgSQ0KPiBkbyBub3QgdGhpbmsgdGhhdCB1c2luZyBsb2NhdG9ycyBp
cyBuZWNlc3NhcnkuIEp1c3Qgcm91dGluZyB0byBBUyBJUA0KPiBhZGRyZXNzZXMgc2VlbXMgbW9y
ZSB0aGVuIHN1ZmZpY2llbnQgeWV0IGF1dG9tYXRpYyBhbmQgZG9lcyBub3QgcmVxdWlyZQ0KPiBh
bnkgbmV3IHNpZ25hbGluZy4NCj4NCg0KRG9uJ3QgeW91IHRoaW5rIGl0IGlzIGJldHRlciB0byBo
YXZlIHNldmVyYWwgQVMgSVBzIGluc3RlYWQgb2YganVzdCBvbmU/Lg0KDQoNCj4gVGh4LA0KPiBS
Lg0KPg0KPiBQUy4gTW9yZSBjb21tZW50cyB3aGVuL2lmIHdlIGFncmVlIG9uIHRoZSBhYm92ZSA7
KS4gQXMgaXQgc2VlbXMgdGhhdCB3ZQ0KPiBhcmUgYm90aCBjdXJyZW50bHkgbG9jYXRlZCBpbiBF
dXJvcGUgcGVyaGFwcyBhIGRpcmVjdCBtZWV0aW5nIHdvdWxkIGJlDQo+IGJldHRlciB0byBoYXZl
IGEgZm9jdXNlZCBkYXkgb24gdGhpcy4=




--===============1740932478==
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

--===============1740932478==--



From idr-bounces@ietf.org Fri Nov 10 06:31:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GiUX8-0008M6-GR; Fri, 10 Nov 2006 06:26:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GiUX7-0008M1-Bn
	for idr@ietf.org; Fri, 10 Nov 2006 06:26:53 -0500
Received: from giss7.seg-social.es ([194.179.55.129] helo=smtp.seg-social.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiUX5-0001EG-Qy
	for idr@ietf.org; Fri, 10 Nov 2006 06:26:53 -0500
Received: from gwinternet.correo.portal.ss ([10.99.1.89]) by
	smtp.seg-social.es (Netscape Messaging Server 4.15) with ESMTP
	id J8IIGG01.82N for <idr@ietf.org>; Fri, 10 Nov 2006 12:26:40 +0100 
From: JUAN-JOSE.ADAN@giss.seg-social.es
X-Priority: 1 (High)
Subject: Rm: [Idr] Draft on "Tunneled Inter-domain Routing"
To: idr@ietf.org
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OF48A9BC53.4F9624F7-ONC1257222.003C705E-C1257222.003E3652@tgss.seg-social.es>
Date: Fri, 10 Nov 2006 12:18:24 +0100
X-MIMETrack: Serialize by Router on GWINTERNET/SRV/SEG-SOCIAL(Release
	6.5.5|November 30, 2005) at 10/11/2006 12:26:39
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
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


Robert,

Thank you very much for your comments.
You can find my comments below.

Regards,
Juanjo


----- Remitido por JUAN JOSE ADAN LUENGO/GISS/SEG-SOCIAL con fecha
10/11/2006 12:01 -----

Robert Raszuk <raszuk@cisco.com> escribi=F3 el 08/11/2006 14:48:08:

> Juan,
>
> Excellent doc !!!! I must say that I with few other folks from Cisco =
are
> also actively working on a very similar idea for about last 8 months.=
 I
> am not sure if you would like to continue the individual work or woul=
d
> be willing for a joint collaboration.
>

The draft I sent to the IDR WG is based on a paper I tried to publish
in the journal of big networking company based on San Jose (California)=
,
without success. Later, I rewrote the paper for the Global Internet
Symposium of INFOCOM-2006, but it was rejected. Therefore this is my
third attempt to get it. However I must say I am new. This is my
first research paper and I don't know if it could published as an
individual submission, after it is pulished by all of your comments
of course.

The draft is a general overview of TIDR, and I left for a second
draft the specifications for the LOCATOR attribute and the
modifications for the BGP bestpath algorithm. For this second draft,
if my proposal is interesting, I will be very glad to write
it with you.

I am also preparing a third draft on "The use of TIDR with IGPs".

>
> While reading your draft I found a few opportunities which may even m=
ore
> relax the need for a separate locator advertisement. Also AS numbers =
are
> now 4 bytes not two :). I will try to spend some time this week to
> comment on it.
>
> Cheers,
> R.
>
>
> > Hi,
> >
> > I sent a draft in October on "Tunneled Inter-domain Routing" (TIDR)=
:
> > draft-adan-idr-tidr-00.txt.
> >
> > TIDR is a proposal to modify the way in which traffic is routed to
> > "stub networks". The meaning of "stub network" is not the same for
> > inter-domain routing than for intra-domain routing.
> >
> > For BGP a "stub network" is simply a leaf autonomous system, whethe=
r
> > it be single- or multi-homed. ISPs would add a new transitive BGP
> > attribute called LOCATOR to a client prefix so as to specify how ot=
her
> > autonomous systems can send tunneled traffic for that client prefix=
.
> > The tunnel type is left open in TIDR (we can use several types), bu=
t
> > the best way to understand TIDR is to think on multipoint GRE tunne=
ls.
> >
> > This LOCATOR attribute will eventually allow us to move client pref=
ixes
> > from the global RIB to a new table called "Tunnel Information Base"=

(TIB).
> > And this move provides many benefits, e.g. client prefixes
instabilities
> > will affect only the TIB, not the RIB.
> >
> > ISP prefixes used for TIDR tunnels endpoints will be stored in the =
RIB
> > and they will act as true locators for the client prefixes. And cli=
ent
> > prefixes will be stored in the TIB and will be used as identifiers.=

> >
> > When routing a packet to a leaf AS, the TIB will be search to perfo=
rm
> > locator imposition, and the RIB will be used for actual routing. Th=
e
> > ISP that added the LOCATOR attribute will de-tunnel the traffic bef=
ore
> > delivering it to its cliet.
> >
> >
> > This is the abstract:
> >
> >    In this paper we propose a new hierarchical method to enhance
> >    the current routing and forwarding paradigm for the Internet
> >    called Tunneled Inter-Domain Routing (TIDR). We will present the=

> >    way in which TIDR permits to establish tunnels to the edge of
> >    the network, and how they will be used to forward traffic to
> >    stub networks. These tunnels will be explicitly signaled by
> >    using a new transitive BGP attribute called LOCATOR. This new
> >    routing and forwarding paradigm provides, among others, the
> >    following benefits: global routing table reduction, inter-domain=

> >    routing infrastructure protection, improved multi-homing of edge=

> >    networks, numerous forwarding decisions for a particular address=

> >    prefix, it stops the AS number consumption, and it can be
> >    smoothly deployed.
> >
> >
> > Any comments will be appreciated.
> >
> > Juanjo
> >
> >
> >
> > _______________________________________________
> > 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 Nov 10 06:31:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GiUXC-0008MT-WA; Fri, 10 Nov 2006 06:26:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GiUXA-0008MO-Vn
	for idr@ietf.org; Fri, 10 Nov 2006 06:26:56 -0500
Received: from giss7.seg-social.es ([194.179.55.129] helo=smtp.seg-social.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiUX9-0001Ef-T6
	for idr@ietf.org; Fri, 10 Nov 2006 06:26:56 -0500
Received: from gwinternet.correo.portal.ss ([10.99.1.89]) by
	smtp.seg-social.es (Netscape Messaging Server 4.15) with ESMTP
	id J8IIGO01.H2O for <idr@ietf.org>; Fri, 10 Nov 2006 12:26:48 +0100 
From: JUAN-JOSE.ADAN@giss.seg-social.es
X-Priority: 1 (High)
Subject: Rm: [Idr] Draft on "Tunneled Inter-domain Routing"
To: idr@ietf.org
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OFD49734CA.999280B4-ONC1257222.0034EA45-C1257222.003EBC2D@tgss.seg-social.es>
Date: Fri, 10 Nov 2006 12:24:07 +0100
X-MIMETrack: Serialize by Router on GWINTERNET/SRV/SEG-SOCIAL(Release
	6.5.5|November 30, 2005) at 10/11/2006 12:26:47
MIME-Version: 1.0
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 4515df9441674711565101d9d5c4f63f
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="===============1740932478=="
Errors-To: idr-bounces@ietf.org

--===============1740932478==
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: base64

DQpSb2JlcnQsDQoNCkkgaGF2ZSBpbmNsdWRlZCBteSBjb21tZW50cyB0byB5b3VyIG9ic2VydmF0
aW9ucy4gSSBob3BlDQp0aGV5IHB1dCBtb3JlIGxpZ2h0IG9uIG15IHByb3Bvc2FsLg0KDQpJIHdp
bGwgYmUgb3V0IGZvciBhIHdlZWsuIEkgd2lsbCBjaGVjayBsYXRlciBhYm91dCB0aGUNCnBvc3Np
YmlsaXR5IG9mIGhhdmluZyBhIG1lZXRpbmcgc29tZXdoZXJlIGluIEV1cm9wZS4NCkkgd2lsbCBo
YXZlIHRvIGNvbnZpbmNlIG15IGJvc3MgZmlyc3QgOi0pLg0KDQpSZWdhcmRzLA0KSnVhbmpvDQoN
Cg0KLS0tLS0gUmVtaXRpZG8gcG9yIEpVQU4gSk9TRSBBREFOIExVRU5HTy9HSVNTL1NFRy1TT0NJ
QUwgY29uIGZlY2hhDQoxMC8xMS8yMDA2IDEwOjM5IC0tLS0tDQoNClJvYmVydCBSYXN6dWsgPHJh
c3p1a0BjaXNjby5jb20+IGVzY3JpYmnDsyBlbCAwOS8xMS8yMDA2IDAwOjU2OjMzOg0KDQo+IEhp
IEp1YW4sDQo+DQo+IEJlbG93IGFyZSBteSBtb3JlIGRldGFpbGVkIGNvbW1lbnRzLiBZb3UgaGF2
ZSBhIGNob2ljZSB0byBpZ25vcmUgdGhlbSBvcg0KPiBhdHRlbXB0IHRvIHdvcmsgdG9nZXRoZXIg
dG8gc2ltcGxpZnkgdGhlIGN1cnJlbnQgcHJvcG9zYWwgdG8gYmUgbXVjaA0KPiBtb3JlIGVhc3kg
dG8gZGVwbG95IGJvdGggZnJvbSB2ZW5kb3IgYXMgd2VsbCBhcyBjdXN0b21lcnMgcG9pbnQgb2Yg
dmlldy4NCj4NCj4gQ29tbWVudHM6DQo+IC0tLS0tLS0tLQ0KPg0KPiA+IEkgc2VudCBhIGRyYWZ0
IGluIE9jdG9iZXIgb24gIlR1bm5lbGVkIEludGVyLWRvbWFpbiBSb3V0aW5nIiAoVElEUik6DQo+
ID4gZHJhZnQtYWRhbi1pZHItdGlkci0wMC50eHQuDQo+DQo+ID4gMS4gSW50cm9kdWN0aW9uDQo+
ID4NCj4gPiAgICBSb3V0aW5nIHByb3RvY29scyBpbnN0YWxsIGFsbCBzdWJuZXQgcHJlZml4ZXMg
aW4gdGhlIHJvdXRpbmcgdGFibGUNCj4gPiAgICBpbiB0aGUgc2FtZSBtYW5uZXIsIHdpdGhvdXQg
dGFraW5nIGludG8gY29uc2lkZXJhdGlvbiB0aGUgcGxhY2UNCj4gPiAgICB3aGVyZSB0aGVzZSBz
dWJuZXRzIHJlc2lkZSB3aXRoaW4gdGhlIG5ldHdvcmsuIEJlY2F1c2Ugb2YgdGhpcyBmYWN0LA0K
PiA+ICAgIGV2ZXJ5IHRpbWUgdGhlcmUgaXMgYSBjaGFuZ2UgaW4gYSBzdHViIG5ldHdvcmsgdGhl
IFJJQiBpcyBhbHdheXMNCj4gPiAgICByZWJ1aWx0IGFnYWluLA0KPg0KPiBXZWxsIG1vc3Qgb2Yg
dGhlIG1vZGVybiBpbXBsZW1lbnRhdGlvbnMgZG8gbm90ICJyZWJ1aWxkIiBSSUIgYWdhaW4gb24N
Cj4gZGVsZXRlL3VwZGF0ZS9tb2RpZnkgbWVzc2FnZS4gSW5jcmVtZW50YWwgdXBkYXRpbmcgb2Yg
Ym90aCBSSUIgJiBGSUIgYXJlDQo+IHdlbGwga25vd24gdGVjaG5pY3MuDQoNCldoZW4gSSBzYXkg
InJlYnVpbGQiIEkgZG9uwrR0IG1lYW4gdG8gcmVidWlsZCB0aGUgUklCIF9mcm9tIHNjcmF0Y2hf
Lg0KDQo+DQo+ID4gdGh1cyBwb3NzaWJseSBjYXVzaW5nIGFuIGluc3RhYmlsaXR5IHRvIHRoZSBy
b3V0aW5nDQo+ID4gICAgc3lzdGVtOg0KPiA+DQo+ID4gICAgMSkgSW4gdGhlIEludGVybmV0LCBw
cmVmaXhlcyBvZiBhIG11bHRpLWhvbWVkIG5vbi10cmFuc2l0IGRvbWFpbiwNCj4gPiAgICAgICBp
LmUuIGFuIGF1dG9ub21vdXMgc3lzdGVtIG5vdCBwYXJ0aWNpcGF0aW5nIGluIHRydWUgaW50ZXIt
ZG9tYWluDQo+ID4gICAgICAgcm91dGluZywgYXJlIGdpdmVuIHRoZSBzYW1lIHRyZWF0bWVudCBh
cyB0aGUgcHJlZml4ZXMgb2YgYQ0KdHJhbnNpdA0KPiA+ICAgICAgIGRvbWFpbi4gSXJyZXNwZWN0
aXZlIG9mIHRoZSB0eXBlIG9mIGRvbWFpbiBhbGwgcHJlZml4ZXMgYXJlDQo+ID4gICAgICAgaW5z
dGFsbGVkIGJ5IEJHUCBbMV0gaW4gdGhlIHNhbWUgZ2xvYmFsIHJvdXRpbmcgdGFibGUsIGFsc28g
a25vd24NCj4gPiAgICAgICBhcyB0aGUgZ2xvYmFsIHJvdXRpbmcgaW5mb3JtYXRpb24gYmFzZSAo
UklCKS4NCj4gPg0KPiA+ICAgIDIpIFdpdGhpbiBhIHNpbmdsZSBkb21haW4sIHN0dWIgbmV0d29y
ayBwcmVmaXhlcyBhcmUgaW5zdGFsbGVkIGJ5DQo+ID4gICAgICAgaW50ZXJpb3IgZ2F0ZXdheSBw
cm90b2NvbHMgKElHUHMpLCBsaWtlIE9TUEYgWzJdIG9yIElTLUlTIFszXSwNCj4gPiAgICAgICBp
biB0aGUgc2FtZSByb3V0aW5nIHRhYmxlIChSSUIpIHdoZXJlIHRoZXkgaW5zdGFsbCB0cmFuc2l0
DQo+ID4gICAgICAgbmV0d29ya3MsIHdoZXRoZXIgc3R1YiBuZXR3b3JrIHByZWZpeGVzIGFyZSBp
bnN0YWxsZWQgYXMgYQ0KPiA+ICAgICAgIHJlc3VsdCBvZiBhIGZ1bGwgU1BGIHJ1biBvciBhIHBh
cnRpYWwgU1BGIHJ1bi4NCj4NCj4gV2VsbCB3aXRoIEJHUCB5b3UgYXJlIGNvcnJlY3QuIFdpdGgg
SUdQcyBub3Qgc28gbXVjaCA7KSBUaGUgZ2VuZXJhbA0KPiBwcmFjdGljZSBpcyB0byBpbnN0YWxs
IGp1c3QgYSBzdW1tYXJ5IHJvdXRlIHRvIGEgc3R1YiBhcmVhLiBUaGUgaXNzdWUNCj4gaGVyZSBp
cyB0aGF0IHdpdGggTVBMUyBhbmQgTVBMUyBhcHBsaWNhdGlvbnMgdGhlcmUgaXMgcmVxdWlyZW1l
bnQgZm9yDQo+IC8zMnMgdGhhdCdzIHdoeSB0aG9zZSBhcmUgbGVha2VkIGV2ZXJ5d2hlcmUgaW4g
bWFueSBNUExTIG5ldHdvcmtzLiBCdXQNCj4gdGhpcyBpcyBtb3JlIG9mIGV4Y2VwdGlvbiB0aGVu
IGEgcnVsZSBpbiBnZW5lcmFsLg0KDQpXaGVuIEkgc2F5ICJzdHViIG5ldHdvcmsiIEkgZG9uJ3Qg
bWVhbiAic3R1YiBhcmVhIi4gSWYgd2UgaGF2ZQ0KYSBiaWcgcm91dGluZyBkb21haW4gY29uZmln
dXJlZCBhcyBhIHNpbmdsZSBhcmVhLCBPU1BGIG9yIElTLUlTLA0KdGhlIG51bWJlciBvZiAic3R1
YiBuZXR3b3JrcyIgKHRob3NlIGluIHdoaWNoIHRoZSBJR1AgZG9lc27CtHQNCmVzdGFibGlzaCBh
bnkgYWRqYWNlbmNpZXMpIG1heSBiZSBfdmVyeSBiaWdfLCB0aHVzIG1ha2luZyB0aGUgUklCDQph
bmQgb2J2aW91c2x5IHRoZSBGSUIgdmVyeSBiaWcgZXZlbiBmb3IgYSBzaW5nbGUgYXJlYS4NCg0K
DQo+DQo+ID4gICAgVHVubmVsZWQgSW50ZXItRG9tYWluIFJvdXRpbmcgKFRJRFIpIG1vZGlmaWVz
IGJvdGggdGhlIHVzdWFsIHJvdXRpbmcNCj4gPiAgICBhbmQgZm9yd2FyZGluZyBwcm9jZXNzZXMg
Y3VycmVudGx5IHVzZWQgaW4gSVAgbmV0d29ya3MgYnkgdHJlYXRpbmcNCj4gPiAgICBzdHViIG5l
dHdvcmtzIGluIGEgZGlmZmVyZW50IHdheSB0aGFuIHRyYW5zaXQgbmV0d29ya3MuIFRoaXMgc3Bl
Y2lhbA0KPiA+ICAgIHRyZWF0bWVudCBpcyB0d29mb2xkOiBzdHViIG5ldHdvcmsgcHJlZml4ZXMg
d2lsbCBub3QgYmUgaW5zdGFsbGVkIGluDQo+ID4gICAgdGhlIFJJQjsgYW5kIHRyYWZmaWMgZm9y
IHN0dWIgbmV0d29ya3Mgd2lsbCBiZSBzZW50IG92ZXIgdHVubmVscw0KPiA+ICAgIGVzdGFibGlz
aGVkIHRvIHRoZSBlZGdlIG9mIHRoZSBuZXR3b3JrLiBXZSB3aWxsIHNob3cgaG93IHRoaXMNCnNw
ZWNpYWwNCj4gPiAgICB0cmVhdG1lbnQgb2Ygc3R1YiBuZXR3b3JrIHByZWZpeGVzIGlzIG5vdGhp
bmcgZWxzZSBidXQgYW4gZWFzeQ0KPiA+ICAgIHNvbHV0aW9uIHRvIHRoZSBpZGVudGlmaWVyLWxv
Y2F0aW9uIHNwbGl0IHByb2JsZW0sIGFuZCBzb21lIG9mIHRoZQ0KPiA+ICAgIG1hbnkgYmVuZWZp
dHMgdGhhdCBzdWNoIGEgc3BsaXQgcHJvdmlkZXMgaW4gdGVybXMgb2Ygc2NhbGFiaWxpdHksDQo+
ID4gICAgc3RhYmlsaXR5IGFuZCB0aGUgaW50cm9kdWN0aW9uIG9mIG5ldyByb3V0aW5nIGZlYXR1
cmVzLg0KPg0KPiBXZWxsIGxldCdzIGZvY3VzIG9uIEJHUCBwYXJ0IG9ubHkuIFlvdSBoYXZlIHRv
IHJlYWxpemUgYW5kIG9ic2VydmUgdGhhdA0KPiB0byBnZXQgbW9zdCBvZiB0aGUgYmVuZWZpdHMg
eW91IGFyZSB0YXJnZXRpbmcgdGhpcyB3b3JrIHRvIHN1Y2ggYSBzcGxpdA0KPiBpcyBub3QgYSBt
dXN0LiBBcyBsb25nIGFzIHlvdSBjYW4gaWRlbnRpZnkgaW4gdGhlIGN1cnJlbnQgc3R1Yi90cmFu
c2l0DQo+IG5ldHdvcmtzIGFuIGVsZW1lbnQgd2hpY2ggY2FuIGJlIHVzZWQgYXMgdGhlIHR1bm5l
bCBlbmRwb2ludCB3ZSBhcmUNCj4gZmluZS4gVGhlcmUgaXMgbm8gbmVlZCBmb3IgaW50cm9kdWN0
aW9uIG9mIG5ldyBMb2NhdG9yIGF0dHJpYnV0ZS4gV2UgKEkNCj4gJiBTdGVmYW5vIFByZXZpZGkp
IGhhdmUgcHJvcG9zZWQganVzdCB0aGUgdXNlIG9mIEFTIElQIGFkZHJlc3MgYXMgdGhlDQo+IGF1
dG9tYXRlZCBsb2NhdG9yLiBPZiBjb3Vyc2Uga2VlcGluZyBpbiBtaW5kIHRoYXQgZXZlbiB0aGUg
bWFwcGluZyBjb3VsZA0KPiBiZSBhdXRvbWF0ZWQuIE1vc3Qgb2YgdGhlIGdhaW5zIGFyZSB0aGUg
c2FtZSB3aGlsZSBpbXBsZW1lbnRhdGlvbiBhbmQNCj4gZGVwbG95bWVudCByZWFsaXN0aWMuIEkg
ZG8gbm90IHRoaW5rIHRoYXQgd2Ugd2lsbCBnbyBmYXIgaWYgdGhlIGFzayBmb3INCj4gaW1wbGVt
ZW50YXRpb25zIHRvIHN1cHBvcnQgVElCLiBTZWUgdGhlIGJvdHRvbSBsaW5lIGlzIHRoYXQgZXNw
ZWNpYWxseQ0KPiBpbiB0cmFuc2l0IG5ldHdvcmtzIGhhdmluZyBiaWcgQkdQIFJJQiBvbiB0aGUg
UlAgaXMgbm8gaXNzdWUuIFdoYXQgaXMNCj4gdGhlIGJpZ2dlc3Qgc2F2aW5nIGlzIHRvIGhhdmUg
YSBjb250YWluZWQgRklCLiBUaGlzIGlzIHdoeSBJIHRoaW5rIHRoYXQNCj4gdGhlcmUgaXMgYSBs
b3Qgb2YgZ2FpbiB3aXRob3V0IG11Y2ggaW1wbGVtZW50YXRpb24gY2hhbmdlcyB0byBiZQ0KcHJv
cG9zZWQuDQo+DQoNCkkgdGhpbmsgdGhlIGxvY2F0b3IvSUQgc3BsaXQgaGFzIGFwcGVhcmVkIG1h
bnkgdGltZXMgaW4NCm1hbnkgV0dzIGFzIHRoZSBwb3NzaWJsZSBzb2x1dGlvbiB0byBtYW55IHBy
b2JsZW1zIG9mIHRoZQ0KY3VycmVudCByb3V0aW5nIHBhcmFkaWdtLg0KDQo+ID4NCj4gPiAyLiBJ
ZGVudGlmaWVycyBhbmQgTG9jYXRvcnMgaW4gVElEUg0KPiA+DQo+ID4gICAgSXQgaXMgd2VsbCBr
bm93biB0aGF0IElQIGFkZHJlc3NlcyBhcmUgc2VtYW50aWNhbGx5IG92ZXJsb2FkZWQNCmJlY2F1
c2UNCj4gPiAgICB0aGV5IGNhcnJ5IGluZm9ybWF0aW9uIG9uIGJvdGggdGhlIGxvY2F0aW9uIGFu
ZCB0aGUgaWRlbnRpdHkgb2ZhDQpkZXZpY2UuDQo+ID4gICAgVGhlIG5lZWQgdG8gc3BsaXQgdGhl
c2UgdHdvIHJvbGVzIGhhcyBiZWVuIGRpc2N1c3NlZCBtYW55IHRpbWVzIGluDQptYW55DQo+ID4g
ICAgZGlmZmVyZW50IGZvcnVtcyB3aXRoIHJlZ2FyZCB0byAoYSkgdGhlIHBvc3NpYmxlIGludHJv
ZHVjdGlvbiBvZiBhDQpuZXcNCj4gPiAgICBoaWVyYXJjaGljYWwgcm91dGluZyBwYXJhZGlnbSBp
biB0aGUgSW50ZXJuZXQgWzRdIFs1XSBbNl0sIChiKSBhcyBhDQp3YXkNCj4gPiAgICB0byBwcm92
aWRlIHNjYWxhYmxlIHNpdGUgbXVsdGktaG9taW5nIFs3XSwgb3IgKGMpIHRoZSBpbnRyb2R1Y3Rp
b24NCm9mIGENCj4gPiAgICBuZXcgYWRkcmVzc2luZyBhcmNoaXRlY3R1cmUgWzhdLCBhbW9uZyBv
dGhlciBiZW5lZml0cy4NCj4NCj4gVmVyeSB0cnVlLg0KPg0KPiA+ICAgIFNvbWUgaGF2ZSBwb2lu
dGVkIG91dCB0aGF0IE5BVCBpcyB0aGUgZmVhdHVyZSB0aGF0IGZpbmFsbHkgYnJlYWtzDQp0aGUN
Cj4gPiAgICBzZW1hbnRpYyBvdmVybG9hZCBvZiB0aGUgSVAgYWRkcmVzcyBhcyBib3RoIGEgbG9j
YXRvciBhbmQgYSBnbG9iYWwNCj4gPiAgICBpZGVudGlmaWVyIFs5XSBidXQgd2hhdCBOQVQgcmVh
bGx5IGRvZXMgaXMgdG8gdHJhbnNsYXRlIGdsb2JhbA0KPiA+ICAgIGlkZW50aWZpZXJzIGludG8g
YW5vdGhlciBzZXQgb2YgaWRlbnRpZmllcnMsIG5hbWVseSBwcml2YXRlDQo+ID4gICAgaWRlbnRp
ZmllcnMsIHdoaWNoIGlzIHByZWNpc2VseSB0aGUgcmVhc29uIHdoeSB0aGUgZW5kLXRvLWVuZA0K
cHJpbmNpcGxlDQo+ID4gICAgaXMgYnJva2VuIGJ5IE5BVC4gVElEUiBjbGVhcmx5IGRpZmZlcmVu
dGlhdGVzIHRoZSB1c2Ugb2YgbG9jYXRvcnMNCmFuZA0KPiA+ICAgIGlkZW50aWZpZXJzIGFuZCBk
b2VzIG5vdCBpbXBlZGUgdGhlIHVzZSBvZiBlaXRoZXIgaWRlbnRpZmllcnMgb3IgbmV3DQo+ID4g
ICAgbWVjaGFuaXNtcyBmb3IgZW5kcG9pbnQgaWRlbnRpZmljYXRpb24gd2l0aGluIHRoZSBhcHBs
aWNhdGlvbnMuDQo+DQo+IEkgd2FzIG5ldmVyIGtlZW4gb24gdGhlIE5BVCBhcHByb2FjaCB0byBz
Y2FsZSB0aGUgbmV0IDspLg0KPg0KPiA+IDMuIFR1bm5lbGVkIEludGVyLWRvbWFpbiBSb3V0aW5n
DQo+ID4NCj4gPiAgICBEbyB3ZSByZWFsbHkgbmVlZCBzdHViIG5ldHdvcmtzIHByZWZpeGVzIGZv
ciBhY3R1YWwgSVAgcm91dGluZz8uDQpUSURSDQo+ID4gICAgcGVybWl0cyB0byBzZW5kIHRyYWZm
aWMgZm9yIHN0dWIgbmV0d29ya3Mgb3ZlciB0dW5uZWxzIGVzdGFibGlzaGVkDQp0bw0KPiA+ICAg
IHRoZSBlZGdlIG9mIHRoZSBuZXR3b3JrLiBCdXQsIHdoZXJlIGlzIHRoZSBlZGdlIG9mIGEgbmV0
d29yaz8uIEluDQpUSURSLA0KPiA+ICAgIHRoZSBlZGdlIG9mIGEgbmV0d29yayB3aWxsIGJlIHRo
ZSBwbGFjZSB3aGVyZSBzdHViIG5ldHdvcmtzDQphcmVhdHRhY2hlZC4NCj4gPiAgICBBbmQgdGhl
IGV4YWN0IG1lYW5pbmcgb2YgInN0dWIgbmV0d29yayIgd2lsbCBiZSByZWxhdGl2ZSB0byB0aGUN
Cj4gPiAgICBlbnZpcm9ubWVudCB3ZSBhcmUgYW5hbHl6aW5nOiB0aGUgSW50ZXJuZXQgb3IgYW4g
ZW50ZXJwcmlzZSBkb21haW4uDQo+ID4NCj4gPiAgICBUSURSIHByb3Bvc2VzIGEgbmV3IG1ldGhv
ZCB0aGF0IGN1cnJlbnQgcm91dGluZyBwcm90b2NvbHMgd2lsbCB1c2UNCnRvDQo+ID4gICAgbWFu
YWdlIHN0dWIgbmV0d29ya3MuIEluIFRJRFIgc3R1YiBuZXR3b3JrcyB3aWxsIG5vdCBiZSBpbnN0
YWxsZWQgaW4NCnRoZQ0KPiA+ICAgIFJJQiwgYXMgdXN1YWwsIGJ1dCBpbiBhIG5ldyB0YWJsZSBj
YWxsZWQgVHVubmVsIEluZm9ybWF0aW9uIEJhc2UNCihUSUIpLg0KPg0KPiBTZWUgYWJvdmUgY29t
bWVudC4NCj4NCj4gPiAgICBBZnRlcndhcmRzLCB3aGVuIHJvdXRpbmcgYSBwYWNrZXQgdG8gdGhl
IGRlc3RpbmF0aW9uIHByZWZpeCwgdGhlIFRJQg0Kd2lsbA0KPiA+ICAgIGJlIHNlYXJjaGVkIGZp
cnN0IHRvIHBlcmZvcm0gdHVubmVsIGltcG9zaXRpb24sIGFuZCBzZWNvbmRseSB0aGUgUklCDQpm
b3INCj4gPiAgICBhY3R1YWwgcm91dGluZy4NCj4NCj4gSWYgVElCIGhhcyB0byBiZSBzZWFyY2hl
ZCB0aGVyZSBpcyBubyBuZWVkIGZvciBzcGxpdC4gVG8gZG8gaXQgYXQgbGluZQ0KPiByYXRlIGl0
IGhhcyB0byBiZSBkb25lIGluIGhhcmR3YXJlLiBCdHcgLSBKdXN0IEZZSSBoYXJkd2FyZSBhbHJl
YWR5IGRvZXMNCj4gcmVjdXJzaW9uIGVhc2lseSBvbiB0aGUgc2FtZSB0YWJsZXMgOikuDQo+DQoN
CldoZW4gSSBzYXkgd2UgbmVlZCBhIG5ldyB0YWJsZSwgdGhlIFRJQiwgSSBhbSBub3QgcHJlY2x1
ZGluZw0KdGhlIGltcGxlbWVudGF0aW9uIG9mIHRoZSBUSUIgaW4gYSBzcGVjaWZpYyBtYW5uZXIu
IEluIGZhY3QNCml0IGNvdWxkIGJlIGluY2x1ZGVkIHdpdGhpbiB0aGUgRklCLiBUaGUgcHJvYmxl
bSBhcHBlYXJzIGlmDQp0aGUgbnVtYmVyIG9mIHR1bm5lbHMgaW4gdGhlIFRJQiBpcyB0b28gYmln
LiBCdXQgZG9uwrR0IGZvcmdldA0KdGhhdCB0aGUgVElCIGlzIG5vdCBuZWNlc3Nhcnkgb24gcHVy
ZSB0cmFuc2l0IHJvdXRlcnMgYnV0DQpvbmx5IG9mIGVkZ2Ugcm91dGVycywgdGhvc2UgZmFjaW5n
IGNsaWVudHMuDQoNClRoZSBpZGVhIG9mIGhhdmluZyBhbiBJUCBhZGRyZXNzIGZvciBhbiBBUyBp
cyBzb21ldGhpbmcgdGhhdA0KSSBhbHNvIGNvbnNpZGVyZWQgYnV0IEkgdGhpbmsgaXQgaXMgbXVj
aCBtb3JlIGludGVyZXN0aW5nIHRvDQpoYXZlIGEgcHJlZml4IHNvIHRoYXQgd2UgY291bGQgZXZl
biBzcGVjaWZ5IGEgc3BlY2lmaWMgZW50cnkNCnBvaW50IGluIHRoZSBBUyBwb3IgdHJhZmZpYyBk
aXJlY3RlZCB0byBhIHNwZWNpZmljICJpZGVudGlmaWVyDQpwcmVmaXgiLiBBbmQgYSBzcGVjaWZp
YyBsb2NhdG9yIGNvdWxkIGJlIGNvbmZpZ3VyZWQgYXMgYW4gYW55Y2FzdA0KSVAgYWRkcmVzcyBz
byB0aGF0IGluIGNhc2Ugb2YgYSBwcm9ibGVtIGluIGFuIGVudHJ5IHBvaW50LCB0aGUNCnR1bm5l
bGVkIHRyYWZmaWMgY291bGQgYmUgZGVsaXZlcmVkIHRocm91Z2ggYW5vdGhlciBlbnRyeSBwb2lu
dC4NCg0KPg0KPiA+ICAgIEFmdGVyIHRoZSBlZGdlIHJvdXRlciBwZXJmb3JtcyB0dW5uZWwgaW1w
b3NpdGlvbiwgYWxsDQo+ID4gICAgcm91dGVycyBpbiB0aGUgbWlkZGxlIHdpbGwgcm91dGUgdGhp
cyBwYWNrZXQgdW50aWwgdGhlIHJvdXRlciBiZWluZw0KdGhlDQo+ID4gICAgdGFpbC1lbmQgb2Yg
dGhlIHR1bm5lbC4NCj4gPg0KPiA+ICAgIEFsbCB3ZSBuZWVkIGlzIHRvIGZpbmQgYSB3YXkgZm9y
IGEgcm91dGVyIHRvIHRlbGwgaXQgaXMgYWJsZSB0bw0KcmVjZWl2ZQ0KPiA+ICAgIHR1bm5lbGVk
IHRyYWZmaWMgZm9yIGEgZ2l2ZW4gcHJlZml4LiBGb3IgdGhhdCBwdXJwb3NlIHdlIHdpbGwNCmFu
YWx5emUNCj4gPiAgICBjdXJyZW50IHJvdXRpbmcgcHJvdG9jb2xzIHRvIGZpbmQgb3V0IHdoYXQg
aW5mb3JtYXRpb24gY2FuIGJlIHVzZWQNCmFzIGENCj4gPiAgICBsb2NhdG9yIGZvciBhIHNwZWNp
ZmljIHN0dWIgbmV0d29yay4gT25jZSB3ZSBmaW5kIGEgcG9zc2libGUgbG9jYXRvcg0KdGhlbg0K
PiA+ICAgIHdlIHdpbGwgYmUgYWJsZSB0byBzZW5kIHR1bm5lbGVkIHRyYWZmaWMgZm9yIHRoYXQg
c3R1YiBuZXR3b3JrLA0KcHJvdmlkZWQNCj4gPiAgICB0aGF0IGJvdGggdGhlIHJvdXRlciBwZXJm
b3JtaW5nIHR1bm5lbCBpbXBvc2l0aW9uIGFuZCB0aGUgcm91dGVyDQpyZWNlaXZpbmcNCj4gPiAg
ICB0aGUgdHVubmVsZWQgcGFja2V0IGFyZSBUSURSLWF3YXJlLiBUaGVyZWZvcmUsIHRoZSByZWNl
aXZpbmcgcm91dGVyLA0KaW4NCj4gPiAgICBhZGRpdGlvbiB0byB0aGUgSVAgYWRkcmVzcyBvZiB0
aGUgdHVubmVsIGRlc3RpbmF0aW9uIChsb2NhdG9yKSx3aWxsDQpoYXZlDQo+ID4gICAgdG8gdGVs
bCB0aGUgdHlwZXMgb2YgZW5jYXBzdWxhdGlvbnMgaXQgc3VwcG9ydHMgZm9yIGEgcGFydGljdWxh
cg0KcHJlZml4LA0KPiA+ICAgIGFuZCB0aGUgcm91dGVyIHBlcmZvcm1pbmcgdHVubmVsIGltcG9z
aXRpb24gd2lsbCBoYXZlIHRvIHN1cHBvcnQNCnRoYXQNCj4gPiAgICBzcGVjaWZpYyBlbmNhcHN1
bGF0aW9uIG1ldGhvZCwgYSBtdWx0aXBvaW50IEdSRSB0dW5uZWwgZm9yIGluc3RhbmNlLg0KPg0K
PiBXZWxsIHdlIGFscmVhZHkgaGF2ZSBhIG51bWJlciBvZiBkcmFmdCBwcm9wb3NhbHMgZGVmaW5p
bmcgZm9yIHR1bm5lbA0KPiBlbmNhcHN1bGF0aW9uIGF0dHJpYnV0ZXMgb3IgZXh0IGNvbW11bml0
aWVzIGZvciB0aGF0IHB1cnBvc2UuIEkgd3JvdGUNCj4gb25lIHdpdGggUmFodWwgaW4gdGhlIHBh
c3QsIEplcmVteSBkaWQgc29tZSBvcmlnaW5hbCB3b3JrLCB0aGVuIHdlIGhhbmQNCj4gdHVubmVs
IHNhZmkgKG5vdyBjYWxsZWQgaW5mby1zYWZpKSwgYW5kIGNvbWluZyB1cCB5ZXQgYW5vdGhlciBv
bmUgc29vbg0KPiBmcm9tIG1lIDotKS4gTm90IHN1cmUgdGhlcmUgaXMgYSBuZXcgbmVlZCBmb3Ig
eWV0IGFub3RoZXIgdHVubmVsIGRlY2FwDQo+IGNhcGFiaWxpdHkgZW5jb2RpbmcuDQo+DQoNCkkg
dGhpbmsgbXkgcHJvcG9zYWwgaXMgbXVjaCBtb3JlIGdlbmVyYWwuIE1vc3Qgb2YgdGhlIHZhbHVl
LWFkZGVkDQpzZXJ2aWNlcyBhcmUgYmFzZWQgb24gdHVubmVscyAobW9iaWxpdHksIFZQTnMsIFRF
LC4uLikuIEkgdGhpbmsNCnRoZXJlIGlzIGEgbmVlZCBmb3IgYSByaWNoZXIgcm91dGluZyBwYXJh
ZGlnbSwgYW5kIGluIG15IG9waW5pb24NCnRoZSBzb2x1dGlvbiBpcyBzb21ldGhpbmcgbGlrZSBU
SURSLiBUSURSIGlzIG5vdCBhbiBvdmVybGF5IHNvbHV0aW9uDQpidXQgYSB3YXkgdG8gY29tYmlu
ZSBkaXJlY3QgYW5kIGluZGlyZWN0IHJvdXRpbmcsIHRoZSBsYXR0ZXIgYmFzZWQNCm9uIHR1bm5l
bHMuIEFuZCBJIHRoaW5rIFRJRFIgcGFyYWRpZ20gY291bGQgYWxzbyBiZSB2YWx1YWJsZSBmb3IN
Cm90aGVyIFdHcyAodjZvcHMsIHRyaWxsLCAuLi4pLiBJIHRoaW5rIHdlIG5lZWQgdGhlIGNvbWUg
b2YgYWdlDQpvZiB0dW5uZWxzIHdpdGhpbiB0aGUgSVAgYXJjaGl0ZWN0dXJlLg0KDQoNCj4gPiAg
ICBUaGlzIElQIGNvdWxkIGJlIGZvcm1lZCB1c2luZyBhIHNwYXJlIC84IHByZWZpeCBhbmQgdGhl
IEFTDQo+ID4gICAgbnVtYmVyIGZvciBzZWNvbmQgYW5kIHRoaXJkIG9jdGV0cywgYW5kIGl0IHdv
dWxkIGJlIHVzZWQgYXMNCj4gPiAgICBhbiBhbnljYXN0IGFkZHJlc3MgYXNzaWduZWQgdG8gYQ0K
Pg0KPiBXaHkgc2Vjb25kICYgdGhpcmQgb2N0ZXQgPyBTdXJlIHdlIGNhbiB1c2UgMDAwLzggd2hp
Y2ggaXMgcmVzZXJ2ZWQgYnkNCj4gSUFOQSBzaW5jZSAxOTgxIGJ1dCBub3cgd2UgaGF2ZSA0IGJ5
dGVzIEFTZXMuIFdlIGNvdWxkIHVzZSB0aHJlZSBieXRlcw0KPiBvdXQgb2YgaXQuDQo+DQoNCkkg
a25vdyB0aGF0IEFTIG51bWJlcnMgYXJlIDQtYnl0ZSBsb25nLiBJIG1lbnRpb24gMi1ieXRlIEFT
TnMNCmluIG15IGRvYyB0byBsZWF2ZSB0aGUgZm91cnRoIGJ5dGUgZm9yIGV4YW1wbGUgdG8gc3Bl
Y2lmeSBhDQpzcGVjaWZpYyBlbnRyeSBwb2ludCBpbiB0aGUgQVMuDQoNCj4gPiAgICBMZXQncyBj
b250aW51ZSB0byBsb29rIGF0IHRoZSBBU19QYXRoIGF0dHJpYnV0ZTogaWYgdGhlDQo+ID4gICAg
cGVudWx0aW1hdGUgQVMgaW4gdGhlIHBhdGggd291bGQgYmUgYWJsZSB0byBhY2NlcHQNCj4gPiAg
ICB0dW5uZWxlZCB0cmFmZmljIGZvciB0aGF0IHByZWZpeCB0aGVuIHdlIGNvdWxkDQo+DQo+IFdo
eSBkbyB5b3Ugc3RpbGwgcHJvcG9zaW5nIHRoZSBjb3VwbGluZyBvZiBsb2NhdG9yIHRvIHByZWZp
eGVzIGluIHNheWluZw0KPiAiZm9yIHRoYXQgcHJlZml4IiA/IElNSE8gd2Ugc2hvdWxkIGtlZXAg
dGhvc2UgdHdvIGluZGVwZW5kZW50LiBJbiBvdGhlcg0KPiB3b3JkcyBpZiBBU0JSIFggaXMgYWJs
ZSB0byBkZS1jYXBzdWxhdGUgdHJhZmZpYyB0byBpdCdzIEFTIChpZiBzdHViIG9yDQo+IHN0dWIt
cGVudWx0aW1hdGUpIGl0IHNob3VsZCBiZSBvayBmb3IgYW55IHByZWZpeCB0byBiZSB0dW5uZWxl
ZCB0byBzdWNoDQpBUy4NCj4NCg0KTWF5YmUgbXkgRW5nbGlzaCBpcyBub3QgY2xlYXIgZW5vdWdo
LiAiTG9jYXRvciBwcmVmaXhlcyIgYW5kDQoiSWRlbnRpZmllciBwcmVmaXhlcyIgYXJlIGtlcHQg
aW5kZXBlbmRlbnQuIFdoYXQgSSBtZWFuIGlzDQp0aGF0IHRyYWZmaWMgZm9yIGEgbGVhZiBBUyAo
c3R1YiBvciBtdWx0aS1ob21lZCkgc2hvdWxkIGJlDQpkZWNhcHN1bGF0ZWQgYnkgYW55IG9mIGl0
cyB1cHN0cmVhbSBJU1BzLiBPYnZpb3VzbHkgdGhpcw0KaXMgYWxzbyB0cnVlIGZvciB0aGUgSVNQ
IHByZWZpeGVzIHRoYXQgdGhlIElTUCB1c2VzIGZvcg0KaXRzIG93biBzZXJ2aWNlcyAoRE5TLCB3
ZWIgc2VydmVycywgLi4uKS4gSW4gb3RoZXIgd29yZHMsDQp0aGUgImlkZW50aWZpZXIgcHJlZml4
ZXMiIHdpdGhpbiB0aGUgSVNQIG5ldHdvcmsgYXJlIGFsc28NCmFzc2lnbmVkICJsb2NhdG9yIHBy
ZWZpeGVzIiB3aGVuIHRoZSBmb3JtZXIgYXJlIGFubm91bmNlZA0KYnkgQkdQLg0KDQoNCg0KPiA+
IDUuMi4gVElEUiBCYXNpYyBNZWNoYW5pc20gZm9yIGEgU2luZ2xlLUhvbWVkIFNpdGUuDQo+ID4N
Cj4gPiAgICBMZXTvv71zIGNvbnNpZGVyIGEgc2l0ZSBzaW5nbGUtaG9tZWQgdG8gdXBzdHJlYW0g
cHJvdmlkZXIgSVNQMSB0aGF0DQp1c2VzIGENCj4gPiAgICBwcm92aWRlci1pbmRlcGVuZGVudCBw
cmVmaXgsIHdoYXQgaW1wbGllcyBpdHMgcHJlc2VuY2UgaW4gdGhlDQo+ID4gICAgQkdQIGdsb2Jh
bCBSSUIuIExldCdzIHN1cHBvc2Ugbm93IHRoYXQgSVNQMSBpcyBUSURSLWF3YXJlLCB3aGljaA0K
bWVhbnMNCj4+ICAgICBpdCB3aWxsIGFkdmVydGlzZSB0aGUgcHJlZml4IHVzaW5nIGEgbmV3IHRy
YW5zaXRpdmUgQkdQIGF0dHJpYnV0ZQ0KY2FsbGVkIExPQ0FUT1INCj4NCj4gWW91IGRvIG5vdCBh
ZHZlcnRpc2UgdGhlIHByZWZpeCB1c2luZyBuZXcgYXR0cmlidXRlLiBUaGUgbmV3IGF0dHJpYnV0
ZQ0KPiBjb3VsZCBiZSBhdHRhY2ggdG8gdGhlIHVwZGF0ZSBtc2cgaWYgZXZlciByZXF1aXJlZC4N
Cj4NCg0KVGhlIHByZWZpeCBvZiB0aGUgY2xpZW50IG5ldHdvcmsgd2lsbCBiZWNvbWUgYW4gImlk
ZW50aWZpZXIgcHJlZml4Ig0Kd2hlbiBpdHMgSVNQIGFkZHMgdGhlIExPQ0FUT1IgYXR0cmlidXRl
LiBUaGUgcHJlZml4ZXMgdXNlZCBieSB0aGUgSVNQDQpmb3IgdGhlIHR1bm5lbCBlbmRwb2ludHMg
d2lsbCBiZSBhbm5vdW5jZWQgd2l0aG91dCBhZGRpbmcgYW55DQpMT0NBVE9SIGF0dHJpYnV0ZSwg
aS5lLiB0aGV5IHdpbGwgYmUgImxvY2F0b3IgcHJlZml4ZXMiLCBhcyBhcmUNCmFsbCB0aGUgcHJl
Zml4ZXMgY3VycmVudGx5IHN0b3JlZCBpbiB0aGUgZ2xvYmFsIEludGVybmV0IHRhYmxlLg0KUHJl
Zml4ZXMgaW4gdGhlIGN1cnJlbnQgZ2xvYmFsIEJHUCB0YWJsZSBhcmUgImxvY2F0b3IgcHJlZml4
ZXMiDQppbiB0aGUgc2Vuc2UgdGhhdCB0aGV5IGFyZSB1c2VkIGZvciBhY3R1YWwgcm91dGluZy4N
Cg0KDQo+ID4gICAgV2hlbiBhbGwgYXV0b25vbW91cyBzeXN0ZW1zIGluIHRoZSBJbnRlcm5ldCBh
cmUgVElEUi1hd2FyZSB0aGUNCj4gPiAgICBmaW5hbCByZXN1bHRpcyB0aGF0IGFsbCByb3V0ZXJz
IGhhdmluZyBmdWxsLXJvdXRpbmcgd2lsbCBoYXZlDQo+ID4gICAgdGhlIGN1c3RvbWVyIHByZWZp
eCBib3RoIGluIHRoZSBSSUIgYW5kIHRoZSBUSUIuIFdoZW4gYSBuZXcNCj4gPiAgICBwYWNrZXQg
aXMgc2VudCB0byB0aGUgY3VzdG9tZXIgb25seSB0aGUgZmlyc3QgVElEUi1hd2FyZSByb3V0ZXIN
Cj4gPiAgICB3aWxsIGhhdmUgdG8gbG9vayB1cCB0aGUgVElCK1JJQiB3aGVyZWFzIHRoZSByZXN0
IG9mIHRoZQ0KPiA+ICAgIHRyYW5zaXQgcm91dGVycyB3aWxsIG9ubHkgaGF2ZSB0byBsb29rIHVw
IHRoZSBSSUIuIEluIG90aGVyDQo+ID4gICAgd29yZHMsIHRoZSByb3V0ZXIgcGVyZm9ybWluZyB0
dW5uZWwgaW1wb3NpdGlvbiB3aWxsIHVzZSB0aGUNCj4gPiAgICBUSUIrUklCLCBhbmQgdGhlIG90
aGVycyB3aWxsIHVzZSB0aGUgUklCLg0KPg0KPiBIb3cgZG9lcyB0aGUgdHJhbnNpdCByb3V0ZXIg
a25vdyB0byB3aGljaCB0YWJlbCB0byBsb29rID8gWW91IHNhaWQgYWJvdmUNCj4gdGhhdCB0aGUg
bG9va3VwIGlzIFRJQiAtPiBSSUIgLi4uIEkgZG8gbm90IHNlZSBhIHdheSBmb3IgdGhlIHRyYW5z
aXQNCj4gbm9kZSB0byBleGFtaW5lIHRoZSBkc3QgYW5kIG1ha2UgYSBsb29rdXAgdGFibGUgZGVj
aXNpb24gYmFzZWQgb24gdGhpcy4NCj4NCg0KT25jZSB0aGUgZWRnZSByb3V0ZXIgcGVyZm9ybXMg
dHVubmVsIGltcG9zaXRpb24gdGhlIGZvbGxvd2luZw0Kcm91dGVycyB3aWxsIHJvdXRlIHRvd2Fy
ZHMgdGhlIHR1bm5lbCBkZXN0aW5hdGlvbi4NCg0KDQo+ID4gICAgV2hlbiB0aGVzZSB0d28gQkdQ
IGFubm91bmNlbWVudHMgYXJyaXZlIHRvIHRoZSByb3V0ZXJzIG9mIHRoZQ0KPiA+ICAgIFRJRFIt
YXdhcmUgSVNQMyB0aGV5IHdpbGwgaW5zdGFsbCB0aGUgcHJlZml4IGluIHRoZSBSSUIgYXMgdXN1
YWwsDQo+ID4gICAgYnV0IHRoZXkgd2lsbCBhbHNvIGluc3RhbGwgdGhlIHByZWZpeCBpbiB0aGUg
VElCLiBMYXRlciwgd2hlbg0KPiA+ICAgIG9uZSBvZiB0aGVzZSByb3V0ZXJzIHJlY2VpdmVzIGEg
cGFja2V0IGZvciB0aGUgbXVsdGktaG9tZWQgc2l0ZQ0KPiA+ICAgIGl0IHdpbGwgY2hlY2sgdGhl
IFRJQiBiZWZvcmUgdGhlIFJJQiBhbmQgIGl0IHdpbGwgZmluZA0KPiA+ICAgIHR3byBsb2NhdG9y
cy4NCj4NCj4gV2VsbCBhcyBvZiB0b2RheSBpdCB3aWxsIG5vdCBmaW5kIHR3byBsb2NhdG9ycyBz
aW1wbHkgZHVlIHRvIGZhY3Qgb2YNCj4gYmVzdCBwYXRoIG9ubHkgYWR2ZXJ0aXNlbWVudCBmcm9t
IGVpdGhlciBsb2NhbCBJU1AzIFJSIG9yIHNvbWUgSVB2NCBSUg0KPiBvbiB0aGUgd2F5LiBBbHNv
IHRoaW5rIHRoZXJlIGFyZSBvdGhlciBnb29kIHdheXMgdG8gYWNoaWV2ZSBtdWx0aWhvbWluZw0K
PiBidXQgaW4gZmFjdCBkbyBub3QgYXNrIElTUDIgJiBJU1AxIGZvciBhbnkgY29vcGVyYXRpb24u
IEl0IGNvdWxkIGJlIGp1c3QNCj4gY3VzdG9tZXIgd2hvIGlzIHRoZSBlbmQgcG9pbnQgdmlhIHR3
byAob3IgTikgcGVlcmluZyBJU1BzLg0KPg0KDQpZZXMuIFRoZSBCR1AgYmVzdCBwYXRoIHNlbGVj
dGlvbiBhbGdvcml0aG0gd2lsbCBoYXZlIHRvIGJlDQptb2RpZmllZCBpbiB0aGUgZm9sbG93aW50
IHNlbnNlOiBpZiBhIHJvdXRlciByZWNlaXZlcyB0d28NCmFubm91bmNlbWVudHMgZm9yIHByZWZp
eCBYLCB0aGUgZmlyc3QgYW5ub3VuY2VtZW50IGhhdmluZw0KTG9jYXRvcjEgYW5kIHRoZSBzZWNv
bmQgYW5ub3VuY2VtZW50IGhhdmluZyBMb2NhdG9yMiwgdGhlDQpCR1AgYmVzdCBwYXRoIGFsZ29y
aXRoIHdpbGwgd29yayBhcyB1c3VhbCBCVVQgaXQgd2lsbCBoYXZlDQp0byBhZGQgYm90aCBMb2Nh
dG9yMSBhbmQgTG9jYXRvcjIgdG8gdGhlIGJlc3RwYXRoLg0KDQoNCj4gPiAgICBUbyBhdm9pZCB0
aGF0IG9ubHkgb25lIG9mIHRoZSBsb2NhdG9ycyBhcnJpdmVzIHRvIElTUDMgYmVjYXVzZQ0KPiA+
ICAgIG9mIHRoZSBlZmZlY3Qgb2YgdGhlIEJHUCBiZXN0IHBhdGggc2VsZWN0aW9uIGFsZ29yaXRo
bQ0KPiA+ICAgIHNvbWV3aGVyZSBpbiB0aGUgcGF0aCwgd2Ugd2lsbCBuZWVkIHRvIHNsaWdodGx5
IG1vZGlmeSB0aGlzDQo+ID4gICAgYWxnb3JpdGhtDQo+DQo+IEkgZG8gbm90IHRoaW5rIHRoYXQg
dGhpcyBpcyBwcmFjdGljYWxseSBkb2FibGUgdG8gbW9kaWZ5IEludGVybmV0IGxpa2UNCj4gdGhp
cy4gRXNwZWNpYWxseSB3aGVyZSB0aGVyZSBhcmUgYWx0ZXJuYXRpdmVzIHdoaWNoIGRvIG5vdCBy
ZXF1aXJlIHN1Y2gNCj4gbW9kaWZpY2F0aW9ucyA7KS4NCj4NCg0KSSBkb27CtHQga25vdyBhYm91
dCB0aGUgYWx0ZXJuYXRpdmVzIHlvdSBtZW50aW9uLiBDYW4geW91IHBsZWFzZQ0KcHJvdmlkZSBt
b3JlIGluZm8/LiBUaGUgQkdQIGJlc3QgcGF0aCBhbGdvcml0aG0gd2lsbCB3b3JrIGFzDQp1c3Vh
bC4gV2Ugd2lsbCBvbmx5IG5lZWQgdG8gYXBwZW5kIGJvdGggbG9jYXRvcnMgdG8gdGhlDQphbm5v
dW5jZW1lbnQuIEJvdGggbG9jYXRvcnMgd291bGQgYmUgaW4gdGhlIHNhbWUgTE9DQVRPUiBhdHRy
aWJ1dGUsDQppLmUuIHRoZSBMT0NBVE9SIGF0dHJpYnV0ZSBwZXJtaXRzIHRvIGFubm91bmNlIHNl
dmVyYWwgbG9jYXRvcnMNCmF0IHRoZSBzYW1lIHRpbWUsIGFuZCBoYXZpbmcgZGlmZmVyZW50IHR1
bm5lbGluZyB0ZWNobmlxdWVzDQooR1JFLCBJUC1pbi1JUCwgLi4uKS4NCg0KDQo+ID4gNi4gTG9j
YXRvcnMgb2YgTG9jYXRvcnMgZm9yIGEgSGllcmFyY2hpY2FsIEludGVybmV0OiBUaGUgT25pb24g
TW9kZWwNCj4gPg0KPiAuLi4NCj4gPiAgICBMZXQnc3Mgc3VwcG9zZSBub3cgdGhhdCBJU1AtMTAx
IHN1cHBvcnRzIGhpZXJhcmNoaWNhbCBUSURSDQo+ID4gICAgKEgtVElEUiksIHdoaWNoIG1lYW5z
IHRoYXQgSVNQLTEwMSB3aWxsIGFzc2lnbiBuZXcgbG9jYXRvcnMNCj4gPiAgICB0byB0aGUgbG9j
YXRvciBwcmVmaXggdGhhdCBJU1AxIGFubm91bmNlZCB0byB0aGUgSW50ZXJuZXQuDQo+ID4gICAg
VGhlIExPQ0FUT1IgYXR0cmlidXRlIGZvciB0aGlzIGxvY2F0b3IgcHJlZml4IHdpbGwgbm93DQo+
ID4gICAgY29udGFpbiBhcyB0dW5uZWwgZGVzdGluYXRpb24gYW4gSVAgYWRkcmVzcyBvZiBJU1At
MTAxLCBhbmQNCj4gPiAgICB0aGUgTE9DQVRPUiBhdHRyaWJ1dGUgd2lsbCBtYXJrIHRoaXMgbmV3
IGxvY2F0b3IgYXMgYSBsZXZlbC0yDQo+ID4gICAgbG9jYXRvci4gV2hlbiB0aGlzIEJHUCBhbm5v
dW5jZW1lbnQgYXJyaXZlcyB0byBhIGxldmVsLTIgYXdhcmUNCj4gPiAgICBBUywgaXQgd2lsbCBu
b3QgaW5zdGFsbCB0aGUgbG9jYXRvciBwcmVmaXggaW4gdGhlIFRJQiBhcyB3aXRoDQo+ID4gICAg
YW55IGlkZW50aWZpZXIgbG9jYXRvciBidXQgaXQgd2lsbCBpbnN0YWxsIHRoZSBsb2NhdG9yIHBy
ZWZpeA0KPiA+ICAgIGluIHRoZSBSSUIgYW5kIGl0IHdpbGwgbWFyayBpdCB0byBrbm93IHRoYXQg
YSBsZXZlbC0yIGxvY2F0b3INCj4gPiAgICBpcyBhdmFpbGFibGUgZm9yIGl0LiBUaGlzIGxldmVs
LTIgbG9jYXRvciB3aWxsIGJlIGluc3RhbGxlZCBpbg0KPiA+ICAgIGEgbmV3IHRhYmxlIGNhbGxl
ZCBSSUItMi4gTGF0ZXIsIHdoZW4gSVNQLTEwMSByZWNlaXZlcyB0cmFmZmljDQo+ID4gICAgd2hp
Y2ggaXMgdHVubmVsZWQgd2l0aCB0aGUgbGV2ZWwtMSBsb2NhdG9yIGl0IHdpbGwgcGVyZm9ybQ0K
PiA+ICAgIGVpdGhlciBhIHNlY29uZCB0dW5uZWwgaW1wb3NpdGlvbiB1c2luZyB0aGUNCj4gPiAg
ICBsZXZlbC0yIGxvY2F0b3IgKHRlbGVzY29waW5nKSBvciBldmVuIGl0IGNvdWxkIHN3YXAgdGhl
IGluY29taW5nDQo+ID4gICAgbGV2ZWwtMSB0dW5uZWwgZW5jYXBzdWxhdGlvbiB3aXRoIGEgbmV3
IGxldmVsLTIgdHVubmVsDQo+ID4gICAgZW5jYXBzdWxhdGlvbiAodHVubmVsIHN3YXBwaW5nKS4N
Cj4NCj4gSSBhZ3JlZSB3aXRoIHRoZSBOIHN0YWdlIG9mIGVuY2FwLiBCdXQgYWdhaW4gYXMgaW4g
dGhlIG9yaWdpbmFsIGNhc2UgSQ0KPiBkbyBub3QgdGhpbmsgdGhhdCB1c2luZyBsb2NhdG9ycyBp
cyBuZWNlc3NhcnkuIEp1c3Qgcm91dGluZyB0byBBUyBJUA0KPiBhZGRyZXNzZXMgc2VlbXMgbW9y
ZSB0aGVuIHN1ZmZpY2llbnQgeWV0IGF1dG9tYXRpYyBhbmQgZG9lcyBub3QgcmVxdWlyZQ0KPiBh
bnkgbmV3IHNpZ25hbGluZy4NCj4NCg0KRG9uJ3QgeW91IHRoaW5rIGl0IGlzIGJldHRlciB0byBo
YXZlIHNldmVyYWwgQVMgSVBzIGluc3RlYWQgb2YganVzdCBvbmU/Lg0KDQoNCj4gVGh4LA0KPiBS
Lg0KPg0KPiBQUy4gTW9yZSBjb21tZW50cyB3aGVuL2lmIHdlIGFncmVlIG9uIHRoZSBhYm92ZSA7
KS4gQXMgaXQgc2VlbXMgdGhhdCB3ZQ0KPiBhcmUgYm90aCBjdXJyZW50bHkgbG9jYXRlZCBpbiBF
dXJvcGUgcGVyaGFwcyBhIGRpcmVjdCBtZWV0aW5nIHdvdWxkIGJlDQo+IGJldHRlciB0byBoYXZl
IGEgZm9jdXNlZCBkYXkgb24gdGhpcy4=




--===============1740932478==
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

--===============1740932478==--



From idr-bounces@ietf.org Fri Nov 10 10:20:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GiY8G-0006x0-GC; Fri, 10 Nov 2006 10:17:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GiY8E-0006vp-I3
	for idr@ietf.org; Fri, 10 Nov 2006 10:17:26 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiY8D-00023T-6j
	for idr@ietf.org; Fri, 10 Nov 2006 10:17:26 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-5.cisco.com with ESMTP; 10 Nov 2006 07:17:24 -0800
X-IronPort-AV: i="4.09,410,1157353200"; 
	d="scan'208"; a="342439157:sNHT55245056"
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 kAAFHO1e010956; 
	Fri, 10 Nov 2006 07:17:24 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id kAAFHOdE000063;
	Fri, 10 Nov 2006 07:17:24 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 10 Nov 2006 07:17:23 -0800
Received: from [10.10.10.93] ([10.25.90.226]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 10 Nov 2006 07:17:23 -0800
Message-ID: <455497FB.7050601@cisco.com>
Date: Fri, 10 Nov 2006 07:17:15 -0800
From: Robert Raszuk <raszuk@cisco.com>
Organization: http://raszuk.net/
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: JUAN-JOSE.ADAN@giss.seg-social.es
Subject: Re: Rm: [Idr] Draft on "Tunneled Inter-domain Routing"
References: <OFD49734CA.999280B4-ONC1257222.0034EA45-C1257222.003EBC2D@tgss.seg-social.es>
In-Reply-To: <OFD49734CA.999280B4-ONC1257222.0034EA45-C1257222.003EBC2D@tgss.seg-social.es>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Nov 2006 15:17:23.0758 (UTC)
	FILETIME=[52D7ECE0:01C704DB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3061; t=1163171844;
	x=1164035844; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=raszuk@cisco.com;
	z=From:=20Robert=20Raszuk=20<raszuk@cisco.com>
	|Subject:=20Re=3A=20Rm=3A=20[Idr]=20Draft=20on=20=22Tunneled=20Inter-doma
	in=20Routing=22 |Sender:=20;
	bh=d8xsZ4zG1p5dOqfLrq4o8800nF0WqhHr7T9WgMnzfnk=;
	b=D4h7jnqzMNhbk75sUjN+LSqm+bS34K6hBsr+4KSasX27m9uRKF9SSqzgm3ZhHdtd2ZsFRodl
	DpnHhzDrpXikIqsgqXiq+DLfx83tdtkaKbau7Ay6edD8mUxGrfsIoSw/;
Authentication-Results: sj-dkim-7; header.From=raszuk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: raszuk@cisco.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

Hi Juan,

> I will be out for a week. I will check later about the
> possibility of having a meeting somewhere in Europe.
> I will have to convince my boss first :-).

Well we could have a sub-idr meeting for this project in Madrid then
discuss it more at next IETF in Prague ;-).

> The idea of having an IP address for an AS is something that
> I also considered but I think it is much more interesting to
> have a prefix so that we could even specify a specific entry
> point in the AS por traffic directed to a specific "identifier
> prefix". And a specific locator could be configured as an anycast
> IP address so that in case of a problem in an entry point, the
> tunneled traffic could be delivered through another entry point.
+
> Don't you think it is better to have several AS IPs instead of just
> one?.

I think we both agree on the anycasting model. I also think we all agree
on the need for more then one dst for end AS. Most practical need is
triggered for a prefix group based inbound traffic engineering.

The only disconnects are I think minor reg the allocation model of those
destinations and their choice of signaling.

> I think my proposal is much more general. Most of the value-added
> services are based on tunnels (mobility, VPNs, TE,...). I think
> there is a need for a richer routing paradigm, and in my opinion
> the solution is something like TIDR. TIDR is not an overlay solution
> but a way to combine direct and indirect routing, the latter based
> on tunnels. And I think TIDR paradigm could also be valuable for
> other WGs (v6ops, trill, ...). I think we need the come of age
> of tunnels within the IP architecture.

Well I must warn you that some folks in the industry get high blood
pressure when they hear word "tunnel" :). So at minimum I would propose
to reword the tunnel (which in the traditional meaning just indicates an
 end to end logical pipe between two end points) to simply
encapsulation.  It is more descriptive anyway to reflect real nature of
anycast destinations. And btw ... I see nothing wrong with calling it an
overlay. In fact I believe it is an overlay build by routing protocol
directly.

> I know that AS numbers are 4-byte long. I mention 2-byte ASNs
> in my doc to leave the fourth byte for example to specify a
> specific entry point in the AS.

Yes but you will have a problem mapping 3 octets AS# in that scheme ;).
Not to mention 4th octet if we ever go that for .....

> Yes. The BGP best path selection algorithm will have to be
> modified in the followint sense: if a router receives two
> announcements for prefix X, the first announcement having
> Locator1 and the second announcement having Locator2, the
> BGP best path algorith will work as usual BUT it will have
> to add both Locator1 and Locator2 to the bestpath.

Well I don't think we need yet another flavour of add-path here ;). If
we indeed conclude that sending more then best path is required I think
we should base this on add-path proposal.

Cheers,
R.

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



From idr-bounces@ietf.org Fri Nov 17 12:52:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gl7oi-0006C2-2V; Fri, 17 Nov 2006 12:47:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gl7og-00068w-5W
	for idr@ietf.org; Fri, 17 Nov 2006 12:47:54 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gl7oQ-0001tx-7A
	for idr@ietf.org; Fri, 17 Nov 2006 12:47:54 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by sj-iport-5.cisco.com with ESMTP; 17 Nov 2006 09:47:37 -0800
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id kAHHlanI009651; 
	Fri, 17 Nov 2006 12:47:36 -0500
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kAHHlaYJ006674; 
	Fri, 17 Nov 2006 12:47:36 -0500 (EST)
To: idr@ietf.org
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.2
Date: Fri, 17 Nov 2006 12:47:36 -0500
Message-ID: <3358.1163785656@cisco.com>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=195; t=1163785657;
	x=1164649657; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:=20Eric=20Rosen=20<erosen@cisco.com>
	|Subject:=20draft-lefaucheur-idr-v4nlri-v6nh-00.txt |Sender:=20
	|To:=20idr@ietf.org;
	bh=m0015SHlqcGNDTdELv558GkSMadT4gD93GMuHKoAfx4=;
	b=VFBaH/PN/SspRFz4MvK4a2gu3wf7aeBwV/n++oeK45/c4LxEuFkij0DpDlF1AN7hKfEGNtpY
	7ZUypq2bk1m/FzRm/Jvdz7QN7m5n+T38mSXUVMECRe24vrDOz/vmn5oj;
Authentication-Results: rtp-dkim-1; header.From=erosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574
Subject: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.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

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



From idr-bounces@ietf.org Sat Nov 18 15:39:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GlWtV-000809-NJ; Sat, 18 Nov 2006 15:34:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GlWtU-000800-1F
	for idr@ietf.org; Sat, 18 Nov 2006 15:34:32 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GlWtS-00022s-MV
	for idr@ietf.org; Sat, 18 Nov 2006 15:34:32 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by sj-iport-5.cisco.com with ESMTP; 18 Nov 2006 12:34:30 -0800
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 kAIKYTsw022674
	for <idr@ietf.org>; Sat, 18 Nov 2006 15:34:29 -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 kAIKYRDM010126
	for <idr@ietf.org>; Sat, 18 Nov 2006 15:34:29 -0500 (EST)
Received: from xmb-rtp-203.amer.cisco.com ([64.102.31.20]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Nov 2006 15:34:26 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
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] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
Date: Sat, 18 Nov 2006 15:34:26 -0500
Message-ID: <BABC859E6D0B9A4D8448CC7F41CD2B0702C83BB8@xmb-rtp-203.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
Thread-Index: AccKchiIuPIALS4GS2eGXAm2D3Q75QASp8rw
From: "Zafar Ali \(zali\)" <zali@cisco.com>
To: "Eric Rosen \(erosen\)" <erosen@cisco.com>, <idr@ietf.org>
X-OriginalArrivalTime: 18 Nov 2006 20:34:27.0233 (UTC)
	FILETIME=[F105D910:01C70B50]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=600; t=1163882069;
	x=1164746069; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=zali@cisco.com;
	z=From:=20=22Zafar=20Ali=20\(zali\)=22=20<zali@cisco.com>
	|Subject:=20RE=3A=20[Idr]=20draft-lefaucheur-idr-v4nlri-v6nh-00.txt
	|Sender:=20
	|To:=20=22Eric=20Rosen=20\(erosen\)=22=20<erosen@cisco.com>,
	=20<idr@ietf. org>;
	bh=LRX5H/FrMXgZCMtH8r6043X1T90T8ForOVQvK8B67N8=;
	b=KN3NNmEo1sIub9n37n/dJlM0cVaIqst6ovA7tYhVDnoexpFaaFAqPbVfDDZnFMCRBPULPlys
	uSVgfRIiefgA4l4u3z55I4VHfFH+5tc7lexmO9HxNbgQm+le9Ptw/dZ3;
Authentication-Results: rtp-dkim-1; header.From=zali@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 
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

In favor.=20

Thanks

Regards... Zafar =20

> -----Original Message-----
> From: Eric Rosen (erosen)=20
> Sent: Friday, November 17, 2006 12:48 PM
> To: idr@ietf.org
> Subject: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
>=20
> At  the  IDR  WG  meeting  last  week,  we  discussed =20
> draft-lefaucheur-idr- v4nlri-v6nh.  I would like to propose=20
> now  that this be adopted as an IDR WG document.  Your=20
> feedback is invited.=20
>=20
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr
>=20

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



From idr-bounces@ietf.org Sun Nov 19 12:09:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Glq5b-0002Ac-0i; Sun, 19 Nov 2006 12:04:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Glq5Z-0002AW-Nh
	for idr@ietf.org; Sun, 19 Nov 2006 12:04:17 -0500
Received: from kremlin.juniper.net ([207.17.137.120])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Glq5Y-00071y-ET
	for idr@ietf.org; Sun, 19 Nov 2006 12:04:17 -0500
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by kremlin.juniper.net with ESMTP; 19 Nov 2006 09:01:15 -0800
X-IronPort-AV: i="4.09,439,1157353200"; 
	d="scan'208"; a="611944962:sNHT51903144"
Received: from emailwf1.jnpr.net ([10.10.2.33]) by proton.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Sun, 19 Nov 2006 12:04:14 -0500
Received: from 172.23.1.4 ([172.23.1.4]) by emailwf1.jnpr.net ([10.10.2.33])
	with Microsoft Exchange Server HTTP-DAV ; 
	Sun, 19 Nov 2006 17:04:14 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Sun, 19 Nov 2006 12:04:15 -0500
Subject: Re: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
From: Bruno Rijsman <brijsman@juniper.net>
To: "Eric Rosen (erosen)" <erosen@cisco.com>,
	<idr@ietf.org>
Message-ID: <C185F8BF.4015%brijsman@juniper.net>
Thread-Topic: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
Thread-Index: AccKchiIuPIALS4GS2eGXAm2D3Q75QASp8rwAFABka8=
In-Reply-To: <BABC859E6D0B9A4D8448CC7F41CD2B0702C83BB8@xmb-rtp-203.amer.cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 19 Nov 2006 17:04:14.0536 (UTC)
	FILETIME=[BDAEC480:01C70BFC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: 
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

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

I am in favor of adopting this as a WG document.

> Your feedback is invited.

It would good to explicitly point out that the "Extended Next Hop Encoding"
capability is not to be used for legacy address families mentioned in
section 1 which already have some existing mechanism to determine the type
of next-hop (e.g. ietf-l3vpn-rt-constrain).

In section 3 the draft says "However, this encoding has been chosen to
facilitate potential use of a similar mechanism in the future for other
address families."

It would be good to clarify that future drafts for new address families
should consider both IPv4 and IPv6 next-hops right from the get-go and
should provide some mechanism to infer the type of next-hop from the
encoding (e.g. based on length). That way, these new address families will
not need the "Extended Next Hop Encoding" capability.

We only need the capability if we extend some existing draft (which was
already defined, implemented and deployed) with some new type of next-hop in
such a way that it might confuse existing implementations.

To be more "future proof", new drafts might include language such as "If the
length or the format of the next-hop is not recognized, the route should be
declared unreachable but the session should not be torn down."

-- Bruno


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



From idr-bounces@ietf.org Mon Nov 20 03:34:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gm4WJ-0003LF-4v; Mon, 20 Nov 2006 03:28:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gm4WH-0003LA-Qh
	for idr@ietf.org; Mon, 20 Nov 2006 03:28:49 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gm4WF-0002zl-CC
	for idr@ietf.org; Mon, 20 Nov 2006 03:28:49 -0500
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 20 Nov 2006 09:28:46 +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 kAK8SkN9015666; 
	Mon, 20 Nov 2006 09:28:46 +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 kAK8Skwv000478; 
	Mon, 20 Nov 2006 09:28:46 +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); 
	Mon, 20 Nov 2006 09:28:46 +0100
Received: from [10.0.0.1] ([10.61.65.157]) by xfe-ams-331.emea.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Nov 2006 09:28:42 +0100
In-Reply-To: <C185F8BF.4015%brijsman@juniper.net>
References: <C185F8BF.4015%brijsman@juniper.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <7F4C27C0-8A0F-4D4F-A42B-9DD7401BA962@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: Mon, 20 Nov 2006 09:27:22 +0100
To: Bruno Rijsman <brijsman@juniper.net>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 20 Nov 2006 08:28:42.0988 (UTC)
	FILETIME=[E374DAC0:01C70C7D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2046; t=1164011326;
	x=1164875326; 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=bPQFTvWgwwdwf44GRRUOiZTQjn307xKz3lvsl/YquDc=;
	b=bwzeb+J7UYbWv7DWLwLM9lwzB6ybR7t35zfc1C1J9+Nerm1dUiLrQXyZqlHnEmlYmc1z+MJG
	lfx5MtO1sfrEfkOSD4fA71P1d5QP/gMhHk8xR3Ih++qsyMl5rKbLHqDi;
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: 244a2fd369eaf00ce6820a760a3de2e8
Cc: idr@ietf.org, Francois Le Faucheur IMAP <flefauch@cisco.com>,
	"Eric Rosen \(erosen\)" <erosen@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

Hello Bruno,

On 19 Nov 2006, at 18:04, Bruno Rijsman wrote:

>> 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.
>
> I am in favor of adopting this as a WG document.
>
>> Your feedback is invited.
>
> It would good to explicitly point out that the "Extended Next Hop  
> Encoding"
> capability is not to be used for legacy address families mentioned in
> section 1 which already have some existing mechanism to determine  
> the type
> of next-hop (e.g. ietf-l3vpn-rt-constrain).

Right. We've already got some edits in the works clarifying the set  
of <AFI/SAFI> for which the "Extended Next Hop Encoding" is  
applicable (and hence for which it is not).


>
> In section 3 the draft says "However, this encoding has been chosen to
> facilitate potential use of a similar mechanism in the future for  
> other
> address families."
>
> It would be good to clarify that future drafts for new address  
> families
> should consider both IPv4 and IPv6 next-hops right from the get-go and
> should provide some mechanism to infer the type of next-hop from the
> encoding (e.g. based on length). That way, these new address  
> families will
> not need the "Extended Next Hop Encoding" capability.

Agreed. We'll include such a recommendation.

Thanks

Francois

>
> We only need the capability if we extend some existing draft (which  
> was
> already defined, implemented and deployed) with some new type of  
> next-hop in
> such a way that it might confuse existing implementations.
>
> To be more "future proof", new drafts might include language such  
> as "If the
> length or the format of the next-hop is not recognized, the route  
> should be
> declared unreachable but the session should not be torn down."
>
> -- 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 Mon Nov 20 11:58:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmCT8-0007ug-L4; Mon, 20 Nov 2006 11:58:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmCT7-0007ua-Nm
	for idr@ietf.org; Mon, 20 Nov 2006 11:58:05 -0500
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmCT6-0006XW-CX
	for idr@ietf.org; Mon, 20 Nov 2006 11:58:05 -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 kAKGw1X13131
	for <idr@ietf.org>; Mon, 20 Nov 2006 08:58: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 kAKGvuB27176
	for <idr@ietf.org>; Mon, 20 Nov 2006 08:57:56 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200611201657.kAKGvuB27176@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: <60452.1164041876.1@juniper.net>
Date: Mon, 20 Nov 2006 08:57:56 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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,

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

From idr-bounces@ietf.org Mon Nov 20 11:58:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmCQK-0007RW-JV; Mon, 20 Nov 2006 11:55:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmCQJ-0007RP-OE
	for idr@ietf.org; Mon, 20 Nov 2006 11:55:11 -0500
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmCQH-0006LI-2v
	for idr@ietf.org; Mon, 20 Nov 2006 11:55:11 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	kAKGt61Z084729
	for <idr@ietf.org>; Mon, 20 Nov 2006 08:55:06 -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 kAKGt6B26434
	for <idr@ietf.org>; Mon, 20 Nov 2006 08:55:06 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200611201655.kAKGt6B26434@merlot.juniper.net>
To: idr@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <60308.1164041706.1@juniper.net>
Date: Mon, 20 Nov 2006 08:55:06 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75
Subject: [Idr] IETF67 - IDR WG minutes
X-BeenThere: idr@ietf.org
X-Mailman-VFrom idr-bounces@ietf.org Mon Nov 20 11:58:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmCT8-0007ug-L4; Mon, 20 Nov 2006 11:58:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmCT7-0007ua-Nm
	for idr@ietf.org; Mon, 20 Nov 2006 11:58:05 -0500
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmCT6-0006XW-CX
	for idr@ietf.org; Mon, 20 Nov 2006 11:58:05 -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 kAKGw1X13131
	for <idr@ietf.org>; Mon, 20 Nov 2006 08:58: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 kAKGvuB27176
	for <idr@ietf.org>; Mon, 20 Nov 2006 08:57:56 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200611201657.kAKGvuB27176@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: <60452.1164041876.1@juniper.net>
Date: Mon, 20 Nov 2006 08:57:56 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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,

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

From idr-bounces@ietf.org Mon Nov 20 11:58:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmCQK-0007RW-JV; Mon, 20 Nov 2006 11:55:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmCQJ-0007RP-OE
	for idr@ietf.org; Mon, 20 Nov 2006 11:55:11 -0500
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmCQH-0006LI-2v
	for idr@ietf.org; Mon, 20 Nov 2006 11:55:11 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	kAKGt61Z084729
	for <idr@ietf.org>; Mon, 20 Nov 2006 08:55:06 -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 kAKGt6B26434
	for <idr@ietf.org>; Mon, 20 Nov 2006 08:55:06 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200611201655.kAKGt6B26434@merlot.juniper.net>
To: idr@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <60308.1164041706.1@juniper.net>
Date: Mon, 20 Nov 2006 08:55:06 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75
Subject: [Idr] IETF67 - IDR WG minutes
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,

Attached are the minutes of the IDR WG. Please send corrections, if any.

Yakov.
-------------------------------------------------------------------------
IDR 2006/11/08 meeting:

Taken by John Scudder and Dave Ward.

1. Document status (Yakov):

Lots of progress:
- GR to RFC editor
- Multiprotocol also on RFC editor queue.  Needs a little editorial change
   but nothing substantive.
- 6PE -- through IESG LC, IETF LC, approve announcement forthcoming.
- 4byte ASNs -- IESG comments to be incorporated.
- AS confeds -- revised ID needed, authors to do Real Soon Now.
- AS_PATHLIMIT -- early allocation procedures have worked very smoothly.

No progress on:
- ORF
- AS wide unique ID
- Avoid Best Path transition
- Prefix based ORF

2. AFI and SAFI (Yakov, Bill):

Yakov:
No IANA procedures for allocating AFIs!

Bill Fenner:
- IANA needs guidance for what their policy should be for AFI, asked IESG.
- Who are stakeholders?  Routing for sure, but must be others -- why
   is AFI 16 == DNS registered?  (Bill's guess: MIB.)
- If routing is only stakeholder, routing should propose policy.
- Other considerations -- scarce? (No, 16 bits.) potential harm from
   allocation?
- Possible policies -- specification req'd + early allocation, or FCFS

Discussion:
Acee Lindem: Should be some review of AFI, otherwise I could get an
   Acee Lindem AFI
Bill Fenner: Is that harmful though?
Yakov: But you can already get a SAFI today...
Chandra Appanna: I don't mind FCFS, but how to handle indiscriminate
   allocations?
Bill: FCFS doesn't pretend to, but could break into ranges like other
   registries, allocate half for FCFS, reserve half for later.
Kireeti: Do we have to choose one? Can't we have spaces?
Bill: We can have spaces.
Kireeti: OK let's, half for FCFS, half for Spec Req'd.
Bill: Why?
Kireeti: To prevent DoS allocations.
Kireeti: Also Spec Req'd code points are shinier and more important
   looking.
Danny McPherson: Talked about this in Paris too, and IESG was asked
   to make a general guideline about this.  In PWE3 we split into three,
   expert review req'd, FCFS, etc.
John: I don't really see a point of having two different allocation
   policies.  If you have FCFS anyway, may as well have only that.
Danny: Worry about depletion with FCFS. Challenge was not necessarily 
   an attack but, greedy alloc and potential for depletion. My experience 
   was that FCFS was seen to have the potential for abuse.

Bill: If we don't have FCFS, people will just pull numbers from
   clear blue sky.
Yakov: I suggest 1/3 or 1/2 of space reserved, then remainder is
   some mix of FCFS and maybe Spec Req'd.
Bill: OK, let's follow up on list, I'll send a strawman.

3. draft-lefaucheur-idr-v4nlri-v6nh-00.txt (Eric Rosen):

For years now we've been playing with different uses for NH of 
different AF from NLRI.  Different deployed examples --
- VPN-IPv4 with IPv4 NH (but with bizarre encoding)
- IPv6 AF with IPv4 NH using "IPv4 mapped IPv6 addres"
- And so on, e.g. l2vpn, rt-constraint, using length field to
   distinguish between v4 and v6.
- Leaves us with one odd man out: IPv4 NLRI, no way to have v6 NH,
   no obvious encoding trick to stuff in v6 NH.
- Softwire WG has requirement to carry v4 routing over v6-only single
   stack core -- analogous to "BGP-free core", v4 routing at border
   routers but not in core.
- Implies v4 NLRI with v6 addresses as NH (for tunnels across core).
- Straightforward solution is to simply declare that v4 AF can have
   v6 NH.
- Many possible encodings.  Current proposal, use length field to
   distinguish.
- Since this isn't interoperable with implemeersion: 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,

Attached are the minutes of the IDR WG. Please send corrections, if any.

Yakov.
-------------------------------------------------------------------------
IDR 2006/11/08 meeting:

Taken by John Scudder and Dave Ward.

1. Document status (Yakov):

Lots of progress:
- GR to RFC editor
- Multiprotocol also on RFC editor queue.  Needs a little editorial change
   but nothing substantive.
- 6PE -- through IESG LC, IETF LC, approve announcement forthcoming.
- 4byte ASNs -- IESG comments to be incorporated.
- AS confeds -- revised ID needed, authors to do Real Soon Now.
- AS_PATHLIMIT -- early allocation procedures have worked very smoothly.

No progress on:
- ORF
- AS wide unique ID
- Avoid Best Path transition
- Prefix based ORF

2. AFI and SAFI (Yakov, Bill):

Yakov:
No IANA procedures for allocating AFIs!

Bill Fenner:
- IANA needs guidance for what their policy should be for AFI, asked IESG.
- Who are stakeholders?  Routing for sure, but must be others -- why
   is AFI 16 == DNS registered?  (Bill's guess: MIB.)
- If routing is only stakeholder, routing should propose policy.
- Other considerations -- scarce? (No, 16 bits.) potential harm from
   allocation?
- Possible policies -- specification req'd + early allocation, or FCFS

Discussion:
Acee Lindem: Should be some review of AFI, otherwise I could get an
   Acee Lindem AFI
Bill Fenner: Is that harmful though?
Yakov: But you can already get a SAFI today...
Chandra Appanna: I don't mind FCFS, but how to handle indiscriminate
   allocations?
Bill: FCFS doesn't pretend to, but could break into ranges like other
   registries, allocate half for FCFS, reserve half for later.
Kireeti: Do we have to choose one? Can't we have spaces?
Bill: We can have spaces.
Kireeti: OK let's, half for FCFS, half for Spec Req'd.
Bill: Why?
Kireeti: To prevent DoS allocations.
Kireeti: Also Spec Req'd code points are shinier and more important
   looking.
Danny McPherson: Talked about this in Paris too, and IESG was asked
   to make a general guideline about this.  In PWE3 we split into three,
   expert review req'd, FCFS, etc.
John: I don't really see a point of having two different allocation
   policies.  If you have FCFS anyway, may as well have only that.
Danny: Worry about depletion with FCFS. Challenge was not necessarily 
   an attack but, greedy alloc and potential for depletion. My experience 
   was that FCFS was seen to have the potential for abuse.

Bill: If we don't have FCFS, people will just pull numbers from
   clear blue sky.
Yakov: I suggest 1/3 or 1/2 of space reserved, then remainder is
   some mix of FCFS and maybe Spec Req'd.
Bill: OK, let's follow up on list, I'll send a strawman.

3. draft-lefaucheur-idr-v4nlri-v6nh-00.txt (Eric Rosen):

For years now we've been playing with different uses for NH of 
different AF from NLRI.  Different deployed examples --
- VPN-IPv4 with IPv4 NH (but with bizarre encoding)
- IPv6 AF with IPv4 NH using "IPv4 mapped IPv6 addres"
- And so on, e.g. l2vpn, rt-constraint, using length field to
   distinguish between v4 and v6.
- Leaves us with one odd man out: IPv4 NLRI, no way to have v6 NH,
   no obvious encoding trick to stuff in v6 NH.
- Softwire WG has requirement to carry v4 routing over v6-only single
   stack core -- analogous to "BGP-free core", v4 routing at border
   routers but not in core.
- Implies v4 NLRI with v6 addresses as NH (for tunnels across core).
- Straightforward solution is to simply declare that v4 AF can have
   v6 NH.
- Many possible encodings.  Current proposal, use length field to
   distinguish.
- Since this isn't interoperable with implementations that don't
   understand v6 NH, use BGP capability to make sure you don't send
   such next hops to peers that don't understand them.
- Other options considered:
   - TLV: better solution in general.  Slightly more complex encoding.
     Architecturally "purer".  But, we already have hacks for every
     other option in the matrix of NLRI/NH combinations, so since we
     just have this one v4/v6 case, might as well do the expedient
     thing.
   - New AFI/SAFI for 4/6 case:  Operationally more complicated,
     creates implementation hassles.
- Is it even needed?  For example, you could have v4-free core by having
   configured overlay tunnel topology, then run v4 routing protocols
   over it.
   - This is a softwire problem, not an IDR problem, softwires is
     proposing requirements
   - In general, overlay model seems more painful!

Discussion:
Yakov: I don't think it's purely a softwire problem.  2547 over IPv6
   also needs to be solved -- and your proposal solves it!
Eric: Yep, and for the same reason 6PE is useful for softwires.  Great!
Yakov: What do you want to do with it?
Eric: Make it an RFC.
Yakov: Oh come on.
Eric: Make it a WG doc.  Shall we?
Yakov: How many have read it?  (Show of hands, some.)  Of those who've
   read it, how many would object to making it a WG doc?  (~1 hand)
Yakov:  Eric-Francois to make request to list after posting revision 
   of the draft

4. draft-pmohapat-idr-info-safi-00.txt (Eric Rosen):
- Softwire problem requires v4 packets to be tunneled through v6 core
   and vice-versa.
- Of course they should just use MPLS but WG wants to do it the
   hard way.
- So, need to be able to pick an encapsulation.  Not only that, but
   to make it more complex, desire to have various policies for what
   tunnels are used for what destinations, etc.
- At least want to be able to categorize routers into classes, to which
   tunneling policies can be applied.
- Some IP encaps (GRE, L2TPv3) lack appropriate native signalling
   protocols for multipoint-to-point tunnels.
- Hence proposal: New SAFI, "Info-SAFI" (everyone agrees choice of name
   is poor...)
- Carries:
   - Address of BGP speaker, embedded in NLRI
   - Characteristics of speaker, as communities
   - For signalled tunnels, new attribute with signalling info
   - Allows multiple info-SAFIs per speaker
- Obvious alternative:  Just use a /32 identifying speaker, attach
   attributes to that.
- Why not?
   - Route distribution constraints might be different
   - Don't want trouble with summarization policies
- Isn't:
   - Tunnel-SAFI -- no hidden infrastructure, not naming tunnels, not
     replacing NH with tunnels
   - Not "all purpose use BGP to send any random info about anything"
     scheme

Discussion:
Chandra: Range of info-SAFIs, or just one?
Eric: Just one. In the info-safi there are multiple NRLI's per speaker - good
   clarification
Chandra: Why even bother spec'ing, you could have multiple SAFIs per
   speaker, what's special about info-SAFI?
Eric: Huh?
Eric: Oh, what I meant is, there are multiple *NLRI* per speaker
   within the info-SAFI.
Yakov: GRE doesn't have signaling protocol and only need one if you require
   key. We know GRE works today w/o any of this if key is not used. If you want
   to mark certain routes to go over GRE tunnel and you want to use a key; what
   does this proposal buy you vs just carry GRE key with the routes.
Eric: I assumed while working this out that we wanted to do it
   efficiently -- just advertise the BGP speaker's properties ONCE,
   instead of re-advertising them again and again (once per update).
   Not clear whether this is the right tradeoff or not -- a little
   extra complexity for a little extra efficiency.  Consider though,
   that if you change the key or something, you would have to readvertise
   your whole RIB.
Yakov: Good point about L2TPv3.  Why not just think of your proposal
   as just an L2TPv3 signalling protocol for mp2p tunnels?  I think that 
   would be fine.
   If we need it for GRE, get another SAFI. It fits into model we have 
   today for MPLS where wentations that don't
   understand v6 NH, use BGP capability to make sure you don't send
   such next hops to peers that don't understand them.
- Other options considered:
   - TLV: better solution in general.  Slightly more complex encoding.
     Architecturally "purer".  But, we already have hacks for every
     other option in the matrix of NLRI/NH combinations, so since we
     just have this one v4/v6 case, might as well do the expedient
     thing.
   - New AFI/SAFI for 4/6 case:  Operationally more complicated,
     creates implementation hassles.
- Is it even needed?  For example, you could have v4-free core by having
   configured overlay tunnel topology, then run v4 routing protocols
   over it.
   - This is a softwire problem, not an IDR problem, softwires is
     proposing requirements
   - In general, overlay model seems more painful!

Discussion:
Yakov: I don't think it's purely a softwire problem.  2547 over IPv6
   also needs to be solved -- and your proposal solves it!
Eric: Yep, and for the same reason 6PE is useful for softwires.  Great!
Yakov: What do you want to do with it?
Eric: Make it an RFC.
Yakov: Oh come on.
Eric: Make it a WG doc.  Shall we?
Yakov: How many have read it?  (Show of hands, some.)  Of those who've
   read it, how many would object to making it a WG doc?  (~1 hand)
Yakov:  Eric-Francois to make request to list after posting revision 
   of the draft

4. draft-pmohapat-idr-info-safi-00.txt (Eric Rosen):
- Softwire problem requires v4 packets to be tunneled through v6 core
   and vice-versa.
- Of course they should just use MPLS but WG wants to do it the
   hard way.
- So, need to be able to pick an encapsulation.  Not only that, but
   to make it more complex, desire to have various policies for what
   tunnels are used for what destinations, etc.
- At least want to be able to categorize routers into classes, to which
   tunneling policies can be applied.
- Some IP encaps (GRE, L2TPv3) lack appropriate native signalling
   protocols for multipoint-to-point tunnels.
- Hence proposal: New SAFI, "Info-SAFI" (everyone agrees choice of name
   is poor...)
- Carries:
   - Address of BGP speaker, embedded in NLRI
   - Characteristics of speaker, as communities
   - For signalled tunnels, new attribute with signalling info
   - Allows multiple info-SAFIs per speaker
- Obvious alternative:  Just use a /32 identifying speaker, attach
   attributes to that.
- Why not?
   - Route distribution constraints might be different
   - Don't want trouble with summarization policies
- Isn't:
   - Tunnel-SAFI -- no hidden infrastructure, not naming tunnels, not
     replacing NH with tunnels
   - Not "all purpose use BGP to send any random info about anything"
     scheme

Discussion:
Chandra: Range of info-SAFIs, or just one?
Eric: Just one. In the info-safi there are multiple NRLI's per speaker - good
   clarification
Chandra: Why even bother spec'ing, you could have multiple SAFIs per
   speaker, what's special about info-SAFI?
Eric: Huh?
Eric: Oh, what I meant is, there are multiple *NLRI* per speaker
   within the info-SAFI.
Yakov: GRE doesn't have signaling protocol and only need one if you require
   key. We know GRE works today w/o any of this if key is not used. If you want
   to mark certain routes to go over GRE tunnel and you want to use a key; what
   does this proposal buy you vs just carry GRE key with the routes.
Eric: I assumed while working this out that we wanted to do it
   efficiently -- just advertise the BGP speaker's properties ONCE,
   instead of re-advertising them again and again (once per update).
   Not clear whether this is the right tradeoff or not -- a little
   extra complexity for a little extra efficiency.  Consider though,
   that if you change the key or something, you would have to readvertise
   your whole RIB.
Yakov: Good point about L2TPv3.  Why not just think of your proposal
   as just an L2TPv3 signalling protocol for mp2p tunnels?  I think that 
   would be fine.
   If we need it for GRE, get another SAFI. It fits into model we have 
   today for MPLS where we have a distinct AFI/SAFI for setting up mp2p LSPs 
   with BGP.
Chandra: I understand that to carry the tunneling info we need a SAFI,
   but as for attributes of a speaker you exchange them in capabilities.
Eric: I'll answer Yakov's question first.  It's not clear to me
   if it's better or worse to have one SAFI for all tunnel signalling,
   or one for each technology.  I'm not sure how to compare them.
Yakov: If you do this specific per tunnel encap, you only carry that info.
   For another you use another. Avoids attr clash and errors. Diff tunneling
   protocols have different things.
Yakov: Regarding Chandra's question, I think "characteristic of BGP
   speaker" are things we already advertise, and we don't need a
   info-SAFI!
Eric: Problem is desire to divide routers into classes based on, e.g.,
   what kind of tunneling technologies they support.
Yakov: That doesn't sound like general characteristics of BGP speakers.
   That sounds like just characteristics wrt tunnels.
Eric: How do you think you're actually going to restrict it?
   Communities are general things.  Once you have an update message,
   you can put communities in it.
Yakov: But the point is, those communities would be embedded in
   BGP update that carries L2TPv3 tunnel info!
Eric: So how do you think you'd signal stuff like tunneling technology
   preference?
Yakov: Color each route with a community.
Eric: Seems pretty inefficient when you change an attribute.
Eric: So suppose we change the name to tunnel signalling SAFI and leave
   it the same otherwise?
Yakov: That's what it is!
Chandra: To carry tunnel info you need a safi but, you say "attributes of a
speaker" are those that send in dyn cap at OPEN. So, I am confused
Rajiv Asari: I agree with Yakov.  Suppose next I want to stick
   for example compression info out?
Yakov: Right, what happens if other end doesn't understand?
John Scudder: You can do this with an optional attribute.
Yakov: What do you want to do with the doc?
Eric: Not ready for WG doc.
Chandra: Probably not ready for WG doc.
Yakov: Please discuss on mailing list.


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





 have a distinct AFI/SAFI for setting up mp2p LSPs 
   with BGP.
Chandra: I understand that to carry the tunneling info we need a SAFI,
   but as for attributes of a speaker you exchange them in capabilities.
Eric: I'll answer Yakov's question first.  It's not clear to me
   if it's better or worse to have one SAFI for all tunnel signalling,
   or one for each technology.  I'm not sure how to compare them.
Yakov: If you do this specific per tunnel encap, you only carry that info.
   For another you use another. Avoids attr clash and errors. Diff tunneling
   protocols have different things.
Yakov: Regarding Chandra's question, I think "characteristic of BGP
   speaker" are things we already advertise, and we don't need a
   info-SAFI!
Eric: Problem is desire to divide routers into classes based on, e.g.,
   what kind of tunneling technologies they support.
Yakov: That doesn't sound like general characteristics of BGP speakers.
   That sounds like just characteristics wrt tunnels.
Eric: How do you think you're actually going to restrict it?
   Communities are general things.  Once you have an update message,
   you can put communities in it.
Yakov: But the point is, those communities would be embedded in
   BGP update that carries L2TPv3 tunnel info!
Eric: So how do you think you'd signal stuff like tunneling technology
   preference?
Yakov: Color each route with a community.
Eric: Seems pretty inefficient when you change an attribute.
Eric: So suppose we change the name to tunnel signalling SAFI and leave
   it the same otherwise?
Yakov: That's what it is!
Chandra: To carry tunnel info you need a safi but, you say "attributes of a
speaker" are those that send in dyn cap at OPEN. So, I am confused
Rajiv Asari: I agree with Yakov.  Suppose next I want to stick
   for example compression info out?
Yakov: Right, what happens if other end doesn't understand?
John Scudder: You can do this with an optional attribute.
Yakov: What do you want to do with the doc?
Eric: Not ready for WG doc.
Chandra: Probably not ready for WG doc.
Yakov: Please discuss on mailing list.


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





From idr-bounces@ietf.org Mon Nov 20 13:41:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmE1A-000353-0A; Mon, 20 Nov 2006 13:37:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmE17-00034t-Mu
	for idr@ietf.org; Mon, 20 Nov 2006 13:37:17 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmE16-0008Ul-Bm
	for idr@ietf.org; Mon, 20 Nov 2006 13:37:17 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 20 Nov 2006 10:37:15 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kAKIbFjP025317; 
	Mon, 20 Nov 2006 10:37:15 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kAKIbFio018351;
	Mon, 20 Nov 2006 10:37:15 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Nov 2006 10:37:15 -0800
Received: from [10.10.10.93] ([10.25.90.226]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Nov 2006 10:37:14 -0800
Message-ID: <4561F5D2.8090200@cisco.com>
Date: Mon, 20 Nov 2006 10:37:06 -0800
From: Robert Raszuk <raszuk@cisco.com>
Organization: http://raszuk.net/
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
References: <200611201657.kAKGvuB27176@merlot.juniper.net>
In-Reply-To: <200611201657.kAKGvuB27176@merlot.juniper.net>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Nov 2006 18:37:15.0278 (UTC)
	FILETIME=[E67A2AE0:01C70CD2]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=900; t=1164047835;
	x=1164911835; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=raszuk@cisco.com;
	z=From:=20Robert=20Raszuk=20<raszuk@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20draft-lefaucheur-idr-v4nlri-v6nh-00.txt
	|Sender:=20; bh=uW8ummW3YaJ1/By/JXg7XF0+DEGeQfPkQWMxviDYZqM=;
	b=lO8fWDMc/G4qqt1VToiNtzdxQexUF2zuZG7zeJ/Tkj3NwdNWjmqm1XOhRU99Nz070a08r/wk
	VsDyDkWUCbz2yDlS3InSAb2rY8sB0Eot84C41FgWDqGwiIRBqHj+0Wjm;
Authentication-Results: sj-dkim-2; header.From=raszuk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: raszuk@cisco.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 support this draft to be an IDR WG item.

Cheers,
R.

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

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



From idr-bounces@ietf.org Wed Nov 22 15:53:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2q-00063R-1z; Wed, 22 Nov 2006 15:50:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2g-00061h-BO; Wed, 22 Nov 2006 15:50:02 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2g-0005WE-21; Wed, 22 Nov 2006 15:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id E3BE526E63;
	Wed, 22 Nov 2006 20:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gmz2f-0006kL-Kz; Wed, 22 Nov 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gmz2f-0006kL-Kz@stiedprstage1.ietf.org>
Date: Wed, 22 Nov 2006 15:50:01 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: idr@ietf.org
Subject: [Idr] I-D ACTION:draft-ietf-idr-dynamic-cap-09.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		: Dynamic Capability for BGP-4
	Author(s)	: E. Chen, S. Sangli
	Filename	: draft-ietf-idr-dynamic-cap-09.txt
	Pages		: 8
	Date		: 2006-11-22
	
This document defines a new BGP capability termed "Dynamic
   Capability", which would allow the dynamic update of capabilities
   over an established BGP session. This capability would facilitate
   non-disruptive capability changes by BGP speakers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-dynamic-cap-09.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-ietf-idr-dynamic-cap-09.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-ietf-idr-dynamic-cap-09.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: <From idr-bounces@ietf.org Wed Nov 22 15:53:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2q-00063R-1z; Wed, 22 Nov 2006 15:50:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2g-00061h-BO; Wed, 22 Nov 2006 15:50:02 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2g-0005WE-21; Wed, 22 Nov 2006 15:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id E3BE526E63;
	Wed, 22 Nov 2006 20:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gmz2f-0006kL-Kz; Wed, 22 Nov 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gmz2f-0006kL-Kz@stiedprstage1.ietf.org>
Date: Wed, 22 Nov 2006 15:50:01 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: idr@ietf.org
Subject: [Idr] I-D ACTION:draft-ietf-idr-dynamic-cap-09.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		: Dynamic Capability for BGP-4
	Author(s)	: E. Chen, S. Sangli
	Filename	: draft-ietf-idr-dynamic-cap-09.txt
	Pages		: 8
	Date		: 2006-11-22
	
This document defines a new BGP capability termed "Dynamic
   Capability", which would allow the dynamic update of capabilities
   over an established BGP session. This capability would facilitate
   non-disruptive capability changes by BGP speakers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-dynamic-cap-09.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-ietf-idr-dynamic-cap-09.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-ietf-idr-dynamic-cap-09.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-11-22110527.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-dynamic-cap-09.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-idr-dynamic-cap-09.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-11-22110527.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 Nov 22 15:53:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2x-0006Ux-4r; Wed, 22 Nov 2006 15:50:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2h-00062C-46; Wed, 22 Nov 2006 15:50:03 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2f-0005WB-RX; Wed, 22 Nov 2006 15:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id CA7F53289B;
	Wed, 22 Nov 2006 20:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gmz2f-0006kR-MO; Wed, 22 Nov 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gmz2f-0006kR-MO@stiedprstage1.ietf.org>
Date: Wed, 22 Nov 2006 15:50:01 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: idr@ietf.org
Subject: [Idr] I-D ACTION:draft-ietf-idr-bgp-identifier-08.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		: AS-wide Unique BGP Identifier for BGP-4
	Author(s)	: E. Chen, J. Yuan
	Filename	: draft-ietf-idr-bgp-identifier-08.txt
	Pages		: 5
	Date		: 2006-11-22
	
To accommodate situations where the current requirements for the BGP
   Identifier are not met, this document relaxes the definition of the
   BGP Identifier to be a 4-octet unsigned, non-zero integer, and
   relaxes the "uniqueness" requirement so that only AS-wide uniqueness
   of the BGP Identifiers is required. These revisions to the base BGP
   specification do not introduce any backward compatibility issue.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-identifier-08.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-ietf-idr-bgp-identifier-08.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-ietf-idr-bgp-identifier-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack2006-11-22110527.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-dynamic-cap-09.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-idr-dynamic-cap-09.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-11-22110527.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 Nov 22 15:53:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2x-0006Ux-4r; Wed, 22 Nov 2006 15:50:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2h-00062C-46; Wed, 22 Nov 2006 15:50:03 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gmz2f-0005WB-RX; Wed, 22 Nov 2006 15:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id CA7F53289B;
	Wed, 22 Nov 2006 20:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gmz2f-0006kR-MO; Wed, 22 Nov 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Gmz2f-0006kR-MO@stiedprstage1.ietf.org>
Date: Wed, 22 Nov 2006 15:50:01 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: idr@ietf.org
Subject: [Idr] I-D ACTION:draft-ietf-idr-bgp-identifier-08.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		: AS-wide Unique BGP Identifier for BGP-4
	Author(s)	: E. Chen, J. Yuan
	Filename	: draft-ietf-idr-bgp-identifier-08.txt
	Pages		: 5
	Date		: 2006-11-22
	
To accommodate situations where the current requirements for the BGP
   Identifier are not met, this document relaxes the definition of the
   BGP Identifier to be a 4-octet unsigned, non-zero integer, and
   relaxes the "uniqueness" requirement so that only AS-wide uniqueness
   of the BGP Identifiers is required. These revisions to the base BGP
   specification do not introduce any backward compatibility issue.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-identifier-08.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-ietf-idr-bgp-identifier-08.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-ietf-idr-bgp-identifier-08.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-11-22110833.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-bgp-identifier-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idr-bgp-identifier-08.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-11-22110833.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--





" 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-11-22110833.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idr-bgp-identifier-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idr-bgp-identifier-08.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-11-22110833.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 Nov 22 20:57:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gn3nD-00044x-LQ; Wed, 22 Nov 2006 20:54:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gn3nC-00044s-6I
	for idr@ietf.org; Wed, 22 Nov 2006 20:54:22 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gn3nA-0002Vq-Hb
	for idr@ietf.org; Wed, 22 Nov 2006 20:54:21 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by sj-iport-5.cisco.com with ESMTP; 22 Nov 2006 17:54:20 -0800
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 kAN1sJXb012021; 
	Wed, 22 Nov 2006 20:54:19 -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 kAN1sHDM014536; 
	Wed, 22 Nov 2006 20:54:17 -0500 (EST)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Nov 2006 20:54:17 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
Date: Wed, 22 Nov 2006 20:54:16 -0500
Message-ID: <15B86BC7352F864BB53A47B540C089B6028B04E3@xmb-rtp-20b.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
Thread-Index: AccMxVfsMbZwS4EuTxGPLQXvXHFIlQB3N3nQ
From: "Rajiv Asati \(rajiva\)" <rajiva@cisco.com>
To: "Yakov Rekhter" <yakov@juniper.net>, <idr@ietf.org>
X-OriginalArrivalTime: 23 Nov 2006 01:54:17.0156 (UTC)
	FILETIME=[48C2B840:01C70EA2]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1159; t=1164246859;
	x=1165110859; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rajiva@cisco.com;
	z=From:=20=22Rajiv=20Asati=20\(rajiva\)=22=20<rajiva@cisco.com>
	|Subject:=20RE=3A=20[Idr]=20draft-lefaucheur-idr-v4nlri-v6nh-00.txt
	|Sender:=20
	|To:=20=22Yakov=20Rekhter=22=20<yakov@juniper.net>,=20<idr@ietf.org>;
	bh=Y1UaWkWepy7Fd/tM9vdpijcmPEL8jLBuCioJyMEXZnM=;
	b=r4h63eXOcoMS+A5tO1+ET151+97Btj+hljnOsgwkiCewXTN1jYUuWigBB4J9xdaitF/Xu4nG
	r/f2EY+UVBKYFgltPBPBNB2dWb0HPwWCxDd7zFykLYU96Ag9y8wS2joo;
Authentication-Results: rtp-dkim-1; header.From=rajiva@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: 
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 support the adoption of this draft as the WG item.=20

Cheers,
Rajiv

> -----Original Message-----
> From: Yakov Rekhter [mailto:yakov@juniper.net]=20
> Sent: Monday, November 20, 2006 11:58 AM
> To: idr@ietf.org
> Subject: [Idr] draft-lefaucheur-idr-v4nlri-v6nh-00.txt
>=20
> Folks,
>=20
> Please comment on the attached. The deadline for comments is
> Dec 1, 2006.
>=20
> Yakov.
> ------- Forwarded Message
>=20
> 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
>=20
> At  the  IDR  WG  meeting  last  week,  we  discussed =20
> draft-lefaucheur-idr-
> v4nlri-v6nh.  I would like to propose now  that this be=20
> adopted as an IDR WG
> document.  Your feedback is invited.=20
>=20
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr
>=20
> ------- End of Forwarded Message
>=20
>=20
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www1.ietf.org/mailman/listinfo/idr
>=20

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



From idr-bounces@ietf.org Tue Nov 28 09:02:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gp3Un-0004ZI-HR; Tue, 28 Nov 2006 08:59:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gp3Um-0004Z9-8X
	for idr@ietf.org; Tue, 28 Nov 2006 08:59:36 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gp3Uj-0000oD-Qo
	for idr@ietf.org; Tue, 28 Nov 2006 08:59:36 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by sj-iport-4.cisco.com with ESMTP; 28 Nov 2006 05:59:28 -0800
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 kASDxSqk032108; 
	Tue, 28 Nov 2006 08:59:28 -0500
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kASDxRDM008008; 
	Tue, 28 Nov 2006 08:59:27 -0500 (EST)
To: idr@ietf.org
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.2
Date: Tue, 28 Nov 2006 08:59:27 -0500
Message-ID: <2962.1164722367@cisco.com>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4655; t=1164722368;
	x=1165586368; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:=20Eric=20Rosen=20<erosen@cisco.com>
	|Subject:=20draft-pmohapat-idr-info-safi |Sender:=20
	|To:=20idr@ietf.org;
	bh=OyFdamiQkOGG7geQflDw3MlD0i0hrIwBnr7yCdZ9BNU=;
	b=R/rvQghvzLjLtCkTJg3Y+gu63ZMPYWabwxF9B7DPpSyv+M0vDUTy/tJBWaEsWsFN6aCQmLJI
	y/w+2/ch/SCZcfduJK4kphNrP0HP1dVsz7Uz4Ji81T1d/h9ZcjtHrHFz;
Authentication-Results: rtp-dkim-2; header.From=erosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Subject: [Idr] draft-pmohapat-idr-info-safi
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.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

At the  IDR WG meeting,  several issues were  raised with respect  to draft-
pmohapat-idr-info-safi-00.txt.  Enclosed is my summary of the issues and how
I would like to address them. 

One issue is whether  the draft proposes a good way of  using BGP to signal,
e.g., multipoint-to-point  L2TPv3 tunnels.   The draft proposed  a dedicated
SAFI  to  be  used   for  distributing  encapsulation  information,  and  in
particular  for doing  the signaling  needed to  set  up multipoint-to-point
L2TPv3  tunnels.  This information  is encoded  in an  "L2TPv3 encapsulation
(optional, transitive)  attribute" which  is attached to  that SAFI,  and is
sent in an update originated by the receiving endpoint of the tunnel.

A  possible  alternative   that  was  suggested  is  to   send  the  "L2TPv3
encapsulation  attribute"  along  with  each  prefix for  which  the  tunnel
endpoint sends an update.  Then one wouldn't need the special purpose SAFI.

I don't  think this is  a very good  alternative, for the  following reason.
The  tunnel endpoint  may be  be  maintaining routing  information for  many
thousands  of prefixes.   If  the encapsulation  information  ever needs  to
change, this would require that each one of the prefixes be updated.

Granted, it  is rare for the  encaps info to  change, and it's not  like one
sends a separate update for each  prefix.  Still, the number of updates does
increase in  proportion to the number  of prefixes (even if  the constant of
proportionality is less than 1), and by using a dedicated SAFI one can avoid
this.  Why send more updates than one needs to? 

Also, if one includes the  encapsulation attribute with each prefix, one has
to  define a  new procedure  whereby  the attribute  is removed  by any  BGP
speaker that  does "next hop self".   I think this means  that the attribute
really  could not  be made  transitive, unless  supported with  a capability
advertisement.   With the  use of  a dedicated  SAFI, no  such  procedure is
needed, the encapsulation attribute is  just handled like any other optional
transitive  attribute.  (Though  perhaps the  two alternatives  don't behave
that  differently,   since  using  a   dedicated  SAFI  would   prevent  the
encapsulation info from passing through any BGP speaker that doesn't support
that SAFI.)

Overall, I think it turns out simpler to use the dedicated SAFI. 

Assuming we use a dedicated  SAFI for encapsulation signaling, another issue
is whether to  use one SAFI for all the  encapsulation protocols, or whether
to use  a different SAFI  for each  one.  It was  suggested that by  using a
different  SAFI  for  each  encapsulation  protocol,  a  BGP  speaker  would
automatically avoid  receiving encaps info for  encapsulation protocols that
it doesn't support.   However, I don't think this is a  good thing.  I think
we want to allow the encaps  info for a particular encapsulation protocol to
pass transparently  through BGP speakers that don't  support that particular
encapsulation  protocol, in  the manner  of optional  transitive attributes.
Certainly we don't want to have to update the route reflectors every time we
add a new encapsulation protocol.  So  I propose to keep a single SAFI which
can carry the encapsulation info for multiple protocols in a as attributes. 

Another issue is  the form of the  NLRI.  We have proposed that  the NLRI be
composed of the IP address of  the BGP speaker originating the update, along
with  a  two-byte  distinguisher.   The distinguisher  doesn't  provide  any
semantics, it  really just gives  you a way  to break the set  of attributes
into  several updates.   That allows  you to  modify and  update one  of the
encapsulation info  attributes without having  to include all the  others in
your  update.  This seems  to me  to be  a reasonable  feature, even  if not
really necessary. 

The final issue has to do with  the name of the new SAFI.  I've assumed that
the updates  might carry  not only encapsulation  info attributes,  but also
other  attributes that  might be  used to  help the  remote  tunnel endpoint
decide  which  encapsulation  to  use.   We've  proposed  that  these  other
attributes be communities or  extended communities.  Once these are allowed,
there's no  way to force  people to include  a particular community  only if
that community has something to  do with encapsulation.  However, as long as
that  is  understood,   I  have  no  problem  with   choosing  a  name  like
"encapsulation  signalling SAFI"  (I guess  it  would be  "encaps SAFI"  for
short.)  

Comments? 

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



From idr-bounces@ietf.org Tue Nov 28 18:29:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpCMt-0002G8-Fj; Tue, 28 Nov 2006 18:28:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GpCMs-0002G3-8g
	for idr@ietf.org; Tue, 28 Nov 2006 18:28:02 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpCMm-0005Nq-KE
	for idr@ietf.org; Tue, 28 Nov 2006 18:28:02 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 28 Nov 2006 15:27:56 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kASNRuwZ004016; 
	Tue, 28 Nov 2006 15:27:56 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kASNRtip022467;
	Tue, 28 Nov 2006 15:27:55 -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); 
	Tue, 28 Nov 2006 15:27:55 -0800
Received: from [10.21.112.220] ([10.21.112.220]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Nov 2006 15:27:55 -0800
Message-ID: <456CC5F7.3060807@cisco.com>
Date: Tue, 28 Nov 2006 15:27:51 -0800
From: Robert Raszuk <raszuk@cisco.com>
Organization: http://raszuk.net/
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: erosen@cisco.com, idr@ietf.org
Subject: Re: [Idr] draft-pmohapat-idr-info-safi
References: <2962.1164722367@cisco.com>
In-Reply-To: <2962.1164722367@cisco.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Nov 2006 23:27:55.0262 (UTC)
	FILETIME=[D4D289E0:01C71344]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7454; t=1164756476;
	x=1165620476; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=raszuk@cisco.com;
	z=From:=20Robert=20Raszuk=20<raszuk@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20draft-pmohapat-idr-info-safi
	|Sender:=20; bh=2xsRDV9ZmR+Kd05espRYMmKzVAiTguP0wf8kXF5qhdE=;
	b=DKQ8w52yGN5VA+XyYaWBvje4ceeDosDyU8mZkt0q8wXplCFBq3EZXSZVoS0uzxIAz5YLyoqJ
	qEIgjWGNW53yp87QyHJSdQKbYIJTmc9Fi53u4ZEoIJEflrvpuJZVaN4V;
Authentication-Results: sj-dkim-2; header.From=raszuk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Cc: 
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: raszuk@cisco.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

Eric & WG,

> Assuming we use a dedicated  SAFI for encapsulation signaling, another
> issue is whether to  use one SAFI for all the  encapsulation
> protocols, or whether to use  a different SAFI  for each  one.

I think your email below would be a good place to consider and get IDR
WG input and comments on one more alternative here.

For the number of years we are observing growing number of essentially
non routing information to be carried in routing protocols.

For IGPs we already have a set of predefined opaque TLVs which are
easily extendable when need arises to carry new information type. The
changes required to the IGP at such event are minimal. Clear separation
of opaque vs routing information also allows to treat and process opaque
info differently if needed.

Few months back when I revisited my former work on bgp auto discovery
the conclusion drawn was that again this is an classic example of opaque
information. So is encapsulation info, configuration parameters and
perhaps few more elements which if exchanged between bgp speakers could
provide a number of new services. Therefor the idea arised to define a
single opaque BGP SAFI with single BGP Informational Attribute which
could be used to carry per each NLRI different sets of non routing
information between interested nodes.

The very preliminary draft has been placed here for your review:
http://raszuk.net/info/draft-raszuk-idr-oid-base-00a.pdf

The official version will be posted for Prague IETF.

One of the major advantage is that BGP would not need to understand nor
process the opaque content. As long as the new opaque SAFI is supported
as well as single attribute known what is exchanged within this
attribute payload would be transparent to BGP code.

It would be client's responsibility to process the carried information
depending (per NLRI key) being router's encapsulation engine, ibgp peer
provisioning module etc ...

I also think that such approach offers very clear (AS IS) migration way
for using a new dedicated flooding distribution model (non BGP based)
without the need for any modification to service clients. And since I
think most of us agree that such a new information distribution protocol
is needed considering in the mean time introduction of a number of
dedicated new SAFIs as well as many new BGP attributes carrying opaque
information only to have the issue with their eminent removal seems not
too optimal.

Comments ?

Cheers,
R.


> At the  IDR WG meeting,  several issues were  raised with respect  to draft-
> pmohapat-idr-info-safi-00.txt.  Enclosed is my summary of the issues and how
> I would like to address them. 
> 
> One issue is whether  the draft proposes a good way of  using BGP to signal,
> e.g., multipoint-to-point  L2TPv3 tunnels.   The draft proposed  a dedicated
> SAFI  to  be  used   for  distributing  encapsulation  information,  and  in
> particular  for doing  the signaling  needed to  set  up multipoint-to-point
> L2TPv3  tunnels.  This information  is encoded  in an  "L2TPv3 encapsulation
> (optional, transitive)  attribute" which  is attached to  that SAFI,  and is
> sent in an update originated by the receiving endpoint of the tunnel.
> 
> A  possible  alternative   that  was  suggested  is  to   send  the  "L2TPv3
> encapsulation  attribute"  along  with  each  prefix for  which  the  tunnel
> endpoint sends an update.  Then one wouldn't need the special purpose SAFI.
> 
> I don't  think this is  a very good  alternative, for the  following reason.
> The  tunnel endpoint  may be  be  maintaining routing  information for  many
> thousands  of prefixes.   If  the encapsulation  information  ever needs  to
> change, this would require that each one of the prefixes be updated.
> 
> Granted, it  is rare for the  encaps info to  change, and it's not  like one
> sends a separate update for each  prefix.  Still, the number of updates does
> increase in  proportion to the number  of prefixes (even if  the constant of
> proportionality is less than 1), and by using a dedicated SAFI one can avoid
> this.  Why send more updates than one needs to? 
> 
> Also, if one includes the  encapsulation attribute with each prefix, one has
> to  define a  new procedure  whereby  the attribute  is removed  by any  BGP
> speaker that  does "next hop self".   I think this means  that the attribute
> really  could not  be made  transitive, unless  supported with  a capability
> advertisement.   With the  use of  a dedicated  SAFI, no  such  procedure is
> needed, the encapsulation attribute is  just handled like any other optional
> transitive  attribute.  (Though  perhaps the  two alternatives  don't behave
> that  differently,   since  using  a   dedicated  SAFI  would   prevent  the
> encapsulation info from passing through any BGP speaker that doesn't support
> that SAFI.)
> 
> Overall, I think it turns out simpler to use the dedicated SAFI. 
> 
> Assuming we use a dedicated  SAFI for encapsulation signaling, another issue
> is whether to  use one SAFI for all the  encapsulation protocols, or whether
> to use  a different SAFI  for each  one.  It was  suggested that by  using a
> different  SAFI  for  each  encapsulation  protocol,  a  BGP  speaker  would
> automatically avoid  receiving encaps info for  encapsulation protocols that
> it doesn't support.   However, I don't think this is a  good thing.  I think
> we want to allow the encaps  info for a particular encapsulation protocol to
> pass transparently  through BGP speakers that don't  support that particular
> encapsulation  protocol, in  the manner  of optional  transitive attributes.
> Certainly we don't want to have to update the route reflectors every time we
> add a new encapsulation protocol.  So  I propose to keep a single SAFI which
> can carry the encapsulation info for multiple protocols in a as attributes. 
> 
> Another issue is  the form of the  NLRI.  We have proposed that  the NLRI be
> composed of the IP address of  the BGP speaker originating the update, along
> with  a  two-byte  distinguisher.   The distinguisher  doesn't  provide  any
> semantics, it  really just gives  you a way  to break the set  of attributes
> into  several updates.   That allows  you to  modify and  update one  of the
> encapsulation info  attributes without having  to include all the  others in
> your  update.  This seems  to me  to be  a reasonable  feature, even  if not
> really necessary. 
> 
> The final issue has to do with  the name of the new SAFI.  I've assumed that
> the updates  might carry  not only encapsulation  info attributes,  but also
> other  attributes that  might be  used to  help the  remote  tunnel endpoint
> decide  which  encapsulation  to  use.   We've  proposed  that  these  other
> attributes be communities or  extended communities.  Once these are allowed,
> there's no  way to force  people to include  a particular community  only if
> that community has something to  do with encapsulation.  However, as long as
> that  is  understood,   I  have  no  problem  with   choosing  a  name  like
> "encapsulation  signalling SAFI"  (I guess  it  would be  "encaps SAFI"  for
> short.)  
> 
> Comments? 
> 
> _______________________________________________
> 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



