IETF Logo Mail Archive

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

Satoru Matsushima <satoru.matsushima@gmail.com> Wed, 07 February 2018 06:04 UTC

Return-Path: <satoru.matsushima@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 8116E12DA17; Tue, 6 Feb 2018 22:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-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 dVm4BQaiRm5V; Tue, 6 Feb 2018 22:04:21 -0800 (PST)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 AC0F512D88B; Tue, 6 Feb 2018 22:04:21 -0800 (PST)
Received: by mail-io0-x235.google.com with SMTP id l17so756755ioc.3; Tue, 06 Feb 2018 22:04:21 -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=aSH8JTARwqNQA+eEv2VPEI7qO+LDw901sHtKd9Kpt6Q=; b=Ti5yRDnzDzOXGy5ruVGZlyVrZzNuihH8EivHh3vJ3ZTwAJelg72CY/Mhcluz8pscO6 O1Tr13EXscVV/DJJBDu8MeFGG9ABnZqopsrClOnbPGSHOXpEKv/M7/rs5o70IqQXW5ZD hvu/Fbgynx3ECMif136M3v0q04y3w8tfZRbZcwtmqI7SyB/UrXbwuqtDbVlqSBzovq7z BfK5Y7NF4FM3lfmezZsBufrm+YRCFoX3uInPSgdItxyZpGwGCCpso5s/Dky8OIJSLSD5 9eBsmrn+MDbKSY20JvL221oRA0h3jKn/jLXQL0eYd7N0nxLLQoJZqMxNqi04uwjLujCh 9OJg==
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=aSH8JTARwqNQA+eEv2VPEI7qO+LDw901sHtKd9Kpt6Q=; b=iwElo8CXn0Sa3RQP1+vYecqeWfyG0zo92hbxqOncbNDsWxQptWYz0ONPhp/NjPhEyi MQl29JWEyv/55jZgfFEuhXWk+YRiguWYFExiixcMAjCcn/stSlsbusIf+dVXv6mKHdb+ lIxnX/N+7wknnUMqj8Pn3drfmaraBYihD3PXwhj1GbZWS7olDUFy04HJ7bTXAzDo+kRe MvvYCk7eYl9qDi7SOW5AkVp3oDmWc5VAOAEnSI7Jp8X1jGeYuTtrdavpgNyfeEEFZKtg f6XmfmC0l+l5kns4U3CGvAXqvOTDUNtFqw8WfEqBdDtkwI5cJjFcjEb/uqaGRbWcIc26 Xq4Q==
X-Gm-Message-State: APf1xPBE25XBwq28jjHYfmepUlJbEV1sxYLQzBz2+oaBaKL3eO/R2PQa OCrLzkR6dc72Jxb+00mSISfKqmUo
X-Google-Smtp-Source: AH8x22703GELKuEaASa/lmrZsyRA1JDr3ZMFzIF8rFmZ9bwFhmVUbqOn88AhLKkvQfAKETyA3qwgqw==
X-Received: by 10.107.129.12 with SMTP id c12mr6233043iod.303.1517983460487; Tue, 06 Feb 2018 22:04:20 -0800 (PST)
Received: from [10.207.114.36] ([202.45.12.164]) by smtp.gmail.com with ESMTPSA id 15sm917167iti.15.2018.02.06.22.04.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Feb 2018 22:04:19 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <d8d6d12f582545ce913284556d259d3b@scwexch12apd.uswin.ad.vzwcorp.com>
Date: Wed, 07 Feb 2018 15:04:17 +0900
Cc: "ila@ietf.org" <ila@ietf.org>, "Bogineni, Kalyani" <Kalyani.Bogineni@VerizonWireless.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <481EE606-3226-4679-8F0F-CBA4E2116B64@gmail.com>
References: <15c36020cfea41d0a93331ab4a3c0fdf@scwexch12apd.uswin.ad.vzwcorp.com> <B924DE6A-008D-40B4-9FA9-695DF1AEB02E@gmail.com> <d8d6d12f582545ce913284556d259d3b@scwexch12apd.uswin.ad.vzwcorp.com>
To: dmm <dmm@ietf.org>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/7T-JmOG9ybr53fSbiIWQ_MwhJIs>
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: Wed, 07 Feb 2018 06:04:23 -0000

Hello Kalyani,

Thank you for your feedbacks. I’ll take it into account.

And yes, slide 6 shows just one deployment scenario. A spreadsheet which I shared in my google drive would help to see the rest of scenarios.
Perhaps those would be deployed on somewhere in operators.

Cheers,
--satoru

> 2018/02/06 22:23、Bogineni, Kalyani <Kalyani.Bogineni@VerizonWireless.com>のメール:
> 
> Satoru:
>  
> Your slide 6 shows one implementation (other operators may have other implementations).
> Below is the Figure from CT4 TR 29.891. Can you show how your slide 7 impacts this
> end-to-end protocol stack and which interfaces are impacted?
>  
> <image002.png>
>  
>  
> Your slides 9 – 13 show interactions between UPFs and SMF. There are 2 kinds of UPFs:
> Anchor type UPF and service function type UPF. What are the functionalities of these?
> What are the changes in SMF functionalities to support SRv6? Is the interface between
> SMF and UPFs based on N4/Sx (PFCP in TS 29.244)?
> Also you show IPv6/SRv6 nodes in those slides. Are the UPFs ‘overlaid’ on IPv6/SRv6 nodes?
> Are these UPFs VNFs? Or are UPFs implemented on IPv6/SRv6 nodes?
>  
> It would be beneficial if you can provide clarifications and add a section to your draft.
>  
> Kalyani
>  
> -----Original Message-----
> From: Satoru Matsushima [mailto:satoru.matsushima@gmail.com] 
> Sent: Tuesday, February 6, 2018 2:53 AM
> To: Bogineni, Kalyani <Kalyani.Bogineni@VerizonWireless.com>
> Subject: [E] Re: review comments on ] draft-ietf-dmm-srv6-mobile-uplane-00.txt
>  
> Hello Kalyani,
>  
> >  Do you have a deck that shows 5G architecture, procedures and
> > services for your functions?
>  
> Hope you find it in a tdoc from the following link:
>  
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.3gpp.org_ftp_tsg-5Fct_WG4-5Fprotocollars-5Fex-2DCN4_TSGCT4-5F81-5FReno_Docs_C4-2D176177.zip&d=DwIFAg&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=IdiSODh8aDRjdCeGgd9MznLHMYKgKcs_YSwXBDiaofh47oilzaXYRYETcBynUdpT&m=v2OzLQOmEladDjJ7cnv7BOUHOIJU3q5_zuGVajrMM6U&s=vvhsviIu1Hxx94-BJWqR63wLWmlzMdhh_X8op2Xv_y4&e=
>  
> Cheers,
> --satoru
> <oledata.mso>

v2.23.0 | Report a Bug | By Email