IETF Logo Mail Archive

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 13:06 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 E8CF812DB71; Tue, 6 Feb 2018 05:06:33 -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 lCpuysAHZQ6O; Tue, 6 Feb 2018 05:06:32 -0800 (PST)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (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 ECD18126BF7; Tue, 6 Feb 2018 05:06:31 -0800 (PST)
Received: by mail-pg0-x229.google.com with SMTP id u1so1070871pgr.0; Tue, 06 Feb 2018 05:06:31 -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=64NUudfWSJ8aKgkzLbQu+99HwwI4sIIQ0LC8Ds9N+c4=; b=KtkzBGHnDc4LPPqMHcj1EkmiYUL9wEuX2GVuJLjxJb80lPpBbvL4rgbRzXJGoVXgdV aZiLC7oeb3rjqI1PjEYp87DZoAtPKZeVhwJ+HMSqFvLdJ9kBCmqNrJn2iB0qN4epJJPv ubDoZ/BjVeJsPopOreER+d2QZDp8D/KC8PMH18bTdIvtPz7Mob9YJZPgvSGoiDDBIgWa B3DBPSzh60pwIy/hD8jpqsBa+zwOawpFt0hz+oVCouS+y89ShUAhbUGJh7SodRqO45xH 47bekE07BegiJjgTWJHg31g2nAajeyZHSBFvSJk7xPVifnMRsOK7eKvwl5FcOILCViYW khmw==
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=64NUudfWSJ8aKgkzLbQu+99HwwI4sIIQ0LC8Ds9N+c4=; b=Qw5cvPonaXJ/UFzcgMGxxAt+gAQPZuX59ShC/dViR3woVc0bNRqq7xNdH5UwoosujD lIPj5mTx3EtYEZM0zczYf7R0IGX51ysg63JKRU8hm7j5U0kfv5rawpJufJq2JkjE6dg2 +MXlFk1Ai+wKSb6+0xd89N5HczkMq0XP+omfC8SAEfw+8qtMsN/1VsX1OFagB4XtG+qk r4n8Bw9Gi5tX4NZAT2i3rnNzDxgXrdJerFZQtlrVnHE19N065AcV7lJnNPwDQ/vcxmPt 44cVKx0XhIhSrN+s6Xklk4Di6EdR6rXXCSBJb00jN9ew2NSZueuDXLW6xcWd5IT0mhSw C74w==
X-Gm-Message-State: APf1xPAPU6NApG1F1Jfj6ysw57ctMn7yFO4XIzc3VrQCej3bKWgLR1YW T2fxaMTiLg/yjiUwxHBIfKZSmFyo
X-Google-Smtp-Source: AH8x2264AnEhTPgvOYJBC0KZGGk3a244fAKJ7XABifpub8pbNHMH+bcamcCP1FMnRHiva/38W1EjDQ==
X-Received: by 10.101.64.74 with SMTP id h10mr1886842pgp.200.1517922391284; Tue, 06 Feb 2018 05:06:31 -0800 (PST)
Received: from [10.174.67.223] ([211.185.161.174]) by smtp.gmail.com with ESMTPSA id q10sm13052338pfl.106.2018.02.06.05.06.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Feb 2018 05:06:30 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (15D60)
In-Reply-To: <64f9daae47c1461aa9a85625eedd155a@scwexch12apd.uswin.ad.vzwcorp.com>
Date: Tue, 06 Feb 2018 22:06:25 +0900
Cc: Tom Herbert <tom@quantonium.net>, "ila@ietf.org" <ila@ietf.org>, dmm <dmm@ietf.org>, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E8D19FC-0B07-4FF5-8051-564A5A73FEE8@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> <3EA991DB-D28C-44A9-AAF5-71437AE8C9FB@gmail.com> <64f9daae47c1461aa9a85625eedd155a@scwexch12apd.uswin.ad.vzwcorp.com>
To: "Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/JEI7Vvoe9iV5mt-gOLeA5HjGqd4>
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:06:34 -0000

The other authors can comment but to me ILSR and LISP are the same thing. 

ILSR is an architecture that can use the LISP protocol set. 

Dino

> On Feb 6, 2018, at 10:03 PM, Bogineni, Kalyani <Kalyani.Bogineni@VerizonWireless.com> wrote:
> 
> 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