rfc9648v5.txt | rfc9648.txt | |||
---|---|---|---|---|
skipping to change at line 238 ¶ | skipping to change at line 238 ¶ | |||
Similar to the TCP MIB [RFC4022], this document also specifies basic | Similar to the TCP MIB [RFC4022], this document also specifies basic | |||
statistics, a TCP connection list, and a TCP listener list. | statistics, a TCP connection list, and a TCP listener list. | |||
* Statistics: Counters for the number of active/passive opens, sent | * Statistics: Counters for the number of active/passive opens, sent | |||
and received TCP segments, errors, and possibly other detailed | and received TCP segments, errors, and possibly other detailed | |||
debugging information. | debugging information. | |||
* TCP connection list: Access to status information for all TCP | * TCP connection list: Access to status information for all TCP | |||
connections. Note that the connection table is modeled as a list | connections. Note that the connection table is modeled as a list | |||
that is readable and writeable, even though a connection cannot be | that is readable and writable, even though a connection cannot be | |||
created by adding entries to the table. Similarly, deletion of | created by adding entries to the table. Similarly, deletion of | |||
connections from this list is implementation-specific. | connections from this list is implementation-specific. | |||
* TCP listener list: A list containing information about TCP | * TCP listener list: A list containing information about TCP | |||
listeners, i.e., applications willing to accept connections. | listeners, i.e., applications willing to accept connections. | |||
This allows implementations of TCP MIB [RFC4022] to migrate to the | This allows implementations of TCP MIB [RFC4022] to migrate to the | |||
YANG data model defined in this memo. Note that the TCP MIB does not | YANG data model defined in this memo. Note that the TCP MIB does not | |||
include means to reset statistics, which are defined in this | include means to reset statistics, which are defined in this | |||
document. This is not a major addition, as a reset can simply be | document. This is not a major addition, as a reset can simply be | |||
skipping to change at line 297 ¶ | skipping to change at line 297 ¶ | |||
4. TCP YANG Data Model | 4. TCP YANG Data Model | |||
This YANG module references "The TCP Authentication Option" | This YANG module references "The TCP Authentication Option" | |||
[RFC5925], "Protection of BGP Sessions via the TCP MD5 Signature | [RFC5925], "Protection of BGP Sessions via the TCP MD5 Signature | |||
Option" [RFC2385], and "Transmission Control Protocol (TCP)" | Option" [RFC2385], and "Transmission Control Protocol (TCP)" | |||
[RFC9293] and imports "Common YANG Data Types" [RFC6991], "Network | [RFC9293] and imports "Common YANG Data Types" [RFC6991], "Network | |||
Configuration Access Control Model" [RFC8341], and "YANG Groupings | Configuration Access Control Model" [RFC8341], and "YANG Groupings | |||
for TCP Clients and TCP Servers" [RFC9643]. | for TCP Clients and TCP Servers" [RFC9643]. | |||
<CODE BEGINS> file "ietf-tcp@2022-09-11.yang" | <CODE BEGINS> file "ietf-tcp@2024-10-10.yang" | |||
module ietf-tcp { | module ietf-tcp { | |||
yang-version 1.1; | yang-version 1.1; | |||
namespace "urn:ietf:params:xml:ns:yang:ietf-tcp"; | namespace "urn:ietf:params:xml:ns:yang:ietf-tcp"; | |||
prefix tcp; | prefix tcp; | |||
import ietf-yang-types { | import ietf-yang-types { | |||
prefix yang; | prefix yang; | |||
reference | reference | |||
"RFC 6991: Common YANG Data Types."; | "RFC 6991: Common YANG Data Types."; | |||
} | } | |||
skipping to change at line 365 ¶ | skipping to change at line 365 ¶ | |||
without modification, is permitted pursuant to, and subject to | without modification, is permitted pursuant to, and subject to | |||
the license terms contained in, the Revised BSD License set | the license terms contained in, the Revised BSD License set | |||
forth in Section 4.c of the IETF Trust's Legal Provisions | forth in Section 4.c of the IETF Trust's Legal Provisions | |||
Relating to IETF Documents | Relating to IETF Documents | |||
(https://trustee.ietf.org/license-info). | (https://trustee.ietf.org/license-info). | |||
This version of this YANG module is part of RFC 9648 | This version of this YANG module is part of RFC 9648 | |||
(https://www.rfc-editor.org/info/rfc9648); see the RFC itself | (https://www.rfc-editor.org/info/rfc9648); see the RFC itself | |||
for full legal notices."; | for full legal notices."; | |||
revision 2022-09-11 { | revision 2024-10-10 { | |||
description | description | |||
"Initial version."; | "Initial version."; | |||
reference | reference | |||
"RFC 9648: YANG Data Model for TCP."; | "RFC 9648: YANG Data Model for TCP."; | |||
} | } | |||
// Typedefs | // Typedefs | |||
typedef mss { | typedef mss { | |||
type uint16; | type uint16; | |||
description | description | |||
skipping to change at line 616 ¶ | skipping to change at line 616 ¶ | |||
by delayed segments from previous connections."; | by delayed segments from previous connections."; | |||
} | } | |||
} | } | |||
config false; | config false; | |||
description | description | |||
"The state of this TCP connection."; | "The state of this TCP connection."; | |||
} | } | |||
description | description | |||
"List of TCP connections with their parameters. | "List of TCP connections with their parameters. | |||
The list is modeled as writeable even though only some of | The list is modeled as writable even though only some of | |||
the nodes are writeable, e.g., keepalive. Connections | the nodes are writable, e.g., keepalive. Connections | |||
that are created and match this list SHOULD apply the | that are created and match this list SHOULD apply the | |||
writeable parameters. At the same time, implementations | writable parameters. At the same time, implementations | |||
may not allow creation of new TCP connections simply by | may not allow creation of new TCP connections simply by | |||
adding entries to the list. Furthermore, the behavior | adding entries to the list. Furthermore, the behavior | |||
upon removal is implementation-specific. Implementations | upon removal is implementation-specific. Implementations | |||
may not support closing or resetting a TCP connection | may not support closing or resetting a TCP connection | |||
upon an operation that removes the entry from the list. | upon an operation that removes the entry from the list. | |||
The operational state of this list SHOULD reflect | The operational state of this list SHOULD reflect | |||
connections that have configured but not created and | connections that have configured but not created and | |||
connections that have been created. Connections in the | connections that have been created. Connections in the | |||
CLOSED state are not reflected on this list."; | CLOSED state are not reflected on this list."; | |||
End of changes. 5 change blocks. | ||||
6 lines changed or deleted | 6 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |