rfc9128.txt   rfc9128-11Oct2021.txt 
Internet Engineering Task Force (IETF) X. Liu Internet Engineering Task Force (IETF) X. Liu
Request for Comments: 9128 Volta Networks Request for Comments: 9128 Volta Networks
Category: Standards Track P. McAllister Category: Standards Track P. McAllister
ISSN: 2070-1721 Metaswitch Networks ISSN: 2070-1721 Metaswitch Networks
A. Peter A. Peter
Individual Individual
M. Sivakumar M. Sivakumar
Juniper Networks Juniper Networks
Y. Liu Y. Liu
China Mobile Huawei Technologies
F. Hu F. Hu
Individual Contributor Individual Contributor
November 2021 September 2021
YANG Data Model for Protocol Independent Multicast (PIM) YANG Data Model for Protocol Independent Multicast (PIM)
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 devices supporting Protocol Independent Multicast (PIM). and manage devices supporting Protocol Independent Multicast (PIM).
The model covers the PIM protocol configuration, operational state, The model covers the PIM protocol configuration, operational state,
and event notifications data. and event notifications data.
skipping to change at line 492 skipping to change at line 492
+--ro oper-status? enumeration +--ro oper-status? enumeration
+--ro gen-id? uint32 +--ro gen-id? uint32
+--ro hello-expiration? rt-types:timer-value-seconds16 +--ro hello-expiration? rt-types:timer-value-seconds16
+--ro ipv4 +--ro ipv4
| +--ro address* inet:ipv4-address | +--ro address* inet:ipv4-address
| +--ro dr-address? inet:ipv4-address | +--ro dr-address? inet:ipv4-address
+--ro ipv6 +--ro ipv6
| +--ro address* inet:ipv6-address | +--ro address* inet:ipv6-address
| +--ro dr-address? inet:ipv6-address | +--ro dr-address? inet:ipv6-address
Support for BFD client configuration is achieved by using a grouping Support for BFD is achieved by using a grouping provided by an
provided by an external module, "ietf-bfd-types", as defined in external module, "ietf-bfd-types", as defined in [RFC9127].
[RFC9127].
3.1.5. Neighbor Modeling 3.1.5. Neighbor Modeling
For each PIM interface, there can be a list of neighbors that For each PIM interface, there can be a list of neighbors that
contains operational state data for each neighbor. To model such contains operational state data for each neighbor. To model such
data, the following structure is specified: data, the following structure is specified:
+--rw pim! +--rw pim!
+--rw interfaces +--rw interfaces
+--rw interface* [name] +--rw interface* [name]
skipping to change at line 950 skipping to change at line 949
+--rw address-family identityref +--rw address-family identityref
+--rw bfd {bfd}? +--rw bfd {bfd}?
| +--rw enabled? boolean | +--rw enabled? boolean
| +--rw local-multiplier? multiplier | +--rw local-multiplier? multiplier
| +--rw (interval-config-type)? | +--rw (interval-config-type)?
| +--:(tx-rx-intervals) | +--:(tx-rx-intervals)
| | +--rw desired-min-tx-interval? uint32 | | +--rw desired-min-tx-interval? uint32
| | +--rw required-min-rx-interval? uint32 | | +--rw required-min-rx-interval? uint32
| +--:(single-interval) | +--:(single-interval)
| {single-minimum-interval}? | {single-minimum-interval}?
| +--rw min-interval? uint32 | +--rw min-interval uint32
+--rw dr-priority? uint32 +--rw dr-priority? uint32
| {intf-dr-priority}? | {intf-dr-priority}?
+--rw hello-interval? +--rw hello-interval?
| rt-types:timer-value-seconds16 | rt-types:timer-value-seconds16
| {intf-hello-interval}? | {intf-hello-interval}?
+--rw (hello-holdtime-or-multiplier)? +--rw (hello-holdtime-or-multiplier)?
| +--:(holdtime) {intf-hello-holdtime}? | +--:(holdtime) {intf-hello-holdtime}?
| | +--rw hello-holdtime? | | +--rw hello-holdtime?
| | rt-types:timer-value-seconds16 | | rt-types:timer-value-seconds16
| +--:(multiplier) {intf-hello-multiplier}? | +--:(multiplier) {intf-hello-multiplier}?
skipping to change at line 1658 skipping to change at line 1657
* Features * Features
*/ */
feature bfd { feature bfd {
description description
"Supports BFD (Bidirectional Forwarding Detection)."; "Supports BFD (Bidirectional Forwarding Detection).";
reference reference
"RFC 5880: Bidirectional Forwarding Detection (BFD)"; "RFC 5880: Bidirectional Forwarding Detection (BFD)";
} }
feature bfd-client-cfg {
description
"Support for BFD configuration of client parameters.";
reference
"RFC 9127: YANG Data Model for Bidirectional Forwarding
Detection (BFD)";
}
feature global-graceful-restart { feature global-graceful-restart {
description description
"Global configuration for graceful restart support as per "Global configuration for graceful restart support as per
RFC 8706."; RFC 8706.";
reference reference
"RFC 8706: Restart Signaling for IS-IS"; "RFC 8706: Restart Signaling for IS-IS";
} }
feature intf-dr-priority { feature intf-dr-priority {
description description
skipping to change at line 2362 skipping to change at line 2353
description description
"Reference to an entry in the global interface list."; "Reference to an entry in the global interface list.";
} }
list address-family { list address-family {
key "address-family"; key "address-family";
description description
"Each list entry for one address family."; "Each list entry for one address family.";
uses rt:address-family; uses rt:address-family;
container bfd { container bfd {
if-feature "bfd"; if-feature "bfd";
leaf enabled {
type boolean;
default "false";
description
"Indicates whether BFD is enabled.";
}
container bfd-client-parms {
if-feature "bfd-client-cfg";
uses bfd-types:base-cfg-parms;
description
"BFD client configuration.";
reference
"RFC 9127: YANG Data Model for Bidirectional
Forwarding Detection (BFD)";
}
description description
"BFD interface configuration."; "BFD (Bidirectional Forwarding Detection)
operation.";
uses bfd-types:client-cfg-parms;
} }
leaf dr-priority { leaf dr-priority {
if-feature "intf-dr-priority"; if-feature "intf-dr-priority";
type uint32; type uint32;
default "1"; default "1";
description description
"DR (Designated Router) priority as the preference in "DR (Designated Router) priority as the preference in
the DR election process."; the DR election process.";
} }
leaf hello-interval { leaf hello-interval {
skipping to change at line 4515 skipping to change at line 4493
DOI 10.17487/RFC8349, March 2018, DOI 10.17487/RFC8349, March 2018,
<https://www.rfc-editor.org/info/rfc8349>. <https://www.rfc-editor.org/info/rfc8349>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
[RFC9127] Rahman, R., Ed., Zheng, L., Ed., Jethanandani, M., Ed., [RFC9127] Rahman, R., Ed., Zheng, L., Ed., Jethanandani, M., Ed.,
Pallagatti, S., and G. Mirsky, "YANG Data Model for Pallagatti, S., and G. Mirsky, "YANG Data Model for
Bidirectional Forwarding Detection (BFD)", RFC 9127, Bidirectional Forwarding Detection (BFD)", RFC 9127,
DOI 10.17487/RFC9127, October 2021, DOI 10.17487/RFC9127, September 2021,
<https://www.rfc-editor.org/info/rfc9127>. <https://www.rfc-editor.org/info/rfc9127>.
9.2. Informative References 9.2. Informative References
[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version Thyagarajan, "Internet Group Management Protocol, Version
3", RFC 3376, DOI 10.17487/RFC3376, October 2002, 3", RFC 3376, DOI 10.17487/RFC3376, October 2002,
<https://www.rfc-editor.org/info/rfc3376>. <https://www.rfc-editor.org/info/rfc3376>.
[RFC3618] Fenner, B., Ed. and D. Meyer, Ed., "Multicast Source [RFC3618] Fenner, B., Ed. and D. Meyer, Ed., "Multicast Source
skipping to change at line 4998 skipping to change at line 4976
Mahesh Sivakumar Mahesh Sivakumar
Juniper Networks Juniper Networks
1133 Innovation Way 1133 Innovation Way
Sunnyvale, California Sunnyvale, California
United States of America United States of America
Email: sivakumar.mahesh@gmail.com Email: sivakumar.mahesh@gmail.com
Yisong Liu Yisong Liu
China Mobile Huawei Technologies
China Mobile Innovation Building Huawei Administration Building
32 Xuanwumen West Street Longgang
Beijing Guangdong, 518129
100053
China China
Email: liuyisong@chinamobile.com Email: liuyisong@chinamobile.com
Fangwei Hu Fangwei Hu
Individual Contributor Individual Contributor
86 Bohang Road 86 Bohang Road
Shanghai Shanghai
Shanghai, 200126 Shanghai, 200126
China China
 End of changes. 9 change blocks. 
36 lines changed or deleted 13 lines changed or added

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

mirror server hosted at Truenetwork, Russian Federation.