Re: [v6ops] State of play as of today

Mark Smith <markzzzsmith@gmail.com> Fri, 02 October 2015 00:21 UTC

Return-Path: <markzzzsmith@gmail.com>
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 F2D061A90DC for <v6ops@ietfa.amsl.com>; Thu, 1 Oct 2015 17:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, SPF_PASS=-0.001] autolearn=no
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 Q2FrrM6Wa77M for <v6ops@ietfa.amsl.com>; Thu, 1 Oct 2015 17:21:07 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89B421A90DB for <v6ops@ietf.org>; Thu, 1 Oct 2015 17:21:07 -0700 (PDT)
Received: by vkgd64 with SMTP id d64so51088999vkg.0 for <v6ops@ietf.org>; Thu, 01 Oct 2015 17:21:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=aadgtDZf7NX+VDKG1modffmjCaXw+H5eUcaKiyXDvSE=; b=QcODUSWIrFeB0OjpB9Y8WcdWHebhdhINXrXl87f9lzQfl8sGt9KcR3ikVsPLTZH90N lAYhwgQ/jyLVDDIOkHAfyELgcLCFNOCIiIAOwZCJUqr9N216PwzrewZ+GxGH1fP0Q0G2 ZBHkv4bVJIUfWzhRcjUHKwwpLXzxje54d6P1qDzFSmAWDaIM4exaOmFWiYHHKrF6CWhu BMrf22HIvuB3IBC9BnYpcavL4mnhyPR2invEVF8KvqjGBEjkdpR2tcjqhTblfC9G+Io5 yGchhgKQLm/79ZSCd/TTfDN31NiIq8d8i82rghBK2sXpHSFMmB9o5QATm4Xm7jd6lDzV aeYA==
X-Received: by 10.31.9.81 with SMTP id 78mr7833090vkj.10.1443745266680; Thu, 01 Oct 2015 17:21:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.77.16 with HTTP; Thu, 1 Oct 2015 17:20:37 -0700 (PDT)
In-Reply-To: <560DBA24.6050206@gmail.com>
References: <71893E8D-913C-4F12-B159-4E522861A0E4@cisco.com> <75B6FA9F576969419E42BECB86CB1B891690C2BE@xmb-rcd-x06.cisco.com> <41497FF1-E7F3-4A4C-8434-D9BD54E152B6@cisco.com> <560DBA24.6050206@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 02 Oct 2015 10:20:37 +1000
Message-ID: <CAO42Z2zfBqiBqrLEK8vVxmn=E_9SauMVLT-9kMi+00-VCo=uWw@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/2g03VRTD2LxP1GSVvGHEs_r58Fg>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] State of play as of today
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 02 Oct 2015 00:21:09 -0000

Hi,

On 2 October 2015 at 08:56, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

<snip>

>>>  Certainly, this work could be discussed including the fact whether the consensus is to remain within the 64-bit boundary between the interface-id vs. not for any IPv6 addressing.
>
> I would strongly suggest discussing draft-smith-enhance-vne-with-ipv6 at
> the same time.
>

To save people a bit of time, I did the following presentation on that
draft at the AusNOG 2014 conference:

"Network Virtualisation: The Killer App for IPv6?"
http://www.slideshare.net/MarkSmith214/nvtkaipv6-50785685


Tom asked me to review his ILA draft a while back. In the context of
both his and my drafts, and having had some further time to think
about them, I think there might be two different but related problems
being considered:

- network virtualization, which I think might actually be more
accurately described as "network emulation"

- virtual machine / process portability across physical machines and
grouping of them together so they share a prefix for policy and other
reasons


My draft was purely focussed on the first problem, although it
inherently addresses the second. From memory, I think Tom's was
specifically addressing both of the problems.

The reason I've come to realise there are probably two different
problems to consider is that one of the fundamental differences
between what I proposed (and what other network
virtualization/emulation methods propose) and what Tom proposed is
that in his model, the hosts within the virtual networks have to have
IPv6 addresses that are structured to suit the operation of the
underlay network. This is easy or easier to achieve when the operator
of both the underlay and overlay networks is the same
entity/organisation.

I think that difference is fairly significant from the point of view
of trying to perform network emulation successfully. It seems to me
that if you're emulating a network, then your fundamental goal is that
the emulation of the network should be as transparent as possible to
the hosts using the emulated network, which includes allowing them to
use what ever addressing / addressing structure they'd like.

I think Tom's proposal is a good solution to the second problem,
however I wouldn't see it as a complete network emulation solution
because of its client host addressing requirements. I do think there
is a need for solutions to both types of "network virtualization".


Regards,
Mark.