HI, I gave this comment also to version 03, but I will then repeat it here again :-):
I do think that it is overkill to say that TCP implements the following Transport Protocol Components: o ordered delivery for each byte stream o stream-oriented delivery in a single stream Given that one TCP connection is able to serve one and only one byte stream, I think that it would suffice to give one of these statements. Preferably the latter one. BR, Karen >-----Original Message----- >From: Taps [mailto:taps-boun...@ietf.org] On Behalf Of Brian Trammell >Sent: Tuesday, May 26, 2015 3:26 PM >To: taps WG >Subject: Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt > >Greetings, all, > >We've submitted revision -04 of taps-transports, which includes: > >(1) a new section on HTTP as a pseudotransport over TCP (thanks, Dragana >Damjanovic!) > >(2) a new section on NORM (thanks, Brian Adamson!) > >(3) frontmatter in Section 4 normalizing and categorizing the transport >protocol components; please review this and suggest necessary or useful >changes for using this as background for selecting taps features. > >Next up is completing the outstanding sections on transports and transport- >like things, of which we have four: > >3.2 MP-TCP >3.7 RTP >3.9 TLS/DTLS pseudotransport >3.11 WebSockets > >We hope to get an -05 with text for these out in the next couple of weeks, >and will follow up with contributors for each of these sections shortly. > >Thanks, cheers, > >Brian (for the editors of taps-transports) > >> On 26 May 2015, at 14:41, internet-dra...@ietf.org wrote: >> >> >> A New Internet-Draft is available from the on-line Internet-Drafts >directories. >> This draft is a work item of the Transport Services Working Group of the >IETF. >> >> Title : Services provided by IETF transport protocols and congestion >control mechanisms >> Authors : Godred Fairhurst >> Brian Trammell >> Mirja Kuehlewind >> Filename : draft-ietf-taps-transports-04.txt >> Pages : 35 >> Date : 2015-05-26 >> >> Abstract: >> This document describes services provided by existing IETF protocols >> and congestion control mechanisms. It is designed to help >> application and network stack programmers and to inform the work of >> the IETF TAPS Working Group. >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-taps-transports/ >> >> There's also a htmlized version available at: >> https://tools.ietf.org/html/draft-ietf-taps-transports-04 >> >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=draft-ietf-taps-transports-04 >> >> >> 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. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> Taps mailing list >> Taps@ietf.org >> https://www.ietf.org/mailman/listinfo/taps _______________________________________________ Taps mailing list Taps@ietf.org https://www.ietf.org/mailman/listinfo/taps
