The MPLS WG Archive

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



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

[PWE3] MPLS PID

  • From: "Thomas D. Nadeau" <tnadeau@cisco.com>
  • Date: Wed, 26 Mar 2003 10:34:22 -0500
  • Cc: "Andrew G. Malis" <Andy.Malis@vivacenetworks.com>, "'mpls@uu.net'" <mpls@UU.NET>

At 02:18 PM 3/25/2003 -0800, Shahram Davari wrote:

> >1.  Dealing with ECMP behavior
> >2.  Inband OAM flows
> >3.  Identifying flows for netmanagement applications.
> >
>
>I don't think any of them justifies adding PID.
>
>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.

>2) OAM flows could use IPv4/V6 null or MPLS Alert label

         Encased in the PW or just as a label stack?

>3) Netmanagment could identify the flow at the ingress.

         What about the egress?

         --Tom


>-Shahram


http://www.elsevier-international.com/catalogue/title.cfm?ISBN=155860751X

  • References: