The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2003-Nov> msg00134



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

on the mpls oam framework

  • From: "Thomas D. Nadeau" <tnadeau@cisco.com>
  • Date: Tue, 18 Nov 2003 07:53:57 -0500
  • Importance: Normal
  • Organization: Cisco Systems, inc.



>-----Original Message-----
>From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com] 
>Sent: Tuesday, November 18, 2003 4:48 AM
>To: 'tnadeau@cisco.com'; mpls@UU.NET
>Subject: RE: on the mpls oam framework 
>
>
>>	While I would of course agree that knowing all of the
>>algorithms would make things easier, I disagree that we cannot
>>move forward with solutions today. I think that solutions can be 
>>created to manage what is deployed today. There is clear evidence
>>of this already.
>>
>>	--Tom
>
>How can one create solutions to manage deployed boxes, without 
>knowing how they behave? for example how can you design the VCCV if you
don't know 
>which fields in the header are used today to hash ECMP. As an example
>the Alert Label (in VCCV) won't work with implementations that 
>hash all label stack.

	Using the example of LSP Ping, you ask the boxes 
what they are going to do. In the case of VCCV,
we don't care because we aren't tracing, just following
whatever path the data takes.

	--Tom