Re: [nvo3] Draft NVO3 WG Charter

John E Drake <jdrake@juniper.net> Fri, 17 February 2012 18:37 UTC

Return-Path: <jdrake@juniper.net>
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 A682421E8028 for <nvo3@ietfa.amsl.com>; Fri, 17 Feb 2012 10:37:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.766
X-Spam-Level:
X-Spam-Status: No, score=-4.766 tagged_above=-999 required=5 tests=[AWL=1.833, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 1altuHQmwFqp for <nvo3@ietfa.amsl.com>; Fri, 17 Feb 2012 10:37:19 -0800 (PST)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 7867221E8015 for <nvo3@ietf.org>; Fri, 17 Feb 2012 10:37:19 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKTz6eWvH0FJD4IPMlTXajPMhvP4WAZFEf@postini.com; Fri, 17 Feb 2012 10:37:19 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Fri, 17 Feb 2012 10:34:57 -0800
From: John E Drake <jdrake@juniper.net>
To: "robert@raszuk.net" <robert@raszuk.net>
Date: Fri, 17 Feb 2012 10:34:55 -0800
Thread-Topic: [nvo3] Draft NVO3 WG Charter
Thread-Index: AcztnQWOSy7AVmwpS5iiaJYPMdZAxAABX7Pw
Message-ID: <5E893DB832F57341992548CDBB333163A55C914A45@EMBX01-HQ.jnpr.net>
References: <201202171451.q1HEptR3027370@cichlid.raleigh.ibm.com>, <5E893DB832F57341992548CDBB333163A55C70661A@EMBX01-HQ.jnpr.net> <5E613872-0E27-46D2-8097-B31E7F0F37C5@mimectl> <5E893DB832F57341992548CDBB333163A55C70669D@EMBX01-HQ.jnpr.net> <4F3E851F.6060604@raszuk.net> <5E893DB832F57341992548CDBB333163A55C9148D8@EMBX01-HQ.jnpr.net> <4F3E898C.3000605@raszuk.net> <5E893DB832F57341992548CDBB333163A55C914924@EMBX01-HQ.jnpr.net> <4F3E9405.8070602@raszuk.net>
In-Reply-To: <4F3E9405.8070602@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-exclaimer-md-config: e4081efb-6d29-443c-8708-750833aec629
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "narten@us.ibm.com" <narten@us.ibm.com>, Ronald Bonica <rbonica@juniper.net>, "david.black@emc.com" <david.black@emc.com>, "nvo3@ietf.org" <nvo3@ietf.org>, Adrian Farrel <afarrel@juniper.net>, Nitin Bahadur <nitinb@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 18:37:20 -0000

Robert,

Although we might disagree wrt the applicability of certain technologies, such as LISP, I think you are reinforcing my point that there are lots of existing IETF technologies that should be evaluated.

Thanks,

John 

> -----Original Message-----
> From: Robert Raszuk [mailto:robert@raszuk.net]
> Sent: Friday, February 17, 2012 9:53 AM
> To: John E Drake
> Cc: narten@us.ibm.com; Ronald Bonica; david.black@emc.com;
> nvo3@ietf.org; Adrian Farrel; Nitin Bahadur
> Subject: Re: [nvo3] Draft NVO3 WG Charter
> 
> Hi John,
> 
> > Btw, are you aware of the VM mobility
> > draft:http://datatracker.ietf.org/doc/draft-raggarwa-data-center-
> mobility/?
> 
> The most interesting there is the section 6.2 attempting to propose
> ways
> to avoid inter-dc triangular routing after VM migration.
> 
> However I am not keen on host routes injection even in the limited
> radius (which may not be possible in hybrid cloud cases) nor NHRP
> proposal from section 6.2.3.
> 
> IMHO much better class of solutions are already documented in LISP
> and/or ILNP documents. They solve the same problem in much more elegant
> way. Note that those can be deployed within one's administration domain
> boundaries only or extend beyond given domain (for example to given
> domain's customers).
> 
> Many thx,
> R.