< draft-chen-bier-pce-bier-02.txt   draft-chen-bier-pce-bier-03.txt >
Networking Working Group Ran. Chen Networking Working Group Ran. Chen
Internet-Draft Zheng. Zhang Internet-Draft Zheng. Zhang
Intended status: Standards Track ZTE Corporation Intended status: Standards Track ZTE Corporation
Expires: July 8, 2017 January 4, 2017 Expires: January 16, 2018 July 15, 2017
PCEP Extensions for BIER PCEP Extensions for BIER
draft-chen-bier-pce-bier-02 draft-chen-bier-pce-bier-03
Abstract Abstract
Bit Index Explicit Replication (BIER)-TE shares architecture and Bit Index Explicit Replication (BIER)-TE shares architecture and
packet formats with BIER as described in packet formats with BIER as described in
[I-D.ietf-bier-architecture]. BIER-TE forwards and replicates [I-D.ietf-bier-architecture]. BIER-TE forwards and replicates
packets based on a BitString in the packet header, but every packets based on a BitString in the packet header, but every
BitPosition of the BitString of a BIER-TE packet indicates one or BitPosition of the BitString of a BIER-TE packet indicates one or
more adjacencies.BIER-TE Path can be derived from a Path Computation more adjacencies.BIER-TE Path can be derived from a Path Computation
Element (PCE). Element (PCE).
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 8, 2017. This Internet-Draft will expire on January 16, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 5 skipping to change at page 4, line 5
4.1.1. The OPEN Object 4.1.1. The OPEN Object
This document defines a new optional TLV for use in the OPEN Object. This document defines a new optional TLV for use in the OPEN Object.
4.1.1.1. The BIER PCE Capability TLV 4.1.1.1. The BIER PCE Capability TLV
The BIER-PCE-CAPABILITY TLV is an optional TLV associated with the The BIER-PCE-CAPABILITY TLV is an optional TLV associated with the
OPEN Object to exchange BIER capability of PCEP speakers. The format OPEN Object to exchange BIER capability of PCEP speakers. The format
of the BIER-PCE-CAPABILITY TLV is shown in the following figure: of the BIER-PCE-CAPABILITY TLV is shown in the following figure:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Flags | | Reserved | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1 Figure 1
The code point for the TLV type is to be defined by IANA. The code point for the TLV type is to be defined by IANA.
skipping to change at page 5, line 14 skipping to change at page 5, line 14
4.2.2. The New BIER END-POINT Object 4.2.2. The New BIER END-POINT Object
The END-POINTS object is used in a PCReq message to specify the BIER The END-POINTS object is used in a PCReq message to specify the BIER
information of the path for which a path computation is requested. information of the path for which a path computation is requested.
To represent the end points for a BIER path efficiently, we define a To represent the end points for a BIER path efficiently, we define a
new END-POINT Object for the BIER path: new END-POINT Object for the BIER path:
The format of the new END-POINTS Object is as follows: The format of the new END-POINTS Object is as follows:
0 1 2 3 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Subdomain-ID | BS Length | Source BFR-id | |Subdomain-ID | BS Length | Source BFR-id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination BFR-id ~ ... ~ | Destination BFR-id ~ ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ... ~ Destination BFR-id | ~ ... ~ Destination BFR-id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 Figure 2
skipping to change at page 7, line 35 skipping to change at page 7, line 35
TBD. TBD.
6. IANA Considerations 6. IANA Considerations
6.1. PCEP Objects 6.1. PCEP Objects
As discussed in Section 4.2.2, a new END-POINTS Object-Type is As discussed in Section 4.2.2, a new END-POINTS Object-Type is
defined. IANA has made the following Object-Type allocations from defined. IANA has made the following Object-Type allocations from
the "PCEP Objects" sub-registry: the "PCEP Objects" sub-registry:
Object Object-Class Value Object Object-Class Value
----------------------- -------------------------- --------------------- --------------------------
BIER END-POINT Object TBD BIER END-POINT Object TBD
As discussed in Section 4.2.3 and 4.2.4, a new sub-object type for As discussed in Section 4.2.3 and 4.2.4, a new sub-object type for
the PCEP explicit route object (ERO), and a new sub-object type for the PCEP explicit route object (ERO), and a new sub-object type for
the PCEP record route object (RRO) are defined. the PCEP record route object (RRO) are defined.
IANA has made the following sub-objects allocation from the RSVP IANA has made the following sub-objects allocation from the RSVP
Parameters registry: Parameters registry:
Object Sub-Object Sub-Object Type Object Sub-Object Sub-Object Type
--------------------- -------------------------- -------------------------- --------------------- -------------------------- --------------------------
EXPLICIT_ROUTE BIER-ERO (PCEP-specific) TBD EXPLICIT_ROUTE BIER-ERO (PCEP-specific) TBD
ROUTE_RECORD BIER-RRO (PCEP-specific) TBD ROUTE_RECORD BIER-RRO (PCEP-specific) TBD
6.2. PCEP-Error Objects and Types 6.2. PCEP-Error Objects and Types
As described in Section 4.2.3.1.1, a number of new PCEP-ERROR Object As described in Section 4.2.3.1.1, a number of new PCEP-ERROR Object
Error Values have been defined. Error Values have been defined.
Error-Type Meaning Reference Error-Type Meaning Reference
---------- ----------------------------------- --------------------------------- ---------- ----------------------------------- ---------------------------------
10 Reception of an invalid object. RFC5540 10 Reception of an invalid object. RFC5540
Error-value = TBD: BitStringLength is absent This document Error-value = TBD: BitStringLength is absent This document
Error-value = TBD: BitString is absent This document Error-value = TBD: BitString is absent This document
Error-value = TBD: Invalid BitStringLength This document Error-value = TBD: Invalid BitStringLength This document
6.3. PCEP TLV Type Indicators 6.3. PCEP TLV Type Indicators
IANA is requested to allocate a new code point in the PCEP TLV Type IANA is requested to allocate a new code point in the PCEP TLV Type
Indicators registry, as follows: Indicators registry, as follows:
Value Meaning Reference Value Meaning Reference
-------------------- ---------------------------- ----------------------------------- -------------------- ---------------------------- -----------------------------------
TBD BIER-PCE-CAPABILITY TLV This document TBD BIER-PCE-CAPABILITY TLV This document
6.4. New Path Setup Type 6.4. New Path Setup Type
IANA is requested to allocate a new code point in the PCEP IANA is requested to allocate a new code point in the PCEP
PATH_SETUP_TYPE TLV PST field registry, as follows: PATH_SETUP_TYPE TLV PST field registry, as follows:
Value Description Reference Value Description Reference
---------------- ------------------------------------ ---------------------------- ---------------- ------------------------------------ ----------------------------
2 Path is setup using BIER Traffic This document 2 Path is setup using BIER Traffic This document
Engineering technique Engineering technique
7. References 7. References
7.1. Normative references 7.1. Normative references
[I-D.ietf-bier-architecture] [I-D.ietf-bier-architecture]
Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and
S. Aldrin, "Multicast using Bit Index Explicit S. Aldrin, "Multicast using Bit Index Explicit
Replication", draft-ietf-bier-architecture-05 (work in Replication", draft-ietf-bier-architecture-07 (work in
progress), October 2016. progress), June 2017.
[I-D.ietf-pce-lsp-setup-type] [I-D.ietf-pce-lsp-setup-type]
Sivabalan, S., Medved, J., Minei, I., Crabbe, E., Varga, Sivabalan, S., Tantsura, J., Minei, I., Varga, R., and J.
R., Tantsura, J., and J. Hardwick, "Conveying path setup Hardwick, "Conveying path setup type in PCEP messages",
type in PCEP messages", draft-ietf-pce-lsp-setup-type-03 draft-ietf-pce-lsp-setup-type-04 (work in progress), April
(work in progress), June 2015. 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
Element (PCE) Communication Protocol (PCEP)", RFC 5440, Element (PCE) Communication Protocol (PCEP)", RFC 5440,
DOI 10.17487/RFC5440, March 2009, DOI 10.17487/RFC5440, March 2009,
<http://www.rfc-editor.org/info/rfc5440>. <http://www.rfc-editor.org/info/rfc5440>.
7.2. Informative references 7.2. Informative references
[I-D.eckert-bier-te-arch] [I-D.eckert-bier-te-arch]
Eckert, T., Cauchie, G., Braun, W., and M. Menth, "Traffic Eckert, T., Cauchie, G., Braun, W., and M. Menth, "Traffic
Engineering for Bit Index Explicit Replication BIER-TE", Engineering for Bit Index Explicit Replication BIER-TE",
draft-eckert-bier-te-arch-04 (work in progress), July draft-eckert-bier-te-arch-05 (work in progress), June
2016. 2017.
Authors' Addresses Authors' Addresses
Ran Chen Ran Chen
ZTE Corporation ZTE Corporation
No.50 Software Avenue,Yuhuatai District No.50 Software Avenue,Yuhuatai District
Nanjing, Jiangsu Province 210012 Nanjing, Jiangsu Province 210012
China China
Phone: +86 025 88014636 Phone: +86 025 88014636
 End of changes. 13 change blocks. 
23 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/