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

Dino Farinacci <farinacci@gmail.com> Tue, 06 February 2018 02:53 UTC

Return-Path: <farinacci@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 45B1D12DA48; Mon, 5 Feb 2018 18:53:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 d4FtxJ7JxRQr; Mon, 5 Feb 2018 18:53:07 -0800 (PST)
Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e:c05::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 0310912DA3F; Mon, 5 Feb 2018 18:53:06 -0800 (PST)
Received: by mail-pg0-x22d.google.com with SMTP id f6so480358pgs.10; Mon, 05 Feb 2018 18:53:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0p438J/OlHB+zEh6DUjygJAQ5NKgEoIG3dIT0qDiVrI=; b=HRKqEyypoJtb+uwOsBEKf2W5jZgIvJUkRufyUgpkrrQEM0hvFXTc0yzCJHFL9/TrNw JoepeLoKEHZIqH7TtalmBSw85Y+XwS+S0DAhtNFNGL1I4zA4FJLSwL6yhGa6yHqQB+Bn K/XJj1kuncN4AixNQ4hAhFhSO3+nVyV9mB8bu5lsf6fDVDhIuzU5BQt64cDn8NnymnML w6ozhhLEfjbA8H8JFIHvzCrQcrIoo9Q9T/IB5xnovjubXd5mDL0laSqGb2qVPjRcqQo4 gSQIjPh6Jg0FxdEH3smEhicgWa1VaZ+4/GmcLDs1MD91jdLdiztydvNJwOFa9AS9Tptq lCWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0p438J/OlHB+zEh6DUjygJAQ5NKgEoIG3dIT0qDiVrI=; b=ejt1SUEjp95pNq3P7IgZ8f3pJIvahUW3zLddw3+2wA+rrliqcfpbWK52KgMHBeNDHg ugo7ROfpP0/o1n65Jt1PAKPpWL4a0Lb/geXxwq2Fca9bOCLbyDgTicLAVreQq9e9oCQY v5CGprcJoSwRr8oBE/q8/0OnyltdDCdcJ1+HlxgrE/M6UHQ6ULWJW2If7o9+fgk8kFwq p8AdNBS7YVfOTytINZMEISVa1kqerMFcHBsr7m2929reQlRr7PKG9C8edmGVT97kHBYj pl+pukRiBezuiCo5si2a14bDOHENGsrq0fbkLvWV50HHD/20T7D8LM4PBM3dacq+/EAh D3EA==
X-Gm-Message-State: APf1xPCmvTx8/FGXE162wUtVBI+NIQJ93v0lGJKSD/Y8NnvVZv0z5X7O a5PDqAohkAK1OFze1mkUXeE=
X-Google-Smtp-Source: AH8x225UcOf8X0vIVXQjI7HdPX7rWPCww3RAVLOk0UEvwhvRGVuuqkeVIIAzGSx6xeM6u4CA28aysQ==
X-Received: by 10.99.135.67 with SMTP id i64mr52597pge.331.1517885585534; Mon, 05 Feb 2018 18:53:05 -0800 (PST)
Received: from [10.174.67.169] ([211.185.161.174]) by smtp.gmail.com with ESMTPSA id p1sm14771497pfb.82.2018.02.05.18.52.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Feb 2018 18:53:05 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <D69E5671.10DCE%sgundave@cisco.com>
Date: Mon, 05 Feb 2018 18:52:40 -0800
Cc: Kalyani Bogineni <Kalyani.Bogineni@VerizonWireless.com>, Tom Herbert <tom@quantonium.net>, "ila@ietf.org" <ila@ietf.org>, dmm <dmm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <680D7F3C-8417-40A3-856D-205D77B21AA6@gmail.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> <b9d5a581af5c46d3834f080c8e62b6a3@scwexch12apd.uswin.ad.vzwcorp.com> <1ED57BC0-DBE3-49A9-801C-7F19EE98ECE9@gmail.com> <5d6067277f484e78b561cf511f9d2861@scwexch12apd.uswin.ad.vzwcorp.com> <D69E42B4.10DB3%sgundave@cisco.com> <60D36175-0CB4-48E1-98C1-B7B1CAA0B876@gmail.com> <D69E5671.10DCE%sgundave@cisco.com>
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/4x2GPm2Qhcjnf1FermV4bKk8WOU>
Subject: Re: [Ila] [E] Re: [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: Tue, 06 Feb 2018 02:53:09 -0000

> Sure, but I assume the mapping table/DB is some where else in some central
> location and not on the UPF?

True.

> The question is how does the UPF fetch that entry and if the interface for
> that query is built on some 3GPP interface, or its internal to LISP with
> no bearing on the access technology.

The UPF sends IP packets. The UPF is part of the NGC core, right? So the packets from the UPF get to a map-resolver and map-server via IP. It’s pretty simple. At least it should be.

Dino

> 
> Sri
> 
> 
> 
> On 2/5/18, 6:42 PM, "Dino Farinacci" <farinacci@gmail.com> wrote:
> 
>> I don’t know what you mean. If you put the xTR function on an UPF, then
>> by LISP spec definition, Map-Request, Map-Reply, and Map-Register
>> functionality is part of the UPF.
>> 
>> Dino
>> 
>>> On Feb 5, 2018, at 5:27 PM, Sri Gundavelli (sgundave)
>>> <sgundave@cisco.com> wrote:
>>> 
>>> I suspect there might be a need for a new interface.
>>> 
>>> Assuming the LISP mapping system stays in the control plane, next to
>>> SMF/AMF, and the xTR functions on the UPF, there needs to be probably a
>>> new interface along the lines of the N4, for managing the LISP MAP
>>> operations (Reg/Req/Reply/Notify..).  But, off course if the mapping
>>> system stays in the user-plane, may be there is just interworking with
>>> the
>>> 3GPP authentication interfaces.
>>> 
>>> Sri
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 2/5/18, 5:15 PM, "Bogineni, Kalyani"
>>> <Kalyani.Bogineni@VerizonWireless.com> wrote:
>>> 
>>>> Dino:
>>>> 
>>>> Please look at 3GPP TS 23.501 to understand the architecture of NGC. We
>>>> tried to explain that in the White paper.
>>>> TS 23.502 has the procedures for the NGC. TS 23.503 specifies the
>>>> policy
>>>> and charging control framework for NGC.
>>>> CT4 has a technical report on protocol aspects for NGC in TR 29.891.
>>>> 
>>>> Your draft needs to describe how it fits in the 5G architecture, right
>>>> now it only addresses 4G.
>>>> 
>>>> Kalyani
>>>> 
>>>> 
>>>> 
>>>> -----Original Message-----
>>>> From: ila [mailto:ila-bounces@ietf.org] On Behalf Of Dino Farinacci
>>>> Sent: Monday, February 5, 2018 7:32 PM
>>>> To: Bogineni, Kalyani <Kalyani.Bogineni@VerizonWireless.com>
>>>> Cc: Tom Herbert <tom@quantonium.net>; ila@ietf.org; dmm <dmm@ietf.org>;
>>>> Sri Gundavelli (sgundave) <sgundave@cisco.com>
>>>> Subject: Re: [Ila] [E] Re: [DMM] Fwd: New Version Notification for
>>>> draft-herbert-ila-mobile-00.txt
>>>> 
>>>>> On Feb 6, 2018, at 5:04 AM, Bogineni, Kalyani
>>>>> <Kalyani.Bogineni@VerizonWireless.com> wrote:
>>>>> 
>>>>> Dino:
>>>>> 
>>>>> Can you add a section to show how this proposal would fit in 5G
>>>>> architecture? 
>>>> 
>>>> Can you be more specific in what you¹d like to see in the new section?
>>>> 
>>>> There are references throughout the draft where you see eNodeB and pGW
>>>> that UPF functionality could be at the same network mode location.
>>>> 
>>>> Dino
>>>> _______________________________________________
>>>> ila mailing list
>>>> ila@ietf.org
>>>> 
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailma
>>>> n_
>>>> 
>>>> listinfo_ila&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=Id
>>>> iS
>>>> 
>>>> ODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=zf1KfRu4n
>>>> UF
>>>> 
>>>> sUT8IJVExPygA_iAC-h4BErkY_CE2ugM&s=oLQOKLOAxuYtjVD_qWMbiQjkmP9acy6Au0X6l
>>>> pS
>>>> iBvg&e=
>>> 
>> 
>