Dear Tommy, Thanks a lot for your comments! Very helpful - and painful too :-) to fix the messy style (lower case / upper case / ..), which originated from me just copy+pasting it from the various source RFCs… I should have fixed this long ago, I think it looks much better now - so thanks indeed for making me do this!
About MPTCP, that’s also done (mention that everything applies to both - I actually did say so for an earlier “pass” but now I added it for pass 3 too). Cheers, Michael > On Jun 4, 2017, at 10:40 PM, Tommy Pauly <[email protected]> wrote: > > Agreed, these both look ready to go! Just a few minor typographical nits > below; these could be cleaned up later. > > Best, > Tommy > > Usage Draft: > > - In Section 3.1, the style of most items is lower case without underscores; > however there are "USER TIMEOUT event:” and "ERROR_REPORT event:”, and then > the rest of the list is in camel-case like "Type-of-Service:”. These should > probably be cleaned up. Same for other lists. > > - In Section 5.1, would it be useful to explicitly mention MPTCP for the > common elements with TCP, or simply mention that anything that applies to TCP > also applies to MPTCP? > > UDP Usage Draft: > > - Section 3 has some mismatched parenthetical clauses: > (in and how the > transport is used (based on abstract API descriptions, where they are > available). > - Section 3.1 has a sentence that doesn’t parse well: > > should be able to create receive, source and > destination ports and addresses > > - Also in Section 3.1, it seems that there should be a comma before the “or > by” rather than a full stop. > > 1. bind(): A bind operation sets the local port, either > implicitly, triggered by a "sendto" operation on an unbound, > unconnected socket using an ephemeral port. Or by an explicit > "bind" to use a configured or well-known port. > > - Section 3.1, "ERROR_REPORT The ERROR_REPORT” is missing the colon that all > other items have. Same for SET_MIN_COVERAGE in section 3.2 > > >> On May 30, 2017, at 3:14 AM, Brian Trammell (IETF) <[email protected] >> <mailto:[email protected]>> wrote: >> >> hi Aaron, all, >> >> I've read these, and IMO they're ready for publication. Many thanks to the >> authors for the impressive amount of work that went into them! >> >> Cheers, >> >> Brian >> >> >>> On 29 May 2017, at 18:30, Aaron Falk <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Dear TAPS working group: >>> >>> The authors have indicated the two drafts below are complete and are ready >>> for a final working group review. WGLC starts today and will be three >>> weeks, concluding June 19. Send comments, including an indication that the >>> docs are ready for publication, to the working group list. >>> >>> • On the Usage of Transport Features Provided by IETF Transport >>> Protocols >>> • Features of the User Datagram Protocol (UDP) and Lightweight UDP >>> (UDP- Lite) Transport Protocols >>> —aaron >>> >>> _______________________________________________ >>> Taps mailing list >>> [email protected] <mailto:[email protected]> >>> https://www.ietf.org/mailman/listinfo/taps >> >> _______________________________________________ >> Taps mailing list >> [email protected] <mailto:[email protected]> >> https://www.ietf.org/mailman/listinfo/taps > > _______________________________________________ > Taps mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/taps
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
