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:20 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 9F98A126B7E; Thu, 1 Feb 2018 17:20:10 -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_H3=-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 7JExtuvvDLLr; Thu, 1 Feb 2018 17:20:09 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8E1E1200E5; Thu, 1 Feb 2018 17:20:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2296; q=dns/txt; s=iport; t=1517534408; x=1518744008; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=0cF6i5tMW3Hv8ItuhC5BltlgA15oLJyH6n0jjheFAr4=; b=N79KNiFnxAS38vSAPMCWYDO7sdG0eqFGFT8L7+OrwLtIwxse2z7CeOJv uFFfiCoGK276qqXUOeUVwBqpMOIJ12WTFIDvGwPe61J1lQzq8t3ru00fE WCZuaIqfpfyJST8P/q8FrK9YxFA1/uP5gn07GtEyrHMlZVX4vO/Ntk80r E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DFAACGu3Na/5RdJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYNCZnUoCoNWiiSOLZlKghcKGAuFGAIaghdUGAEBAQEBAQEBAmsohSQCBAEBMjoJAhACAQgSCigCAiULFw4CBA4FG4oaEJBFnWoGgimKZAEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQmDYIIVgVeBaIMugy8BAQKFAIJrAQSSRZFeApVslDGXPwIRGQGBOwEfOYFQcBU9giqDCoFteIpVgRcBAQE
X-IronPort-AV: E=Sophos;i="5.46,445,1511827200"; d="scan'208";a="350943913"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Feb 2018 01:20:07 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w121K72o031653 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 2 Feb 2018 01:20:07 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 1 Feb 2018 19:20:06 -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:20:06 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Marco Liebsch <Marco.Liebsch@neclab.eu>
CC: "ila@ietf.org" <ila@ietf.org>, dmm <dmm@ietf.org>, Dino Farinacci <farinacci@gmail.com>
Thread-Topic: [Ila] [DMM] Fwd: New Version Notification for draft-herbert-ila-mobile-00.txt
Thread-Index: AQHTm8JLSxkp68tilkKRsAlpjZjNr6OQLuoA
Date: Fri, 02 Feb 2018 01:20:06 +0000
Message-ID: <D698FC46.10A60%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> <E84F6DDD-764A-4157-B755-434F628155B1@neclab.eu>
In-Reply-To: <E84F6DDD-764A-4157-B755-434F628155B1@neclab.eu>
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: <133DE39CFF6F3444839890E44BB73A8D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/RYR5ok6RWLw8khFh69Wyderjsos>
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:20:10 -0000

Absolutely! A programmable data plane what FPC interface is offering,
keeps the CUPS objectives.

Sri

On 2/1/18, 5:07 PM, "ila on behalf of Marco Liebsch" <ila-bounces@ietf.org
on behalf of Marco.Liebsch@neclab.eu> wrote:

>I think we should rather relax the dependency between control and data
>plane. If we treat the data plane as nodes which enforce policies (encap,
>recap, re-write, etc), any c plane may suit and enforce suitable policies
>in the selected data plane nodes, e.g.  by utilizing the DMM group’s FPC
>models. Any solution that binds the data plane to a particular control
>plane may constrain its deployment, no?
>
>marco
>
>
>
>On 2. Feb 2018, at 01:39, 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
>> 
>> 
>> (with no chair hat)
>> 
>> 
>> _______________________________________________
>> dmm mailing list
>> dmm@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmm
>
>_______________________________________________
>ila mailing list
>ila@ietf.org
>https://www.ietf.org/mailman/listinfo/ila