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

Re: ASON reqts



> > > 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.
> >
> > Pointers please.
> > There was no intention to drop any requirement so please let us know what is
> > missing.
>
> See my previous email to Deborah, as well as G.7713, G.8080, and G.8080 Amd.
1.
>
> NB: All of these documents have been liaised to the IETF.  The liaison
statements
> including the documents can be found under the CCAMP link at:
>
>
ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltransport/COMMUNICATIONS/in
dex.html

Will respond to you email to Deborah separately.
With regards to your comments here...
This isn't an accademic guessing game - if you have specific constructive
comments along the lines of "requirement xyz as specificed in dogument G.1234
section a.b.c is missing" then please say so. The authors are trying to do their
best and are asking for helpful input.

> > > 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.
> >
> > Well, there is no reason not to reference this material at this stage.
Indeed,
> > someone just asked for it to be referenced, I think.
>
> Unfortunately, the IPO-ASON draft referenced doesn't include a number of the
> conceptual items developed after the consent of G.8080 in Oct. 2001.  Many of
these
> items were added in G.8080 Amd. 1 and G.7713.2, both of which were consented
in
> January of 2003.
>
> > With regard to other material, again please provide pointers and we will
happily
> > read and reference is as appropriate.
>
> G.8080 as updated by G.8080 Amd. 1, and G.7713.2 are more up to date.

Ah, OK. No new references. Just a query about whether IPO-ASON is ood.
It may be ood but it also provides relevant IETF b/g.
So it stays for the moment and either it gets republished, or the ref gets
dropped later.

Thanks,
Adrian