On the Usage of Transport Features Provided by IETF Transport Protocols
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: The IESG <firstname.lastname@example.org>, Zaheduzzaman.Sarker@ericsson.com, email@example.com, firstname.lastname@example.org, email@example.com, Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>, firstname.lastname@example.org, email@example.com Subject: Document Action: 'On the Usage of Transport Features Provided by IETF Transport Protocols' to Informational RFC (draft-ietf-taps-transports-usage-09.txt) The IESG has approved the following document: - 'On the Usage of Transport Features Provided by IETF Transport Protocols' (draft-ietf-taps-transports-usage-09.txt) as Informational RFC This document is the product of the Transport Services Working Group. The IESG contact persons are Mirja Kühlewind and Spencer Dawkins. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-taps-transports-usage/
Technical Summary This document describes well established function calls as "primitives" that any program can use to get automated transport services from TCP, MP-TCP, SCTP, LEDBAT, UDP and UDP-lite protocols. This description gives very good information about the services provided by the protocols as defined in the RFC series. Further it describes the 3 pass process the working group followed to derive the transport features. Overall this document serves as a useful source of information for users of using transport services. Working Group Summary There were discussions on what protocols the document should cover, especially for inclusion of secure protocols such as TLS and DTLS. This was well communicated with respective working groups. As at that time the TAPS working group lacked security protocol expertise, the consensus was to keep those out of the scope of the document. When this document was in the working group, TAPS was explicitly not chartered to perform detailed analysis of the security aspects of transport protocols. Document Quality As this document describes primitives based on what is already available in standards- track RFCs for the corresponding transport protocols, it was straightforward to get consensus on the primitives. All versions of this document got a fair amount of discussion in the mailing list, were well reviewed, and got positive feedback in working group last call. Personnel The document shepherd is Zaheduzzaman Sarker. The responsible Area Director is Spencer Dawkins.