RE: ASON reqts

["Ash, Gerald R (Jerry), ALABS" <gash@att.com>]

Yangguang,

> Woke up too early. Thought reading this document may put me 
> back to sleep, well, it didn't :-) So nice work, just some 
> clarifications:
> 
> -- Support for SPC. 
> I understand SPC but don't think the first requirement to 
> GMPLS signaling is MUST. It depends on implementation, doesn't it?

See the ASON requirements summary ('identified gaps') presented by ITU-T (Steve Trowbridge) to CCAMP at IETF-53 (March 2002) http://ietf.org/proceedings/02mar/slides/ccamp-4/sld005.htm.  Note the inclusion of SPC and crankback, both are MUST.

SPC is required by ASON, it was included in the first Recommendation on Requirements for the Automatic Switched Transport Networks (G.807 published in 2001).  For operators, SPC support is considered as a critical application for ASON.  Until UNI/E-NNI support functionality is available (e.g. billing systems/directory services), this will likely be the first application for most operators of ASON.  For example, in ITU-T Rec'd G.7713.1 on ASON PNNI (consented January 2003), it is only concerned with specifying soft permanent connections.
 
> -- Support for crankback. 
> I think we may want to separate fault localization and crankback, 
> as the former may be more desirable. Also, not a big fan of 
> crankback, I'd like to know more details about the crankback 
> requirement. For example, is crankback a must or optional? is 
> crankback a must at inter-domain interface or also a must at
> intra-domain interface?  (I hope requirement only document 
> what must be done)

Again, ASON requirements/'identified gaps' include crankback as a MUST, inter-domain and inter-domain.  It is already included in G.7713.1 and G.7713.3.  More information on crankback is available in the draft http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-05.txt.

Thanks,
Jerry

> 
> That what I have so far.
> 
> Regards,
> 
> Yangguang  
> 
> Kireeti Kompella wrote:
> > 
> > On Fri, 2 May 2003, Brungard, Deborah A, ALABS wrote:
> > 
> > > 
> http://www.ietf.org/internet-drafts/draft-papadimitriou-ccamp-gmpls-ason-reqts-00.txt
> 
> 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 think it would be very useful to progress this document in a timely
> fashion, so I encourage folks to read and comment on it; and perhaps
> in a week or two, to check for consensus to progress it.
> 
> > Good reading material for a weekend -
> 
> Agreed, for both documents.
> 
> Thanks, Deborah!
> 
> Kireeti.