From nobody Mon Apr 1 17:56:06 2019 Return-Path: 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 ; 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 ; 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 ; 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)" To: Marco Liebsch , "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: References: <0D39C2AC-3674-44E7-A688-9D89BE28E849@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: 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Apr 2019 00:56:05 -0000 --_000_D8C801132F1435sgundaveciscocom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Thank Marco. We will add this to the meeting minutes. Sri From: Marco Liebsch > Date: Thursday, March 28, 2019 at 2:36 AM To: Sri Gundavelli >, "dmm@ie= tf.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 integra= tion and operation is done per our proposal. The answer was no as we don=92t 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 net= work edge may mitigate/eliminate the use of an N9 interface but N3 will definitely be there for 5G radio access. Hence = it=92s rather complementary than interfering. About the slicing question: I said it=92s complementary, though including i= dentifies of resources/slices associated with the data plane into the data models helps the controllers, which enforce traffi= c treatment policies in the data plane, to access the right resources. So, the data model should take such identifiers into a= ccount, unless the controller has its own binding between identifiers associated with the data plane where a policy a= pplies 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 (sgunda= ve) Sent: Mittwoch, 27. M=E4rz 2019 06:02 To: dmm@ietf.org Subject: [DMM] IETF104 DMM WG meeting minutes Thank you Miya-san. Folks - Please review the below meeting minutes, and propose any correctio= ns. https://etherpad.ietf.org/p/notes-ietf-104-dmm?useMonospaceFont=3Dtrue Sri From: "Miya Kohno (mkohno)" > Date: Tuesday, March 26, 2019 at 11:41 AM To: "Sri Gundavelli (sgundave)" > Cc: "Miya Kohno (mkohno)" > 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=92d be great if someone could check and complete. https://etherpad.ietf.org/p/notes-ietf-104-dmm?useMonospaceFont=3Dtrue Miya --_000_D8C801132F1435sgundaveciscocom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <2FC1E079940136409163D1880E7BE56D@namprd11.prod.outlook.com> Content-Transfer-Encoding: quoted-printable
Thank Marco. We will add this to the meeting minutes.

Sri


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

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

 

Notes wite:

..

>   (?) Edge computing needs N3, n= ot only N6?

>   (Marco) Yes, if interfering wi= th GTP

..

 

The question was if the N3 interface is affected when MEC-5G syst= em integration and operation is done per our proposal.

The answer was no as we don=92t interfere with N3 and N9 but prop= ose means to align N6 traffic treatment policies
which is not GTP encapsulated. Bringing the session anchor (UPF) to the net= work edge may mitigate/eliminate the use of
an N9 interface but N3 will definitely be there for 5G radio access. Hence = it=92s rather complementary than interfering.

 

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

 

A more extensive Q&A in writing J

 

Thanks,

marco

 

 

 

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

 

Than= k you Miya-san.

 

Folk= s -  Please review the below meeting minutes, and propose any correcti= ons.

 

https://etherpad.ietf.org/p/notes-ietf-104-dmm?useMonospaceFont=3Dtrue<= /a>

 

 

Sri<= o:p>

 

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

 

Hi S= ri,

&nbs= p;

Than= k you for the WG meeting today!

Sorr= y, I could not fully catch the Q&A and especially the name of persons..

That= =92d be great if someone could check and complete.

&nbs= p;

https://etherpad.ietf.org/p/notes-ietf-104-dmm?useMonospaceFont=3Dtrue<= /a>

&nbs= p;

Miya=

--_000_D8C801132F1435sgundaveciscocom_-- From nobody Sun Apr 7 12:39:21 2019 Return-Path: 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 66B131201BC; Sun, 7 Apr 2019 12:39:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net 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 5MIWxixp8Onu; Sun, 7 Apr 2019 12:39:16 -0700 (PDT) Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 988C31200D6; Sun, 7 Apr 2019 12:39:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1554665956; bh=AdfOfaqBdZAcFZ1fRzz57pnWw5Ae4WOcURXI f05Db+M=; h=Received:From:Subject:To:Cc:Message-ID:Date:User-Agent: MIME-Version:Content-Type:Content-Transfer-Encoding: Content-Language:X-ELNK-Trace:X-Originating-IP; b=VGFVEaOOHEb4l5mA BKlvef7f/sfcJR2LkQMhDmlI9YLV0l6Zq1KBbxHbChULQ50+qZl4y+yQXr7FK8Gfjdt jyFjgGktWR/ahsps17TCqGjlN1CFeXSD6PPPnqDBgUzuxOMZ87gDZEJVEshbL5UN1+l fsEFLGLA/FbGO6quHeo5GJYGOHb+5OY6Zoh2AgjSvDKkKm1fmxksLc33rR7roNFCziz lTQWqFyJe+/zT7BEM8YRcLfH7XXt+jlw14j00w8SflkbPnEHsVjsWTUdLJ7xSAJLT/4 DLwl1BA2fLqI1/0VW9JqIIniPStLBDV4k8lPsNu0j+Bsa8nDBvpnwZ9alw== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=CncROhsLGS0oxATf4lpzRPhDMtogXFXdggz2RwNmfKV4m7s2Zhb55lksje5+ZAY1KfiKl0z8uvUXitLFS+nqjsUTsso0XCDSfnos/wkVTTYPVQmsyvzfgAg9w6gBorPbdtxjpGDL/sbLntI/WbFykbtExwj/XLPH4j+32A3Ti8KYlenONLbLeZIEFpYtBvspLFJEfnJvF1I5v0x1OR5xB+LxOehvBfCGt4rfregeSd2LhHPuuK4uJmHdIggA9d1VkISBWQdtVqjWgz36a5w0nD+lfh1+H7gG+tL20cP8JoRRd3DVmuXfzXeKar0lEeYkm2596R3PGhfMF0MIqrPhVA==; h=Received:From:Subject:To:Cc:Message-ID:Date:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Language:X-ELNK-Trace:X-Originating-IP; Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4) (envelope-from ) id 1hDDdK-000BwN-LL; Sun, 07 Apr 2019 15:39:14 -0400 From: Charlie Perkins To: "dmm@ietf.org" Cc: draft-ietf-dmm-fpc-cpdp@ietf.org, Suresh Krishnan Message-ID: <0c7dd732-2cba-d356-748f-ececb8bb9f2b@earthlink.net> Date: Sun, 7 Apr 2019 12:39:13 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956846b590522b13c952641287275c174e3197cb3e30e919f4b350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 99.51.72.196 Archived-At: Subject: [DMM] Disaggregated FPC documents X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Apr 2019 19:39:19 -0000 Hello folks, During the [dmm] meeting at IETF 104, I suggested that we should try breaking the YANG definitions out into a different document so that potential reviewers would not be intimidated by 150+ pages of document text.  I got reasonable support for at least trying the idea. If it doesn't work, I will volunteer to recombine them in the future. Briefly scanning the base document, I see that it needs another pass for readability as well.  That will take a while, so I propose to do that later after the submission of the two companion documents.  I will scan both documents for consistency and so on, but they are ready for submission now.  In the YANG document, I was considering to include a list (without definitions) in the Terminology section for the FPC terms that are defined in the base document.  Comments are welcome about that suggestion. Suresh has expressed the opinion that it would be O.K. to have the companion YANG document considered to be a WG document.  If anyone in the [dmm] group has objections to this proposal, please let me know. Thanks in advance! Regards, Charlie P. From nobody Sun Apr 7 16:01:02 2019 Return-Path: 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 8EF031201C5; Sun, 7 Apr 2019 16:01:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.748 X-Spam-Level: X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 8jYgBctB_9C0; Sun, 7 Apr 2019 16:00:58 -0700 (PDT) Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 47350120148; Sun, 7 Apr 2019 16:00:58 -0700 (PDT) Received: by mail-lf1-x131.google.com with SMTP id v24so5040343lfe.9; Sun, 07 Apr 2019 16:00:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5NWckcH8xXbpKLwQyJUEci5kzAbs9RFIgIJEhr11psM=; b=Fp/2nddyDRpskcXUYgC94c9c4x7XCs2xRRY4fG7OfgAvUkoGZZwO7L3QmBEHZyrRzu OotZ63HrttnYZrwaurKKdl2IT5B2hoE0YsGP8GI2oV5jOagPYguPODhpDYrB180v1hSH S13P8MEHhaauRj29bChyYqmademKAuifVaL84kpOLRak6BIhjnYksSNWRbiqfZoFXMcw uqlF5oqKDfAp8W+jp37bFsS1fRDXAGoksbcCj+mXWirHScwO1OxjxcagllHW/z45ve2f rsgD7qSiG+uotOxY1xnjbxC45vBDmfz+K9aA9Y3WNxiJfqMvbxno128Z32wOrGylFh9r MIwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5NWckcH8xXbpKLwQyJUEci5kzAbs9RFIgIJEhr11psM=; b=Ngxr+cOZIBfEbq4wN3VrJ/YvSXfekbUyOBHG0dPUbiB9hsceBfh3xlXAv9nu93BPSc LHNs7sdT9rJh414+mlPXnuANu/SwpyYDgY2MuVKW0bwudsZD9n3ITu0fj59ZrB9nB9q8 s4rNkTIrzl7qI7vNmNyM9BQ7blQDvX/IED4FEjm1ELeiYCF6HayGW6eiWWQz1R1dpYJV BQPSPqOK2tprMtKi8EmzHJriWohxxocjcqLIqnH65zYcoU/TcozkNac6D4alLOkHFbXd CAxHFkTV6V1xW+GzfLk6y3bf3MdaQa1AsXT3IJl0D+Lv9lVDOzJLdag1boNwvJgrwytQ ifbA== X-Gm-Message-State: APjAAAWA+YZlj+03D0CF8H9R7dlfXgln/m3SrUs3qpCefbHNReADuO2R t2Nnc1isCjCE/8e8VBdeuUVQ2YvXe8klxax1ZyQ= X-Google-Smtp-Source: APXvYqwcyKZlxTwvahZcjbA68h6TnjwQuyqmvXSfMgRSOeyuhTaog3L2UZFgo43Ru/34tKT1rDyDdDe3byNf/beKddc= X-Received: by 2002:ac2:5189:: with SMTP id u9mr8873015lfi.3.1554678056365; Sun, 07 Apr 2019 16:00:56 -0700 (PDT) MIME-Version: 1.0 References: <0c7dd732-2cba-d356-748f-ececb8bb9f2b@earthlink.net> In-Reply-To: <0c7dd732-2cba-d356-748f-ececb8bb9f2b@earthlink.net> From: Lyle Bertz Date: Sun, 7 Apr 2019 18:00:43 -0500 Message-ID: To: Charlie Perkins Cc: dmm , draft-ietf-dmm-fpc-cpdp@ietf.org, Suresh Krishnan Content-Type: multipart/alternative; boundary="0000000000004a321e0585f8b16d" Archived-At: Subject: Re: [DMM] Disaggregated FPC documents X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Apr 2019 23:01:01 -0000 --0000000000004a321e0585f8b16d Content-Type: text/plain; charset="UTF-8" As the YANG document is standalone you may want to ensure you are still complying with netmod criteria for such RFCs. On Sun, Apr 7, 2019, 2:39 PM Charlie Perkins wrote: > Hello folks, > > During the [dmm] meeting at IETF 104, I suggested that we should try > breaking the YANG definitions out into a different document so that > potential reviewers would not be intimidated by 150+ pages of document > text. I got reasonable support for at least trying the idea. If it > doesn't work, I will volunteer to recombine them in the future. > > Briefly scanning the base document, I see that it needs another pass for > readability as well. That will take a while, so I propose to do that > later after the submission of the two companion documents. I will scan > both documents for consistency and so on, but they are ready for > submission now. In the YANG document, I was considering to include a > list (without definitions) in the Terminology section for the FPC terms > that are defined in the base document. Comments are welcome about that > suggestion. > > Suresh has expressed the opinion that it would be O.K. to have the > companion YANG document considered to be a WG document. If anyone in > the [dmm] group has objections to this proposal, please let me know. > > Thanks in advance! > > Regards, > Charlie P. > > > > _______________________________________________ > dmm mailing list > dmm@ietf.org > https://www.ietf.org/mailman/listinfo/dmm > --0000000000004a321e0585f8b16d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
As the YANG document is standalone you may want to ensure= you are still complying with netmod criteria for such RFCs.

On Sun, Apr 7, = 2019, 2:39 PM Charlie Perkins <charles.perkins@earthlink.net> wrote:
Hello folks,

During the [dmm] meeting at IETF 104, I suggested that we should try
breaking the YANG definitions out into a different document so that
potential reviewers would not be intimidated by 150+ pages of document
text.=C2=A0 I got reasonable support for at least trying the idea. If it doesn't work, I will volunteer to recombine them in the future.

Briefly scanning the base document, I see that it needs another pass for readability as well.=C2=A0 That will take a while, so I propose to do that =
later after the submission of the two companion documents.=C2=A0 I will sca= n
both documents for consistency and so on, but they are ready for
submission now.=C2=A0 In the YANG document, I was considering to include a =
list (without definitions) in the Terminology section for the FPC terms that are defined in the base document.=C2=A0 Comments are welcome about tha= t
suggestion.

Suresh has expressed the opinion that it would be O.K. to have the
companion YANG document considered to be a WG document.=C2=A0 If anyone in =
the [dmm] group has objections to this proposal, please let me know.

Thanks in advance!

Regards,
Charlie P.



_______________________________________________
dmm mailing list
dmm@ie= tf.org
https://www.ietf.org/mailman/listinfo/dmm
--0000000000004a321e0585f8b16d-- From nobody Fri Apr 19 23:50:37 2019 Return-Path: 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 3740A12007C; Fri, 19 Apr 2019 23:50:35 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Sri Gundavelli via Datatracker To: X-Test-IDTracker: no X-IETF-IDTracker: 6.95.0 Auto-Submitted: auto-generated Precedence: bulk Cc: Dapeng Liu , iesg-secretary@ietf.org, dmm-chairs@ietf.org, maxpassion@gmail.com, dmm@ietf.org Message-ID: <155574303521.5432.10940142611601231273.idtracker@ietfa.amsl.com> Date: Fri, 19 Apr 2019 23:50:35 -0700 Archived-At: Subject: [DMM] Publication has been requested for draft-ietf-dmm-distributed-mobility-anchoring-13 X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.29 List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Apr 2019 06:50:35 -0000 Sri Gundavelli has requested publication of draft-ietf-dmm-distributed-mobility-anchoring-13 as Informational on behalf of the DMM working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-dmm-distributed-mobility-anchoring/ From nobody Sat Apr 20 00:02:02 2019 Return-Path: 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 3343D120099; Sat, 20 Apr 2019 00:02:00 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Sri Gundavelli via Datatracker To: X-Test-IDTracker: no X-IETF-IDTracker: 6.95.0 Auto-Submitted: auto-generated Precedence: bulk Cc: max.ldp@alibaba-inc.com, iesg-secretary@ietf.org, dmm-chairs@ietf.org, dmm@ietf.org, Dapeng Liu Message-ID: <155574372020.10277.17306112267507095422.idtracker@ietfa.amsl.com> Date: Sat, 20 Apr 2019 00:02:00 -0700 Archived-At: Subject: [DMM] Publication has been requested for draft-ietf-dmm-pmipv6-dlif-04 X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.29 List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Apr 2019 07:02:00 -0000 Sri Gundavelli has requested publication of draft-ietf-dmm-pmipv6-dlif-04 as Experimental on behalf of the DMM working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-dmm-pmipv6-dlif/ From nobody Sun Apr 28 22:48:09 2019 Return-Path: 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 396B6120074; Sun, 28 Apr 2019 22:48:07 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: dmm@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.95.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: dmm@ietf.org Message-ID: <155651688708.20938.17312789449050606002@ietfa.amsl.com> Date: Sun, 28 Apr 2019 22:48:07 -0700 Archived-At: Subject: [DMM] I-D Action: draft-ietf-dmm-fpc-yang-00.txt X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.29 List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2019 05:48:07 -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 : YANG for Protocol for Forwarding Policy Configuration (FPC) Authors : Satoru Matsushima Lyle Bertz Marco Liebsch Sri Gundavelli Danny Moses Charles E. Perkins Filename : draft-ietf-dmm-fpc-yang-00.txt Pages : 82 Date : 2019-04-11 Abstract: This document provides YANG modules to exhibit a data model for the information models defining Forwarding Policy Configuration (FPC) to manage the separation of data-plane and control-plane. FPC defines a flexible mobility management system using FPC agent and FPC client functions. A FPC agent provides an abstract interface to the data- plane. The FPC client configures data-plane nodes by using the functions and abstractions provided by the FPC agent for the data- plane nodes. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dmm-fpc-yang/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dmm-fpc-yang-00 https://datatracker.ietf.org/doc/html/draft-ietf-dmm-fpc-yang-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/