From idr-bounces@ietf.org Tue Jan 08 00:18:37 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JC6pT-00070r-Mc; Tue, 08 Jan 2008 00:16:47 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JC6pS-0006pV-Kr
	for idr@ietf.org; Tue, 08 Jan 2008 00:16:46 -0500
Received: from otm-mgo00.iij.ad.jp ([210.138.20.174])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JC6pR-0000Ud-RO
	for idr@ietf.org; Tue, 08 Jan 2008 00:16:46 -0500
DKIM-Signature: v=1;a=rsa-sha256;c=relaxed/simple;d=iij.ad.jp;h=From:To:
	Subject:Mime-Version:Content-Type:Message-Id:Date; i=kura@iij.ad.jp;
	s=omgo0; t= 1199769403; x=1200979003;
	bh=euc/KZGBCtfoKBF6UHBgVKhYvDbS6SUqjd9+ooGDXjw=; b=d1K
	H71ecKTxY68c+njpL4qJt8bz3KELXABnKUUPSrGn8hZ2o7CXmPEk/u1eD9l8g07GVQ5ynBMvV/z/3
	Ix/LYjNhxd5NhOVBZ4MryKqhUYyVS1wyCuLtpUasRQrRJzyY6LRh5mrekg1l10TUlS8qTBN3Iq6h5
	POIoPheFyT2EsE=;
Received: OTM-MO(otm-mgo00) id m085GhxP064849;
	Tue, 8 Jan 2008 14:16:43 +0900 (JST)
Received: OTM-MIX(otm-mix00) id m085Ghrp061357;
	Tue, 8 Jan 2008 14:16:43 +0900 (JST)
Received: from melchior.iij.ad.jp (melchior.iij.ad.jp [192.168.168.33])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp01) id m085Ggh6083651
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <idr@ietf.org>; Tue, 8 Jan 2008 14:16:43 +0900 (JST)
Received: by melchior.iij.ad.jp (Postfix)
	id D1B9623384; Tue,  8 Jan 2008 14:16:42 +0900 (JST)
From: kura@iij.ad.jp
To: idr@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Mailer: mnews [version 1.22PL7] 2003-09/29(Mon)
Message-Id: <20080108051642.D1B9623384@melchior.iij.ad.jp>
Date: Tue,  8 Jan 2008 14:16:42 +0900 (JST)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Subject: [Idr] recommendation for iBGP multipath plus IGP multipath
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 all,

I'm searching drafts, papers, presentation slides, etc. in regard to
the recommendation for traffic dividing under iBGP multipath plus IGP
multipath environment, because I have observed different behaviours
through my test with some production routers. Would you please give
me any information of this case if you have?

Best regards,
-- 
Tomohiko Kurahashi <kura@iij.ad.jp>

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



From idr-bounces@ietf.org Wed Jan 09 08:12:31 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCahY-0003cv-W4; Wed, 09 Jan 2008 08:10:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCahX-0003cl-3L
	for idr@ietf.org; Wed, 09 Jan 2008 08:10:35 -0500
Received: from exprod7og111.obsmtp.com ([64.18.2.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCahU-0006a2-NU
	for idr@ietf.org; Wed, 09 Jan 2008 08:10:35 -0500
Received: from source ([66.129.224.36]) by exprod7ob111.postini.com
	([64.18.6.12]) with SMTP; Wed, 09 Jan 2008 05:10:27 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 9 Jan 2008 05:02:54 -0800
Received: from [172.26.250.99] ([172.26.250.99])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m09D2m912375;
	Wed, 9 Jan 2008 05:02:53 -0800 (PST)
	(envelope-from raszuk@juniper.net)
Message-ID: <4784C5EF.1070806@juniper.net>
Date: Wed, 09 Jan 2008 05:02:39 -0800
From: Robert Raszuk <raszuk@juniper.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <200801061814.m06IE8920382@magenta.juniper.net>
	<22AB40E0-1660-4B9D-BA74-B1CB98EB0882@cisco.com>
	<47813E05.2050602@juniper.net>
	<A627A8DF-42D2-4701-A6D5-1C8102537A41@cisco.com>
	<4781FFEA.8050800@juniper.net> <4782170D.2040200@cisco.com>
	<478252F3.4000809@juniper.net> <4782D04B.50703@gmail.com>
	<47832402.9090001@cisco.com> <47833D03.7050005@juniper.net>
	<4783E670.5080003@gmail.com> <4783EA14.2030900@juniper.net>
	<4783F0B8.3070401@gmail.com> <4783F4A8.2000506@juniper.net>
	<792E56AD-25FB-4942-B649-FAF12DBEFD77@muada.com>
In-Reply-To: <792E56AD-25FB-4942-B649-FAF12DBEFD77@muada.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jan 2008 13:02:54.0173 (UTC)
	FILETIME=[F28EB8D0:01C852BF]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: idr <idr@ietf.org>
Subject: [Idr] Re: BGP issues
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: raszuk@juniper.net
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 Iljitsch,

As we are discussing BGP i am redirecting this to idr list for IDR WG to 
comment or work on.

>> But I would like to also see the real list of what are the issue in 
>> BGP we are trying to address ... Is this point-to-point model, is this 
>> TCP transport, is this update format ... No one yet stated what is 
>> broken. And when we do not know what is broken .. or which link of BGP 
>> chain is fragile it is quite a challenge to design new thing around 
>> the unknown.
> 
> In addition to the fact that it's possible to configure iBGP such that 
> you can have routing loops?

Could you provide an example ?

> it suffers from some of the problems inherent to distance vector
> routing, such as slow convergence

BGP can converge today in subseconds. More over BGP routes with correct 
implementation may converge in prefix independent manner. It is not that 
BGP is slow. The vast majority of end to end convergence is a product of 
failure localization, failure detection time and failure propagation 
time. BGP can be made even today to propagate more then one path within 
given AS when best external functionality is in place. Ask your 
favourite vendor for details. More over there are also proposals 
discussed at IDR to send more then best path in BGP.

 > Another problem area for
> BGP is the fact that all processing happens on a per-prefix basis: there
> is no way to communicate reachability or policy changes except to update
> all impacted prefixes. 

Not true. There is proposal for BGP aggregate withdraw. Prefixes can be 
aggregated itself by it's mask. There ways to distribute policies 
without attaching them to the prefixes (example: rt-constrain).

> BGP is extremely agnostic as to the underlying
> path selection algorithm in order to accommodate as much policy control
> as possible.

Accommodating policies is not a BGP protocol requirement but it comes 
from operators using this protocol to fit their operational needs.

> Unfortunately, this makes it very hard to predict BGP's
> behavior and the default behavior (especially with today's rather flat
> AS hierarchy) is more often than not suboptimal. BGP allows harmful
> policies that keep the protocol from converging to a stable state.

Again this is not BGP which allows to configure harmful policies. 
Policies can be harmful indeed as there is no mechanism or in any way 
control on them. If in IGP you block LSA flooding on all links of the 
other routers in IGP peers would you call this an OSPF fault that your 
router is somehow not seen by the rest of them ?

 > Lack
> of workable aggregation mechanisms means that once an address block is
> deaggregated, it's almost impossible to get rid of the resulting long
> prefixes, leading to excessive growth of the internet's global routing
> table. 

Correct. I think we agree that scalable multi-homing should be solved. 
Perhaps a way to do that is to use PI address spaces, perhaps shim6, or 
berhaps just to decouple sending all in one flat BGP as is today. 
Protocol IMHO is ready for 2 tier hierarchy with no protocol changes 
required.

> Coarseness of the only available end-to-end metric (the AS path)
> pushes operators to deaggregation for traffic engineering purposes. 

What other metrics would you recommend to add to BGP and how that would 
that reduce deaggregation ?

> The
> way BGP operates within a single AS requires an additional intra-domain
> routing protocol 

IMHO this is a feature not a bug. In fact for convergence reasons this 
is a very useful feature to have fast IGP.

> and suboptimal engineering tradeoffs by requiring
> having a full mesh between all BGP routers within the AS or having route
> reflectors or a confederation. 

That problem has been solved today. Within any domain you can run 
encpasulation of your choice between ASBRs and non of the routers in the 
core need to have any BGP routes.

> There is no validation of routing
> information beyond the next hop. 

Are you alluding to S-BGP/so-BGP proposals ? If not what other 
validation would be required ?

> A BGP speaker only communicates its
> best path (if any) to a neighbor, with no way to tie additional
> information to the nonexistence of a path and no way to accomplish type
> of service routing or install backup paths. 

Discussed that one above.

 > Paths must be explicitly
> revoked, which in practice requires a BGP speaker to keep track of which
> paths were communicated to which peer. 

Not today. Today you revoke the prefix not the path. When the ability to 
send more then best path is added true .. paths would have to be 
explicitly revoked. Any other proposal in RRG does the very same. 
Readvertisement of EID with new list of locators is an explicit 
modification.

> BGP requires fairly extensive
> configuration (setting up filters) before it's useful.

It could be just one line if you like to send/accept everything to/from 
your peer.

Cheers,
R.


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



From idr-bounces@ietf.org Fri Jan 11 11:29:29 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDMkq-00066H-Fd; Fri, 11 Jan 2008 11:29:12 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDMko-000666-PE
	for idr@ietf.org; Fri, 11 Jan 2008 11:29:10 -0500
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JDMkn-0002b7-PX
	for idr@ietf.org; Fri, 11 Jan 2008 11:29:10 -0500
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m0BGT0Tr086168
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 11 Jan 2008 17:29:01 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Message-Id: <7006D2FB-DE3D-4DB2-80FF-B16D21C2347B@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: raszuk@juniper.net
In-Reply-To: <4784C5EF.1070806@juniper.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Date: Fri, 11 Jan 2008 17:29:01 +0100
References: <200801061814.m06IE8920382@magenta.juniper.net>
	<22AB40E0-1660-4B9D-BA74-B1CB98EB0882@cisco.com>
	<47813E05.2050602@juniper.net>
	<A627A8DF-42D2-4701-A6D5-1C8102537A41@cisco.com>
	<4781FFEA.8050800@juniper.net> <4782170D.2040200@cisco.com>
	<478252F3.4000809@juniper.net> <4782D04B.50703@gmail.com>
	<47832402.9090001@cisco.com> <47833D03.7050005@juniper.net>
	<4783E670.5080003@gmail.com> <4783EA14.2030900@juniper.net>
	<4783F0B8.3070401@gmail.com> <4783F4A8.2000506@juniper.net>
	<792E56AD-25FB-4942-B649-FAF12DBEFD77@muada.com>
	<4784C5EF.1070806@juniper.net>
X-Mailer: Apple Mail (2.915)
X-Spam-Status: No, score=-2.4 required=3.5 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Cc: idr <idr@ietf.org>
Subject: [Idr] Re: BGP issues
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 9 jan 2008, at 14:02, Robert Raszuk wrote:

> As we are discussing BGP i am redirecting this to idr list for IDR  
> WG to comment or work on.

Ah, I saw that you wrote a reply but I couldn't find it at first.  :-)

>> In addition to the fact that it's possible to configure iBGP such  
>> that you can have routing loops?

> Could you provide an example ?

R1e - R2i - R3i - R4e

If R1 and R4 both prefer their eBGP path towards a certain destination  
and then R2 prefers the path over R4 while R3 prefers the path over  
R1, packets will loop between R2 and R3. Note that this configuration  
only happens when applying policy to iBGP sessios or in unfortunate  
route reflector placement.

>> it suffers from some of the problems inherent to distance vector
>> routing, such as slow convergence

> BGP can converge today in subseconds.

Sure, but it can also take many minutes, especially with a min-route- 
advertisement timer in effect in many places and if the update is a  
withdrawl. Now I've argued that this shouldn't be too problematic  
because if you're revoking your advertisement that means you're  
unreachable anyway, but not everyone agrees with that. (Not good if  
you are revoking a more specific and you want the aggregate to attract  
the traffic.)

One reason that BGP is getting chattier is because updates tend to be  
multiplied if there are several interconnects between two ASes.

> > Another problem area for
>> BGP is the fact that all processing happens on a per-prefix basis:  
>> there
>> is no way to communicate reachability or policy changes except to  
>> update
>> all impacted prefixes.

> Not true. There is proposal for BGP aggregate withdraw.

I'm talking about what's out there, not about what's proposed. Very  
little of what is proposed makes it to wide deployment.

>> BGP is extremely agnostic as to the underlying
>> path selection algorithm in order to accommodate as much policy  
>> control
>> as possible.

> Accommodating policies is not a BGP protocol requirement but it  
> comes from operators using this protocol to fit their operational  
> needs.

Sure, but in my opinion, BGP takes it a bit too far, it's too easy to  
shoot yourself in the foot. Or, in other words: a routing protocol  
that allows loops is doing something wrong.

>> Unfortunately, this makes it very hard to predict BGP's
>> behavior and the default behavior (especially with today's rather  
>> flat
>> AS hierarchy) is more often than not suboptimal. BGP allows harmful
>> policies that keep the protocol from converging to a stable state.

> Again this is not BGP which allows to configure harmful policies.  
> Policies can be harmful indeed as there is no mechanism or in any  
> way control on them. If in IGP you block LSA flooding on all links  
> of the other routers in IGP peers would you call this an OSPF fault  
> that your router is somehow not seen by the rest of them ?

The difference is that in OSPF filtering LSAs is not supported by  
reasonable implementations because that is incompatible with the SPF  
architecture, while in BGP policies are fully supported by design,  
even some harmful ones.

> > Lack
>> of workable aggregation mechanisms means that once an address block  
>> is
>> deaggregated, it's almost impossible to get rid of the resulting long
>> prefixes, leading to excessive growth of the internet's global  
>> routing
>> table.

> Correct. I think we agree that scalable multi-homing should be solved.

And scalable traffic engineering. Remember that at least 200000  
prefixes in the DFZ are NOT the result of multihoming using the one  
AS / one prefix model.

>> Coarseness of the only available end-to-end metric (the AS path)
>> pushes operators to deaggregation for traffic engineering purposes.

> What other metrics would you recommend to add to BGP and how that  
> would that reduce deaggregation ?

I would like to see a value that is increased by every AS (twice, for  
good measure: once on reception, once on transmission), but not by  
one, but by a value (say) between 1 and 127, with a default in the  
middle (11). So where you'd see an AS path length 3 today, you'd see a  
metric value 66 if nobody in the path changed the default. But if  
someone wants to make this path just a little better or a little  
worse, they can make it 65 or 67. This allows finer grained control  
that the AS path so it reduces the need for deaggregation for TE  
purposes.

>> The
>> way BGP operates within a single AS requires an additional intra- 
>> domain
>> routing protocol

> IMHO this is a feature not a bug. In fact for convergence reasons  
> this is a very useful feature to have fast IGP.

It also adds tons of complexity, especially if you don't want to have  
a full iBGP mesh. I'm not saying you shouldn't have an IGP, I'm saying  
you shouldn't _have_ to have an IGP.

>> There is no validation of routing
>> information beyond the next hop.

> Are you alluding to S-BGP/so-BGP proposals ?

Yes, to their problem statement, at least. Not sure if drowning  
everything in sticky crypto syrup is the best solution, though.

> > Paths must be explicitly
>> revoked, which in practice requires a BGP speaker to keep track of  
>> which
>> paths were communicated to which peer.

> Not today. Today you revoke the prefix not the path.

Path in the sense of "a prefix learned over a specific eBGP session".

> When the ability to send more then best path is added true .. paths  
> would have to be explicitly revoked. Any other proposal in RRG does  
> the very same.

It would be better if implementations wouldn't have to keep track of  
what they sent where. However, this is probably relatively easy to fix  
("start now" .... "forget all the prefixes that I haven't refreshed  
since "start now"") but the fix will probably be hard to deploy.

>> BGP requires fairly extensive
>> configuration (setting up filters) before it's useful.

> It could be just one line if you like to send/accept everything to/ 
> from your peer.

Yes, and I'm happy this setup is so easy to configure every single  
time I have any use for it.  </sarcasm>

Iljitsch

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



From idr-bounces@ietf.org Fri Jan 11 12:02:20 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDNG1-00087m-Ht; Fri, 11 Jan 2008 12:01:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDNG0-00087h-1d
	for idr@ietf.org; Fri, 11 Jan 2008 12:01:24 -0500
Received: from exprod7og104.obsmtp.com ([64.18.2.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDNFz-0000nt-96
	for idr@ietf.org; Fri, 11 Jan 2008 12:01:24 -0500
Received: from source ([66.129.224.36]) by exprod7ob104.postini.com
	([64.18.6.12]) with SMTP; Fri, 11 Jan 2008 09:01:18 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 11 Jan 2008 08:57:55 -0800
Received: from [172.26.250.99] ([172.26.250.99])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m0BGvs985493;
	Fri, 11 Jan 2008 08:57:55 -0800 (PST)
	(envelope-from raszuk@juniper.net)
Message-ID: <4787A011.3070309@juniper.net>
Date: Fri, 11 Jan 2008 08:57:53 -0800
From: Robert Raszuk <raszuk@juniper.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <200801061814.m06IE8920382@magenta.juniper.net>
	<22AB40E0-1660-4B9D-BA74-B1CB98EB0882@cisco.com>
	<47813E05.2050602@juniper.net>
	<A627A8DF-42D2-4701-A6D5-1C8102537A41@cisco.com>
	<4781FFEA.8050800@juniper.net> <4782170D.2040200@cisco.com>
	<478252F3.4000809@juniper.net> <4782D04B.50703@gmail.com>
	<47832402.9090001@cisco.com> <47833D03.7050005@juniper.net>
	<4783E670.5080003@gmail.com> <4783EA14.2030900@juniper.net>
	<4783F0B8.3070401@gmail.com> <4783F4A8.2000506@juniper.net>
	<792E56AD-25FB-4942-B649-FAF12DBEFD77@muada.com>
	<4784C5EF.1070806@juniper.net>
	<7006D2FB-DE3D-4DB2-80FF-B16D21C2347B@muada.com>
In-Reply-To: <7006D2FB-DE3D-4DB2-80FF-B16D21C2347B@muada.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Jan 2008 16:57:55.0801 (UTC)
	FILETIME=[1C9BE490:01C85473]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: idr <idr@ietf.org>
Subject: [Idr] Re: BGP issues
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: raszuk@juniper.net
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 Iljitsch,

>>> In addition to the fact that it's possible to configure iBGP such 
>>> that you can have routing loops?
> 
>> Could you provide an example ?
> 
> R1e - R2i - R3i - R4e
> 
> If R1 and R4 both prefer their eBGP path towards a certain destination 
> and then R2 prefers the path over R4 while R3 prefers the path over R1, 
> packets will loop between R2 and R3. Note that this configuration only 
> happens when applying policy to iBGP sessios or in unfortunate route 
> reflector placement.

Altering best path selection on IBGP routers is a bad idea when you have 
hop by hop switching.

>> BGP can converge today in subseconds.
> 
> Sure, but it can also take many minutes, especially with a 
> min-route-advertisement timer in effect in many places and if the update 
> is a withdrawl. Now I've argued that this shouldn't be too problematic 
> because if you're revoking your advertisement that means you're 
> unreachable anyway, but not everyone agrees with that. (Not good if you 
> are revoking a more specific and you want the aggregate to attract the 
> traffic.)
> 
> One reason that BGP is getting chattier is because updates tend to be 
> multiplied if there are several interconnects between two ASes.

Just to clarify here .. what I call convergence is in fact reachability 
restoration. And that is in vast majority of cases just the thing within 
your AS or at most to your peering AS.

As long as reachability is restored (even if temporarily in an 
suboptimal fashion) does not impact user's traffic. Then BGP can take as 
long as it likes to "converge" to an optimal path as long as 
reachability is in place. That IMHO should be the focus.

>> Not true. There is proposal for BGP aggregate withdraw.
> 
> I'm talking about what's out there, not about what's proposed. Very 
> little of what is proposed makes it to wide deployment.

If you say that very little on what is proposed or what vendors ship 
makes it to the actual wide deployment what could we say about something 
which is not even proposed yet ? Should we sit and do nothing for years 
to come ???

>> Accommodating policies is not a BGP protocol requirement but it comes 
>> from operators using this protocol to fit their operational needs.
> 
> Sure, but in my opinion, BGP takes it a bit too far, it's too easy to 
> shoot yourself in the foot. Or, in other words: a routing protocol that 
> allows loops is doing something wrong.

See the problem is that loops can form with bad policies. And it would 
not be that hard to detect them algorithmically. The problem is that no 
operators wants to share his polices to others. So while you could quite 
easy come out with the intra-domain policy verifier .. doing the same 
inter-domain is a non technical challenge. I don't think BGP or any 
other protocol would do any magic if there is no data at hand to work on.

>> What other metrics would you recommend to add to BGP and how that 
>> would that reduce deaggregation ?
> 
> I would like to see a value that is increased by every AS (twice, for 
> good measure: once on reception, once on transmission), but not by one, 
> but by a value (say) between 1 and 127, with a default in the middle 
> (11). So where you'd see an AS path length 3 today, you'd see a metric 
> value 66 if nobody in the path changed the default. But if someone wants 
> to make this path just a little better or a little worse, they can make 
> it 65 or 67. This allows finer grained control that the AS path so it 
> reduces the need for deaggregation for TE purposes.

Hmmmm that's an idea ... Perhaps you should write a brief draft on it ?


>> IMHO this is a feature not a bug. In fact for convergence reasons this 
>> is a very useful feature to have fast IGP.
> 
> It also adds tons of complexity, especially if you don't want to have a 
> full iBGP mesh. I'm not saying you shouldn't have an IGP, I'm saying you 
> shouldn't _have_ to have an IGP.

IMHO recursive protocol should recurse via something. And for 
intra-domain reachability restoration bgp is not the best choice. I saw 
in the past some attempts to use iBGP as an IGP but it is IMHO a very 
bad idea limited to very few specific topologies.

The issue is that intra and inter domain requirements for routing 
protocol are very different and diverse. It is a challenge to come up 
with a huge protocol to do all .. as such would not do anything very 
good. On that grounds I do believe that we should have precise tools for 
  different jobs. For the same reason I have a big workshop in my garage 
not to have bend wires, cut wood or unscrew car bolts all with one set 
of pliers.

>> When the ability to send more then best path is added true .. paths 
>> would have to be explicitly revoked. Any other proposal in RRG does 
>> the very same.
> 
> It would be better if implementations wouldn't have to keep track of 
> what they sent where. However, this is probably relatively easy to fix 
> ("start now" .... "forget all the prefixes that I haven't refreshed 
> since "start now"") but the fix will probably be hard to deploy.

Then you would loose the huge benefit of BGP to be an incremental protocol !

Cheers,
R.


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



From idr-bounces@ietf.org Fri Jan 11 12:54:49 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JDO5W-0003Rj-2G; Fri, 11 Jan 2008 12:54:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JDO5S-0003Ra-Qe
	for idr@ietf.org; Fri, 11 Jan 2008 12:54:36 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDO5R-0001n1-MW
	for idr@ietf.org; Fri, 11 Jan 2008 12:54:34 -0500
X-IronPort-AV: E=Sophos;i="4.24,272,1196658000"; d="scan'208";a="83071623"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 11 Jan 2008 12:54:12 -0500
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 m0BHsCml013132; 
	Fri, 11 Jan 2008 12:54:12 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m0BHro77016967; 
	Fri, 11 Jan 2008 17:54:08 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 11 Jan 2008 12:54:00 -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] Re: BGP issues
Date: Fri, 11 Jan 2008 12:53:18 -0500
Message-ID: <15B86BC7352F864BB53A47B540C089B604B69BF1@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <7006D2FB-DE3D-4DB2-80FF-B16D21C2347B@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] Re: BGP issues
Thread-Index: AchUbywJMWRu9O/5RtuDC6cErIDU7wAA49tQ
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>, <raszuk@juniper.net>
X-OriginalArrivalTime: 11 Jan 2008 17:54:00.0290 (UTC)
	FILETIME=[F2002C20:01C8547A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=11172; t=1200074052;
	x=1200938052; 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]=20Re=3A=20BGP=20issues |Sender:=20
	|To:=20=22Iljitsch=20van=20Beijnum=22=20<iljitsch@muada.com
	>,=20<raszuk@juniper.net>;
	bh=oRC4SqYKkCo82wVqKKjDYM/ELWANeOjRmq1sn1eLvDg=;
	b=KZ2XqZfELZFohdKuU/R4qWJm7pnkALRJVCKonsRWxURoLgYofxKO1CEhwi
	0ri1zB2nnDPdVnO6YdfW56wfjgO59tTy4tMBQwW3oCOzYHoVNMa6nyDY0g66
	bDHzt3RDbV;
Authentication-Results: rtp-dkim-1; header.From=rajiva@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 10d2fdecab7a7fa796e06e001d026c91
Cc: idr <idr@ietf.org>
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Errors-To: idr-bounces@ietf.org

Hi Iljitsch,

Good points. However, we should not mix up 'what's deployed' with
'what's a allowed by the protocol'.

By all means, the BGP traffic engineering and BGP deaggregation points
are worthy of further discussion.=20

> worse, they can make it 65 or 67. This allows finer grained control =20
> that the AS path so it reduces the need for deaggregation for TE =20
> purposes.

I think that you are alluding to enabling each transient AS to attach
its relevant weight/preference for each BGP prefix. This furhter enables
each AS to get end-to-end metric for each prefix with or without the
AS_PATH. Correct?

While I agree that it may help wrt TE, but it doesn't fully solve the
deaggregation. For example, a network may advertise one chunk of
prefixes (bunch of /24s) to one AS and antoher chunk (bunch of /24s) to
another AS to receive the traffic accordingly from different Ases,
though the network could have advertised one aggregate /23 (say).

> >> There is no validation of routing
> >> information beyond the next hop.
>=20
> > Are you alluding to S-BGP/so-BGP proposals ?
>=20
> Yes, to their problem statement, at least. Not sure if drowning =20
> everything in sticky crypto syrup is the best solution, though.

I agree with you to this point. Perhaps, you would prefer something like
the IRV -
http://www3.ietf.org/proceedings/02nov/slides/rpsec-6/index.html


Regarding other points, please see inline,

> >> In addition to the fact that it's possible to configure iBGP such =20
> >> that you can have routing loops?

Your example to create routing loop in BGP by (mis)using policies is
somewhat valid.  But, one can create loops by just configuring static
routes. It is quite subjective to characterize what's easy to shoot and
what's not.

BGP policies provide a toolkit to help making educated designs. Yes,
they are good if used appropriately, and bad, if not used appropriately.
That's why there are guidelines. The policies are meant to aid the one's
preference of tweaking the result of protocol at one's own expense.=20

I think that the better question would be - should the protocol
claim/advertise the reachability for a certain prefix, when the
reachability may not exist in the forwarding plane?=20


> The difference is that in OSPF filtering LSAs is not supported by =20
> reasonable implementations because that is incompatible with the SPF =20
> architecture, while in BGP policies are fully supported by design, =20
> even some harmful ones.

This is an apple to orange comparision. Firstly, the OSPF specification
(RFC2328 section 3) allows for unidentical link-state database in an AS
(due to introduction of areas).

Secondly, independent of filtering, one can infuse a policy to deny OSPF
to install a route in the routing table. So, while the neighbors can
send the traffic for that route, the router will either drop it or
forward it as per the less specific route. One may end up with loop.
Again, nothing to do with protocol itself.

> Sure, but it can also take many minutes, especially with a min-route-=20
> advertisement timer in effect in many places and if the update is a =20
> withdrawl. Now I've argued that this shouldn't be too problematic =20

Well, the min-route-advertisement timer is meant to help in reacting to
every routing change faster or slower. Well, one may argue that it is
advantageous to tune the timer according to one's preference and one's
understanding of the network(s).


> It also adds tons of complexity, especially if you don't want=20
> to have =20
> a full iBGP mesh. I'm not saying you shouldn't have an IGP,=20
> I'm saying you shouldn't _have_ to have an IGP.

Agreed.=20
BGP mustn't mandate the usage of IGP, and it doesn't.
One can use static routes to reach the next-hops, and obviate IGP
altogether.
~~~~~~~~~~~~~

Cheers,
Rajiv

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]=20
> Sent: Friday, January 11, 2008 11:29 AM
> To: raszuk@juniper.net
> Cc: idr
> Subject: [Idr] Re: BGP issues
>=20
> On 9 jan 2008, at 14:02, Robert Raszuk wrote:
>=20
> > As we are discussing BGP i am redirecting this to idr list for IDR =20
> > WG to comment or work on.
>=20
> Ah, I saw that you wrote a reply but I couldn't find it at first.  :-)
>=20
> >> In addition to the fact that it's possible to configure iBGP such =20
> >> that you can have routing loops?
>=20
> > Could you provide an example ?
>=20
> R1e - R2i - R3i - R4e
>=20
> If R1 and R4 both prefer their eBGP path towards a certain=20
> destination =20
> and then R2 prefers the path over R4 while R3 prefers the path over =20
> R1, packets will loop between R2 and R3. Note that this=20
> configuration =20
> only happens when applying policy to iBGP sessios or in unfortunate =20
> route reflector placement.
>=20
> >> it suffers from some of the problems inherent to distance vector
> >> routing, such as slow convergence
>=20
> > BGP can converge today in subseconds.
>=20
> Sure, but it can also take many minutes, especially with a min-route-=20
> advertisement timer in effect in many places and if the update is a =20
> withdrawl. Now I've argued that this shouldn't be too problematic =20
> because if you're revoking your advertisement that means you're =20
> unreachable anyway, but not everyone agrees with that. (Not good if =20
> you are revoking a more specific and you want the aggregate=20
> to attract =20
> the traffic.)
>=20
> One reason that BGP is getting chattier is because updates=20
> tend to be =20
> multiplied if there are several interconnects between two ASes.
>=20
> > > Another problem area for
> >> BGP is the fact that all processing happens on a=20
> per-prefix basis: =20
> >> there
> >> is no way to communicate reachability or policy changes except to =20
> >> update
> >> all impacted prefixes.
>=20
> > Not true. There is proposal for BGP aggregate withdraw.
>=20
> I'm talking about what's out there, not about what's proposed. Very =20
> little of what is proposed makes it to wide deployment.
>=20
> >> BGP is extremely agnostic as to the underlying
> >> path selection algorithm in order to accommodate as much policy =20
> >> control
> >> as possible.
>=20
> > Accommodating policies is not a BGP protocol requirement but it =20
> > comes from operators using this protocol to fit their operational =20
> > needs.
>=20
> Sure, but in my opinion, BGP takes it a bit too far, it's too=20
> easy to =20
> shoot yourself in the foot. Or, in other words: a routing protocol =20
> that allows loops is doing something wrong.
>=20
> >> Unfortunately, this makes it very hard to predict BGP's
> >> behavior and the default behavior (especially with today's rather =20
> >> flat
> >> AS hierarchy) is more often than not suboptimal. BGP allows harmful
> >> policies that keep the protocol from converging to a stable state.
>=20
> > Again this is not BGP which allows to configure harmful policies. =20
> > Policies can be harmful indeed as there is no mechanism or in any =20
> > way control on them. If in IGP you block LSA flooding on all links =20
> > of the other routers in IGP peers would you call this an=20
> OSPF fault =20
> > that your router is somehow not seen by the rest of them ?
>=20
> The difference is that in OSPF filtering LSAs is not supported by =20
> reasonable implementations because that is incompatible with the SPF =20
> architecture, while in BGP policies are fully supported by design, =20
> even some harmful ones.
>=20
> > > Lack
> >> of workable aggregation mechanisms means that once an=20
> address block =20
> >> is
> >> deaggregated, it's almost impossible to get rid of the=20
> resulting long
> >> prefixes, leading to excessive growth of the internet's global =20
> >> routing table.
>=20
> > Correct. I think we agree that scalable multi-homing should=20
> be solved.
>=20
> And scalable traffic engineering. Remember that at least 200000 =20
> prefixes in the DFZ are NOT the result of multihoming using the one =20
> AS / one prefix model.
>=20
> >> Coarseness of the only available end-to-end metric (the AS path)
> >> pushes operators to deaggregation for traffic engineering purposes.
>=20
> > What other metrics would you recommend to add to BGP and how that =20
> > would that reduce deaggregation ?
>=20
> I would like to see a value that is increased by every AS=20
> (twice, for =20
> good measure: once on reception, once on transmission), but not by =20
> one, but by a value (say) between 1 and 127, with a default in the =20
> middle (11). So where you'd see an AS path length 3 today,=20
> you'd see a =20
> metric value 66 if nobody in the path changed the default. But if =20
> someone wants to make this path just a little better or a little =20
> worse, they can make it 65 or 67. This allows finer grained control =20
> that the AS path so it reduces the need for deaggregation for TE =20
> purposes.
>=20
> >> The
> >> way BGP operates within a single AS requires an additional intra-=20
> >> domain
> >> routing protocol
>=20
> > IMHO this is a feature not a bug. In fact for convergence reasons =20
> > this is a very useful feature to have fast IGP.
>=20
> It also adds tons of complexity, especially if you don't want=20
> to have =20
> a full iBGP mesh. I'm not saying you shouldn't have an IGP,=20
> I'm saying =20
> you shouldn't _have_ to have an IGP.
>=20
> >> There is no validation of routing
> >> information beyond the next hop.
>=20
> > Are you alluding to S-BGP/so-BGP proposals ?
>=20
> Yes, to their problem statement, at least. Not sure if drowning =20
> everything in sticky crypto syrup is the best solution, though.
>=20
> > > Paths must be explicitly
> >> revoked, which in practice requires a BGP speaker to keep=20
> track of =20
> >> which
> >> paths were communicated to which peer.
>=20
> > Not today. Today you revoke the prefix not the path.
>=20
> Path in the sense of "a prefix learned over a specific eBGP session".
>=20
> > When the ability to send more then best path is added true=20
> .. paths =20
> > would have to be explicitly revoked. Any other proposal in=20
> RRG does =20
> > the very same.
>=20
> It would be better if implementations wouldn't have to keep track of =20
> what they sent where. However, this is probably relatively=20
> easy to fix =20
> ("start now" .... "forget all the prefixes that I haven't refreshed =20
> since "start now"") but the fix will probably be hard to deploy.
>=20
> >> BGP requires fairly extensive
> >> configuration (setting up filters) before it's useful.
>=20
> > It could be just one line if you like to send/accept everything to/=20
> > from your peer.
>=20
> Yes, and I'm happy this setup is so easy to configure every single =20
> time I have any use for it.  </sarcasm>
>=20
> Iljitsch
>=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 Mon Jan 14 15:55:29 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JEWKo-00047c-5E; Mon, 14 Jan 2008 15:55:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JEWKm-000445-79
	for idr@ietf.org; Mon, 14 Jan 2008 15:55:04 -0500
Received: from bgp.nu ([64.27.28.76])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JEWKl-0005Vo-SJ
	for idr@ietf.org; Mon, 14 Jan 2008 15:55:04 -0500
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id ED39153E0FC;
	Mon, 14 Jan 2008 15:55:02 -0500 (EST)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id trd6AmSgCrCe; Mon, 14 Jan 2008 15:54:57 -0500 (EST)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id C545A53E0F8;
	Mon, 14 Jan 2008 15:54:56 -0500 (EST)
Message-Id: <2C8C3F04-5C5E-4057-B03D-EB2725DC0EE2@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <7006D2FB-DE3D-4DB2-80FF-B16D21C2347B@muada.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [Idr] Re: BGP issues
Date: Mon, 14 Jan 2008 15:54:55 -0500
References: <200801061814.m06IE8920382@magenta.juniper.net>
	<22AB40E0-1660-4B9D-BA74-B1CB98EB0882@cisco.com>
	<47813E05.2050602@juniper.net>
	<A627A8DF-42D2-4701-A6D5-1C8102537A41@cisco.com>
	<4781FFEA.8050800@juniper.net> <4782170D.2040200@cisco.com>
	<478252F3.4000809@juniper.net> <4782D04B.50703@gmail.com>
	<47832402.9090001@cisco.com> <47833D03.7050005@juniper.net>
	<4783E670.5080003@gmail.com> <4783EA14.2030900@juniper.net>
	<4783F0B8.3070401@gmail.com> <4783F4A8.2000506@juniper.net>
	<792E56AD-25FB-4942-B649-FAF12DBEFD77@muada.com>
	<4784C5EF.1070806@juniper.net>
	<7006D2FB-DE3D-4DB2-80FF-B16D21C2347B@muada.com>
X-Mailer: Apple Mail (2.915)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: idr <idr@ietf.org>, John Scudder <jgs@juniper.net>
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 Jan 11, 2008, at 11:29 AM, Iljitsch van Beijnum wrote:
> However, this is probably relatively easy to fix ("start now" ....  
> "forget all the prefixes that I haven't refreshed since "start  
> now"") but the fix will probably be hard to deploy.

If you squint hard enough you will realize that this is available  
today under the name "graceful restart".

--John

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



From idr-bounces@ietf.org Thu Jan 17 07:10:17 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFTXj-0006Rw-6w; Thu, 17 Jan 2008 07:08:23 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFTXi-0006Rg-0j
	for idr@ietf.org; Thu, 17 Jan 2008 07:08:22 -0500
Received: from hibernia.jakma.org ([212.17.55.49])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFTXh-0003YJ-Cm
	for idr@ietf.org; Thu, 17 Jan 2008 07:08:21 -0500
Received: from melandri.lan ([81.168.24.37]) (authenticated bits=0)
	by hibernia.jakma.org (8.14.2/8.14.1) with ESMTP id m0HC7uCL028586
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 17 Jan 2008 12:08:12 GMT
Date: Thu, 17 Jan 2008 12:07:54 +0000 (GMT)
From: Paul Jakma <paul@clubi.ie>
X-X-Sender: paul@localhost.localdomain
To: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [Idr] Re: BGP issues
In-Reply-To: <7006D2FB-DE3D-4DB2-80FF-B16D21C2347B@muada.com>
Message-ID: <alpine.LFD.1.00.0801171205560.6799@localhost.localdomain>
References: <200801061814.m06IE8920382@magenta.juniper.net>
	<22AB40E0-1660-4B9D-BA74-B1CB98EB0882@cisco.com>
	<47813E05.2050602@juniper.net>
	<A627A8DF-42D2-4701-A6D5-1C8102537A41@cisco.com>
	<4781FFEA.8050800@juniper.net> <4782170D.2040200@cisco.com>
	<478252F3.4000809@juniper.net> <4782D04B.50703@gmail.com>
	<47832402.9090001@cisco.com> <47833D03.7050005@juniper.net>
	<4783E670.5080003@gmail.com> <4783EA14.2030900@juniper.net>
	<4783F0B8.3070401@gmail.com> <4783F4A8.2000506@juniper.net>
	<792E56AD-25FB-4942-B649-FAF12DBEFD77@muada.com>
	<4784C5EF.1070806@juniper.net>
	<7006D2FB-DE3D-4DB2-80FF-B16D21C2347B@muada.com>
User-Agent: Alpine 1.00 (LFD 882 2007-12-20)
Mail-Copies-To: paul@jakma.org
X-NSA: al aqsar fluffy jihad cute musharef kittens jet-A1 ear avgas wax
	ammonium bad qran dog inshallah allah al-akbar martyr iraq
	hammas hisballah rabin ayatollah korea revolt pelvix mustard
	gas x-ray british airways washington peroxide cool
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1
	(hibernia.jakma.org [212.17.55.49]);
	Thu, 17 Jan 2008 12:08:17 +0000 (UTC)
X-Virus-Scanned: ClamAV 0.91.2/5489/Thu Jan 17 01:22:56 2008 on
	hibernia.jakma.org
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: idr <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 Fri, 11 Jan 2008, Iljitsch van Beijnum wrote:

> I would like to see a value that is increased by every AS (twice, 
> for good measure: once on reception, once on transmission),

That's one to add to the "AS_PATH reform" list possibly (encoding 
AS_PATHs as {ASN,metric} has been proposed before).

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
Few things are harder to put up with than the annoyance of a good example.
 		-- "Mark Twain, Pudd'nhead Wilson's Calendar"

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



From idr-bounces@ietf.org Thu Jan 31 00:06:33 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKRcl-0003bT-1Q; Thu, 31 Jan 2008 00:06:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKRcj-0003RL-BI
	for idr@ietf.org; Thu, 31 Jan 2008 00:06:05 -0500
Received: from py-out-1112.google.com ([64.233.166.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKRcg-0002vw-Ke
	for idr@ietf.org; Thu, 31 Jan 2008 00:06:05 -0500
Received: by py-out-1112.google.com with SMTP id x19so589717pyg.24
	for <idr@ietf.org>; Wed, 30 Jan 2008 21:06:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	bh=lhEbsZh83tUR+NR3vtBgK7s1iF/7PmtGi+tCod19HVA=;
	b=NE2oPOXGrzD4JqmkRhVcHjEVAgTi65IixLrB1PfJPXwUo/Qmj2HmMyBJWax8BAedvfAr2YSNGKy4qDrdTmtYrP8aSiBBIOXPe0DurUAVRH50BKif+lLHXIR6OagFslW2w8rP0NJFNLQ3LFIynMq5HAbJQ9bSW16m+NC7nEfRBS0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=hVWqYdmsMFRkh6cihxxKcLJ2sTbQ3Jq3mySyxjgSJlregrGFY+ewAjMoZ4YsHpmXNjFIvPU8Otky3G5j/9t/9JLH6PPcqoyqP9ByZUzrNGNze1lG/zU0WN5MQjCuYtyHllGcTmHk4KQBrvCYyHwiUdFEKa2XH/WCHwfuHTfM/X0=
Received: by 10.142.135.9 with SMTP id i9mr873302wfd.211.1201755960900;
	Wed, 30 Jan 2008 21:06:00 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Wed, 30 Jan 2008 21:06:00 -0800 (PST)
Message-ID: <77ead0ec0801302106s13f4dedclac443f86964058a3@mail.gmail.com>
Date: Wed, 30 Jan 2008 21:06:00 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: idr <idr@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_34917_8668606.1201755960921"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f5c1164b9029aa0dd842007e530e24ad
Subject: [Idr] 6PE-Alt draft
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

------=_Part_34917_8668606.1201755960921
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi folks,

We have written a draft which will possibly replace the 6PE RFC. The
6PE RFC uses a label to be sent along with the prefix for each route.
This label is then used as the "VPN label" (keeping with the
terminology of BGP MPLS IP VPN RFC). However the only use the label
serves is to tell the encapsulated packet is an IPv6 packet, as well
as some additional uses as defined in the RFC.

Because a VPN label is required and its only use is to signal that the
inside packet is IPv6, we instead elegantly use the "IPv6 Explicit
NULL label". This label signals the same information. The advantage is
that labels need not be added with the routes and no such extension is
required. It also considerably simplifies the Multi AS scenarios.

The draft will soon be visible in the IETF site and is attached here. I
have removed some sections of the draft temporarily so that the mail
does not bounce from the IDR list.

Thanks,
Vishwas and Manoj

------=_Part_34917_8668606.1201755960921
Content-Type: text/plain; name=draft-manral-idr-mpls-explicit-null-00-short.txt
Content-Transfer-Encoding: base64
X-Attachment-Id: f_fc2ued5f0
Content-Disposition: attachment;
	filename=draft-manral-idr-mpls-explicit-null-00-short.txt

ICAgICAgICAgICAgICAgICAgIA0KSW50ZXJuZXQgRW5naW5lZXJpbmcgVGFzayBGb3JjZSAgICAg
ICAgICAgICAgICAgICAgICAgICAgIFZpc2h3YXMgTWFucmFsDQpJbnRlcm5ldC1EcmFmdCAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTWFub2ogRHV0dGENCklu
dGVuZGVkIHN0YXR1czogU3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAgSVAg
SW5mdXNpb24gSW5jLiAgIA0KRXhwaXJlczogSnVseSAzMCwgMjAwOCAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIEphbnVhcnkgMzAsIDIwMDgNCg0KDQpDb25uZWN0aW5nIElQ
djYgSXNsYW5kcyBvdmVyIElQdjQgTVBMUyBuZXR3b3JrcyB1c2luZyBJUHY2IFByb3ZpZGVyIEVk
Z2UgDQogICAgICAgICAgICAgICAgICAgICAgICBSb3V0ZXJzICg2UEUtQWx0KQ0KICAgICAgICAg
ICAgICAgICAgIGRyYWZ0LW1hbnJhbC1pZHItbXBscy1leHBsaWNpdC1udWxsLTAwLnR4dA0KDQpT
dGF0dXMgb2YgdGhpcyBNZW1vDQoNCiAgIEJ5IHN1Ym1pdHRpbmcgdGhpcyBJbnRlcm5ldC1EcmFm
dCwgZWFjaCBhdXRob3IgcmVwcmVzZW50cyB0aGF0IGFueQ0KICAgYXBwbGljYWJsZSBwYXRlbnQg
b3Igb3RoZXIgSVBSIGNsYWltcyBvZiB3aGljaCBoZSBvciBzaGUgaXMgYXdhcmUNCiAgIGhhdmUg
YmVlbiBvciB3aWxsIGJlIGRpc2Nsb3NlZCwgYW5kIGFueSBvZiB3aGljaCBoZSBvciBzaGUgYmVj
b21lcw0KICAgYXdhcmUgd2lsbCBiZSBkaXNjbG9zZWQsIGluIGFjY29yZGFuY2Ugd2l0aCBTZWN0
aW9uIDYgb2YgQkNQIDc5Lg0KDQogICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1l
bnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZw0KICAgVGFzayBGb3JjZSAoSUVURiksIGl0
cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5vdGUgdGhhdA0KICAgb3RoZXIgZ3Jv
dXBzIG1heSBhbHNvIGRpc3RyaWJ1dGUgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQtDQog
ICBEcmFmdHMuDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlk
IGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocw0KICAgYW5kIG1heSBiZSB1cGRhdGVkLCByZXBs
YWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnkNCiAgIHRpbWUuICBJ
dCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlDQog
ICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVz
cy4iDQoNCiAgIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtRHJhZnRzIGNhbiBiZSBhY2Nl
c3NlZCBhdA0KICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pZXRmLzFpZC1hYnN0cmFjdHMudHh0Lg0K
DQogICBUaGUgbGlzdCBvZiBJbnRlcm5ldC1EcmFmdCBTaGFkb3cgRGlyZWN0b3JpZXMgY2FuIGJl
IGFjY2Vzc2VkIGF0DQogICBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sLg0KDQogICBU
aGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIEp1bHkgMzAsIDIwMDguDQoNCkNvcHly
aWdodCBOb3RpY2UNCg0KICAgQ29weXJpZ2h0IChDKSBUaGUgSUVURiBUcnVzdCAoMjAwOCkuDQoN
CkFic3RyYWN0DQoNCiAgIFRoaXMgZG9jdW1lbnQgcHJvdmlkZXMgYW4gYWx0ZXJuYXRlIG1lY2hh
bmlzbSB0byBbNlBFXSB0byBpbnRlcmNvbm5lY3QgDQogICBJUHY2IHJvdXRlcyBvdmVyIE1QTFMt
ZW5hYmxlZCBJUHY0Y2xvdWRzLiBUaGlzIGFwcHJvYWNoDQoNCg0KDQpNYW5yYWwgYW5kIER1dHRh
ICAgICAgICAgIEV4cGlyZXMgSnVseSAzMCwgMjAwOCAgICAgICAgICAgICAgICAgW1BhZ2UgMV0N
CiANCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAgNlBFLUFsdCAgICAgICAgICAg
ICAgICAgICAgIEphbnVhcnkgMjAwOA0KDQoNCiAgIHJlbGllcyBvbiBJUHY2IFByb3ZpZGVyIEVk
Z2Ugcm91dGVycyAoNlBFLUFsdCkgd2hpY2ggYXJlIER1YWwgU3RhY2sgaW4NCiAgIG9yZGVyIHRv
IGNvbm5lY3QgdG8gSVB2NiBpc2xhbmRzIGFuZCB0byB0aGUgTVBMUyBjb3JlIHdoaWNoIGlzIG9u
bHkNCiAgIHJlcXVpcmVkIHRvIHJ1biBJUHY0IE1QTFMuICBUaGUgNlBFLUFsdCByb3V0ZXJzIGV4
Y2hhbmdlIHRoZSBJUHY2DQogICByZWFjaGFiaWxpdHkgaW5mb3JtYXRpb24gdHJhbnNwYXJlbnRs
eSBvdmVyIHRoZSBjb3JlIHVzaW5nIHRoZSBNdWx0aS0NCiAgIFByb3RvY29sIEJvcmRlciBHYXRl
d2F5IFByb3RvY29sIChNUC1CR1ApIG92ZXIgSVB2NC4gIEluIGRvaW5nIHNvLA0KICAgdGhlIEJH
UCBOZXh0IEhvcCBmaWVsZCBpcyB1c2VkIHRvIGNvbnZleSB0aGUgSVB2NCBhZGRyZXNzIG9mIHRo
ZSA2UEUtQWx0DQogICByb3V0ZXIgc28gdGhhdCBkeW5hbWljYWxseSBlc3RhYmxpc2hlZCBJUHY0
LXNpZ25hbGVkIE1QTFMgTGFiZWwNCiAgIFN3aXRjaGVkIFBhdGhzIChMU1BzKSBjYW4gYmUgdXNl
ZCB3aXRob3V0IGV4cGxpY2l0IHR1bm5lbA0KICAgY29uZmlndXJhdGlvbi4gVW5saWtlIFs2UEVd
IGNhc2UgdGhlIGxhYmVscyBhcmUgbm90IHNlbnQgd2l0aCBlYWNoIHJvdXRlDQogICBhbmQgZG9l
cyBub3QgdXNlIEJHUCB0byB0cmFucG9ydCBsYWJlbHMgW1JGQzMxMDddLiBJdCBpbnN0ZWFkIG1h
a2VzIHVzZQ0KICAgb2YgdGhlIElQdjYgRXhwbGljaXQgTlVMTCBsYWJlbCBhcyB0aGUgVlBOIGxh
YmVsLCB3aGljaCBpcyBkZWZpbmVkIA0KICAgW1JGQzMwMzJdIGFuZCB1cGRhdGVkIGluIFtSRkM0
MTgyXS4gDQoNCiAgIFRoaXMgZG9jdW1lbnQgZWxlZ2FudGx5IHVzZXMgdGhlIGNvbmNlcHQgb2Yg
bm9uIG92ZXJsYXBwaW5nIElQdjYgcm91dGVzIHRvDQogICBwcm92aWRlIEJHUCBNUExTIElQIFZQ
TiBmdW5jdGlvbmFsaXR5LiBUaGUgZG9jdW1lbnQgY2FuIGJlIGZ1cnRoZXIgdXNlZCBmb3IgDQog
ICBwcm92aW5kaW5nIHRoZSBmdW5jdGlvbmFsaXR5IGluIGNhc2Ugb2Ygbm9uLW92ZXJsYXBwaW5n
IElQdjYgcm91dGVzLg0KDQogICBUaGlzIGFwcHJvYWNoIGFsbG93cyBhIGZ1bmN0aW9uYWxpdHkg
c2ltaWxhciB0byBbUkZDNDY1OV0sIHdpdGhvdXQgdGhlIA0KICAgY3VtYnVyc29tZSBleHRlbnNp
b25zIHJlcXVpcmVkIGZvciB0aGUgc2FtZS4gV2l0aCB0aGUgW1JGQzM4NzldIElQdjYgYWRkcmVz
c2VzDQogICBhcmUgbm93IGdsb2JhbGx5IHVuaXF1ZSAoZXhjZXB0IGZvciBMaW5rIGxvY2FsKS4g
SXQgYWxzbyByZWR1Y2VzIHRoZSBudW1iZXIgDQogICBvZiBtdWx0aSBBUyBzY2VuYXJpb3MuDQoN
Cg0KUmVxdWlyZW1lbnRzIExhbmd1YWdlDQoNCiAgIFRoZSBrZXkgd29yZHMgIk1VU1QiLCAiTVVT
VCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9UIiwNCiAgICJTSE9VTEQiLCAi
U0hPVUxEIE5PVCIsICJSRUNPTU1FTkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbiB0aGlz
DQogICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFJGQyAy
MTE5IFtSRkMyMTE5XS4NCg0KDQpUYWJsZSBvZiBDb250ZW50cw0KDQogICAxLiAgSW50cm9kdWN0
aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDMN
CiAgIDIuICBQcm90b2NvbCBPdmVydmlldyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAgNQ0KICAgMy4gIFRyYW5zcG9ydCBvdmVyIElQdjQtc2lnbmFsZWQgTFNQ
cyBhbmQgSVB2NiBsYWJlbCBiaW5kaW5nIC4gLiAuICA2DQogICA0LiAgQ3Jvc3NpbmcgTXVsdGlw
bGUgSVB2NCBBdXRvbm9tb3VzIFN5c3RlbXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDgNCiAgIDUu
ICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAxMA0KICAgNi4gIElBTkEgQ29uc2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDExDQogICA3LiAgQWNrbm93bGVkZ2VtZW50cyAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTENCiAgIDguICBSZWZl
cmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAxMQ0KICAgICA4LjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIDExDQogICAgIDguMi4gIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTINCiAgIEF1dGhvcnMnIEFkZHJl
c3NlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMw0K
ICAgSW50ZWxsZWN0dWFsIFByb3BlcnR5IGFuZCBDb3B5cmlnaHQgU3RhdGVtZW50cyAuIC4gLiAu
IC4gLiAuIC4gLiAuIDE0DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KTWFucmFs
IGFuZCBEdXR0YSAgICAgICAgICBFeHBpcmVzIEp1bHkgMzAsIDIwMDggICAgICAgICAgICAgICAg
IFtQYWdlIDJdDQogDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAgIDZQRS1BbHQg
ICAgICAgICAgICAgICAgICAgICBKYW51YXJ5IDIwMDgNCg0KDQoxLiAgSW50cm9kdWN0aW9uDQoN
CiAgIFRoZXJlIGFyZSBzZXZlcmFsIGFwcHJvYWNoZXMgZm9yIHByb3ZpZGluZyBJUHY2IGNvbm5l
Y3Rpdml0eSBvdmVyIGFuDQogICBNUExTIGNvcmUgbmV0d29yayBbUkZDNDAyOV0gaW5jbHVkaW5n
IChpKSByZXF1aXJpbmcgdGhhdCBNUExTDQogICBuZXR3b3JrcyBzdXBwb3J0IHNldHRpbmcgdXAg
SVB2Ni1zaWduYWxlZCBMYWJlbCBTd2l0Y2hlZCBQYXRocyAoTFNQcykNCiAgIGFuZCBlc3RhYmxp
c2ggSVB2NiBjb25uZWN0aXZpdHkgYnkgdXNpbmcgdGhvc2UgTFNQcywgKGlpKSB1c2UNCiAgIGNv
bmZpZ3VyZWQgdHVubmVsaW5nIG92ZXIgSVB2NC1zaWduYWxlZCBMU1BzLCAoaXYpIHVzZSBbUkZD
NDc5OF0gd2hpY2gNCiAgIHByb3ZpZGVzIHRoZSBzYW1lIGZ1bmN0aW9uYWxpdHkgYXMgdGhpcyBk
cmFmdCBidXQgd2l0aCBhIGxvdCBvZiBhZGRlZCANCiAgIHNpZ25hbGxpbmcgb3IgKGl2KSB1c2Ug
dGhlIElQdjYgUHJvdmlkZXIgRWRnZSAoNlBFLUFsdCkgYXBwcm9hY2ggDQogICBkZWZpbmVkIGlu
IHRoaXMgZG9jdW1lbnQuDQoNCiAgIFRoZSA2UEUtQWx0IGFwcHJvYWNoIGlzIHJlcXVpcmVkIGFz
IGFuIGFsdGVybmF0aXZlIHRvIHRoZSB1c2Ugb2Ygc3RhbmRhcmQNCiAgIHR1bm5lbHMsIGJlY2F1
c2UgaXQgcHJvdmlkZXMgYSBzb2x1dGlvbiBmb3IgYW4gTVBMUyBlbnZpcm9ubWVudCB3aGVyZQ0K
ICAgYWxsIHR1bm5lbHMgYXJlIGVzdGFibGlzaGVkIGR5bmFtaWNhbGx5LCB0aGVyZWJ5IGFkZHJl
c3NpbmcNCiAgIGVudmlyb25tZW50cyB3aGVyZSB0aGUgZWZmb3J0IHRvIGNvbmZpZ3VyZSBhbmQg
bWFpbnRhaW4gZXhwbGljaXRseQ0KICAgY29uZmlndXJlZCB0dW5uZWxzIGlzIG5vdCBhY2NlcHRh
YmxlLiBJdCBpcyBhIGJldHRlciBhcHByb2FjaCB0aGFuIA0KICAgW1JGQzQ3OThdIHdoaWNoIHJl
cXVpcmVzIHRoZSB1c2Ugb2YgYWRkaXRpb25hbCBzaWduYWxsaW5nIG1lY2hhbmlzbXMsIA0KICAg
YW5kIHN0aWxsIGFjaGlldmVzIHRoZSBzYW1lIGZ1bmN0aW9uYWxpdHkuIEl0IHJlcXVpcmVzIG5v
IGFkZGl0aW9uYWwgDQogICBzaWduYWxsaW5nIGV4dGVuc2lvbnMgb3Igb3ZlcmhlYWRzLg0KDQog
ICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBvcGVyYXRpb25zIG9mIHRoZSA2UEUtQWx0IGFwcHJv
YWNoIGZvcg0KICAgaW50ZXJjb25uZWN0aW9uIG9mIElQdjYgaXNsYW5kcyBvdmVyIGFuIElQdjQg
TVBMUyBjbG91ZC4gIFRoZQ0KICAgYXBwcm9hY2ggcmVxdWlyZXMgdGhlIGVkZ2Ugcm91dGVycyB0
aGF0IGFyZSBjb25uZWN0ZWQgdG8gSVB2NiBpc2xhbmRzDQogICB0byBiZSBEdWFsIFN0YWNrIE11
bHRpLVByb3RvY29sLUJHUC1zcGVha2luZyByb3V0ZXJzIFtSRkM0NzYwXQ0KICAgd2hpbGUgdGhl
IGNvcmUgcm91dGVycyBhcmUgb25seSByZXF1aXJlZCB0byBydW4gSVB2NCBNUExTLiAgVGhlDQog
ICBhcHByb2FjaCB1c2VzIE1QLUJHUCBvdmVyIElQdjQsIHJlbGllcyBvbiBpZGVudGlmaWNhdGlv
biBvZiB0aGUgNlBFLUFsdA0KICAgcm91dGVycyBieSB0aGVpciBJUHY0IGFkZHJlc3MgYW5kIHVz
ZXMgSVB2NC1zaWduYWxlZCBNUExTIExTUHMgdGhhdA0KICAgZG9uJ3QgcmVxdWlyZSBhbnkgZXhw
bGljaXQgdHVubmVsIGNvbmZpZ3VyYXRpb24uDQoNCiAgIFRocm91Z2hvdXQgdGhpcyBkb2N1bWVu
dCwgdGhlIHRlcm1pbm9sb2d5IG9mIFtSRkMyNDYwXSBhbmQgW1JGQzQzNjRdDQogICBpcyB1c2Vk
Lg0KDQogICBJbiB0aGlzIGRvY3VtZW50IGFuICdJUHY2IGlzbGFuZCcgaXMgYSBuZXR3b3JrIHJ1
bm5pbmcgbmF0aXZlIElQdjYgYXMNCiAgIHBlciBbUkZDMjQ2MF0uICBBIHR5cGljYWwgZXhhbXBs
ZSBvZiBhbiBJUHY2IGlzbGFuZCB3b3VsZCBiZSBhDQogICBjdXN0b21lcidzIElQdjYgc2l0ZSBj
b25uZWN0ZWQgdmlhIGl0cyBJUHY2IEN1c3RvbWVyIEVkZ2UgKENFKSByb3V0ZXINCiAgIHRvIG9u
ZSAob3IgbW9yZSkgRHVhbCBTdGFjayBQcm92aWRlciBFZGdlIHJvdXRlcihzKSBvZiBhIFNlcnZp
Y2UNCiAgIFByb3ZpZGVyLiBUaGVzZSBJUHY2IFByb3ZpZGVyIEVkZ2Ugcm91dGVycyAoNlBFLUFs
dCkgYXJlIGNvbm5lY3RlZCB0bw0KICAgYW4gSVB2NCBNUExTIGNvcmUgbmV0d29yay4NCg0KDQog
ICAgICAgKy0tLS0tLS0tKw0KICAgICAgIHxzaXRlIEEgIENFLS0tKyAgKy0tLS0tLS0tLS0tLS0t
LS0tKw0KICAgICAgICstLS0tLS0tLSsgICAgfCAgfCAgICAgICAgICAgICAgICAgfCAgICAgICAr
LS0tLS0tLS0rDQogICAgICAgICAgICAgICAgICAgIDZQRS1BbHQtKyAgSVB2NCBNUExTIGNvcmUg
Ky02UEUtQWx0LS1DRSBzaXRlIEMgfA0KICAgICAgICstLS0tLS0tLSsgICAgfCAgfCAgICAgICAg
ICAgICAgICAgfCAgICAgICArLS0tLS0tLS0rDQogICAgICAgfHNpdGUgQiAgQ0UtLS0rICArLS0t
LS0tLS0tLS0tLS0tLS0rDQogICAgICAgKy0tLS0tLS0tKw0KDQogICAgICAgIElQdjYgaXNsYW5k
cyAgICAgICAgICBJUHY0IGNsb3VkICAgICAgIElQdjYgaXNsYW5kDQogICAgICAgPC0tLS0tLS0t
LS0tLS0+PC0tLS0tLS0tLS0tLS0tLS0tLS0tLT48LS0tLS0tLS0tLS0tLS0+DQoNCg0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgRmlndXJlIDENCg0KDQoNCk1hbnJhbCBhbmQgRHV0
dGEgICAgICAgICAgRXhwaXJlcyBKdWx5IDMwLCAyMDA4ICAgICAgICAgICAgICAgICBbUGFnZSAz
XQ0KIA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICA2UEUtQWx0ICAgICAgICAg
ICAgICAgICAgICAgSmFudWFyeSAyMDA4DQoNCg0KICAgVGhlIGludGVyY29ubmVjdGlvbiBtZXRo
b2QgZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1lbnQgdHlwaWNhbGx5DQogICBhcHBsaWVzIHRvIGFu
IEludGVybmV0IFNlcnZpY2UgUHJvdmlkZXIgKElTUCkgdGhhdCBoYXMgYW4gSVB2NCBNUExTDQog
ICBuZXR3b3JrIGFuZCBpcyBmYW1pbGlhciB3aXRoIEJHUCAocG9zc2libHkgYWxyZWFkeSBvZmZl
cmluZyBCR1AvTVBMUw0KICAgVlBOIHNlcnZpY2VzKSBhbmQgdGhhdCB3YW50cyB0byBvZmZlciBJ
UHY2IHNlcnZpY2VzIHRvIHNvbWUgb2YgaXRzDQogICBjdXN0b21lcnMuICBXaXRoIHByb2dyZXNz
aW5nIHRpbWUgZW5kIHVzZXIgZGV2aWNlcyB3aWxsIGhhdmUgSVB2NiANCiAgIGFkZHJlc3NlcyBh
c3NpZ25lZCB0byB0aGVtLCBob3dldmVyIHRoZSBJU1AgbWF5IG5vdCAoeWV0KSB3YW50IHRvIHVw
Z3JhZGUNCiAgIGl0cyBuZXR3b3JrIGNvcmUgdG8gSVB2NiBub3IgdXNlIG9ubHkgSVB2Ni1vdmVy
LUlQdjQgdHVubmVsaW5nLiAgV2l0aCB0aGUNCiAgIDZQRS1BbHQgYXBwcm9hY2ggZGVzY3JpYmVk
IGhlcmUsIHRoZSBwcm92aWRlciBvbmx5IGhhcyB0byB1cGdyYWRlIHNvbWUNCiAgIFByb3ZpZGVy
IEVkZ2UgKFBFKSByb3V0ZXJzIHRvIER1YWwgU3RhY2sgb3BlcmF0aW9ucyBzbyB0aGV5IGJlaGF2
ZSBhcw0KICAgNlBFLUFsdCByb3V0ZXJzIChhbmQgcm91dGUgcmVmbGVjdG9ycyBpZiB0aG9zZSBh
cmUgdXNlZCBmb3IgZXhjaGFuZ2Ugb2YNCiAgIElQdjYgcmVhY2hhYmlsaXR5IGFtb25nIDZQRS1B
bHQgcm91dGVycykgd2hpbGUgbGVhdmluZyB0aGUgSVB2NCBNUExTIGNvcmUNCiAgIHJvdXRlcnMg
dW50b3VjaGVkLiAgVGhlc2UgNlBFLUFsdCByb3V0ZXJzIHByb3ZpZGUgY29ubmVjdGl2aXR5IHRv
IElQdjYNCiAgIGlzbGFuZHMuICBUaGV5IG1heSBhbHNvIHByb3ZpZGUgb3RoZXIgc2VydmljZXMg
c2ltdWx0YW5lb3VzbHkgKElQdjQNCiAgIGNvbm5lY3Rpdml0eSwgSVB2NCBMM1ZQTiBzZXJ2aWNl
cywgTDJWUE4gc2VydmljZXMsIGV0Yy4pLiAgQWxzbyB3aXRoDQogICB0aGUgNlBFLUFsdCBhcHBy
b2FjaCwgbm8gdHVubmVscyBuZWVkIHRvIGJlIGV4cGxpY2l0bHkgY29uZmlndXJlZCwgYW5kIG5v
DQogICBJUHY0IGhlYWRlcnMgbmVlZCB0byBiZSBpbnNlcnRlZCBpbiBmcm9udCBvZiB0aGUgSVB2
NiBwYWNrZXRzIGJldHdlZW4NCiAgIHRoZSBjdXN0b21lciBhbmQgcHJvdmlkZXIgZWRnZS4NCg0K
ICAgVGhlIElTUCBvYnRhaW5zIElQdjYgY29ubmVjdGl2aXR5IHRvIGl0cyBwZWVycyBhbmQgdXBz
dHJlYW1zIHVzaW5nDQogICBtZWFucyBvdXRzaWRlIG9mIHRoZSBzY29wZSBvZiB0aGlzIG1lbW8s
IGFuZCBpdHMgNlBFLUFsdCByb3V0ZXJzDQogICByZWFkdmVydGlzZSBpdCBvdmVyIHRoZSBJUHY0
IE1QTFMgY29yZSB3aXRoIE1QLUJHUC4NCg0KICAgVGhlIGludGVyZmFjZSBiZXR3ZWVuIHRoZSBl
ZGdlIHJvdXRlciBvZiB0aGUgSVB2NiBpc2xhbmQgKEN1c3RvbWVyDQogICBFZGdlIChDRSkgcm91
dGVyKSBhbmQgdGhlIDZQRS1BbHQgcm91dGVyIGlzIGEgbmF0aXZlIElQdjYgaW50ZXJmYWNlIHdo
aWNoDQogICBjYW4gYmUgcGh5c2ljYWwgb3IgbG9naWNhbC4gIEEgcm91dGluZyBwcm90b2NvbCAo
SUdQIG9yIEVHUCkgbWF5IHJ1bg0KICAgYmV0d2VlbiB0aGUgQ0Ugcm91dGVyIGFuZCB0aGUgNlBF
LUFsdCByb3V0ZXIgZm9yIHRoZSBkaXN0cmlidXRpb24gb2YgSVB2Ng0KICAgcmVhY2hhYmlsaXR5
IGluZm9ybWF0aW9uLiAgQWx0ZXJuYXRpdmVseSwgc3RhdGljIHJvdXRlcyBhbmQvb3IgYQ0KICAg
ZGVmYXVsdCByb3V0ZSBtYXkgYmUgdXNlZCBvbiB0aGUgNlBFLUFsdCByb3V0ZXIgYW5kIHRoZSBD
RSByb3V0ZXIgdG8NCiAgIGNvbnRyb2wgcmVhY2hhYmlsaXR5LiAgQW4gSVB2NiBpc2xhbmQgbWF5
IGNvbm5lY3QgdG8gdGhlIHByb3ZpZGVyDQogICBuZXR3b3JrIG92ZXIgbW9yZSB0aGFuIG9uZSBp
bnRlcmZhY2UuDQoNCiAgIFRoZSA2UEUtQWx0IGFwcHJvYWNoIGRlc2NyaWJlZCBpbiB0aGlzIGRv
Y3VtZW50IGNhbiBiZSB1c2VkIGZvciBjdXN0b21lcnMNCiAgIHRoYXQgYWxyZWFkeSBoYXZlIGFu
IElQdjQgc2VydmljZSBmcm9tIHRoZSBuZXR3b3JrIHByb3ZpZGVyIGFuZA0KICAgYWRkaXRpb25h
bGx5IHJlcXVpcmUgYW4gSVB2NiBzZXJ2aWNlLCBhcyB3ZWxsIGFzIGZvciBjdXN0b21lcnMgdGhh
dA0KICAgcmVxdWlyZSBvbmx5IElQdjYgY29ubmVjdGl2aXR5Lg0KDQogICBUaGUgc2NlbmFyaW8g
aXMgYWxzbyBkZXNjcmliZWQgaW4gW1JGQzQwMjldLg0KDQogICBOb3RlIHRoYXQgdGhlIDZQRS1B
bHQgYXBwcm9hY2ggc3BlY2lmaWVkIGluIHRoaXMgZG9jdW1lbnQgcHJvdmlkZXMgZ2xvYmFsDQog
ICBJUHY2IHJlYWNoYWJpbGl0eS4gIFN1cHBvcnQgb2YgSVB2NiBWUE5zIGNhbiBzaW1pbGFybHkg
YmUgZ2l2ZW4gYnkgdGhpcyBkcmFmdCwNCiAgIGlmIHRoZSBJUHY2IHJvdXRlcyBpbiB0aGUgVlBO
J3MgZG8gbm90IG92ZXJsYXAuIFRoZSBJUCBWUE4ncyBmdW5jdGlvbmFsaXR5IGlzDQogICBhZGRy
ZXNzZWQgaW4gW1JGQzQ2NTldLiBJbnN0ZWFkIG9mIGV4Y2hhbmdpbmcgYSAidHVubmVsIGxhYmVs
IiBpdCB1c2VzIHRoZSANCiAgICJJUHY2IEV4cGxpY2l0IE5VTEwgbGFiZWwiLCBiZWNhdXNlIHRo
ZSBzaWduYWxsZWQgbGFiZWwgaW4gNlBFIGRpZCBub3QgY29udmV5IA0KICAgYW55IG1vcmUgbWVh
bmluZy4gDQoNCiAgIERlcGxveW1lbnQgb2YgdGhlIDZQRS1BbHQgYXBwcm9hY2ggb3ZlciBhbiBl
eGlzdGluZyBJUHY0IE1QTFMgY2xvdWQgZG9lcw0KICAgbm90IHJlcXVpcmUgaW50cm9kdWN0aW9u
IG9mIG5ldyBtZWNoYW5pc21zIGluIHRoZSBjb3JlIChvdGhlciB0aGFuDQogICBwb3RlbnRpYWxs
eSB0aG9zZSBkZXNjcmliZWQgYXQgdGhlIGVuZCBvZiBzZWN0aW9uIDMgZm9yIGRlYWxpbmcgd2l0
aA0KICAgZHluYW1pYyBNVFUgZGlzY292ZXJ5KS4gIENvbmZpZ3VyYXRpb24gYW5kIG9wZXJhdGlv
bnMgb2YgdGhlIDZQRS1BbHQNCiAgIGFwcHJvYWNoIGhhcyBhIGxvdCBvZiBzaW1pbGFyaXRpZXMg
d2l0aCB0aGUgY29uZmlndXJhdGlvbiBhbmQNCiAgIG9wZXJhdGlvbnMgb2YgYW4gSVB2NCBWUE4g
c2VydmljZSAoW1JGQzQzNjRdKSBvciBJUHY2IFZQTiBzZXJ2aWNlDQogICAoW1JGQzQ2NTldKSBv
dmVyIGFuIElQdjQgTVBMUyBjb3JlIHNpbmNlIHRoZXkgYWxsIHVzZSBNUC1CR1AgdG8NCg0KDQoN
Ck1hbnJhbCBhbmQgRHV0dGEgICAgICAgICAgRXhwaXJlcyBKdWx5IDMwLCAyMDA4ICAgICAgICAg
ICAgICAgICBbUGFnZSA0XQ0KIA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICA2
UEUtQWx0ICAgICAgICAgICAgICAgICAgICAgSmFudWFyeSAyMDA4DQoNCg0KICAgZGlzdHJpYnV0
ZSBub24tSVB2NCByZWFjaGFiaWxpdHkgaW5mb3JtYXRpb24gZm9yIHRyYW5zcG9ydCBvdmVyIGFu
DQogICBJUHY0IE1QTFMgQ29yZS4gIEhvd2V2ZXIsIHRoZSBjb25maWd1cmF0aW9uIGFuZCBvcGVy
YXRpb25zIG9mIHRoZSA2UEUtQWx0DQogICBhcHByb2FjaCBpcyBzb21ld2hhdCBzaW1wbGVyLCBz
aW5jZSBpdCBkb2VzIG5vdCBpbnZvbHZlIGFsbCB0aGUgVlBODQogICBjb25jZXB0cyBzdWNoIGFz
IFZSRnMuIA0KDQoNCjIuICBQcm90b2NvbCBPdmVydmlldw0KDQogICBFYWNoIElQdjYgc2l0ZSBp
cyBjb25uZWN0ZWQgdG8gYXQgbGVhc3Qgb25lIFByb3ZpZGVyIEVkZ2Ugcm91dGVyIHRoYXQNCiAg
IGlzIGxvY2F0ZWQgb24gdGhlIGJvcmRlciBvZiB0aGUgSVB2NCBNUExTIGNsb3VkLiAgV2UgY2Fs
bCBzdWNoIGENCiAgIHJvdXRlciBhIDZQRS1BbHQgcm91dGVyLiAgVGhlIDZQRS1BbHQgcm91dGVy
IE1VU1QgYmUgZHVhbCBzdGFjayBJUHY0IGFuZA0KICAgSVB2Ni4gIFRoZSA2UEUtQWx0IHJvdXRl
ciBNVVNUIGJlIGNvbmZpZ3VyZWQgd2l0aCBhdCBsZWFzdCBvbmUgSVB2NA0KICAgYWRkcmVzcyBv
biB0aGUgSVB2NCBzaWRlIGFuZCBhdCBsZWFzdCBvbmUgSVB2NiBhZGRyZXNzIG9uIHRoZSBJUHY2
DQogICBzaWRlLiAgVGhlIGNvbmZpZ3VyZWQgSVB2NCBhZGRyZXNzIG5lZWRzIHRvIGJlIHJvdXRh
YmxlIGluIHRoZSBJUHY0DQogICBjbG91ZCwgYW5kIHRoZXJlIG5lZWRzIHRvIGJlIGEgbGFiZWwg
Ym91bmQgdmlhIGFuIElQdjQgbGFiZWwNCiAgIGRpc3RyaWJ1dGlvbiBwcm90b2NvbCB0byB0aGlz
IElQdjQgcm91dGUuDQoNCiAgIEFzIGEgcmVzdWx0IG9mIHRoaXMsIGV2ZXJ5IGNvbnNpZGVyZWQg
NlBFLUFsdCByb3V0ZXIga25vd3Mgd2hpY2ggTVBMUw0KICAgbGFiZWwgdG8gdXNlIHRvIHNlbmQg
cGFja2V0cyB0byBhbnkgb3RoZXIgNlBFLUFsdCByb3V0ZXIuICBOb3RlIHRoYXQgYW4NCiAgIE1Q
TFMgbmV0d29yayBvZmZlcmluZyBCR1AvTVBMUyBJUCBWUE4gc2VydmljZXMgYWxyZWFkeSBmdWxm
aWxscyB0aGVzZQ0KICAgcmVxdWlyZW1lbnRzLg0KDQogICBObyBleHRyYSByb3V0ZXMgbmVlZCB0
byBiZSBpbmplY3RlZCBpbiB0aGUgSVB2NCBjbG91ZC4NCg0KICAgV2UgY2FsbCB0aGUgNlBFLUFs
dCByb3V0ZXIgcmVjZWl2aW5nIElQdjYgcGFja2V0cyBmcm9tIGFuIElQdjYgc2l0ZSBhbg0KICAg
SW5ncmVzcyA2UEUtQWx0IHJvdXRlciAocmVsYXRpdmUgdG8gdGhlc2UgSVB2NiBwYWNrZXRzKS4g
IFdlIGNhbGwgYSA2UEUtQWx0DQogICByb3V0ZXIgZm9yd2FyZGluZyBJUHY2IHBhY2tldHMgdG8g
YW4gSVB2NiBzaXRlIGFuIEVncmVzcyA2UEUtQWx0IHJvdXRlcg0KICAgKHJlbGF0aXZlIHRvIHRo
ZXNlIElQdjYgcGFja2V0cykuDQoNCiAgIEludGVyY29ubmVjdGluZyBJUHY2IGlzbGFuZHMgb3Zl
ciBhbiBJUHY0IE1QTFMgY2xvdWQgdGFrZXMgcGxhY2UNCiAgIHRocm91Z2ggdGhlIGZvbGxvd2lu
ZyBzdGVwczoNCg0KICAgMS4gIEV4Y2hhbmdlIElQdjYgcmVhY2hhYmlsaXR5IGluZm9ybWF0aW9u
IGFtb25nIDZQRS1BbHQgcm91dGVycyB3aXRoIE1QLQ0KICAgICAgIEJHUCBbUkZDNDc2MF06DQoN
CiAgICAgICBUaGUgNlBFLUFsdCByb3V0ZXJzIE1VU1QgZXhjaGFuZ2UgdGhlIElQdjYgcHJlZml4
ZXMgb3ZlciBNUC1CR1ANCiAgICAgICBzZXNzaW9ucyBhcyBwZXIgW1JGQzQ3NjBdIHJ1bm5pbmcg
b3ZlciBJUHY0LiAgVGhlIE1QLUJHUCBBZGRyZXNzDQogICAgICAgRmFtaWx5IElkZW50aWZpZXIg
KEFGSSkgdXNlZCBNVVNUIGJlIElQdjYgKHZhbHVlIDIpLiAgSW4gZG9pbmcNCiAgICAgICBzbywg
dGhlIDZQRS1BbHQgcm91dGVycyBjb252ZXkgdGhlaXIgSVB2NCBhZGRyZXNzIGFzIHRoZSBCR1Ag
TmV4dCBIb3ANCiAgICAgICBmb3IgdGhlIGFkdmVydGlzZWQgSVB2NiBwcmVmaXhlcy4gIFRoZSBJ
UHY0IGFkZHJlc3Mgb2YgdGhlIGVncmVzcw0KICAgICAgIDZQRS1BbHQgcm91dGVyIE1VU1QgYmUg
ZW5jb2RlZCBhcyBhbiBJUHY0LW1hcHBlZCBJUHY2IGFkZHJlc3MgaW4gdGhlDQogICAgICAgQkdQ
IE5leHQgSG9wIGZpZWxkLiAgVGhpcyBlbmNvZGluZyBpcyBjb25zaXN0ZW50IHdpdGggdGhlDQog
ICAgICAgZGVmaW5pdGlvbiBvZiBhbiBJUHY0LW1hcHBlZCBJUHY2IGFkZHJlc3MgaW4gW1JGQzM1
MTNdIGFzIGFuDQogICAgICAgImFkZHJlc3MgdHlwZSB1c2VkIHRvIHJlcHJlc2VudCB0aGUgYWRk
cmVzcyBvZiBJUHY0IG5vZGVzIGFzIElQdjYNCiAgICAgICBhZGRyZXNzZXMiLiAgSG93ZXZlciB1
bmxpbmUgWzZQRV0sIHRoZSA2UEUtQWx0IGRvZXMgbm90IG5lZWQgdG8gYmluZCANCiAgICAgICBh
IGxhYmVsIHRvIHRoZSBJUHY2IHByZWZpeCBhcyBwZXIgW1JGQzMxMDddLiAgVGhlIFN1YnNlcXVl
bmNlIEFkZHJlc3MgRmFtaWx5DQogICAgICAgSWRlbnRpZmllciAoU0FGSSkgdXNlZCBpbiBNUC1C
R1AgTVVTVCBiZSB0aGUgc2FtZSBhcyBhIHJlZ3VsYXIgSVB2NiByb3V0ZS4NCiAgICAgICBUaGUg
cmF0aW9uYWxlIGZvciB0aGlzIGxhYmVsIGlzIGRpc2N1c3NlZCBpbiBzZWN0aW9uIDMuDQoNCg0K
DQpNYW5yYWwgYW5kIER1dHRhICAgICAgICAgIEV4cGlyZXMgSnVseSAzMCwgMjAwOCAgICAgICAg
ICAgICAgICAgW1BhZ2UgNV0NCiANCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAg
NlBFLUFsdCAgICAgICAgICAgICAgICAgICAgIEphbnVhcnkgMjAwOA0KDQoNCg0KDQogICAyLiAg
VHJhbnNwb3J0IElQdjYgcGFja2V0cyBmcm9tIEluZ3Jlc3MgNlBFLUFsdCByb3V0ZXIgdG8gRWdy
ZXNzIDZQRS1BbHQNCiAgICAgICByb3V0ZXIgb3ZlciBJUHY0LXNpZ25hbGVkIExTUHM6DQoNCiAg
ICAgICBUaGUgSW5ncmVzcyA2UEUtQWx0IHJvdXRlciBNVVNUIGZvcndhcmQgSVB2NiBkYXRhIG92
ZXIgdGhlIElQdjQtDQogICAgICAgc2lnbmFsZWQgTFNQIHRvd2FyZHMgdGhlIEVncmVzcyA2UEUt
QWx0IHJvdXRlciBpZGVudGlmaWVkIGJ5IHRoZSBJUHY0DQogICAgICAgYWRkcmVzcyBhZHZlcnRp
c2VkIGluIHRoZSBJUHY0LW1hcHBlZCBJUHY2IGFkZHJlc3Mgb2YgdGhlIEJHUA0KICAgICAgIE5l
eHQgSG9wIGZvciB0aGUgY29ycmVzcG9uZGluZyBJUHY2IHByZWZpeC4gVGhlIHJvdXRlciBzaG91
bGQgZmlyc3QgDQogICAgICAgUFVTSCB0aGUgIklQdjYgRXhwbGljaXQgTlVMTCIgbGFiZWwsIGFz
IHRoZSBWUE4gbGFiZWwuIFRoZSB0dW5uZWwNCiAgICAgICBsYWJlbCB0aGVuIGdldHMgcHVzaGVk
IG9uIHRoZSBNUExTIGxhYmVsIHN0YWNrLCBhbmQgdGhlIHBhY2tldCBpcw0KICAgICAgIGZvcndh
cmRlZCB0byB0aGUgdHVubmVsJ3MgbmV4dCBob3AuDQoNCg0KICAgQXMgcmVxdWlyZWQgYnkgdGhl
IEJHUCBzcGVjaWZpY2F0aW9uIFtSRkM0MjcxXSwgUEUgcm91dGVycyBmb3JtIGENCiAgIGZ1bGwg
cGVlcmluZyBtZXNoIHVubGVzcyBSb3V0ZSBSZWZsZWN0b3JzIGFyZSB1c2VkLg0KDQoNCjMuICBU
cmFuc3BvcnQgb3ZlciBJUHY0LXNpZ25hbGVkIExTUHMgYW5kIElQdjYgbGFiZWwgYmluZGluZw0K
DQogICBJbiB0aGlzIGFwcHJvYWNoLCB0aGUgSVB2NC1tYXBwZWQgSVB2NiBhZGRyZXNzZXMgYWxs
b3cgYSA2UEUtQWx0IHJvdXRlcg0KICAgdGhhdCBoYXMgdG8gZm9yd2FyZCBhbiBJUHY2IHBhY2tl
dCB0byBhdXRvbWF0aWNhbGx5IGRldGVybWluZSB0aGUNCiAgIElQdjQtc2lnbmFsZWQgTFNQIHRv
IHVzZSBmb3IgYSBwYXJ0aWN1bGFyIElQdjYgZGVzdGluYXRpb24gYnkgbG9va2luZw0KICAgYXQg
dGhlIE1QLUJHUCByb3V0aW5nIGluZm9ybWF0aW9uLg0KDQogICBUaGUgSVB2NC1zaWduYWxlZCBM
U1BzIGNhbiBiZSBlc3RhYmxpc2hlZCB1c2luZyBhbnkgZXhpc3RpbmcNCiAgIHRlY2huaXF1ZSBm
b3IgbGFiZWwgc2V0dXAgW1JGQzMwMzFdIChMRFAgW1JGQzUwMzZdLCBSU1ZQLVRFIFtSRkMzMjA5
XSkuDQoNCiAgIFRvIGVuc3VyZSBpbnRlcm9wZXJhYmlsaXR5IGFtb25nIHN5c3RlbXMgdGhhdCBp
bXBsZW1lbnQgdGhlIDZQRS1BbHQNCiAgIGFwcHJvYWNoIGRlc2NyaWJlZCBpbiB0aGlzIGRvY3Vt
ZW50LCBhbGwgc3VjaCBzeXN0ZW1zIE1VU1Qgc3VwcG9ydA0KICAgdHVubmVsaW5nIHVzaW5nIElQ
djQtc2lnbmFsZWQgTVBMUyBMU1BzIGVzdGFibGlzaGVkIGJ5IExEUCBbUkZDMzAzNl0uDQoNCiAg
IFdoZW4gdHVubmVsaW5nIElQdjYgcGFja2V0cyBvdmVyIHRoZSBJUHY0IE1QTFMgYmFja2JvbmUs
IHJhdGhlciB0aGFuDQogICBzdWNjZXNzaXZlbHkgcHJlcGVuZCBhbiBJUHY0IGhlYWRlciBhbmQg
dGhlbiBwZXJmb3JtIGxhYmVsIGltcG9zaXRpb24NCiAgIGJhc2VkIG9uIHRoZSBJUHY0IGhlYWRl
ciwgdGhlIGluZ3Jlc3MgNlBFLUFsdCBSb3V0ZXIgTVVTVCBkaXJlY3RseQ0KICAgcGVyZm9ybSBs
YWJlbCBpbXBvc2l0aW9uIG9mIHRoZSBJUHY2IGhlYWRlciB3aXRob3V0IHByZXBlbmRpbmcgYW55
DQogICBJUHY0IGhlYWRlci4gIFRoZSB0dW5uZWwgbGFiZWwgaW1wb3NlZCBNVVNUIGNvcnJlc3Bv
bmQgdG8gdGhlIElQdjQtDQogICBzaWduYWxlZCBMU1Agc3RhcnRpbmcgb24gdGhlIGluZ3Jlc3Mg
NlBFLUFsdCBSb3V0ZXIgYW5kIGVuZGluZyBvbiB0aGUNCiAgIGVncmVzcyA2UEUtQWx0IFJvdXRl
ci4NCg0KICAgV2hpbGUgdGhpcyBhcHByb2FjaCBjb3VsZCB0aGVvcmV0aWNhbGx5IG9wZXJhdGUg
aW4gc29tZSBzaXR1YXRpb25zDQogICB1c2luZyBhIHNpbmdsZSBsZXZlbCBvZiBsYWJlbHMsIHRo
ZXJlIGFyZSBzaWduaWZpY2FudCBhZHZhbnRhZ2VzIGluDQogICB1c2luZyBhIHNlY29uZCBsZXZl
bCBvZiBsYWJlbHMgd2hpY2ggYXJlIGJvdW5kIHRvIElQdjYgcHJlZml4ZXMgdmlhDQogICBNUC1C
R1AgYWR2ZXJ0aXNlbWVudHMgaW4gYWNjb3JkYW5jZSB3aXRoIFtSRkMzMTA3XS4NCg0KICAgRm9y
IGluc3RhbmNlLCB1c2Ugb2YgYSBzZWNvbmQgbGV2ZWwgbGFiZWwgYWxsb3dzIFBlbnVsdGltYXRl
IEhvcA0KICAgUG9wcGluZyAoUEhQKSBvbiB0aGUgSVB2NCBMYWJlbCBTd2l0Y2ggUm91dGVyIChM
U1IpIHVwc3RyZWFtIG9mIHRoZQ0KICAgZWdyZXNzIDZQRS1BbHQgcm91dGVyIHdpdGhvdXQgYW55
IElQdjYgY2FwYWJpbGl0aWVzL3VwZ3JhZGUgb24gdGhlDQogICBwZW51bHRpbWF0ZSByb3V0ZXI7
IHRoaXMgaXMgYmVjYXVzZSBpdCBzdGlsbCB0cmFuc21pdHMgTVBMUyBwYWNrZXRzDQogICBldmVu
IGFmdGVyIHRoZSBQSFAgKGluc3RlYWQgb2YgaGF2aW5nIHRvIHRyYW5zbWl0IElQdjYgcGFja2V0
cyBhbmQNCiAgIGVuY2Fwc3VsYXRlIHRoZW0gYXBwcm9wcmlhdGVseSkuDQoNCg0KDQoNCk1hbnJh
bCBhbmQgRHV0dGEgICAgICAgICAgRXhwaXJlcyBKdWx5IDMwLCAyMDA4ICAgICAgICAgICAgICAg
ICBbUGFnZSA2XQ0KIA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICA2UEUtQWx0
ICAgICAgICAgICAgICAgICAgICAgSmFudWFyeSAyMDA4DQoNCg0KICAgQWxzbywgYW4gZXhpc3Rp
bmcgSVB2NC1zaWduYWxlZCBMU1Agd2hpY2ggaXMgdXNpbmcgIklQdjQgRXhwbGljaXQNCiAgIE5V
TEwgbGFiZWwiIG92ZXIgdGhlIGxhc3QgaG9wIChzYXkgYmVjYXVzZSB0aGF0IExTUCBpcyBhbHJl
YWR5IHVzZWQNCiAgIHRvIHRyYW5zcG9ydCBJUHY0IHRyYWZmaWMgd2l0aCB0aGUgUGlwZSBEaWZm
LVNlcnYgVHVubmVsaW5nIE1vZGVsIGFzDQogICBkZWZpbmVkIGluIFtSRkMzMjcwXSkgY291bGQg
bm90IGJlIHVzZWQgdG8gY2FycnkgSVB2NiB3aXRoIGEgc2luZ2xlDQogICBsYWJlbCBzaW5jZSB0
aGUgIklQdjQgRXhwbGljaXQgTlVMTCBsYWJlbCIgY2FuIG5vdCBiZSB1c2VkIHRvIGNhcnJ5DQog
ICBuYXRpdmUgSVB2NiB0cmFmZmljIChzZWUgW1JGQzMwMzJdKSwgd2hpbGUgaXQgY291bGQgYmUg
dXNlZCB0byBjYXJyeQ0KICAgbGFiZWxlZCBJUHY2IHRyYWZmaWMgKHNlZSBbUkZDNDE4Ml0pLg0K
DQogICBUaGlzIGlzIHdoeSBhIHNlY29uZCBsYWJlbCBNVVNUIGJlIHVzZWQgd2l0aCB0aGUgNlBF
LUFsdCBhcHByb2FjaC4NCg0KICAgVGhlIGxhYmVsIE1VU1QgYmUgdGhlIElQdjYgRXhwbGljaXQg
TnVsbCBMYWJlbC4gDQoNCiAgIFtSRkMyNDYwXSByZXF1aXJlcyB0aGF0IGV2ZXJ5IGxpbmsgaW4g
dGhlIElQdjYgSW50ZXJuZXQgaGF2ZSBhbiBNVFUNCiAgIG9mIDEyODAgb2N0ZXRzIG9yIGxhcmdl
ci4gIFRoZXJlZm9yZSwgb24gTVBMUyBsaW5rcyB0aGF0IGFyZSB1c2VkIGZvcg0KICAgdHJhbnNw
b3J0IG9mIElQdjYgYXMgcGVyIHRoZSA2UEUtQWx0IGFwcHJvYWNoIGFuZCB0aGF0IGRvIG5vdCBz
dXBwb3J0DQogICBsaW5rLXNwZWNpZmljIGZyYWdtZW50YXRpb24gYW5kIHJlYXNzZW1ibHksIHRo
ZSBNVFUgbXVzdCBiZQ0KICAgY29uZmlndXJlZCB0byBhdCBsZWFzdCAxMjgwIG9jdGV0cyBwbHVz
IHRoZSBlbmNhcHN1bGF0aW9uIG92ZXJoZWFkLg0KDQogICBTb21lIElQdjYgaG9zdHMgbWlnaHQg
YmUgc2VuZGluZyBwYWNrZXRzIGxhcmdlciB0aGFuIHRoZSBNVFUNCiAgIGF2YWlsYWJsZSBpbiB0
aGUgSVB2NCBNUExTIGNvcmUgYW5kIHJlbHkgb24gUGF0aCBNVFUgZGlzY292ZXJ5IHRvDQogICBs
ZWFybiBhYm91dCB0aG9zZSBsaW5rcy4gIFRvIHNpbXBsaWZ5IE1UVSBkaXNjb3Zlcnkgb3BlcmF0
aW9ucywgb25lDQogICBvcHRpb24gaXMgZm9yIHRoZSBuZXR3b3JrIGFkbWluaXN0cmF0b3IgdG8g
ZW5naW5lZXIgdGhlIE1UVSBvbiB0aGUNCiAgIGNvcmUgZmFjaW5nIGludGVyZmFjZXMgb2YgdGhl
IGluZ3Jlc3MgNlBFLUFsdCwgY29uc2lzdGVudCB3aXRoIHRoZSBjb3JlDQogICBNVFUsIHNvIHRo
YXQgSUNNUCAnUGFja2V0IFRvbyBCaWcnIG1lc3NhZ2VzIGNhbiBiZSBzZW50IGJhY2sgYnkgdGhl
DQogICBpbmdyZXNzIDZQRS1BbHQgd2l0aG91dCB0aGUgY29ycmVzcG9uZGluZyBwYWNrZXRzIGV2
ZXIgZW50ZXJpbmcgdGhlIE1QTFMNCiAgIGNvcmUuICBPdGhlcndpc2UsIHJvdXRlcnMgaW4gdGhl
IElQdjQgTVBMUyBuZXR3b3JrIGhhdmUgdGhlIG9wdGlvbiB0bw0KICAgZ2VuZXJhdGUgYW4gSUNN
UCAiUGFja2V0IFRvbyBCaWciIG1lc3NhZ2UgdXNpbmcgbWVjaGFuaXNtcyBhcw0KICAgZGVzY3Jp
YmVkIGluIHNlY3Rpb24gMi4zLjIgIlR1bm5lbGluZyBQcml2YXRlIEFkZHJlc3NlcyB0aHJvdWdo
IGENCiAgIFB1YmxpYyBCYWNrYm9uZSIgb2YgW1JGQzMwMzJdLg0KDQogICBJbiB0aGF0IGNhc2Us
IG5vdGUgdGhhdCwgc2hvdWxkIGEgY29yZSByb3V0ZXIgd2l0aCBhbiBvdXRnb2luZyBsaW5rDQog
ICB3aXRoIGEgTVRVIHNtYWxsZXIgdGhhbiAxMjgwIHJlY2VpdmUgYW4gZW5jYXBzdWxhdGVkIElQ
djYgcGFja2V0DQogICBsYXJnZXIgdGhhbiAxMjgwLCB0aGVuIHRoZSBtZWNoYW5pc21zIG9mIFtS
RkMzMDMyXSBtYXkgcmVzdWx0IGluIHRoZQ0KICAgIlBhY2tldCBUb28gQmlnIiBtZXNzYWdlIG5l
dmVyIHJlYWNoaW5nIHRoZSBzZW5kZXIuICBUaGlzIGlzIGJlY2F1c2UsDQogICBhY2NvcmRpbmcg
dG8gW1JGQzI0NjNdLCB0aGUgY29yZSByb3V0ZXIgd2lsbCBidWlsZCBhbiBJQ01QICJQYWNrZXQN
CiAgIFRvbyBCaWciIG1lc3NhZ2UgZmlsbGVkIHdpdGggdGhlIGludm9raW5nIHBhY2tldCB1cCB0
byAxMjgwIGJ5dGVzIGFuZA0KICAgd2hlbiBmb3J3YXJkaW5nIGRvd25zdHJlYW0gdG93YXJkcyB0
aGUgZWdyZXNzIFBFIGFzIHBlciBbUkZDMzAzMl0sDQogICB0aGUgTVRVIG9mIHRoZSBvdXRnb2lu
ZyBsaW5rIHdpbGwgY2F1c2UgdGhlIHBhY2tldCB0byBiZSBkcm9wcGVkLg0KICAgVGhpcyBtYXkg
Y2F1c2Ugc2lnbmlmaWNhbnQgb3BlcmF0aW9uYWwgcHJvYmxlbXM7IHRoZSBvcmlnaW5hdG9yIG9m
DQogICB0aGUgcGFja2V0cyB3aWxsIG5vdGljZSB0aGF0IGhpcyBkYXRhIGlzIG5vdCBnZXR0aW5n
IHRocm91Z2gsIHdpdGhvdXQNCiAgIGtub3dpbmcgd2h5IGFuZCB3aGVyZSB0aGV5IGFyZSBkaXNj
YXJkZWQuICBUaGlzIGlzc3VlIHdvdWxkIG9ubHkNCiAgIG9jY3VyIGlmIHRoZSBhYm92ZSByZWNv
bW1lbmRhdGlvbiAodG8gY29uZmlndXJlIE1UVSBvbiBNUExTIGxpbmtzIG9mDQogICBhdCBsZWFz
dCAxMjgwIG9jdGV0cyBwbHVzIGVuY2Fwc3VsYXRpb24gb3ZlcmhlYWQpIGlzIG5vdCBhZGhlcmVk
IHRvDQoNCg0KDQpNYW5yYWwgYW5kIER1dHRhICAgICAgICAgIEV4cGlyZXMgSnVseSAzMCwgMjAw
OCAgICAgICAgICAgICAgICAgW1BhZ2UgN10NCiANCkludGVybmV0LURyYWZ0ICAgICAgICAgICAg
ICAgICAgICAgNlBFLUFsdCAgICAgICAgICAgICAgICAgICAgIEphbnVhcnkgMjAwOA0KDQoNCiAg
IChwZXJoYXBzIGJ5IG1pc2NvbmZpZ3VyYXRpb24pLg0KDQoNCjQuICBDcm9zc2luZyBNdWx0aXBs
ZSBJUHY0IEF1dG9ub21vdXMgU3lzdGVtcw0KDQogICBUaGlzIHNlY3Rpb24gZGlzY3Vzc2VzIHRo
ZSBjYXNlIHdoZXJlIHR3byBJUHY2IGlzbGFuZHMgYXJlIGNvbm5lY3RlZA0KICAgdG8gZGlmZmVy
ZW50IEF1dG9ub21vdXMgU3lzdGVtcy4gTm8gZXh0cmEgc2lnbmFsbGluZyBpcyBkb25lLCBob3dl
dmVyIHRoZQ0KICAgTXVsdGlwbGUgQVMgc2NlbmFyaW8gcmVxdWlyZXMgbm8gY2hhbmdlIGluIHRo
ZSBCR1AgSVB2NiBjb2RlLiANCg0KICAgTGlrZSBpbiB0aGUgY2FzZSBvZiBtdWx0aS1BUyBiYWNr
Ym9uZSBvcGVyYXRpb25zIGZvciBJUHY0IFZQTnMNCiAgIGRlc2NyaWJlZCBpbiBzZWN0aW9uIDEw
IG9mIFtSRkM0MzY0XSwgdGhyZWUgbWFpbiBhcHByb2FjaGVzIGNhbiBiZQ0KICAgZGlzdGluZ3Vp
c2hlZDoNCg0KICAgYS4gIEVCR1AgcmVkaXN0cmlidXRpb24gb2YgSVB2NiByb3V0ZXMgZnJvbSBB
UyB0byBuZWlnaGJvcmluZyBBUw0KDQogICAgICAgVGhpcyBhcHByb2FjaCBpcyB0aGUgZXF1aXZh
bGVudCBmb3IgZXhjaGFuZ2Ugb2YgSVB2NiByb3V0ZXMgdG8NCiAgICAgICBwcm9jZWR1cmUgKGEp
IGRlc2NyaWJlZCBpbiBzZWN0aW9uIDEwIG9mIFtSRkM0MzY0XSBmb3IgdGhlDQogICAgICAgZXhj
aGFuZ2Ugb2YgVlBOLUlQdjQgcm91dGVzLg0KDQogICAgICAgSW4gdGhpcyBhcHByb2FjaCwgdGhl
IDZQRS1BbHQgcm91dGVycyB1c2UgSUJHUCAoYWNjb3JkaW5nIHRvDQogICAgICAgW1JGQzI1NDVd
IGFuZCBbUkZDMzEwN10gYW5kIGFzIGRlc2NyaWJlZCBpbiB0aGlzIGRvY3VtZW50IGZvciB0aGUN
CiAgICAgICBzaW5nbGUtQVMgc2l0dWF0aW9uKSB0byByZWRpc3RyaWJ1dGUgSVB2NiByb3V0ZXMg
ZWl0aGVyDQogICAgICAgdG8gYW4gQXV0b25vbW91cyBTeXN0ZW0gQm9yZGVyIFJvdXRlciAoQVNC
UikgNlBFLUFsdCByb3V0ZXIsIG9yIHRvIGENCiAgICAgICByb3V0ZSByZWZsZWN0b3Igb2Ygd2hp
Y2ggYW4gQVNCUiA2UEUtQWx0IHJvdXRlciBpcyBhIGNsaWVudC4gIFRoZQ0KICAgICAgIEFTQlIg
dGhlbiB1c2VzIEVCR1AgdG8gcmVkaXN0cmlidXRlIHRoZSBJUHY2IHJvdXRlcw0KICAgICAgIHRv
IGFuIEFTQlIgaW4gYW5vdGhlciBBUywgd2hpY2ggaW4gdHVybiBkaXN0cmlidXRlcyB0aGVtIHRv
IHRoZQ0KICAgICAgIDZQRS1BbHQgcm91dGVycyBpbiB0aGF0IEFTIGFzIGRlc2NyaWJlZCBlYXJs
aWVyIGluIHRoaXMNCiAgICAgICBzcGVjaWZpY2F0aW9uLCBvciBwZXJoYXBzIHRvIGFub3RoZXIg
QVNCUiB3aGljaCBpbiB0dXJuDQogICAgICAgZGlzdHJpYnV0ZXMgdGhlbSBldGMuDQoNCiAgICAg
ICBUaGVyZSBtYXkgYmUgb25lLCBvciBtdWx0aXBsZSwgQVNCUiBpbnRlcmNvbm5lY3Rpb24ocykg
YWNyb3NzIGFueQ0KICAgICAgIHR3byBBU2VzLiAgSVB2NiBuZWVkcyB0byBiZSBhY3RpdmF0ZWQg
b24gdGhlIGludGVyLUFTQlIgbGlua3MgYW5kDQogICAgICAgZWFjaCBBU0JSIDZQRS1BbHQgcm91
dGVyIGhhcyBhdCBsZWFzdCBvbmUgSVB2NiBhZGRyZXNzIG9uIHRoZQ0KICAgICAgIGludGVyZmFj
ZSB0byB0aGF0IGxpbmsuDQoNCiAgICAgICBObyBpbnRlci1BUyBMU1BzIGFyZSB1c2VkLiAgVGhl
cmUgaXMgZWZmZWN0aXZlbHkgYSBzZXBhcmF0ZSBtZXNoDQogICAgICAgb2YgTFNQcyBhY3Jvc3Mg
dGhlIDZQRS1BbHQgcm91dGVycyB3aXRoaW4gZWFjaCBBUy4NCg0KICAgICAgIEluIHRoaXMgYXBw
cm9hY2gsIHRoZSBBU0JSIGV4Y2hhbmdpbmcgSVB2NiByb3V0ZXMgbWF5IHBlZXIgb3Zlcg0KICAg
ICAgIElQdjYgb3Igb3ZlciBJUHY0LiAgVGhlIGV4Y2hhbmdlIG9mIElQdjYgcm91dGVzIE1VU1Qg
YmUgY2FycmllZA0KICAgICAgIG91dCBhcyBwZXIgW1JGQzI1NDVdLg0KDQogICAgICAgTm90ZSB0
aGF0IHRoZSBwZWVyaW5nIEFTQlIgaW4gdGhlIG5laWdoYm9yaW5nIEFTIHRvIHdoaWNoIHRoZQ0K
ICAgICAgIElQdjYgcm91dGVzIHdlcmUgZGlzdHJpYnV0ZWQgd2l0aCBFQkdQLCBzaG91bGQgaW4g
aXRzIHR1cm4NCiAgICAgICByZWRpc3RyaWJ1dGUgdGhlc2Ugcm91dGVzIHRvIHRoZSA2UEUtQWx0
cyBpbiBpdHMgQVMgdXNpbmcgSUJHUCBhbmQNCiAgICAgICBlbmNvZGluZyBpdHMgb3duIElQdjQg
YWRkcmVzcyBhcyB0aGUgSVB2NC1tYXBwZWQgSVB2NiBCR1AgTmV4dA0KICAgICAgIEhvcC4NCg0K
DQoNCg0KDQpNYW5yYWwgYW5kIER1dHRhICAgICAgICAgIEV4cGlyZXMgSnVseSAzMCwgMjAwOCAg
ICAgICAgICAgICAgICAgW1BhZ2UgOF0NCiANCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAg
ICAgICAgNlBFLUFsdCAgICAgICAgICAgICAgICAgICAgIEphbnVhcnkgMjAwOA0KDQoNCiAgICBi
LiAgTXVsdGlob3AgRUJHUCByZWRpc3RyaWJ1dGlvbiBvZiBJUHY2IHJvdXRlcyBiZXR3ZWVuDQog
ICAgICAgc291cmNlIGFuZCBkZXN0aW5hdGlvbiBQRSByb3V0ZXJzLCB3aXRoIEVCR1AgcmVkaXN0
cmlidXRpb24gb2YgDQogICAgICAgSVB2NCByb3V0ZXMgZnJvbSBBUyB0byBuZWlnaGJvcmluZyBB
UyBmb3IgdGhlIFBFJ3MuDQoNCiAgICAgICBUaGlzIGFwcHJvYWNoIGlzIHRoZSBlcXVpdmFsZW50
IGZvciBleGNoYW5nZSBvZiBJUHY2IHJvdXRlcyB0bw0KICAgICAgIHByb2NlZHVyZSAoYykgZGVz
Y3JpYmVkIGluIHNlY3Rpb24gMTAgb2YgW1JGQzQzNjRdIGZvciBleGNoYW5nZQ0KICAgICAgIG9m
IFZQTi0gSVB2NCByb3V0ZXMuDQoNCiAgICAgICBJbiB0aGlzIGFwcHJvYWNoLCBJUHY2IHJvdXRl
cyBhcmUgbmVpdGhlciBtYWludGFpbmVkIG5vcg0KICAgICAgIGRpc3RyaWJ1dGVkIGJ5IHRoZSBB
U0JSIHJvdXRlcnMuICBUaGUgQVNCUiByb3V0ZXJzIG5lZWQgbm90IGJlDQogICAgICAgZHVhbCBz
dGFjayBhbmQgbWF5IGJlIElQdjQvTVBMUy1vbmx5IHJvdXRlcnMuICBBbiBBU0JSIG5lZWRzIHRv
DQogICAgICAgbWFpbnRhaW4gbGFiZWxlZCBJUHY0IC8zMiByb3V0ZXMgdG8gdGhlIDZQRS1BbHQg
cm91dGVycyB3aXRoaW4gaXRzDQogICAgICAgQVMuICBJdCB1c2VzIEVCR1AgdG8gZGlzdHJpYnV0
ZSB0aGVzZSByb3V0ZXMgdG8gb3RoZXIgQVNlcy4NCiAgICAgICBBU0JScyBpbiBhbnkgdHJhbnNp
dCBBU2VzIHdpbGwgYWxzbyBoYXZlIHRvIHVzZSBFQkdQIHRvIHBhc3MNCiAgICAgICBhbG9uZyB0
aGUgbGFiZWxlZCBJUHY0IC8zMiByb3V0ZXMuICBUaGlzIHJlc3VsdHMgaW4gdGhlIGNyZWF0aW9u
DQogICAgICAgb2YgYW4gSVB2NCBsYWJlbCBzd2l0Y2hlZCBwYXRoIGZyb20gdGhlIGluZ3Jlc3Mg
NlBFLUFsdCByb3V0ZXIgdG8gdGhlDQogICAgICAgZWdyZXNzIDZQRS1BbHQgcm91dGVyLiAgTm93
IDZQRS1BbHQgcm91dGVycyBpbiBkaWZmZXJlbnQgQVNlcyBjYW4NCiAgICAgICBlc3RhYmxpc2gg
bXVsdGktaG9wIEVCR1AgY29ubmVjdGlvbnMgdG8gZWFjaCBvdGhlciBvdmVyIElQdjQsIGFuZA0K
ICAgICAgIGNhbiBleGNoYW5nZSBsYWJlbGVkIElQdjYgcm91dGVzICh3aXRoIGFuIElQdjQtbWFw
cGVkIElQdjYgQkdQDQogICAgICAgTmV4dCBIb3ApIG92ZXIgdGhvc2UgY29ubmVjdGlvbnMuDQoN
CiAgICAgICBJUHY2IG5lZWQgbm90IGJlIGFjdGl2YXRlZCBvbiB0aGUgaW50ZXItQVNCUiBsaW5r
cy4NCg0KICAgICAgIFRoZSBjb25zaWRlcmF0aW9ucyBkZXNjcmliZWQgZm9yIHByb2NlZHVyZSAo
YykgaW4gc2VjdGlvbiAxMCBvZg0KICAgICAgIFtSRkM0MzY0XSB3aXRoIHJlc3BlY3QgdG8gcG9z
c2libGUgdXNlIG9mIG11bHRpLWhvcCBFQkdQDQogICAgICAgY29ubmVjdGlvbnMgdmlhIHJvdXRl
LXJlZmxlY3RvcnMgaW4gZGlmZmVyZW50IEFTZXMsIGFzIHdlbGwgYXMNCiAgICAgICB3aXRoIHJl
c3BlY3QgdG8gdGhlIHVzZSBvZiBhIHRoaXJkIGxhYmVsIGluIGNhc2UgdGhlIElQdjQgLzMyDQog
ICAgICAgcm91dGVzIGZvciB0aGUgUEUgcm91dGVycyBhcmUgTk9UIG1hZGUga25vd24gdG8gdGhl
IFAgcm91dGVycywNCiAgICAgICBhcHBseSBlcXVhbGx5IHRvIHRoaXMgYXBwcm9hY2ggZm9yIElQ
djYuDQoNCk1hbnJhbCBhbmQgRHV0dGEgICAgICAgICAgRXhwaXJlcyBKdWx5IDMwLCAyMDA4ICAg
ICAgICAgICAgICAgICBbUGFnZSA5XQ0KIA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAg
ICAgICA2UEUtQWx0ICAgICAgICAgICAgICAgICAgICAgSmFudWFyeSAyMDA4DQoNCg0KDQogICAg
ICAgVGhpcyBhcHByb2FjaCByZXF1aXJlcyB0aGF0IHRoZXJlIGJlIElQdjQgbGFiZWwgc3dpdGNo
ZWQgcGF0aHMNCiAgICAgICBlc3RhYmxpc2hlZCBhY3Jvc3MgdGhlIEFTZXMgbGVhZGluZyBmb3Jt
IGEgcGFja2V0J3MgaW5ncmVzcyA2UEUtQWx0DQogICAgICAgcm91dGVyIHRvIGl0cyBlZ3Jlc3Mg
NlBFLUFsdCByb3V0ZXIuICBIZW5jZSwgdGhlIGNvbnNpZGVyYXRpb25zDQogICAgICAgZGVzY3Jp
YmVkIGZvciBwcm9jZWR1cmUgKGMpIGluIHNlY3Rpb24gMTAgb2YgW1JGQzQzNjRdIHdpdGgNCiAg
ICAgICByZXNwZWN0IHRvIExTUHMgc3Bhbm5pbmcgbXVsdGlwbGUgQVNlcyBhcHBseSBlcXVhbGx5
IHRvIHRoaXMNCiAgICAgICBhcHByb2FjaCBmb3IgSVB2Ni4NCg0KICAgICAgIE5vdGUgYWxzbyB0
aGF0IHRoZSBleGNoYW5nZSBvZiBJUHY2IHJvdXRlcyBjYW4gb25seSBzdGFydCBhZnRlcg0KICAg
ICAgIEJHUCBoYXMgY3JlYXRlZCBJUHY0IGNvbm5lY3Rpdml0eSBiZXR3ZWVuIHRoZSBBU2VzLg0K
DQoNCiA=
------=_Part_34917_8668606.1201755960921
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

------=_Part_34917_8668606.1201755960921--




From idr-bounces@ietf.org Thu Jan 31 09:31:56 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKaRy-000566-Rf; Thu, 31 Jan 2008 09:31:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKaRv-0004zI-M6
	for idr@ietf.org; Thu, 31 Jan 2008 09:31:31 -0500
Received: from wr-out-0506.google.com ([64.233.184.229])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKaRt-0006qS-EX
	for idr@ietf.org; Thu, 31 Jan 2008 09:31:31 -0500
Received: by wr-out-0506.google.com with SMTP id 50so749196wri.25
	for <idr@ietf.org>; Thu, 31 Jan 2008 06:31:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=kWeJ2l/STxMartXRrRJzMki+IHPsSdt4IvkUt0HWko0=;
	b=fq7ZihD39EGpk6GFM1g4OkKYNqCt1E6th6WwBTRkIFgH40asRbEZprjqZ1aHTjzR1XUQx+afOR+UdBWd9esLSY2W/huf6HWaIJ25T1A8R/VpLcULflvYyxjUZKhPgOZVFaiHbqmq3jGp7C+X/UPreuSh0NzOsuJw1vLZ3X9CEGk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ZDYHzr23O0k6xon6MvoASiruIqIH83G6sd6cbPlACX17lWOR0lxgRVFKp33SwLAK55R0WvYGYe7ils8joBWqtsSBAPCxu2Yj/wX5HvGyoMmtRHc7ra3ah83ctjMQfddDBgfktYVR5rsCMwYQPQWG8BFmLQOTP/p7kz3mhHK+lpA=
Received: by 10.142.139.19 with SMTP id m19mr1190394wfd.7.1201789887309;
	Thu, 31 Jan 2008 06:31:27 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Thu, 31 Jan 2008 06:31:27 -0800 (PST)
Message-ID: <77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
Date: Thu, 31 Jan 2008 06:31:27 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Jan Novak" <jjjnovak@hotmail.com>
Subject: Re: [Idr] 6PE-Alt draft
In-Reply-To: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Errors-To: idr-bounces@ietf.org

Hi Jan,

You may be missing the scope of the document. There is a discussion in
the v6ops group too which .

The idea is simple. We do not need to define a new AFI/ SAFI
combination to achieve the 6PE functionality. We can just use the
meaning implied in the IPv6 Explicit NULL label. The 6PE RFC does talk
about allowing signaling for the Explicit NULL label in which case the
dataplane functionality becomes just the same, but in 6PE even that is
signaled using BGP extensions defined in RFC3107.

Thanks,
Vishwas

On Jan 31, 2008 2:14 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
>
>
> Hi,
>
> Just out of curiosity - lets say you have two IPv4 VPNs with
> overlapping set of Pes and both of them want to provide 6PE
> service.
> When the explicit-null encapsulated packets from two different
> VPNs (but same PE) arrive to the other side PE - how do you
> decide which is which - e.g. which packet should be shipped to
> which VPN ??
>
> Jan
>
>
> _________________________________________________________________
> Telly addicts unite!
> http://www.searchgamesbox.com/tvtown.shtml

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



From idr-bounces@ietf.org Thu Jan 31 10:01:04 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKauO-0002ez-9U; Thu, 31 Jan 2008 10:00:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKauN-0002et-80
	for idr@ietf.org; Thu, 31 Jan 2008 10:00:55 -0500
Received: from rn-out-0910.google.com ([64.233.170.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKauL-0007XT-03
	for idr@ietf.org; Thu, 31 Jan 2008 10:00:55 -0500
Received: by rn-out-0910.google.com with SMTP id a46so208209rne.10
	for <idr@ietf.org>; Thu, 31 Jan 2008 07:00:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=Xlwrs7Nb30N0PONg78RkwWosNCpKOK/7akkaKVLi8kI=;
	b=XgGjdNV4vOrz0LHCDWYtUI5JY4jw63OeXoDqUR5WhwXsYMH10QFF81HeTKjEIRBcK+Y/32wHCeM6dCjv+N6xXeWY1xIVtvJ0z/yH6kAfLb7OZw0zEA9GVbPrN1U91L2Pyqz5kLBzEfstXwSExmMLZqqbpBqtcYfEE+m5wuAeZKo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=nX3P3TWiElkHmgakGHyxZWaKpBn9Bm7MROPlJ+Xf9ryOTgUocS+/zRCHqp3wFRwFeh5ineMsvEfKHvtPX+yKiNZ5K8Ho7M2G9DGA3YfLNkn1eyor2zYgSWJT6tBnjiF1vE5VwxsjQWMAAPvVl5nZ5DNAgBA3p7MMTKn8Ntf1Bm8=
Received: by 10.143.36.15 with SMTP id o15mr1186909wfj.182.1201791651357;
	Thu, 31 Jan 2008 07:00:51 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Thu, 31 Jan 2008 07:00:51 -0800 (PST)
Message-ID: <77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
Date: Thu, 31 Jan 2008 07:00:51 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Jan Novak" <jjjnovak@hotmail.com>
Subject: Re: [Idr] 6PE-Alt draft
In-Reply-To: <77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: idr@ietf.org, Francois Le Faucheur IMAP <flefauch@cisco.com>,
	Ooms Dirk <dirk@onesparrow.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

Hi Jan,

I am CC'ing the authors of the 6PE draft to get their views. Let me
explain the draft in greater detail however.

In 6PE, MP-BGP SAFI family label is used to exchange routes between 2
6PE routers (a new AFI/ SAFI combination is defined). Each route is
attached with a label (which may be the IPv6 Explicit NULL label). In
the data-plane this label is used as the inner label and the other
label is the tunnel label, which gets the packet from source PE to
destination PE. Once the packet gets to the destination PE, the inner
label is looked up and a POP operation is done on it and the IPv6
header is looked up in the routing table.

With 6PE-Alt, no additional signaling mechanism is required. All we
need to do is instead of using the signaled label as the inner label,
we use the IPv6 Explicit NULL label. The same operations happen as 6PE
without any explicit signaling of the labels with each route. It helps
prevent all the excess signaling and still providing the exact same
functionality. We are using the meaning implied in the "Explicit NULL
Label". We do not need to signal anything here.

As an alternate, if you notice in IPv6, the end sites/ devices will
become IPv6 and the network may still have IPv4. If the assumption
that each device in the IPv6 networks has a Global IPv6 address (not
that IPv6 site local has been deprecated), we can do without the
entire BGP MPLS IPv6 VPN functionality.

Thanks,
Vishwas

On Jan 31, 2008 6:31 AM, Vishwas Manral <vishwas.ietf@gmail.com> wrote:
> Hi Jan,
>
> You may be missing the scope of the document. There is a discussion in
> the v6ops group too which .
>
> The idea is simple. We do not need to define a new AFI/ SAFI
> combination to achieve the 6PE functionality. We can just use the
> meaning implied in the IPv6 Explicit NULL label. The 6PE RFC does talk
> about allowing signaling for the Explicit NULL label in which case the
> dataplane functionality becomes just the same, but in 6PE even that is
> signaled using BGP extensions defined in RFC3107.
>
> Thanks,
> Vishwas
>
>
> On Jan 31, 2008 2:14 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
> >
> >
> > Hi,
> >
> > Just out of curiosity - lets say you have two IPv4 VPNs with
> > overlapping set of Pes and both of them want to provide 6PE
> > service.
> > When the explicit-null encapsulated packets from two different
> > VPNs (but same PE) arrive to the other side PE - how do you
> > decide which is which - e.g. which packet should be shipped to
> > which VPN ??
> >
> > Jan
> >
> >
> > _________________________________________________________________
> > Telly addicts unite!
> > http://www.searchgamesbox.com/tvtown.shtml
>

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



From idr-bounces@ietf.org Thu Jan 31 11:56:43 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKciF-0007AO-Bj; Thu, 31 Jan 2008 11:56:31 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKciE-0007AG-IU
	for idr@ietf.org; Thu, 31 Jan 2008 11:56:30 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JKciC-0000hI-MX
	for idr@ietf.org; Thu, 31 Jan 2008 11:56:30 -0500
X-IronPort-AV: E=Sophos;i="4.25,286,1199660400"; d="scan'208,217";a="4532501"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 31 Jan 2008 17:56:28 +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 m0VGuRWn010651; 
	Thu, 31 Jan 2008 17:56:27 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m0VGuGEt023274; 
	Thu, 31 Jan 2008 16:56:27 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 Jan 2008 17:56:26 +0100
Received: from [10.0.0.61] ([10.61.81.79]) by xfe-ams-331.emea.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 31 Jan 2008 17:56:25 +0100
In-Reply-To: <77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <C6F4F2F4-7113-4611-9723-425A49817D5B@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [Idr] 6PE-Alt draft
Date: Thu, 31 Jan 2008 17:56:18 +0100
To: Vishwas Manral <vishwas.ietf@gmail.com>, Jan Novak <jjjnovak@hotmail.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 31 Jan 2008 16:56:25.0191 (UTC)
	FILETIME=[36DCE770:01C8642A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=24960; t=1201798587;
	x=1202662587; 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]=206PE-Alt=20draft |Sender:=20;
	bh=a2rKLJ82OHezjnt9JgLjAdrwOSHg2fZdBcYUBN9Kcqs=;
	b=YpN1uiicfAyzvBZXv9ljok5+BiOyDV9tID6gyzdrTLvGOlnRnSryzjJd+v
	5QzpmAsCY+xnD/En8rSzdJ3UUWW2jsT4K4XCstYKd0VxxOo30dtfNpb1YYBx
	dd9VA7oagy;
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: f560cc438c8be83d0aa5c816c29b481c
Cc: idr@ietf.org, Francois Le Faucheur IMAP <flefauch@cisco.com>,
	Ooms Dirk <dirk@onesparrow.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>
Content-Type: multipart/mixed; boundary="===============1357407970=="
Errors-To: idr-bounces@ietf.org


--===============1357407970==
Content-Type: multipart/alternative; boundary=Apple-Mail-34-153079576


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

Hi,

FYI, here is a note posted on the v6ops list where that topic was  
brought up first by Vishwas.


Begin forwarded message:
> From: Francois Le Faucheur IMAP <flefauch@cisco.com>
> Date: 31 January 2008 17:53:54 GMT+01:00
> To: Vishwas Manral <vishwas.ietf@gmail.com>
> Cc: Francois Le Faucheur IMAP <flefauch@cisco.com>,  
> v6ops@ops.ietf.org, "Jeremy De Clercq" <jeremy.de_clercq@alcatel- 
> lucent.be>, "Ooms Dirk" <dirk@onesparrow.com>, stuart.prevost@bt.com
> Subject: Re: 6PE-Alt
>
>
> On 31 Jan 2008, at 15:25, Vishwas Manral wrote:
>
>> Hi Francois,
>>
>> The document I have written does not use signaling
>
> It is a bit of a stretch to claim that 6PE-Alt does not use signaling.
> 6PE-Alt and 6PE both use MP-BGP to signal IPv6 reachability.  6PE- 
> Alt would simply save you one field (the label value) inside the  
> same advertisement.
>
> On the other hand, 6PE-Alt would restrict operations to only one of  
> the options allowed in 6PE. The reasons 6PE allowed multiple label  
> allocation is precisely because different PEs may want to use  
> different label allocation policies.  For example, one 6PE router  
> may prefer to allocate per-prefix label in order to be able to  
> forward packets via label switching as opposed to performing IPv6  
> lookup. 6PE allows each PR router to use whatever label allocation  
> scheme it sees best.
>
>
>> and does not define
>> a new AFI/SAFI functionality to achieve the 6PE.
>
> It is a bit of a stretch to imply that 6PE defines a new AFI/SAFI.
> 6PE uses the IPv6 AFI and the SAFI defined in RFC3107 (which for  
> memory dates back from 2001) precisely for the purpose of binding  
> an MPLS label when advertising IPv6 reachability.
>
>>
>> The difference is obvious, we get the same functionality
>
> my impression is that you get a restricted subset of the  
> functionality (ie forcing every router to use that single label  
> allocation scheme). This had been discussed before and decided that  
> such a restriction was undesirable and unnecessary.
>
>> without
>> adding any new signaling mechanism.
>
> my impression is that both use the same MP-BGP signaling mechanism  
> except one would save a few bytes in the same MP-BGP advertisements.
>
> There are multiple interoperable implementations of 6PE today and  
> am not aware of significant issues with the current 6PE control plane.
>
> Cheers
>
> Francois
>



On 31 Jan 2008, at 16:00, Vishwas Manral wrote:

> Hi Jan,
>
> I am CC'ing the authors of the 6PE draft to get their views. Let me
> explain the draft in greater detail however.
>
> In 6PE, MP-BGP SAFI family label is used to exchange routes between 2
> 6PE routers (a new AFI/ SAFI combination is defined). Each route is
> attached with a label (which may be the IPv6 Explicit NULL label). In
> the data-plane this label is used as the inner label and the other
> label is the tunnel label, which gets the packet from source PE to
> destination PE. Once the packet gets to the destination PE, the inner
> label is looked up and a POP operation is done on it and the IPv6
> header is looked up in the routing table.
>
> With 6PE-Alt, no additional signaling mechanism is required. All we
> need to do is instead of using the signaled label as the inner label,
> we use the IPv6 Explicit NULL label. The same operations happen as 6PE
> without any explicit signaling of the labels with each route. It helps
> prevent all the excess signaling and still providing the exact same
> functionality. We are using the meaning implied in the "Explicit NULL
> Label". We do not need to signal anything here.
>
> As an alternate, if you notice in IPv6, the end sites/ devices will
> become IPv6 and the network may still have IPv4. If the assumption
> that each device in the IPv6 networks has a Global IPv6 address (not
> that IPv6 site local has been deprecated), we can do without the
> entire BGP MPLS IPv6 VPN functionality.
>
> Thanks,
> Vishwas
>
> On Jan 31, 2008 6:31 AM, Vishwas Manral <vishwas.ietf@gmail.com>  
> wrote:
>> Hi Jan,
>>
>> You may be missing the scope of the document. There is a  
>> discussion in
>> the v6ops group too which .
>>
>> The idea is simple. We do not need to define a new AFI/ SAFI
>> combination to achieve the 6PE functionality. We can just use the
>> meaning implied in the IPv6 Explicit NULL label. The 6PE RFC does  
>> talk
>> about allowing signaling for the Explicit NULL label in which case  
>> the
>> dataplane functionality becomes just the same, but in 6PE even  
>> that is
>> signaled using BGP extensions defined in RFC3107.
>>
>> Thanks,
>> Vishwas
>>
>>
>> On Jan 31, 2008 2:14 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
>>>
>>>
>>> Hi,
>>>
>>> Just out of curiosity - lets say you have two IPv4 VPNs with
>>> overlapping set of Pes and both of them want to provide 6PE
>>> service.
>>> When the explicit-null encapsulated packets from two different
>>> VPNs (but same PE) arrive to the other side PE - how do you
>>> decide which is which - e.g. which packet should be shipped to
>>> which VPN ??
>>>
>>> Jan
>>>
>>>
>>> _________________________________________________________________
>>> Telly addicts unite!
>>> http://www.searchgamesbox.com/tvtown.shtml
>>


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

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<div>Hi,</div><div><br class=3D"webkit-block-placeholder"></div><div>FYI, =
here is a note posted on the v6ops list where that topic was brought up =
first by Vishwas.</div><div><br =
class=3D"webkit-block-placeholder"></div><div><br =
class=3D"webkit-block-placeholder"></div><div><div>Begin forwarded =
message:</div><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font =
face=3D"Helvetica" size=3D"5" color=3D"#000000" style=3D"font: normal =
normal normal 18px/normal Helvetica; color: rgb(0, 0, 0); =
"><b>From:=A0</b></font><font face=3D"Helvetica" size=3D"5" style=3D"font:=
 normal normal normal 18px/normal Helvetica; ">Francois Le Faucheur IMAP =
&lt;<a =
href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a>&gt;</font></div>=
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: normal normal normal 18px/normal Helvetica; color: rgb(0, =
0, 0); "><b>Date:=A0</b></font><font face=3D"Helvetica" size=3D"5" =
style=3D"font: normal normal normal 18px/normal Helvetica; ">31 January =
2008 17:53:54 GMT+01:00</font></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font =
face=3D"Helvetica" size=3D"5" color=3D"#000000" style=3D"font: normal =
normal normal 18px/normal Helvetica; color: rgb(0, 0, 0); =
"><b>To:=A0</b></font><font face=3D"Helvetica" size=3D"5" style=3D"font: =
normal normal normal 18px/normal Helvetica; ">Vishwas Manral &lt;<a =
href=3D"mailto:vishwas.ietf@gmail.com">vishwas.ietf@gmail.com</a>&gt;</fon=
t></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><font face=3D"Helvetica" size=3D"5" =
color=3D"#000000" style=3D"font: normal normal normal 18px/normal =
Helvetica; color: rgb(0, 0, 0); "><b>Cc:=A0</b></font><font =
face=3D"Helvetica" size=3D"5" style=3D"font: normal normal normal =
18px/normal Helvetica; ">Francois Le Faucheur IMAP &lt;<a =
href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a>&gt;, <a =
href=3D"mailto:v6ops@ops.ietf.org">v6ops@ops.ietf.org</a>, "Jeremy De =
Clercq" &lt;<a =
href=3D"mailto:jeremy.de_clercq@alcatel-lucent.be">jeremy.de_clercq@alcate=
l-lucent.be</a>&gt;, "Ooms Dirk" &lt;<a =
href=3D"mailto:dirk@onesparrow.com">dirk@onesparrow.com</a>&gt;, <a =
href=3D"mailto:stuart.prevost@bt.com">stuart.prevost@bt.com</a></font></di=
v><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: normal normal normal 18px/normal Helvetica; color: rgb(0, =
0, 0); "><b>Subject:=A0</b></font><font face=3D"Helvetica" size=3D"5" =
style=3D"font: normal normal normal 18px/normal Helvetica; "><b>Re: =
6PE-Alt</b></font></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">On 31 Jan 2008, at 15:25, Vishwas Manral =
wrote:</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Hi =
Francois,</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">The document I have written does not use =
signaling</div></blockquote><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">It is a bit of a stretch to =
claim that 6PE-Alt does not use signaling.</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">6PE-Alt =
and 6PE both use MP-BGP to signal IPv6 reachability.=A0=A06PE-Alt would =
simply save you one field (the label value) inside the same =
advertisement.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">On the other hand, 6PE-Alt would restrict operations =
to only one of the options allowed in 6PE. The reasons 6PE allowed =
multiple label allocation is precisely because different PEs may want to =
use different label allocation policies.=A0=A0For example, one 6PE =
router may prefer to allocate per-prefix label in order to be able to =
forward packets via label switching as opposed to performing IPv6 =
lookup. 6PE allows each PR router to use whatever label allocation =
scheme it sees best.</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">and does not =
define</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">a new AFI/SAFI functionality to =
achieve the 6PE.</div></blockquote><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">It is a bit of a stretch to =
imply that 6PE defines a new AFI/SAFI.</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">6PE uses =
the IPv6 AFI and the SAFI defined in RFC3107 (which for memory dates =
back from 2001) precisely for the purpose of binding an MPLS label when =
advertising IPv6 reachability.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The =
difference is obvious, we get the same =
functionality</div></blockquote><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">my impression is that you get a =
restricted subset of the functionality (ie forcing every router to use =
that single label allocation scheme). This had been discussed before and =
decided that such a restriction was undesirable and =
unnecessary.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">without</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">adding any new signaling =
mechanism.</div></blockquote><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">my impression is that both use =
the same MP-BGP signaling mechanism except one would save a few bytes in =
the same MP-BGP advertisements.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">There are multiple interoperable =
implementations of 6PE today and am not aware of significant issues with =
the current 6PE control plane.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Cheers</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Francois</div><div><br =
class=3D"webkit-block-placeholder"></div></blockquote></div><div><br =
class=3D"webkit-block-placeholder"></div><br><div><div>On 31 Jan 2008, =
at 16:00, Vishwas Manral wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Hi Jan,</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">I am CC'ing the authors of the =
6PE draft to get their views. Let me</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">explain the =
draft in greater detail however.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">In 6PE, MP-BGP SAFI family label =
is used to exchange routes between 2</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">6PE routers =
(a new AFI/ SAFI combination is defined). Each route is</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">attached with a label (which may be the IPv6 =
Explicit NULL label). In</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the =
data-plane this label is used as the inner label and the other</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">label is the tunnel label, which gets the packet =
from source PE to</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">destination PE. Once the packet =
gets to the destination PE, the inner</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">label is =
looked up and a POP operation is done on it and the IPv6</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">header is looked up in the routing table.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">With =
6PE-Alt, no additional signaling mechanism is required. All we</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">need to do is instead of using the signaled label as =
the inner label,</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">we use the IPv6 Explicit NULL =
label. The same operations happen as 6PE</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">without =
any explicit signaling of the labels with each route. It helps</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">prevent all the excess signaling and still providing =
the exact same</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">functionality. We are using the =
meaning implied in the "Explicit NULL</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Label". =
We do not need to signal anything here.</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">As an =
alternate, if you notice in IPv6, the end sites/ devices will</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">become IPv6 and the network may still have IPv4. If =
the assumption</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">that each device in the IPv6 =
networks has a Global IPv6 address (not</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">that =
IPv6 site local has been deprecated), we can do without the</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">entire BGP MPLS IPv6 VPN functionality.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Thanks,</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Vishwas</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">On Jan =
31, 2008 6:31 AM, Vishwas Manral &lt;<a =
href=3D"mailto:vishwas.ietf@gmail.com">vishwas.ietf@gmail.com</a>&gt; =
wrote:</div> <blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Hi =
Jan,</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">You may be missing the scope of the document. There =
is a discussion in</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">the v6ops group too which =
.</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">The idea is simple. We do not need to define a new =
AFI/ SAFI</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">combination to achieve the 6PE =
functionality. We can just use the</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">meaning =
implied in the IPv6 Explicit NULL label. The 6PE RFC does talk</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">about allowing signaling for the Explicit NULL label =
in which case the</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">dataplane functionality becomes =
just the same, but in 6PE even that is</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">signaled =
using BGP extensions defined in RFC3107.</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Thanks,</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Vishwas</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">On Jan 31, =
2008 2:14 AM, Jan Novak &lt;<a =
href=3D"mailto:jjjnovak@hotmail.com">jjjnovak@hotmail.com</a>&gt; =
wrote:</div> <blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Hi,</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Just out of curiosity - lets say =
you have two IPv4 VPNs with</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">overlapping =
set of Pes and both of them want to provide 6PE</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">service.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">When the =
explicit-null encapsulated packets from two different</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">VPNs (but same PE) arrive to the other side PE - how =
do you</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">decide which is which - e.g. =
which packet should be shipped to</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">which VPN =
??</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Jan</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; =
">_________________________________________________________________</div><=
div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Telly addicts unite!</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a =
href=3D"http://www.searchgamesbox.com/tvtown.shtml">http://www.searchgames=
box.com/tvtown.shtml</a></div> </blockquote><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div> =
</blockquote></blockquote></div><br></body></html>=

--Apple-Mail-34-153079576--


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

--===============1357407970==--




From idr-bounces@ietf.org Thu Jan 31 12:06:11 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKcrW-0007Mc-ER; Thu, 31 Jan 2008 12:06:06 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKcrV-0007IW-0m
	for idr@ietf.org; Thu, 31 Jan 2008 12:06:05 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JKcrU-0001Ir-6t
	for idr@ietf.org; Thu, 31 Jan 2008 12:06:04 -0500
X-IronPort-AV: E=Sophos;i="4.25,286,1199660400"; d="scan'208,217";a="4533718"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 31 Jan 2008 18:06:03 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m0VH63cb023581; 
	Thu, 31 Jan 2008 18:06:03 +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 m0VH61Ep027299; 
	Thu, 31 Jan 2008 17:06:03 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 Jan 2008 18:06:01 +0100
Received: from [10.0.0.61] ([10.61.81.79]) by xfe-ams-332.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 31 Jan 2008 18:06:00 +0100
In-Reply-To: <BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <8BDF3D48-B388-44A9-A245-64DC68FD6BAC@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Subject: Re: [Idr] 6PE-Alt draft
Date: Thu, 31 Jan 2008 18:05:54 +0100
To: Jan Novak <jjjnovak@hotmail.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 31 Jan 2008 17:06:00.0840 (UTC)
	FILETIME=[8DF9F880:01C8642B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7248; t=1201799163;
	x=1202663163; c=relaxed/simple; s=amsdkim1002;
	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]=206PE-Alt=20draft |Sender:=20;
	bh=PHbKn+fQd3MBg5Y6NNCE1lwH+zDiFYjAx2Vw/MijUkg=;
	b=w7RXOrwY2TRTr0YujqInXfa43kHDwAwH/YjonmYCwoVs9YyNRQReC1Frrh
	isN96ZwVNzPtfRqTgQk9MmJ23R2lOBokvsk2jM96L3I23PgAO+T2XslyrIlc
	b5F2asBFJ4;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Cc: idr@ietf.org, Francois Le Faucheur IMAP <flefauch@cisco.com>,
	Ooms Dirk <dirk@onesparrow.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>
Content-Type: multipart/mixed; boundary="===============0831285961=="
Errors-To: idr-bounces@ietf.org


--===============0831285961==
Content-Type: multipart/alternative; boundary=Apple-Mail-36-153655041


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

Hi Jan,

There are two documents that relate to transport of IPv6 over an IPv4  
MPLS core:
	* RFC4659 (6VPE): IPv6 VPNS over (say) IPv4 MPLS
	* RFC4798 (6PE): IPv6 over IPv4 MPLS

The quote below is from the 6PE RFC (ie WITHOUT VPN/VRF). It does not  
apply to the 6VPE.

Francois

On 31 Jan 2008, at 18:00, Jan Novak wrote:

>
>
>
> Hi Vishwas,
>
> I believe you refer to this part of 6PE spec:
>
>    The label bound by MP-BGP to the IPv6 prefix indicates to the  
> egress
>    6PE Router that the packet is an IPv6 packet.  This label  
> advertised
>    by the egress 6PE Router with MP-BGP MAY be an arbitrary label  
> value,
>    which identifies an IPv6 routing context or outgoing interface to
>    send the packet to, or MAY be the IPv6 Explicit Null Label.  An
>    ingress 6PE Router MUST be able to accept any such advertised  
> label.
>
> I don't know what is the envisaged use of Explicit Null here - but  
> I would think
> it is for some other purposes since to deliver the packet to the  
> VPN this is
> still needed "identifies an IPv6 routing context or outgoing  
> interface to".
>
> Jan
>
>
>
>
> _________________________________________________________________
> Share what Santa brought you
> https://www.mycooluncool.com


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

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
Hi Jan,<div><br class=3D"webkit-block-placeholder"></div><div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"5" style=3D"font: =
18.0px Helvetica">There are two documents that relate to transport of =
IPv6 over an IPv4 MPLS core:</font></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font =
face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px Helvetica"><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>*=A0RFC4659=
 (6VPE): IPv6 VPNS over (say) IPv4 MPLS</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"5" style=3D"font: =
18.0px Helvetica"><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* RFC4798 (6PE): IPv6 over IPv4 =
MPLS</font></div><div><br =
class=3D"webkit-block-placeholder"></div><div>The quote below is from =
the 6PE RFC (ie WITHOUT VPN/VRF). It does not apply to the =
6VPE.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Francois</div><div><br =
class=3D"webkit-block-placeholder"></div></div><div><div><div>On 31 Jan =
2008, at 18:00, Jan Novak wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Hi Vishwas,</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I =
believe you refer to this part of 6PE spec:</div><div style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>The label bound by MP-BGP =
to the IPv6 prefix indicates to the egress</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>6PE Router that the packet =
is an IPv6 packet.<span class=3D"Apple-converted-space">=A0 </span>This =
label advertised</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>by the egress 6PE Router =
with MP-BGP MAY be an arbitrary label value,</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0=A0 =
</span>which identifies an IPv6 routing context or outgoing interface =
to</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><span class=3D"Apple-converted-space">=A0=A0 =
</span>send the packet to, or MAY be the IPv6 Explicit Null Label.<span =
class=3D"Apple-converted-space">=A0 </span>An</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0=A0 =
</span>ingress 6PE Router MUST be able to accept any such advertised =
label.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">I don't know what is the envisaged use of Explicit =
Null here - but I would think</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">it is for =
some other purposes since to deliver the packet to the VPN this =
is</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; ">still needed "identifies an IPv6 routing =
context or outgoing interface to".</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Jan</div><div style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">_________________________________________________________________</div><=
div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Share what Santa brought you</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><a =
href=3D"https://www.mycooluncool.com">https://www.mycooluncool.com</a></di=
v> </blockquote></div><br></div></body></html>=

--Apple-Mail-36-153655041--


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

--===============0831285961==--




From idr-bounces@ietf.org Thu Jan 31 12:23:51 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKd8b-0008PX-H3; Thu, 31 Jan 2008 12:23:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKd8a-0008PQ-Mb
	for idr@ietf.org; Thu, 31 Jan 2008 12:23:44 -0500
Received: from el-out-1112.google.com ([209.85.162.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKd8Z-0002ZJ-VP
	for idr@ietf.org; Thu, 31 Jan 2008 12:23:44 -0500
Received: by el-out-1112.google.com with SMTP id j27so352418elf.25
	for <idr@ietf.org>; Thu, 31 Jan 2008 09:23:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=pXVpxTbSnBgtF/eh14fzf8vikwpW0as9JuvAuj2YhbA=;
	b=stN+7hQ5l0x96pM2ryKLntqjf5VR8/uXT4eeoAp2Sx7waMVeDKc+DjCKaR9BoD6rGSzMtMTjLQ0iQ3XBboygS6rmVgqO9sLgiXRIM1seLMjFilQdAP/wuOdMg6DCTBG8mzUF1RiQyP/rm8YNmNcd5KOUNEGovmuyr1wYawygE+A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Ro+3t+9h7Za/XnhtaFcx2KhekUB3S19kMS/u294ovlfAuIvuL0IRnSBLtYMLHRUW7h7YsXj5HtrX7lKzM4t1Q4o5JK7ZRwczpb+L5IkInw8B7NIOVoWiqY0umtXo9ultJJT25ZsWnHdB54ulkFqAqGN8NEy9Yf+UmRCZd4l3SNQ=
Received: by 10.142.213.9 with SMTP id l9mr1346528wfg.104.1201800222088;
	Thu, 31 Jan 2008 09:23:42 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Thu, 31 Jan 2008 09:23:42 -0800 (PST)
Message-ID: <77ead0ec0801310923q44251999i8af1b386c8c5bbc2@mail.gmail.com>
Date: Thu, 31 Jan 2008 09:23:42 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Francois Le Faucheur IMAP" <flefauch@cisco.com>
Subject: Re: [Idr] 6PE-Alt draft
In-Reply-To: <C6F4F2F4-7113-4611-9723-425A49817D5B@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<C6F4F2F4-7113-4611-9723-425A49817D5B@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Cc: idr@ietf.org, Jan Novak <jjjnovak@hotmail.com>,
	Ooms Dirk <dirk@onesparrow.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

Hi Francois,

As the 6PE-Alt does not require any additional functionality from
BGP-IPv6 (yes that is the signaling required - but that is the same
required for normal BGP IPv6. For 6PE we use a new AFI/ SAFI and send
labels uselessly. So please do not say that the claim no signaling
changes are required for 6PE-Alt  is a stretch), and that is why we
have inter-operable implementations of 6PE-Alt too. It is not about
interoperable implmentations alone though. I however am surprised how
this simple mechanism was not captured earlier in the review or coding
process.

We do not need to transport labels at all which are now being
transported. Also as the peer decides the label I use, we may have to
configure different labels from different peers (thus using bigger
keys/ more memory in the tables and a lot of other overload). There is
a lot of overhead of signaling and dataplane without any necessity.

I also have issues with the 6VPE RFC too but let us tackle issues one at a time.

Thanks,
Vishwas

On Jan 31, 2008 8:56 AM, Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
>
> Hi,
>
> FYI, here is a note posted on the v6ops list where that topic was brought up
> first by Vishwas.
>
>
>
> Begin forwarded message:
> From: Francois Le Faucheur IMAP <flefauch@cisco.com>
> Date: 31 January 2008 17:53:54 GMT+01:00
> To: Vishwas Manral <vishwas.ietf@gmail.com>
> Cc: Francois Le Faucheur IMAP <flefauch@cisco.com>, v6ops@ops.ietf.org,
> "Jeremy De Clercq" <jeremy.de_clercq@alcatel-lucent.be>, "Ooms Dirk"
> <dirk@onesparrow.com>, stuart.prevost@bt.com
> Subject: Re: 6PE-Alt
>
>
> On 31 Jan 2008, at 15:25, Vishwas Manral wrote:
>
>
> Hi Francois,
>
> The document I have written does not use signaling
>
> It is a bit of a stretch to claim that 6PE-Alt does not use signaling.
> 6PE-Alt and 6PE both use MP-BGP to signal IPv6 reachability.  6PE-Alt would
> simply save you one field (the label value) inside the same advertisement.
>
> On the other hand, 6PE-Alt would restrict operations to only one of the
> options allowed in 6PE. The reasons 6PE allowed multiple label allocation is
> precisely because different PEs may want to use different label allocation
> policies.  For example, one 6PE router may prefer to allocate per-prefix
> label in order to be able to forward packets via label switching as opposed
> to performing IPv6 lookup. 6PE allows each PR router to use whatever label
> allocation scheme it sees best.
>
>
>
> and does not define
> a new AFI/SAFI functionality to achieve the 6PE.
>
> It is a bit of a stretch to imply that 6PE defines a new AFI/SAFI.
> 6PE uses the IPv6 AFI and the SAFI defined in RFC3107 (which for memory
> dates back from 2001) precisely for the purpose of binding an MPLS label
> when advertising IPv6 reachability.
>
>
>
> The difference is obvious, we get the same functionality
>
> my impression is that you get a restricted subset of the functionality (ie
> forcing every router to use that single label allocation scheme). This had
> been discussed before and decided that such a restriction was undesirable
> and unnecessary.
>
>
> without
> adding any new signaling mechanism.
>
> my impression is that both use the same MP-BGP signaling mechanism except
> one would save a few bytes in the same MP-BGP advertisements.
>
> There are multiple interoperable implementations of 6PE today and am not
> aware of significant issues with the current 6PE control plane.
>
> Cheers
>
> Francois
>
>
>
>
>
>
> On 31 Jan 2008, at 16:00, Vishwas Manral wrote:
>
> Hi Jan,
>
> I am CC'ing the authors of the 6PE draft to get their views. Let me
> explain the draft in greater detail however.
>
> In 6PE, MP-BGP SAFI family label is used to exchange routes between 2
> 6PE routers (a new AFI/ SAFI combination is defined). Each route is
> attached with a label (which may be the IPv6 Explicit NULL label). In
> the data-plane this label is used as the inner label and the other
> label is the tunnel label, which gets the packet from source PE to
> destination PE. Once the packet gets to the destination PE, the inner
> label is looked up and a POP operation is done on it and the IPv6
> header is looked up in the routing table.
>
> With 6PE-Alt, no additional signaling mechanism is required. All we
> need to do is instead of using the signaled label as the inner label,
> we use the IPv6 Explicit NULL label. The same operations happen as 6PE
> without any explicit signaling of the labels with each route. It helps
> prevent all the excess signaling and still providing the exact same
> functionality. We are using the meaning implied in the "Explicit NULL
> Label". We do not need to signal anything here.
>
> As an alternate, if you notice in IPv6, the end sites/ devices will
> become IPv6 and the network may still have IPv4. If the assumption
> that each device in the IPv6 networks has a Global IPv6 address (not
> that IPv6 site local has been deprecated), we can do without the
> entire BGP MPLS IPv6 VPN functionality.
>
> Thanks,
> Vishwas
>
> On Jan 31, 2008 6:31 AM, Vishwas Manral <vishwas.ietf@gmail.com> wrote:
> Hi Jan,
>
> You may be missing the scope of the document. There is a discussion in
> the v6ops group too which .
>
> The idea is simple. We do not need to define a new AFI/ SAFI
> combination to achieve the 6PE functionality. We can just use the
> meaning implied in the IPv6 Explicit NULL label. The 6PE RFC does talk
> about allowing signaling for the Explicit NULL label in which case the
> dataplane functionality becomes just the same, but in 6PE even that is
> signaled using BGP extensions defined in RFC3107.
>
> Thanks,
> Vishwas
>
>
> On Jan 31, 2008 2:14 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
>
>
> Hi,
>
> Just out of curiosity - lets say you have two IPv4 VPNs with
> overlapping set of Pes and both of them want to provide 6PE
> service.
> When the explicit-null encapsulated packets from two different
> VPNs (but same PE) arrive to the other side PE - how do you
> decide which is which - e.g. which packet should be shipped to
> which VPN ??
>
> Jan
>
>
> _________________________________________________________________
> Telly addicts unite!
> http://www.searchgamesbox.com/tvtown.shtml
>
>
>

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



From idr-bounces@ietf.org Thu Jan 31 12:32:09 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKdGf-0007Tn-1v; Thu, 31 Jan 2008 12:32:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKdGe-0007TY-1b
	for idr@ietf.org; Thu, 31 Jan 2008 12:32:04 -0500
Received: from wr-out-0506.google.com ([64.233.184.231])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKdGd-0002mh-LT
	for idr@ietf.org; Thu, 31 Jan 2008 12:32:04 -0500
Received: by wr-out-0506.google.com with SMTP id 50so890195wri.25
	for <idr@ietf.org>; Thu, 31 Jan 2008 09:32:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=qyHJmKd+h8yHEIZqV/rC7ldQbNbGC77s4VKqV25TKKE=;
	b=HmROfZ973W6JlxZW24momYi6L5ymvbHGKHpHjrNbOokR9oTsJ1BW1KEb7IYik5mTnpQh5XOxEIMbywWgl+lnksTs39OePgjrR/BZoigdbngz1iAOG5xp/HPiNvBtptGie5y8/hajaQJUIvuS8yEx4S6uUz/1LlHlBwQu5hDBHZ8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=P2i3wiGw3Uqwz3dWCh2NDFkpiNF+dSlCdOX/rCI6gR1JBGCHfFNEA0Usp2X3j6uluES/UMb/YTLsbNnMd0znsyyK4zChCdW4AW/jRaeOO/b5LDizlj23WHofz7ds/n5cYZfQKH8rnFcL67PzqlTQtIs4Xc+2lVHa8ku+r/o1OG4=
Received: by 10.142.215.5 with SMTP id n5mr1347755wfg.140.1201800721966;
	Thu, 31 Jan 2008 09:32:01 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Thu, 31 Jan 2008 09:32:01 -0800 (PST)
Message-ID: <77ead0ec0801310932i5d6ed617j3fe1df7674c0740f@mail.gmail.com>
Date: Thu, 31 Jan 2008 09:32:01 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Jan Novak" <jjjnovak@hotmail.com>
Subject: Re: [Idr] 6PE-Alt draft
In-Reply-To: <BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<BAY120-W1856D92C0C10B950241B43D8370@phx.gbl>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: idr@ietf.org, Francois Le Faucheur IMAP <flefauch@cisco.com>,
	Ooms Dirk <dirk@onesparrow.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

Hi Jan,

Unlike in BGP MPLS IP VPN, the label does not tell any interface as we
finally look up the only routing table the IPv6 routing table. We do
not have the VRF concept here. That is the reason we do not need any
presignaled label. The 6PE draft mentions why we need the top label
very clearly.

However they have wrongly decided to signal a label with each route
instead of just using the IPv6 Explicit NULL label.

Thanks,
Vishwas

On Jan 31, 2008 9:00 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
>
>
>
> Hi Vishwas,
>
> I believe you refer to this part of 6PE spec:
>
>    The label bound by MP-BGP to the IPv6 prefix indicates to the egress
>    6PE Router that the packet is an IPv6 packet.  This label advertised
>    by the egress 6PE Router with MP-BGP MAY be an arbitrary label value,
>    which identifies an IPv6 routing context or outgoing interface to
>    send the packet to, or MAY be the IPv6 Explicit Null Label.  An
>    ingress 6PE Router MUST be able to accept any such advertised label.
>
> I don't know what is the envisaged use of Explicit Null here - but I would think
> it is for some other purposes since to deliver the packet to the VPN this is
> still needed "identifies an IPv6 routing context or outgoing interface to".
>
> Jan
>
>
>
>
> _________________________________________________________________
> Share what Santa brought you
> https://www.mycooluncool.com

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



From idr-bounces@ietf.org Thu Jan 31 14:31:40 2008
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKf86-00073K-SC; Thu, 31 Jan 2008 14:31:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKf84-000735-J6
	for idr@ietf.org; Thu, 31 Jan 2008 14:31:20 -0500
Received: from rn-out-0910.google.com ([64.233.170.188])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKf82-0005pA-Pe
	for idr@ietf.org; Thu, 31 Jan 2008 14:31:20 -0500
Received: by rn-out-0910.google.com with SMTP id a46so358771rne.10
	for <idr@ietf.org>; Thu, 31 Jan 2008 11:31:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=KzCtmj/LRBTtElNUBet1ZySCz8H4XAZByBYfwWj9YCc=;
	b=B6uFvr/1GcGxYxNnZBqTg/Y9qtJf7cU8C7tYrUCs4wF4nlwiDA559k8z2/pp4Dk5QBIZvF9d6vKjTcrVVu4mByMKrESOkMpiVv0u+HUsXAxiTjrgk2fspaNeMeqUbVVckAzmAkH3K+Rnr+DqJaSEukM54aKSimxFfmIT8N1uo6s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=mEIg8sI/BpLmUfiZ6Hks9Eb5YCry46q9x9jC7iBCDTnWTNQcy9Vc1O3DbB5LUA+fQmlf2xMnDvvMtocVIyL/LWd1QBYvTnLwgn/COqVKWCedZu4U8vTIwfZg9xzePvDMGfI0FfW0nZNnLBTDQG0MDtQXAE8Sep1gB05aNkm2ylw=
Received: by 10.142.246.8 with SMTP id t8mr1515429wfh.8.1201807874636;
	Thu, 31 Jan 2008 11:31:14 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Thu, 31 Jan 2008 11:31:14 -0800 (PST)
Message-ID: <77ead0ec0801311131r372138fbh389becdd9e101402@mail.gmail.com>
Date: Thu, 31 Jan 2008 11:31:14 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Francois Le Faucheur IMAP" <flefauch@cisco.com>
Subject: Re: [Idr] 6PE-Alt draft
In-Reply-To: <77ead0ec0801310923q44251999i8af1b386c8c5bbc2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <BAY120-W259B9D353746E33D0864CED8370@phx.gbl>
	<77ead0ec0801310631r29449dafq961d8a9aecfea098@mail.gmail.com>
	<77ead0ec0801310700j55f10bcah2aae27dd0fea3927@mail.gmail.com>
	<C6F4F2F4-7113-4611-9723-425A49817D5B@cisco.com>
	<77ead0ec0801310923q44251999i8af1b386c8c5bbc2@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0aa019322dfce838bd8604f5a841b57
Cc: idr@ietf.org, Jan Novak <jjjnovak@hotmail.com>,
	Ooms Dirk <dirk@onesparrow.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

Forwarding Francois reply and my subsequent reply on the v6ops list,
to this list.

Thanks,
Vishwas
====================================================================
Hi Francois,

Thanks a lot for the reply.

It seems the only thing the 6PE RFC does is that it allows different
label allocation policies (for different routes), when no label
allocation is required at all.

If you think people will still use the 6PE approach even when they can
achieve the same without any new signaling extensions (a new AFI/SAFI
pair) then I am fine to position the draft as an option to your draft.
Do let me know if you feel that way?

Thanks,
Vishwas
- Hide quoted text -

On Jan 31, 2008 11:00 AM, Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
> Hi Vishwas,
>
> I think I've brought up my main points in the previous message so
> will leave it at that for now.
>
> On 31 Jan 2008, at 18:29, Vishwas Manral wrote:
>
> > Hi Francois,
> >
> > As the 6PE-Alt does not require any additional functionality from
> > BGP-IPv6 (yes that is the signaling required - but that is the same
> > required for normal BGP IPv6. For 6PE we use a new AFI/ SAFI and send
> > labels uselessly. So please do not say that the claim no signaling
> > changes are required for 6PE-Alt  is a stretch), and that is why we
> > have inter-operable implementations of 6PE-Alt too. It is not about
> > interoperable implementations alone though. I however am surprised how
> > this simple mechanism was not captured earlier in the review or coding
> > process.
> >
> > We do not need to transport labels at all which are now being
> > transported. Also as the peer decides the label I use, we may have to
> > configure different labels from different peers (thus using bigger
> > keys/ more memory in the tables and a lot of other overload). There is
> > a lot of overhead of signaling and dataplane without any necessity.
> >
> > I also have issues with the 6VPE RFC too but let us tackle issues one
> > at a time. Also please note 6VPE has the concept of VRF's and is used
> > to give VPN services, while VPE is used for basic IPv6 connectivity
> > over MPLS IPv4 coulds. So please do not confuse the 2.
>
> I didn't really feel confused about the 2, but thanks for the advise ^)
>
> Cheers
>
> Francois
>
>
> >
> > Thanks,
> > Vishwas
> >
> > On Jan 31, 2008 8:53 AM, Francois Le Faucheur IMAP
> > <flefauch@cisco.com> wrote:
> >>
> >> On 31 Jan 2008, at 15:25, Vishwas Manral wrote:
> >>
> >>> Hi Francois,
> >>>
> >>> The document I have written does not use signaling
> >>
> >> It is a bit of a stretch to claim that 6PE-Alt does not use
> >> signaling.
> >> 6PE-Alt and 6PE both use MP-BGP to signal IPv6 reachability.  6PE-Alt
> >> would simply save you one field (the label value) inside the same
> >> advertisement.
> >>
> >> On the other hand, 6PE-Alt would restrict operations to only one of
> >> the options allowed in 6PE. The reasons 6PE allowed multiple label
> >> allocation is precisely because different PEs may want to use
> >> different label allocation policies.  For example, one 6PE router may
> >> prefer to allocate per-prefix label in order to be able to forward
> >> packets via label switching as opposed to performing IPv6 lookup. 6PE
> >> allows each PR router to use whatever label allocation scheme it sees
> >> best.
> >>
> >>
> >>> and does not define
> >>> a new AFI/SAFI functionality to achieve the 6PE.
> >>
> >> It is a bit of a stretch to imply that 6PE defines a new AFI/SAFI.
> >> 6PE uses the IPv6 AFI and the SAFI defined in RFC3107 (which for
> >> memory dates back from 2001) precisely for the purpose of binding an
> >> MPLS label when advertising IPv6 reachability.
> >>
> >>>
> >>> The difference is obvious, we get the same functionality
> >>
> >> my impression is that you get a restricted subset of the
> >> functionality (ie forcing every router to use that single label
> >> allocation scheme). This had been discussed before and decided that
> >> such a restriction was undesirable and unnecessary.
> >>
> >>> without
> >>> adding any new signaling mechanism.
> >>
> >> my impression is that both use the same MP-BGP signaling mechanism
> >> except one would save a few bytes in the same MP-BGP advertisements.
> >>
> >> There are multiple interoperable implementations of 6PE today and am
> >> not aware of significant issues with the current 6PE control plane.
> >>
> >> Cheers
> >>
> >> Francois
> >>
>
>

On Jan 31, 2008 9:23 AM, Vishwas Manral <vishwas.ietf@gmail.com> wrote:
> Hi Francois,
>
> As the 6PE-Alt does not require any additional functionality from
> BGP-IPv6 (yes that is the signaling required - but that is the same
> required for normal BGP IPv6. For 6PE we use a new AFI/ SAFI and send
> labels uselessly. So please do not say that the claim no signaling
> changes are required for 6PE-Alt  is a stretch), and that is why we
> have inter-operable implementations of 6PE-Alt too. It is not about
> interoperable implmentations alone though. I however am surprised how
> this simple mechanism was not captured earlier in the review or coding
> process.
>
> We do not need to transport labels at all which are now being
> transported. Also as the peer decides the label I use, we may have to
> configure different labels from different peers (thus using bigger
> keys/ more memory in the tables and a lot of other overload). There is
> a lot of overhead of signaling and dataplane without any necessity.
>
> I also have issues with the 6VPE RFC too but let us tackle issues one at a time.
>
> Thanks,
> Vishwas
>
>
> On Jan 31, 2008 8:56 AM, Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
> >
> > Hi,
> >
> > FYI, here is a note posted on the v6ops list where that topic was brought up
> > first by Vishwas.
> >
> >
> >
> > Begin forwarded message:
> > From: Francois Le Faucheur IMAP <flefauch@cisco.com>
> > Date: 31 January 2008 17:53:54 GMT+01:00
> > To: Vishwas Manral <vishwas.ietf@gmail.com>
> > Cc: Francois Le Faucheur IMAP <flefauch@cisco.com>, v6ops@ops.ietf.org,
> > "Jeremy De Clercq" <jeremy.de_clercq@alcatel-lucent.be>, "Ooms Dirk"
> > <dirk@onesparrow.com>, stuart.prevost@bt.com
> > Subject: Re: 6PE-Alt
> >
> >
> > On 31 Jan 2008, at 15:25, Vishwas Manral wrote:
> >
> >
> > Hi Francois,
> >
> > The document I have written does not use signaling
> >
> > It is a bit of a stretch to claim that 6PE-Alt does not use signaling.
> > 6PE-Alt and 6PE both use MP-BGP to signal IPv6 reachability.  6PE-Alt would
> > simply save you one field (the label value) inside the same advertisement.
> >
> > On the other hand, 6PE-Alt would restrict operations to only one of the
> > options allowed in 6PE. The reasons 6PE allowed multiple label allocation is
> > precisely because different PEs may want to use different label allocation
> > policies.  For example, one 6PE router may prefer to allocate per-prefix
> > label in order to be able to forward packets via label switching as opposed
> > to performing IPv6 lookup. 6PE allows each PR router to use whatever label
> > allocation scheme it sees best.
> >
> >
> >
> > and does not define
> > a new AFI/SAFI functionality to achieve the 6PE.
> >
> > It is a bit of a stretch to imply that 6PE defines a new AFI/SAFI.
> > 6PE uses the IPv6 AFI and the SAFI defined in RFC3107 (which for memory
> > dates back from 2001) precisely for the purpose of binding an MPLS label
> > when advertising IPv6 reachability.
> >
> >
> >
> > The difference is obvious, we get the same functionality
> >
> > my impression is that you get a restricted subset of the functionality (ie
> > forcing every router to use that single label allocation scheme). This had
> > been discussed before and decided that such a restriction was undesirable
> > and unnecessary.
> >
> >
> > without
> > adding any new signaling mechanism.
> >
> > my impression is that both use the same MP-BGP signaling mechanism except
> > one would save a few bytes in the same MP-BGP advertisements.
> >
> > There are multiple interoperable implementations of 6PE today and am not
> > aware of significant issues with the current 6PE control plane.
> >
> > Cheers
> >
> > Francois
> >
> >
> >
> >
> >
> >
> > On 31 Jan 2008, at 16:00, Vishwas Manral wrote:
> >
> > Hi Jan,
> >
> > I am CC'ing the authors of the 6PE draft to get their views. Let me
> > explain the draft in greater detail however.
> >
> > In 6PE, MP-BGP SAFI family label is used to exchange routes between 2
> > 6PE routers (a new AFI/ SAFI combination is defined). Each route is
> > attached with a label (which may be the IPv6 Explicit NULL label). In
> > the data-plane this label is used as the inner label and the other
> > label is the tunnel label, which gets the packet from source PE to
> > destination PE. Once the packet gets to the destination PE, the inner
> > label is looked up and a POP operation is done on it and the IPv6
> > header is looked up in the routing table.
> >
> > With 6PE-Alt, no additional signaling mechanism is required. All we
> > need to do is instead of using the signaled label as the inner label,
> > we use the IPv6 Explicit NULL label. The same operations happen as 6PE
> > without any explicit signaling of the labels with each route. It helps
> > prevent all the excess signaling and still providing the exact same
> > functionality. We are using the meaning implied in the "Explicit NULL
> > Label". We do not need to signal anything here.
> >
> > As an alternate, if you notice in IPv6, the end sites/ devices will
> > become IPv6 and the network may still have IPv4. If the assumption
> > that each device in the IPv6 networks has a Global IPv6 address (not
> > that IPv6 site local has been deprecated), we can do without the
> > entire BGP MPLS IPv6 VPN functionality.
> >
> > Thanks,
> > Vishwas
> >
> > On Jan 31, 2008 6:31 AM, Vishwas Manral <vishwas.ietf@gmail.com> wrote:
> > Hi Jan,
> >
> > You may be missing the scope of the document. There is a discussion in
> > the v6ops group too which .
> >
> > The idea is simple. We do not need to define a new AFI/ SAFI
> > combination to achieve the 6PE functionality. We can just use the
> > meaning implied in the IPv6 Explicit NULL label. The 6PE RFC does talk
> > about allowing signaling for the Explicit NULL label in which case the
> > dataplane functionality becomes just the same, but in 6PE even that is
> > signaled using BGP extensions defined in RFC3107.
> >
> > Thanks,
> > Vishwas
> >
> >
> > On Jan 31, 2008 2:14 AM, Jan Novak <jjjnovak@hotmail.com> wrote:
> >
> >
> > Hi,
> >
> > Just out of curiosity - lets say you have two IPv4 VPNs with
> > overlapping set of Pes and both of them want to provide 6PE
> > service.
> > When the explicit-null encapsulated packets from two different
> > VPNs (but same PE) arrive to the other side PE - how do you
> > decide which is which - e.g. which packet should be shipped to
> > which VPN ??
> >
> > Jan
> >
> >
> > _________________________________________________________________
> > Telly addicts unite!
> > http://www.searchgamesbox.com/tvtown.shtml
> >
> >
> >
>

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



From idr-bounces@ietf.org  Thu Jan 31 18:46:50 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1CAD128C1E3;
	Thu, 31 Jan 2008 18:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xLcYAqcl20d3; Thu, 31 Jan 2008 18:46:48 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BFC9228C159;
	Thu, 31 Jan 2008 18:46:48 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 27AC728C159
	for <idr@core3.amsl.com>; Thu, 31 Jan 2008 18:46:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id An-xbbUPoAum for <idr@core3.amsl.com>;
	Thu, 31 Jan 2008 18:46:45 -0800 (PST)
Received: from gateway.ipinfusion.com (mail.ipinfusion.com [65.223.109.2])
	by core3.amsl.com (Postfix) with ESMTP id 2F02F28C14F
	for <idr@ietf.org>; Thu, 31 Jan 2008 18:46:44 -0800 (PST)
Received: from samitacD600 ([10.10.0.157])
	by gateway.ipinfusion.com (8.11.6/8.11.6) with ESMTP id m112k3430950;
	Thu, 31 Jan 2008 18:46:03 -0800
From: "Samita Chakrabarti" <samitac@ipinfusion.com>
To: <idr@ietf.org>, <quaizar.vohra@gmail.com>, <enkechen@cisco.com>
Date: Thu, 31 Jan 2008 18:46:10 -0800
Message-ID: <002f01c8647c$9dafb700$9d000a0a@samitacD600>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AchkfJnFg0bX62edRpC+ThO14/0EDg==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: [Idr] Comments on RFC4893
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hello Quaizar and Enke:

While reviewing RFC4893 (4-byte AS Number support for BGP), I have
encountered several questions related to interoperability and
implementation.

I am listing them below; my apology if they are already discussed in this
list before. (I am new in this mailing list)

It seems to me that the RFC has ambiguity in several places that needs to be
corrected from implementation perspective. Is there a plan for a revision?

Regards,
-Samita
----------------------------------------------------------------------------
----------------------------------------------------------------------------
RFC4893 is unclear about the processing of "My ASN" field in the OPEN
message. Section 3
 mentions about the capability message for 4byte ASN support:

"The Capability that is used by a BGP speaker to convey to its BGP peer the
4-octet Autonomous System number
 capability, also carries the 4-octet Autonomous System number of the
speaker in the Capability Value field of the
 Capability Optional Parameter. The Capability Length field of the
Capability is set to 4. "

and 
"We denote this special AS number as AS_TRANS for ease of description in the
rest of this
 specification. This AS number is also placed in the "My Autonomous System"
field of the 
OPEN message originated by a NEW BGP speaker, if the speaker does not have a
 (globally unique) 2-octet AS number." 

Clarification 1:
============
In section 4 it describes the interaction between NEW BGP speakers; it
discusses the UPDATE 
message processing with 
NEW and OLD BGP speakers. But  it does not discuss the OPEN message
send/recv in details;
the following cases need clarification:
1) NEW BGP speakers interactions: If the BGP speaker has a 2byte unique ASN
it uses the 
   2 byte ASN in the "My ASN" field of OPEN message. If the BGP speaker has
a 4 byte 
   non-mappable AS number, then it  uses AS_TRANS in "My ASN" field of OPEN
message.
2) Receiving OPEN message: If a NEW BGP speaker receives a OPEN message with
extended ASN
   capability, then it ignores the "My ASN" field of OPEN message and uses
the 4byte ASN
   value in the capability message. [ this will clarify the 
   ambiguity  and increases interoperability ]

Clarification 2:
=============
Scenario for AS_PATH.
 o-------------------o-------------------o----------------------o---------o
 OLD                     NEW                   NEW           OLD        NEW
 (50)                    (5000)             (65666)      (101)       (65777)

The RFC says that :
"4.2.1. BGP Peering Note that peering between a NEW BGP speaker and an OLD
one is possible 
only if the NEW BGP speaker has a 2-octet AS number. However, this document
does not assume 
that an Autonomous System with NEW speakers has to have a globally unique
2-octet AS number - AS_TRANS 
could be used instead (even if a multiple Autonomous System would use it)." 
-------
From the above text it is not clear whether a NEW BGP speaker with 4byte
non-mappable ASN
 can talk to the OLD BGP speaker or not.Practically it is not possible to
communicate with
 OLD and NEW BGP peer with non-mappable 4byte ASN (see the above scenario
where both peers of 
a OLD BGP are NEW with 4byte ASN). I assume that the RFC recommends :
     1)  If the NEW BGP speaker has a unique 2 byte ASN or a 2-byte-mappable
4byte ASN, it 
           SHOULD use the 2 byte ASN in the "My ASN field" for OPEN message.
     2) The NEW BGP with non-mappable 4byte ASN SHOULD not peer with OLD BGP
speaker; 
           this can easily produce routing loop or loss of ASN value in the
PATH.

Clarification 3
============
Section 3 of RFC4893 states:
"NEW BGP speakers carry AS path information expressed in terms of 4-octet
Autonomous Systems
 numbers by using the existing AS_PATH attribute, except that each AS number
in this
 attribute is encoded not as a 2-octet, but as a 4-octet entity."

 o-------------------o----------------------o-------------------
  NEW1                NEW2               OLD2                    OLD3
=====> Route Adv

In the above sequence of configuration, how does the OLD2 process the 4byte
ASN value in 
the AS_PATH  put by NEW1 ? The OLD BGP implementation is expected to use
2byte ASN value.
 Please clarify.
Should not it be easy and backward compatible if NEW BGP speakers always use
AS4_PATH for 
4byte ASN and use AS_PATH only when the ASNs are mappable to 2bytes?



Clarification 4
================

When the NEW BGP speaker has a non-mappable 4byte unique AS number and it is
peering with an OLD BGP
speaker, only then should it use AS_TRANS in AS_PATH and a corresponding
AS4_PATH 4byte
 AS number?
This should simplify reconstructing the AS number from both AS_PATH and
AS4_PATH and also
is in sync with AS4_AGGREGATOR processing as described in the RFC. 



section 4.2.2:
"When communicating with an OLD BGP speaker, a NEW speaker MUST send
   the AS path information in the AS_PATH attribute encoded with 2-octet
   AS numbers.  The NEW speaker MUST also send the AS path information
   in the AS4_PATH attribute (encoded with 4-octet AS numbers), except
   for the case where the entire AS path information is composed of 2-
   octet AS numbers only.  In this case, the NEW speaker SHOULD NOT send
   the AS4_PATH attribute."

The above rule is confusing from the implementation perspective. How about
making it simple by doing the same thing as AS_AGGREGATOR (as follows) ?

  "Similarly, if the NEW speaker has to send the AGGREGATOR attribute,
   and if the aggregating Autonomous System's AS number is truly 4-
   octets, then the speaker constructs the AS4_AGGREGATOR attributes by
   taking the attribute length and attribute value from the AGGREGATOR
   attribute and placing them into the attribute length and attribute
   value of the AS4_AGGREGATOR attribute, and sets the AS number field
   in the existing AGGREGATOR attribute to the reserved AS number,
   AS_TRANS.  Note that if the AS number is 2-octets only, then the
   AS4_AGGREGATOR attribute SHOULD NOT be sent."

I assume that "truly 4-octet" means it is higher than 65535.


Clarification 5
===================

Should the NEW BGP speaker send a NOTIFICATION with error code =2 and
subcode=7 
(unsupported capability) when it receives a OPEN message with AS_TRANS but
without
any corresponding capability message ?

Similarly, should a NEW BGP speaker with AS number higher than 65535, send a

NOTIFICATION to a OLD BGP speaker with error code =2 and subcode=7, before
closing the
peering connection ?


IMHO, the above NOTIFICATION is helpful for transition phase.



_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr
From idr-bounces@ietf.org  Thu Jan 31 18:56:59 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 93BC028C170;
	Thu, 31 Jan 2008 18:56:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0FngcvYpdBbM; Thu, 31 Jan 2008 18:56:58 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5EBCB28C101;
	Thu, 31 Jan 2008 18:56:58 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E34E28C0FD
	for <idr@core3.amsl.com>; Thu, 31 Jan 2008 18:56:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 36i884-6u1+A for <idr@core3.amsl.com>;
	Thu, 31 Jan 2008 18:56:56 -0800 (PST)
Received: from hs-out-2122.google.com (hs-out-0708.google.com [64.233.178.244])
	by core3.amsl.com (Postfix) with ESMTP id 0D53828C101
	for <idr@ietf.org>; Thu, 31 Jan 2008 18:56:55 -0800 (PST)
Received: by hs-out-2122.google.com with SMTP id 54so792522hsz.5
	for <idr@ietf.org>; Thu, 31 Jan 2008 18:58:29 -0800 (PST)
Received: by 10.142.252.11 with SMTP id z11mr1832373wfh.50.1201834708678;
	Thu, 31 Jan 2008 18:58:28 -0800 (PST)
Received: by 10.142.102.19 with HTTP; Thu, 31 Jan 2008 18:58:28 -0800 (PST)
Message-ID: <77ead0ec0801311858w5b9eec35q668c9e308dfb4706@mail.gmail.com>
Date: Thu, 31 Jan 2008 18:58:28 -0800
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: idr <idr@ietf.org>
In-Reply-To: <77ead0ec0801311546p40ad4e50jfa5ae868ff257a23@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <77ead0ec0801302108w3120b3a8uefd910567f43fb28@mail.gmail.com>
	<77ead0ec0801310625x285deb18u4b78a0b2089354ef@mail.gmail.com>
	<4F19CDE8-7704-4577-A2E6-DAD0A42A2081@cisco.com>
	<77ead0ec0801310929o16ab4207taf7e4308a1029bec@mail.gmail.com>
	<88FDC6C9EFCCEE4CA69577595AD6DB1501839267@FRVELSMBS22.ad2.ad.alcatel.com>
	<77ead0ec0801311311q3eef469fj23a99cfeaab475f5@mail.gmail.com>
	<88FDC6C9EFCCEE4CA69577595AD6DB150183926E@FRVELSMBS22.ad2.ad.alcatel.com>
	<77ead0ec0801311417x1f30f982v9c8b021fa27b9013@mail.gmail.com>
	<88FDC6C9EFCCEE4CA69577595AD6DB150183926F@FRVELSMBS22.ad2.ad.alcatel.com>
	<77ead0ec0801311546p40ad4e50jfa5ae868ff257a23@mail.gmail.com>
Subject: [Idr] Fwd: 6PE-Alt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Forwarding from the discussion on the v6ops list - on the draft.

---------- Forwarded message ----------
From: Vishwas Manral <vishwas.ietf@gmail.com>
Date: Jan 31, 2008 3:46 PM
Subject: Re: 6PE-Alt
To: DE CLERCQ Jeremy <jeremy.de_clercq@alcatel-lucent.be>
Cc: Francois Le Faucheur IMAP <flefauch@cisco.com>,
v6ops@ops.ietf.org, Ooms Dirk <dirk@onesparrow.com>,
stuart.prevost@bt.com


Hi Jeremy,

You are absolutely right.

This is not an alternate mechanism it is just an interesting way of
using already existing functionality BGP-IPv6 to derive the same
functionality as 6PE. We can get 6PE functionality without having to
do any different signaling at all.

It saves all the complicated mechanisms of label distribution, label
signaling, defining AFI/ SAFI and the complicated Inter-AS
distribution to achieve the same functionality. We do not need to
populate the hardware either with that many entries. I think that is
the idea of the draft.

Thanks,
Vishwas

On Jan 31, 2008 3:41 PM, DE CLERCQ Jeremy

<jeremy.de_clercq@alcatel-lucent.be> wrote:
> Hi Vishwas,
>
> Aha. Now I see; I got carried away by the discussion instead of looking
> at the draft ;).
>
> So the question remains whether the possible benefits of this solution
> justify bringing another alternative approach solving the same problem
> into the standards.
>
>
> Regards,
> Jeremy.
>
> >
> > Hi Jeremy,
> >
> > I agree a single level of label should not be used. The 6PE RFC
> > clearly talks about reasons for the same in great detail.
> >
> > That option should not be used and I agree to it. However the 6PE-Alt
> > approach uses 2 level of labels. The inner label is the Explicit NULL
> > label and the outer label is the tunnel label which gets the packet
> > from one 6Pe router to the other. The document below clearly misses
> > the idea of using a predefined label as the tunnel label.
> >
> > I hope things are clearer now to you.
> >
> > Thanks,
> > Vishwas
> >
> > On Jan 31, 2008 2:07 PM, DE CLERCQ Jeremy
> > <jeremy.de_clercq@alcatel-lucent.be> wrote:
> > > Hi Vishwas,
> > >
> > > I was refering to e.g. section 6.2 in
> > > draft-ietf-ngtrans-bgp-tunnel-02.txt, where it says
> > >
> > > "
> > > Where a single level of label is used and no label are advertised by
> > > MP-BGP, the SAFI used in MP-BGP will be one of the basic values:
> > > unicast, multicast or both (1,2 or 3).
> > > "
> > >
> > > With regards to the reason why the labelled approach was finally
> > > selected: it had to do on one hand with the main
> > applicability of the
> > > approach for routers that typically do labelled BGP distribution for
> > > VPNs, and on the other hand with the fact that the
> > advantages of using
> > > labelled distribution seemed to outweigh the disadvantages
> > like memory
> > > requirements etc.
> > >
> > > With regards to interoperability, what I meant was that it
> > was deemed
> > > better to have not too many optional and alternative
> > solutions in one
> > > RFC and to limit it to the chosen approach.
> > >
> > > Regards,
> > > Jeremy.
> > >
> > >
> > >
> > > > Hi Jeremy,
> > > >
> > > > I did look at the draft-ietf-ngtrans-bgp-tunnel-02.txt. I
> > could not
> > > > find a mention of the mechanism I have mentioned. Could you please
> > > > point me to the place where the mechanism is mentioned?
> > > >
> > > > BTW, the simple mechanism you talk about, adds a AFI/ SAFI pair to
> > > > BGP, unnecessarily passes labels around which are not
> > used at all. It
> > > > increases the memory requirement of each route, increases
> > the size of
> > > > the serach key and has complicated Transit provider
> > mechanisms. It in
> > > > turn clutters the forwarding tables with data which could
> > be easily
> > > > done without. The interesting part is the same could be
> > done without
> > > > any extensions at all.
> > > >
> > > > You seem to say that due to some interoperability
> > concerns you added
> > > > the mechanism to explicitly signal labels, which serve no
> > purpose. Can
> > > > you let me know which implementations had
> > interoperability concerns?
> > > > It would be great if you can give a more exact technical
> > reason of why
> > > > the approach we intend to bring to the IETF (which by default is
> > > > inter-operable - as no extensions are required). It is
> > hard to for a
> > > > person who has not been through the entire history to
> > understand the
> > > > same.
> > > >
> > > > Thanks,
> > > > Vishwas
> > > >
> > > > On Jan 31, 2008 12:56 PM, DE CLERCQ Jeremy
> > > > <jeremy.de_clercq@alcatel-lucent.be> wrote:
> > > > > Hi Vishwas,
> > > > >
> > > > > > I however am surprised how
> > > > > > this simple mechanism was not captured earlier in the
> > > > review or coding
> > > > > > process.
> > > > >
> > > > > The work that lead to what is now known as 6PE has seen
> > > > many forms and
> > > > > many many iterations. Including approaches without label
> > > > signaling and
> > > > > allocation, even including approaches without MPLS. You
> > > > should be able
> > > > > to find out about this history via earlier versions of the
> > > > draft like
> > > > > draft-nguyen-ngtrans-bgp-tunnel-00.txt and
> > > > > draft-ietf-ngtrans-bgp-tunnel-02.txt.
> > > > >
> > > > > So I'd say that this simple mechanism was captured earlier
> > > > but that it
> > > > > has been decided not to retain it, and to keep only one
> > mandatory
> > > > > procedure for interoperability purposes.
> > > > >
> > > > > At the end it was working group consensus and interoperable
> > > > > implementations that lead to the current 6PE approach.
> > > > >
> > > > > Regards,
> > > > > Jeremy
> > > > >
> > > >
> > >
> >
>
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr
From idr-bounces@ietf.org  Thu Jan 31 20:15:05 2008
Return-Path: <idr-bounces@ietf.org>
X-Original-To: ietfarch-idr-archive@core3.amsl.com
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B4D128C187;
	Thu, 31 Jan 2008 20:15:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aXbsXre-Y4yy; Thu, 31 Jan 2008 20:15:03 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6AB0928C13D;
	Thu, 31 Jan 2008 20:15:03 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B10D528C13D
	for <idr@core3.amsl.com>; Thu, 31 Jan 2008 20:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RMvP9ZDg6nDB for <idr@core3.amsl.com>;
	Thu, 31 Jan 2008 20:15:00 -0800 (PST)
Received: from mx.force10networks.com (corp.force10networks.com
	[64.186.164.204])
	by core3.amsl.com (Postfix) with ESMTP id 7E82528C0F0
	for <idr@ietf.org>; Thu, 31 Jan 2008 20:15:00 -0800 (PST)
Received: from EXCH-CLUSTER-03.force10networks.com ([10.11.0.53]) by
	mx.force10networks.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 31 Jan 2008 20:15:57 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 31 Jan 2008 20:15:53 -0800
Message-ID: <44ED058B21DF294ABE394CABE5C1B52102775B3B@EXCH-CLUSTER-03.force10networks.com>
In-Reply-To: <002f01c8647c$9dafb700$9d000a0a@samitacD600>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] Comments on RFC4893
Thread-Index: AchkfJnFg0bX62edRpC+ThO14/0EDgAB9ayQ
References: <002f01c8647c$9dafb700$9d000a0a@samitacD600>
From: "Kalpesh Zinjuwadia" <kzinjuwadia@force10networks.com>
To: "Samita Chakrabarti" <samitac@ipinfusion.com>, <idr@ietf.org>,
	<quaizar.vohra@gmail.com>, <enkechen@cisco.com>
X-OriginalArrivalTime: 01 Feb 2008 04:15:57.0348 (UTC)
	FILETIME=[24F65640:01C86489]
Subject: Re: [Idr] Comments on RFC4893
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/idr>,
	<mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Some comments inline.

Thanks,
Kalpesh

-----Original Message-----
From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of
Samita Chakrabarti
Sent: Thursday, January 31, 2008 6:46 PM
To: idr@ietf.org; quaizar.vohra@gmail.com; enkechen@cisco.com
Subject: [Idr] Comments on RFC4893

Hello Quaizar and Enke:

While reviewing RFC4893 (4-byte AS Number support for BGP), I have
encountered several questions related to interoperability and
implementation.

I am listing them below; my apology if they are already discussed in
this
list before. (I am new in this mailing list)

It seems to me that the RFC has ambiguity in several places that needs
to be
corrected from implementation perspective. Is there a plan for a
revision?

Regards,
-Samita
------------------------------------------------------------------------
----
------------------------------------------------------------------------
----
RFC4893 is unclear about the processing of "My ASN" field in the OPEN
message. Section 3
 mentions about the capability message for 4byte ASN support:

"The Capability that is used by a BGP speaker to convey to its BGP peer
the
4-octet Autonomous System number
 capability, also carries the 4-octet Autonomous System number of the
speaker in the Capability Value field of the
 Capability Optional Parameter. The Capability Length field of the
Capability is set to 4. "

and 
"We denote this special AS number as AS_TRANS for ease of description in
the
rest of this
 specification. This AS number is also placed in the "My Autonomous
System"
field of the 
OPEN message originated by a NEW BGP speaker, if the speaker does not
have a
 (globally unique) 2-octet AS number." 


Clarification 1:
============
In section 4 it describes the interaction between NEW BGP speakers; it
discusses the UPDATE 
message processing with 
NEW and OLD BGP speakers. But  it does not discuss the OPEN message
send/recv in details;
the following cases need clarification:
1) NEW BGP speakers interactions: If the BGP speaker has a 2byte unique
ASN
it uses the 
   2 byte ASN in the "My ASN" field of OPEN message. If the BGP speaker
has
a 4 byte 
   non-mappable AS number, then it  uses AS_TRANS in "My ASN" field of
OPEN
message.
2) Receiving OPEN message: If a NEW BGP speaker receives a OPEN message
with
extended ASN
   capability, then it ignores the "My ASN" field of OPEN message and
uses
the 4byte ASN
   value in the capability message. [ this will clarify the 
   ambiguity  and increases interoperability ]

Kalpesh> NEW BGP speaker (R1) will always put the 4-BYTE-AS capability
in the Open message, unless it's acting as OLD. "My AS" will contain the
actual AS if it's mappable to 2-byte field; else it will contain
AS-TRANS. OLD speaker (R2) will use AS-TRANS as R1's AS. NEW speaker
(R3) will use the ASN in the capability as R1's AS. R3 may also put
sanity check such as "My AS" can be AS-TRANS iff R1's actual ASN is
4-byte non-mappable.

Clarification 2:
=============
Scenario for AS_PATH.
 
o-------------------o-------------------o----------------------o--------
-o
 OLD                     NEW                   NEW           OLD
NEW
 (50)                    (5000)             (65666)      (101)
(65777)

The RFC says that :
"4.2.1. BGP Peering Note that peering between a NEW BGP speaker and an
OLD
one is possible 
only if the NEW BGP speaker has a 2-octet AS number. However, this
document
does not assume 
that an Autonomous System with NEW speakers has to have a globally
unique
2-octet AS number - AS_TRANS 
could be used instead (even if a multiple Autonomous System would use
it)." 
-------
From the above text it is not clear whether a NEW BGP speaker with 4byte
non-mappable ASN
 can talk to the OLD BGP speaker or not.Practically it is not possible
to
communicate with
 OLD and NEW BGP peer with non-mappable 4byte ASN (see the above
scenario
where both peers of 
a OLD BGP are NEW with 4byte ASN). I assume that the RFC recommends :
     1)  If the NEW BGP speaker has a unique 2 byte ASN or a
2-byte-mappable
4byte ASN, it 
           SHOULD use the 2 byte ASN in the "My ASN field" for OPEN
message.
     2) The NEW BGP with non-mappable 4byte ASN SHOULD not peer with OLD
BGP
speaker; 
           this can easily produce routing loop or loss of ASN value in
the
PATH.

Kalpesh> I don't know if I understand your question completely. However,
I don't think RFC puts any restriction on NEW BGP speaker with
non-mappable 4-byte ASN to communicate with OLD & NEW BGP speakers at
the same time. In your case, NEW speaker w/ ASN 65666 will communicate
differently with NEW speaker w/ ASN 5000 and OLD speaker w/ ASN 101.
Each speaker pair should be is treated independently and not confused
with others.


Clarification 3
============
Section 3 of RFC4893 states:
"NEW BGP speakers carry AS path information expressed in terms of
4-octet
Autonomous Systems
 numbers by using the existing AS_PATH attribute, except that each AS
number
in this
 attribute is encoded not as a 2-octet, but as a 4-octet entity."

 o-------------------o----------------------o-------------------
  NEW1                NEW2               OLD2                    OLD3
=====> Route Adv

In the above sequence of configuration, how does the OLD2 process the
4byte
ASN value in 
the AS_PATH  put by NEW1 ? The OLD BGP implementation is expected to use
2byte ASN value.
 Please clarify.
Should not it be easy and backward compatible if NEW BGP speakers always
use
AS4_PATH for 
4byte ASN and use AS_PATH only when the ASNs are mappable to 2bytes?

Kalpesh> NEW1 & NEW2 will exchange update with 4-byte AS-PATH & AGGR
attributes. However, when NEW2 advertises update to OLD2, it will split
4-byte AS-PATH attribute into 2-byte AS-PATH and 4-byte AS4-PATH using
the steps mentioned in RFC. Same goes for AGGR attribute. OLD2 & OLD3
will treat AS4-PATH & AS4-AGGR attributes as unknown opt-trans and pass
it further.


Clarification 4
================

When the NEW BGP speaker has a non-mappable 4byte unique AS number and
it is
peering with an OLD BGP
speaker, only then should it use AS_TRANS in AS_PATH and a corresponding
AS4_PATH 4byte
 AS number?
This should simplify reconstructing the AS number from both AS_PATH and
AS4_PATH and also
is in sync with AS4_AGGREGATOR processing as described in the RFC. 

Kalpesh> NEW speaker will generate AS4-PATH only if the AS-PATH to be
sent to OLD peer has at least 1 non-mappable 4-byte ASN. Hence, a NEW
speaker with 2-byte mappable AS may generate AS4-PATH if reqd.

section 4.2.2:
"When communicating with an OLD BGP speaker, a NEW speaker MUST send
   the AS path information in the AS_PATH attribute encoded with 2-octet
   AS numbers.  The NEW speaker MUST also send the AS path information
   in the AS4_PATH attribute (encoded with 4-octet AS numbers), except
   for the case where the entire AS path information is composed of 2-
   octet AS numbers only.  In this case, the NEW speaker SHOULD NOT send
   the AS4_PATH attribute."

The above rule is confusing from the implementation perspective. How
about
making it simple by doing the same thing as AS_AGGREGATOR (as follows) ?

  "Similarly, if the NEW speaker has to send the AGGREGATOR attribute,
   and if the aggregating Autonomous System's AS number is truly 4-
   octets, then the speaker constructs the AS4_AGGREGATOR attributes by
   taking the attribute length and attribute value from the AGGREGATOR
   attribute and placing them into the attribute length and attribute
   value of the AS4_AGGREGATOR attribute, and sets the AS number field
   in the existing AGGREGATOR attribute to the reserved AS number,
   AS_TRANS.  Note that if the AS number is 2-octets only, then the
   AS4_AGGREGATOR attribute SHOULD NOT be sent."

I assume that "truly 4-octet" means it is higher than 65535.

Kalpesh> I think conditions mentioned for generating AS4-PATH & AS4-AGGR
are inherently same. For AS-PATH all ASN in it are considered for AGGR
the aggregating ASN is considered.

Yes "truly 4-octet" ASN means ASN > 65535.

Clarification 5
===================

Should the NEW BGP speaker send a NOTIFICATION with error code =2 and
subcode=7 
(unsupported capability) when it receives a OPEN message with AS_TRANS
but
without
any corresponding capability message ?

Kalpesh> RFC doesn't discuss how NEW speaker should behave when OLD
speaker uses AS-TRANS in "My AS" field. Behavior is implementation
dependent.

Similarly, should a NEW BGP speaker with AS number higher than 65535,
send a

NOTIFICATION to a OLD BGP speaker with error code =2 and subcode=7,
before
closing the
peering connection ?

Kalpesh> What caused NEW BGP speaker to close the connection with OLD
peer? If same as previous question, again it's implementation dependent.

IMHO, the above NOTIFICATION is helpful for transition phase.



_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr
_______________________________________________
Idr mailing list
Idr@ietf.org
http://www.ietf.org/mailman/listinfo/idr
