Re: Questions: WG Review: Network Virtualization Overlays (nvo3) - 23-Apr-2012 update

Stewart Bryant <stbryant@cisco.com> Tue, 24 April 2012 21:28 UTC

Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBCDF21F863E; Tue, 24 Apr 2012 14:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.461
X-Spam-Level:
X-Spam-Status: No, score=-110.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EoRFnkruBTNy; Tue, 24 Apr 2012 14:28:52 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 89CA721F863D; Tue, 24 Apr 2012 14:28:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=972; q=dns/txt; s=iport; t=1335302932; x=1336512532; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=6LocvEx+dt3WIuEf76yl9r2IHISh828YxSKUgIPIM28=; b=AYVu23i70CIG0Nw8aGV6h+rBmIo/8gBF5CtHEKqS5UDFR7ggWu1+VX25 xj+wtnwqW7CAwkqkIlK5yKJCnNe/Yq5GVZEQN+DZrC1K62mwg0HJt3PUt sN2oy/UhYN71zoDqbEXDXnMEVXvoFLl3jKzqhSH9dlimGkmO3MIZA1qX4 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EABAal0+Q/khR/2dsb2JhbABErkyDLYEHggkBAQEEEgECI0EQCxgJJQ8CRhMBBwEBHodtmiyDQhCcW41NgyUElXqOVYECZ4JqgVs
X-IronPort-AV: E=Sophos;i="4.75,474,1330905600"; d="scan'208";a="136125369"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 24 Apr 2012 21:28:50 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q3OLSjVo031747; Tue, 24 Apr 2012 21:28:50 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q3OLSh7G016741; Tue, 24 Apr 2012 22:28:44 +0100 (BST)
Message-ID: <4F971B0B.707@cisco.com>
Date: Tue, 24 Apr 2012 22:28:43 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: Questions: WG Review: Network Virtualization Overlays (nvo3) - 23-Apr-2012 update
References: <03fe01cd2255$853351f0$8f99f5d0$@olddog.co.uk>
In-Reply-To: <03fe01cd2255$853351f0$8f99f5d0$@olddog.co.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: nvo3@ietf.org, iesg@ietf.org, 'IETF Discussion' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 21:28:52 -0000

On 24/04/2012 21:04, Adrian Farrel wrote:
>
> NVO3 will consider approaches to multi-tenancy that reside at the
> network layer rather than using traditional isolation mechanisms
> I know we have been dancing around this and there is a lot of paranoia. It is
> clear that we mean that no IETF technology will be excluded from consideration a
> priori. This may be sensitive because the PWE3 charter (which had to handle a
> similar question) explicitly called out IP and MPLS. I can't think of a better
> way of saying what the text says other than "network layer" but perhaps, for the
> avoidance of doubt, Stewart could put an email in the archive that says "I
> confirm that the phrase 'network layer' in the context of the NVO3 charter does
> not exclude MPLS." Then (hopefully) we can all move along and do the real work
> :-)

For the avoidance of doubt, in the context of the NVO3 charter, the term
'network layer' does not exclude MPLS.

Stewart