The Path Computation Element Communication Protocol (PCEP) Extension for Wavelength Switched Optical Network (WSON) Routing and Wavelength Assignment (RWA)
RFC 8780

Document Type RFC - Proposed Standard (July 2020; No errata)
Last updated 2020-07-21
Replaces draft-lee-pce-wson-rwa-ext
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Daniele Ceccarelli
Shepherd write-up Show (last changed 2017-01-12)
IESG IESG state RFC 8780 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to "Daniele Ceccarelli" <daniele.ceccarelli@ericsson.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack


Internet Engineering Task Force (IETF)                       Y. Lee, Ed.
Request for Comments: 8780                           Samsung Electronics
Category: Standards Track                               R. Casellas, Ed.
ISSN: 2070-1721                                                     CTTC
                                                               July 2020

The Path Computation Element Communication Protocol (PCEP) Extension for
   Wavelength Switched Optical Network (WSON) Routing and Wavelength
                            Assignment (RWA)

Abstract

   This document provides Path Computation Element Communication
   Protocol (PCEP) extensions for the support of Routing and Wavelength
   Assignment (RWA) in Wavelength Switched Optical Networks (WSONs).
   Path provisioning in WSONs requires an RWA process.  From a path
   computation perspective, wavelength assignment is the process of
   determining which wavelength can be used on each hop of a path and
   forms an additional routing constraint to optical path computation.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8780.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction
   2.  Terminology
   3.  Requirements Language
   4.  Encoding of an RWA Path Request
     4.1.  Wavelength Assignment (WA) Object
     4.2.  Wavelength Selection TLV
     4.3.  Wavelength Restriction TLV
       4.3.1.  Link Identifier Field
       4.3.2.  Wavelength Constraint Field
     4.4.  Signal Processing Capability Restrictions
       4.4.1.  Signal Processing Exclusion
       4.4.2.  Signal Processing Inclusion
   5.  Encoding of an RWA Path Reply
     5.1.  Wavelength Allocation TLV
     5.2.  Error Indicator
     5.3.  NO-PATH Indicator
   6.  Manageability Considerations
     6.1.  Control of Function and Policy
     6.2.  Liveness Detection and Monitoring
     6.3.  Verifying Correct Operation
     6.4.  Requirements on Other Protocols and Functional Components
     6.5.  Impact on Network Operation
   7.  Security Considerations
   8.  IANA Considerations
     8.1.  New PCEP Object: Wavelength Assignment Object
     8.2.  WA Object Flag Field
     8.3.  New PCEP TLV: Wavelength Selection TLV
     8.4.  New PCEP TLV: Wavelength Restriction TLV
     8.5.  Wavelength Restriction TLV Action Values
     8.6.  New PCEP TLV: Wavelength Allocation TLV
     8.7.  Wavelength Allocation TLV Flag Field
     8.8.  New PCEP TLV: Optical Interface Class List TLV
     8.9.  New PCEP TLV: Client Signal Information TLV
     8.10. New Bit Flag for NO-PATH-VECTOR TLV
     8.11. New Error-Types and Error-Values
     8.12. New Subobjects for the Exclude Route Object
     8.13. New Subobjects for the Include Route Object
     8.14. Request for Updated Note for LMP TE Link Object Class Type
   9.  References
     9.1.  Normative References
     9.2.  Informative References
   Acknowledgments
   Contributors
   Authors' Addresses

1.  Introduction

   [RFC5440] specifies the Path Computation Element Communication
   Protocol (PCEP) for communications between a Path Computation Client
   (PCC) and a PCE, or between two PCEs.  Such interactions include Path
   Computation Requests (PCReqs) and Path Computation Replies (PCReps)
   as well as notifications of specific states related to the use of a
   PCE in the context of Multiprotocol Label Switching (MPLS) and
   Generalized MPLS (GMPLS) Traffic Engineering (TE).

   A PCC is said to be any network component that makes such a request
   and may be, for instance, an optical switching element within a
   Wavelength Division Multiplexing (WDM) network.  The PCE, itself, can
   be located anywhere within the network and may be within an optical
   switching element, a Network Management System (NMS), or an
   Operational Support System (OSS), or it may be an independent network
Show full document text