rfc9648v2.txt | rfc9648.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) M. Scharf | Internet Engineering Task Force (IETF) M. Scharf | |||
Request for Comments: 9648 Hochschule Esslingen | Request for Comments: 9648 Hochschule Esslingen | |||
Category: Standards Track M. Jethanandani | Category: Standards Track M. Jethanandani | |||
ISSN: 2070-1721 Kloud Services | ISSN: 2070-1721 Kloud Services | |||
V. Murgai | V. Murgai | |||
F5, Inc. | F5, Inc. | |||
August 2024 | September 2024 | |||
YANG Data Model for TCP | YANG Data Model for TCP | |||
Abstract | Abstract | |||
This document specifies a minimal YANG data model for TCP on devices | This document specifies a minimal YANG data model for TCP on devices | |||
that are configured and managed by network management protocols. The | that are configured and managed by network management protocols. The | |||
YANG data model defines a container for all TCP connections and | YANG data model defines a container for all TCP connections and | |||
groupings of authentication parameters that can be imported and used | groupings of authentication parameters that can be imported and used | |||
in TCP implementations or by other models that need to configure TCP | in TCP implementations or by other models that need to configure TCP | |||
skipping to change at line 123 ¶ | skipping to change at line 123 ¶ | |||
using "Translation of Structure of Management Information Version 2 | using "Translation of Structure of Management Information Version 2 | |||
(SMIv2) MIB Modules to YANG Modules" [RFC6643]. However, this | (SMIv2) MIB Modules to YANG Modules" [RFC6643]. However, this | |||
approach is not used in this document, because a translated model | approach is not used in this document, because a translated model | |||
would not be up-to-date. | would not be up-to-date. | |||
There are other existing TCP-related YANG data models, which are | There are other existing TCP-related YANG data models, which are | |||
orthogonal to this specification. Examples are: | orthogonal to this specification. Examples are: | |||
* TCP header attributes are modeled in other security-related | * TCP header attributes are modeled in other security-related | |||
models, such as those described in "YANG Data Model for Network | models, such as those described in "YANG Data Model for Network | |||
Access Control Lists (ACLs)" [RFC8519], "Distributed | Access Control Lists (ACLs)" [RFC8519], "Distributed Denial-of- | |||
Denial-of-Service Open Threat Signaling (DOTS) Data Channel | Service Open Threat Signaling (DOTS) Data Channel Specification" | |||
Specification" [RFC8783], "I2NSF Capability YANG Data Model" | [RFC8783], "I2NSF Capability YANG Data Model" [NSF-CAP-YANG], or | |||
[NSF-CAP-YANG], or "I2NSF Network Security Function-Facing | "I2NSF Network Security Function-Facing Interface YANG Data Model" | |||
Interface YANG Data Model" [NSF-FACING-YANG]. | [NSF-FACING-YANG]. | |||
* TCP-related configuration of a NAT (e.g., NAT44, NAT64, or | * TCP-related configuration of a NAT (e.g., NAT44, NAT64, or | |||
Destination NAT) is defined in "A YANG Module for Network Address | Destination NAT) is defined in "A YANG Module for Network Address | |||
Translation (NAT) and Network Prefix Translation (NPT)" [RFC8512] | Translation (NAT) and Network Prefix Translation (NPT)" [RFC8512] | |||
and "A YANG Data Model for Dual-Stack Lite (DS-Lite)" [RFC8513]. | and "A YANG Data Model for Dual-Stack Lite (DS-Lite)" [RFC8513]. | |||
* TCP-AO and TCP MD5 configuration for Layer 3 VPNs is modeled in "A | * TCP-AO and TCP MD5 configuration for Layer 3 VPNs is modeled in "A | |||
YANG Network Data Model for Layer 3 VPNs" [RFC9182]. This model | YANG Network Data Model for Layer 3 VPNs" [RFC9182]. This model | |||
assumes that TCP-AO-specific parameters are preconfigured in | assumes that TCP-AO-specific parameters are preconfigured in | |||
addition to the key chain parameters. | addition to the key chain parameters. | |||
skipping to change at line 871 ¶ | skipping to change at line 871 ¶ | |||
<CODE ENDS> | <CODE ENDS> | |||
5. IANA Considerations | 5. IANA Considerations | |||
5.1. The IETF XML Registry | 5.1. The IETF XML Registry | |||
IANA has registered the following URI in the "ns" registry defined in | IANA has registered the following URI in the "ns" registry defined in | |||
the "IETF XML Registry" [RFC3688]. | the "IETF XML Registry" [RFC3688]. | |||
URI: urn:ietf:params:xml:ns:yang:ietf-tcp | URI: urn:ietf:params:xml:ns:yang:ietf-tcp | |||
Registrant Contact: The IESG | Registrant Contact: The IESG. | |||
XML: N/A; the requested URI is an XML namespace. | XML: N/A; the requested URI is an XML namespace. | |||
5.2. The YANG Module Names Registry | 5.2. The YANG Module Names Registry | |||
IANA has registered the following in the "YANG Module Names" registry | IANA has registered the following in the "YANG Module Names" registry | |||
created by "YANG - A Data Modeling Language for the Network | created by "YANG - A Data Modeling Language for the Network | |||
Configuration Protocol (NETCONF)" [RFC6020]. | Configuration Protocol (NETCONF)" [RFC6020]. | |||
Name: ietf-tcp | Name: ietf-tcp | |||
Namespace: urn:ietf:params:xml:ns:yang:ietf-tcp | Namespace: urn:ietf:params:xml:ns:yang:ietf-tcp | |||
skipping to change at line 1033 ¶ | skipping to change at line 1033 ¶ | |||
[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>. | |||
[RFC9293] Eddy, W., Ed., "Transmission Control Protocol (TCP)", | [RFC9293] Eddy, W., Ed., "Transmission Control Protocol (TCP)", | |||
STD 7, RFC 9293, DOI 10.17487/RFC9293, August 2022, | STD 7, RFC 9293, DOI 10.17487/RFC9293, August 2022, | |||
<https://www.rfc-editor.org/info/rfc9293>. | <https://www.rfc-editor.org/info/rfc9293>. | |||
[RFC9643] Watsen, K. and M. Scharf, "YANG Groupings for TCP Clients | [RFC9643] Watsen, K. and M. Scharf, "YANG Groupings for TCP Clients | |||
and TCP Servers", RFC 9643, DOI 10.17487/RFC9643, May | and TCP Servers", RFC 9643, DOI 10.17487/RFC9643, | |||
2024, <https://www.rfc-editor.org/info/rfc9643>. | September 2024, <https://www.rfc-editor.org/info/rfc9643>. | |||
7.2. Informative References | 7.2. Informative References | |||
[BGP-MODEL] | [BGP-MODEL] | |||
Jethanandani, M., Patel, K., Hares, S., and J. Haas, "YANG | Jethanandani, M., Patel, K., Hares, S., and J. Haas, "YANG | |||
Model for Border Gateway Protocol (BGP-4)", Work in | Model for Border Gateway Protocol (BGP-4)", Work in | |||
Progress, Internet-Draft, draft-ietf-idr-bgp-model-17, 5 | Progress, Internet-Draft, draft-ietf-idr-bgp-model-17, 5 | |||
July 2023, <https://datatracker.ietf.org/doc/html/draft- | July 2023, <https://datatracker.ietf.org/doc/html/draft- | |||
ietf-idr-bgp-model-17>. | ietf-idr-bgp-model-17>. | |||
skipping to change at line 1134 ¶ | skipping to change at line 1134 ¶ | |||
[TAPS-INTERFACE] | [TAPS-INTERFACE] | |||
Trammell, B., Ed., Welzl, M., Ed., Enghardt, R., | Trammell, B., Ed., Welzl, M., Ed., Enghardt, R., | |||
Fairhurst, G., Kühlewind, M., Perkins, C., Tiesel, P., and | Fairhurst, G., Kühlewind, M., Perkins, C., Tiesel, P., and | |||
T. Pauly, "An Abstract Application Layer Interface to | T. Pauly, "An Abstract Application Layer Interface to | |||
Transport Services", Work in Progress, Internet-Draft, | Transport Services", Work in Progress, Internet-Draft, | |||
draft-ietf-taps-interface-26, 16 March 2024, | draft-ietf-taps-interface-26, 16 March 2024, | |||
<https://datatracker.ietf.org/doc/html/draft-ietf-taps- | <https://datatracker.ietf.org/doc/html/draft-ietf-taps- | |||
interface-26>. | interface-26>. | |||
[W3C.REC-xml-20081126] | ||||
Bray, T., Paoli, J., Sperberg-McQueen, C.M., Maler, E., | ||||
and F. Yergeau, "Extensible Markup Language (XML) 1.0 | ||||
(Fifth Edition)", World Wide Web Consortium | ||||
Recommendation REC-xml-20081126, November 2008, | ||||
<https://www.w3.org/TR/2008/REC-xml-20081126/>. | ||||
Appendix A. Examples | Appendix A. Examples | |||
A.1. Keepalive Configuration | A.1. Keepalive Configuration | |||
This particular example demonstrates how a particular connection can | This particular example demonstrates how a particular connection can | |||
be configured for keepalives. | be configured for keepalives. | |||
The following example uses the XML [W3C.REC-xml-20081126] encoding. | ||||
NOTE: '\' line wrapping per RFC 8792 | NOTE: '\' line wrapping per RFC 8792 | |||
<?xml version="1.0" encoding="UTF-8"?> | <?xml version="1.0" encoding="UTF-8"?> | |||
<!-- | <!-- | |||
This example shows how TCP keepalive, MSS, and PMTU can be configure\ | This example shows how TCP keepalive, MSS, and PMTU can be configure\ | |||
d for a given connection. An idle connection is dropped after | d for a given connection. An idle connection is dropped after | |||
idle-time + (max-probes * probe-interval). | idle-time + (max-probes * probe-interval). | |||
--> | --> | |||
<tcp | <tcp | |||
xmlns="urn:ietf:params:xml:ns:yang:ietf-tcp"> | xmlns="urn:ietf:params:xml:ns:yang:ietf-tcp"> | |||
skipping to change at line 1175 ¶ | skipping to change at line 1184 ¶ | |||
</connections> | </connections> | |||
</tcp> | </tcp> | |||
A.2. TCP-AO Configuration | A.2. TCP-AO Configuration | |||
The following example demonstrates how to model a TCP-AO [RFC5925] | The following example demonstrates how to model a TCP-AO [RFC5925] | |||
configuration for the example in "TCP Authentication Option (TCP-AO) | configuration for the example in "TCP Authentication Option (TCP-AO) | |||
Test Vectors" [RFC9235]. The IP addresses and other parameters are | Test Vectors" [RFC9235]. The IP addresses and other parameters are | |||
taken from the test vectors. | taken from the test vectors. | |||
The following example uses the XML [W3C.REC-xml-20081126] encoding. | ||||
NOTE: '\' line wrapping per RFC 8792 | NOTE: '\' line wrapping per RFC 8792 | |||
<?xml version="1.0" encoding="UTF-8"?> | <?xml version="1.0" encoding="UTF-8"?> | |||
<!-- | <!-- | |||
This example sets TCP-AO configuration parameters similarly to | This example sets TCP-AO configuration parameters similarly to | |||
the examples in RFC 9235. | the examples in RFC 9235. | |||
--> | --> | |||
<key-chains | <key-chains | |||
xmlns="urn:ietf:params:xml:ns:yang:ietf-key-chain"> | xmlns="urn:ietf:params:xml:ns:yang:ietf-key-chain"> | |||
End of changes. 7 change blocks. | ||||
9 lines changed or deleted | 20 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |