hi, clarification: yes i said what's written below, but i think this is the first time the taps folks hear about it. so if that's fine with everyone, that's our plan - it seemed to us to be the most reasonable approach.
about adopting this separate document, it makes sense to me Sent from my iPhone > On 6. okt. 2016, at 10.22, Gorry Fairhurst <[email protected]> wrote: > > We have just submitted an updated copy of the UDP usage draft we have been > working on in TAPS. > > Specifically: > > (1) It omits the text for pass 2 and 3 that we now expect to be directly > incorporated in draft-ietf-taps-transport-usage. > Michael Welzl I think indicated that this text will be copied from rev > -usage-udp-02. > > (2) It contains small changes to the document text to allow this to be > publsihed as a separate document. The WG discussed whether such a document > could be adopted for publication as a pair with > draft-ietf-taps-transport-usage. The authors are now looking to the group to > know if the WG would like to adopt this and then what further work may be > needed. > > Best wishes, > > Tom & Gorry > > >> On 05/10/2016 21:46, [email protected] wrote: >> A new version of I-D, draft-fairhurst-taps-transports-usage-udp-03.txt >> has been successfully submitted by Godred Fairhurst and posted to the >> IETF repository. >> >> Name: draft-fairhurst-taps-transports-usage-udp >> Revision: 03 >> Title: Features of the User Datagram Protocol (UDP) and Lightweight >> UDP (UDP- Lite) Transport Protocols >> Document date: 2016-10-05 >> Group: Individual Submission >> Pages: 18 >> URL: >> https://www.ietf.org/internet-drafts/draft-fairhurst-taps-transports-usage-udp-03.txt >> Status: >> https://datatracker.ietf.org/doc/draft-fairhurst-taps-transports-usage-udp/ >> Htmlized: >> https://tools.ietf.org/html/draft-fairhurst-taps-transports-usage-udp-03 >> Diff: >> https://www.ietf.org/rfcdiff?url2=draft-fairhurst-taps-transports-usage-udp-03 >> >> Abstract: >> This document describes how the User Datagram Protocol (UDP) and the >> Lightweight User Datagram Protocol (UDP-Lite) transport protocols >> expose services to applications and how an application can configure >> and use the features offered by the transport service. The document >> is intended as a contribution to the Transport Services (TAPS) >> working group to assist in analysis of the UDP and UDP-Lite transport >> interface. >> >> >> >> >> Please note that it may take a couple of minutes from the time of submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> The IETF Secretariat > > _______________________________________________ > Taps mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/taps _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
