IETF Logo Mail Archive

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

"Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com> Tue, 06 February 2018 13:03 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 ED52C1200B9; Tue, 6 Feb 2018 05:03:44 -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 sm3oGRDGNQuu; Tue, 6 Feb 2018 05:03:38 -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 0AC7612DB70; Tue, 6 Feb 2018 05:03:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizonwireless.com; i=@verizonwireless.com; q=dns/txt; s=prodmail; t=1517922210; x=1549458210; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=43/vhgBAi/k/I09Imq2xaMp0dqlX2QXGGlzY5oewAzM=; b=L1dI0WG5E/u/zwhXIVlrJhT1Vwycd4i3szt3fXabSmSa082lbBTd6BrG 735Ah3bVUyoqEaCUqk/qqaPUIUud0Tz5cUuws6mLSporXJj/6b4xQR89/ Uj3mFWdZ2xjRqiN+D/wGv+kdlMo7K+zuskErVd86aZiHym18rAEWLcjx0 A=;
X-Host: challenger.odc.vzwcorp.com
Received: from casac1exh001.uswin.ad.vzwcorp.com ([10.11.218.43]) by mercury.verizonwireless.com with ESMTP/TLS/AES128-SHA256; 06 Feb 2018 13:03:27 +0000
Received: from scwexch01apd.uswin.ad.vzwcorp.com (153.114.130.20) by CASAC1EXH001.uswin.ad.vzwcorp.com (10.11.218.43) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 6 Feb 2018 05:03:27 -0800
Received: from scwexch12apd.uswin.ad.vzwcorp.com (153.114.130.31) by scwexch01apd.uswin.ad.vzwcorp.com (153.114.130.20) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 6 Feb 2018 05:03:26 -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; Tue, 6 Feb 2018 05:03:26 -0800
From: "Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com>
To: Dino Farinacci <farinacci@gmail.com>
CC: Tom Herbert <tom@quantonium.net>, "ila@ietf.org" <ila@ietf.org>, dmm <dmm@ietf.org>, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
Thread-Topic: [Ila] [E] Re: [DMM] Fwd: New Version Notification for draft-herbert-ila-mobile-00.txt
Thread-Index: AQHTnuHzIb9qygu90kms8kltK9eB4KOWkNhAgACgSICAACWn4A==
Date: Tue, 06 Feb 2018 13:03:26 +0000
Message-ID: <64f9daae47c1461aa9a85625eedd155a@scwexch12apd.uswin.ad.vzwcorp.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> <3EA991DB-D28C-44A9-AAF5-71437AE8C9FB@gmail.com>
In-Reply-To: <3EA991DB-D28C-44A9-AAF5-71437AE8C9FB@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/9XEby5ZaItOPEY_acAm0l0pqQPY>
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 13:03:45 -0000

Dino:

This paper does describe the architecture. This information in a section would help and also explain what is different between
LISP and ILSR. Figure 3 shows SMF for ILSR, AMF+, Nsmf+, Namf+, and ILSR4. You can explain what the '+' means and what the
new functionalities in SMF for ILSR are and what ILSR4 is (is it a variant of N4/Sx - PFCP in 29.244).

Kalyani

-----Original Message-----
From: Dino Farinacci [mailto:farinacci@gmail.com] 
Sent: Monday, February 5, 2018 9:44 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

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

This whitepaper (attached below) indicates how draft-farinacci-lisp-mobile-network fits into the 5G architecture. First of all, do you agree with it? And if so, do you think that information be put in a new section?

Dino

v2.23.0 | Report a Bug | By Email