Internet DRAFT - draft-wu-pce-pcep-ls-sr-extension
draft-wu-pce-pcep-ls-sr-extension
Network Working Group N. Wu
Internet-Draft Z. Li
Intended status: Standards Track Huawei Technologies
Expires: March 7, 2016 September 4, 2015
PCEP Link-State Extensions for Segment Routing
draft-wu-pce-pcep-ls-sr-extension-00
Abstract
This document introduces extensions of PCEP Link-State to export path
segment information to a PCE.
Requirements Language
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 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on March 7, 2016.
Copyright Notice
Copyright (c) 2015 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
(http://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
Wu & Li Expires March 7, 2016 [Page 1]
Internet-Draft PCEP-LS for SR September 2015
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
2. PCEP Extensions for Segment Routing . . . . . . . . . . . . . 2
2.1. Node Attribute TLVs . . . . . . . . . . . . . . . . . . . 2
2.2. Link Attribute TLVs . . . . . . . . . . . . . . . . . . . 3
2.3. Prefix Attribute TLVs . . . . . . . . . . . . . . . . . . 3
3. Operational Considerations . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
PCE-LS [I-D.dhodylee-pce-pcep-te-data-extn] is designed to collect
topology information and TED across IGP domains. In order to better
support SR-TE, this document introduces extensions of PCEP-LS to
export path segment information.
2. PCEP Extensions for Segment Routing
PCEP-LS [I-D.dhodylee-pce-pcep-te-data-extn] introduces new message
type and new object to accommodate link-state information in PCEP.
This document defines new additional TLVs to accommodate segment
routing information. The value portion of these new TLVs can reuse
the structure defined in [I-D.ietf-isis-segment-routing-extensions]
and [I-D.ietf-idr-bgpls-segment-routing-epe].
2.1. Node Attribute TLVs
New
optional, non-transitive node attribute TLVs are defined for carrying
segment routing information and are listed as below:
Wu & Li Expires March 7, 2016 [Page 2]
Internet-Draft PCEP-LS for SR September 2015
+--------------+-----------------------+----------+-----------------------+
|TLV Code Point| Description | Length | Value defined |
+--------------+-----------------------+----------+-----------------------+
| TBD1 | SID/Label Binding | variable | [ISIS-SR]#section2.4 |
+--------------+-----------------------+----------+-----------------------+
| TBD2 | SR-Capabilities | variable | [ISIS-SR]#section3.1 |
+--------------+-----------------------+----------+-----------------------+
| TBD3 | SR-Algorithm | variable | [ISIS-SR]#section3.2 |
+--------------+-----------------------+----------+-----------------------+
[ISIS-SR]: https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/
Table 1: Node Attribute TLVs
2.2. Link Attribute TLVs
New optional, non-transitive link attribute TLVs are defined for
carrying segment routing information and are listed below:
+--------------+-----------------------+----------+-----------------------+
|TLV Code Point| Description | Length | Value defined |
+--------------+-----------------------+----------+-----------------------+
| TBD4 | Adjacency Segment | variable | [ISIS-SR]#section2.2.1|
+--------------+-----------------------+----------+-----------------------+
| TBD5 | LAN Adjacency Segment | variable | [ISIS-SR]#section2.2.2|
+--------------+-----------------------+----------+-----------------------+
| TBD6 | Peer Segment | variable | [BGPLS-SR]#section4.3 |
+--------------+-----------------------+----------+-----------------------+
| TBD7 | Peer-Set Segment | variable | [BGPLS-SR]#section4.3 |
+--------------+-----------------------+----------+-----------------------+
[ISIS-SR]: https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/
[BGPLS-SR]:http://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/
Table 2: Link Attribute TLVs
2.3. Prefix Attribute TLVs
A new optional, non-transitive link attribute TLV is defined for
carrying segment routing information and are listed below:
+--------------+-----------------------+----------+-----------------------+
|TLV Code Point| Description | Length | Value defined |
+--------------+-----------------------+----------+-----------------------+
| TBD8 | Prefix Segment | variable | [ISIS-SR]#section2.1.2|
+--------------+-----------------------+----------+-----------------------+
[ISIS-SR]: https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/
Table 3: Prefix Attribute TLVs
Wu & Li Expires March 7, 2016 [Page 3]
Internet-Draft PCEP-LS for SR September 2015
3. Operational Considerations
The procedure for segment routing information reporting from PCC to
PCE will follow those defined in
[I-D.dhodylee-pce-pcep-te-data-extn].
4. IANA Considerations
TBD.
5. Security Considerations
This document does not introduce new security threat.
6. References
6.1. Normative References
[I-D.dhodylee-pce-pcep-te-data-extn]
Dhody, D., Lee, Y., and D. Ceccarelli, "PCEP Extension for
Transporting TE Data", draft-dhodylee-pce-pcep-te-data-
extn-02 (work in progress), March 2015.
[I-D.ietf-idr-bgpls-segment-routing-epe]
Previdi, S., Filsfils, C., Ray, S., Patel, K., Dong, J.,
and M. Chen, "Segment Routing Egress Peer Engineering BGP-
LS Extensions", draft-ietf-idr-bgpls-segment-routing-
epe-00 (work in progress), June 2015.
[I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Filsfils, C., Bashandy, A., Gredler, H.,
Litkowski, S., Decraene, B., and J. Tantsura, "IS-IS
Extensions for Segment Routing", draft-ietf-isis-segment-
routing-extensions-05 (work in progress), June 2015.
[I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,
and r. rjs@rob.sh, "Segment Routing Architecture", draft-
ietf-spring-segment-routing-04 (work in progress), July
2015.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
Wu & Li Expires March 7, 2016 [Page 4]
Internet-Draft PCEP-LS for SR September 2015
6.2. Informative References
[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
Element (PCE) Communication Protocol (PCEP)", RFC 5440,
DOI 10.17487/RFC5440, March 2009,
<http://www.rfc-editor.org/info/rfc5440>.
Authors' Addresses
Nan Wu
Huawei Technologies
Huawei Bld., No.156 Beiqing Rd.
Beijing 100095
China
Email: eric.wu@huawei.com
Zhenbin Li
Huawei Technologies
Huawei Bld., No.156 Beiqing Rd.
Beijing 100095
China
Email: lizhenbin@huawei.com
Wu & Li Expires March 7, 2016 [Page 5]
