Re: [DMM] IETF104 DMM WG meeting minutes

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Tue, 02 April 2019 00:56 UTC

Return-Path: <sgundave@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 D3FB11200E6 for <dmm@ietfa.amsl.com>; Mon, 1 Apr 2019 17:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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=Qq9PgqOs; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=k7h6wM3j
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 wML-c5SYz9Zm for <dmm@ietfa.amsl.com>; Mon, 1 Apr 2019 17:56:02 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7B47120086 for <dmm@ietf.org>; Mon, 1 Apr 2019 17:56:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14659; q=dns/txt; s=iport; t=1554166561; x=1555376161; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=CLWq9FSHADwTJ1LX7iVaISCoksrdjPdlKUwxmSkbAjI=; b=Qq9PgqOseaBNFffyIQZ35RVvZEpTvneGEIlfoYMHpu8UtEdmdbpixVNU te3ulSccSU0lUCE5pgxuOLjLXujVPkSf4FOo0faWAG8IX1boikgVL5GOl 4ZWknPOA4wMVQry/mkL3auTy5uU4e84xd2n6xnhs7CuKhnp7Gfvr6VLuD U=;
IronPort-PHdr: =?us-ascii?q?9a23=3AzQ4IPhy/MbaLLovXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZueBlD9IPf0YgQxHd9JUxlu+HToeUU=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DcAABGsqJc/4QNJK1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBVAIBAQEBCwGBDi9QA2hUIAQLJwqHSwOPNBwugg2SRoRJgUK?= =?us-ascii?q?BEANUDgEBIwmEQAKFRCI3Bg0BAQMBAQkBAwJtHAyFSgEBAQQtEwEBOA8CAQg?= =?us-ascii?q?RAwEBARYSBzIUCQgCBAESgyOBEUwDFQECDKJYAooUgiCCeQEBBYE1BIENgkY?= =?us-ascii?q?YggwDBYEvAYsyF4FAP4QjPoEEgV0CAhiBAlMSDQkJhSKKfIYqHpQJCQKHb4t?= =?us-ascii?q?vGoIDhgyKYIE9iz+BGIR5jT0CBAIEBQIOAQEFgWMigVZwFYMnggoMDAuDS4U?= =?us-ascii?q?UhT9ygSiNcAGBHgEB?=
X-IronPort-AV: E=Sophos;i="5.60,298,1549929600"; d="scan'208,217";a="255236491"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Apr 2019 00:56:00 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x320u0tw000787 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Apr 2019 00:56:00 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Apr 2019 19:55:59 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Apr 2019 19:55:58 -0500
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 1 Apr 2019 19:55:59 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MDgRbM7Z+mMWXXrIMxFmcmAzjYIbsLmTgMXx+WFml+w=; b=k7h6wM3jCdjRpuVcnavNk5Zcsy8i9AFIqdoGCh6gyR8br7E7nTdC7COffnSSMAa56E6iwtylhQ1MjF5UETWeHqBUNRMXSpw7HqiEaYdZAWZhc5I8OJRAjBrUnFJJK+DJCvWpAGetiaiaLyUhH4RWL5EUIVQNVspgnDSjsBNilbQ=
Received: from BYAPR11MB3558.namprd11.prod.outlook.com (20.178.206.75) by BYAPR11MB3750.namprd11.prod.outlook.com (20.178.238.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.22; Tue, 2 Apr 2019 00:55:58 +0000
Received: from BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::a07b:c022:56cf:60fb]) by BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::a07b:c022:56cf:60fb%6]) with mapi id 15.20.1750.017; Tue, 2 Apr 2019 00:55:58 +0000
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Marco Liebsch <Marco.Liebsch@neclab.eu>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: IETF104 DMM WG meeting minutes
Thread-Index: AQHU5AOK5OkNkiKCvEuPIxGJ+Sagzw==
Date: Tue, 2 Apr 2019 00:55:57 +0000
Message-ID: <D8C80113.2F1435%sgundave@cisco.com>
References: <0D39C2AC-3674-44E7-A688-9D89BE28E849@cisco.com> <C0EE6558-B872-4E91-8E36-C1184881F8C5@cisco.com> <69756203DDDDE64E987BC4F70B71A26DE5A911ED@DAPHNIS.office.hd>
In-Reply-To: <69756203DDDDE64E987BC4F70B71A26DE5A911ED@DAPHNIS.office.hd>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.7.170905
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sgundave@cisco.com;
x-originating-ip: [128.107.241.184]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a812a9b5-3e63-4566-499c-08d6b705f7e7
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:BYAPR11MB3750;
x-ms-traffictypediagnostic: BYAPR11MB3750:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BYAPR11MB37502AB01CDC02B8FDB2A02AD9560@BYAPR11MB3750.namprd11.prod.outlook.com>
x-forefront-prvs: 0995196AA2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(136003)(396003)(346002)(376002)(39860400002)(199004)(189003)(51914003)(966005)(2906002)(97736004)(54896002)(36756003)(66066001)(256004)(14444005)(14454004)(102836004)(6506007)(76176011)(53546011)(68736007)(6486002)(6436002)(6116002)(3846002)(790700001)(229853002)(66574012)(71190400001)(71200400001)(478600001)(25786009)(236005)(106356001)(105586002)(486006)(2616005)(476003)(11346002)(53936002)(6512007)(446003)(606006)(6306002)(86362001)(8676002)(6246003)(58126008)(110136005)(186003)(561944003)(316002)(26005)(5660300002)(81156014)(2501003)(7736002)(81166006)(99286004)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3750; H:BYAPR11MB3558.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: LTO+8qYSRilMkw7Kz1U8qVRka8fIkEeONkVIhwav3CDUUhNx/tWKXg0y2a57Ow6GHkN0mRpy6c75piqQWrixpIdElNEPZBzA8KNFw9JmwcD+neQv3iaYepuW0bnKDE8XA7C6JZmylfbw/ZjtJiRlHvwdRiqr9SE1fwYvNuIvaDPirFjt4OF31zyrlWFswQJ38fDYSwCtyRjYH8PaIwKcZDniOj0u2CHMngH4BDjs+k2UWRCVUjBh1Hp4NKT5WyXH8xVXSXaLwg1xdd+twNEkHTrmkifMddfBSg+JbpLg8k3w85qvXzyDrHhB1KH+cdZgMaW1C+S15jDg5Eemib3M1eZ9/3Ts3YBkBIgT+exHZPDIQd1iBaoza8nTmbN1/OnXR65RjKfuHZuL/mTTVpZQ34//X2TL+USX3EQLY6DFznU=
Content-Type: multipart/alternative; boundary="_000_D8C801132F1435sgundaveciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a812a9b5-3e63-4566-499c-08d6b705f7e7
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Apr 2019 00:55:57.9562 (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-Transport-CrossTenantHeadersStamped: BYAPR11MB3750
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.18, xch-rcd-008.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/Vi-EZ5OizRLenR5kxPCVCYvqJ8M>
Subject: Re: [DMM] IETF104 DMM WG meeting minutes
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, 02 Apr 2019 00:56:05 -0000

Thank Marco. We will add this to the meeting minutes.

Sri


From: Marco Liebsch <Marco.Liebsch@neclab.eu<mailto:Marco.Liebsch@neclab.eu>>
Date: Thursday, March 28, 2019 at 2:36 AM
To: Sri Gundavelli <sgundave@cisco.com<mailto:sgundave@cisco.com>>, "dmm@ietf.org<mailto:dmm@ietf.org>" <dmm@ietf.org<mailto:dmm@ietf.org>>
Subject: RE: IETF104 DMM WG meeting minutes

Thanks for the minutes. Only on minor update of a note, as I think the Q&A could be clarified

Notes wite:
..
>   (?) Edge computing needs N3, not only N6?
>   (Marco) Yes, if interfering with GTP
..

The question was if the N3 interface is affected when MEC-5G system integration and operation is done per our proposal.
The answer was no as we don’t interfere with N3 and N9 but propose means to align N6 traffic treatment policies
which is not GTP encapsulated. Bringing the session anchor (UPF) to the network edge may mitigate/eliminate the use of
an N9 interface but N3 will definitely be there for 5G radio access. Hence it’s rather complementary than interfering.

About the slicing question: I said it’s complementary, though including identifies of resources/slices associated with the
data plane into the data models helps the controllers, which enforce traffic treatment policies in the data plane, to access
the right resources. So, the data model should take such identifiers into account, unless the controller has its own
binding between identifiers associated with the data plane where a policy applies and the associated resources/slice.

A more extensive Q&A in writing :)

Thanks,
marco



From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of Sri Gundavelli (sgundave)
Sent: Mittwoch, 27. März 2019 06:02
To: dmm@ietf.org<mailto:dmm@ietf.org>
Subject: [DMM] IETF104 DMM WG meeting minutes

Thank you Miya-san.

Folks -  Please review the below meeting minutes, and propose any corrections.

https://etherpad.ietf.org/p/notes-ietf-104-dmm?useMonospaceFont=true


Sri

From: "Miya Kohno (mkohno)" <mkohno@cisco.com<mailto:mkohno@cisco.com>>
Date: Tuesday, March 26, 2019 at 11:41 AM
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com<mailto:sgundave@cisco.com>>
Cc: "Miya Kohno (mkohno)" <mkohno@cisco.com<mailto:mkohno@cisco.com>>
Subject: IETF104 DMM WG meeting minutes

Hi Sri,

Thank you for the WG meeting today!
Sorry, I could not fully catch the Q&A and especially the name of persons..
That’d be great if someone could check and complete.

https://etherpad.ietf.org/p/notes-ietf-104-dmm?useMonospaceFont=true

Miya