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

Tom Herbert <tom@quantonium.net> Mon, 29 January 2018 18:08 UTC

Return-Path: <tom@quantonium.net>
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 A8B9C12FAB3 for <ila@ietfa.amsl.com>; Mon, 29 Jan 2018 10:08:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-net.20150623.gappssmtp.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 0swcUhHTF9tC for <ila@ietfa.amsl.com>; Mon, 29 Jan 2018 10:08:03 -0800 (PST)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DB1812FA94 for <ila@ietf.org>; Mon, 29 Jan 2018 10:08:01 -0800 (PST)
Received: by mail-wm0-x22d.google.com with SMTP id v123so35479169wmd.5 for <ila@ietf.org>; Mon, 29 Jan 2018 10:08:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ptH3hNJtpKaw0HcMhY01GeB7MuCuUlP30rE2wBrYGec=; b=noD0fs/ybYKFdbCaFj7ygevKh7LOvurnuvmeP8Okjfc/OXwVE8U0DEhFtnGQq/PF5H +Mx2XDHWVJ6eS19fDvLJzRYzvjuxZDsdkE44R6Lx58Z6kLPTiumNmW8o66KXsKBtl3i4 IZhJCayWcTEYb2VRnuXKG96lZYNEe0Y26B7tb5LsrEPB5XbQTTb6LnetNeBBYdLPL/zn n0oXZ+rvkG2zcjq8FJvDKxf9/gtc1YDtgFBAj+EcQlJ8jjJevAo+HE9gfA9egraG1/Pb iKq83+YP7an0xKQ5R0XNkFQHEIQNo+IeP77bdYhVFoj898S1mb8wa4UzV0pj3irphU3+ zemQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ptH3hNJtpKaw0HcMhY01GeB7MuCuUlP30rE2wBrYGec=; b=TCewlKFCPH76RxZd+U+3tdAVayKg6BzFmHuVaS0yX78MnfREJryAjqAFl233jfGq23 yKxyLqg8z0IocPNH65sw+FC6ow0vze0KjgKZhGZreSPV3b+7QYquBmMj6oJfGahVtf8Z HYeI3dwAlGQwLIrXxUtpQDif6jFNbl1Pv0yFMnK3y+MSzqAIAO65+7S6YB/7u9s/md1H WOyZRopfjCCnfbNFmBaPm+BYpq3B25/t8U8G/xbsEsPsdYN9paFTvHJ+XroPEL+JFmFS MyapBEXecS4qtuwI8IWG9RBlDQpOir4S/rd3FIuxLV72LE/epCPIph8EEgKwChbmbdaw Cs9w==
X-Gm-Message-State: AKwxyteuTs+jeWc7sfLvVmLPWW9+eGgTtCmVfR54GuiPyfvAuJyGc8dL XYDfKG2lM7CxzAw8VxIDI4IP5WLcuvVqxhYyx1u77w==
X-Google-Smtp-Source: AH8x226bDuzY9mhmNTTUS2qtpnc6HyLOM761Z5bBH6zqvpZSu30IfArPFh+0o4A/EO7uxz1i5WbQ3dB2JYAn2bjfUYY=
X-Received: by 10.28.129.212 with SMTP id c203mr17708253wmd.98.1517249279683; Mon, 29 Jan 2018 10:07:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.173.66 with HTTP; Mon, 29 Jan 2018 10:07:59 -0800 (PST)
In-Reply-To: <8613c1f417d543b5990da934f9fb4ec4@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>
From: Tom Herbert <tom@quantonium.net>
Date: Mon, 29 Jan 2018 10:07:59 -0800
Message-ID: <CAPDqMepp8szBtvez26j+m_B6ebNA1vYxX3dy7jkZB-Cv81CRoA@mail.gmail.com>
To: "Bogineni, Kalyani" <Kalyani.Bogineni@verizonwireless.com>
Cc: "ila@ietf.org" <ila@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/AjE3YvzgRA2QmWQM3txPt1qv5nY>
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:08:05 -0000

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?

> 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