RE: ITU Liaison regarding ASON Requirements Design Team

["Lam, Hing-Kam (Kam)" <hklam@lucent.com>]

Hi,

This is a resend to include the ccamp list as I got notices of Undelivery to some of the addressees from the Mail sever.

Regards,
Kam Lam 
ITU-T Q14/15 Rapporteur

> -----Original Message-----
> From: Lam, Hing-Kam (Kam) 
> Sent: Wednesday, November 19, 2003 8:51 AM
> To: 'Kireeti Kompella'; 'adrian@olddog.co.uk'
> Cc: 'Scott Bradner'; 'Alex Zinin'; 'Bill Fenner';
> 'betts01@nortelnetworks.com'; 'tsg15q14@itu.int'; 'tsg15q12@itu.int'
> Subject: RE: ITU Liaison regarding ASON Requirements Design Team
> 
> 
> Dear Mr. Kompella and Mr. Farrel,
> 
> In addition to our request for your feedback on signalling 
> protocol extensions for ASON, we will also appreciate any 
> detail information related to your comments raised during the 
> June Q14/15 meeting regarding potential issues with G.7713.2. 
> In particular, the following would be very helpful:
> To show the detailed message flows as defined in ASON, and 
> point out which message sequence causes the issues (and
> reference the RFC text that conflicts -- thus causing 
> issues). The reference that would be relevant here would be 
> RFC 2205 (the original RSVP protocol definition), RFC 3209 
> (RSVP-TE), RFC 3473 (GMPLS extensions), and RFC 2209 (an 
> informational document discussing the message processing rules).
> 
> Regards,
> Kam Lam
> Q14/15 Rapporteur
> 
> > -----Original Message-----
> > From: Lam, Hing-Kam (Kam) 
> > Sent: Tuesday, November 18, 2003 3:36 PM
> > To: 'Kireeti Kompella'; 'adrian@olddog.co.uk'
> > Cc: Scott Bradner; Alex Zinin; Bill Fenner; 
> > betts01@nortelnetworks.com;
> > 'tsg15q14@itu.int'; 'tsg15q12@itu.int'
> > Subject: RE: ITU Liaison regarding ASON Requirements Design Team
> > 
> > 
> > Dear Mr. Kompella and Mr. Farrel,
> > 
> > Thank you for your liaison statement regarding ccamp's ASON 
> > Requirements Design Team. We are looking forward to reveiw 
> > its output when the document is available.
> > 
> > Regarding ASON signalling protocol extensions, please note 
> > that in the June 2003 Q14/15 Chicago interim meeting, a 
> > liaison statement
> > (ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltranspor
> > t/COMMUNICATIONS/ccamp/IETF_ccamp_sigprotocol.html) 
> > was sent to ccamp. We will appreciate your feedback regarding 
> > SG15's suggestion on signalling protocol extensions for ASON.
> > 
> > Regards,
> > Kam Lam
> > Q14/15 Rapporteur
> > 
> > > -----Original Message-----
> > > From: Kireeti Kompella [mailto:kireeti@juniper.net]
> > > Sent: Saturday, November 15, 2003 4:02 PM
> > > To: betts01@nortelnetworks.com; hklam@lucent.com
> > > Cc: Scott Bradner; Alex Zinin; Bill Fenner; ccamp@ops.ietf.org
> > > Subject: ITU Liaison regarding ASON Requirements Design Team
> > > 
> > > 
> > > Dear Mr. Lam and Mr. Betts,
> > > 
> > > We would like to inform Q12/15 and Q14/15 that IETF CCAMP WG has
> > > initiated a Design Team on GMPLS ASON Routing Requirements. 
> > The GMPLS
> > > ASON Routing Requirements Design Team's Charter is as follows:
> > > 
> > > "To understand the requirements for ASON routing so as to capture
> > > what's missing from current CCAMP work in a "GMPLS ASON Routing
> > > Requirements" document.  The ground rules are the same as for ASON
> > > signaling requirements: no requirement will be considered in this
> > > document that is not an ASON routing requirement (as 
> > decided by those
> > > working on Questions 12 and 14 of Study Group 15).  Requirements
> > > should be justified briefly and prioritized. If needed, a 
> section on
> > > terminology should be included. No attempt should be made in this
> > > document to do protocol design or suggest protocol extensions."
> > > 
> > > We expect to liaison to you a draft of the above WG 
> document during
> > > Dec. 2003.  We wish to work with you cooperatively on 
> this document
> > > and we would appreciate your assistance in reviewing this draft.
> > > 
> > > Thank you,
> > > Kireeti Kompella & Adrian Farrel
> > > CCAMP WG chairs, IETF
> > > 
> > 
>