Subject: [Stackevo] Fwd: New Version Notification for draft-trammell-stackevo-explicit-coop-00.txt

From: Brian Trammell <[email-masked]>
Date: Thu, 24 Sep 2015 00:23:15 +0200

Greetings, all,

I've (finally) just posted draft-trammell-stackevo-explicit-coop, which we discussed in Prague as a potential IAB document to discuss the architectural aspects of the space of approaches to implement the principle of explicit cooperation using (UDP-based) encapsulations. It follows from draft-trammell-stackevo-newtea, and incorporates some of the insights that have come out of discussions about SPUD, but neutral to the actual design and implementation of any protocol to provide explicit cooperation.

Cheers,

Brian

> Begin forwarded message:
> 
> From: [email-masked]
> Subject: New Version Notification for draft-trammell-stackevo-explicit-coop-00.txt
> Date: 24 Sep 2015 00:11:23 CEST
> To: "Brian Trammell" <[email-masked]>, "Brian Trammell" <[email-masked]>
> 
> 
> A new version of I-D, draft-trammell-stackevo-explicit-coop-00.txt
> has been successfully submitted by Brian Trammell and posted to the
> IETF repository.
> 
> Name:		draft-trammell-stackevo-explicit-coop
> Revision:	00
> Title:		Architectural Considerations for Transport Evolution with Explicit Path Cooperation
> Document date:	2015-09-23
> Group:		Individual Submission
> Pages:		12
> URL:            https://www.ietf.org/internet-drafts/draft-trammell-stackevo-explicit-coop-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-trammell-stackevo-explicit-coop/
> Htmlized:       https://tools.ietf.org/html/draft-trammell-stackevo-explicit-coop-00
> 
> 
> Abstract:
>   The IAB Stack Evolution in a Middlebox Internet (SEMI) workshop in
>   Zurich in January 2015 and the follow-up Substrate Protocol for User
>   Datagrams (SPUD) BoF session at the IETF 92 meeting in Dallas in
>   March 2015 identified the potential need for a UDP-based
>   encapsulation to allow explicit cooperation with middleboxes while
>   using encryption at the transport layer and above to protect user
>   payload and metadata from inspection and interference.  This document
>   proposes a set of architectural considerations for such approaches.
> 
> 
> 
> 
> 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
>