The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2000-Dec> msg00001



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

AW: New MPLS charter

  • From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
  • Date: Fri, 1 Dec 2000 10:51:56 +0100
  • Cc: mpls@UU.NET

Georg,
  
you wrote"...we can define new ways of carrying labels where new kinds of link layers may emerge out of the Optical work".
Let me think in this direction:
Let me call all so far defined LSPs "User Plane LSPs" because they  transmit user data (in such a way that no transit-LSR will
evaluate the IP Header of the user data packets).
We may define as well "Control Plane LSPs": They should transmit only messages for establishing/terminating User Plane LSPs.
Hereby the "Control Plane" labels should only be used to determine the next hop( = replacement of the longest prefix match mechanism).
Each transit-LSR should evaluate the IP Header and even the entire
"Control Plane" packet =MPLS-message like RSVP-PATH or a CRLDP-LABEL_REQUEST,... 
Remains the question how and when to install the NHLFEs of the "Control Plane" labels: Well, BGP4, PIM, LDP-unsolicited
downstream may be used to install them.

The benefit: The establishing of User Plane LSPs by means of RSVP resp.  LDP-downstream-on-demand, can be done 
almost as fast as transmitting user data by the User Plane LSP.

Another goal:
Studying and specifying the case where a Control Plane LSP and any of its associated User Plane LSPs only share
the common endpoints but not the route between these endpoints.


What do you think ?

Heinrich Hummel
Siemens AG
heinrich.hummel@icn.siemens.de
 

	--------------------------------------------------------------------- 
> Spencer -
> 
> The way I read that (and I would like to be wrong on this, but doubt
> that I am) is we can define new ways of carrying labels where new
> kinds of link layers may emerge out of the Optical work.  Also I don't
> really anticipate any need in that area, since we already have an
> encapsulation over PPP and PPP is likely to be defined over any thing
> that emerges out of the optical work.
> 
> ...George
> 
> ==================================================================
> George Swallow       Cisco Systems                   (978) 244-8143
>                      250 Apollo Drive
>                      Chelmsford, Ma 01824