| rfc9621v2.txt | rfc9621.txt | |||
|---|---|---|---|---|
| skipping to change at line 338 ¶ | skipping to change at line 338 ¶ | |||
| Endpoints. | Endpoints. | |||
| Server: The peer responsible for responding to a Connection | Server: The peer responsible for responding to a Connection | |||
| initiation. | initiation. | |||
| Socket: The combination of a destination IP address and a | Socket: The combination of a destination IP address and a | |||
| destination port number [RFC8303]. | destination port number [RFC8303]. | |||
| System Policy: The input from an operating system or other global | System Policy: The input from an operating system or other global | |||
| preferences that can constrain or influence how an implementation | preferences that can constrain or influence how an implementation | |||
| will gather Candidate Paths and Protocol Stacks and race the | will gather Candidate Paths and Candidate Protocol Stacks and race | |||
| candidates during establishment of a Connection. | the candidates during establishment of a Connection. | |||
| Transport Feature: A specific end-to-end feature that the transport | Transport Feature: A specific end-to-end feature that the transport | |||
| layer provides to an application. | layer provides to an application. | |||
| Transport Property: A property of a transport protocol and the | Transport Property: A property of a transport protocol and the | |||
| services it provides [RFC8095]. | services it provides [RFC8095]. | |||
| Transport Service: A set of transport features, not associated with | Transport Service: A set of transport features, not associated with | |||
| any given framing protocol, that provides a complete service to an | any given framing protocol, that provides a complete service to an | |||
| application. | application. | |||
| skipping to change at line 1296 ¶ | skipping to change at line 1296 ¶ | |||
| phase (Section 4.2.2). | phase (Section 4.2.2). | |||
| Candidate Protocol Stack: One Protocol Stack that can be used by an | Candidate Protocol Stack: One Protocol Stack that can be used by an | |||
| application for a Connection, for which there can be several | application for a Connection, for which there can be several | |||
| candidates. Candidate Protocol Stacks are identified during the | candidates. Candidate Protocol Stacks are identified during the | |||
| gathering phase (Section 4.2.1) and are started during the racing | gathering phase (Section 4.2.1) and are started during the racing | |||
| phase (Section 4.2.2). | phase (Section 4.2.2). | |||
| System Policy: The input from an operating system or other global | System Policy: The input from an operating system or other global | |||
| preferences that can constrain or influence how an implementation | preferences that can constrain or influence how an implementation | |||
| will gather candidate paths and Protocol Stacks (Section 4.2.1) | will gather Candidate Paths and Candidate Protocol Stacks | |||
| and race the candidates during establishment (Section 4.2.2). | (Section 4.2.1) and race the candidates during establishment | |||
| Specific aspects of the System Policy apply to either all | (Section 4.2.2). Specific aspects of the System Policy apply to | |||
| Connections or only certain Connections, depending on the runtime | either all Connections or only certain Connections, depending on | |||
| context and properties of the Connection. | the runtime context and properties of the Connection. | |||
| Cached State: The state and history that the implementation keeps | Cached State: The state and history that the implementation keeps | |||
| for each set of associated Endpoints that have been used | for each set of associated Endpoints that have been used | |||
| previously. This can include DNS results, TLS session state, | previously. This can include DNS results, TLS session state, | |||
| previous success and quality of transport protocols over certain | previous success and quality of transport protocols over certain | |||
| paths, as well as other information. This caching does not imply | paths, as well as other information. This caching does not imply | |||
| that the same decisions are necessarily made for subsequent | that the same decisions are necessarily made for subsequent | |||
| connections; rather, it means that cached state is used by a | connections; rather, it means that cached state is used by a | |||
| Transport Services Implementation to inform functions such as | Transport Services Implementation to inform functions such as | |||
| choosing the candidates to be raced, selecting appropriate | choosing the candidates to be raced, selecting appropriate | |||
| skipping to change at line 1446 ¶ | skipping to change at line 1446 ¶ | |||
| 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>. | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/info/rfc8174>. | |||
| 7.2. Informative References | 7.2. Informative References | |||
| [POSIX] "IEEE Standard for Information Technology -- Portable | [POSIX] "IEEE/Open Group Standard for Information Technology - | |||
| Operating System Interface (POSIX(R))", IEEE | Portable Operating System Interface (POSIX(TM)) Base | |||
| Std 1003.1-2008, DOI 10.1109/IEEESTD.2008.4694976, 2008, | Specifications, Issue 8", IEEE Std 1003.1-2024, | |||
| <https://ieeexplore.ieee.org/document/4694976>. | DOI 10.1109/IEEESTD.2024.10555529, 2024, | |||
| <https://ieeexplore.ieee.org/document/10555529>. | ||||
| [RFC5482] Eggert, L. and F. Gont, "TCP User Timeout Option", | [RFC5482] Eggert, L. and F. Gont, "TCP User Timeout Option", | |||
| RFC 5482, DOI 10.17487/RFC5482, March 2009, | RFC 5482, DOI 10.17487/RFC5482, March 2009, | |||
| <https://www.rfc-editor.org/info/rfc5482>. | <https://www.rfc-editor.org/info/rfc5482>. | |||
| [RFC6265] Barth, A., "HTTP State Management Mechanism", RFC 6265, | [RFC6265] Barth, A., "HTTP State Management Mechanism", RFC 6265, | |||
| DOI 10.17487/RFC6265, April 2011, | DOI 10.17487/RFC6265, April 2011, | |||
| <https://www.rfc-editor.org/info/rfc6265>. | <https://www.rfc-editor.org/info/rfc6265>. | |||
| [RFC7556] Anipko, D., Ed., "Multiple Provisioning Domain | [RFC7556] Anipko, D., Ed., "Multiple Provisioning Domain | |||
| End of changes. 3 change blocks. | ||||
| 11 lines changed or deleted | 12 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||