Subject: [Taps] Fwd: New Version Notification for draft-gjessing-taps-minset-00.txt

From: Michael Welzl <[email-masked]>
Date: Fri, 26 Jun 2015 09:21:40 +0200

Dear all,

This is a very first stab at a draft addressing the charter's second item - the minimal set of transport services that end systems should support.

It is based on version 4 of draft-ietf-taps-transports, so the list of features / components is not up to date - but that's not really the main point of the document for now anyway:
it's about showing how the number of exposed services *could* be reduced. Our hope is that, by sketching the possible destination of our journey, this helps the current discussion of the first document.

Cheers,
Michael

> Begin forwarded message:
> 
> From: <[email-masked]>
> Subject: New Version Notification for draft-gjessing-taps-minset-00.txt
> Date: 22 Jun 2015 14:37:43 CEST
> To: Michael Welzl <[email-masked]>, Stein Gjessing <[email-masked]>, Stein Gjessing <[email-masked]>, Michael Welzl <[email-masked]>
> Resent-From: <[email-masked]>
> 
> 
> A new version of I-D, draft-gjessing-taps-minset-00.txt
> has been successfully submitted by Michael Welzl and posted to the
> IETF repository.
> 
> Name:		draft-gjessing-taps-minset
> Revision:	00
> Title:		A Minimal Set of Transport Services for TAPS Systems
> Document date:	2015-06-22
> Group:		Individual Submission
> Pages:		10
> URL:            https://www.ietf.org/internet-drafts/draft-gjessing-taps-minset-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-gjessing-taps-minset/
> Htmlized:       https://tools.ietf.org/html/draft-gjessing-taps-minset-00
> 
> 
> Abstract:
>   This draft will eventually recommend a minimal set of IETF Transport
>   Services offered by end systems supporting TAPS, and give guidance on
>   choosing among the available mechanisms and protocols.  As a starting
>   point for discussion, it currently only gives an overview of some
>   ways to categorize the set of transport services in the first TAPS
>   document (version 4: draft-ietf-taps-transports-04), assuming that
>   the eventual minimal set of transport services will be based on a
>   similar form of categorization.
> 
> 
> 
> 
> 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
>