The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Jan> msg00313



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Labelled route across AS

  • From: Robert Raszuk <raszuk@cisco.com>
  • Date: Sun, 28 Jan 2001 23:20:12 -0800
  • CC: "erosen@cisco.com" <erosen@cisco.com>, "mpls@uu.net" <mpls@UU.NET>
  • Organization: Signature: http://www.employees.org/~raszuk/sig/


First let me clarify - that by the "route" you mean the customer
external not your peer's AS next hops. If that is the case I would not
talk about "redistribution" as this at least to me means transfer a
route from one routing protocol to the other but the more appropriate
term would be "propagate" as all we are talking about here is a
EBGP/IBGP propagation. 

So to answer your question about next hop both scenarios are possible
and adopted. In the small Inter-AS architectures where number of
inter-as routes does not exceed the capacity of edge box setting next
hop on the edge is fine. When a number of routes grow and your vpnv4
ebgp session is being extended from vpnv4 RRs then setting nhs on them
would not be advisable.

R.

> Radha PK wrote:
> 
> Hi,
> When a labelled route is received (by an ASBR) from a peer in a different AS, the route is redistributed into the AS.
> During this redistribution, the NextHop (to the address of ASBR doing the redistribution) and also the label could be changed
> Or
> Just redistribute the label and the route as they were received from the ASBR.
> 
> Could anyone suggest me as to which of these are usually adopted?
> Pls correct me if my interpretations are wrong.
> 
> With Regards.
> Radha
> 
> _____________________________________________________
> Chat with your friends as soon as they come online. Get Rediff Bol at
> http://bol.rediff.com