1. 1 Requirements for Generalized MPLS (GMPLS) Usage and Extensions for Automatically Switched Optical Network (ASON) (draft-ietf-ccamp-gmpls-ason-reqts-04.txt) Jerry Ash AT&T gash@att.com Dimitri Papadimitriou, Editor Alcatel dimitri.papadimitriou@alcatel.be John Drake Calient jdrake@calient.net Lyndon Ong Ciena lyong@ciena.com Adrian Farrel Olddog Consulting adrian@olddog.co.uk

2. 2 Outline (draft-ietf-ccamp-gmpls-ason-reqts-04.txt) qbrief review of problem statement & requirements for GMPLS signaling extensions for ASON v‘you read the draft’ qchanges from 01 to 04 version qnext steps

3. 3 Problem Statement for GMPLS Extensions for ASON qproblem statement vextend GMPLS signaling [RFC 3471/RFC 3473] –must meet FULL functional requirements of ASON architecture in GMPLS provide call & connection management [G.7713] –must be BACKWARD COMPATIBLE with current GMPLS RFCs vASON architecture includes –automated control plane supporting both call & connection management [G.8080] –control plane applicable to different transport technologies (e.g., SDH/SONET, OTN) & networking environments (e.g., inter-carrier, intra-carrier) –multiple reference points of information exchange between administrative domain & user between administrative domains & areas within administrative domain between controllers within areas

4. 4 Requirements for GMPLS Extensions for ASON qneed to support ASON functionality in GMPLS vsoft permanent connection capability vcall & connection separation (includes calls without connections & adding/removing connections to/from calls) vcall segments vextended restart capabilities during control plane failures vextended label association vcrankback capability vadditional error cases

5. 5 Changes from 01 to 04 Version qIntroduction vrefine reference point terminology (UNI, E-NNI, I-NNI) vASON model distinguishes reference points (representing points of protocol information exchange) –between an administrative domain & a user a.k.a. user-network interface (UNI) –between administrative domains a.k.a. external network- network interface (E-NNI) –between areas of the same administrative domain & between controllers within areas a.k.a. internal network-network interface (I-NNI) qterminology section: add UNI term qreview of author list

6. 6 Changes from 01 to 04 Version qSection 4: Requirements for Extending Applicability of GMPLS to ASON vdefinition of GMPLS [RFC 3473] compliant UNI: –‘any User-Network Interface (UNI) that is compliant with [RFC 3473] is considered, by definition, to be a GMPLS UNI and must be supported’ –[GMPLS-OVERLAY] & [GMPLS-VPN] meet definition of GMPLS UNI vrefine agnosticism criteria wrt UNI implementation for GMPLS support of ASON requirements –‘support of GMPLS-ASON signaling protocol requirements must be strictly independent of & agnostic to any UNI & not be constrained by implementation specifics of the UNI [G.8080, G.7713]’

7. 7 Changes from 01 to 04 Version qrefine interworking aspects of non-GMPLS address space/signaling mapping vend-to-end signaling should be facilitated regardless of administrative boundaries & protocols within the network –includes both GMPLS control domains & non-GMPLS control domains vI-D addresses ASON support within a GMPLS control domain & between GMPLS control domains vI-D does not restrict use of other protocols within a control domain –mapping of non-GMPLS protocol signaling requests & support of non-GMPLS address formats are responsibility of non- GMPLS control domain

8. 8 Changes from 01 to 04 Version qadd Section 5: Backward Compatibility vfollowing comment at IETF-57 & discussion on list vsection defines backward compatibility wrt GMPLS signaling extensions for ASON: –in a network where some nodes support GMPLS signaling extensions for ASON & some do not, it must be possible to set up conventional connections per [RFC 3473] between any pair of nodes & traversing any set of nodes –use of GMPLS signaling extensions for ASON to set up calls must not perturb existing conventional connections –transit nodes in the path of a connection that do not need to participate in the new ASON-related functions must be able to pass call setup information onwards, unmodified –transit or egress nodes called upon to participate in the ASON- related functions, but not supporting the functions, must be able to reject calls by pre-existing GMPLS signaling mechanisms in a way not detrimental to the network

9. 9 Next Steps qno open issues at this point qauthors feel this I-D is ready for WG last call vdraft-ietf-ccamp-gmpls-ason-reqts-04.txt qprogress GMPLS signaling extensions for ASON qprogress GMPLS routing requirements & protocol extensions for ASON