RE: ASON reqts

["Hirokazu Ishimatsu" <hirokazu.ishimatsu@japan-telecom.co.jp>]

List,

I have read this document and it is ready to be a CCAMP WG doc

because of 2 in Steve's email.

Hiro Ishimatsu


> I think I have detected the following motivations from 
> different posts in the thread:
> 
> 1. Those who don't want this to be a WG document (we are done with
>    this version of the specifications, lets get some experience
>    with them before considering any further change or evolution).
> 
> 2. Those who think this should be a WG document so that ASON 
> extensions
>    currently standardized in ITU-T will get standards track status in
>    IETF (no intent to change the protocol, but document the superset
>    in one place so that we don't get so many GMPLS implementations
>    that don't support the ASON extensions).
> 
> 3. Those who think there is nothing wrong with the ITU-T extensions to
>    meet the ASON requirements, but believe that RFC 3474 
> didn't translate
>    G.7713.2 properly and this draft is a first step to fixing 
> RFC 3474.
> 
> 4. Those who think that even the ITU-T extensions don't meet the ASON
>    requirements, so IETF should now take it over and do it 
> better starting
>    with this draft.
> 
> 5. Those who think that ITU-T didn't get the requirements right, so we
>    need to look at everything from scratch.
> 
> Regards,
> Steve