
From nobody Tue Oct 12 03:31:32 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD343A0A98; Tue, 12 Oct 2021 03:31:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dmm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.39.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dmm@ietf.org
Message-ID: <163403468922.10708.6791247890767909755@ietfa.amsl.com>
Date: Tue, 12 Oct 2021 03:31:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/GTBA8EEgcwbMbmaxz5ethmrAvI8>
Subject: [DMM] I-D Action: draft-ietf-dmm-srv6-mobile-uplane-17.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2021 10:31:30 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Mobility Management WG of the IETF.

        Title           : Segment Routing IPv6 for Mobile User Plane
        Authors         : Satoru Matsushima
                          Clarence Filsfils
                          Miya Kohno
                          Pablo Camarillo Garvia
                          Daniel Voyer
                          Charles E. Perkins
	Filename        : draft-ietf-dmm-srv6-mobile-uplane-17.txt
	Pages           : 32
	Date            : 2021-10-12

Abstract:
   This document specifies the applicability of SRv6 (Segment Routing
   IPv6) to the user-plane of mobile networks.  The network programming
   nature of SRv6 accomplishes mobile user-plane functions in a simple
   manner.  The statelessness of SRv6 and its ability to control both
   service layer path and underlying transport can be beneficial to the
   mobile user-plane, providing flexibility, end-to-end network slicing,
   and SLA control for various applications.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-srv6-mobile-uplane/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-dmm-srv6-mobile-uplane-17.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-srv6-mobile-uplane-17


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Tue Oct 12 03:34:25 2021
Return-Path: <pcamaril@cisco.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 287343A0B17 for <dmm@ietfa.amsl.com>; Tue, 12 Oct 2021 03:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.596
X-Spam-Level: 
X-Spam-Status: No, score=-9.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=iNvHtOEn; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ZA/gkocE
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 xs8y-qJfwk-3 for <dmm@ietfa.amsl.com>; Tue, 12 Oct 2021 03:34:14 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D850B3A0FAE for <dmm@ietf.org>; Tue, 12 Oct 2021 03:34:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3461; q=dns/txt; s=iport; t=1634034853; x=1635244453; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=tlabKmDTBqSs9isBjorBaQDXw8snSLTv4yINk3xWSVg=; b=iNvHtOEn6LvbqPXswYzMUFGbj4IVocdvheCk/dF6PQx2npOaZqTCL5p7 WPw3C6yomj/uRqtFGuYVaoYYBjqRBS9aNmEDVXuVblDFC18pfdolGdbbX wkarNd8PlZ3FpOTQPv33jf+IjM9u7MMyWv9vg38A2aYnBkcPgrX8MQf5G g=;
IronPort-PHdr: =?us-ascii?q?A9a23=3ACSXgeR2rbCL7kunRsmDPT1BlVkEcU/3cMgsc8?= =?us-ascii?q?JFhir9SfOKk5ZuxdEDc5PA4iljPUM2b7v9fkOPZvujmXnBI+peOtn0OMfkuH?= =?us-ascii?q?x8IgMkbhUosVciCD0CoIPvjdSd8HcleWhli5X7oeURQEdz1MlvVpHD65DUOG?= =?us-ascii?q?xL5YAxyIOm9GoPbg8mtke6o/JiGaARTjz37arR3f32L?=
IronPort-Data: =?us-ascii?q?A9a23=3ALPpqva3lE2ToVyR88fbD5exzkn2cJEfYwER7X?= =?us-ascii?q?KvMYLTBsI5bpzVSm2QZWmyCPPmJY2Tzf91wPYq29UkP7JbVxtNjSgM53Hw8F?= =?us-ascii?q?HgiRegpqji6wuYcB84ZRyH6ZBoPA/42N5+QcajYcleG/k30a+C49yElvU21b?= =?us-ascii?q?uOU5NDsa3gZqTBMEE/NuTo78wIIqtYAbeqRWmthivuqyyHrA2JJ7hYvWo4iB?= =?us-ascii?q?w1vnzs01Bj6kGtwUlXT/pmntneG/5UeJMp3ya1csxLFrodo8u6SH44vzZmj9?= =?us-ascii?q?W/fuhwqEN7gz/Dwc1YBRfjZOg3mZnh+Avf5xEMd4H1plP9mapLwam8P49mNt?= =?us-ascii?q?8h6wdBEr520YQwoJabL3u8aVnG0FgkvYfMWpuGeeiLXXcu7iheun2HX6/lrC?= =?us-ascii?q?Wk3MJEWvOFtDglm5+4YITYCO0zbhf+wwaq2UK9qi9gLIMziJohZu3x8w3feF?= =?us-ascii?q?/lOfHxpa80m/vdC1zs2w8tJB/ubOowSaCFka1LLZBgnB7veM7pm9M/Au5U1W?= =?us-ascii?q?2cwRIqpmJcK?=
IronPort-HdrOrdr: =?us-ascii?q?A9a23=3A1uDvt6sSILW91OwOajSeJ44/7skCLoAji2?= =?us-ascii?q?hC6mlwRA09TyXGraGTdaUguyMc1gx/ZJh5o6H+BEGBKUmskqKdkrNhQ4tKOz?= =?us-ascii?q?OW+FdATbsSrLcKpgeBJ8SQzJ8n6U4NSdkaNDS0NykHsS+Y2nj6Lz9D+qj8zE?= =?us-ascii?q?nAv463pB0BIXAIGsNdBkVCe3um+yZNNW977O8CZeKhD7181kOdkBosH6CGL0?= =?us-ascii?q?hAe9KGi8zAlZrgbxJDLQUg8hOygTSh76O/OwSE3z8FOgk/g4sKwCzgqUjU96?= =?us-ascii?q?+ju/a0xlv3zGnI9albn9Pn159qGNGMsM4IMT/h4zzYIbiJGofy+Azdktvfrm?= =?us-ascii?q?rCo+O8+ivI+P4Ds085S1vF5icFHTOQiwrGpUWSk2NwykGT0PARDAhKe/apw7?= =?us-ascii?q?gpLycwLyEbzY5BOGUh5RPEi3MfN2KyoA3to9fPTB1kjUyyvD4rlvMSlWVWVc?= =?us-ascii?q?8EZKZWtpF3xjIZLH4sJlOw1GkcKpglMCgc3ocgTXqKK3TC+mV/yt2lWXo+Wh?= =?us-ascii?q?+AX0gZo8SQlzxbhmpwwUcUzNEW2i5ozuNzd7BUo+Dfdqh4nrBHScEbKap7Ge?= =?us-ascii?q?caWMOyTmjAWwjFPm6eKUnuUKsHJ3XOoZjq56hd3pDnRLUYiJ8p3JjRWlJRsm?= =?us-ascii?q?A/P0roFM2VxZVOtgvARW2sNA6dgv22J6IJ84EUYYCbfxFrZGpe5vdIks9vdP?= =?us-ascii?q?EzAczDSq6+K8WTWVfTJQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BOAAC3Y2Vh/5xdJa1aHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQFAgUUHAQELAYFQUQd3WjcxiA4DhFlgiAsDmm+BLhSBEQNUCwE?= =?us-ascii?q?BAQ0BAS0UBAEBhH4CgkgCJTQJDgECBAEBARIBAQUBAQECAQYEgREThWgNhkI?= =?us-ascii?q?BAQEBAxIVEwYBATcBCwQCAQgRBAEBHxAyHQgBAQQOBQgaglCCVQMvAaMfAYE?= =?us-ascii?q?6AoofeIEBMoEBgggBAQYEBIUKGII1CYE6AYMCiwgnHIFJRIEVQ4JnPoQQARI?= =?us-ascii?q?BI4NNgi6LGQEtRAExNoFrgTYskSgmrDgKgzCKRpREFINqi2yXQbtuAgQCBAU?= =?us-ascii?q?CDgEBBoFhO2lwcBWDJAlIGQ+OIAwWg1CJd2d0OAIGCwEBAwmUFQEB?=
X-IronPort-AV: E=Sophos;i="5.85,367,1624320000"; d="scan'208";a="946866132"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Oct 2021 10:34:12 +0000
Received: from mail.cisco.com (xbe-rcd-007.cisco.com [173.37.102.22]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id 19CAYCBb016381 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Tue, 12 Oct 2021 10:34:12 GMT
Received: from xfe-aln-004.cisco.com (173.37.135.124) by xbe-rcd-007.cisco.com (173.37.102.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Tue, 12 Oct 2021 05:34:12 -0500
Received: from xfe-rcd-002.cisco.com (173.37.227.250) by xfe-aln-004.cisco.com (173.37.135.124) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Tue, 12 Oct 2021 05:34:11 -0500
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xfe-rcd-002.cisco.com (173.37.227.250) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15 via Frontend Transport; Tue, 12 Oct 2021 05:34:11 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aKWSnxqUSqrBYn/005hqDSp8yygPo8O3fHV8A3lSZnL0Lm0lYctsLM1TPzcSiR8LN8S96Y+QQgqxa5IWZdMuF8cLiu7hVliOdH1ydb+kbS+59qsZErL7mccadhAR4O+cTr+TcN8R2Lh5PW4txqJdHztYUy9glGcRsVcYMcAy6/ck9RVD35gfcA7JO4vDrg+R3/sHJk3nPxnBYad0M6fozDgdmqvKYJNE0rEN6YEVOQLB5npoViiWqMJQH8tDY2YjtKgTLRVHw+t63OUt/w/ISqjb3cmf8vm/NuDijdJc2sdcgs7vigGykCRWnXokbfCbIR3hc9KQ/oKM6aoBwlIDsA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=yCqAL2o9t6RPC2vrjWiyHh8PCl13eOM5fKjYZTeGUWI=; b=Mp1AT/dn9lezWEVBCfk+TlX2Nbi+ogA6IF5VZAXiazb7sSul6YiweZKH8e1ypDwE4W4Y466lompC3bEa+V9DdHfNiZLwCufEyoGW94M/tkHw9a6+IqQYg5hm95aJGTEgnrKWKmQu+31G96yW9SzhhY6nlLJOUnKcFLuggXLhswEj7oEdED9NwLFpkknHoOxxgO/DVo8DGuIptNQcHkat7uGOJyJbU8tk45YtyTohKaAB4bKmoutDbt0ss7YaZbgJ6Nfls9tQvPKPnzzzMt6hUCCuvDIb6L4lh4mzwJxTsKvS8MK8kiQK3rxJxfGEej/FaRgWnH1BIJSvKbvVN919Fg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yCqAL2o9t6RPC2vrjWiyHh8PCl13eOM5fKjYZTeGUWI=; b=ZA/gkocENuf2cgQty8Mu+mGE6P0vsVw9jR9qPgIaHe7baddfwTWR/uqJquEgfRCS6qk1RfDgPU9sl2Qkj0D9b7SKk8iBrXfVrx06nH6dcVJYl6ZxLu4tBJnZcWZgoXAevkd/rrGop5UZKDEzA4A+fK4n9QnCR6LrEZnxTVufz0c=
Received: from DM8PR11MB5719.namprd11.prod.outlook.com (2603:10b6:8:10::6) by DM5PR11MB1834.namprd11.prod.outlook.com (2603:10b6:3:113::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4587.18; Tue, 12 Oct 2021 10:32:53 +0000
Received: from DM8PR11MB5719.namprd11.prod.outlook.com ([fe80::18ed:c961:785a:1fcb]) by DM8PR11MB5719.namprd11.prod.outlook.com ([fe80::18ed:c961:785a:1fcb%7]) with mapi id 15.20.4587.026; Tue, 12 Oct 2021 10:32:53 +0000
From: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang=40juniper.net@dmarc.ietf.org>
CC: "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: draft-ietf-dmm-srv6-mobile-uplane-16 comments
Thread-Index: AdeaJLOpII08EjY4Tw2u+OienVqWHQA+xR0Q
Date: Tue, 12 Oct 2021 10:32:52 +0000
Message-ID: <DM8PR11MB57190BD00878F021DEBB8BC3C9B69@DM8PR11MB5719.namprd11.prod.outlook.com>
References: <BL0PR05MB56524308DC54112C0A0BD5FBD4C79@BL0PR05MB5652.namprd05.prod.outlook.com>
In-Reply-To: <BL0PR05MB56524308DC54112C0A0BD5FBD4C79@BL0PR05MB5652.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=cisco.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 33580011-80fd-47ba-a559-08d98d6ba5af
x-ms-traffictypediagnostic: DM5PR11MB1834:
x-microsoft-antispam-prvs: <DM5PR11MB1834AFC5BCCF7B9FB218D2F0C9B69@DM5PR11MB1834.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Cd7LTyRRAYMYPQpA8NS7JPMqmLCSUXziSktyembVd3Ei6az9K2JQkJpOUYDsQvGxJi0gbGQ4kzlAk1hiUplCeBT/0pF+hL+KRlpBzI8ZMcQyZoKXDDRgLHlufWQ6ZlGkDIAqOMnDSWZattcfq7UX8wUqn1wRBA+0S4boDMoMszKrPQU8HU2BKeoVaRnAGYAIswas4BKWPDXFASQN3DuHvV2d2isYBoUAnfK3NctXd14p5+9z8jaVjwSD23tAwW2EvBdFtfZcCSHj7YT4kUgM4DqYDB/e2f2zRX7owEUKIofH5ji60aOf6FpQ31EAyZcBEKnsOQ3YsCkInaXy2GHasDmMq5UNWmq6SMGpon9w21KGA/iIiEV/9U0glnHeLRVFp7kN7mq5UU0KnOGqR5nYRR17FJEFe8lhvaPncTdtkXEip6GnweYe+g1kQjee9fvsxzw7rtpj5n9kzNZZKqn8hby8nNOytOWd8JEdZ/qtvUrGTYbIKO5bBa9op25JnBi0ZgMWfRBG6f1S/QnaJKjcbeUmz4hNU/w0S0EmUvgWOZxFdmwXLuKjXjd65svG324fa8MOOYSKCwMk5T1S7sxnpk/4oBU8iNrORkeOSusTa8rM5jRdck4IOQxGBBoKxWCZfTD1XV+yAtPt8/atieh1Fl8/yxm8tS1CYuCEQLc5g+en1oL8pEGcTzwa3gw/b3LjolaezNgh4n6gauEBgjOI628Yd+yZt2pw1HenV1xPb98=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM8PR11MB5719.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(366004)(316002)(52536014)(76116006)(508600001)(66946007)(8936002)(83380400001)(33656002)(9686003)(55016002)(186003)(71200400001)(26005)(38100700002)(122000001)(5660300002)(66446008)(53546011)(66476007)(64756008)(66556008)(6506007)(86362001)(38070700005)(8676002)(2906002)(7696005)(4326008)(21314003); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?MbJxe9N/TeJ2BGTC9+QhzwgwDxmNwWf8z/4fkpsnLf92nqcMxTBimwjwWuYp?= =?us-ascii?Q?slNs38dVrGEs3uEb0cjQTuk3FVUpwdKCzrvtUdWVpEjkIY+fiNNd+gwKyk5N?= =?us-ascii?Q?XsVauAcZgD88MYnklqEq++sddJn7v7EAZWN8oX3SzkIHnsf3xe7UrbtfBKOC?= =?us-ascii?Q?BF2ioz80VO3aajM/8y+CovL9R5wzWroBvSsJrjOxck1Sjn2MpdRC+LWebtDt?= =?us-ascii?Q?fJnyhWYXHGfF6jpo/OWueWMU/Ql6Yr9nD1Gc4izSJUGZQgzHgC4qTXAQVoSM?= =?us-ascii?Q?bAu3YYK6rQgU9XbrOLcJr6+QvZM2j7u1wPnwOY3gDHGHehcsYDdWFjYhN2uT?= =?us-ascii?Q?yjjKGyVCl4A+LZkW3EFdXPM+7dgpO1sJjjb8dQUVl8Djnm17extD3MRl4oG8?= =?us-ascii?Q?WmCMaysWOzK9UqG9ZAEsv3wfpAN4wiv/xCncxf5KKw+GQoGj/lKYFaQFy9uC?= =?us-ascii?Q?+5s3HIdD6vFukD32w0UkzpygbZ/RLRLAZ8DV1vUuTtZpe90p6Lo+bPFNmD1w?= =?us-ascii?Q?XcRL2arutlPZpYdODXA9zYpi5QyIn6Wg/oA39N+F6BOwMNYyQfm4JBJ4v1hR?= =?us-ascii?Q?Mtv6WbVdgEjZ9bDN/LiEhvd1nNxoVWouaI864yZEQ/hdgaVOH5cGvkijEq9H?= =?us-ascii?Q?dvSAwKAMNopbPFq4cEpA88cSD+D2fJYBy5HgfOUElsQ3HoI9xdPzsOIk4mfx?= =?us-ascii?Q?/r/8WbAw4U5JmGa7sGBzrIEIXnX6K9bdiR+UB2VYbAHe7xa+DyKLYhz7oY6Y?= =?us-ascii?Q?hR9nNH2uqAYJAt3T9mF21OWFiOvYK/G/8ofxXVX/f3RMjs51M1LJkBjIdcol?= =?us-ascii?Q?El6OHn0e3bJLwRaIMSnlNi63RgejnZZtBXvSQIsNn1NcYSIBARIUcWOOQIbc?= =?us-ascii?Q?9jApyrnPlLsUmx3QkPWF9ZacY6AdZecHhQsAEsuLFo07GhZ4U226pSdUu9Og?= =?us-ascii?Q?MmgXTWD4bKNAzUGTn8/F0sKwFbaHADZ1//y7hKv94rWE9bA0hvA6kXhSPE+A?= =?us-ascii?Q?p21PDHNdsKu6or9ZUulsCPeaFid9PmO0FbhXhB5WTBXPsm+gg0Swu0SAMz9Z?= =?us-ascii?Q?LGXvgYKqeREcJRYn2rB/VSpTYdP1EzY7RTwMAFLW7x8JGotqu9QJR53EslNA?= =?us-ascii?Q?mp/xSUfQdg2LUUt9B7Vbv2l+ylupuLsP2tWPRpckfXmj4JOS9QQvz2cveDsX?= =?us-ascii?Q?H4mEdjEiSzhyHcQxfx4f1ylLkMPXBGLv3i61mnWowTng32dmakdDvR0ofK25?= =?us-ascii?Q?xXQ7NKx/iziar4D3nQwczuKRGSuIgKpzWPU80DJYp1Ta5+PpXOrZks35fTRb?= =?us-ascii?Q?sOUGYFnPcw6/YR4TmcvBNaNS?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM8PR11MB5719.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 33580011-80fd-47ba-a559-08d98d6ba5af
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Oct 2021 10:32:52.8951 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 3STss/Hq5HqX/udt/NLBxtatx04wd/Inz5sIrE4kH/BpdCkgFDhnj6X16cElJ3M4JzpUTFZZsxwk3pN2V0FlLg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1834
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.22, xbe-rcd-007.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/xm7_sJBj1mAp25oIQJVSWxz82No>
Subject: Re: [DMM] draft-ietf-dmm-srv6-mobile-uplane-16 comments
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2021 10:34:20 -0000

Hi Jeffrey,

In 5.3, in the downlink, you want to have a SID at the SRGW. This allows yo=
u to a) have the packet FlexAlgo routed up to the SR GW; b) trigger a parti=
cular SRv6 behavior at the GW. There is no benefit in using PBR in the gate=
way to trigger the mapping.

Regarding your comments:
- On (A,Z) usage being inconsistent: Please specify the page or section. I =
don't spot it. Thanks.
- On the 5.3.1 typo, fixed (rev17).

Cheers,
Pablo.

-----Original Message-----
From: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>=20
Sent: jueves, 26 de agosto de 2021 5:21
To: Pablo Camarillo (pcamaril) <pcamaril@cisco.com>
Cc: dmm@ietf.org
Subject: draft-ietf-dmm-srv6-mobile-uplane-16 comments

Hi Pablo,

I have not got a chance to go through -16 closely to correlate to our email=
 discussions, but I have the following comments.

Previously:

-------------
In 5.3, for uplink traffic, the GW has End.M.GTP6.D for the UPF address B a=
nd the gNB does not need to know the existence of GW. For downlink traffic,=
 the UPF knows there is a GW and put the GW::TEID in the SRH. Why not make =
GW invisible to UPF as well and just use gNB::TEID, and then have gNB/96 as=
 End.M.GTP6.E on the SRGW? You can still put GW in the SRH to steer traffic=
 through the GW.
[PC] That is a valid point. I'll think about it and get back to you.
-------------

I think we should get a conclusion on this.
Similarly, even for the drop-in mode, SGA can use (U::TEID, C1; SL=3D3) for=
 uplink traffic instead of using (U::1, SGB::TEID, C1; SL=3D3). Then, on SG=
B, U/96 can be a End.M.GTP6.E. With that, we don't need End.M.GTP6.D.Di any=
more, and End.M.GTP6.E will be like others - checking for "Segments Left !=
=3D 0" instead of " Segments Left !=3D 1" (no need to use SRH[0] as destina=
tion address of the GTP packet).

BTW - 5.4 drop-in mode only talks about uplink traffic. I suppose downlink =
traffic is the same - either use End.M.GTP6.D.Di or just use End.M.GTP6.D w=
ith (gNB::TEID, ...).
In fact, drop-in mode is not thing special any more - it's just that there =
is an SGB attached to the UPF as well as an SGA attached to the gNB like in=
 5.3.1.

Please see the following additional comments (more may come when I get a ch=
ance to comb through).

(Z,A) or (Z,A) is used to denote the source/destination address of PDU pack=
et. Then, for End.M.xxx behaviors, A is used to denote something different.=
 Better change the A to a different letter in either the PDU packets or in =
the End.M.xxx behaviors to avoid confusion.

End.M.GTP6.D has the following operation:

   S02.    Copy the GTP TEID to buffer memory
   ...
   S08.    Write in the last SID of the SRH the Args.Mob.Session
              based on the information of buffer memory

   With that, the U2::1 should be changed to U2::TEID in the following:

5.3.1.1.  Packet flow - Uplink

   The uplink packet flow is as follows:

   UE_out  : (A,Z)
   gNB_out : (gNB, B)(GTP: TEID T)(A,Z)       -> Interface N3 unmodified
                                                 (IPv6/GTP)
   SRGW_out: (SRGW, S1)(U2::1, C1; SL=3D2)(A,Z) -> B is an End.M.GTP6.D
                                                 SID at the SRGW
   S1_out  : (SRGW, C1)(U2::1, C1; SL=3D1)(A,Z)
   C1_out  : (SRGW, U2::1)(A,Z)               -> End with PSP
   UPF2_out: (A,Z)                            -> End.DT4 or End.DT6

Thanks.
Jeffrey


From nobody Tue Oct 12 03:34:34 2021
Return-Path: <pcamaril@cisco.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C6773A0B62 for <dmm@ietfa.amsl.com>; Tue, 12 Oct 2021 03:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.596
X-Spam-Level: 
X-Spam-Status: No, score=-9.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=BiNuuAHK; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=b21NjOKp
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 lysVUZQpt8vr for <dmm@ietfa.amsl.com>; Tue, 12 Oct 2021 03:34:14 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3CF23A11ED for <dmm@ietf.org>; Tue, 12 Oct 2021 03:34:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=28494; q=dns/txt; s=iport; t=1634034854; x=1635244454; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=XBa9aNIwOhuR2AtDYHzbvXVIFjQZmQ6S/KnEX7RifE4=; b=BiNuuAHKTAh8/TdL/FhtQVzobJc3roMJCW/GKw6hIn6vrfdQxmjoviEi UNCbgJzm5T8bAvBPtKKx8u/r8IoEM2/xY5liHejRJBxoiJG9WS8X8mj9g 2bmA9GZaNhkSaS5By8lV1pIzsqfsSezf3v6nlkUMJWEfY5FA2QoWY51me s=;
IronPort-PHdr: =?us-ascii?q?A9a23=3Ai70BFxVO8Q3KEMWVY8egZlzU+AnV8K0aAWYlg?= =?us-ascii?q?6HPw5pCd6259NLjMVDRo/J3gwyBUYba7qdCjOzb++DlVHcb6JmM+HYFbNRXV?= =?us-ascii?q?hADhMlX+m5oAMOMBUDhavK/aSs8EZdOUVZ/9De6PFRbXsHkaA6arni79zVHH?= =?us-ascii?q?BL5OEJ8Lfj0HYiHicOx2qiy9pTfbh8OiiC6ZOZ5LQ69qkPascxF6bY=3D?=
IronPort-Data: =?us-ascii?q?A9a23=3Al1miJqiBcIZsEqff0Z1A36C2X161XxIKZh0uj?= =?us-ascii?q?C45NGQN5FlHY01jehtvXGCDb/yKYGDyKItyO9yw9UgEvZ6HztNhTQtuqiljQ?= =?us-ascii?q?XhjpJueD7x1DKtf0wB+jyH7ockOA/w2MrEsF+hpCC+BzvuRGuK59yAljfjSH?= =?us-ascii?q?uOU5NPsY0ideyc1EE/Ntjo78wIJqtYAbemRW2thi/uryyHsEAfNNwpPD44hw?= =?us-ascii?q?/nrRCWDExjFkGhwUlQWPZintbJF/pUfJMp3yaqZdxMUTmTId9NWSdovzJnhl?= =?us-ascii?q?o/Y1w0mBtXgmbHhfwhaBLXTJgOJzHFRXsBOgDAb+Xd0ifl9ZaFaMBsL49mKt?= =?us-ascii?q?4gZJNFlrZe5TA4zP6nkk+UGWB4eGCZ7VUFD0O6deSHg4JLDniUqdFOpmZ2CF?= =?us-ascii?q?noeMYgd0ud6HW8I8uYXQBgffBCKge3jnOq5V+9tnsk5as/mIKsTv3h6xnfYA?= =?us-ascii?q?OooB5fZTM33CXVwtNsrrtpFEfCbbM0DZH8/Kh/BeBZIfFwQDfoDcC6TriGXW?= =?us-ascii?q?1VlRJi9/MLbO1Tu8TE=3D?=
IronPort-HdrOrdr: =?us-ascii?q?A9a23=3Afey0q6F9/r74YpQMpLqFsJLXdLJyesId70?= =?us-ascii?q?hD6qkvc31om52j+fxGws516fatskdvZJkh8erwX5VoMkmsi6KdhrNhfYtKPT?= =?us-ascii?q?OW+VdASbsD0WKM+UyaJ8STzJ856U4kSdkDNDSSNyk4sS+Z2njDLz9I+rDum8?= =?us-ascii?q?rE6Za8vhVQpENRGtxdBmxCe2Cm+zhNNXF77O0CZeOhD6R81l6dUEVSSv7+Km?= =?us-ascii?q?gOXuDFqdGOvonhewQ6Cxku7xTLpS+06ZbheiLonCs2Yndq+/MP4GLFmwv26u?= =?us-ascii?q?GIqPeg0CLR0GfV8tB/hMbh8N1eH8aB4/JlbwkEyzzYILiJaYfy+gzdk9vfsW?= =?us-ascii?q?rCV+O8+yvICv4DrE85uFvF+icFlTOQigrGoEWSuGNwyUGT0fARAghKVvaoQe?= =?us-ascii?q?liA0TkA41KhqAh7EsD5RPri7NHSRzHhyjz/N7OSlVjkVe1u2MrlaoJg2VYSp?= =?us-ascii?q?Z2Us4dkWUzxjIfLH47JlOx1GnnKpgYMOjMoPJNNV+KZXHQuWdihNSqQ3QoBx?= =?us-ascii?q?+DBkwPoNac3TRalG1wixJw/r1Rol4QsJYmD5VU7eXNNapl0LlIU88NdKp4QO?= =?us-ascii?q?MMW9G+BGDBSQ/FdGiSPVPkHqcaPG+lke+63JwloOWxPJAYxpo7n5rMFFteqG?= =?us-ascii?q?4pYkrrTdaD2ZVamyq9CFlVnQ6dg/22wqIJ9IEUaICbRBFreWpe5fdI+c9vcP?= =?us-ascii?q?Ezc8zDTK5rPw=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BzAABFZGVh/5BdJa1QCh0BAQEBCQE?= =?us-ascii?q?SAQUFAUCBRQgBCwGBUCMuB3daNzGIDgOEWWCICwOQFYpagS4UgREDVAsBAQE?= =?us-ascii?q?NAQEtFAQBAYR+AoJIAiU0CQ4BAgQBAQESAQEFAQEBAgEGBIERE4U7AQYmDYZ?= =?us-ascii?q?CAQEBAQMSCA0TBgEBNwELBAIBCBEBAwEBHxAyFwYIAQEEDgUIEweCUIJVAy8?= =?us-ascii?q?Box4BgToCih94gQEygQGCCAEBBgQEhQoYgjUJgToBgwKKDXsnHIFJRIEUAUO?= =?us-ascii?q?CFVI+g30TAQEGBQYBBxwFHxKDF4IuixkBEFsGATEMJgQUDhAJCAgoJgojCB0?= =?us-ascii?q?YFQgNBAEKFAEEAQEBJwYFAwENMpFOByuqY4EjCoMwnwoUg2qLbIZGkHuYRZ4?= =?us-ascii?q?nDA2EaQIEAgQFAg4BAQaBYTtpcHAVO4JpCUgZD4hKbIRqDBaDUIV0hGkBdDg?= =?us-ascii?q?CBgsBAQMJkU8BBgoXgh4BAQ?=
X-IronPort-AV: E=Sophos;i="5.85,367,1624320000"; d="scan'208";a="920179689"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Oct 2021 10:34:12 +0000
Received: from mail.cisco.com (xbe-rcd-001.cisco.com [173.37.102.16]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 19CAYC6x025885 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Tue, 12 Oct 2021 10:34:12 GMT
Received: from xfe-rcd-002.cisco.com (173.37.227.250) by xbe-rcd-001.cisco.com (173.37.102.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Tue, 12 Oct 2021 05:34:12 -0500
Received: from xfe-rcd-002.cisco.com (173.37.227.250) by xfe-rcd-002.cisco.com (173.37.227.250) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Tue, 12 Oct 2021 05:34:11 -0500
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xfe-rcd-002.cisco.com (173.37.227.250) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15 via Frontend Transport; Tue, 12 Oct 2021 05:34:11 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZGIyfYFr/n0AbJZtMJn54/hwwymI1HquW68MtGKOhhap/tD/rGvzU7FOSLQxvsoLVlooTqGXHiI7xRDCwpLwuQtJBw5dXelCgt1hpnzda3MA6TsJzwsmdEkbkWI12baK1sM0J35PtVJUikBd3b8cSNMiXjy+tEzY8GoIg/WsK2RDMySdX1DXjjzS0rAqpm3whrOhzIM5UvI2J98l0Kuw99myWOw6idy3XvRz9s4jRrVDhSz9z7U/QupJ9X6RbGuQRGZNlzHMxTjBdtTzNa9NKlHPx1JsmlwwkN8Zphd4N55jM3X4xhrm5L/1l1xNXjkcsv85wdM1MR3ybnjEW8Ps8Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=xfm6+VQirNTg4pif24cSbY9fl4HPEvtDx2HLFF6Bl5A=; b=XuxuwNdZ6hJF3YXcJwJRlKC+++AJv4/mQgoPYpUxYYyOIAvYYN6ot8F834bUEIbRs+0T5Mgz+13GsWtx8i5vJnE3+0uUu0VJoj/miMiUNxlKr6WBB1EghACemL8KR95I6Mx9dA2OBxCn2lL3/PbaQH/Y7brFGMEK0M22WbApQFC+htJiWqqdjoWZ3voi/BHPGOjmx09BVByecM033RAn5GWO1tENzVIKokPdmkSc1HNgwPPp1l/9NBiCpCeWg5mGRIpiiHiDu7hTZgX5+2A8HQ1yYxiPRp4ESR2UriYvr/4cMksamD+SnUnVljdKhoxby+C/rTA3+PKuEpegSbFc+Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xfm6+VQirNTg4pif24cSbY9fl4HPEvtDx2HLFF6Bl5A=; b=b21NjOKpdl9+Nlj8Rnx+QnR293dVPr+DYZwsMWodMSpTs1NvBzUZMTHR29PTxp4QTeY6QLLxOOybujT5/L1wusbc9lQ6dSOt6bNbeQneAxQjqP6s2LsjWks/wkVV5v6jw2DTU0yG4ZzyqiQzhq5ydpJduWOvHxLNumFI4DctVYE=
Received: from DM8PR11MB5719.namprd11.prod.outlook.com (2603:10b6:8:10::6) by DM5PR11MB1834.namprd11.prod.outlook.com (2603:10b6:3:113::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4587.18; Tue, 12 Oct 2021 10:32:55 +0000
Received: from DM8PR11MB5719.namprd11.prod.outlook.com ([fe80::18ed:c961:785a:1fcb]) by DM8PR11MB5719.namprd11.prod.outlook.com ([fe80::18ed:c961:785a:1fcb%7]) with mapi id 15.20.4587.026; Tue, 12 Oct 2021 10:32:55 +0000
From: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang=40juniper.net@dmarc.ietf.org>
CC: "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: Additional draft-ietf-dmm-srv6-mobile-uplane-16 comments
Thread-Index: Adeau+zJ0JiEFvVCSi6KXkk8Vn57PgAZUYEw
Date: Tue, 12 Oct 2021 10:32:55 +0000
Message-ID: <DM8PR11MB57196E9C38080AF7AE2A45D2C9B69@DM8PR11MB5719.namprd11.prod.outlook.com>
References: <BL0PR05MB56524662FCFD3167BAE04737D4C79@BL0PR05MB5652.namprd05.prod.outlook.com>
In-Reply-To: <BL0PR05MB56524662FCFD3167BAE04737D4C79@BL0PR05MB5652.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=cisco.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f9423a15-3279-4b50-98aa-08d98d6ba71f
x-ms-traffictypediagnostic: DM5PR11MB1834:
x-microsoft-antispam-prvs: <DM5PR11MB1834BA3ACDA711B58958C831C9B69@DM5PR11MB1834.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: lBwggVNJvDIPwNkdAiX47uUbujeiZT1DrmB703aWFrBMm+3nwtlMTzBBG2lV5hDhSm5SpEfncpfZbvHCgks2H2zYE+PFYvCIcAR+Mc8bY861WDDCUun0Vhtr4Urgek7ymaNtg36/drHMoXcb2Sy8s5ko0Ob5zO9nER6NVBzctNNLn6D1jU4Nx6WniW8E97kYEYb3iCc5sIWcL32G2XuL4IxsdvgZBM4H63xZSMddv+h6hG6udVOXEkAAuMJpYw/Dd8mhNXVV4dVowCwDzsX1PZ0hJVqg3R/4e+dzl8BHhzFgKDnXovFb2gAG0hYHp/YJ5NKbwfq1hLqIftbtx4MxfHBcWecu2mB7PBeTAq4239eFToOzGya9cwaJixHOwHeQ47nP+Qcfj7KYrWGHWy6fFHA+lIChVR4UdG0JK+UV60WnCviOR9Bjmzej2M3aXJzu16jwPWamZErsxc4SMgolUusUsfWgHWnTdyvarsG1Ud5cUVizC6PAXlqVwAWkEKqGy1tK04cqYEjNnuaYrriqh+mj5PRGcw6u77wGXIOAp4J6G56Hg98lij1HrOkbvFiKht2z73u+jcPm1OHCevC1o5NlUrSFeC/SZlOub9r8SVZf5oA++tHoNfF5PHq6gVLGVErj/vnuxVKHR1Cap8mttq1vMiM5YJC7cMEsi+W4fVLMu5Ddy/gZmL0ef3Af30I0pFSN4lSjxVbpNcGcww5IrA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM8PR11MB5719.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(366004)(316002)(52536014)(76116006)(508600001)(66946007)(8936002)(83380400001)(33656002)(9686003)(55016002)(30864003)(186003)(71200400001)(26005)(38100700002)(122000001)(5660300002)(66446008)(53546011)(66476007)(64756008)(66556008)(6506007)(86362001)(38070700005)(8676002)(2906002)(7696005)(4326008)(579004)(559001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?yB4p5oSltOKi/zAqd/wofmys3UY7mqDMUSKbEOt5Q1+dtI37vBAmAh/EPZXc?= =?us-ascii?Q?6w0nbj/WW9ZS6quiOkbBluZzH+Q5RyQYWhPQ4sn3wKWbj/cqj/2781MqDi//?= =?us-ascii?Q?kM1z7iLp4gib6d4CWevai7MklqMQbe9iZZMAPoXqnomsQW3o3brUZcxDESFD?= =?us-ascii?Q?k4067aayUfWxKjGtMMtpV+c2vmpmk+QCAilUJDd35P0ccOmXqLA/oezgAHAk?= =?us-ascii?Q?RHXWmyt1uUt+tAm9u2ReB4GOLrDoaY7ojC2Qfe/nOH1JHbs4VOaV7kqodgUO?= =?us-ascii?Q?zhqF+UkD2SsruvRsw9Ji3sp7Tc31zjlq++MwJMi+Ib/br6clIaar+QoZW7+y?= =?us-ascii?Q?vgkCq5oBmuEs52Wqp3pc7U4de38Om2c3rnkT+9cz17IfWUNJTGlnbu327BZK?= =?us-ascii?Q?sw80L04fVcBSEe1/OB8RYoZVh8YvwU2Spv/UGehKESYro2IPj35UFG6pMMLw?= =?us-ascii?Q?GC2oLGosO3JdsFkNEA1FibeuN61lpWuR4K2RCWHdaFSpaFSxyLItKuxZ3JyO?= =?us-ascii?Q?BsIcpJP/vkcxfWbvQZtwiF6pNeBY2bgQlcDQgg6mh1fS2izcKq7WDMPSufe/?= =?us-ascii?Q?/5SNA1+bkePz+WDgYGv96dmIepL8xMq6SMqgG7nfb7oIxh4OTOtF1d6EuE3c?= =?us-ascii?Q?eO4e+lu2oZxLCOHobXecDFCcMo25av7kuez3AJJTNmPqxt+/vXCAI9d1fO21?= =?us-ascii?Q?NSKVJSfKNI+OPncuxtyzpuJ6IMEPCposC+ELtvs9tgNtt/cttxhRazVgs1B8?= =?us-ascii?Q?shq5O4XplFpaONt2TpsTm8P+xFv3cvvzaFIcjSDzVG1HE+WvarMHpAbvcceg?= =?us-ascii?Q?bs4puBse/BawuLO5qvCsuOqyoK05Atfb6JltYS88E62KuxZoiNI6RiBAhoAs?= =?us-ascii?Q?oN743rDvR2aXJWLIrSBB1X29sc6JGlHQRKVOcpOe+tfH9qJz46PauqFmoKib?= =?us-ascii?Q?B9dHPid1rQ5IHb7wFeWfTTaUpNC7vxVElcdxUOevvZuvtg7v35a+QFI3MySr?= =?us-ascii?Q?U2R63Nafu2M4wBVCoZSXIn81aXVivdnOAzbEr4OGQZrukElKixaPxBVYbqJ5?= =?us-ascii?Q?27/RyWrZkAkHQocEQSDkv3cJmaQjOKtc4HeS984HhnoT69Guu6w/mYpgbTO/?= =?us-ascii?Q?W1O8FYmqvtzY1/Sc4NqiHLHzgfhrs3NpLQ/JSZMd4YX9GL2IRDwGASJrw/s1?= =?us-ascii?Q?LIm6PR6eS5jKz//ljuxv8doh3hVTrbsIck2pomBSCUsD3bMbhCeCdMuEosuf?= =?us-ascii?Q?vJgOlPftBhDcEbHXAF0mWvybCYbv7dNftbDzoErhQsbF5v0e1s2xCdVmmYhz?= =?us-ascii?Q?dcbDnNccaGI6egQznTqA5b6M?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM8PR11MB5719.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f9423a15-3279-4b50-98aa-08d98d6ba71f
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Oct 2021 10:32:55.3025 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: tNnR6dzL3IKNqSyB88XL34qaZPrGw6E31/TYtc3A1G5hmelsw9QdH6b/KfgleBfAcaesN7a5OHwB3TEvffTYog==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1834
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.16, xbe-rcd-001.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/4VrB9lkc90ubIY1U5fqUz-lkC0o>
Subject: Re: [DMM] Additional draft-ietf-dmm-srv6-mobile-uplane-16 comments
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2021 10:34:23 -0000

Hi Jeffrey,

Inline with PC. New version of the draft posted (rev17).

Thanks,
Pablo.

-----Original Message-----
From: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>=20
Sent: viernes, 27 de agosto de 2021 1:01
To: Pablo Camarillo (pcamaril) <pcamaril@cisco.com>
Cc: dmm@ietf.org
Subject: Additional draft-ietf-dmm-srv6-mobile-uplane-16 comments

Hi Pablo,

Some editorial/nit comments and some more substantial questions/comments be=
low.

   In mobile networks, mobility management systems provide connectivity
   over a wireless link to stationary and non-stationary nodes.  The
   user-plane establishes a tunnel between the mobile node and its
   anchor node over IP-based backhaul and core networks.

A nit question - why "management" systems? That sounds like user plane is n=
ot involved.
[PC] "Management" removed.

   This document shows the applicability of SRv6 (Segment Routing IPv6)
   to mobile networks.

This document is not just "showing" the applicability. It actually specifie=
s how it is done, right?
[PC] s/shows/specifies

   Segment Routing [RFC8402] is a source routing architecture: a node
   steers a packet through an ordered list of instructions called
   "segments".  A segment can represent any instruction, topological or
   service based.

   SRv6 applied to mobile networks enables a source-routing based mobile
   architecture, where operators can explicitly indicate a route for the
   packets to and from the mobile node.  The SRv6 Endpoint nodes serve
   as mobile user-plane anchors.

The last sentence is not exactly true. The SRv6 endpoint nodes could be GWs=
.
[PC] Feel free to propose a different text. In the traditional and enhanced=
 mode the SRv6 endpoints are the mobility user-plane anchors.

   The second mode is the "Enhanced mode".  This is an evolution from
   the "Traditional mode".  In this mode the N3, N9 or N6 interfaces
   have intermediate waypoints -SIDs- that are used for Traffic
   Engineering or VNF purposes.  This results in optimal end-to-end
   policies across the mobile network with transport and services
   awareness.

s/purposes/purposes transparent to 3GPP functionalities/
[PC] Changed.

5.1.  Traditional mode

   In the traditional mode, the existing mobile UPFs remain unchanged
   with the sole exception of the use of SRv6 as the data plane instead
   of GTP-U.  There is no impact to the rest of the mobile system.

   In existing 3GPP mobile networks, a PDU Session is mapped 1-for-1
   with a specific GTP tunnel (TEID).  This 1-for-1 mapping is mirrored
   here to replace GTP encapsulation with the SRv6 encapsulation, while
   not changing anything else.  There will be a unique SRv6 SID
   associated with each PDU Session, and the SID list only contains a
   single SID.

Does "a unique SRv6 SID associated with each PDU Session" mean that gNB/UPF=
 will have those individual unique SIDs installed in the forwarding plane"?
[PC] Yes... in the same way today they need to have the GTP-U tunnel parame=
ters installed in the forwarding plane. Not sure I get your point.

   The traditional mode minimizes the changes required to the mobile
   system; hence it is a good starting point for forming a common
   ground.

   The gNB/UPF control-plane (N2/N4 interface) is unchanged,
   specifically a single IPv6 address is provided to the gNB.  The same
   control plane signalling is used, and the gNB/UPF decides to use SRv6
   based on signaled GTP-U parameters per local policy.  The only
   information from the GTP-U parameters used for the SRv6 policy is the
   TEID and the IPv6 Destination Address.

Also QFI?
[PC] Added.

   Our example topology is shown in Figure 2.  In traditional mode the
   gNB and the UPFs are SR-aware. =20

Strike "In traditional mode"?
[PC] Removed.

5.1.1.  Packet flow - Uplink

   The uplink packet flow is as follows:

         UE_out  : (A,Z)
         gNB_out : (gNB, U1::1) (A,Z)     -> H.Encaps.Red <U1::1>
         UPF1_out: (gNB, U2::1) (A,Z)     -> End.MAP
         UPF2_out: (A,Z)                  -> End.DT4 or End.DT6

   When the UE packet arrives at the gNB, the gNB performs a
   H.Encaps.Red operation.  Since there is only one SID, there is no
   need to push an SRH. gNB only adds an outer IPv6 header with IPv6 DA
   U1::1.  U1::1 represents an anchoring SID specific for that session
   at UPF1. gNB obtains the SID U1::1 from the existing control plane
   (N2 interface).

The last sentence is misleading. SID U1::1 is constructed by gNB and it sho=
uld really be U1::TEID where U1 is the "single IPv6 address is provided to =
the gNB".
[PC] Reverted the order of those two last sentences which I believe improve=
s readability.

   When the packet arrives at UPF1, the SID U1::1 is associated with the
   End.MAP SRv6 Endpoint Behavior.  End.MAP replaces U1::1 by U2::1,
   that belongs to the next UPF (U2).

U::1 should be U1::TEID1, and U2::1 should be U2::TEID2?
[PC] As stated in the draft "U1::1 represents an anchoring SID specific for=
 that session at UPF1."
[PC] and actually I would expect all the addressing of this document to be =
changed to 2001::db8:: as it goes through IESG...

   Thus, the main difference is that the SR policy MAY include SIDs for
   traffic engineering and service programming in addition to the
   anchoring SIDs at UPFs.

   Additionally in this mode the operator may choose to aggregate
   several devices under the same SID list (e.g., stationary residential
   meters connected to the same cell) to improve scalability.


   Figure 3 shows an Enhanced mode topology.  In the Enhanced mode, the
   gNB and the UPF are SR-aware. =20

Strike "In the Enhanced mode"?
[PC] Done.

5.2.1.  Packet flow - Uplink

   The uplink packet flow is as follows:

   UE_out  : (A,Z)
   gNB_out : (gNB, S1)(U1::1, C1; SL=3D2)(A,Z)->H.Encaps.Red<S1,C1,U1::1>
   S1_out  : (gNB, C1)(U1::1, C1; SL=3D1)(A,Z)
   C1_out  : (gNB, U1::1)(A,Z)              ->End with PSP
   UPF1_out: (A,Z)                          ->End.DT4,End.DT6,End.DT2U

   UE sends its packet (A,Z) on a specific bearer to its gNB.  gNB's
   control plane associates that session from the UE(A) with the IPv6
   address B.  gNB's control plane does a lookup on B to find the
   related SID list <S1, C1, U1::1>.

   When gNB transmits the packet, it contains all the segments of the SR
   policy.  The SR policy includes segments for traffic engineering (C1)
   and for service programming (S1).

As we have discussed before, you either need to use U1::TEID so that UPF1 c=
an use the TEID to determine in which table to do End.DT2/4/6, or you need =
to point out that different U1 addresses need to be used for different tabl=
es.
[PC] Based on your previous feedback we already added in rev16 the last par=
agraph of 5.2.2.


5.2.2.  Packet flow - Downlink

   The downlink packet flow is as follows:

   UPF1_in : (Z,A)                             ->UPF1 maps the flow w/
                                                 SID list <C1,S1, gNB>
   UPF1_out: (U1::1, C1)(gNB::1, S1; SL=3D2)(Z,A)->H.Encaps.Red
   C1_out  : (U1::1, S1)(gNB::1, S1; SL=3D1)(Z,A)
   S1_out  : (U1::1, gNB::1)(Z,A)              ->End with PSP
   gNB_out : (Z,A)                             ->End.DX4/End.DX6/End.DX2

   When the packet arrives at the UPF1, the UPF1 maps that particular
   flow into a UE PDU Session.  This UE PDU Session is associated with
   the policy <C1, S1, gNB>.  The UPF1 performs a H.Encaps.Red
   operation, encapsulating the packet into a new IPv6 header with its
   corresponding SRH.

   The nodes C1 and S1 perform their related Endpoint processing.

   Once the packet arrives at the gNB, the IPv6 DA corresponds to an
   End.DX4, End.DX6 or End.DX2 behavior at the gNB (depending on the
   underlying traffic).  The gNB decapsulates the packet, removing the
   IPv6 header, and forwards the traffic towards the UE.  The SID gNB::1
   is one example of a SID associated to this service.

Same as above. gNB::1 in the last sentence above is not enough - gNB::TEID =
needs to be used to do End.DX2/4/6.
[PC] The value of the SRv6 Service SID assigned does not need to include th=
e TEID. Hence using gNB::TEID seems incorrect to me. Instead one particular=
 SID is associated with the service. The last paragraph highlights exactly =
that.

   Note that there are several means to provide the UE session
   aggregation.  The decision on which one to use is a local decision
   made by the operator.  One option is to use the Args.Mob.Session
   (Section 6.1).  Another option comprises the gNB performing an IP
   lookup on the inner packet by using the End.DT4, End.DT6, and End.DT2
   behaviors.

To clarify, when I say gNB::TEID, I do refer to use of Args.Mob.Session. I =
don't think we should be shy from calling out gNB::TEID.
If you want to do End.DT2/4/6 on gNB, the following should be pointed out:

- this is a change of gNB behavior
- we still need a way to identify in which table to do it - and like in the=
 uplink case, you either use TEID or use different gNB addresses.

[PC] The draft currently allows both options. Its an operational choice fro=
m the operator to select one. I have a personal preference over Args.Mob.Se=
ssion, but an operator might prefer the other option hence keeping both opt=
ions available.

5.2.3.  Scalability

   The Enhanced Mode improves since it allows the aggregation of several
   UEs under the same SID list.  For example, in the case of stationary
   residential meters that are connected to the same cell, all such
   devices can share the same SID list.  This improves scalability
   compared to Traditional Mode (unique SID per UE) and compared to
   GTP-U (dedicated TEID per UE).

The scalability improvement comes when you don't need to use TEID for the f=
ollowing:

- for uplink, determining the table in which to do End.DT2/4/6
- End.DX2/4/6 for downlink (End.DT2/4/6 will be used).

[PC] SRv6 identifies services by using a different SID.
In both cases, different UPF or gNB addresses are needed to determine the t=
able.
[PC] Same as with any SRv6 solution -not specific to SRv6 mobile- no? I don=
't see the difference with respect to RFC8986.
That should be clarified, including how the addresses are determined.

5.3.1.  Interworking with IPv6 GTP

   *  The 5G Control-Plane towards the gNB (N2 interface) is unmodified;
      one IPv6 address is needed per SLA(i.e. a BSID at the SRGW).  The
      SRv6 SID is different depending on the required SLA.

Is it that the N2 signaling *encoding* is not changed, but *content* is ind=
eed changed so that different IPv6 addresses can be given for different SLA=
/tenant?
[PC] The content is still an IPv6 address. The IPv6 address is different de=
pending on the required SLA (as stated in the text).

   *  There is no state for the downlink at the SRGW.
   *  There is simple state in the uplink at the SRGW; using Enhanced
      mode results in fewer SR policies on this node.  An SR policy is
      shared across UEs as long as they belong to the same context
      (i.e., tenant).  A set of many different policies (i.e., different
      SLAs) increases the amount of state required.

I am still having trouble grasping the "no state for downlink" and "simple =
state for uplink" difference.
For downlink, there is End.M.GTP6.E, right? What are you referring to when =
you say "no state for downlink"? Do you mean no per-PDU session state?
[PC] There is no state at all. All the information is contained in the pack=
et.
If so, uplink does not seem to need per-PDU session state either?=20
[PC] In the uplink you need to store the entire SR policy that will be used=
. Therefore, there is more state in uplink that in the downlink. This is fu=
rther explained in 5.3.1.3. I agree there is no per-PDU session state, it i=
s less than that.
Even in the "traditional mode", all you need is one End.M.GTP6.D SID that p=
ut together U::TEID.
If you aggregate (so that UPF does not need to look at TEIDs), how does the=
 SRGW know what SLA/tenant a PDU session is associated with? A gNB/UPF know=
s that because of N2/N4 signaling, but SRGW is not involved in N2/N4 signal=
ing. If it relies on different IPv6 addresses, then it seems that "traditio=
nal mode" actually has few state than the enhanced mode?


   *  In the uplink, the SRv6 BSID located in the IPv6 DA steers traffic
      into an SR policy when it arrives at the SRGW.

"SRv6 BSID located in the IPv6 DA" does not read well. Do you mean "... on =
the SRGW"?
[PC] Removed "located in the IPv6 DA" from the sentence.

5.3.1.1.  Packet flow - Uplink

   The uplink packet flow is as follows:

   UE_out  : (A,Z)
   gNB_out : (gNB, B)(GTP: TEID T)(A,Z)       -> Interface N3 unmodified
                                                 (IPv6/GTP)
   SRGW_out: (SRGW, S1)(U2::1, C1; SL=3D2)(A,Z) -> B is an End.M.GTP6.D
                                                 SID at the SRGW
   S1_out  : (SRGW, C1)(U2::1, C1; SL=3D1)(A,Z)
   C1_out  : (SRGW, U2::1)(A,Z)               -> End with PSP
   UPF2_out: (A,Z)                            -> End.DT4 or End.DT6

End.M.GTP6.D does the following:

   S02.    Copy the GTP TEID to buffer memory
   ...
   S08.    Write in the last SID of the SRH the Args.Mob.Session
              based on the information of buffer memory

Therefore, U2::1 really should be changed to U2::TEID.
[PC] Same reply as before.


5.3.1.3.  Scalability

   For the downlink traffic, the SRGW is stateless.  All the state is in
   the SRH pushed by the UPF2.  The UPF2 must have the UE states since
   it is the UE's session anchor point.

   For the uplink traffic, the state at the SRGW does not necessarily
   need to be unique per PDU Session; the SR policy can be shared among
   UEs.  This enables more scalable SRGW deployments compared to a
   solution holding millions of states, one or more per UE.

As commented above, the sharing/aggregation is based on different addresses=
 for different SLA/tenants signaled over N2. If sharing/aggregation is not =
used (i.e. traditional mode), there is no need for per-session state for up=
link either.
[PC] If sharing is not used, then you need one policy for each different PD=
U session (in order to be able to map it to a different SLA).

5.3.2.  Interworking with IPv4 GTP

   In this interworking mode the gNB uses GTP over IPv4 in the N3
   Interface

What does SMF tell UPF over N4? GTP with IPv4 parameters? Good to clarify.
[PC] Out of the scope of this draft as stated in the draft. I don't see why=
 this section deserves special treatment from the rest of the doc.

5.3.2.1.  Packet flow - Uplink
   ...
   Note that the interworking mechanisms for IPv4/GTP and IPv6/GTP
   differs.  This is due to the fact that in IPv6/GTP we can leverage
   the remote steering capabilities provided by SRv6.  In IPv4 this is
   not the case, and it would require a significant address consumption.

"remote steering capabilities provided by SRv6" is unclear about its meanin=
g - perhaps just remove the sentence and simply talk about address consumpt=
ion. Different addresses are used for different SLAs/tenants - if that's no=
t a concern even for IPv4 then it be can use for IPv4 as well and otherwise=
 either per-session classification is needed on the SRGW or just don't do a=
ggregation at all for IPv4 (then you just need one IPv4 route to come up wi=
th the U::TEID SID in the outgoing packets).
[PC] s/remote steering capabilities provided by SRv6/remote steering capabi=
lities provided by the Segment Routing BSID./
[PC] I've changed the IPv4 sentence to: " In IPv4 this construct is not ava=
ilable, and building a similar mechanism would require a significant addres=
s consumption."

On the other hand, how are the classification rules configured on the SRGW =
since it is not involved in the N2 signaling? Is it feasible at all to conf=
igure those on the SRGW?
[PC] CLI, Netconf, or other means.

5.3.2.2.  Packet flow - Downlink

   The downlink packet flow is as follows:

   UPF2_in : (Z,A)                            -> UPF2 maps flow with SID
                                               <C1, S1,GW::SA:DA:TEID>
   UPF2_out: (U2::1, C1)(GW::SA:DA:TEID, S1; SL=3D2)(Z,A) ->H.Encaps.Red
   C1_out  : (U2::1, S1)(GW::SA:DA:TEID, S1; SL=3D1)(Z,A)
   S1_out  : (U2::1, GW::SA:DA:TEID)(Z,A)
   SRGW_out: (GW, gNB)(GTP: TEID=3DT)(Z,A)       -> End.M.GTP4.E
   gNB_out : (Z,A)

   ...
   Once the packet arrives at the SRGW, the SRGW identifies the active
   SID as an End.M.GTP4.E function.  The SRGW removes the IPv6 header
   and all its extensions headers.  The SRGW generates an IPv4, UDP, and
   GTP headers.  The IPv4 SA and DA are received as SID arguments.  The
   TEID in the generated GTP header is also the arguments of the
   received End.M.GTP4.E SID.  The SRGW pushes the headers to the packet
   and forwards the packet toward the gNB.

What is the SA? Is it an address on the UPF or is it a local address on the=
 GW?
If it is of the GW, is there a need to carry it in the SRH?
If it is of the UPF while the packet really originated at the GW, why could=
n't same be done for IPv6 (in 5.3.1.1, when SRGW sends out packets it uses =
its own not the gNB address as source).
[PC] The SA is provided in the dataplane by using the encoding seen in Figu=
re 10.

5.3.2.3.  Scalability
   ...
   For the uplink traffic, the state at the SRGW is dedicated on a per
   UE/session basis according to a classification engine.  There is
   state for steering the different sessions in the form of an SR
   Policy.  However, SR policies are shared among several UE/sessions.

Is it really feasible to have those per UE/session classification rules?=20
[PC] We are already doing that today (classification based on TEID).
Compared to using per-SLA/tenant IPv4 addresses, which is more practical?
[PC] Then you have the address consumption issue...

5.4.  SRv6 Drop-in Interworking

   In this section we introduce another mode useful for legacy gNB and
   UPFs that still operate with GTP-U.  This mode provides an
   SRv6-enabled user plane in between two GTP-U tunnel endpoints.

   In this mode we employ two SRGWs that map GTP-U traffic to SRv6 and
   vice-versa.

5.3 talks about interworking between an SRv6 UPF and GTP gNB. 5.4 talks abo=
ut using SRv6 to connect GTP gNB and GTP UPF. Perhaps it's better to talk a=
bout interworking between SRv6 gNB and GTP UPF first, and then if you put t=
wo interworking mode together you achieve what current 5.4 achieves - a GW =
basically presents a GTP NF as an SRv6 NF.

In fact, GW for UPF just seems to be a mirror of the GW for gNB.
[PC] It is a mirror...

   When the packet arrives at SRGW-A, the SRGW identifies U::1 as an
   End.M.GTP6.D.Di Binding SID (see Section 6.4).  Hence, the SRGW
   removes the IPv6, UDP, and GTP headers, and pushes an IPv6 header
   with its own SRH containing the SIDs bound to the SR policy
   associated with this Binding SID.  There is one instance of the
   End.M.GTP6.D.Di SID per PDU type.

In the other email I talked about not needing End.M.GTP6.D.Di.

6.1.  Args.Mob.Session

   Arg.Mob.Session is required in case that one SID aggregates multiple
   PDU Sessions.  Since the SRv6 SID is likely NOT to be instantiated
   per PDU session, Args.Mob.Session helps the UPF to perform the
   behaviors which require per QFI and/or per PDU Session granularity.

   Note that the encoding of user-plane messages (e.g., Echo Request,
   Echo Reply, Error Indication and End Marker) is out of the scope of
   this draft.  [I-D.murakami-dmm-user-plane-message-encoding] defines
   one possible encoding.

I actually missed that Args.Mob.Session was encoding information like QFI (=
that's why I wanted to have a normative reference to draft-murakami).
Why don't we use it for traditional, non-aggregate mode as well (the above =
text only says it's required for aggregation)? In that mode different SIDs =
are used for different sessions, but those SIDs can still be viewed as a lo=
cator+ Args.Mob.Session (which also encodes QFI that is also needed).
[PC] I agree with you that would be a good enhancement, however I believe t=
his cannot be done. The usage of Args.Mob.Session requires allocating a use=
rplane identifier. I don't think in Traditional mode we can have any user p=
lane identifier different from TEID.=20

6.2.  End.MAP

   The "Endpoint behavior with SID mapping" behavior (End.MAP for short)
   is used in several scenarios.  Particularly in mobility, End.MAP is
   used in the UPFs for the PDU Session anchor functionality.

Hmm ... not sure about the last sentence. It seems that End.MAP is used for=
 intermediate UPFs instead of anchoring UPFs.
[PC] Corrected indeed.

   When node N receives a packet whose IPv6 DA is S and S is a local
   End.MAP SID, N does:

   S01. If (IPv6 Hop Limit <=3D 1) {
   S02.    Send an ICMP Time Exceeded message to the Source Address,
              Code 0 (Hop limit exceeded in transit),
              interrupt packet processing, and discard the packet.
   S03. }
   S04. Decrement IPv6 Hop Limit by 1
   S05. Lookup the IPv6 DA in the mapping table
   S06. Update the IPv6 DA with the new mapped SID
   S07. Submit the packet to the egress IPv6 FIB lookup for
           transmission to the new destination

   Notes: The SIDs in the SRH are not modified.

Since the entire IPv6 DA is the End.MAP SID, e.g. per the following in 5.1.=
2:

   Upon packet arrival on UPF1, the SID U1::2 is a local SID associated
   with the End.MAP SRv6 Endpoint Behavior.  It maps the SID to the next
   anchoring point and replaces U1::2 by gNB::1, that belongs to the
   next hop.

The SID itself can do the mapping already w/o looking up a mapping table, s=
o S05 is not needed, right? In other words, the mapped to SID is associated=
 with this SID already, no need to do a lookup.
[PC] Ill remove the line as that goes really into implementation specific o=
n whether you the mapping in a single shot or your need the extra lookup...
The above procedures would make sense only if just part of the IPv6 address=
 (e.g. the U1 part) is the SID, while the ::2 part is used to lookup a mapp=
ing table.

6.3.  End.M.GTP6.D

   S01. If (Next Header =3D UDP & UDP_Dest_port =3D GTP) {
   S02.    Copy the GTP TEID to buffer memory
   S03.    Pop the IPv6, UDP, and GTP Headers
   S04.    Push a new IPv6 header with its own SRH containing B
   S05.    Set the outer IPv6 SA to A
   S06.    Set the outer IPv6 DA to the first SID of B
   S07.    Set the outer Payload Length, Traffic Class, Flow Label,
              Hop Limit, and Next-Header fields

Add "(NH)" after "Next-Header" above? There were several "NH" references la=
ter.
[PC] Added.

   S08.    Write in the last SID of the SRH the Args.Mob.Session
              based on the information of buffer memory
   S09.    Submit the packet to the egress IPv6 FIB lookup and
              transmission to the new destination
   S10. } Else {
   S11.    Process as per [RFC8986] Section 4.1.1
   S12. }

Shouldn't we copy the QFI part as well in step S08?
[PC] Added in S02.

   The prefix of A SHOULD be an End.M.GTP6.E SID instantiated at an SR
   gateway.

Why is the above required? A is the source address of the packet output by =
the GW. It's understandable that on reverse direction, A could be an End.M.=
GTP6.E SID but that is not mandatory - a different address could be used (e=
ither the gNB address as I suggested or another local address on the GW).
[PC] Agreed. Sentence removed.

6.4.  End.M.GTP6.D.Di

As mentioned in the other email, this is not needed?
[PC] The WG decided to add the DropIn mode as it found value after the demo=
s shown by Arashmid.
[PC] If the working group wants to change that, fine with me. However, give=
n that this is just one SRv6 Endpoint Behavior.. I don't see the problem in=
 keeping it defined in the document.

6.5.  End.M.GTP6.E

   The "Endpoint behavior with encapsulation for IPv6/GTP tunnel"
   behavior (End.M.GTP6.E for short) is used in interworking scenario
   for the downlink toward the legacy gNB using IPv6/GTP.

This is used for uplink in drop-in mode as well.
[PC] Indeed. Changed.

6.6.  End.M.GTP4.E

   S01. If (Next Header =3D UDP & UDP_Dest_port =3D GTP) {
   S02.    Sotre the IPv6 DA and SA in buffer memory

What is SA used for? The DA part provides all the information according to =
5.3.2.2, which seems to be conflicting from the following:
[PC] The IPv6 Source Address also encodes the IPv4 address that has to be u=
sed in the crafted GTP-U packet. See figure 10.

   Notes: The End.M.GTP4.E SID in S has the following format:

       0                                                         127
       +-----------------------+-------+----------------+---------+
       |  SRGW-IPv6-LOC-FUNC   |IPv4DA |Args.Mob.Session|0 Padded |
       +-----------------------+-------+----------------+---------+
              128-a-b-c            a            b           c


                    Figure 9: End.M.GTP4.E SID Encoding

   The IPv6 Source Address has the following format:

       0                                                         127
       +----------------------+--------+--------------------------+
       |  Source UPF Prefix   |IPv4 SA | any bit pattern(ignored) |
       +----------------------+--------+--------------------------+
                128-a-b            a                  b


                Figure 10: IPv6 SA Encoding for End.M.GTP4.E

6.7.  H.M.GTP4.D

Similarly, the example in 5.3.2.1 should be modified to match this.

   The prefix of B' SHOULD be an End.M.GTP4.E SID with its format
   instantiated at an SR gateway with the IPv4 SA of the receiving
   packet.

Similarly, why is the above required?
[PC] Sentence removed. This is not a requirement (as discussed earlier).

6.8.  End.Limit: Rate Limiting behavior

Can you elaborate how this is used? An example of inserting this SID into o=
ne of the SRHs will be helpful.
[PC] This SID is added when the operator wishes to Rate Limit a particular =
flow of packets. The SID contains two arguments (group-id and limit-rate).
[PC] The node instantiating this segment has a rate limiting policy that is=
 applied to the packet.

9.  Control Plane Considerations

   This document focuses on user-plane behavior and its independence
   from the control plane.  While there are benefits in an enhanced
   control plane (e.g., to dynamically configure SR policies from a
   controller), this document does not impose any change to the existant
   mobility control plane.

It should be pointed out that for aggregation, N2/N4 need to give out diffe=
rent NF addresses for different SLA/tenants.
[PC] Added.

10.  Security Considerations

   The security considerations for Segment Routing are discussed in
   [RFC8402].  More specifically for SRv6 the security considerations
   and the mechanisms for securing an SR domain are discussed in
   [RFC8754].  Together, they describe the required security mechanisms
   that allow establishment of an SR domain of trust to operate
   SRv6-based services for internal traffic while preventing any
   external traffic from accessing or exploiting the SRv6-based
   services.

   The technology described in this document is applied to a mobile
   network that is within the SR Domain.

   This document introduces new SRv6 Endpoint Behaviors.  Those
   behaviors do not need any special security consideration given that
   it is deployed within that SR Domain.

For interworking, GTP and SRv6 packets are converted to each other. Does th=
at mean encryption can not be used? That should be pointed out.
[PC] The payload of the packet is neither inspected nor modified. Hence if =
you wish to use encryption on the packet payload there should be no problem=
. Please detail more if you think otherwise. I might be missing your point.

Jeffrey


From nobody Fri Oct 15 15:45:12 2021
Return-Path: <agenda@ietf.org>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B49C3A0EBA; Fri, 15 Oct 2021 15:34:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <dmm-chairs@ietf.org>, <sgundave@cisco.com>
Cc: dmm@ietf.org, ek.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.39.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <163433724955.17026.16709928933995641393@ietfa.amsl.com>
Date: Fri, 15 Oct 2021 15:34:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/T94P9zamEpIP29E348zxIs1Laq8>
Subject: [DMM] dmm - Requested session has been scheduled for IETF 112
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2021 22:34:27 -0000

Dear Sri Gundavelli,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    dmm Session 1 (2:00 requested)
    Wednesday, 10 November 2021, Session III 1600-1800
    Room Name: Room 2 size: 502
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/112/sessions/dmm.ics

Request Information:


---------------------------------------------------------
Working Group Name: Distributed Mobility Management
Area Name: Internet Area
Session Requester: Sri Gundavelli


Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 30
Conflicts to Avoid: 

       


People who must be present:
  Dapeng Liu
  Erik Kline
  Satoru Matsushima
  Sri Gundavelli

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Fri Oct 22 14:23:27 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 690FA3A0C3D; Fri, 22 Oct 2021 14:22:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dmm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.39.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dmm@ietf.org
Message-ID: <163493772828.9452.18262589147169377986@ietfa.amsl.com>
Date: Fri, 22 Oct 2021 14:22:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/u88BiVAJFAJuA7ScoDqjnScZC2o>
Subject: [DMM] I-D Action: draft-ietf-dmm-tn-aware-mobility-02.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2021 21:22:10 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Mobility Management WG of the IETF.

        Title           : Mobility aware Transport Network Slicing for 5G
        Authors         : Uma Chunduri
                          John Kaippallimalil
                          Sridhar Bhaskaran
                          Jeff Tantsura
                          Praveen Muley
	Filename        : draft-ietf-dmm-tn-aware-mobility-02.txt
	Pages           : 24
	Date            : 2021-10-22

Abstract:
   This document specifies a framework and mapping of slices in 5G
   mobile systems to transport network slices in IP, Layer 2 or Layer 1
   transport networks.  Slices in 5G systems are characterized by
   latency bounds, reservation guarantees, jitter, data rates,
   availability, mobility speed, usage density, criticality and
   priority.  These characteristics are mapped to transport network
   slice include bandwidth, latency and criteria such as isolation,
   directionality and disjoint routes.  Mobile slice criteria are mapped
   to the appropriate transport slice and capabilities offered in
   backhaul, midhaul and fronthaul connectivity segments between radio
   side network functions and user plane function(gateway).

   This document describes how a mobile network slice is mapped to a
   slice in IP or Layer 2 transport network between 3GPP provisioning
   end points.  The same mapping mechanisms apply during initial UE
   session setup and following UE mobility.  Applicability of this
   framework and underlying transport networks, which can enable
   different slice properties are also discussed.  This is based on
   mapping between mobile and transport underlays (L2, Segment Routing,
   IPv6, MPLS and IPv4).



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mobility-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-tn-aware-mobility-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Fri Oct 22 14:35:41 2021
Return-Path: <umac.ietf@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1FC73A0DB0 for <dmm@ietfa.amsl.com>; Fri, 22 Oct 2021 14:35:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 R8WBIsbKidXm for <dmm@ietfa.amsl.com>; Fri, 22 Oct 2021 14:35:30 -0700 (PDT)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 D570A3A0DAB for <dmm@ietf.org>; Fri, 22 Oct 2021 14:35:29 -0700 (PDT)
Received: by mail-yb1-xb31.google.com with SMTP id i9so9881878ybi.8 for <dmm@ietf.org>; Fri, 22 Oct 2021 14:35:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=q85PeiZIjoxQIBIwRBmR263Uf9QzblmzWwZ57v59DtA=; b=qO0mwQBWcS3Q7t3yJ33eJ4kesHAkIZDPsJZD1PzHOtQuNPltr7KwpMW5rl3oR/FQ8x FOm/T3Bw8IHhYCI1QILXaeV26QYJwm7Pc9qflQotAo7fBKCiZxAwkXFQY34VNQ2O7fWC ERCPzseXPuQCv9QQ5CZpGAMTdvxdt0Z63mm/J3i6wyz921X9DuwPtzm36++EdHOGYPAT +2CjkbHe9zz5SsDVR1lvJuamhIDC8Ykn5P1oHUd+YFchk1IqVDALjCqSKCk73jgiMsg8 zYNNBU1d95KKl50Vpw5rd9e+VWJ2Zl26FS0Dx17y7KvcO4jWX3rAoNWkYFm6uOTCKsvg f1Mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=q85PeiZIjoxQIBIwRBmR263Uf9QzblmzWwZ57v59DtA=; b=hg05XXS30DN2/o5VxYkOfDYa0FJlyOpyJMoKHQngtXqXNtshrvoy1pGDSCqMdb35pO JGdYoTmWwOdVMRM58XDKK12Rxl2V29CirmAkhArkMAIaQzJFkD2i5XrXtgGuXEuwwNaG AK/hH9gpTVJdLvH0BvtwBqGFBnZhncw0W4u+GuRXkMRk0vFcIoHy9eTo7yoOtLER91VL sfXJb4seqOw7OrK6waQT0+Djuwjg0dizRmolIs9xa8a74Zvh6ogvA4dS1rga2ILhteNs +hXu+8aBBycsR6yfeRehu0LDHV/wEboNU0WRyERpFg8gssmNN/4kLr68jHxxuAGv1pXo mobw==
X-Gm-Message-State: AOAM5305MQKvcm4Ay9btqX2P2P4N9dsvuEL/24XpVTqvdPVnS25qgVH1 vJAPfYI+fDr3KD5+cxl73BddA8Q8lGVXgBgxAI+wkhwD
X-Google-Smtp-Source: ABdhPJxhY36/0H4FPSajsw0gDsQQpGLXlh0Vs+LdPJAYK1bqBNNIlx04/OBU1Fw7IDh3bTO8Z9HGMZmCEFWJvubhkB8=
X-Received: by 2002:a25:4003:: with SMTP id n3mr2594691yba.544.1634938528273;  Fri, 22 Oct 2021 14:35:28 -0700 (PDT)
MIME-Version: 1.0
References: <163493772828.9452.18262589147169377986@ietfa.amsl.com>
In-Reply-To: <163493772828.9452.18262589147169377986@ietfa.amsl.com>
From: Uma Chunduri <umac.ietf@gmail.com>
Date: Fri, 22 Oct 2021 14:35:17 -0700
Message-ID: <CAF18ct6LNPR9=EyhDfM9_5eYL59DZseLJ_3svadZ=bKF_vuCBg@mail.gmail.com>
To: dmm <dmm@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000035186805cef7ca34"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/Msk90v_vFPtoV1sFomc6lj7YNUE>
Subject: Re: [DMM] I-D Action: draft-ietf-dmm-tn-aware-mobility-02.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2021 21:35:38 -0000

--00000000000035186805cef7ca34
Content-Type: text/plain; charset="UTF-8"

Dear DMM WG,

Some of the recent discussions in DMM and routing areas regarding this
draft have been addressed in 01 and 02 versions.

Feel free to post your comments.  We (John K.)  will go over the updates in
the next IETF meeting.

Have a great day!
--
Uma C.

On Fri, Oct 22, 2021 at 2:23 PM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Distributed Mobility Management WG of the
> IETF.
>
>         Title           : Mobility aware Transport Network Slicing for 5G
>         Authors         : Uma Chunduri
>                           John Kaippallimalil
>                           Sridhar Bhaskaran
>                           Jeff Tantsura
>                           Praveen Muley
>         Filename        : draft-ietf-dmm-tn-aware-mobility-02.txt
>         Pages           : 24
>         Date            : 2021-10-22
>
> Abstract:
>    This document specifies a framework and mapping of slices in 5G
>    mobile systems to transport network slices in IP, Layer 2 or Layer 1
>    transport networks.  Slices in 5G systems are characterized by
>    latency bounds, reservation guarantees, jitter, data rates,
>    availability, mobility speed, usage density, criticality and
>    priority.  These characteristics are mapped to transport network
>    slice include bandwidth, latency and criteria such as isolation,
>    directionality and disjoint routes.  Mobile slice criteria are mapped
>    to the appropriate transport slice and capabilities offered in
>    backhaul, midhaul and fronthaul connectivity segments between radio
>    side network functions and user plane function(gateway).
>
>    This document describes how a mobile network slice is mapped to a
>    slice in IP or Layer 2 transport network between 3GPP provisioning
>    end points.  The same mapping mechanisms apply during initial UE
>    session setup and following UE mobility.  Applicability of this
>    framework and underlying transport networks, which can enable
>    different slice properties are also discussed.  This is based on
>    mapping between mobile and transport underlays (L2, Segment Routing,
>    IPv6, MPLS and IPv4).
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/
>
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mobility-02
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-tn-aware-mobility-02
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>

--00000000000035186805cef7ca34
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear DMM WG,<div><br></div><div>Some of the recent discuss=
ions in DMM and routing areas regarding this draft have been addressed in 0=
1 and 02 versions.=C2=A0</div><div><br></div><div>Feel free to post your co=
mments.=C2=A0 We (John K.)=C2=A0 will go over the updates in the next IETF =
meeting.</div><div><br></div><div>Have a great day!</div><div>--</div><div>=
Uma C.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"=
gmail_attr">On Fri, Oct 22, 2021 at 2:23 PM &lt;<a href=3D"mailto:internet-=
drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Distributed Mobility Management WG of the =
IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Mobility aware Transport Network Slicing for 5G<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Uma =
Chunduri<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 John Kaippallimalil<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Sridhar Bhaskaran<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Jeff Tantsura<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Praveen Muley<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-dmm-tn-aware-mobility-02.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 24<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2021-10-22<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document specifies a framework and mapping of slices in 5=
G<br>
=C2=A0 =C2=A0mobile systems to transport network slices in IP, Layer 2 or L=
ayer 1<br>
=C2=A0 =C2=A0transport networks.=C2=A0 Slices in 5G systems are characteriz=
ed by<br>
=C2=A0 =C2=A0latency bounds, reservation guarantees, jitter, data rates,<br=
>
=C2=A0 =C2=A0availability, mobility speed, usage density, criticality and<b=
r>
=C2=A0 =C2=A0priority.=C2=A0 These characteristics are mapped to transport =
network<br>
=C2=A0 =C2=A0slice include bandwidth, latency and criteria such as isolatio=
n,<br>
=C2=A0 =C2=A0directionality and disjoint routes.=C2=A0 Mobile slice criteri=
a are mapped<br>
=C2=A0 =C2=A0to the appropriate transport slice and capabilities offered in=
<br>
=C2=A0 =C2=A0backhaul, midhaul and fronthaul connectivity segments between =
radio<br>
=C2=A0 =C2=A0side network functions and user plane function(gateway).<br>
<br>
=C2=A0 =C2=A0This document describes how a mobile network slice is mapped t=
o a<br>
=C2=A0 =C2=A0slice in IP or Layer 2 transport network between 3GPP provisio=
ning<br>
=C2=A0 =C2=A0end points.=C2=A0 The same mapping mechanisms apply during ini=
tial UE<br>
=C2=A0 =C2=A0session setup and following UE mobility.=C2=A0 Applicability o=
f this<br>
=C2=A0 =C2=A0framework and underlying transport networks, which can enable<=
br>
=C2=A0 =C2=A0different slice properties are also discussed.=C2=A0 This is b=
ased on<br>
=C2=A0 =C2=A0mapping between mobile and transport underlays (L2, Segment Ro=
uting,<br>
=C2=A0 =C2=A0IPv6, MPLS and IPv4).<br>
<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobilit=
y/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/d=
raft-ietf-dmm-tn-aware-mobility/</a><br>
<br>
There is also an htmlized version available at:<br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-dmm-tn-aware-mo=
bility-02" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/doc/html/draft-ietf-dmm-tn-aware-mobility-02</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dmm-tn-aware-mobi=
lity-02" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?=
url2=3Ddraft-ietf-dmm-tn-aware-mobility-02</a><br>
<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
<br>
_______________________________________________<br>
dmm mailing list<br>
<a href=3D"mailto:dmm@ietf.org" target=3D"_blank">dmm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/dmm</a><br>
</blockquote></div>

--00000000000035186805cef7ca34--


From nobody Mon Oct 25 18:42:14 2021
Return-Path: <satoru.matsushima@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3969E3A0E7D; Mon, 25 Oct 2021 18:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, 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 Hhbv9RtC0YcU; Mon, 25 Oct 2021 18:42:08 -0700 (PDT)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 D22163A0E7E; Mon, 25 Oct 2021 18:42:05 -0700 (PDT)
Received: by mail-pj1-x102e.google.com with SMTP id np13so9674128pjb.4; Mon, 25 Oct 2021 18:42:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=content-transfer-encoding:from:mime-version:subject:date:references :cc:to:message-id; bh=6mofb6+rM0WCUI3Zg+aDnom6o02TUTzVK6AUzFPnTRI=; b=p7hPBPDdRKX3i+G1mXdx/hYd94OUx+P1fFX9z7LExLFSx3kfs/RjEvuYhb9i5AhYF7 lTBPS+1Eu6zjOGYCB7kUjfd3OJmqyIteHC5AWw2aujbFVJtSSouIMrBC2wMPce5eHUYq advjAMl9CylLtX4A1iE7Nx7px3gAf8rzt/Ytzfw7bJ4pN3GfFQ2m6DHrtv2lGXo/t3Jg Q6uR0hleNQxMlarV8YbHsF5jv76CYevTBAPUsbnzx5i62XChD50moRthyPdjQo+mQVMq x2Ugto6Wu8m8sigFqfafCzjjI/zUx8YFm1GsT4WI00Ey0ouexIRxgqCvsXJ7S+8bj/pJ PuVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:references:cc:to:message-id; bh=6mofb6+rM0WCUI3Zg+aDnom6o02TUTzVK6AUzFPnTRI=; b=pjg7w3/rUjXA+MPZu9VZER0p5d27WtHyzdlhkV0dlPGv1CGSXAydIu83MeiNiQ+KCq +OFnJEnLD0aJLtaOc5H/f3ZXgvbkDIT+Jtg+maFKcbd3wR/jpPCZuUk4+mt3IRSCJWp7 eQlPz3EBN3o45iGYUY1LUjrW2lj1qiTb7Kx9wBCr2q5S6hQ9zmhmQK9gXmO32Dc4fMoL uruSAxBEsSjOOs7hU3nYbDUoNuK/2+gTB+Tk7UynwZ5f8GqC6ag4Xyqq0GLYPdcoawQN mm4mdNF8wjRe0vTfcLdcAudP88+Dru8WZ8SRl4S3qg9/zTJlsfV6a/KlvfOqtfxWg3b0 GfvQ==
X-Gm-Message-State: AOAM532cukvLKNk1UlOpVNIzR7lPKQda3x0dHyyZ7SOYvhGnIwjiNFMX zx/jrmzNrG9EWZ0Mo8vu+NY=
X-Google-Smtp-Source: ABdhPJy+zZE7/m1g57j/PQSYQ+c0EbBMttZsDCci6jtLXLZUCNctWpBhkAuol+Ff1+zf4it6ZH5vSQ==
X-Received: by 2002:a17:90a:a389:: with SMTP id x9mr39407865pjp.167.1635212523518;  Mon, 25 Oct 2021 18:42:03 -0700 (PDT)
Received: from smtpclient.apple ([2400:2411:8900:0:f15c:37ec:34ec:c731]) by smtp.gmail.com with ESMTPSA id g14sm17228542pgo.88.2021.10.25.18.42.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Oct 2021 18:42:02 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-5515D719-8989-4B05-AD52-E9C1BD463E67
Content-Transfer-Encoding: 7bit
From: Satoru Matsushima <satoru.matsushima@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 26 Oct 2021 10:42:00 +0900
References: <163518352308.14869.12443696227178260709@ietfa.amsl.com>
Cc: draft-mhkk-dmm-srv6mup-architecture.all@ietf.org
To: dmm <dmm@ietf.org>
Message-Id: <6BF0FD2A-60DB-4950-AA14-FB08E08BFA8B@gmail.com>
X-Mailer: iPad Mail (19A404)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/xBBAZhj5Jzpy8h7u0U1f11Y5WtQ>
Subject: [DMM] Fwd: I-D Action: draft-mhkk-dmm-srv6mup-architecture-00.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Oct 2021 01:42:13 -0000

--Apple-Mail-5515D719-8989-4B05-AD52-E9C1BD463E67
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi DMMers,

We have submitted a new draft of an SRv6 mobile user plane architecture for D=
MM. Please take a look at it. Any feedbacks from the WG are really appreciat=
e.

Cheers,=20
--satoru

Begin forwarded message:

> From: internet-drafts@ietf.org
> Date: October 26, 2021 2:38:43 JST
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-mhkk-dmm-srv6mup-architecture-00.txt
> Reply-To: internet-drafts@ietf.org
>=20
> =EF=BB=BF
> A New Internet-Draft is available from the on-line Internet-Drafts directo=
ries.
>=20
>=20
>        Title           : Segment Routing IPv6 Mobile User Plane Architectu=
re for Distributed Mobility Management
>        Authors         : Satoru Matsushima
>                          Katsuhiro Horiba
>                          Ashiq Khan
>                          Yuya Kawakami
>                          Tetsuya Murakami
>                          Keyur Patel
>                          Miya Kohno
>                          Teppei Kamata
>                          Pablo Camarillo
>    Filename        : draft-mhkk-dmm-srv6mup-architecture-00.txt
>    Pages           : 11
>    Date            : 2021-10-25
>=20
> Abstract:
>   This document defines the Segment Routing IPv6 Mobile User Plane
>   (SRv6 MUP) architecture for Distributed Mobility Management.  The
>   requirements for Distributed Mobility Management described in
>   [RFC7333] can be satisfied by routing fashion.
>=20
>   Mobile services are deployed over several parts of IP networks.  A
>   Segment Routing over IPv6 (SRv6) network can accommodate all, or part
>   of those networks thanks to the large address space of IPv6 and the
>   network programming capability described in [RFC8986].
>=20
>   Segment Routing IPv6 Mobile User Plane Architecture can incorporate
>   existing session based mobile networks.  By leveraging SRv6 network
>   programmability, mobile user plane can be integrated into the SRv6
>   data plane.  In that routing paradigm, session information between
>   the entities of the mobile user plane is turned to routing
>   information.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-mhkk-dmm-srv6mup-architecture/
>=20
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-mhkk-dmm-srv6mup-architecture-=
00
>=20
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--Apple-Mail-5515D719-8989-4B05-AD52-E9C1BD463E67
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">Hi DMMers,<div><br></div><div>We have submi=
tted a new draft of an SRv6 mobile user plane architecture for DMM. Please t=
ake a look at it. Any feedbacks from the WG are really appreciate.</div><div=
><br></div><div>Cheers,&nbsp;<br><div dir=3D"ltr">--satoru</div><div dir=3D"=
ltr"><br>Begin forwarded message:<br><br></div><blockquote type=3D"cite"><di=
v dir=3D"ltr"><b>From:</b> internet-drafts@ietf.org<br><b>Date:</b> October 2=
6, 2021 2:38:43 JST<br><b>To:</b> i-d-announce@ietf.org<br><b>Subject:</b> <=
b>I-D Action: draft-mhkk-dmm-srv6mup-architecture-00.txt</b><br><b>Reply-To:=
</b> internet-drafts@ietf.org<br><br></div></blockquote><blockquote type=3D"=
cite"><div dir=3D"ltr">=EF=BB=BF<span></span><br><span>A New Internet-Draft i=
s available from the on-line Internet-Drafts directories.</span><br><span></=
span><br><span></span><br><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;T=
itle &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Segment R=
outing IPv6 Mobile User Plane Architecture for Distributed Mobility Manageme=
nt</span><br><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Authors &nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Satoru Matsushima</span><br><spa=
n> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;Katsuhiro Horiba</span><br><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ashiq Khan</span><br><span> &nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Yuya Kawakami</sp=
an><br><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;Tetsuya Murakami</span><br><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Keyur Patel</span><br><span> &nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Miya K=
ohno</span><br><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;Teppei Kamata</span><br><span> &nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Pablo Camarillo</span><br><=
span> &nbsp; &nbsp;Filename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draf=
t-mhkk-dmm-srv6mup-architecture-00.txt</span><br><span> &nbsp; &nbsp;Pages &=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 11</span><br><s=
pan> &nbsp; &nbsp;Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;: 2021-10-25</span><br><span></span><br><span>Abstract:</span><=
br><span> &nbsp;&nbsp;This document defines the Segment Routing IPv6 Mobile U=
ser Plane</span><br><span> &nbsp;&nbsp;(SRv6 MUP) architecture for Distribut=
ed Mobility Management. &nbsp;The</span><br><span> &nbsp;&nbsp;requirements f=
or Distributed Mobility Management described in</span><br><span> &nbsp;&nbsp=
;[RFC7333] can be satisfied by routing fashion.</span><br><span></span><br><=
span> &nbsp;&nbsp;Mobile services are deployed over several parts of IP netw=
orks. &nbsp;A</span><br><span> &nbsp;&nbsp;Segment Routing over IPv6 (SRv6) n=
etwork can accommodate all, or part</span><br><span> &nbsp;&nbsp;of those ne=
tworks thanks to the large address space of IPv6 and the</span><br><span> &n=
bsp;&nbsp;network programming capability described in [RFC8986].</span><br><=
span></span><br><span> &nbsp;&nbsp;Segment Routing IPv6 Mobile User Plane Ar=
chitecture can incorporate</span><br><span> &nbsp;&nbsp;existing session bas=
ed mobile networks. &nbsp;By leveraging SRv6 network</span><br><span> &nbsp;=
&nbsp;programmability, mobile user plane can be integrated into the SRv6</sp=
an><br><span> &nbsp;&nbsp;data plane. &nbsp;In that routing paradigm, sessio=
n information between</span><br><span> &nbsp;&nbsp;the entities of the mobil=
e user plane is turned to routing</span><br><span> &nbsp;&nbsp;information.<=
/span><br><span></span><br><span></span><br><span>The IETF datatracker statu=
s page for this draft is:</span><br><span>https://datatracker.ietf.org/doc/d=
raft-mhkk-dmm-srv6mup-architecture/</span><br><span></span><br><span>There i=
s also an htmlized version available at:</span><br><span>https://datatracker=
.ietf.org/doc/html/draft-mhkk-dmm-srv6mup-architecture-00</span><br><span></=
span><br><span></span><br><span>Internet-Drafts are also available by anonym=
ous FTP at:</span><br><span>ftp://ftp.ietf.org/internet-drafts/</span><br><s=
pan></span><br><span></span><br><span>______________________________________=
_________</span><br><span>I-D-Announce mailing list</span><br><span>I-D-Anno=
unce@ietf.org</span><br><span>https://www.ietf.org/mailman/listinfo/i-d-anno=
unce</span><br><span>Internet-Draft directories: http://www.ietf.org/shadow.=
html</span><br><span>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt</span><br>=
</div></blockquote></div></body></html>=

--Apple-Mail-5515D719-8989-4B05-AD52-E9C1BD463E67--

