[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ASON reqts

To: "Stephen Trowbridge" <sjtrowbridge@lucent.com>,"John Drake" <jdrake@calient.net>
Subject: Re: ASON reqts
From: "Adrian Farrel" <afarrel@movaz.com>
Date: Mon, 12 May 2003 19:09:25 -0400
Cc: "'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>,"Kireeti Kompella" <kireeti@juniper.net>, <ccamp@ops.ietf.org>
References: <9D42C6E086250248810DCADA39CE7EFC972551@nimbus> <3EC011A9.D62C5364@lucent.com>

> Back to Bert's original questions:
> > > > > - is there or do we see any conflict?
> - As Zhi said, this is not (yet) fully aligned with ITU-T requirements
>   and should not be advanced to a WG document until it is. However, before
>   we do, I think we need to understand why this is necessary - see below.

Notwithstanding the immediate future of this document (WG or not WG) I would
greatly appreciate a summary of the areas that are deficient.

Thanks,
Adrian

References:
- RE: ASON reqts
  - From: John Drake <jdrake@calient.net>
- Re: ASON reqts
  - From: Stephen Trowbridge <sjtrowbridge@lucent.com>

Prev by Date: Re: ASON reqts
Next by Date: RE: ASON reqts
Previous by thread: Re: ASON reqts
Next by thread: Re: ASON reqts
Index(es):
- Date
- Thread