Preferred Path Routing (PPR) in OSPF
draft-chunduri-lsr-ospf-preferred-path-routing-03
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-05-16
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized
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)
|
LSR Working Group U. Chunduri
Internet-Draft Y. Qu
Intended status: Standards Track Huawei USA
Expires: November 17, 2019 R. White
Juniper Networks
J. Tantsura
Apstra Inc.
L. Contreras
Telefonica
May 16, 2019
Preferred Path Routing (PPR) in OSPF
draft-chunduri-lsr-ospf-preferred-path-routing-03
Abstract
This document specifies a Preferred Path Routing (PPR), a routing
protocol mechanism to simplify the path description of data plane
traffic in Segment Routing (SR) deployments with OSPFv2 and OSPFv3
protocols. PPR aims to mitigate the MTU and data plane processing
issues that may result from SR packet overheads; and also supports
further extensions along the paths. Preferred path routing is
achieved through the addition of path descriptions to the OSPF
advertised prefixes, and mapping those to a PPR data-plane
identifier.
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 RFC2119 [RFC2119],
RFC8174 [RFC8174] when, and only when they appear in all capitals, as
shown here".
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
Chunduri, et al. Expires November 17, 2019 [Page 1]
Internet-Draft Preferred Path Routing (PPR) in OSPF May 2019
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 November 17, 2019.
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
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
1.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 3
2. OSPFv2 PPR TLV . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. PPR-Flags . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2. PPR-Prefix Sub-TLV . . . . . . . . . . . . . . . . . . . 6
2.3. PPR-ID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 7
2.4. PPR-PDE Sub-TLV . . . . . . . . . . . . . . . . . . . . . 9
2.5. PPR-Attributes Sub-TLV . . . . . . . . . . . . . . . . . 11
3. OSPFv3 PPR TLV . . . . . . . . . . . . . . . . . . . . . . . 12
3.1. OSPFv3 PPR-Prefix Sub-TLV . . . . . . . . . . . . . . . . 13
3.2. OSPFv3 PPR-ID Sub-TLVs . . . . . . . . . . . . . . . . . 14
3.3. OSPFv3 PPR-PDE Sub-TLV . . . . . . . . . . . . . . . . . 16
3.4. OSPFv3 PPR-Attributes Sub-TLV . . . . . . . . . . . . . . 19
4. Other Considerations . . . . . . . . . . . . . . . . . . . . 19
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 20
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.1. Normative References . . . . . . . . . . . . . . . . . . 20
8.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
Chunduri, et al. Expires November 17, 2019 [Page 2]
Show full document text