Re: [Taps] I-D Action: draft-ietf-taps-impl-16.txt

[Tommy Pauly <[e-mail]>]

One thing to note about BCP205 Implementation Status sections is that they are intended to be removed during publication as RFC. I’m not sure that’s what we’d want to do with the implementation draft, since it still might be a useful reference in the future?

Tommy

> On Jun 5, 2023, at 9:58 AM, Michael Welzl <[e-mail]> wrote:
> 
> Hi,
> 
> I have one very minor comment / question:
> 
> In his Genart review of the interface draft, Thomas Fossati wrote:
> 
>> I was curious about the implementation status but I couldn't find
>> further info.  If you happen to have implementations already, it'd be
>> nice to give them visibility in a BCP205 "Implementation Status"
>> section.
> 
> I believe that the implementation draft would be the right place for this, and we do have such a section there: appendix C.
> However, it’s not called a BCP205 “Implementation Status” section, but “Existing Implementations”.
> I believe that we had discussed this and decided for this title instead of “Implementation Status” for a reason, but I can’t remember that reason now…
> 
> If my memory fails me, and we should indeed rename this section, I figure that we can still do this during AUTH48 (and, perhaps, if that’s the case, then the RFC Editor will tell us) - so this is just a note to remember.
> 
> Cheers,
> Michael
> 
> 
>> On Jun 5, 2023, at 4:50 PM, Tommy Pauly <tpauly=[e-mail]> wrote:
>> 
>> Hi all,
>> 
>> draft-ietf-taps-impl-16 includes all changes from the directorate reviews. There are no more currently outstanding issues on the implementation document, so this should be ready to progress.
>> 
>> Thanks,
>> Tommy
>> 
>>> On Jun 5, 2023, at 7:48 AM, [e-mail] wrote:
>>> 
>>> 
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories. This Internet-Draft is a work item of the Transport Services
>>> (TAPS) WG of the IETF.
>>> 
>>> Title           : Implementing Interfaces to Transport Services
>>> Authors         : Anna Brunstrom
>>>                   Tommy Pauly
>>>                   Reese Enghardt
>>>                   Philipp S. Tiesel
>>>                   Michael Welzl
>>> Filename        : draft-ietf-taps-impl-16.txt
>>> Pages           : 55
>>> Date            : 2023-06-05
>>> 
>>> Abstract:
>>> The Transport Services system enables applications to use transport
>>> protocols flexibly for network communication and defines a protocol-
>>> independent Transport Services Application Programming Interface
>>> (API) that is based on an asynchronous, event-driven interaction
>>> pattern.  This document serves as a guide to implementing such a
>>> system.
>>> 
>>> The IETF datatracker status page for this Internet-Draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-taps-impl/
>>> 
>>> There is also an HTML version available at:
>>> https://www.ietf.org/archive/id/draft-ietf-taps-impl-16.html
>>> 
>>> A diff from the previous version is available at:
>>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-taps-impl-16
>>> 
>>> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>>> 
>>> 
>>> _______________________________________________
>>> Taps mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/taps
>> 
>> _______________________________________________
>> Taps mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/taps
> 
> _______________________________________________
> Taps mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/taps