Re: [Ila] Second round draft charter
Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 22 February 2018 12:55 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ila@ietfa.amsl.com
Delivered-To: ila@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A681B12EA87 for <ila@ietfa.amsl.com>; Thu, 22 Feb 2018 04:55:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.622
X-Spam-Level:
X-Spam-Status: No, score=-2.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, T_FREEMAIL_DOC_PDF=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 RbCnALlSs0ba for <ila@ietfa.amsl.com>; Thu, 22 Feb 2018 04:55:13 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63E4812EAAB for <ila@ietf.org>; Thu, 22 Feb 2018 04:55:07 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w1MCt431011769; Thu, 22 Feb 2018 13:55:04 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 462A7202BDE; Thu, 22 Feb 2018 13:55:04 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id CB949203011; Thu, 22 Feb 2018 13:55:03 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id w1MCt2Zq029672; Thu, 22 Feb 2018 13:55:03 +0100
To: Tom Herbert <tom@quantonium.net>
Cc: ila@ietf.org
References: <CAPDqMeqgk2WtkfCkyeYduGuawWL9OuSaQ3vH8BYoTAu2UiXxaQ@mail.gmail.com> <25B4902B1192E84696414485F572685413540524@SJCEML521-MBB.china.huawei.com> <35f86e2e-9cb6-adb3-f26e-118d7e387afa@gmail.com> <CAPDqMerjpCaagP1tmt3yWscNcjt_oKjz+w1p_kWBApEZAMbmaA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <d5b39db9-7646-a339-8e7c-bec6b4fc4df5@gmail.com>
Date: Thu, 22 Feb 2018 13:55:02 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAPDqMerjpCaagP1tmt3yWscNcjt_oKjz+w1p_kWBApEZAMbmaA@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------4DBA99AB595AF596733DD3E9"
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/wn3HACUcwBeE_MSlRRgjANrfLY0>
Subject: Re: [Ila] Second round draft charter
X-BeenThere: ila@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Identifier Locator Addressing <ila.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ila>, <mailto:ila-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ila/>
List-Post: <mailto:ila@ietf.org>
List-Help: <mailto:ila-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ila>, <mailto:ila-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2018 12:55:16 -0000
Le 15/02/2018 à 18:27, Tom Herbert a écrit : > On Thu, Feb 15, 2018 at 4:39 AM, Alexandre Petrescu > <alexandre.petrescu@gmail.com> wrote: >> >> >> Le 09/02/2018 à 02:28, Uma Chunduri a écrit : >>> >>> Hi Tom, >>> >>> Below draft looks fine as a starting point. >>> >>> Few comments in-line [Uma]: >>> >>> -- >>> >>> Uma C. >>> >>> *From:*ila [mailto:ila-bounces@ietf.org] *On Behalf Of *Tom Herbert >>> *Sent:* Thursday, February 08, 2018 4:04 PM >>> *To:* ila@ietf.org; Bogineni, Kalyani >>> <kalyani.bogineni@verizonwireless.com> >>> *Subject:* [Ila] Second round draft charter >>> >>> Hello, >>> >>> I Incorporated feedback from the first draft including replacing >>> "translation" with "transformation". Aldo, incorporated some of the language >>> from the BOF description. >>> >>> Please comment! >>> >>> Thanks, >>> >>> Tom >>> >>> ------ >>> >>> Identifier-Locator Addressing (ILA) is a protocol to implement transparent >>> network overlays without encapsulation. It addresses the need for network >>> overlays in virtualization and mobility that are efficient, lightweight, >>> performant, scalable, secure, provide seamless mobility, leverage and >>> encourage use of IPv6, provide strong privacy, are interoperable with >>> existing infrastructure, applicable to a variety of use cases, and have >>> simplified control and management. >>> >>> The use cases of ILA include mobile networks, datacenter virtualization, >>> and network virtualization. >>> >>> *[Uma]: Can you expand mobile networks term here. I hope you meant, >>> cellular and wi-fi networks or anything else? >> >> >> Side-note, at IETF a 'Mobile Network' is a network that moves, per RFC3753: >> >>> Mobile network >>> >>> An entire network, moving as a unit, which dynamically changes its >>> point of attachment to the Internet and thus its reachability in >>> the topology. The mobile network is composed of one or more IP- >>> subnets and is connected to the global Internet via one or more >>> Mobile Routers (MR). The internal configuration of the mobile >>> network is assumed to be relatively stable with respect to the MR. >> >> >> For example, such a mobile network is what a user generates when s/he >> tethers a smartphone ('tethering'). >> >> On another hand, a 'mobile network' is what many people call in current >> conversation, including IETF WG email lists like v6ops, a 'cellular >> network'. >> >> This discrepancy exist there for many years. It seems to me more and more >> people tend to ignore that RFC terminology. >> >> It deserves clarification, but maybe not in this Charter proposal. >> > Alex, > > Thanks for the pointer. It would seem that use of "mobile networks" in > the charter is not correct. Maybe this should be "device mobility" or > "mobile networking". This needs to capture the use case where it is > physical devices that are mobile, as opposed to virtual hosts moving > in network virtualization. I think 'mobile networking' is a good term for that. As a side note, a private conversation about another matter, elightened me further on the term "Mobile Network"; it was used as early as 1993 in this context: "The techniques of encapsulation or source routing can be both used to deliver packets from the Mobile Network to wherever the particular Mobile Host is currently located." in a document that reflects perspective of IETF at that time. Contrary to RFC 3753, the term 'Mobile Network' was used differently even at IETF. Alex > > Tom > >> That's why it's a side-note. >> >> Alex >> [...] >> >> _______________________________________________ >> ila mailing list >> ila@ietf.org >> https://www.ietf.org/mailman/listinfo/ila >
- [Ila] Second round draft charter Tom Herbert
- Re: [Ila] Second round draft charter Uma Chunduri
- Re: [Ila] Second round draft charter Alexandre Petrescu
- Re: [Ila] Second round draft charter Tom Herbert
- Re: [Ila] Second round draft charter Alexandre Petrescu