rfc9621v7.txt | rfc9621.txt | |||
---|---|---|---|---|
skipping to change at line 616 ¶ | skipping to change at line 616 ¶ | |||
robustness to failure, or some other metric. | robustness to failure, or some other metric. | |||
Beyond these, if the Transport Services API remains the same over | Beyond these, if the Transport Services API remains the same over | |||
time, new protocols and features can be added to the Transport | time, new protocols and features can be added to the Transport | |||
Services Implementation without requiring changes in applications for | Services Implementation without requiring changes in applications for | |||
adoption. Similarly, this can provide a common basis for utilizing | adoption. Similarly, this can provide a common basis for utilizing | |||
information about a network path or interface, enabling evolution | information about a network path or interface, enabling evolution | |||
below the transport layer. | below the transport layer. | |||
The normative requirements described in this section allow Transport | The normative requirements described in this section allow Transport | |||
Services APIs and the Transport Services Implementations to provide | Services APIs and Transport Services Implementations to provide this | |||
this functionality without causing incompatibility or introducing | functionality without causing incompatibility or introducing security | |||
security vulnerabilities. | vulnerabilities. | |||
3.1. Provide Common APIs for Common Features | 3.1. Provide Common APIs for Common Features | |||
Any functionality that is common across multiple transport protocols | Any functionality that is common across multiple transport protocols | |||
SHOULD be made accessible through a unified set of calls using the | SHOULD be made accessible through a unified set of calls using the | |||
Transport Services API. As a baseline, any Transport Services API | Transport Services API. As a baseline, any Transport Services API | |||
SHOULD allow access to the minimal set of features offered by | SHOULD allow access to the minimal set of features offered by | |||
transport protocols [RFC8923]. If that minimal set is updated or | transport protocols [RFC8923]. If that minimal set is updated or | |||
expanded in the future, the Transport Services API ought to be | expanded in the future, the Transport Services API ought to be | |||
extended to match. | extended to match. | |||
End of changes. 1 change blocks. | ||||
3 lines changed or deleted | 3 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |