RE: ASON reqts

[Kireeti Kompella <kireeti@juniper.net>]

Hi Vishal,

On Wed, 14 May 2003, Vishal Sharma wrote:

> I've been following this discussion for some time now, and would
> like to second the proposal you've made below. Namely, that
> we have a companion document that covers extensions for routing
> as well.

Okay, noted.

> Both documents would then have to be progressed in tandem within
> the WG, because, as Ben rightly observed, routing specifications
> do influence what is carried in signaling.

The progress of GMPLS signaling and routing was always separate, as
can be seen even now: signaling has been an RFC for some time now,
whereas routing is still in Last Call.

In fact, the charter states that signaling and routing be kept
separate:
 - Define signalling and measurement protocols that are independent of
   each other.  This allows applications other than the signalling
   protocol to use the measurement protocol; it also allows the
   signalling protocol to use knowledge obtained by means other than the
   measurement protocol.

This is not to say that they must be developed separately, but a
too-strong tie between them would hurt the above goal.

Finally, there is a need for GMPLS for ASON signaling requirements,
whereas there doesn't appear to be such a pressing need for GMPLS
for ASON routing requirements.

Kireeti.