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

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Tue, 06 February 2018 03:06 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 40810124D68; Mon, 5 Feb 2018 19:06:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 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, URIBL_BLOCKED=0.001, 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 Mac6NpPlTKoC; Mon, 5 Feb 2018 19:06:42 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D449124319; Mon, 5 Feb 2018 19:06:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6548; q=dns/txt; s=iport; t=1517886402; x=1519096002; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=b06WxCQAToTMPxW8qn+HTLsijaH1TNAY17BGalnLSf8=; b=gSTJjUHqY1S0mlZvqC8bdSg6Qkez3IRm47e8u3ygo2Zqd5EIu8JW8MmP zIblTOYObIVCrA7I5jpd9R65jjJ1XszofoIyq2E84rxdEnmbX1eY495zD l+Y1D+Ad8aldt4KzzTsgC/o+u/4m8oZtwjml9Bk0eWzwfpj3AbIj2TpML s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A3BACjGnla/4wNJK1UCRkBAQEBAQEBAQEBAQEHAQEBAQGDUWZwKAqDW5hUggKJE441ghgKI4UYAhqCM1YWAQEBAQEBAQECaygJBYUVAQEBAwE0OgkCBQcEAgEIEQEDAQEBBCMFAgIfERQDBggCBA4Fih0DDQgQnGSdbAaCKYc/DYExgXgBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYEJg2GCFYFXgWiDLoJrRAQZgSwKAQEIFgczgleCawWjZz4CiBeIUYUHgh6GJotzjW1HiRUCERkBgTsBJgMvgVBwFT2CRoJVHBmBbXgBAYxjgSWBFwEBAQ
X-IronPort-AV: E=Sophos;i="5.46,467,1511827200"; d="scan'208";a="346131168"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Feb 2018 03:06:41 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id w1636fZ5004040 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 6 Feb 2018 03:06:41 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 5 Feb 2018 21:06:40 -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; Mon, 5 Feb 2018 21:06:40 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Dino Farinacci <farinacci@gmail.com>
CC: Kalyani Bogineni <Kalyani.Bogineni@VerizonWireless.com>, Tom Herbert <tom@quantonium.net>, "ila@ietf.org" <ila@ietf.org>, dmm <dmm@ietf.org>
Thread-Topic: [Ila] [E] Re: [DMM] Fwd: New Version Notification for draft-herbert-ila-mobile-00.txt
Thread-Index: AQHTnvQmkdxnpj1xF0GbCd8zbJPU3g==
Date: Tue, 06 Feb 2018 03:06:40 +0000
Message-ID: <D69E5971.10DDB%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> <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> <680D7F3C-8417-40A3-856D-205D77B21AA6@gmail.com>
In-Reply-To: <680D7F3C-8417-40A3-856D-205D77B21AA6@gmail.com>
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.37.172]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <74189427CD65EE4C8A2523E3CF05AE37@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/W5YwSJumCqQbvUHLVO8m6NRlU0k>
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 03:06:45 -0000

> 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.

Sure, that LISP control plane packet is an IP packet. But, every message
that is going between CP and UP will be named and numbered in 3GPP specs,
and so said in my first mail that its probably a new interface specific to
LISP.

With any of the IETF protocols, PMIPv6/LISP/ILA, it can be argued that
these are IP packets. But, we should note that there is interworking
needed with the 3GPP authentication infrastructure, and the protocol
specific control plane. Note that these protocols are not doing MN
identity establishment. May be I could be wrong here on the assumptions
you have around LISP MN capabilities, but to me MN is a standard 3GPP UE
with no special capabilities such as MIPv6/LISP MN stack.



Sri
  
 




On 2/5/18, 6:52 PM, "Dino Farinacci" <farinacci@gmail.com> wrote:

>> 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_mail
>>>>>ma
>>>>> n_
>>>>> 
>>>>> 
>>>>>listinfo_ila&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=
>>>>>Id
>>>>> iS
>>>>> 
>>>>> 
>>>>>ODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=zf1KfRu
>>>>>4n
>>>>> UF
>>>>> 
>>>>> 
>>>>>sUT8IJVExPygA_iAC-h4BErkY_CE2ugM&s=oLQOKLOAxuYtjVD_qWMbiQjkmP9acy6Au0X
>>>>>6l
>>>>> pS
>>>>> iBvg&e=
>>>> 
>>> 
>> 
>