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

"Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com> Mon, 29 January 2018 18:12 UTC

Return-Path: <Kalyani.Bogineni@verizonwireless.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 A95FE12FABF for <ila@ietfa.amsl.com>; Mon, 29 Jan 2018 10:12:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.73
X-Spam-Level:
X-Spam-Status: No, score=-2.73 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizonwireless.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 q_Jizsr0gjvs for <ila@ietfa.amsl.com>; Mon, 29 Jan 2018 10:12:51 -0800 (PST)
Received: from mercury.verizonwireless.com (mercury.verizonwireless.com [162.115.227.109]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 208BA12FAF0 for <ila@ietf.org>; Mon, 29 Jan 2018 10:12:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizonwireless.com; i=@verizonwireless.com; q=dns/txt; s=prodmail; t=1517249535; x=1548785535; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=XN8PvTfctpkdgKD5Fztli0QM4FnrcpEc8a9phJlXH+U=; b=hsHmDQ1boIdadZyjAxkHR+gNbrKFlfIIt5kJxHgY7BC/3byq0STSRKvv 6i88WZWoowbhKPk3pXjGyKBRXGstaMS8PLpRBfokh4kU51FAIAqciyWaA oeGwj1hzftzNYG4rqy8WXJeVPzOwowbxXgbSLmvaZl2Jt3OZ/Vzv9UwlM E=;
X-Host: viking.odc.vzwcorp.com
Received: from casac1exh002.uswin.ad.vzwcorp.com ([10.11.218.44]) by mercury.verizonwireless.com with ESMTP/TLS/AES128-SHA256; 29 Jan 2018 18:12:13 +0000
Received: from scwexch12apd.uswin.ad.vzwcorp.com (153.114.130.31) by CASAC1EXH002.uswin.ad.vzwcorp.com (10.11.218.44) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 29 Jan 2018 10:12:08 -0800
Received: from scwexch12apd.uswin.ad.vzwcorp.com (153.114.130.31) by scwexch12apd.uswin.ad.vzwcorp.com (153.114.130.31) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 29 Jan 2018 10:12:07 -0800
Received: from scwexch12apd.uswin.ad.vzwcorp.com ([153.114.130.31]) by scwexch12apd.uswin.ad.vzwcorp.com ([153.114.130.31]) with mapi id 15.00.1263.000; Mon, 29 Jan 2018 10:12:07 -0800
From: "Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com>
To: Tom Herbert <tom@quantonium.net>
CC: "ila@ietf.org" <ila@ietf.org>
Thread-Topic: [Ila] [E] Fwd: New Version Notification for draft-herbert-ila-motivation-00.txt
Thread-Index: AQHTmSwmuO2tGD/OeEG87fZZlagR/qOLJtGg
Date: Mon, 29 Jan 2018 18:12:07 +0000
Message-ID: <2f3fa2694dc94a8086c19d953c9edb5c@scwexch12apd.uswin.ad.vzwcorp.com>
References: <151665923357.29847.349853196062220993.idtracker@ietfa.amsl.com> <CAPDqMeoBFFM7K+KDNOd7yKJeP0ZhE_0DwfoKyywQZBqKGKwpdA@mail.gmail.com> <781c7de13bf449e886d50870b794538e@scwexch12apd.uswin.ad.vzwcorp.com> <CAPDqMep+Fb5O48C3-=Ago8N9nckYqndhmfMr4-hRRVXPL7aaHA@mail.gmail.com> <8613c1f417d543b5990da934f9fb4ec4@scwexch12apd.uswin.ad.vzwcorp.com> <CAPDqMepp8szBtvez26j+m_B6ebNA1vYxX3dy7jkZB-Cv81CRoA@mail.gmail.com>
In-Reply-To: <CAPDqMepp8szBtvez26j+m_B6ebNA1vYxX3dy7jkZB-Cv81CRoA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.11.60.250]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/W7pWXfiEy8Ariz0VkuItbSVfAvI>
Subject: Re: [Ila] [E] Fwd: New Version Notification for draft-herbert-ila-motivation-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: Mon, 29 Jan 2018 18:12:53 -0000


-----Original Message-----
From: ila [mailto:ila-bounces@ietf.org] On Behalf Of Tom Herbert
Sent: Monday, January 29, 2018 1:08 PM
To: Bogineni, Kalyani <Kalyani.Bogineni@VerizonWireless.com>
Cc: ila@ietf.org
Subject: Re: [Ila] [E] Fwd: New Version Notification for draft-herbert-ila-motivation-00.txt

On Sun, Jan 28, 2018 at 10:01 AM, Bogineni, Kalyani <Kalyani.Bogineni@verizonwireless.com> wrote:
> Tom:
>
>
>
> Service function chaining is on the SGi interface in 4G and on N6 
> interface in 5G. Each operator decides whether to
>
> deploy mobile core network as an overlay on IP/MPLS network or integrated.
> Standards should allow both deployment
>
> options. Similarly operators could choose to implement several of the 
> SGI/N6 functions into PGW/UPF.
>
Okay, we'll mention that in the doc.

>
>
> In going through your document again, some comments:
>
>
>
> Section 2.2: It appears that you are using ‘nodes’ for network 
> elements/functions as well as for end device like UE in
>
> 3GPP terminology. Is your sentence “Mobility is likely a rate event….”
> related to network functions or to UEs?
>
>
>
> Section 2.5: This section seems to be about mobility of UEs, but 
> ‘node’ is used. Some clarification between the two sections
>
> is needed.
>
Yes. I think mobile node should be the generic term for something that can move around a network. UE and mobile devices a real devices that move around.

>
>
> Section 2.6.2: Relative to mobile traffic there is Uplink (UL) traffic 
> and Downlink (DL) traffic. I think you need to address
>
> caching relative to both UL and DL traffic. With anchor-less mobility, 
> ILA-R will need to send the DL traffic to the correct
>
> ILA-N/gNB.
>
Yes, I believe that describes the Downlink traffic and an ILA router in the path will do the mapping. For Uplink traffic destined to Internet, ILA is not needed. For Uplink traffic destined to another node within the ILA  domain ILA transformation is done by either and ILA router or forwarding node with a cache entry. Does this description address it?

[KB] Yes

> In this section you describe a Pub/Sub model. Can it be implemented as 
> RESTful APIs? 5G services based architecture
>
> uses APIs from network functions. ILA can be incorporated in 5G 
> services based architecture in one of two ways.
>
Good point. I think we should consider if ILAMP and an protocols into ILA-M (ILA management) can be RESTful. The protocol between the ILA routers might also be considered, but I tend to think this more like either a routing protocol (like BGP) or would implement a distributed database that already has its own protocol.

Tom

_______________________________________________
ila mailing list
ila@ietf.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ila&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=IdiSODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=j5P3Tjt0cLBHFo3ZR0qm5bhvdqmoXwjmoR4HsCsJYrA&s=qDV7PKCfXih4cmKUvbyWw1RCR6Gp_jIsI40A3ywlMuI&e=