[Stackevo] Fwd: New Version Notification for draft-trammell-stackevo-newtea-01.txt

Brian Trammell <ietf@trammell.ch> Thu, 07 May 2015 15:42 UTC

Return-Path: <ietf@trammell.ch>
X-Original-To: stackevo@ietfa.amsl.com
Delivered-To: stackevo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 718451AC3A6 for <stackevo@ietfa.amsl.com>; Thu, 7 May 2015 08:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xUK1pZB7kkTn for <stackevo@ietfa.amsl.com>; Thu, 7 May 2015 08:42:03 -0700 (PDT)
Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id 84A9F1AC434 for <stackevo@iab.org>; Thu, 7 May 2015 08:42:03 -0700 (PDT)
Received: from [192.168.157.78] (unknown [74.125.57.121]) by trammell.ch (Postfix) with ESMTPSA id 76B871A003D for <stackevo@iab.org>; Thu, 7 May 2015 17:42:02 +0200 (CEST)
From: Brian Trammell <ietf@trammell.ch>
X-Pgp-Agent: GPGMail 2.5b6
Content-Type: multipart/signed; boundary="Apple-Mail=_EAD88167-C3CD-4513-AF50-2390CED6674C"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Date: Thu, 07 May 2015 16:42:01 +0100
References: <20150507153835.2974.90599.idtracker@ietfa.amsl.com>
To: stackevo@iab.org
Message-Id: <40EA1B24-A872-4113-B359-2AE6F462D49E@trammell.ch>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/stackevo/g3l89yOFL01y4KiV6YsNoGqoR1I>
Subject: [Stackevo] Fwd: New Version Notification for draft-trammell-stackevo-newtea-01.txt
X-BeenThere: stackevo@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IP Stack Evolution Program Mailing List <stackevo.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/stackevo>, <mailto:stackevo-request@iab.org?subject=unsubscribe>
List-Archive: <http://www.iab.org/mail-archive/web/stackevo/>
List-Post: <mailto:stackevo@iab.org>
List-Help: <mailto:stackevo-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/stackevo>, <mailto:stackevo-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2015 15:42:05 -0000

Greetings, all,

I've dumped a few more thoughts post-Dallas (and mid-IETF/IAB retreat) on encapsulation for transport evolution; comments welcome (especially along the lines of "does this make sense, and does it make sense to continue along these lines?")

thanks, cheers,

Brian

> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-trammell-stackevo-newtea-01.txt
> Date: 7 May 2015 16:38:35 BST
> To: "Brian Trammell" <ietf@trammell.ch>, "Brian Trammell" <ietf@trammell.ch>
> 
> 
> A new version of I-D, draft-trammell-stackevo-newtea-01.txt
> has been successfully submitted by Brian Trammell and posted to the
> IETF repository.
> 
> Name:		draft-trammell-stackevo-newtea
> Revision:	01
> Title:		Thoughts a New Transport Encapsulation Architecture
> Document date:	2015-05-07
> Group:		Individual Submission
> Pages:		10
> URL:            https://www.ietf.org/internet-drafts/draft-trammell-stackevo-newtea-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-trammell-stackevo-newtea/
> Htmlized:       https://tools.ietf.org/html/draft-trammell-stackevo-newtea-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-trammell-stackevo-newtea-01
> 
> Abstract:
>   This document explores architectural considerations for using
>   encapsulation in support of stack evolution and new transport
>   protocol deployment in an increasingly encrypted Internet.  These
>   architectural considerations are based on an idealized architecture
>   where all interactions among applications, endpoints, and the path
>   occur explicitly, with this cooperation enforced cryptographically.
>   This idealized architecture is then lensed through the state of
>   devices in the present Internet and how they would impair the
>   deployability of such an architecture, in order to support an
>   incremental deployment of this approach.
> 
> 
> 
> 
> 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
>