IETF Logo Mail Archive

Re: [Ila] [E] Re: review comments on ] draft-ietf-dmm-srv6-mobile-uplane-00.txt

"Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com> Fri, 09 February 2018 13:27 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 E9F45127136; Fri, 9 Feb 2018 05:27:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.731
X-Spam-Level:
X-Spam-Status: No, score=-2.731 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] 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 uXKhersRjDyo; Fri, 9 Feb 2018 05:27:51 -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 27016124D6C; Fri, 9 Feb 2018 05:27:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizonwireless.com; i=@verizonwireless.com; q=dns/txt; s=prodmail; t=1518182871; x=1549718871; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=D0RRly3v5rK7a5PgoKPwKPznO71j0CeHKpv0Zw6CZik=; b=Vlzof6xEzakZgtQXEXpIYsMfGo8HPux14d6QoRJ/j69YNCfMIdgitcln W+ogSXWZzkFXrMfjqJh9UkF3F0edZAaOGLy9imu6fBMGqOZqItxi/4DXi gWUlHWu39AngyRRu9JuW5NC7r+tPsIy6iAYnbEYhTaDKdKVoXdepfJaFZ Q=;
X-Host: challenger.odc.vzwcorp.com
Received: from casac1exh003.uswin.ad.vzwcorp.com ([10.11.218.45]) by mercury.verizonwireless.com with ESMTP/TLS/AES128-SHA256; 09 Feb 2018 13:27:49 +0000
Received: from scwexch13apd.uswin.ad.vzwcorp.com (153.114.130.32) by CASAC1EXH003.uswin.ad.vzwcorp.com (10.11.218.45) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 9 Feb 2018 05:27:48 -0800
Received: from scwexch12apd.uswin.ad.vzwcorp.com (153.114.130.31) by scwexch13apd.uswin.ad.vzwcorp.com (153.114.130.32) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 9 Feb 2018 05:27:47 -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; Fri, 9 Feb 2018 05:27:47 -0800
From: "Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com>
To: Satoru Matsushima <satoru.matsushima@gmail.com>
CC: "ila@ietf.org" <ila@ietf.org>, dmm <dmm@ietf.org>
Thread-Topic: [Ila] [E] Re: review comments on ] draft-ietf-dmm-srv6-mobile-uplane-00.txt
Thread-Index: AdOevcCGjGhLLFwWT62+igTQ69qI1wApMiYAAAXlQ5AAYQslAAAH9AhQACkdM4AABlqUYA==
Date: Fri, 09 Feb 2018 13:27:47 +0000
Message-ID: <b6b5f3a3abcc40cd826656a04d9625be@scwexch12apd.uswin.ad.vzwcorp.com>
References: <15c36020cfea41d0a93331ab4a3c0fdf@scwexch12apd.uswin.ad.vzwcorp.com> <B924DE6A-008D-40B4-9FA9-695DF1AEB02E@gmail.com> <d8d6d12f582545ce913284556d259d3b@scwexch12apd.uswin.ad.vzwcorp.com> <C9EAC1D6-C37B-45A8-AD84-D0BC0DDFAD4E@gmail.com> <69d06c7ecd624291a868c3bb00cc3e49@scwexch12apd.uswin.ad.vzwcorp.com> <D424F84A-7B6D-43D7-A1C8-3ABFB7BE794A@gmail.com>
In-Reply-To: <D424F84A-7B6D-43D7-A1C8-3ABFB7BE794A@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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/DJOp1F2x92qee9WA6CwROazelS4>
Subject: Re: [Ila] [E] Re: review comments on ] draft-ietf-dmm-srv6-mobile-uplane-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: Fri, 09 Feb 2018 13:27:54 -0000

Satoru:

Comments inline.

-----Original Message-----
From: Satoru Matsushima [mailto:satoru.matsushima@gmail.com] 
Sent: Friday, February 9, 2018 3:25 AM
To: Bogineni, Kalyani <Kalyani.Bogineni@VerizonWireless.com>
Cc: ila@ietf.org; dmm <dmm@ietf.org>
Subject: Re: [Ila] [E] Re: review comments on ] draft-ietf-dmm-srv6-mobile-uplane-00.txt

Hello Kalyani,

> 
> When you see UPF specifically it should be controlled by SMF through N4, they are not the UPFs.
> But you might see them as UPFs if a SMF doesn’t control them directly but the SMF can put the sessions to it through some other means.
> 3GPP SA2 has studied on that case (ETSUN). We consider how SMF deal with that case and SRv6 may help to solve the issues to it in simpler way.
> Please let me know if you are interested in.
> [KB] is there a TR for ETSUN that I can read?

You can read it later on this September. See https://urldefense.proofpoint.com/v2/url?u=https-3A__portal.3gpp.org_ngppapp_CreateTdoc.aspx-3Fmode-3Dview-26contributionUid-3DSP-2D170743&d=DwIFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=IdiSODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=A4gJxIMQxDhuwbITGRX_eHAfWF36yy799w_bFx5TDFc&s=ZNR28OMiy-m_kDk3BNz7y8KuA-bfdBBr2HeRt8WQl5c&e
[KB] Thank you

> 
> [KB] I think your document needs to separate out 3 architectures: one for 4G - SGW/PGW; one for 4G - CUPS; and one for 5G - UPF.

If you mean SRv6 Mobile Uplane draft, it is already a WG document, not my draft. So I’d collect opinions on this from WG. I’m sorry for that.
As a co-author of the draft, I’m afraid I disagree. SRv6 Mobile Uplane draft specifies SRv6 functions for mobile user plane, which should be architecture agnostic.

[KB] Sections 7.2, 7.3 refer to 3GPP terminology like eNB, SGW, PGW. My comment was suggesting that you include 5G terminology and CUPS terminology 
as well so it is clear how your proposal can be used in various scenarios.

> 
> [KB] I am also still not clear if the blue icons (which I think represent IP/MPLS nodes) in your slides are included in SRv6 architecture or not.

I put some text what those icons indicate. Please find them in the slides. The blue icons represent IPv6 or SRv6 node.
[KB] Seems like the IPv6/SRv6 nodes do not interact with SMF. Is that the intent? 

Cheers,
--satoru

v2.23.0 | Report a Bug | By Email