Re: ASON reqts

[Jonathan Sadler <jonathan.sadler@tellabs.com>]

Deborah -

The authors should provide them, along with their reasoning why.

Stating compliance with the requirements docs requires being
familiar with the material in those documents.  Likewise, dropping
the items handled in RFC 3474 would requires an active decision to
be made by the authors.  The document should include this reasoning.

For those unfamiliar with some of the differences, a cursorary review
of the G.7713 reveals:
  - Discussion of required behavior at E-NNI and UNI reference points
  - Support for complete Call/Connection separation, including
    0-connection calls

These are documented by RFC 3474.

Others can be found by looking at G.8080, and G.8080 Amd. 1.

Jonathan Sadler

"Brungard, Deborah A, ALABS" wrote:

> Hi Jonathan,
>
> We need specifics-
> Deborah
>
> -----Original Message-----
> From: Jonathan Sadler [mailto:jonathan.sadler@tellabs.com]
> Sent: Tuesday, May 13, 2003 7:57 PM
> To: Kireeti Kompella
> Cc: ccamp@ops.ietf.org
> Subject: Re: ASON reqts
>
> Kireeti -
>
> "I have read this document, and it isn't ready to be a CCAMP doc".
>
> Currently, the document excludes a number of requirements specified in G.8080,
> and G.7713 that are handled by RFC 3474.  No information is provided in the
> document or on the CCAMP list why these were dropped.
>
> I would also like to know why it is referencing outdated documents (ex.
> [IPO-ASON] was published in March 2002) when more recent
> requirements/architecture material is available.
>
> Jonathan Sadler
>
> Kireeti Kompella wrote:
>
> > Hi All,
> >
> > On Fri, 2 May 2003, Kireeti Kompella wrote:
> >
> > > To take things one at a time, it would be very useful to read and comment
> > > on the ASON reqts draft, as this was deemed tremendously important, and
> > > a rich source of misunderstanding and cross-talk; and coming to a common
> > > understanding over this should help get the IETF and the ITU working
> > > together.
> >
> > I haven't seen many comments, so the assumption is either that no
> > one cares, or that folks have read it and have no issues.
> >
> > I'd like to get a reading on whether this doc is ready to be a
> > CCAMP WG document.  Please respond (preferably publicly) with one of:
> >  - "I have read this document and it is ready to be a CCAMP WG doc" OR
> >  - "I have read this document, and it isn't ready to be a CCAMP doc".
> >
> > Note that if there aren't enough responses, the default assumption is
> > that the document is either not of interest or not ready, and in
> > either case will not become a CCAMP WG doc.  Note too that this doc
> > is an attempt to bridge some gaps between the IETF and the ITU-T,
> > and as such is fairly important.  It would be useful to give an
> > update on its status at the interim T1X1 meeting in June.
> >
> > Please get your responses in by COB Friday May 16th.
> >
> > Thanks,
> > Kireeti.
>
> ============================================================
> The information contained in this message may be privileged
> and confidential and protected from disclosure.  If the
> reader of this message is not the intended recipient, or an
> employee or agent responsible for delivering this message to
> the intended recipient, you are hereby notified that any
> reproduction, dissemination or distribution of this
> communication is strictly prohibited. If you have received
> this communication in error, please notify us immediately by
> replying to the message and deleting it from your computer.
>
> Thank you.
> Tellabs
> ============================================================

============================================================
The information contained in this message may be privileged 
and confidential and protected from disclosure.  If the 
reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to 
the intended recipient, you are hereby notified that any 
reproduction, dissemination or distribution of this 
communication is strictly prohibited. If you have received 
this communication in error, please notify us immediately by 
replying to the message and deleting it from your computer.

Thank you.
Tellabs
============================================================