IETF Logo Mail Archive

Re: [Ila] [DMM] Fwd: New Version Notification for draft-herbert-ila-mobile-00.txt

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Fri, 02 February 2018 01:17 UTC

Return-Path: <sgundave@cisco.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 1BC12126DFB; Thu, 1 Feb 2018 17:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 lXnc2Trj3Nnh; Thu, 1 Feb 2018 17:17:49 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 424AA126B7E; Thu, 1 Feb 2018 17:17:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2394; q=dns/txt; s=iport; t=1517534269; x=1518743869; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=gcXR8ZuhzfgdsKTIibWa/1IZ8D8TePsMQ5hdFfUx9i0=; b=JX1IZJV49wGe+CuRDHKyPSRFBsdyNamM53f2ll3VMeUa7NtbX3KF7wzp F4McA/gRIcRxGguQwznVqM/EnhG2E/0Q9tog5UlD8DEnJo8nY9zCojiIu UXIoEXsEY8g9YNIHQZu3Es2wNEQUpVCPDzw5pWry1KesgxldakZDqqhk+ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ACAgCGu3Na/4oNJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYNCgVsoCoNWmFGCAplfCoU7AhqCF1cVAQEBAQEBAQECayiFJAEFNEMCEAIBCBIGBCgCAjAXDgIEDgWKNZBVnWoGgimKZAEBAQEBAQEBAQEBAQEBAQEBAQEfgQmDYIIVgVeBaIIggQ6DLwSBb4MRgmsBBJJFkV4ClWyUMZc/AhEZAYE7ATUjgVBwFYJngwqBbXiKVYEXAQEB
X-IronPort-AV: E=Sophos;i="5.46,445,1511827200"; d="scan'208";a="352089218"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Feb 2018 01:17:48 +0000
Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w121Hmd1026334 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 2 Feb 2018 01:17:48 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 1 Feb 2018 19:17:47 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1320.000; Thu, 1 Feb 2018 19:17:47 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Tom Herbert <tom@quantonium.net>
CC: Dino Farinacci <farinacci@gmail.com>, dmm <dmm@ietf.org>, "ila@ietf.org" <ila@ietf.org>
Thread-Topic: [DMM] [Ila] Fwd: New Version Notification for draft-herbert-ila-mobile-00.txt
Thread-Index: AQHTm74ye1FoV0iXB0ectXus4q3GS6OQrroA//9/jwA=
Date: Fri, 02 Feb 2018 01:17:47 +0000
Message-ID: <D698FAC3.10A53%sgundave@cisco.com>
References: <151750859755.24445.6929673804211867286.idtracker@ietfa.amsl.com> <CAPDqMerbX4UJ-mK-A-f=im=1h0Yz-52QfWLLgVDkybtSShNp5Q@mail.gmail.com> <D698D3B3.2A3906%sgundave@cisco.com> <D43DF85C-75F6-445B-895F-D27CE3285061@gmail.com> <D698E00C.10A01%sgundave@cisco.com> <51809684-7D19-4498-83CF-AB0C2FF678EF@gmail.com> <D698F0A8.2A3953%sgundave@cisco.com> <CAPDqMerzsK65JnDgUhT7Q-h-zC_R4686QkWCGfJnDEDoEgVfVw@mail.gmail.com>
In-Reply-To: <CAPDqMerzsK65JnDgUhT7Q-h-zC_R4686QkWCGfJnDEDoEgVfVw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.7.106]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <22BE4620C4EDF54D818D0677CE013219@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/uMgCjYDbDT5_OK2yEyuizx6fRcY>
Subject: Re: [Ila] [DMM] Fwd: New Version Notification for draft-herbert-ila-mobile-00.txt
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: Fri, 02 Feb 2018 01:17:51 -0000

Tom, 

Last I remember, we gave one “generic” and an access agnostic protocol in
the form MIPv6/PMIPv6, they never got it and never cared.


But, if you can sell it to 3GPP, this new control-plane that goes into
user-plane, I am with you.  :-)


Sri




On 2/1/18, 4:57 PM, "Tom Herbert" <tom@quantonium.net> wrote:

>On Thu, Feb 1, 2018 at 4:38 PM, Sri Gundavelli (sgundave)
><sgundave@cisco.com> wrote:
>>> One thing to add. LISP has a more mature control-plane mapping system.
>>>ILA has a recent proposal for its control-plane.
>>
>> Mobility architectures started with a unified CP/UP approach, then the
>> industry thought its a great idea to move the Control-plane out, and
>> reduce the state in the User-plane, and eliminate tunnels. Now, we want
>>to
>> eliminate the tunnels, but we need a new control protocol to manage the
>> binding tables, and manage the complex cache states. Wondering, what¹s
>> wrong with this picture?  What de we name this new CUPS architecture?
>>
>Sri,
>
>Bear in mind that "industry" has different meanings depending on the
>context. For ILA, and probably for LISP, the intent is to build a
>generic protocol that can be used across variety of use cases in the
>networking industry which hasn't uniformly adopted CUPS. It's pretty
>obvious that we'd want to leverage a single data plane control plane
>for these (isn't that the point of generic protocols :-) ). The CUPS
>actually architecture helps a lot here by creating a clean well
>abstracted interface that should make it straightforward to adapt an
>ILA control plane. I think our architecture where we define ILA as an
>NF reflects that.
>
>Tom
>
>>
>> Sri
>>
>>
>> (with no chair hat)
>>
>>

v2.23.0 | Report a Bug | By Email