Re: [v6ops] Operational Consensus on deployment

Ray Hunter <v6ops@globis.net> Sat, 16 August 2014 11:37 UTC

Return-Path: <v6ops@globis.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94A3D1A8769 for <v6ops@ietfa.amsl.com>; Sat, 16 Aug 2014 04:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level:
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] 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 k-K7f6-VL13I for <v6ops@ietfa.amsl.com>; Sat, 16 Aug 2014 04:37:21 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id B01631A8762 for <v6ops@ietf.org>; Sat, 16 Aug 2014 04:37:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id DD32387153B; Sat, 16 Aug 2014 13:37:20 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sXpYKfcMN0wN; Sat, 16 Aug 2014 13:37:20 +0200 (CEST)
Received: from Rays-iMac.local (unknown [IPv6:2001:470:1f15:73a:2c3d:d324:45ec:29d7]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id A3DA287153A; Sat, 16 Aug 2014 13:37:20 +0200 (CEST)
Message-ID: <53EF4255.80908@globis.net>
Date: Sat, 16 Aug 2014 13:36:53 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Tore Anderson <tore@fud.no>
References: <256EAE0B-5C11-42C7-BCA1-CEC7EE6713A7@cisco.com> <53DFD634.4020304@fud.no> <53E0C548.9050706@fud.no>
In-Reply-To: <53E0C548.9050706@fud.no>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/jMArCo2cYgkwDP84ojE8Ay7k_fY
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Operational Consensus on deployment
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Aug 2014 11:37:23 -0000


Tore Anderson wrote:
> * Tore Anderson
>
>> Eerily good timing... I just started working on this again today, as it
>> happens. What I'm looking at now is two drafts, the one that's already
>> there for a single-translation network-only implementation, plus another
>> one describing an extension very similar to 464XLAT that would allow
>> NAT-incompatible and/or IPv4-only applications to be used in an
>> otherwise IPv6-only data centre.
>
> Here you go:
>
> http://htmlpreview.github.io/?https://github.com/toreanderson/ietf/blob/master/siit-dc.html
> http://htmlpreview.github.io/?https://github.com/toreanderson/ietf/blob/master/siit-dc-2xlat.html
>
> XML sources and .txt formats at https://github.com/toreanderson/ietf/.
>
> They're work in progress obviously, I haven't uploaded them to the I-D
> repository yet. It would be nice if you and Lee could have a chat with
> the sunset4 chairs and agree on which WG is the most appropriate first.
> (I have no particular preference, but I want it done Right.)
>
> Comments, criticisms, suggestions, pull requests would be very welcome!
>
> Tore
I see these conceptually as partner documents to 464xlat (on the server 
side, rather than the eyeballs side). I therefore think it would be 
useful to bring these documents into v6ops as I-D's, especially if 
real-world operational deployment experience could be included.

-- 
Regards,
RayH