The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-Dec> msg00176



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

Last Call on MPLS ping

  • From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
  • Date: Tue, 10 Dec 2002 10:55:26 -0800
  • Cc: mpls@UU.NET

> -----Original Message-----
> From: Eric Rosen [mailto:erosen@cisco.com]
> Sent: Monday, December 09, 2002 12:38 PM
> Alia> So,  my concern  here  is  for the  case  where the  
> route  is not  an
> Alia> aggregate  and the label  indicates the  egress 
> attachment  circuit as
> Alia> well as the encapsulation header for the packet. 
> 
> Alia> In  this case,  LSP ping  would send  an IP  packet 
> with  the specific
> Alia> route's label and then the PSN's label. 
> 
> That isn't  my interpretation of the  draft.  I think the  
> intention is that
> the LSP  ping carries only  the "PSN label".   That is, it 
> carries  only the
> label  or labels  needed to  get it  to the  egress PE,  not 
> the  label that
> identifies a particular VPN route (or a particular PWE3 pseudowire). 
> 
> If  you wanted  to  know not  only whether  a  particular LSP 
>  leads to  the
> intended PE,  but also whether that PE  is a proper egress  
> for a particular
> VPN route (or PWE3  pseudowire), then I think you would need  
> to use the FEC
> stack TLV in the body of the message to identify that VPN route.
> 

But how do you test that the VPN route is bound to the proper PW label?


-Shahram