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:42 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 2FEDF124BFA; Mon, 5 Feb 2018 18:42:38 -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 xV-3dKqmPxFX; Mon, 5 Feb 2018 18:42:35 -0800 (PST)
Received: from mail-pl0-x22d.google.com (mail-pl0-x22d.google.com [IPv6:2607:f8b0:400e:c01::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 4CD91124217; Mon, 5 Feb 2018 18:42:35 -0800 (PST)
Received: by mail-pl0-x22d.google.com with SMTP id q17so359425pll.1; Mon, 05 Feb 2018 18:42:35 -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=noxTp4xIVCLUrQTdhdETf5qVH5ge0UAfyCU5FlhrSd8=; b=i+2rmZT44vwhKYcwI8WqNauoLbLMeTG7encjxOlqug0/fgI+FCvDC2YjbhAdoBDJ/U 9KEC7Xws75AkyBrYm3Bux4aNvQlk9yBdiEXhO7nv64bslGjKTbyfOPDt4PVyWqDenMjL NZtIQS71S+YET1jzndatbF3ukivImn1S2wKXdtRol1972LDG42L7t/v/a9fuNhXSBq8b OFb2haPrz9YfxgK3vl0+5EMmjak0r9Io7LyYywJlVHt3ndibgh+50tBWw7AJCCfoaDAU +huM+965vevkVdDlygnltceriAyXoqQY+q/gc34hdoxdKG9tj3DGUjaDZ7cPoU9gVB5e QAZw==
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=noxTp4xIVCLUrQTdhdETf5qVH5ge0UAfyCU5FlhrSd8=; b=rDZxEfjUZOAcRplLvoaNN2yU2bRDsqBDnz4FcNz7eYrOx3MZDuPaZp0zr4MwUznJTe RPEN4TYnMqZdAmOAbyBZzvcVIhx8TtlmcEVKnyLbe5ZpCOggkk+46WXPEMDrSTsFPAEr 5/hnTcXe4mPTLDHEjr1FQlSPEr+/4WieVJKNILVL378MY8V44Ab+7Otqo42eiPUfDOB3 r+j2ZwPAlaD2t0GNvQtYZBbV8KOEZ95jw0h4x6/f5M67kjkFefb0XOQBkYbKXQGrLWd9 G8itk1JtWzhT+ZiOmtMINR++3ggimLMwUuW3dvT94RRif0muhbIufTS1Nyw2y5jMRDKe v8pw==
X-Gm-Message-State: APf1xPD9a4Xe7N8Mm0tb19TDV1DEU26wJKcTm2UF9AI8QgMVp0Un4ZkI pwg1JJCC8l/8QF25+1Ab2CU=
X-Google-Smtp-Source: AH8x225vhpLb/XlyfuVyQ15K60AB3Y37M4IbCcUI7Cr2BjxvrH1P5ckkDjDy4XThKt8jTphkfdDzqg==
X-Received: by 2002:a17:902:bf0a:: with SMTP id bi10-v6mr872189plb.181.1517884954921; Mon, 05 Feb 2018 18:42:34 -0800 (PST)
Received: from [10.174.67.169] ([211.185.161.174]) by smtp.gmail.com with ESMTPSA id e23sm207550pff.144.2018.02.05.18.42.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Feb 2018 18:42:34 -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: <D69E42B4.10DB3%sgundave@cisco.com>
Date: Mon, 05 Feb 2018 18:42:25 -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: <60D36175-0CB4-48E1-98C1-B7B1CAA0B876@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>
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/d0CaaYHCzpX5OPLRH4zVHY4KztE>
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:42:38 -0000

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_mailman_
>> listinfo_ila&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=IdiS
>> ODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=zf1KfRu4nUF
>> sUT8IJVExPygA_iAC-h4BErkY_CE2ugM&s=oLQOKLOAxuYtjVD_qWMbiQjkmP9acy6Au0X6lpS
>> iBvg&e=
>