PCEP Link State Abstraction
draft-chen-pce-h-connect-access-03
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-09-11
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
PCE Working Group H. Chen
Internet-Draft Huawei Technologies
Intended status: Standards Track M. Toy
Expires: March 15, 2018 Verizon
X. Liu
Jabil
L. Liu
Fujitsu
Z. Li
China Mobile
September 11, 2017
PCEP Link State Abstraction
draft-chen-pce-h-connect-access-03
Abstract
This document presents extensions to the Path Computation Element
Communication Protocol (PCEP) for a child PCE to abstract its domain
information to its parent for supporting a hierarchical PCE system.
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 15, 2018.
Copyright Notice
Copyright (c) 2017 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
Chen, et al. Expires March 15, 2018 [Page 1]
Internet-Draft H-Connect-Access September 2017
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Conventions Used in This Document . . . . . . . . . . . . . . 3
4. Connections and Accesses . . . . . . . . . . . . . . . . . . . 4
4.1. Information on Inter-domain Link . . . . . . . . . . . . . 4
4.2. Information on ABR . . . . . . . . . . . . . . . . . . . . 5
4.3. Information on Access Point . . . . . . . . . . . . . . . 5
5. Extensions to PCEP . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Messages for Abstract Information . . . . . . . . . . . . 6
5.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . . 7
5.2.1. Child Procedures . . . . . . . . . . . . . . . . . . . 7
5.2.2. Parent Procedures . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 11
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . . 11
Appendix A. Message Encoding . . . . . . . . . . . . . . . . . . 12
A.1. Extension to Existing Message . . . . . . . . . . . . . . 12
A.1.1. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 12
A.1.2. Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . 13
A.2. New Message . . . . . . . . . . . . . . . . . . . . . . . 14
A.2.1. CONNECTION and ACCESS Object . . . . . . . . . . . . . 15
Chen, et al. Expires March 15, 2018 [Page 2]
Internet-Draft H-Connect-Access September 2017
1. Introduction
A hierarchical PCE architecture is described in RFC 6805, in which a
parent PCE maintains an abstract domain topology, which contains its
Show full document text