Open Shortest Path First IGP P. Psenak, Ed.
Internet-Draft S. Previdi, Ed.
Intended status: Standards Track C. Filsfils
Expires: August 17, 2014 Cisco Systems, Inc.
H. Gredler
Juniper Networks, Inc.
R. Shakir
British Telecom
W. Henderickx
Alcatel-Lucent
February 13, 2014
OSPFv3 Extensions for Segment Routing
draft-psenak-ospf-segment-routing-ospfv3-extension-01
Abstract
Segment Routing (SR) allows for a flexible definition of end-to-end
paths within IGP topologies by encoding paths as sequences of
topological sub-paths, called "segments". These segments are
advertised by the link-state routing protocols (IS-IS and OSPF).
This draft describes the necessary OSPFv3 extensions that need to be
introduced for Segment Routing.
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 August 17, 2014.
Psenak, et al. Expires August 17, 2014 [Page 1]Internet-Draft OSPFv3 Extensions for Segment Routing February 2014Copyright Notice
Copyright (c) 2014 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
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. Segment Routing Identifiers . . . . . . . . . . . . . . . . . 3
2.1. SID/Label sub-TLV . . . . . . . . . . . . . . . . . . . . 3
3. Segment Routing Capabilities . . . . . . . . . . . . . . . . . 4
3.1. SR-Algorithm TLV . . . . . . . . . . . . . . . . . . . . . 4
3.2. SID/Label Range TLV . . . . . . . . . . . . . . . . . . . 5
4. Prefix SID Identifier . . . . . . . . . . . . . . . . . . . . 6
4.1. Prefix SID Sub-TLV . . . . . . . . . . . . . . . . . . . . 6
4.2. SID/Label Binding sub-TLV . . . . . . . . . . . . . . . . 8
4.2.1. ERO Metric sub-TLV . . . . . . . . . . . . . . . . . . 10
4.2.2. ERO sub-TLVs . . . . . . . . . . . . . . . . . . . . . 10
5. Adjacency Segment Identifier (Adj-SID) . . . . . . . . . . . . 16
5.1. Adj-SID sub-TLV . . . . . . . . . . . . . . . . . . . . . 17
5.2. LAN Adj-SID Sub-TLV . . . . . . . . . . . . . . . . . . . 18
6. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 19
6.1. Intra-area Segment routing in OSPFv3 . . . . . . . . . . . 19
6.2. Inter-area Segment routing in OSPFv3 . . . . . . . . . . . 20
6.3. SID for External Prefixes . . . . . . . . . . . . . . . . 21
6.4. Advertisement of Adj-SID . . . . . . . . . . . . . . . . . 21
6.4.1. Advertisement of Adj-SID on Point-to-Point Links . . . 21
6.4.2. Adjacency SID on Broadcast or NBMA Interfaces . . . . 21
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
datatracker.ietf.org