Diff: rfc9643v5.txt - rfc9643.txt

	rfc9643v5.txt	rfc9643.txt

	skipping to change at line 17 ¶	skipping to change at line 17 ¶

	YANG Groupings for TCP Clients and TCP Servers	YANG Groupings for TCP Clients and TCP Servers

	Abstract	Abstract

	This document presents three YANG 1.1 modules to support the	This document presents three YANG 1.1 modules to support the
	configuration of TCP clients and TCP servers. The modules include	configuration of TCP clients and TCP servers. The modules include
	basic parameters of a TCP connection relevant for client or server	basic parameters of a TCP connection relevant for client or server
	applications, as well as client configuration required for traversing	applications, as well as client configuration required for traversing
	proxies. The data models defined by these modules may be used	proxies. The data models defined by these modules may be used

	directly (e.g., to define a specific TCP-client or TCP-server) or in	directly (e.g., to define a specific TCP client or TCP server) or in
	conjunction with the configuration defined for higher level protocols	conjunction with the configuration defined for higher level protocols
	that depend on TCP (e.g., SSH, TLS, etc.). Examples of higher level	that depend on TCP (e.g., SSH, TLS, etc.). Examples of higher level
	protocol configuration designed to be used in conjunction with this	protocol configuration designed to be used in conjunction with this
	configuration are in RFCs 9644 and 9645.	configuration are in RFCs 9644 and 9645.

	Status of This Memo	Status of This Memo

	This is an Internet Standards Track document.	This is an Internet Standards Track document.

	This document is a product of the Internet Engineering Task Force	This document is a product of the Internet Engineering Task Force

	skipping to change at line 89 ¶	skipping to change at line 89 ¶
	7.1. Normative References	7.1. Normative References
	7.2. Informative References	7.2. Informative References
	Acknowledgements	Acknowledgements
	Authors' Addresses	Authors' Addresses

	1. Introduction	1. Introduction

	This document defines three YANG 1.1 [RFC7950] modules to support the	This document defines three YANG 1.1 [RFC7950] modules to support the
	configuration of TCP clients and TCP servers (TCP is defined in	configuration of TCP clients and TCP servers (TCP is defined in
	[RFC9293]). The data models defined by these modules may be used	[RFC9293]). The data models defined by these modules may be used

	directly (e.g., to define a specific TCP-client or TCP-server) or in	directly (e.g., to define a specific TCP client or TCP server) or in
	conjunction with the configuration defined for higher level protocols	conjunction with the configuration defined for higher level protocols
	that depend on TCP (e.g., SSH, TLS, etc.). Examples of higher level	that depend on TCP (e.g., SSH, TLS, etc.). Examples of higher level
	protocol configuration designed to be used in conjunction with this	protocol configuration designed to be used in conjunction with this
	configuration are in [RFC9644] and [RFC9645].	configuration are in [RFC9644] and [RFC9645].

	The modules focus on three different types of base TCP parameters	The modules focus on three different types of base TCP parameters
	that matter for TCP-based applications: First, the modules cover	that matter for TCP-based applications: First, the modules cover
	fundamental configuration of a TCP client or TCP server application,	fundamental configuration of a TCP client or TCP server application,
	such as addresses and port numbers. Second, a reusable grouping	such as addresses and port numbers. Second, a reusable grouping
	enables modification of application-specific parameters for TCP	enables modification of application-specific parameters for TCP

	skipping to change at line 1200 ¶	skipping to change at line 1200 ¶
	"The local IP address to listen on for incoming	"The local IP address to listen on for incoming
	TCP client connections. To configure listening	TCP client connections. To configure listening
	on all IPv4 addresses, the value must be '0.0.0.0'	on all IPv4 addresses, the value must be '0.0.0.0'
	(INADDR_ANY). To configure listening on all IPv6	(INADDR_ANY). To configure listening on all IPv6
	addresses, the value must be '::' (INADDR6_ANY).";	addresses, the value must be '::' (INADDR6_ANY).";
	}	}
	leaf local-port {	leaf local-port {
	type inet:port-number;	type inet:port-number;
	description	description
	"The local port number to listen on for incoming TCP	"The local port number to listen on for incoming TCP

	client connections.”;	client connections.";
	}	}
	}	}
	uses tcpcmn:tcp-common-grouping {	uses tcpcmn:tcp-common-grouping {
	refine "keepalives" {	refine "keepalives" {
	if-feature "tcp-server-keepalives";	if-feature "tcp-server-keepalives";
	description	description
	"An 'if-feature' statement so that implementations	"An 'if-feature' statement so that implementations
	can choose to support TCP server keepalives.";	can choose to support TCP server keepalives.";
	}	}
	}	}

	skipping to change at line 1437 ¶	skipping to change at line 1437 ¶
	[RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based	[RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
	Multiplexed and Secure Transport", RFC 9000,	Multiplexed and Secure Transport", RFC 9000,
	DOI 10.17487/RFC9000, May 2021,	DOI 10.17487/RFC9000, May 2021,
	<https://www.rfc-editor.org/info/rfc9000>.	<https://www.rfc-editor.org/info/rfc9000>.

	[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>.

	[RFC9640] Watsen, K., "YANG Data Types and Groupings for	[RFC9640] Watsen, K., "YANG Data Types and Groupings for

	Cryptography", RFC 9640, DOI 10.17487/RFC9640, September	Cryptography", RFC 9640, DOI 10.17487/RFC9640, October
	2024, <https://www.rfc-editor.org/info/rfc9640>.	2024, <https://www.rfc-editor.org/info/rfc9640>.

	7.2. Informative References	7.2. Informative References

	[HTTP-CLIENT-SERVER]	[HTTP-CLIENT-SERVER]
	Watsen, K., "YANG Groupings for HTTP Clients and HTTP	Watsen, K., "YANG Groupings for HTTP Clients and HTTP
	Servers", Work in Progress, Internet-Draft, draft-ietf-	Servers", Work in Progress, Internet-Draft, draft-ietf-
	netconf-http-client-server-23, 15 August 2024,	netconf-http-client-server-23, 15 August 2024,
	<https://datatracker.ietf.org/doc/html/draft-ietf-netconf-	<https://datatracker.ietf.org/doc/html/draft-ietf-netconf-
	http-client-server-23>.	http-client-server-23>.

	skipping to change at line 1519 ¶	skipping to change at line 1519 ¶
	[RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of	[RFC8407] Bierman, A., "Guidelines for Authors and Reviewers of
	Documents Containing YANG Data Models", BCP 216, RFC 8407,	Documents Containing YANG Data Models", BCP 216, RFC 8407,
	DOI 10.17487/RFC8407, October 2018,	DOI 10.17487/RFC8407, October 2018,
	<https://www.rfc-editor.org/info/rfc8407>.	<https://www.rfc-editor.org/info/rfc8407>.

	[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>.

	[RFC9641] Watsen, K., "A YANG Data Model for a Truststore",	[RFC9641] Watsen, K., "A YANG Data Model for a Truststore",

	RFC 9641, DOI 10.17487/RFC9641, September 2024,	RFC 9641, DOI 10.17487/RFC9641, October 2024,
	<https://www.rfc-editor.org/info/rfc9641>.	<https://www.rfc-editor.org/info/rfc9641>.

	[RFC9642] Watsen, K., "A YANG Data Model for a Keystore", RFC 9642,	[RFC9642] Watsen, K., "A YANG Data Model for a Keystore", RFC 9642,

	DOI 10.17487/RFC9642, September 2024,	DOI 10.17487/RFC9642, October 2024,
	<https://www.rfc-editor.org/info/rfc9642>.	<https://www.rfc-editor.org/info/rfc9642>.

	[RFC9644] Watsen, K., "YANG Groupings for SSH Clients and SSH	[RFC9644] Watsen, K., "YANG Groupings for SSH Clients and SSH

	Servers", RFC 9644, DOI 10.17487/RFC9644, September 2024,	Servers", RFC 9644, DOI 10.17487/RFC9644, October 2024,
	<https://www.rfc-editor.org/info/rfc9644>.	<https://www.rfc-editor.org/info/rfc9644>.

	[RFC9645] Watsen, K., "YANG Groupings for TLS Clients and TLS	[RFC9645] Watsen, K., "YANG Groupings for TLS Clients and TLS

	Servers", RFC 9645, DOI 10.17487/RFC9645, September 2024,	Servers", RFC 9645, DOI 10.17487/RFC9645, October 2024,
	<https://www.rfc-editor.org/info/rfc9645>.	<https://www.rfc-editor.org/info/rfc9645>.

	[SOCKS] Koblas, D. and M. Koblas, "SOCKS", USENIX UNIX Security	[SOCKS] Koblas, D. and M. Koblas, "SOCKS", USENIX UNIX Security
	Symposium III, September 1992, <https://www.usenix.org/leg	Symposium III, September 1992, <https://www.usenix.org/leg
	acy/publications/library/proceedings/sec92/full_papers/	acy/publications/library/proceedings/sec92/full_papers/
	koblas.pdf>.	koblas.pdf>.

	[SOCKS_4A] Lee, Y., "SOCKS 4A: A Simple Extension to SOCKS 4	[SOCKS_4A] Lee, Y., "SOCKS 4A: A Simple Extension to SOCKS 4
	Protocol", <https://www.openssh.com/txt/socks4a.protocol>.	Protocol", <https://www.openssh.com/txt/socks4a.protocol>.


End of changes. 8 change blocks.
	8 lines changed or deleted	8 lines changed or added
This html diff was produced by rfcdiff 1.48.