IETF Logo Mail Archive

[Ila] Non-mobility functions in Uplane [was Re: review comments on ] draft-ietf-dmm-srv6-mobile-uplane-00.txt]

Satoru Matsushima <satoru.matsushima@gmail.com> Fri, 09 February 2018 08:53 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 1D6921205D3; Fri, 9 Feb 2018 00:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 Oy8Z_xVZtiyf; Fri, 9 Feb 2018 00:53:22 -0800 (PST)
Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (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 BE3631200E5; Fri, 9 Feb 2018 00:53:22 -0800 (PST)
Received: by mail-ot0-x22c.google.com with SMTP id m20so7047098otf.3; Fri, 09 Feb 2018 00:53:22 -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=qnj9i+BBZy44EZhjzr7SAHgmlItnKYgHwlKquAdW744=; b=McrLg8ZyJ1abz9hcqsrdg32tPcMZjtANG9leR7C//eGuYIvek3Hq5JGb7JaSx5d2WT twAADlU9A2/yiL06juDl5NY/Z5XNBwJNHnt3aaSAYFCdCDnLcHWBqG4rkoqWcaHsX6q2 QFj6wPUBTcc/31Nhsw258qbJpaQvV5tV5IeRIxyBusZb4zptTacxg4IPX43tjrxClAWH gHaQJYDTL8cwfngXGudMyy4yyHvuxUpl4gAzcS1Et4TjeYaSNwce62q6ISrnMofKd5OE +YpMr7Wrs49O95Aaf/joN17NeUMny4SX+A5ejmSOPlKKslaNZgoGj5zg4CYXShQyOFR0 i1+g==
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=qnj9i+BBZy44EZhjzr7SAHgmlItnKYgHwlKquAdW744=; b=YLIBqV3N4BOQI3czo6FFKmnrT1zRjqUXGgTPtkQY8TzD6dCWkWZrxGOKV65qHYsc4u YmfJvHBlvXddmW2uxVICFw14WNlCwfDsf8BQWXMBatNabEEZ/5jDpVVZQjDtkrj0580v d3v+xLxqR1rY3hgUdGtcjBr/Q2TVDHEwOId/LKLQmiJ4j3TGNLq0oQOo9GPMP5VjoqCo DrR/dGeuKkWLJjwBWKJ2bABvRsqhzCTH6JxBuuyniI4mMJYnJi06CVTbhodX+APdwsyZ xOwZ2sOqiN0FnPU1Dh/q27lL1GEv0G/u4J/ggszmM+zZr67/7QdotFfeG56LVDReOZj+ XwkQ==
X-Gm-Message-State: APf1xPAUh/Om6R8cOy3xEbAJmuOGiWV/ZPLqWQywbD8PHDVSHKDh30NA 6lFXFnQZcJFH2BYaiuO3BIg=
X-Google-Smtp-Source: AH8x224AKmcnMr6d2qJxQg4uhwneDEMm7OJTSCHFFctiz8AIFHxTmL2QDYFuGklFt+REJuXKGtmcnQ==
X-Received: by 10.157.56.220 with SMTP id k28mr1746269ote.193.1518166402049; Fri, 09 Feb 2018 00:53:22 -0800 (PST)
Received: from [10.207.113.120] ([202.45.12.164]) by smtp.gmail.com with ESMTPSA id 188sm1005077oid.1.2018.02.09.00.53.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Feb 2018 00:53:21 -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: <69d06c7ecd624291a868c3bb00cc3e49@scwexch12apd.uswin.ad.vzwcorp.com>
Date: Fri, 09 Feb 2018 17:53:17 +0900
Cc: "ila@ietf.org" <ila@ietf.org>, dmm <dmm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC69827A-AC57-4E52-918B-9FC81DDDA0D2@gmail.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>
To: "Bogineni, Kalyani" <Kalyani.Bogineni@verizonwireless.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/W383-QM70i6I_x0s4rOLI0DGQWg>
Subject: [Ila] Non-mobility functions in Uplane [was 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 08:53:25 -0000

Kalyani,
# Subject changed.

> 
> Maybe you can see SRv6 mobile uplane as a set of SRv6 functions like a SRv6 profile for mobile with some augment.
> 
> When it comes to service function type UPF, you name it. Following draft exhibits how service chain can be done by SRv6:
> [KB] I think these are non-mobility functions as being discussed on the email thread with Marco Liebsch.


I saw that discussion. Non-mobility functions of which deployed on SGi/Gi-LAN types can still be considered as functions deployed in N6.
IMO I couldn’t find that assumption in TS23.501. So it would be a clarification point whether those type of UP functions can be deployed within mobility management data path programmed by SMF utilizing (multiple) N9.

Thought?

Cheers,
--satoru

v2.23.0 | Report a Bug | By Email