End-to-end L2-LSP

["CHO, JAI HYUNG" <jaihyung@etri.re.kr>]

Dear all,

Greetings.

I am a co-editor of the Ethernet-GMPLS framework document. 
(draft-papadimitriou-ccamp-gmpls-ethernet-framework-00.txt)

I am writing this to explain the motivation behind the 
proposal of scenario-1, and to raise the issue of 
end-to-end LSP to be included in CCAMP charter.

An important goal intended in scenario-1 is 
QoS control over end-to-end packet delivery using LSP. 
In other words, the purpose of scenario-1 is extending coverage 
of GMPLS control including customer network and end-user device, 
such as PC, VoIP phone, IP-TV, or even future 4G mobile phone. 
End-user applications will have a means to request resources 
to network using GMPLS signal.

Unfortunately, this view is not included in the 
framework because there was strong opinion that 
L2-LSP must not span beyond provider network because 
CCAMP is not chartered to work on customer 
network. I am wondering if this is right argument. 
Perhaps the charter can be amended to include this work.

I believe there is little technical reason to preclude 
LSP being used in customer network. It is a reasonable 
assumption that private company may also use GMPLS 
implemented Ethernet switch, once the L2SC work is successful. 
Currently, CCAMP is the only place discussing the matter of 
Ethernet and LSP. There is no other WG dealing similar issue. 
If CCAMP wants to work on Ethernet, 
I think the coverage of common GMPLS control must be 
extended to include all area where Ethernet is deployed. 
Currently, Ethernet is dominantly deployed in first-mile 
network where access network as well as customer network 
and user hosts are usually included. Therefore, user host must 
be considered as initiation and termination point of L2-LSP.

Another important reason to include user host in CCAMP 
work scope is to achieve consistent end-to-end control of QoS. 
End-to-end QoS has long been desired goal since RSVP was 
first designed. This goal can be best achieved using 
end-to-end GMPLS signal and L2-LSP. 
Currently, RSVP (RFC2205) is available in many user hosts. 
There is only a little difference between RSVP and RSVP-TE. 
If the RSVP-TE signal of provider network can reach user host 
across Ethernet based private network, an LSP can be established 
from application to application via the provider backbone. 
Service providers will be able to control application flows 
in L2-LSP level as well as in aggregated LSP pipe of similar 
application type. A variety of new services will be enabled using 
the enhanced capability of distinguishing and controlling each 
individual application flow.

I personally believe that end-to-end L2-LSP may offer 
innovative solutions for servicing IP-TV as well as fast mobility. 
There have been some experimental approaches combining 
MPLS and IP mobility. However such potential of the new 
application can only be explored when end-user host is 
included in the scope of CCAMP work area.

Therefore, I hereby sincerely request people's attention 
and support on this perspective of end-to-end LSP. 
If there is enough number of people agree on this view, 
the WG can request the necessary update of the charter.

Thank you.
 
Jaihyung Cho
 
 
 
ETRI, Korea
phone :       042) 860-5514
oversea: +82-42-860-5514
fax:         +82-42-861-5550