Internet Draft Network Working Group John Yu Internet Draft Fong Liaw Expiration Date: January 2001 Eric Gray Zaffire, Inc. RSVP Extensions in Support of OIF UNI draft-yu-mpls-rsvp-oif-uni-ext-00.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [1]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This document proposes extensions to signaling defined in "RSVP-TE: Extensions to RSVP for LSP Tunnels" ([2]) as needed to support an Optical Cross-Connect (OXC) User Network Interface (UNI). This effort is in part driven by work in "Signaling Requirements at the Optical UNI" ([3]) but is also intended to be consistent with "Generalized MPLS - Signaling Functional Description" ([4]). This draft reflects ongoing work at the Optical Interworking Forum (OIF). 1. Introduction This document describes how RSVP-TE [2] with extensions may be used as a signaling mechanism for the OXC UNI. [3] defines several OXC UNI abstract messages. This document shows how existing RSVP-TE messages are used to full-fill applicable requirements associated with these abstract messages. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [5]. 2. Overview RSVP-TE is one of the candidate protocols described in [3] for OXC UNI signaling implementation. [3] requires signaling capabilities for creating, deleting and modifying light paths across a network of optical cross-connect switches and querying status of an existing light path. Most of these capabilities may be directly supported by re-using existing messages and objects defined in RSVP-TE [2]. Support of the OXC UNI signaling requirements depends upon the following RSVP behaviors and mechanisms as defined in [2]. - Use of Path messages including the LABEL_REQUEST object. - Use of Resv messages including the LABEL object. - Use of PathErr and ResvErr messages and error codes and values defined in [2]. - Use of PathTear messages. Additional messages are defined to support the propagation of light path status information as defined in [3]. Additional objects are defined for support of attributes defined in [3]. Not all of the abstract messages defined in [3] are supported in this document. 2.1. Use of RSVP-TE messages for the OXC UNI . +------------------+ | An ASCII Picture | | | +------------------+ 2.2. Another Meaty Sub-section 3. Another Meaty Section 3.1. And a Meaty Sub-section 3.2. ... 4. ... 5. Security Considerations A Security Considerations section generally MUST be included if the author has any serious hopes of seeing the draft be accepted by the IESG. 6. References [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [2] Awduche, D. O., Berger, L., Gan, D.-H., Li, T., Swallow, G., Srinivasan, V., "Extensions to RSVP for LSP Tunnels", Work in Progress (Internet Draft), draft-ietf-mpls-rsvp-lsp-tunnel-06.txt, July 2000. [3] Aboul-Magd, O., Aparicio, O., Barry, R., Bernstein, G., Jain, R., Jia, L., Dulepet, R., Lazer, M., Yates, J., Pendarakis, D., Rajagopalan, B., Rennison, R., Xu, Y., Xue, Y., Yu, J. and Zhang, Z., "Signaling Requirements at the Optical UNI", Work in Progress (Internet Draft), July 2000. [4] Ashwood-Smith, P., Fan, Y., Banerjee, A., Drake, J., Lang, J., Berger, L., Bernstein, G., Kompella, K., Mannie, E., Rajagopalan, B., Saha, S., Tang, Z., Rekhter, Y. and Sharma, V., "Generalized MPLS - Signaling Functional Description", Work in Progress (Internet Draft), draft-ashwood-generalized-mpls-signaling-00.txt, June 2000. [5] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119 (BCP 14), March 1997. [17] Awduche, D. O., Rekhter, Y., Drake, J., Coltun, R., "Multi-Protocol Lambda Switching: Combining MPLS Traffic Engineering Control with Optical Crossconnects," Internet Draft, draft-awduche-mpls-te-optical-00.txt, October 1999. [40] Katz, D., Yeung, D., "Traffic Engineering Extensions to OSPF," Internet Draft, 1999 [50] Smit, H. and Li, T., "IS-IS extensions for Traffic Engineering," Internet Draft, 1999. 7. Acknowledgments This document relies heavily on text from drafts referenced as well as additional text by many of the same authors. 8. Author's Addresses John Z. Yu Zaffire, Inc. 2630 Orchard Parkway San Jose, CA 95134 email: jzyu@zaffire.com Fong Liaw Zaffire, Inc. 2630 Orchard Parkway San Jose, CA 95134 email: fliaw@zaffire.com Eric Gray Zaffire, Inc. 2630 Orchard Parkway San Jose, CA 95134 Email: egray@zaffire.com Yu, et al Page 2