The MPLS WG Archive

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



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

[PWE3] MPLS PID

  • From: "Yaakov Stein" <yaakov_s@rad.com>
  • Date: Wed, 26 Mar 2003 18:07:58 +0200
  • Cc: <pwe3@ietf.org>, <mpls@UU.NET>
  • Thread-Index: AcLzpSf9PkyqhDWCQlOuxKT7VMdhEgADAg+Q
  • Thread-Topic: [PWE3] MPLS PID
  • X-MIME-Autoconverted: from quoted-printable to 8bit by cell.onecall.net id h2RGcqP21919

> One possibility for an extended PID that comes to mind is 
> defining one of the remaining 14 values within the first nibble as "extended PID" 
> and follow it with whatever PID definition you like.

Another, which I proposed in draft-stein-pwe3-controlword-00.txt, 
is to use the 4 bits to disambiguate the relevant possibilities.

Since an atm-encap implementation will probably not understand
ethernet-encap, the non 4/6 values could be used for submodes
(e.g. 1:1, N:1, PDU, SDU).
Similarly, the TDM sub-identifier could differentiate between
raw,  AAL1, AAL2, etc.

Alternatively, we could go for a "sanity check"
PWE identifier. We have 14 values available
and so far have only defined a few PW types
(ATM, FR, SONET, TDM, ethernet).

Y(J)S