1. 64th IETF Vancouver November 2005 ASON-Compatible Signaling

2. 64th IETF Vancouver November 2005 Current Status draft-ietf-ccamp-gmpls-rsvp-te-ason-04.txt –No real progress on document for around a year Two experimental implementations have been made –Draft tries to do two things Point out how existing RFCs and I-Ds can be used to meet the requirements of ASON signaling –Requirements in RFC 4139 Define protocol extensions to “fill the gaps” Propose to split the I-D along these lines We need to do both items according to charter There is interest in standardized implementation

3. 64th IETF Vancouver November 2005 Filling the Remaining Gap The remaining gap in GMPLS signaling is support for Calls OIF/RFC3474 approach not acceptable –Designed for UNI not NNI –Piggy-backs call information on Path message –Requires retention of call state within network –Does not allow connection-free calls –Can’t add or remove connections from calls

4. 64th IETF Vancouver November 2005 GMPLS Call Support Use Notify messages –Can be targeted to “Call Controllers” –End points and domain boundaries Notify message carries full details of call Path message can associate a connection with a call Allows independent call/connection setup and management Cleaned-up document –Aim to publish after Vancouver –Plans to implement at once –Last call soon

5. 64th IETF Vancouver November 2005 Applicability Statement The other piece of the work “Applicability of GMPLS signaling to the requirements of an ASON architecture” Short draft based on documented requirements –Pointers to RFCs and I-Ds –Extract material from existing draft Update and polish –Add information for support of calls Just a documentation task