One document matched: draft-ietf-spring-sr-yang-01.xml
<?xml version="1.0"?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc docName="draft-ietf-spring-sr-yang-01" ipr="trust200902" category="std" obsoletes="" updates="" submissionType="IETF" xml:lang="en">
<front>
<title abbrev="sr-yang-cfg">YANG Data Model for Segment Routing</title>
<author fullname="Stephane Litkowski" initials="S" surname="Litkowski">
<organization>Orange Business Service</organization>
<address>
<email>stephane.litkowski@orange.com</email>
</address>
</author>
<author fullname="Yingzhen Qu" initials="Y" surname="Qu">
<organization>Cisco Systems</organization>
<address>
<email>yiqu@cisco.com</email>
</address>
</author>
<author fullname="Pushpasis Sarkar" initials="P" surname="Sarkar">
<organization>Juniper Networks</organization>
<address>
<email>psarkar@juniper.net</email>
</address>
</author>
<author fullname="Jeff Tantsura" initials="J" surname="Tantsura">
<organization>Ericsson</organization>
<address>
<email>jeff.tantsura@ericsson.com</email>
</address>
</author>
<date day="17" month="October" year="2015"/>
<area/>
<workgroup>SPRING Working Group</workgroup>
<abstract>
<t>
This document defines a YANG data model (<xref target="RFC6020" pageno="false" format="default"/>) for segment routing (<xref target="I-D.ietf-spring-segment-routing" pageno="false" format="default"/>) configuration and operation.
This YANG model is intended to be used on network elements to configure or operate segment routing.
This document defines also generic containers that SHOULD be reused by IGP protocol modules to support segment routing.
</t>
</abstract>
<note title="Requirements Language">
<t>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 <xref target="RFC2119" pageno="false" format="default"/>.</t>
</note>
</front>
<middle>
<section anchor="introduction" title="Introduction" toc="default">
<t>
This document defines a YANG data model for segment routing configuration and operation.
This document does not define the IGP extensions to support segment routing but defines generic
groupings that SHOULD be reused by IGP extension modules. The reason of this design choice is to not require
implementations to support all IGP extensions. For example, an implementation may support IS-IS extension but not OSPF.
</t>
<section anchor="tree-info" title="Tree diagram" toc="default">
<t>A simplified graphical representation of the data model is
presented in <xref target="design" pageno="false" format="default"/>.</t>
<t>The meaning of the symbols in these diagrams is as follows:
<list style="symbols">
<t>Brackets "[" and "]" enclose list keys.</t>
<t>Curly braces "{" and "}" contain names of optional features that
make the corresponding node conditional.</t>
<t>Abbreviations before data node names: "rw" means configuration
(read-write), and "ro" state data (read-only).</t>
<t>Symbols after data node names: "?" means an optional node and "*"
denotes a "list" or "leaf-list".</t>
<t>Parentheses enclose choice and case nodes, and case nodes are
also marked with a colon (":").</t>
<t>Ellipsis ("...") stands for contents of subtrees that are not
shown.</t>
</list></t>
</section>
</section>
<section anchor="design" title="Design of the Data Model" toc="default">
<t>As the module definition is just starting, it is expected that there will be changes
as the module matures. </t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
module: ietf-segment-routing
augment /rt:routing/rt:routing-instance:
+--rw segment-routing
+--rw transport-type? identityref
+--rw bindings
| +--rw mapping-server {mapping-server}?
| | +--rw policy* [name]
| | +--rw name string
| | +--rw ipv4
| | | +--rw mapping-entry* [prefix]
| | | +--rw prefix inet:ipv4-prefix
| | | +--rw value-type? enumeration
| | | +--rw start-sid uint32
| | | +--rw range? uint32
| | +--rw ipv6
| | +--rw mapping-entry* [prefix]
| | +--rw prefix inet:ipv6-prefix
| | +--rw value-type? enumeration
| | +--rw start-sid uint32
| | +--rw range? uint32
| +--rw connected-prefix-sid-map
| +--rw ipv4
| | +--rw ipv4-prefix-sid* [prefix]
| | +--rw prefix inet:ipv4-prefix
| | +--rw value-type? enumeration
| | +--rw start-sid uint32
| | +--rw range? uint32
| | +--rw last-hop-behavior? enumeration {sid-last-hop-behavior}?
| +--rw ipv6
| +--rw ipv6-prefix-sid* [prefix]
| +--rw prefix inet:ipv6-prefix
| +--rw value-type? enumeration
| +--rw start-sid uint32
| +--rw range? uint32
| +--rw last-hop-behavior? enumeration {sid-last-hop-behavior}?
+--rw global-srgb
+--rw srgb* [lower-bound upper-bound]
+--rw lower-bound uint32
+--rw upper-bound uint32
augment /rt:routing-state/rt:routing-instance:
+--ro segment-routing
+--ro node-capabilities
| +--ro transport-planes* [transport-plane]
| | +--ro transport-plane identityref
| +--ro segment-stack-push-limit? uint8
| +--ro readable-label-stack-depth? uint8
+--ro label-blocks*
| +--ro lower-bound? uint32
| +--ro upper-bound? uint32
| +--ro size? uint32
| +--ro free? uint32
| +--ro used? uint32
+--ro global-sid-list
+--ro sid* [target sid source source-protocol binding-type]
+--ro target string
+--ro sid uint32
+--ro algorithm? uint8
+--ro source inet:ip-address
+--ro used? boolean
+--ro source-protocol leafref
+--ro binding-type enumeration
notifications:
+---n segment-routing-global-sid-collision
| +--ro received-target? string
| +--ro original-target? string
| +--ro index? uint32
| +--ro routing-protocol? leafref
+---n segment-routing-index-out-of-range
+--ro received-target? string
+--ro received-index? uint32
+--ro routing-protocol? leafref
</artwork>
</figure>
</section>
<section anchor="how" title="Configuration" toc="default">
<t>
This module augments the "/rt:routing/rt:routing-instance:" with a segment-routing container.
This container defines all the configuration parameters related to segment-routing for this particular routing-instance.
</t>
<t>
The segment-routing configuration is split in global routing-instance configuration and interface configuration.
</t>
<t>The global configuration includes :
<list style="symbols">
<t>segment-routing transport type : The underlying transport type
for segment routing. The version of the model limits the transport
type to an MPLS dataplane. The transport-type is only defined once
for a particular routing-instance and is agnostic to the
control plane used. Only a single transport-type is supported
in this version of the model. </t>
<t>bindings : Defines prefix to SID mappings. The operator can control advertisement of Prefix-SID independently
for IPv4 and IPv6. Two types of mappings are available :
<list style="symbols">
<t>Mapping-server : maps non local prefixes to a segment ID. Configuration of bindings does not
automatically allow advertisement of those
bindings. Advertisement must be controlled by each
routing-protocol instance (see <xref target="cp" pageno="false" format="default"/>). Multiple mapping policies
may be defined.</t>
<t>Connected prefixes : maps connected prefixes to a segment ID. Advertisement of the mapping
will be done by IGP when enabled for segment routing (see <xref target="cp" pageno="false" format="default"/>). The SID value can be expressed as an index (default), or an absolute
value. The "last-hop-behavior" configuration dictates the PHP behavior:
"explicit-null", "php", or "non-php".</t>
</list></t>
<t>SRGB (Segment Routing Global Block): Defines a list of label
blocks represented by a pair of lower-bound/upper-bound labels.
The SRGB is also agnostic to the control plane used. So all
routing-protocol instance will have to advertise the same SRGB.</t>
</list>
</t>
</section>
<section anchor="cp" title="IGP Control plane configuration" toc="default">
<t>
Support of segment-routing extensions for a particular IGP control plane is done by augmenting routing-protocol configuration with segment-routing extensions.
This augmentation SHOULD be part of separate YANG modules in order to not create any dependency for implementations to support all protocol extensions.
</t>
<t>
This module defines groupings that SHOULD be used by IGP segment routing modules.
</t>
<t>The "controlplane-cfg" grouping defines the generic global configuration for the IGP.</t>
<t>The "enabled" leaf enables segment-routing extensions for the
routing-protocol instance.</t>
<t>The "bindings" container controls the routing-protocol instance's
advertisement of local bindings and the processing of received
bindings.</t>
<section anchor="igp-interface" title="IGP interface configuration" toc="default">
<t>The interface configuration is part of the "igp-interface-cfg" grouping and includes Adjacency SID properties.</t>
<section anchor="adj-cfg" title="Adjacency SID properties" toc="default">
<section anchor="adj-cfg-bundling" title="Bundling" toc="default">
<t>
This section is a first proposal on how to use S-bit in Adj-SID to create bundles.
Authors would like to trigger discussion based on this first proposal.
</t>
<t>
In case of parallel IP links between routers, an additional Adjacency
SID may be advertised representing more than one adjacency (i.e.,
a bundle of adjacencies). The "advertise-adj-group-sid" configuration
controls whether or not an additional adjacency SID is advertised.
</t>
<t>The "advertise-adj-group-sid" would be a list of "group-id".
The "group-id" will permit to identify interfaces that must
be bundled together.</t>
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height="">
+-------+ +------+
| | ------- L1 ---- | |
| R1 | ------- L2 ---- | R2 |
| | ------- L3 ---- | |
| | ------- L4 ---- | |
+-------+ +------+
</artwork>
</figure>
<t>
In the figure above, R1 and R2 are interconnected by four links. A routing protocol adjacency is established on each link.
Operator would like to create segment-routing Adj-SID that represent some bundles of links. We can imagine two different bundles : L1/L2 and L2/L3.
To achieve this behavior, the service provider will configure a "group-id" X for both interfaces L1 and L2 and a "group-id" Y for both interfaces L3 and L3.
This will result in R1 advertising an additional Adj-SID for each adjacency, for example a Adj-SID with S flag set and value of 400 will be added to L1 and L2.
A Adj-SID with S flag set and value of 500 will be added to L3 and L4. As L1/L2 and L3/L4 does not share the same "group-id", a different SID value will be allocated.
</t>
</section>
<section anchor="adj-cfg-protection" title="Protection" toc="default">
<t>
The "advertise-protection" defines how protection for an interface
is advertised. It does not control the activation or deactivation of
protection. If the "single" option is used, a single Adj-SID will be
advertised for the interface. If the interface is protected, the
B-Flag for the Adj-SID advertisement will be set. If the "dual"
option is used and if the interface is protected, two Adj-SIDs will
be advertised for the interface adjacencies. One Adj-SID will always
have the B-Flag set and the other will have the B-Flag clear. This
option is intended to be used in the case of traffic engineering
where a path must use either protected segments or non-protected
segments.
</t>
</section>
</section>
</section>
</section>
<section anchor="states" title="States" toc="default">
<t>
The operational states contains information reflecting the usage of
allocated SRGB labels.
</t>
<t>It also includes a list of all global SIDs, their associated
bindings, and other information such as the source protocol and
algorithm.</t>
</section>
<section anchor="notif" title="Notifications" toc="default">
<t>
The model proposes two notifications for segment-routing.
<list style="symbols">
<t>segment-routing-global-sid-collision: Raised when a control plane
advertised index is already associated with another target (in
this version, the only defined targets are IPv4 and IPv6 prefixes). </t>
<t>segment-routing-index-out-of-range: Raised when a control plane
advertised index fall outside the range of SRGBs configured for
the network device.</t>
</list>
</t>
</section>
<section anchor="yang" title="YANG Module" toc="default">
<figure title="" suppress-title="false" align="left" alt="" width="" height="">
<artwork><![CDATA[
<CODE BEGINS> file "ietf-segment-routing@2015-10-17.yang"
module ietf-segment-routing {
namespace "urn:ietf:params:xml:ns:"
+ "yang:ietf-segment-routing";
prefix sr;
import ietf-inet-types {
prefix "inet";
}
import ietf-routing {
prefix "rt";
}
organization
"IETF SPRING Working Group";
contact
"WG List: <mailto:spring@ietf.org>
Editor: Stephane Litkowski
<mailto:stephane.litkowski@orange.com>
Author: Acee Lindem
<mailto:acee@cisco.com>
Author: Yingzhen Qu
<mailto:yiqu@cisco.com>
Author: Pushpasis Sarkar
<mailto:psarkar@juniper.net>
Author: Ing-Wher Chen
<mailto:ing-wher.chen@ericsson.com>
Author: Jeff Tantsura
<jeff.tantsura@ericsson.com>
";
description
"The YANG module defines a generic configuration model for
Segment routing common across all of the vendor
implementations.";
revision 2015-10-17 {
description "
* Add per-protocol SRGB config feature
* Move SRBG config to a grouping
";
reference
"RFC XXXX: YANG Data Model for Segment Routing.";
}
revision 2015-06-22 {
description "
* Prefix SID config moved to
connected-prefix-sid-map in global SR cfg
rather than IGP.
";
reference "draft-litkowski-spring-sr-yang-01";
}
revision 2015-04-23 {
description "
* Node flag deprecated from prefixSID
* SR interface cfg moved to protocol
* Adding multiple binding policies for SRMS
";
reference "";
}
revision 2015-02-27 {
description "Initial";
reference "draft-litkowski-spring-sr-yang-00";
}
/* Identities */
identity segment-routing-transport {
description
"Base identity for segment routing transport.";
}
identity segment-routing-transport-mpls {
base segment-routing-transport;
description
"This identity represents MPLS transport for segment
routing.";
}
/* Features */
feature mapping-server {
description
"Support of SRMS.";
}
feature sid-last-hop-behavior {
description
"Configurable last hop behavior.";
}
feature protocol-srgb {
description
"Support per-protocol srgb configuration.";
}
/* Groupings */
grouping srgb-cfg {
list srgb {
key "lower-bound upper-bound";
ordered-by user;
leaf lower-bound {
type uint32;
description
"Lower value in the block.";
}
leaf upper-bound {
type uint32;
description
"Upper value in the block.";
}
description
"List of global blocks to be
advertised.";
}
description
"Grouping for SRGB configuration.";
}
grouping controlplane-cfg {
container segment-routing {
leaf enabled {
type boolean;
default false;
description
"Enables segment-routing
protocol extensions.";
}
container bindings {
container advertise {
leaf-list policies {
type string;
description
"List of policies to be advertised.";
}
description
"Authorize the advertise
of local mappings in binding TLV.";
}
leaf receive {
type boolean;
default true;
description
"Authorize the reception and usage
of binding TLV.";
}
description
"Control of binding advertisement
and reception.";
}
description
"segment routing global config.";
}
description
"Defines protocol configuration.";
}
grouping sid-value-type {
leaf value-type {
type enumeration {
enum index {
description
"The value will be
interpreted as an index.";
}
enum absolute {
description
"The value will become
interpreted as an absolute
value.";
}
}
default index;
description
"This leaf defines how value
must be interpreted.";
}
description
"Defines how the SID value is expressed.";
}
grouping ipv4-sid-cfg {
leaf prefix {
type inet:ipv4-prefix;
description
"connected prefix sid.";
}
uses sid-value-type;
leaf start-sid {
type uint32;
mandatory true;
description
"Value associated with
prefix. The value must
be interpreted in the
context of value-type.";
}
leaf range {
type uint32;
description
"Describes how many SIDs could be
allocated.";
}
description
"This grouping defines cfg of prefix SID.";
}
grouping ipv6-sid-cfg {
leaf prefix {
type inet:ipv6-prefix;
description
"connected prefix sid.";
}
uses sid-value-type;
leaf start-sid {
type uint32;
mandatory true;
description
"Value associated with
prefix. The value must
be interpreted in the
context of value-type.";
}
leaf range {
type uint32;
description
"Describes how many SIDs could be
allocated.";
}
description
"This grouping defines cfg of prefix SID.";
}
grouping last-hop-behavior {
leaf last-hop-behavior {
if-feature sid-last-hop-behavior;
type enumeration {
enum explicit-null {
description
"Use explicit-null for the SID.";
}
enum no-php {
description
"Do no use PHP for the SID.";
}
enum php {
description
"Use PHP for the SID.";
}
}
description
"Configure last hop behavior.";
}
description
"Defines last hop behavior";
}
grouping igp-interface-cfg {
container segment-routing {
container adjacency-sid {
list advertise-adj-group-sid {
key group-id;
leaf group-id {
type uint32;
description
"The value is an internal value to identify
a group-ID. Interfaces with the same
group-ID will be bundled together.
";
}
description
"Control advertisement of S flag.
Enable to advertise a common Adj-SID
for parallel links.";
}
leaf advertise-protection {
type enumeration {
enum "single" {
description
"A single Adj-SID is associated
with the adjacency and reflects
the protection configuration.";
}
enum "dual" {
description
"Two Adj-SIDs will be associated
with the adjacency if interface
is protected. In this case
one will be enforced with
backup flag set, the other
will be enforced to backup flag unset.
In case, protection is not configured,
a single Adj-SID will be advertised
with backup flag unset.";
}
}
description
"If set, the Adj-SID refers to an
adjacency being protected.";
}
description
"Defines the adjacency SID properties.";
}
description
"container for SR interface cfg.";
}
description
"Grouping for IGP interface cfg.";
}
/* Cfg */
augment "/rt:routing/rt:routing-instance" {
description
"This augments routing-instance
configuration with segment-routing.";
container segment-routing {
leaf transport-type {
type identityref {
base segment-routing-transport;
}
default "segment-routing-transport-mpls";
description "Dataplane to be used.";
}
container bindings {
container mapping-server {
if-feature mapping-server;
list policy {
key name;
leaf name {
type string;
description
"Name of the mapping policy.";
}
container ipv4 {
list mapping-entry {
key prefix;
uses ipv4-sid-cfg;
description
"Mapping entries.";
}
description
"IPv4 mapping entries.";
}
container ipv6 {
list mapping-entry {
key prefix;
uses ipv6-sid-cfg;
description
"Mapping entries.";
}
description
"IPv6 mapping entries.";
}
description
"Definition of mapping policy.";
}
description
"Configuration of mapping-server
local entries.";
}
container connected-prefix-sid-map {
container ipv4 {
list ipv4-prefix-sid {
key prefix;
uses ipv4-sid-cfg;
uses last-hop-behavior;
description
"List of prefix SID
mapped to IPv4 local prefixes.";
}
description
"Parameters associated with IPv4 prefix SID";
}
container ipv6 {
list ipv6-prefix-sid {
key prefix;
uses ipv6-sid-cfg;
uses last-hop-behavior;
description
"List of prefix SID
mapped to IPv6 local prefixes.";
}
description
"Parameters associated with IPv6 prefix SID";
}
description
"Prefix SID configuration.";
}
description
"List of bindings.";
}
container global-srgb {
uses srgb-cfg;
description
"Global SRGB configuration.";
}
description
"segment routing global config.";
}
}
/* Operational states */
augment "/rt:routing-state/rt:routing-instance" {
description
"This augments the operational states
with segment-routing.";
container segment-routing {
container node-capabilities {
list transport-planes {
key transport-plane;
leaf transport-plane {
type identityref {
base segment-routing-transport;
}
description
"Transport plane supported";
}
description
"List of supported transport planes.";
}
leaf segment-stack-push-limit {
type uint8;
description
"Describes the number of segments
that can be pushed by the node.";
}
leaf readable-label-stack-depth {
type uint8;
description
"Number of MPLS labels that
can be read in the stack.";
}
description
"Shows the SR capability of the node.";
}
list label-blocks {
leaf lower-bound {
type uint32;
description
"Lower bound of the label block.";
}
leaf upper-bound {
type uint32;
description
"Upper bound of the label block.";
}
leaf size {
type uint32;
description
"Number of indexes in the block.";
}
leaf free {
type uint32;
description
"Number of indexes free in the block.";
}
leaf used {
type uint32;
description
"Number of indexes used in the block.";
}
description
"List of labels blocks currently
in use.";
}
container global-sid-list {
list sid {
key "target sid source source-protocol binding-type";
ordered-by system;
leaf target {
type string;
description
"Defines the target of the binding.
It can be a prefix or something else.";
}
leaf sid {
type uint32;
description
"Index associated with the prefix.";
}
leaf algorithm {
type uint8;
description
"Algorithm to be used for the prefix
SID.";
}
leaf source {
type inet:ip-address;
description
"IP address of the router than own
the binding.";
}
leaf used {
type boolean;
description
"Defines if the binding is used
in forwarding plane.";
}
leaf source-protocol {
type leafref {
path "/rt:routing-state/rt:routing-instance/" +
"rt:routing-protocols/rt:routing-protocol/rt:name";
}
description
"Rtg protocol that owns the binding";
}
leaf binding-type {
type enumeration {
enum prefix-sid {
description
"Binding is learned from
a prefix SID.";
}
enum binding-tlv {
description
"Binding is learned from
a binding TLV.";
}
}
description
"Type of binding.";
}
description
"Binding.";
}
description
"List of prefix and SID associations.";
}
description
"Segment routing operational states.";
}
}
/* Notifications */
notification segment-routing-global-sid-collision {
leaf received-target {
type string;
description
"Target received in the controlplane that
caused SID collision.";
}
leaf original-target {
type string;
description
"Target already available in database that have the same SID
as the received target.";
}
leaf index {
type uint32;
description
"Value of the index used by two different prefixes.";
}
leaf routing-protocol {
type leafref {
path "/rt:routing-state/rt:routing-instance/" +
"rt:routing-protocols/rt:routing-protocol/rt:name";
}
description
"Routing protocol reference that received the event.";
}
description
"This notification is sent when a new mapping is learned
, containing mapping
where the SID is already used.
The notification generation must be throttled with at least
a 5 second gap. ";
}
notification segment-routing-index-out-of-range {
leaf received-target {
type string;
description
"Target received in the controlplane
that caused SID collision.";
}
leaf received-index {
type uint32;
description
"Value of the index received.";
}
leaf routing-protocol {
type leafref {
path "/rt:routing-state/rt:routing-instance/" +
"rt:routing-protocols/rt:routing-protocol/rt:name";
}
description
"Routing protocol reference that received the event.";
}
description
"This notification is sent when a binding
is received, containing a segment index
which is out of the local configured ranges.
The notification generation must be throttled with at least
a 5 second gap. ";
}
}
<CODE ENDS>
]]></artwork>
</figure>
</section>
<section anchor="Security" title="Security Considerations" toc="default">
<t>TBD.</t>
</section>
<section anchor="Acknowledgements" title="Acknowledgements" toc="default">
<t>Authors would like to thank Derek Yeung, Acee Lindem, Greg Hankins, Hannes Gredler, Uma Chunduri, Jeffrey Zhang, Shradda Hedge for their contributions.</t>
</section>
<section anchor="IANA" title="IANA Considerations" toc="default">
<t>TBD.</t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="RFC2119">
<front>
<title abbrev="RFC Key Words">Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials="S." surname="Bradner" fullname="Scott Bradner">
<organization>Harvard University</organization>
<address>
<postal>
<street>1350 Mass. Ave.</street>
<street>Cambridge</street>
<street>MA 02138</street></postal>
<phone>- +1 617 495 3864</phone>
<email>sob@harvard.edu</email></address></author>
<date year="1997" month="March"/>
<area>General</area>
<keyword>keyword</keyword>
<abstract>
<t>
In many standards track documents several words are used to signify
the requirements in the specification. These words are often
capitalized. This document defines these words as they should be
interpreted in IETF documents. Authors who follow these guidelines
should incorporate this phrase near the beginning of their document:
<list>
<t>
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.
</t></list></t>
<t>
Note that the force of these words is modified by the requirement
level of the document in which they are used.
</t></abstract></front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/>
<format type="TXT" octets="4723" target="http://www.rfc-editor.org/rfc/rfc2119.txt"/>
<format type="HTML" octets="17970" target="http://xml.resource.org/public/rfc/html/rfc2119.html"/>
<format type="XML" octets="5777" target="http://xml.resource.org/public/rfc/xml/rfc2119.xml"/>
</reference>
<reference anchor="RFC6020">
<front>
<title>YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)</title>
<author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
<organization/></author>
<date year="2010" month="October"/>
<abstract>
<t>YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name="RFC" value="6020"/>
<format type="TXT" octets="324178" target="http://www.rfc-editor.org/rfc/rfc6020.txt"/>
</reference>
<reference anchor="I-D.ietf-spring-segment-routing">
<front>
<title>Segment Routing Architecture</title>
<author initials="C" surname="Filsfils" fullname="Clarence Filsfils">
<organization/>
</author>
<author initials="S" surname="Previdi" fullname="Stefano Previdi">
<organization/>
</author>
<author initials="B" surname="Decraene" fullname="Bruno Decraene">
<organization/>
</author>
<author initials="S" surname="Litkowski" fullname="Stephane Litkowski">
<organization/>
</author>
<author initials="R" surname="Shakir" fullname="Rob Shakir">
<organization/>
</author>
<date month="May" day="28" year="2015"/>
<abstract><t>Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called segments. A segment can represent any instruction, topological or service-based. A segment can have a local semantic to an SR node or global within an SR domain. SR allows to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node to the SR domain. Segment Routing can be directly applied to the MPLS architecture with no change on the forwarding plane. A segment is encoded as an MPLS label. An ordered list of segments is encoded as a stack of labels. The segment to process is on the top of the stack. Upon completion of a segment, the related label is popped from the stack. Segment Routing can be applied to the IPv6 architecture, with a new type of routing extension header. A segment is encoded as an IPv6 address. An ordered list of segments is encoded as an ordered list of IPv6 addresses in the routing extension header. The segment to process is indicated by a pointer in the routing extension header. Upon completion of a segment, the pointer is incremented.</t></abstract>
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-spring-segment-routing-03"/>
<format type="TXT" target="http://www.ietf.org/internet-drafts/draft-ietf-spring-segment-routing-03.txt"/>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 14:22:36 |