Re: [nvo3] Draft NVO3 WG Charter

Thomas Narten <narten@us.ibm.com> Fri, 17 February 2012 16:16 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8A321F8716 for <nvo3@ietfa.amsl.com>; Fri, 17 Feb 2012 08:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.163
X-Spam-Level:
X-Spam-Status: No, score=-109.163 tagged_above=-999 required=5 tests=[AWL=0.836, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 xmNryHh7VcOo for <nvo3@ietfa.amsl.com>; Fri, 17 Feb 2012 08:16:17 -0800 (PST)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id 81F5721F86DE for <nvo3@ietf.org>; Fri, 17 Feb 2012 08:16:17 -0800 (PST)
Received: from /spool/local by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <nvo3@ietf.org> from <narten@us.ibm.com>; Fri, 17 Feb 2012 09:16:16 -0700
Received: from d01dlp03.pok.ibm.com (9.56.224.17) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 17 Feb 2012 09:13:00 -0700
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id B2178C90054 for <nvo3@ietf.org>; Fri, 17 Feb 2012 11:12:55 -0500 (EST)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q1HGCowU202216 for <nvo3@ietf.org>; Fri, 17 Feb 2012 11:12:51 -0500
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q1HGCldc007243 for <nvo3@ietf.org>; Fri, 17 Feb 2012 09:12:47 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-227-26.mts.ibm.com [9.65.227.26]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q1HGCdA0006779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Feb 2012 09:12:39 -0700
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q1HGAfRq027981; Fri, 17 Feb 2012 11:10:41 -0500
Message-Id: <201202171610.q1HGAfRq027981@cichlid.raleigh.ibm.com>
To: John E Drake <jdrake@juniper.net>
In-reply-to: <5E893DB832F57341992548CDBB333163A55C70661A@EMBX01-HQ.jnpr.net>
References: <201202171451.q1HEptR3027370@cichlid.raleigh.ibm.com> <5E893DB832F57341992548CDBB333163A55C70661A@EMBX01-HQ.jnpr.net>
Comments: In-reply-to John E Drake <jdrake@juniper.net> message dated "Fri, 17 Feb 2012 07:00:50 -0800."
Date: Fri, 17 Feb 2012 11:10:40 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12021716-2398-0000-0000-00000453199E
Cc: Ronald Bonica <rbonica@juniper.net>, Nitin Bahadur <nitinb@juniper.net>, "nvo3@ietf.org" <nvo3@ietf.org>, Adrian Farrel <afarrel@juniper.net>
Subject: Re: [nvo3] Draft NVO3 WG Charter
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "L2 \"Network Virtualization Over l3\" overlay discussion list \(nvo3\)" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2012 16:16:18 -0000

John,

> This basically is a re-statement of what is done by L3/L2 VPNs.

I think this comment is a bit unfair. We had a session in Taipei where
this issue was discussed. The push for this is coming with support
from data center operators themselves, not from the VPN side (and the
"provider-provisioned" VPN side in particular, which is where both
L2VPN and L3VPN have historically worked from and what their current
charters continue to heavily emphasize is their starting point).

> It might be useful to do a gap analysis of these existing
>  technologies, in particular E-VPNs
>  (http://tools.ietf.org/html/draft-raggarwa-sajassi-l2vpn-evpn-04),
>  before asserting that something new is required.

I think it has been established that while existing technologies could
be made to work in data centers in a *theoretical* sense, the Taipei
session showed that there were operators who are not entirely happy
with that approach and wanted the IETF to pursuse what we are
proposing.

Thomas