< draft-ietf-teas-yang-rsvp-te-06.txt   draft-ietf-teas-yang-rsvp-te-07.txt >
TEAS Working Group V. Beeram TEAS Working Group V. Beeram
Internet-Draft T. Saad Internet-Draft T. Saad
Intended status: Standards Track Juniper Networks Intended status: Standards Track Juniper Networks
Expires: October 11, 2019 R. Gandhi Expires: January 8, 2020 R. Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
X. Liu X. Liu
Volta Networks Volta Networks
I. Bryskin I. Bryskin
Huawei Technologies Huawei Technologies
H. Shah H. Shah
Ciena Ciena
April 09, 2019 July 07, 2019
A YANG Data Model for RSVP-TE Protocol A YANG Data Model for RSVP-TE Protocol
draft-ietf-teas-yang-rsvp-te-06 draft-ietf-teas-yang-rsvp-te-07
Abstract Abstract
This document defines a YANG data model for the configuration and This document defines a YANG data model for the configuration and
management of RSVP (Resource Reservation Protocol) to establish management of RSVP (Resource Reservation Protocol) to establish
Traffic-Engineered (TE) Label-Switched Paths (LSPs) for MPLS (Multi- Traffic-Engineered (TE) Label-Switched Paths (LSPs) for MPLS (Multi-
Protocol Label Switching) and other technologies. Protocol Label Switching) and other technologies.
The model defines a generic RSVP-TE module for signaling LSPs that is The model defines a generic RSVP-TE module for signaling LSPs that
technology agnostic. The generic RSVP-TE module is to be augmented are technology agnostic. The generic RSVP-TE module is to be
by technology specific RSVP-TE modules that define technology augmented by technology specific RSVP-TE modules that define
specific data. This document also defines the augmentation for RSVP- technology specific data. This document also defines the
TE MPLS LSPs model. augmentation for RSVP-TE MPLS LSPs model.
This model covers data for the configuration, operational state, This model covers data for the configuration, operational state,
remote procedural calls, and event notifications. remote procedural calls, and event notifications.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 11, 2019. This Internet-Draft will expire on January 8, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 34 skipping to change at page 2, line 34
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3 1.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3
2. Model Overview . . . . . . . . . . . . . . . . . . . . . . . 4 2. Model Overview . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Module Relationship . . . . . . . . . . . . . . . . . . . 4 2.1. Module Relationship . . . . . . . . . . . . . . . . . . . 4
2.2. Model Tree Diagrams . . . . . . . . . . . . . . . . . . . 5 2.2. Model Tree Diagrams . . . . . . . . . . . . . . . . . . . 5
2.2.1. RSVP-TE Model Tree Diagram . . . . . . . . . . . . . 5 2.2.1. RSVP-TE Model Tree Diagram . . . . . . . . . . . . . 5
2.2.2. RSVP-TE MPLS Model Tree Diagram . . . . . . . . . . . 14 2.2.2. RSVP-TE MPLS Model Tree Diagram . . . . . . . . . . . 14
2.3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . 16 2.3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . 16
2.3.1. RSVP-TE YANG Module . . . . . . . . . . . . . . . . . 16 2.3.1. RSVP-TE YANG Module . . . . . . . . . . . . . . . . . 16
2.3.2. RSVP-TE MPLS YANG Module . . . . . . . . . . . . . . 29 2.3.2. RSVP-TE MPLS YANG Module . . . . . . . . . . . . . . 29
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42
4. Security Considerations . . . . . . . . . . . . . . . . . . . 41 4. Security Considerations . . . . . . . . . . . . . . . . . . . 42
5. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 42 5. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 43
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 42 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 43
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.1. Normative References . . . . . . . . . . . . . . . . . . 43 7.1. Normative References . . . . . . . . . . . . . . . . . . 44
7.2. Informative References . . . . . . . . . . . . . . . . . 45 7.2. Informative References . . . . . . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46
1. Introduction 1. Introduction
YANG [RFC7950] is a data modeling language that was introduced to YANG [RFC7950] is a data modeling language that was introduced to
define the contents of a conceptual data store that allows networked define the contents of a conceptual data store that allows networked
devices to be managed using NETCONF [RFC6241]. YANG has proved devices to be managed using NETCONF [RFC6241]. YANG has proved
relevant beyond its initial confines, as bindings to other interfaces relevant beyond its initial confines, as bindings to other interfaces
(e.g. RESTCONF [RFC8040]) and encoding other than XML (e.g. JSON) (e.g. RESTCONF [RFC8040]) and encoding other than XML (e.g. JSON)
are being defined. Furthermore, YANG data models can be used as the are being defined. Furthermore, YANG data models can be used as the
basis of implementation for other interfaces, such as CLI and basis of implementation for other interfaces, such as CLI and
skipping to change at page 16, line 26 skipping to change at page 16, line 26
o ietf-te-types defined in [I-D.ietf-teas-yang-te-types] o ietf-te-types defined in [I-D.ietf-teas-yang-te-types]
o ietf-te and ietf-te-dev defined in [I-D.ietf-teas-yang-te] o ietf-te and ietf-te-dev defined in [I-D.ietf-teas-yang-te]
This module references the following documents: This module references the following documents:
[I-D.ietf-teas-yang-rsvp], [RFC8349], [I-D.ietf-teas-yang-te], [I-D.ietf-teas-yang-rsvp], [RFC8349], [I-D.ietf-teas-yang-te],
[I-D.ietf-teas-yang-te-types], [RFC2210], [RFC4920], [RFC5420], [I-D.ietf-teas-yang-te-types], [RFC2210], [RFC4920], [RFC5420],
[RFC7570], [RFC4859]. [RFC7570], [RFC4859].
<CODE BEGINS> file "ietf-rsvp-te@2019-04-09.yang" <CODE BEGINS> file "ietf-rsvp-te@2019-07-06.yang"
module ietf-rsvp-te { module ietf-rsvp-te {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te"; namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te";
prefix "rsvp-te"; prefix "rsvp-te";
import ietf-rsvp { import ietf-rsvp {
prefix rsvp; prefix rsvp;
reference "draft-ietf-teas-yang-rsvp: A YANG Data Model for reference "draft-ietf-teas-yang-rsvp: A YANG Data Model for
skipping to change at page 17, line 21 skipping to change at page 17, line 21
Engineering Tunnels and Interfaces"; Engineering Tunnels and Interfaces";
} }
/* Import TE generic types */ /* Import TE generic types */
import ietf-te-types { import ietf-te-types {
prefix te-types; prefix te-types;
reference "draft-ietf-teas-yang-te-types: A YANG Data Model for reference "draft-ietf-teas-yang-te-types: A YANG Data Model for
Common Traffic Engineering Types"; Common Traffic Engineering Types";
} }
import ietf-inet-types {
prefix inet;
reference "RFC6991: Common YANG Data Types";
}
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <http://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
WG Chair: Lou Berger WG Chair: Lou Berger
<mailto:lberger@labn.net> <mailto:lberger@labn.net>
skipping to change at page 18, line 28 skipping to change at page 18, line 34
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision "2019-04-09" { revision "2019-07-06" {
description "A YANG Data Model for RSVP-TE"; description "A YANG Data Model for RSVP-TE";
reference reference
"RFCXXXX: A YANG Data Model for RSVP-TE Protocol"; "RFCXXXX: A YANG Data Model for RSVP-TE Protocol";
} }
identity rsvp-message-type { identity rsvp-message-type {
description "RSVP message types"; description "RSVP message types";
} }
identity rsvp-message-path { identity rsvp-message-path {
skipping to change at page 24, line 16 skipping to change at page 24, line 22
"rsvp:interface" { "rsvp:interface" {
description description
"RSVP-TE generic data augmentation pertaining to specific "RSVP-TE generic data augmentation pertaining to specific
interface"; interface";
uses rsvp-te-interface-attributes; uses rsvp-te-interface-attributes;
} }
/* add augmentation for sessions and neighbors */ /* add augmentation for sessions and neighbors */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/"
+ "rsvp:sessions/rsvp:session/rsvp:state/rsvp:psbs/rsvp:psb" { + "rsvp:sessions" {
description
"RSVP-TE generic data augmentation pertaining to session";
list session-te {
key "tunnel-endpoint tunnel-id extended-tunnel-id";
config false;
description
"List of RSVP sessions";
leaf tunnel-endpoint {
type inet:ip-address;
description "XX";
}
leaf tunnel-id {
type uint16;
description "XX";
}
leaf extended-tunnel-id {
type inet:ip-address;
description "XX";
}
uses rsvp:session-attributes-state;
}
}
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/"
+ "rsvp:sessions/session-te/psbs/psb" {
description description
"RSVP-TE generic data augmentation pertaining to session"; "RSVP-TE generic data augmentation pertaining to session";
/* To be added */ /* To be added */
leaf tspec-average-rate { leaf tspec-average-rate {
type rt-types:bandwidth-ieee-float32; type rt-types:bandwidth-ieee-float32;
units "Bytes per second"; units "Bytes per second";
description "Tspec Token Bucket Average Rate"; description "Tspec Token Bucket Average Rate";
reference "RFC2210: RSVP with INTSERV"; reference "RFC2210: RSVP with INTSERV";
} }
leaf tspec-size { leaf tspec-size {
skipping to change at page 24, line 49 skipping to change at page 25, line 35
type uint32; type uint32;
description "Tspec Minimum Policed Unit"; description "Tspec Minimum Policed Unit";
reference "RFC2210"; reference "RFC2210";
} }
leaf max-packet-size { leaf max-packet-size {
type uint32; type uint32;
description "Tspec Maximum Packet Size"; description "Tspec Maximum Packet Size";
reference "RFC2210"; reference "RFC2210";
} }
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/"
+ "rsvp:sessions/rsvp:session/rsvp:state/rsvp:rsbs/rsvp:rsb" { + "rsvp:sessions/session-te/rsbs/rsb" {
description description
"RSVP-TE generic data augmentation pertaining to session"; "RSVP-TE generic data augmentation pertaining to session";
leaf fspec-average-rate { leaf fspec-average-rate {
type rt-types:bandwidth-ieee-float32; type rt-types:bandwidth-ieee-float32;
units "Bytes per second"; units "Bytes per second";
description "Fspec Token Bucket Average Rate"; description "Fspec Token Bucket Average Rate";
reference "RFC2210"; reference "RFC2210";
} }
leaf fspec-size { leaf fspec-size {
type rt-types:bandwidth-ieee-float32; type rt-types:bandwidth-ieee-float32;
skipping to change at page 26, line 42 skipping to change at page 27, line 30
reference "RFC2205"; reference "RFC2205";
} }
} }
grouping rsvp-te-lsp-properties { grouping rsvp-te-lsp-properties {
description "RSVP-TE LSP properties grouping"; description "RSVP-TE LSP properties grouping";
leaf associated-rsvp-session { leaf associated-rsvp-session {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/"
+ "rsvp:sessions/rsvp:session/rsvp:local-index"; + "rsvp:sessions/session-te/tunnel-id";
} }
config false; config false;
description description
"If the signalling protocol specified for this path is "If the signalling protocol specified for this path is
RSVP-TE, this leaf provides a reference to the associated RSVP-TE, this leaf provides a reference to the associated
session within the RSVP-TE protocol sessions list, such session within the RSVP-TE protocol sessions list, such
that details of the signaling can be retrieved."; that details of the signaling can be retrieved.";
} }
uses lsp-properties-config; uses lsp-properties-config;
uses lsp-explicit-route-information-state; uses lsp-explicit-route-information-state;
uses lsp-record-route-information-state; uses lsp-record-route-information-state;
} }
augment "/te:te/te:lsps-state/te:lsp" { augment "/te:te/te:lsps-state/te:lsp" {
when "/te:te/te:lsps-state/te:lsp" + when "/te:te/te:lsps-state/te:lsp" +
"/te:path-setup-protocol = 'te-types:path-setup-rsvp'" { "/te:path-setup-protocol = 'te-types:path-setup-rsvp'" {
description description
"When the signaling protocol is RSVP-TE "; "When the signaling protocol is RSVP-TE ";
skipping to change at page 29, line 16 skipping to change at page 30, line 4
Figure 4: RSVP TE generic YANG module Figure 4: RSVP TE generic YANG module
2.3.2. RSVP-TE MPLS YANG Module 2.3.2. RSVP-TE MPLS YANG Module
The RSVP-TE MPLS YANG module "ietf-rsvp-te-mpls" imports the The RSVP-TE MPLS YANG module "ietf-rsvp-te-mpls" imports the
following module(s): following module(s):
o ietf-rsvp defined in [I-D.ietf-teas-yang-rsvp] o ietf-rsvp defined in [I-D.ietf-teas-yang-rsvp]
o ietf-routing-types defined in [RFC8294] o ietf-routing-types defined in [RFC8294]
o ietf-te-mpls-types defined in [I-D.ietf-teas-yang-te-types] o ietf-te-mpls-types defined in [I-D.ietf-teas-yang-te-types]
o ietf-te and ietf-te-dev defined in [I-D.ietf-teas-yang-te] o ietf-te and ietf-te-dev defined in [I-D.ietf-teas-yang-te]
This module references the following documents: This module references the following documents:
[I-D.ietf-teas-yang-rsvp], [RFC8349], [I-D.ietf-teas-yang-te-types], [I-D.ietf-teas-yang-rsvp], [RFC8349], [I-D.ietf-teas-yang-te-types],
[I-D.ietf-teas-yang-te], [RFC3209]. [I-D.ietf-teas-yang-te], [RFC3209].
<CODE BEGINS> file "ietf-rsvp-te-mpls@2019-04-09.yang" <CODE BEGINS> file "ietf-rsvp-te-mpls@2019-07-06.yang"
module ietf-rsvp-te-mpls { module ietf-rsvp-te-mpls {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te-mpls"; namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te-mpls";
prefix "rsvp-te-mpls"; prefix "rsvp-te-mpls";
import ietf-rsvp { import ietf-rsvp {
prefix "rsvp"; prefix "rsvp";
reference "draft-ietf-teas-yang-rsvp: A YANG Data Model for reference "draft-ietf-teas-yang-rsvp: A YANG Data Model for
skipping to change at page 31, line 28 skipping to change at page 32, line 14
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision "2019-04-09" { revision "2019-07-06" {
description "Update to MPLS RSVP-TE YANG initial revision."; description "Update to MPLS RSVP-TE YANG initial revision.";
reference reference
"RFCXXXX: A YANG Data Model for RSVP-TE Protocol"; "RFCXXXX: A YANG Data Model for RSVP-TE Protocol";
} }
/* RSVP-TE MPLS LSPs groupings */ /* RSVP-TE MPLS LSPs groupings */
grouping lsp-attributes-flags-mpls-config { grouping lsp-attributes-flags-mpls-config {
description description
"Configuration parameters relating to RSVP-TE MPLS LSP "Configuration parameters relating to RSVP-TE MPLS LSP
attribute flags"; attribute flags";
skipping to change at page 39, line 39 skipping to change at page 40, line 27
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
"rsvp:interface" { "rsvp:interface" {
description description
"Augmentations for RSVP-TE MPLS per interface properties"; "Augmentations for RSVP-TE MPLS per interface properties";
/* To be added */ /* To be added */
} }
/* add augmentation for sessions neighbors */ /* add augmentation for sessions neighbors */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/"
+ "rsvp:sessions/rsvp:session/rsvp:state" { + "rsvp:sessions" {
description description
"Augmentations for RSVP-TE MPLS sessions"; "Augmentation for RSVP-TE MPLS sessions";
/* To be added */ /* To be added */
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:neighbors" { + "rt:control-plane-protocol/rsvp:rsvp/rsvp:neighbors" {
description description
"Augmentations for RSVP-TE MPLS neighbors properties"; "Augmentations for RSVP-TE MPLS neighbors properties";
/* To be added */ /* To be added */
} }
/** /**
* Augmentation to TE generic module * Augmentation to TE generic module
*/ */
augment "/te:te/te:tunnels/te:tunnel" { augment "/te:te/te:tunnels/te:tunnel" {
description description
"Augmentations for RSVP-TE MPLS TE tunnel properties"; "Augmentations for RSVP-TE MPLS TE tunnel properties";
uses tunnel-properties-mpls-config; uses tunnel-properties-mpls-config;
} }
augment "/te:te/te:lsps-state/te:lsp" { augment "/te:te/te:lsps-state/te:lsp" {
skipping to change at page 43, line 20 skipping to change at page 44, line 4
Brocade Brocade
Email: raqib@Brocade.com Email: raqib@Brocade.com
Bin Wen Bin Wen
Comcast Comcast
Email: Bin_Wen@cable.comcast.com Email: Bin_Wen@cable.comcast.com
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-teas-yang-rsvp] [I-D.ietf-teas-yang-rsvp]
Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I., Beeram, V., Saad, T., Gandhi, R., Liu, X., and I. Bryskin,
and H. Shah, "A YANG Data Model for Resource Reservation "A YANG Data Model for Resource Reservation Protocol
Protocol (RSVP)", draft-ietf-teas-yang-rsvp-10 (work in (RSVP)", draft-ietf-teas-yang-rsvp-11 (work in progress),
progress), February 2019. July 2019.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"A YANG Data Model for Traffic Engineering Tunnels and "A YANG Data Model for Traffic Engineering Tunnels and
Interfaces", draft-ietf-teas-yang-te-21 (work in Interfaces", draft-ietf-teas-yang-te-21 (work in
progress), April 2019. progress), April 2019.
[I-D.ietf-teas-yang-te-types] [I-D.ietf-teas-yang-te-types]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"Traffic Engineering Common YANG Types", draft-ietf-teas- "Traffic Engineering Common YANG Types", draft-ietf-teas-
yang-te-types-08 (work in progress), April 2019. yang-te-types-10 (work in progress), July 2019.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. [RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, DOI 10.17487/RFC2205, Functional Specification", RFC 2205, DOI 10.17487/RFC2205,
September 1997, <https://www.rfc-editor.org/info/rfc2205>. September 1997, <https://www.rfc-editor.org/info/rfc2205>.
 End of changes. 25 change blocks. 
32 lines changed or deleted 66 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/