The MPLS WG Archive

[Curtis Villamizar <curtis@fictitious.org>]

In message <9D42C6E086250248810DCADA39CE7EFC9722BB@nimbus>, John Drake writes:
> 
> 
> > -----Original Message-----
> > From: Yangguang Xu [mailto:xuyg@lucent.com]
> > Sent: Wednesday, March 05, 2003 2:55 PM
> > To: Dimitri.Papadimitriou@alcatel.be; Zhi-Wei Lin
> > Cc: mpls@UU.NET
> > Subject: Re: I-D ACTION:draft-andersson-mpls-g-chng-proc-00.txt
> > 
> > 
> > Hello,
> > 
> > Some thoughts below, related to both John and Dimitri's response.
> > 
> > We need to differentitate end-to-end operation and 
> > edge-to-edge operation first.
> > GMPLS deals with edge-to-edge connection, G.7713 extends the scope to
> > end-to-end.
> 
> JD:  Oh really?  Where did you read that limitation on the scope of GMPLS?


WG charter.
   
   The CCAMP working group coordinates the work within the IETF
   defining a common control plane and a separate common measurement
   plane for ISP and SP core tunneling technologies.

and 

   - Using input from the TE working group, ensure that the signalling
     and measurement protocols provide both the information and the
     control functions adequate to support the traffic provisioning
     and engineering operations of service providers.

GMPLS is for "core tunneling technologies" and requirements are to
come from the TE-WG.

GMPLS is not intended for end to end connections according to the WG
charter.

ASON or any end to end connection oriented technology is not accepted
by the IESG or IETF as a whole as a requirement and therefore there is
no WG to work on ASON requirements.

The closest thing to ASON is PWE3 which is definitely not ASON.

Perhaps the best thing would be for ASON to be considered in a
requirements WG (like IPO, but separate from IPO) and reviewed, not
rubber stamped.  This would be consistent with the current process
which is for an internet-draft to be reviewed by a WG, the IESG, then
the IETF last call and IESG/IAB decision.  There have been requests
for requirements in the past that were far enough outside of the IETF
mainstream to warent a WG to defined the requirements.

Curtis