draft-ietf-bfd-yang-16.txt   draft-ietf-bfd-yang-17.txt 
Network Working Group R. Rahman, Ed. Network Working Group R. Rahman, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track L. Zheng, Ed. Intended status: Standards Track L. Zheng, Ed.
Expires: December 23, 2018 Huawei Technologies Expires: February 2, 2019 Huawei Technologies
M. Jethanandani, Ed. M. Jethanandani, Ed.
Xoriant Corporation Xoriant Corporation
S. Pallagatti S. Pallagatti
Rtbrick
G. Mirsky G. Mirsky
ZTE Corporation ZTE Corporation
June 21, 2018 August 1, 2018
YANG Data Model for Bidirectional Forwarding Detection (BFD) YANG Data Model for Bidirectional Forwarding Detection (BFD)
draft-ietf-bfd-yang-16 draft-ietf-bfd-yang-17
Abstract Abstract
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage Bidirectional Forwarding Detection (BFD). and manage Bidirectional Forwarding Detection (BFD).
The YANG modules in this document conform to the Network Management The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA). Datastore Architecture (NMDA).
Status of This Memo Status of This Memo
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 December 23, 2018. This Internet-Draft will expire on February 2, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 42 skipping to change at page 2, line 42
2.9. BFD over MPLS LSPs hierarchy . . . . . . . . . . . . . . 18 2.9. BFD over MPLS LSPs hierarchy . . . . . . . . . . . . . . 18
2.10. BFD over MPLS-TE hierarchy . . . . . . . . . . . . . . . 20 2.10. BFD over MPLS-TE hierarchy . . . . . . . . . . . . . . . 20
2.11. Interaction with other YANG modules . . . . . . . . . . . 22 2.11. Interaction with other YANG modules . . . . . . . . . . . 22
2.11.1. Module ietf-interfaces . . . . . . . . . . . . . . . 22 2.11.1. Module ietf-interfaces . . . . . . . . . . . . . . . 22
2.11.2. Module ietf-ip . . . . . . . . . . . . . . . . . . . 22 2.11.2. Module ietf-ip . . . . . . . . . . . . . . . . . . . 22
2.11.3. Module ietf-mpls . . . . . . . . . . . . . . . . . . 23 2.11.3. Module ietf-mpls . . . . . . . . . . . . . . . . . . 23
2.11.4. Module ietf-te . . . . . . . . . . . . . . . . . . . 23 2.11.4. Module ietf-te . . . . . . . . . . . . . . . . . . . 23
2.12. IANA BFD YANG Module . . . . . . . . . . . . . . . . . . 23 2.12. IANA BFD YANG Module . . . . . . . . . . . . . . . . . . 23
2.13. BFD types YANG Module . . . . . . . . . . . . . . . . . . 26 2.13. BFD types YANG Module . . . . . . . . . . . . . . . . . . 26
2.14. BFD top-level YANG Module . . . . . . . . . . . . . . . . 39 2.14. BFD top-level YANG Module . . . . . . . . . . . . . . . . 39
2.15. BFD IP single-hop YANG Module . . . . . . . . . . . . . . 40 2.15. BFD IP single-hop YANG Module . . . . . . . . . . . . . . 41
2.16. BFD IP multihop YANG Module . . . . . . . . . . . . . . . 44 2.16. BFD IP multihop YANG Module . . . . . . . . . . . . . . . 44
2.17. BFD over LAG YANG Module . . . . . . . . . . . . . . . . 47 2.17. BFD over LAG YANG Module . . . . . . . . . . . . . . . . 47
2.18. BFD over MPLS YANG Module . . . . . . . . . . . . . . . . 51 2.18. BFD over MPLS YANG Module . . . . . . . . . . . . . . . . 51
2.19. BFD over MPLS-TE YANG Module . . . . . . . . . . . . . . 55 2.19. BFD over MPLS-TE YANG Module . . . . . . . . . . . . . . 55
3. Data Model examples . . . . . . . . . . . . . . . . . . . . . 58 3. Data Model examples . . . . . . . . . . . . . . . . . . . . . 58
3.1. IP single-hop . . . . . . . . . . . . . . . . . . . . . . 58 3.1. IP single-hop . . . . . . . . . . . . . . . . . . . . . . 58
3.2. IP multihop . . . . . . . . . . . . . . . . . . . . . . . 59 3.2. IP multihop . . . . . . . . . . . . . . . . . . . . . . . 59
3.3. LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.3. LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.4. MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . 60 3.4. MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4. Security Considerations . . . . . . . . . . . . . . . . . . . 61 4. Security Considerations . . . . . . . . . . . . . . . . . . . 62
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66
5.1. IANA-Maintained iana-bfd-types module . . . . . . . . . . 68 5.1. IANA-Maintained iana-bfd-types module . . . . . . . . . . 70
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 68 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 70
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 68 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 70
7.1. Normative References . . . . . . . . . . . . . . . . . . 68 7.1. Normative References . . . . . . . . . . . . . . . . . . 70
7.2. Informative References . . . . . . . . . . . . . . . . . 71 7.2. Informative References . . . . . . . . . . . . . . . . . 73
Appendix A. Echo function configuration example . . . . . . . . 71 Appendix A. Echo function configuration example . . . . . . . . 73
A.1. Example YANG module for BFD echo function configuration . 71 A.1. Example YANG module for BFD echo function configuration . 74
Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 74 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 76
B.1. Changes between versions -15 and -16 . . . . . . . . . . 74 B.1. Changes between versions -16 and -17 . . . . . . . . . . 76
B.2. Changes between versions -14 and -15 . . . . . . . . . . 74 B.2. Changes between versions -15 and -16 . . . . . . . . . . 76
B.3. Changes between versions -13 and -14 . . . . . . . . . . 74 B.3. Changes between versions -14 and -15 . . . . . . . . . . 76
B.4. Changes between versions -12 and -13 . . . . . . . . . . 74 B.4. Changes between versions -13 and -14 . . . . . . . . . . 76
B.5. Changes between versions -11 and -12 . . . . . . . . . . 74 B.5. Changes between versions -12 and -13 . . . . . . . . . . 76
B.6. Changes between versions -10 and -11 . . . . . . . . . . 74 B.6. Changes between versions -11 and -12 . . . . . . . . . . 76
B.7. Changes between versions -09 and -10 . . . . . . . . . . 74 B.7. Changes between versions -10 and -11 . . . . . . . . . . 76
B.8. Changes between versions -08 and -09 . . . . . . . . . . 74 B.8. Changes between versions -09 and -10 . . . . . . . . . . 77
B.9. Changes between versions -07 and -08 . . . . . . . . . . 75 B.9. Changes between versions -08 and -09 . . . . . . . . . . 77
B.10. Changes between versions -06 and -07 . . . . . . . . . . 75 B.10. Changes between versions -07 and -08 . . . . . . . . . . 77
B.11. Changes between versions -05 and -06 . . . . . . . . . . 75 B.11. Changes between versions -06 and -07 . . . . . . . . . . 77
B.12. Changes between versions -04 and -05 . . . . . . . . . . 75 B.12. Changes between versions -05 and -06 . . . . . . . . . . 77
B.13. Changes between versions -03 and -04 . . . . . . . . . . 75 B.13. Changes between versions -04 and -05 . . . . . . . . . . 78
B.14. Changes between versions -02 and -03 . . . . . . . . . . 76 B.14. Changes between versions -03 and -04 . . . . . . . . . . 78
B.15. Changes between versions -01 and -02 . . . . . . . . . . 76 B.15. Changes between versions -02 and -03 . . . . . . . . . . 78
B.16. Changes between versions -00 and -01 . . . . . . . . . . 76 B.16. Changes between versions -01 and -02 . . . . . . . . . . 78
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 76 B.17. Changes between versions -00 and -01 . . . . . . . . . . 78
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 78
1. Introduction 1. Introduction
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage Bidirectional Forwarding Detection (BFD) [RFC5880]. BFD and manage Bidirectional Forwarding Detection (BFD) [RFC5880]. BFD
is a network protocol which is used for liveness detection of is a network protocol which is used for liveness detection of
arbitrary paths between systems. Some examples of different types of arbitrary paths between systems. Some examples of different types of
paths over which we have BFD: paths over which we have BFD:
1) Two systems directly connected via IP. This is known as BFD over 1) Two systems directly connected via IP. This is known as BFD over
skipping to change at page 4, line 17 skipping to change at page 4, line 17
BFD typically does not operate on its own. Various control BFD typically does not operate on its own. Various control
protocols, also known as BFD clients, use the services provided by protocols, also known as BFD clients, use the services provided by
BFD for their own operation as described in Generic Application of BFD for their own operation as described in Generic Application of
BFD [RFC5882]. The obvious candidates which use BFD are those which BFD [RFC5882]. The obvious candidates which use BFD are those which
do not have "hellos" to detect failures, e.g. static routes, and do not have "hellos" to detect failures, e.g. static routes, and
routing protocols whose "hellos" do not support sub-second failure routing protocols whose "hellos" do not support sub-second failure
detection, e.g. OSPF and IS-IS. detection, e.g. OSPF and IS-IS.
The YANG modules in this document conform to the Network Management The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA) Network Management Datastore Datastore Architecture (NMDA) [RFC8342]. This means that the data
Architecture [RFC8342]. This means that the data models do not have models do not have separate top-level or sibling containers for
separate top-level or sibling containers for configuration and configuration and operational state data.
operational state data.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14 [RFC2119] document are to be interpreted as described in BCP 14 [RFC2119]
[RFC8174] when, and only when, they appear in all capitals, as shown [RFC8174] when, and only when, they appear in all capitals, as shown
here. here.
1.2. Tree Diagrams 1.2. Tree Diagrams
This document uses the graphical representation of data models This document uses the graphical representation of data models
defined in [RFC8340]. defined in [RFC8340].
2. Design of the Data Model 2. Design of the Data Model
Since BFD is used for liveliness detection of various forwarding Since BFD is used for liveliness detection of various forwarding
paths, there is no uniform key to identify a BFD session. So the BFD paths, there is no uniform key to identify a BFD session, and so the
data model is split in multiple YANG modules where each module BFD data model is split in multiple YANG modules where each module
corresponds to one type of forwarding path. For example, BFD for IP corresponds to one type of forwarding path. For example, BFD for IP
single-hop is in one YANG module and BFD for MPLS-TE is in another single-hop is in one YANG module and BFD for MPLS-TE is in another
YANG module. The main difference between these modules is how a BFD YANG module. The main difference between these modules is how a BFD
session is uniquely identified, i.e the key for the list containing session is uniquely identified, i.e the key for the list containing
the BFD sessions for that forwarding path. To avoid duplication of the BFD sessions for that forwarding path. To avoid duplication of
BFD definitions, we have common types and groupings which are used by BFD definitions, we have common types and groupings which are used by
all the modules. all the modules.
A new control-plane protocol "bfdv1" is defined and a "bfd" container A new control-plane protocol "bfdv1" is defined and a "bfd" container
is created under control-plane-protocol as specified in "A YANG Data is created under control-plane-protocol as specified in "A YANG Data
skipping to change at page 8, line 29 skipping to change at page 8, line 27
tx-ttl tx-ttl
TTL of outgoing BFD control packets. TTL of outgoing BFD control packets.
rx-ttl rx-ttl
Minimum TTL of incoming BFD control packets. Minimum TTL of incoming BFD control packets.
2.1.4. MPLS Traffic Engineering Tunnels 2.1.4. MPLS Traffic Engineering Tunnels
For MPLS-TE tunnels, BFD is configured under the MPLS-TE tunnel since For MPLS-TE tunnels, BFD is configured under the MPLS-TE tunnel since
the desired failure detection parameters is a property of the MPLS-TE the desired failure detection parameters are a property of the MPLS-
tunnel. This is achieved by augmenting the MPLS-TE data model in TE tunnel. This is achieved by augmenting the MPLS-TE data model in
YANG Data Model for TE Topologies [I-D.ietf-teas-yang-te]. For BFD YANG Data Model for TE Topologies [I-D.ietf-teas-yang-te]. For BFD
parameters which are specific to the TE application, e.g. whether to parameters which are specific to the TE application, e.g. whether to
tear down the tunnel in the event of a BFD session failure, these tear down the tunnel in the event of a BFD session failure, these
parameters will be defined in the YANG model of the MPLS-TE parameters will be defined in the YANG model of the MPLS-TE
application. application.
On top of the usual BFD parameters, we have the following per MPLS-TE On top of the usual BFD parameters, we have the following per MPLS-TE
tunnel: tunnel:
encap encap
skipping to change at page 23, line 26 skipping to change at page 23, line 26
The following configuration is defined in the "ietf-te" YANG module The following configuration is defined in the "ietf-te" YANG module
YANG Data Model for TE Topology [I-D.ietf-teas-yang-te]: YANG Data Model for TE Topology [I-D.ietf-teas-yang-te]:
/ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:config/ietf- /ietf-te:te/ietf-te:tunnels/ietf-te:tunnel/ietf-te:config/ietf-
te:admin-status te:admin-status
If this configuration is not set to "state-up", no BFD MPLS If this configuration is not set to "state-up", no BFD MPLS
packets can be transmitted or received on that tunnel. packets can be transmitted or received on that tunnel.
2.12. IANA BFD YANG Module 2.12. IANA BFD YANG Module
<CODE BEGINS> file "iana-bfd-types@2018-06-21.yang" <CODE BEGINS> file "iana-bfd-types@2018-08-01.yang"
module iana-bfd-types { module iana-bfd-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:iana-bfd-types"; namespace "urn:ietf:params:xml:ns:yang:iana-bfd-types";
prefix "iana-bfd-types"; prefix "iana-bfd-types";
organization "IANA"; organization "IANA";
contact contact
" Internet Assigned Numbers Authority " Internet Assigned Numbers Authority
Postal: ICANN Postal: ICANN
4676 Admiralty Way, Suite 330 12025 Waterfront Drive, Suite 300
Marina del Rey, CA 90292 Los Angeles, CA 90094-2536
United States of America
Tel: +1 310 823 9358 Tel: +1 310 823 9358
<mailto:iana@iana.org>"; <mailto:iana@iana.org>";
description description
"This module defines YANG data types for IANA-registered "This module defines YANG data types for IANA-registered
BFD parameters. BFD parameters.
This YANG module is maintained by IANA and reflects the This YANG module is maintained by IANA and reflects the
'BFD Diagnostic Codes' and 'BFD Authentication Types' registries. 'BFD Diagnostic Codes' and 'BFD Authentication Types' registries.
skipping to change at page 24, line 24 skipping to change at page 24, line 26
(http://trustee.ietf.org/license-info). (http://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 // RFC Ed.: replace XXXX with actual RFC number and remove
// this note // this note
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-21 { revision 2018-08-01 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: IANA BFD YANG Data Types."; reference "RFC XXXX: IANA BFD YANG Data Types.";
} }
/* /*
* Type Definitions * Type Definitions
*/ */
typedef diagnostic { typedef diagnostic {
type enumeration { type enumeration {
enum none { enum none {
skipping to change at page 26, line 25 skipping to change at page 26, line 26
} }
} }
<CODE ENDS> <CODE ENDS>
2.13. BFD types YANG Module 2.13. BFD types YANG Module
This YANG module imports typedefs from [RFC6991], [RFC8177] and the This YANG module imports typedefs from [RFC6991], [RFC8177] and the
"control-plane-protocol" identity from [RFC8349]. "control-plane-protocol" identity from [RFC8349].
<CODE BEGINS> file "ietf-bfd-types@2018-06-21.yang" <CODE BEGINS> file "ietf-bfd-types@2018-08-01.yang"
module ietf-bfd-types { module ietf-bfd-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-types";
prefix "bfd-types"; prefix "bfd-types";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
skipping to change at page 27, line 46 skipping to change at page 27, line 49
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-21 { revision 2018-08-01 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: YANG Data Model for BFD"; reference "RFC XXXX: YANG Data Model for BFD";
} }
/* /*
* Feature definitions * Feature definitions
*/ */
feature single-minimum-interval { feature single-minimum-interval {
description description
"This feature indicates that the server supports configuration "This feature indicates that the server supports configuration
of one minimum interval value which is used for both transmit and of one minimum interval value which is used for both transmit and
receive minimum intervals."; receive minimum intervals.";
} }
skipping to change at page 37, line 34 skipping to change at page 37, line 36
description "Grouping for session statistics summary."; description "Grouping for session statistics summary.";
container summary { container summary {
config false; config false;
description "BFD session statistics summary."; description "BFD session statistics summary.";
leaf number-of-sessions { leaf number-of-sessions {
type yang:gauge32; type yang:gauge32;
description "Number of BFD sessions."; description "Number of BFD sessions.";
} }
leaf number-of-sessions-up { leaf number-of-sessions-up {
type yang:gauge32; type yang:gauge32;
description "Number of BFD sessions currently in up state."; description
"Number of BFD sessions currently in up state (as defined
in RFC 5880).";
} }
leaf number-of-sessions-down { leaf number-of-sessions-down {
type yang:gauge32; type yang:gauge32;
description "Number of BFD sessions currently in down state."; description
"Number of BFD sessions currently in down or init state
but not admin-down (as defined in RFC 5880).";
} }
leaf number-of-sessions-admin-down { leaf number-of-sessions-admin-down {
type yang:gauge32; type yang:gauge32;
description description
"Number of BFD sessions currently in admin-down state."; "Number of BFD sessions currently in admin-down state (as
defined in RFC 5880).";
} }
} }
} }
grouping notification-parms { grouping notification-parms {
description description
"This group describes common parameters that will be sent " + "This group describes common parameters that will be sent " +
"as part of BFD notification."; "as part of BFD notification.";
leaf local-discr { leaf local-discr {
type discriminator; type discriminator;
skipping to change at page 38, line 45 skipping to change at page 39, line 4
leaf source-addr { leaf source-addr {
type inet:ip-address; type inet:ip-address;
description "BFD local address."; description "BFD local address.";
} }
leaf session-index { leaf session-index {
type uint32; type uint32;
description "An index used to uniquely identify BFD sessions."; description "An index used to uniquely identify BFD sessions.";
} }
leaf path-type { leaf path-type {
type identityref { type identityref {
base path-type; base path-type;
} }
description "BFD path type."; description "BFD path type.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
2.14. BFD top-level YANG Module 2.14. BFD top-level YANG Module
This YANG module imports and augments "/routing/control-plane- This YANG module imports and augments "/routing/control-plane-
protocols/control-plane-protocol" from [RFC8349]. protocols/control-plane-protocol" from [RFC8349].
<CODE BEGINS> file "ietf-bfd@2018-06-21.yang" <CODE BEGINS> file "ietf-bfd@2018-08-01.yang"
module ietf-bfd { module ietf-bfd {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd";
prefix "bfd"; prefix "bfd";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
skipping to change at page 40, line 20 skipping to change at page 40, line 26
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-21 { revision 2018-08-01 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: YANG Data Model for BFD"; reference "RFC XXXX: YANG Data Model for BFD";
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol" { + "rt:control-plane-protocol" {
when "derived-from-or-self(rt:type, 'bfd-types:bfdv1')" { when "derived-from-or-self(rt:type, 'bfd-types:bfdv1')" {
description description
"This augmentation is only valid for a control-plane protocol "This augmentation is only valid for a control-plane protocol
instance of BFD (type 'bfdv1')."; instance of BFD (type 'bfdv1').";
skipping to change at page 40, line 50 skipping to change at page 41, line 11
} }
<CODE ENDS> <CODE ENDS>
2.15. BFD IP single-hop YANG Module 2.15. BFD IP single-hop YANG Module
This YANG module imports "interface-ref" from [RFC8343], typedefs This YANG module imports "interface-ref" from [RFC8343], typedefs
from [RFC6991] and augments "/routing/control-plane-protocols/ from [RFC6991] and augments "/routing/control-plane-protocols/
control-plane-protocol" from [RFC8349]. control-plane-protocol" from [RFC8349].
<CODE BEGINS> file "ietf-bfd-ip-sh@2018-06-21.yang" <CODE BEGINS> file "ietf-bfd-ip-sh@2018-08-01.yang"
module ietf-bfd-ip-sh { module ietf-bfd-ip-sh {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh";
prefix "bfd-ip-sh"; prefix "bfd-ip-sh";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
// remove this note // remove this note
import ietf-bfd-types { import ietf-bfd-types {
skipping to change at page 42, line 22 skipping to change at page 42, line 31
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-21 { revision 2018-08-01 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG data model for BFD IP single-hop"; reference "RFC XXXX: A YANG data model for BFD IP single-hop";
} }
/* /*
* Augments * Augments
*/ */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/bfd:bfd" { + "rt:control-plane-protocol/bfd:bfd" {
description "BFD augmentation for IP single-hop"; description "BFD augmentation for IP single-hop";
skipping to change at page 43, line 36 skipping to change at page 43, line 44
} }
} }
} }
/* /*
* Notifications * Notifications
*/ */
notification singlehop-notification { notification singlehop-notification {
description description
"Notification for BFD single-hop session state change. An " + "Notification for BFD single-hop session state change. An " +
"implementation may rate-limit notifications, e.g. when a" + "implementation may rate-limit notifications, e.g. when a " +
"session is continuously changing state."; "session is continuously changing state.";
uses bfd-types:notification-parms; uses bfd-types:notification-parms;
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
description "Interface to which this BFD session belongs to."; description "Interface to which this BFD session belongs to.";
} }
leaf echo-enabled { leaf echo-enabled {
type boolean; type boolean;
description "Was echo enabled for BFD."; description "Was echo enabled for BFD.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
2.16. BFD IP multihop YANG Module 2.16. BFD IP multihop YANG Module
This YANG module imports typedefs from [RFC6991] and augments This YANG module imports typedefs from [RFC6991] and augments
"/routing/control-plane-protocols/control-plane-protocol" from "/routing/control-plane-protocols/control-plane-protocol" from
[RFC8349]. [RFC8349].
<CODE BEGINS> file "ietf-bfd-ip-mh@2018-06-21.yang" <CODE BEGINS> file "ietf-bfd-ip-mh@2018-08-01.yang"
module ietf-bfd-ip-mh { module ietf-bfd-ip-mh {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-ip-mh"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-ip-mh";
prefix "bfd-ip-mh"; prefix "bfd-ip-mh";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
skipping to change at page 45, line 27 skipping to change at page 45, line 38
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-21 { revision 2018-08-01 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG data model for BFD IP multihop."; reference "RFC XXXX: A YANG data model for BFD IP multihop.";
} }
/* /*
* Augments * Augments
*/ */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/bfd:bfd" { + "rt:control-plane-protocol/bfd:bfd" {
description "BFD augmentation for IP multihop."; description "BFD augmentation for IP multihop.";
skipping to change at page 46, line 41 skipping to change at page 47, line 4
list sessions { list sessions {
config false; config false;
description description
"The multiple BFD sessions between a source and a " + "The multiple BFD sessions between a source and a " +
"destination."; "destination.";
uses bfd-types:all-session; uses bfd-types:all-session;
} }
} }
} }
} }
} }
/* /*
* Notifications * Notifications
*/ */
notification multihop-notification { notification multihop-notification {
description description
"Notification for BFD multi-hop session state change. An " + "Notification for BFD multi-hop session state change. An " +
"implementation may rate-limit notifications, e.g. when a" + "implementation may rate-limit notifications, e.g. when a " +
"session is continuously changing state."; "session is continuously changing state.";
uses bfd-types:notification-parms; uses bfd-types:notification-parms;
} }
} }
<CODE ENDS> <CODE ENDS>
2.17. BFD over LAG YANG Module 2.17. BFD over LAG YANG Module
This YANG module imports "interface-ref" from [RFC8343], typedefs This YANG module imports "interface-ref" from [RFC8343], typedefs
from [RFC6991] and augments "/routing/control-plane-protocols/ from [RFC6991] and augments "/routing/control-plane-protocols/
control-plane-protocol" from [RFC8349]. control-plane-protocol" from [RFC8349].
<CODE BEGINS> file "ietf-bfd-lag@2018-06-21.yang" <CODE BEGINS> file "ietf-bfd-lag@2018-08-01.yang"
module ietf-bfd-lag { module ietf-bfd-lag {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-lag"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-lag";
prefix "bfd-lag"; prefix "bfd-lag";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
// remove this note // remove this note
import ietf-bfd-types { import ietf-bfd-types {
prefix "bfd-types"; prefix "bfd-types";
reference "RFC XXXX: YANG Data Model for BFD"; reference "RFC XXXX: YANG Data Model for BFD";
} }
import ietf-bfd { import ietf-bfd {
prefix "bfd"; prefix "bfd";
reference "RFC XXXX: YANG Data Model for BFD"; reference "RFC XXXX: YANG Data Model for BFD";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
reference reference
"RFC 8343: A YANG Data Model for Interface Management"; "RFC 8343: A YANG Data Model for Interface Management";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference "RFC 6991: Common YANG Data Types"; reference "RFC 6991: Common YANG Data Types";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference reference
"RFC 8349: A YANG Data Model for Routing Management "RFC 8349: A YANG Data Model for Routing Management
(NMDA version)"; (NMDA version)";
} }
organization "IETF BFD Working Group"; organization "IETF BFD Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/bfd> "WG Web: <http://tools.ietf.org/wg/bfd>
WG List: <rtg-bfd@ietf.org> WG List: <rtg-bfd@ietf.org>
Editors: Reshad Rahman (rrahman@cisco.com), Editors: Reshad Rahman (rrahman@cisco.com),
Lianshu Zheng vero.zheng@huawei.com), Lianshu Zheng vero.zheng@huawei.com),
Mahesh Jethanandani (mjethanandani@gmail.com)"; Mahesh Jethanandani (mjethanandani@gmail.com)";
description description
"This module contains the YANG definition for BFD over LAG "This module contains the YANG definition for BFD over LAG
interfaces as per RFC7130. interfaces as per RFC7130.
Copyright (c) 2018 IETF Trust and the persons Copyright (c) 2018 IETF Trust and the persons
identified as authors of the code. All rights reserved. identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-21 { revision 2018-08-01 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG data model for BFD over LAG"; reference "RFC XXXX: A YANG data model for BFD over LAG";
}
/* }
* Augments
*/
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/bfd:bfd" {
description "BFD augmentation for LAG";
container lag {
description "BFD over LAG top level container";
container micro-bfd-ipv4-session-statistics {
description "Micro-BFD IPv4 session counters.";
uses bfd-types:session-statistics-summary;
}
container micro-bfd-ipv6-session-statistics {
description "Micro-BFD IPv6 session counters.";
uses bfd-types:session-statistics-summary;
}
container sessions { /*
description * Augments
"BFD over LAG sessions"; */
list session { augment "/rt:routing/rt:control-plane-protocols/"
key "lag-name"; + "rt:control-plane-protocol/bfd:bfd" {
description "List of BFD over LAG sessions."; description "BFD augmentation for LAG";
leaf lag-name { container lag {
type if:interface-ref ; description "BFD over LAG top level container";
description "Name of the LAG";
}
leaf ipv4-dest-addr {
type inet:ipv4-address;
description
"IPv4 address of the peer, for IPv4 micro-BFD.";
}
leaf ipv6-dest-addr {
type inet:ipv6-address;
description
"IPv6 address of the peer, for IPv6 micro-BFD.";
}
uses bfd-types:common-cfg-parms;
leaf use-ipv4 { container micro-bfd-ipv4-session-statistics {
type boolean; description "Micro-BFD IPv4 session counters.";
description "Using IPv4 micro-BFD."; uses bfd-types:session-statistics-summary;
} }
leaf use-ipv6 { container micro-bfd-ipv6-session-statistics {
type boolean; description "Micro-BFD IPv6 session counters.";
description "Using IPv6 micro-BFD."; uses bfd-types:session-statistics-summary;
} }
list member-links { container sessions {
key "member-link"; description
config false; "BFD over LAG sessions";
description list session {
"Micro-BFD over LAG. This represents one member link."; key "lag-name";
description "List of BFD over LAG sessions.";
leaf lag-name {
type if:interface-ref ;
description "Name of the LAG";
}
leaf ipv4-dest-addr {
type inet:ipv4-address;
description
"IPv4 address of the peer, for IPv4 micro-BFD.";
}
leaf ipv6-dest-addr {
type inet:ipv6-address;
description
"IPv6 address of the peer, for IPv6 micro-BFD.";
}
uses bfd-types:common-cfg-parms;
leaf member-link { leaf use-ipv4 {
type if:interface-ref; type boolean;
description description "Using IPv4 micro-BFD.";
"Member link on which micro-BFD is running."; }
} leaf use-ipv6 {
container micro-bfd-ipv4 { type boolean;
when "../../use-ipv4 = 'true'" { description "Using IPv6 micro-BFD.";
description "Needed only if IPv4 is used."; }
}
description
"Micro-BFD IPv4 session state on member link.";
uses bfd-types:all-session;
}
container micro-bfd-ipv6 {
when "../../use-ipv6 = 'true'" {
description "Needed only if IPv6 is used.";
}
description
"Micro-BFD IPv6 session state on member link.";
uses bfd-types:all-session;
}
}
}
}
}
}
/* list member-links {
* Notifications key "member-link";
*/ config false;
notification lag-notification { description
description "Micro-BFD over LAG. This represents one member link.";
"Notification for BFD over LAG session state change. " +
"An implementation may rate-limit notifications, e.g. when a" +
"session is continuously changing state.";
uses bfd-types:notification-parms; leaf member-link {
type if:interface-ref;
description
"Member link on which micro-BFD is running.";
}
container micro-bfd-ipv4 {
when "../../use-ipv4 = 'true'" {
description "Needed only if IPv4 is used.";
}
description
"Micro-BFD IPv4 session state on member link.";
uses bfd-types:all-session;
}
container micro-bfd-ipv6 {
when "../../use-ipv6 = 'true'" {
description "Needed only if IPv6 is used.";
}
description
"Micro-BFD IPv6 session state on member link.";
uses bfd-types:all-session;
}
}
}
}
}
}
leaf lag-name { /*
type if:interface-ref; * Notifications
description "LAG interface name."; */
} notification lag-notification {
description
"Notification for BFD over LAG session state change. " +
"An implementation may rate-limit notifications, e.g. when a " +
"session is continuously changing state.";
leaf member-link { uses bfd-types:notification-parms;
type if:interface-ref;
description "Member link on which BFD is running."; leaf lag-name {
} type if:interface-ref;
} description "LAG interface name.";
} }
<CODE ENDS>
leaf member-link {
type if:interface-ref;
description "Member link on which BFD is running.";
}
}
}
<CODE ENDS>
2.18. BFD over MPLS YANG Module 2.18. BFD over MPLS YANG Module
This YANG module imports typedefs from [RFC6991] and augments This YANG module imports typedefs from [RFC6991] and augments
"/routing/control-plane-protocols/control-plane-protocol" from "/routing/control-plane-protocols/control-plane-protocol" from
[RFC8349]. [RFC8349].
<CODE BEGINS> file "ietf-bfd-mpls@2018-06-21.yang" <CODE BEGINS> file "ietf-bfd-mpls@2018-08-01.yang"
module ietf-bfd-mpls { module ietf-bfd-mpls {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-mpls"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-mpls";
prefix "bfd-mpls"; prefix "bfd-mpls";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
// remove this note // remove this note
import ietf-bfd-types { import ietf-bfd-types {
prefix "bfd-types"; prefix "bfd-types";
reference "RFC XXXX: YANG Data Model for BFD"; reference "RFC XXXX: YANG Data Model for BFD";
} }
import ietf-bfd { import ietf-bfd {
prefix "bfd"; prefix "bfd";
reference "RFC XXXX: YANG Data Model for BFD"; reference "RFC XXXX: YANG Data Model for BFD";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference "RFC 6991: Common YANG Data Types"; reference "RFC 6991: Common YANG Data Types";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference reference
"RFC 8349: A YANG Data Model for Routing Management "RFC 8349: A YANG Data Model for Routing Management
(NMDA version)"; (NMDA version)";
} }
organization "IETF BFD Working Group"; organization "IETF BFD Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/bfd> "WG Web: <http://tools.ietf.org/wg/bfd>
WG List: <rtg-bfd@ietf.org> WG List: <rtg-bfd@ietf.org>
Editors: Reshad Rahman (rrahman@cisco.com),
Lianshu Zheng (vero.zheng@huawei.com),
Mahesh Jethanandani (mjethanandani@gmail.com)";
description Editors: Reshad Rahman (rrahman@cisco.com),
"This module contains the YANG definition for BFD parameters for Lianshu Zheng (vero.zheng@huawei.com),
MPLS LSPs as per RFC 5884. Mahesh Jethanandani (mjethanandani@gmail.com)";
Copyright (c) 2018 IETF Trust and the persons description
identified as authors of the code. All rights reserved. "This module contains the YANG definition for BFD parameters for
MPLS LSPs as per RFC 5884.
Redistribution and use in source and binary forms, with or Copyright (c) 2018 IETF Trust and the persons
without modification, is permitted pursuant to, and subject identified as authors of the code. All rights reserved.
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see Redistribution and use in source and binary forms, with or
the RFC itself for full legal notices."; without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
reference "RFC XXXX"; This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision 2018-06-21 { reference "RFC XXXX";
description "Initial revision.";
reference "RFC XXXX: A YANG data model for BFD over MPLS LSPs";
}
/* revision 2018-08-01 {
* Identity definitions description "Initial revision.";
*/ reference "RFC XXXX: A YANG data model for BFD over MPLS LSPs";
identity encap-gach { }
base bfd-types:encap-type;
description
"BFD with G-ACh encapsulation as per RFC 5586.";
}
identity encap-ip-gach { /*
base bfd-types:encap-type; * Identity definitions
description */
"BFD with IP and G-ACh encapsulation as per RFC 5586."; identity encap-gach {
} base bfd-types:encap-type;
description
"BFD with G-ACh encapsulation as per RFC 5586.";
}
identity encap-ip-gach {
base bfd-types:encap-type;
description
"BFD with IP and G-ACh encapsulation as per RFC 5586.";
}
/* /*
* Groupings * Groupings
*/ */
grouping encap-cfg { grouping encap-cfg {
description "Configuration for BFD encapsulation"; description "Configuration for BFD encapsulation";
leaf encap {
type identityref {
base bfd-types:encap-type;
}
default bfd-types:encap-ip;
description "BFD encapsulation";
}
}
grouping mpls-dest-address { leaf encap {
description "Destination address as per RFC 5884."; type identityref {
base bfd-types:encap-type;
}
default bfd-types:encap-ip;
description "BFD encapsulation";
}
}
leaf mpls-dest-address { grouping mpls-dest-address {
type inet:ip-address; description "Destination address as per RFC 5884.";
config "false";
description
"Destination address as per RFC 5884.
Needed if IP encapsulation is used.";
}
}
/* leaf mpls-dest-address {
* Augments type inet:ip-address;
*/ config "false";
augment "/rt:routing/rt:control-plane-protocols/" description
+ "rt:control-plane-protocol/bfd:bfd" { "Destination address as per RFC 5884.
description "BFD augmentation for MPLS."; Needed if IP encapsulation is used.";
container mpls { }
description "BFD MPLS top level container."; }
uses bfd-types:session-statistics-summary; /*
* Augments
*/
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/bfd:bfd" {
description "BFD augmentation for MPLS.";
container mpls {
description "BFD MPLS top level container.";
container egress { uses bfd-types:session-statistics-summary;
description "Egress configuration.";
uses bfd-types:client-cfg-parms; container egress {
description "Egress configuration.";
uses bfd-types:auth-parms; uses bfd-types:client-cfg-parms;
} uses bfd-types:auth-parms;
}
container session-groups { container session-groups {
description description
"BFD over MPLS session groups."; "BFD over MPLS session groups.";
list session-group { list session-group {
key "mpls-fec"; key "mpls-fec";
description description
"Group of BFD MPLS sessions (for ECMP). A group of " + "Group of BFD MPLS sessions (for ECMP). A group of " +
"sessions is for 1 FEC, each session has a different " + "sessions is for 1 FEC, each session has a different " +
"field in UDP/IP hdr for ECMP."; "field in UDP/IP hdr for ECMP.";
leaf mpls-fec { leaf mpls-fec {
type inet:ip-prefix; type inet:ip-prefix;
description "MPLS FEC."; description "MPLS FEC.";
} }
uses bfd-types:common-cfg-parms; uses bfd-types:common-cfg-parms;
list sessions { list sessions {
config false; config false;
description description
"The BFD sessions for an MPLS FEC. Local " + "The BFD sessions for an MPLS FEC. Local " +
"discriminator is unique for each session in the " + "discriminator is unique for each session in the " +
"group."; "group.";
uses bfd-types:all-session; uses bfd-types:all-session;
uses bfd-mpls:mpls-dest-address; uses bfd-mpls:mpls-dest-address;
} }
} }
} }
} }
} }
/* /*
* Notifications * Notifications
*/ */
notification mpls-notification { notification mpls-notification {
description description
"Notification for BFD over MPLS FEC session state change. " + "Notification for BFD over MPLS FEC session state change. " +
"An implementation may rate-limit notifications, e.g. when a" + "An implementation may rate-limit notifications, e.g. when a " +
"session is continuously changing state."; "session is continuously changing state.";
uses bfd-types:notification-parms; uses bfd-types:notification-parms;
leaf mpls-dest-address { leaf mpls-dest-address {
type inet:ip-address; type inet:ip-address;
description description
"Destination address as per RFC 5884. "Destination address as per RFC 5884.
Needed if IP encapsulation is used."; Needed if IP encapsulation is used.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
2.19. BFD over MPLS-TE YANG Module 2.19. BFD over MPLS-TE YANG Module
This YANG module imports and augments "/te/tunnels/tunnel" from This YANG module imports and augments "/te/tunnels/tunnel" from
[I-D.ietf-teas-yang-te]. [I-D.ietf-teas-yang-te].
<CODE BEGINS> file "ietf-bfd-mpls-te@2018-06-21.yang" <CODE BEGINS> file "ietf-bfd-mpls-te@2018-08-01.yang"
module ietf-bfd-mpls-te { module ietf-bfd-mpls-te {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-mpls-te"; namespace "urn:ietf:params:xml:ns:yang:ietf-bfd-mpls-te";
prefix "bfd-mpls-te"; prefix "bfd-mpls-te";
// RFC Ed.: replace occurences of XXXX with actual RFC number and // RFC Ed.: replace occurences of XXXX with actual RFC number and
skipping to change at page 56, line 33 skipping to change at page 56, line 43
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://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.";
reference "RFC XXXX"; reference "RFC XXXX";
revision 2018-06-21 { revision 2018-08-01 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG data model for BFD over MPLS-TE"; reference "RFC XXXX: A YANG data model for BFD over MPLS-TE";
} }
/* /*
* Augments * Augments
*/ */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/bfd:bfd" { + "rt:control-plane-protocol/bfd:bfd" {
description "BFD augmentation for MPLS-TE."; description "BFD augmentation for MPLS-TE.";
container mpls-te { container mpls-te {
description "BFD MPLS-TE top level container."; description "BFD MPLS-TE top level container.";
container egress { container egress {
description "Egress configuration."; description "Egress configuration.";
uses bfd-types:client-cfg-parms; uses bfd-types:client-cfg-parms;
uses bfd-types:auth-parms; uses bfd-types:auth-parms;
} }
uses bfd-types:session-statistics-summary; uses bfd-types:session-statistics-summary;
} }
} }
augment "/te:te/te:tunnels/te:tunnel" { augment "/te:te/te:tunnels/te:tunnel" {
description "BFD configuration on MPLS-TE tunnel."; description "BFD configuration on MPLS-TE tunnel.";
skipping to change at page 57, line 36 skipping to change at page 57, line 46
uses bfd-mpls:mpls-dest-address; uses bfd-mpls:mpls-dest-address;
} }
/* /*
* Notifications * Notifications
*/ */
notification mpls-te-notification { notification mpls-te-notification {
description description
"Notification for BFD over MPLS-TE session state change. " + "Notification for BFD over MPLS-TE session state change. " +
"An implementation may rate-limit notifications, e.g. when a" + "An implementation may rate-limit notifications, e.g. when a " +
"session is continuously changing state."; "session is continuously changing state.";
uses bfd-types:notification-parms; uses bfd-types:notification-parms;
uses bfd-mpls:mpls-dest-address; uses bfd-mpls:mpls-dest-address;
leaf tunnel-name { leaf tunnel-name {
type string; type string;
description "MPLS-TE tunnel on which BFD was running."; description "MPLS-TE tunnel on which BFD was running.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
3. Data Model examples 3. Data Model examples
skipping to change at page 62, line 15 skipping to change at page 63, line 15
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability: and their sensitivity/vulnerability:
/routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh/ /routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh/
sessions: the list specifies the IP single-hop BFD sessions. sessions: the list specifies the IP single-hop BFD sessions.
/routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh/ /routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh/
sessions: data nodes local-multiplier, desired-min-tx-interval, sessions: data nodes local-multiplier, desired-min-tx-interval,
required-min-rx-interval, min-interval and authentication all impact required-min-rx-interval and min-interval all impact the BFD IP
the BFD IP single-hop session. single-hop session. The source-addr and dest-addr data nodes can be
used to send BFD packets to unwitting recipients, [RFC5880] describes
how BFD mitigates against such threats. Authentication data nodes
key-chain and meticulous impact the security of the BFD IP single-hop
session.
/routing/control-plane-protocols/control-plane-protocol/bfd/ip-mh/ /routing/control-plane-protocols/control-plane-protocol/bfd/ip-mh/
session-group: the list specifies the IP multi-hop BFD session session-group: the list specifies the IP multi-hop BFD session
groups. groups.
/routing/control-plane-protocols/control-plane-protocol/bfd/ip-mh/ /routing/control-plane-protocols/control-plane-protocol/bfd/ip-mh/
session-group: data nodes local-multiplier, desired-min-tx-interval, session-group: data nodes local-multiplier, desired-min-tx-interval,
required-min-rx-interval, min-interval and authentication all impact required-min-rx-interval and min-interval all impact the BFD IP
the BFD IP multi-hop session. multi-hop session. The source-addr and dest-addr data nodes can be
used to send BFD packets to unwitting recipients, [RFC5880] describes
how BFD mitigates against such threats. Authentication data nodes
key-chain and meticulous impact the security of the BFD IP multi-hop
session.
/routing/control-plane-protocols/control-plane-protocol/bfd/lag/ /routing/control-plane-protocols/control-plane-protocol/bfd/lag/
sessions: the list specifies the BFD sessions over LAG. sessions: the list specifies the BFD sessions over LAG.
/routing/control-plane-protocols/control-plane-protocol/bfd/lag/ /routing/control-plane-protocols/control-plane-protocol/bfd/lag/
sessions: data nodes local-multiplier, desired-min-tx-interval, sessions: data nodes local-multiplier, desired-min-tx-interval,
required-min-rx-interval, min-interval and authentication all impact required-min-rx-interval and min-interval all impact the BFD over LAG
the BFD over LAG session. session. The ipv4-dest-addr and ipv6-dest-addr data nodes can be
used to send BFD packets to unwitting recipients, [RFC5880] describes
how BFD mitigates against such threats. Authentication data nodes
key-chain and meticulous impact the security of the BFD over LAG
session.
/routing/control-plane-protocols/control-plane-protocol/bfd/mpls/ /routing/control-plane-protocols/control-plane-protocol/bfd/mpls/
session-group: the list specifies the session groups for BFD over session-group: the list specifies the session groups for BFD over
MPLS. MPLS.
/routing/control-plane-protocols/control-plane-protocol/bfd/mpls/ /routing/control-plane-protocols/control-plane-protocol/bfd/mpls/
session-group: data nodes local-multiplier, desired-min-tx-interval, session-group: data nodes local-multiplier, desired-min-tx-interval,
required-min-rx-interval, min-interval and authentication all impact required-min-rx-interval, and min-interval all impact the BFD over
the BFD over MPLS LSPs session. MPLS LSPs session. Authentication data nodes key-chain and
meticulous impact the security of the BFD over MPLS LSPs session.
/routing/control-plane-protocols/control-plane-protocol/bfd/mpls/ /routing/control-plane-protocols/control-plane-protocol/bfd/mpls/
egress: data nodes local-multiplier, desired-min-tx-interval, egress: data nodes local-multiplier, desired-min-tx-interval,
required-min-rx-interval, min-interval and authentication all impact required-min-rx-interval and min-interval all impact the BFD over
the BFD over MPLS LSPs sessions for which this device is an MPLS LSP MPLS LSPs sessions for which this device is an MPLS LSP egress node.
egress node. Authentication data nodes key-chain and meticulous impact the
security of the BFD over MPLS LSPs sessions for which this device is
an MPLS LSP egress node
/te/tunnels/tunnel: data nodes local-multiplier, desired-min-tx- /te/tunnels/tunnel: data nodes local-multiplier, desired-min-tx-
interval, required-min-rx-interval, min-interval and authentication interval, required-min-rx-interval and min-interval all impact the
all impact the BFD session over the MPLS-TE tunnel. BFD session over the MPLS-TE tunnel. Authentication data nodes key-
chain and meticulous impact the security of the BFD session over the
MPLS-TE tunnel.
/routing/control-plane-protocols/control-plane-protocol/bfd/mpls-te/ /routing/control-plane-protocols/control-plane-protocol/bfd/mpls-te/
egress: data nodes local-multiplier, desired-min-tx-interval, egress: data nodes local-multiplier, desired-min-tx-interval,
required-min-rx-interval, min-interval and authentication all impact required-min-rx-interval and min-interval all impact the BFD over
the BFD over MPLS-TE sessions for which this device is an MPLS-TE MPLS-TE sessions for which this device is an MPLS-TE egress node.
egress node. Authentication data nodes key-chain and meticulous impact the
security of the BFD over MPLS-TE sessions for which this device is an
MPLS-TE egress node.
The YANG module has writeable data nodes which can be used for The YANG module has writeable data nodes which can be used for
creation of BFD sessions and modification of BFD session parameters. creation of BFD sessions and modification of BFD session parameters.
The system should "police" creation of BFD sessions to prevent new The system should "police" creation of BFD sessions to prevent new
sessions from causing existing BFD sessions to fail. For BFD session sessions from causing existing BFD sessions to fail. For BFD session
modification, the BFD protocol has mechanisms in place which allow modification, the BFD protocol has mechanisms in place which allow
for in service modification. for in service modification.
When BFD clients are used to modify BFD configuration (as described
in Section 2.1), the BFD clients need to be included in an analysis
of the security properties of the BFD-using system (e.g., when
considering the authentication and authorization of control actions).
In many cases, BFD is not the most vulnerable portion of such a
composite system, since BFD is limited to generating well-defined
traffic at a fixed rate on a given path; in the case of an IGP as BFD
client, attacking the IGP could cause more broad-scale disruption
than (de)configuring a BFD session could cause.
Some of the readable data nodes in this YANG module may be considered Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
/routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh/ /routing/control-plane-protocols/control-plane-protocol/bfd/ip-sh/
summary: access to this information discloses the number of BFD IP summary: access to this information discloses the number of BFD IP
single-hop sessions which are up, down and admin-down. The counters single-hop sessions which are up, down and admin-down. The counters
include BFD sessions for which the user does not have read-access. include BFD sessions for which the user does not have read-access.
/routing/control-plane-protocols/control-plane-protocol/bfd/ip-
sh/sessions/session/: access to data nodes local-discriminator and
remote-discriminator (combined with the data nodes in the
authentication container) provides the ability to spoof BFD IP
single-hop packets.
/routing/control-plane-protocols/control-plane-protocol/bfd/ip-mh/ /routing/control-plane-protocols/control-plane-protocol/bfd/ip-mh/
summary: access to this information discloses the number of BFD IP summary: access to this information discloses the number of BFD IP
multi-hop sessions which are up, down and admin-down. The counters multi-hop sessions which are up, down and admin-down. The counters
include BFD sessions for which the user does not have read-access. include BFD sessions for which the user does not have read-access.
/routing/control-plane-protocols/control-plane-protocol/bfd/ip-mh/
session-groups/session-group/sessions: access to data nodes local-
discriminator and remote-discriminator (combined with the data nodes
in the session-group's authentication container) provides the ability
to spoof BFD IP multi-hop packets.
/routing/control-plane-protocols/control-plane-protocol/bfd/lag/ /routing/control-plane-protocols/control-plane-protocol/bfd/lag/
micro-bfd-ipv4-session-statistics/summary: access to this information micro-bfd-ipv4-session-statistics/summary: access to this information
discloses the number of micro BFD IPv4 LAG sessions which are up, discloses the number of micro BFD IPv4 LAG sessions which are up,
down and admin-down. The counters include BFD sessions for which the down and admin-down. The counters include BFD sessions for which the
user does not have read-access. user does not have read-access.
/routing/control-plane-protocols/control-plane-
protocol/bfd/lag/sessions/session/member-links/member-link/micro-bfd-
ipv4: access to data nodes local-discriminator and remote-
discriminator (combined with the data nodes in the session's
authentication container) provides the ability to spoof BFD IPv4 LAG
packets.
/routing/control-plane-protocols/control-plane-protocol/bfd/lag/ /routing/control-plane-protocols/control-plane-protocol/bfd/lag/
micro-bfd-ipv6-session-statistics/summary: access to this information micro-bfd-ipv6-session-statistics/summary: access to this information
discloses the number of micro BFD IPv6 LAG sessions which are up, discloses the number of micro BFD IPv6 LAG sessions which are up,
down and admin-down. The counters include BFD sessions for which the down and admin-down. The counters include BFD sessions for which the
user does not have read-access. user does not have read-access.
/routing/control-plane-protocols/control-plane-
protocol/bfd/lag/sessions/session/member-links/member-link/micro-bfd-
ipv6: access to data nodes local-discriminator and remote-
discriminator (combined with the data nodes in the session's
authentication container) provides the ability to spoof BFD IPv6 LAG
packets.
/routing/control-plane-protocols/control-plane-protocol/bfd/mpls/ /routing/control-plane-protocols/control-plane-protocol/bfd/mpls/
summary: access to this information discloses the number of BFD summary: access to this information discloses the number of BFD
sessions over MPLS LSPs which are up, down and admin-down. The sessions over MPLS LSPs which are up, down and admin-down. The
counters include BFD sessions for which the user does not have read- counters include BFD sessions for which the user does not have read-
access. access.
/routing/control-plane-protocols/control-plane-protocol/bfd/mpls/
session-groups/session-group/sessions: access to data nodes local-
discriminator and remote-discriminator (combined with the data nodes
in the session-group's authentication container) provides the ability
to spoof BFD over MPLS LSPs packets.
/routing/control-plane-protocols/control-plane-protocol/bfd/mpls-te/ /routing/control-plane-protocols/control-plane-protocol/bfd/mpls-te/
summary: access to this information discloses the number of BFD summary: access to this information discloses the number of BFD
sessions over MPLS-TE which are up, down and admin-down. The sessions over MPLS-TE which are up, down and admin-down. The
counters include BFD sessions for which the user does not have read- counters include BFD sessions for which the user does not have read-
access. access.
/te/lsps-state/lsp: access to data nodes local-discriminator and
remote-discriminator (combined with the data nodes in the tunnel's
authentication container) provides the ability to spoof BFD over
MPLS-TE packets.
5. IANA Considerations 5. IANA Considerations
This document registers the following namespace URIs in the IETF XML This document registers the following namespace URIs in the IETF XML
registry [RFC3688]: registry [RFC3688]:
-------------------------------------------------------------------- --------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:iana-bfd-types URI: urn:ietf:params:xml:ns:yang:iana-bfd-types
Registrant Contact: The IESG. Registrant Contact: The IESG.
skipping to change at page 68, line 36 skipping to change at page 71, line 8
7.1. Normative References 7.1. Normative References
[I-D.ietf-mpls-base-yang] [I-D.ietf-mpls-base-yang]
Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A
YANG Data Model for MPLS Base", draft-ietf-mpls-base- YANG Data Model for MPLS Base", draft-ietf-mpls-base-
yang-06 (work in progress), February 2018. yang-06 (work in progress), February 2018.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and
I. Bryskin, "A YANG Data Model for Traffic Engineering I. Bryskin, "A YANG Data Model for Traffic Engineering
Tunnels and Interfaces", draft-ietf-teas-yang-te-15 (work Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work
in progress), June 2018. in progress), July 2018.
[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>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
skipping to change at page 72, line 47 skipping to change at page 75, line 15
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://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.";
revision 2018-06-21 { revision 2018-08-01 {
description "Initial revision."; description "Initial revision.";
reference reference
"RFC XXXX: A YANG data model example augmentation for BFD echo "RFC XXXX: A YANG data model example augmentation for BFD echo
function"; function";
} }
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note // note
/* /*
* Groupings * Groupings
*/ */
grouping echo-cfg-parms { grouping echo-cfg-parms {
description "BFD grouping for echo config parameters"; description "BFD grouping for echo config parameters";
skipping to change at page 74, line 4 skipping to change at page 76, line 16
container echo { container echo {
if-feature bfd-types:echo-mode; if-feature bfd-types:echo-mode;
description "BFD echo function container"; description "BFD echo function container";
uses echo-cfg-parms; uses echo-cfg-parms;
} }
} }
} }
Appendix B. Change log Appendix B. Change log
RFC Editor: Remove this section upon publication as an RFC. RFC Editor: Remove this section upon publication as an RFC.
B.1. Changes between versions -15 and -16 B.1. Changes between versions -16 and -17
o Addressed IESG comments.
B.2. Changes between versions -15 and -16
o Added list of modules for YANG module registry. o Added list of modules for YANG module registry.
B.2. Changes between versions -14 and -15 B.3. Changes between versions -14 and -15
o Added missing ietf-bfd-types in XML registry. o Added missing ietf-bfd-types in XML registry.
B.3. Changes between versions -13 and -14 B.4. Changes between versions -13 and -14
o Addressed missing/incorrect references in import statements. o Addressed missing/incorrect references in import statements.
B.4. Changes between versions -12 and -13 B.5. Changes between versions -12 and -13
o Updated references for drafts which became RFCs recently. o Updated references for drafts which became RFCs recently.
B.5. Changes between versions -11 and -12 B.6. Changes between versions -11 and -12
o Addressed comments from YANG Doctor review of rev11. o Addressed comments from YANG Doctor review of rev11.
B.6. Changes between versions -10 and -11 B.7. Changes between versions -10 and -11
o Added 2 examples. o Added 2 examples.
o Added a container around some lists. o Added a container around some lists.
o Fixed some indentation nits. o Fixed some indentation nits.
B.7. Changes between versions -09 and -10 B.8. Changes between versions -09 and -10
o Addressed comments from YANG Doctor review. o Addressed comments from YANG Doctor review.
o Addressed comments from WGLC. o Addressed comments from WGLC.
B.8. Changes between versions -08 and -09 B.9. Changes between versions -08 and -09
o Mostly cosmetic changes to abide by draft-ietf-netmod-rfc6087bis. o Mostly cosmetic changes to abide by draft-ietf-netmod-rfc6087bis.
o Specified yang-version 1.1. o Specified yang-version 1.1.
o Added data model examples. o Added data model examples.
o Some minor changes. o Some minor changes.
B.9. Changes between versions -07 and -08 B.10. Changes between versions -07 and -08
o Timer intervals in client-cfg-parms are not mandatory anymore. o Timer intervals in client-cfg-parms are not mandatory anymore.
o Added list of interfaces under "ip-sh" node for authentication o Added list of interfaces under "ip-sh" node for authentication
parameters. parameters.
o Renamed replay-protection to meticulous. o Renamed replay-protection to meticulous.
B.10. Changes between versions -06 and -07 B.11. Changes between versions -06 and -07
o New ietf-bfd-types module. o New ietf-bfd-types module.
o Grouping for BFD clients to have BFD multiplier and interval o Grouping for BFD clients to have BFD multiplier and interval
values. values.
o Change in ietf-bfd-mpls-te since MPLS-TE model changed. o Change in ietf-bfd-mpls-te since MPLS-TE model changed.
o Removed bfd- prefix from many names. o Removed bfd- prefix from many names.
B.11. Changes between versions -05 and -06 B.12. Changes between versions -05 and -06
o Adhere to NMDA-guidelines. o Adhere to NMDA-guidelines.
o Echo function config moved to appendix as example. o Echo function config moved to appendix as example.
o Added IANA YANG modules. o Added IANA YANG modules.
o Addressed various comments. o Addressed various comments.
B.12. Changes between versions -04 and -05 B.13. Changes between versions -04 and -05
o "bfd" node in augment of control-plane-protocol. o "bfd" node in augment of control-plane-protocol.
o Removed augment of network-instance. Replaced by schema-mount. o Removed augment of network-instance. Replaced by schema-mount.
o Added information on interaction with other YANG modules. o Added information on interaction with other YANG modules.
B.13. Changes between versions -03 and -04 B.14. Changes between versions -03 and -04
o Updated author information. o Updated author information.
o Fixed YANG compile error in ietf-bfd-lag.yang which was due to o Fixed YANG compile error in ietf-bfd-lag.yang which was due to
incorrect when statement. incorrect when statement.
B.14. Changes between versions -02 and -03 B.15. Changes between versions -02 and -03
o Fixed YANG compilation warning due to incorrect revision date in o Fixed YANG compilation warning due to incorrect revision date in
ietf-bfd-ip-sh module. ietf-bfd-ip-sh module.
B.15. Changes between versions -01 and -02 B.16. Changes between versions -01 and -02
o Replace routing-instance with network-instance from YANG Network o Replace routing-instance with network-instance from YANG Network
Instances [I-D.ietf-rtgwg-ni-model] Instances [I-D.ietf-rtgwg-ni-model]
B.16. Changes between versions -00 and -01 B.17. Changes between versions -00 and -01
o Remove BFD configuration parameters from BFD clients, all BFD o Remove BFD configuration parameters from BFD clients, all BFD
configuration parameters in BFD configuration parameters in BFD
o YANG module split in multiple YANG modules (one per type of o YANG module split in multiple YANG modules (one per type of
forwarding path) forwarding path)
o For BFD over MPLS-TE we augment MPLS-TE model o For BFD over MPLS-TE we augment MPLS-TE model
o For BFD authentication we now use YANG Data Model for Key Chains o For BFD authentication we now use YANG Data Model for Key Chains
skipping to change at page 77, line 4 skipping to change at page 79, line 17
Email: vero.zheng@huawei.com Email: vero.zheng@huawei.com
Mahesh Jethanandani (editor) Mahesh Jethanandani (editor)
Xoriant Corporation Xoriant Corporation
1248 Reamwood Ave 1248 Reamwood Ave
Sunnyvale, California 94089 Sunnyvale, California 94089
USA USA
Email: mjethanandani@gmail.com Email: mjethanandani@gmail.com
Santosh Pallagatti Santosh Pallagatti
Rtbrick
India India
Email: santosh.pallagatti@gmail.com Email: santosh.pallagatti@gmail.com
Greg Mirsky Greg Mirsky
ZTE Corporation ZTE Corporation
Email: gregimirsky@gmail.com Email: gregimirsky@gmail.com
 End of changes. 142 change blocks. 
399 lines changed or deleted 483 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/