The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2003-Mar> msg00328



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

[PWE3] MPLS PID

  • From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
  • Date: Wed, 26 Mar 2003 12:34:28 -0800
  • Cc: "Andrew G. Malis" <Andy.Malis@vivacenetworks.com>, "'mpls@uu.net'" <mpls@UU.NET>, tnadeau@cisco.com

>>
>>1) ECMP could use only label hashing and not hash IP header.
>
>         This is unrealistic. Lots of vendors hash on both,
>one or the other.  Lets not go down the road of trying
>to mandate how ECMP works again. We went down that
>road in MPLS and the response was clear.

Hashing on IP header is not part of any IETF standard, and I am not sure all future IETF
standards should be based on supporting non-standard proprietary implementations. if one likes
to still hash IP header, then he could define a proper protocol mux header and use it all the time.


>
>>2) OAM flows could use IPv4/V6 null or MPLS Alert label
>
>         Encased in the PW or just as a label stack?

Tunnel Label - PW label - IPV4/6 explicit null. And hash only up to 2nd label.

>
>>3) Netmanagment could identify the flow at the ingress.
>
>         What about the egress?

Also egress could identify the flow from bottom label.

-Shahram

>
>         --Tom
>
>
>>-Shahram
>
>