Extensions to PCEP for Distributing Label Cross Domains
draft-chen-pce-label-x-domains-09
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-07-07
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
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 Futurewei
Intended status: Standards Track A. Liu
Expires: January 8, 2020 Ciena
M. Toy
Verizon
V. Liu
July 7, 2019
Extensions to PCEP for Distributing Label Cross Domains
draft-chen-pce-label-x-domains-09
Abstract
This document specifies extensions to PCEP for distributing labels
crossing domains for an inter-domain Point-to-Point (P2P) or Point-
to-Multipoint (P2MP) Traffic Engineering (TE) Label Switched Path
(LSP).
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 https://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 January 8, 2020.
Copyright Notice
Copyright (c) 2019 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
Chen, et al. Expires January 8, 2020 [Page 1]
Internet-Draft Label Cross Domains July 2019
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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Conventions Used in This Document . . . . . . . . . . . . . . 3
4. Label Distribution . . . . . . . . . . . . . . . . . . . . . 3
4.1. An Exmaple . . . . . . . . . . . . . . . . . . . . . . . 4
5. Extensions to PCEP . . . . . . . . . . . . . . . . . . . . . 5
5.1. RP Object Extension . . . . . . . . . . . . . . . . . . . 5
5.2. Label Object . . . . . . . . . . . . . . . . . . . . . . 6
5.3. LSP Tunnel Object . . . . . . . . . . . . . . . . . . . . 7
5.4. Request Message Extension . . . . . . . . . . . . . . . . 8
5.5. Reply Message Extension . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7.1. Request Parameter Bit Flags . . . . . . . . . . . . . . . 9
8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
After a path crossing multiple domains is computed, an inter-domain
Traffic Engineering (TE) Label Switched Path (LSP) tunnel may be set
up along the path by a number of tunnel central controllers (TCCs).
Each of the domains through which the path goes may be controlled by
a tunnel central controller (TCC), which sets up the segment of the
TE LSP tunnel in the domain. When the TCC sets up the segment of the
TE LSP tunnel in its domain that is not a domain containing the tail
end of the tunnel, it needs a label and an interface from a
downstream domain, which is next to it along the path.
This document specifies extensions to PCEP for distributing a label
and an interface from a domain to its upstream domain along the path
for the TE LSP tunnel crossing multiple domains.
2. Terminology
ABR: Area Border Router. Routers used to connect two IGP areas
(areas in OSPF or levels in IS-IS).
Chen, et al. Expires January 8, 2020 [Page 2]
Internet-Draft Label Cross Domains July 2019
Show full document text