1 / 6

ASON Routing Requirements

ASON Routing Requirements. draft-alanqar-ccamp-gmpls-ason-routing-reqts-00.txt

jemima
Download Presentation

ASON Routing Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ASON Routing Requirements draft-alanqar-ccamp-gmpls-ason-routing-reqts-00.txt Wesam Alanqar (Sprint) - Deborah Brungard (ATT) - Dave Meyer (1-4-5 Net) Lyndon Ong (Ciena) - Dimitri Papadimitriou (Alcatel) - Jonathan Sadler (Tellabs) Stephen Shew (Nortel)

  2. DT Charter • Understand the requirements to support ASON routing • Capture what's missing in a "GMPLS ASON Routing Requirements" document • Rules (same as for ASON signaling requirements): no requirement that is not an ASON routing requirement (as decided by SG 15/Q12 and SG 15/Q14) will be considered in this document

  3. Warnings • No attempt in the "GMPLS ASON Routing Requirements" document to do protocol design or suggest any protocol extension • Standard design team disclaimer: this design team has no special status in the CCAMP WG. Any document produced is subject to the usual WG procedures

  4. First Cut (-v00.txt) • Template • Architectural model and assumptions • Functional requirements (tba) • support of multiple hierarchical levels • support of multiple data plane layers • support architectural evolution (levels, aggregation, segmentation)

  5. Milestones - Where we are... • Oct'03: Liaison to SG 15 stating creation of DT and charter (completed/to be sent) <http://psg.com/lists/ccamp/ccamp.2003/msg00891.html> • Oct'03: first draft of ASON routing requirements document (template completed) • Nov'03: first CCAMP WG document on ASON routing requirements • Nov'03: Liaison to SG 15 soliciting input on above WG document • Dec'03: CCAMP WG Last Call • Jan'04: hand off document to IESG

  6. ITU-T Liaison • 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 Nov. 2003. We wish to work with you cooperatively on this document and we would appreciate your assistance in reviewing this draft.

More Related