Re: [DMM] Light review of draft-ietf-dmm-fpc-cpdp-12

"Bertz, Lyle T [CTO]" <Lyle.T.Bertz@sprint.com> Wed, 06 March 2019 03:35 UTC

Return-Path: <Lyle.T.Bertz@sprint.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 3DE1D130E6B for <dmm@ietfa.amsl.com>; Tue, 5 Mar 2019 19:35:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 t05ui3ncFHgK for <dmm@ietfa.amsl.com>; Tue, 5 Mar 2019 19:35:53 -0800 (PST)
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-eopbgr680131.outbound.protection.outlook.com [40.107.68.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD44B130E30 for <dmm@ietf.org>; Tue, 5 Mar 2019 19:35:52 -0800 (PST)
Received: from DM5PR05MB2922.namprd05.prod.outlook.com (10.168.176.22) by DM5PR05MB3643.namprd05.prod.outlook.com (10.174.243.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.11; Wed, 6 Mar 2019 03:35:43 +0000
Received: from DM5PR05MB2922.namprd05.prod.outlook.com ([fe80::45b7:ade5:42fb:9356]) by DM5PR05MB2922.namprd05.prod.outlook.com ([fe80::45b7:ade5:42fb:9356%3]) with mapi id 15.20.1686.016; Wed, 6 Mar 2019 03:35:43 +0000
From: "Bertz, Lyle T [CTO]" <Lyle.T.Bertz@sprint.com>
To: "Dirk.von-Hugo@telekom.de" <Dirk.von-Hugo@telekom.de>, "cjbc@it.uc3m.es" <cjbc@it.uc3m.es>, "lyleb551144@gmail.com" <lyleb551144@gmail.com>, "marco.liebsch@netlab.nec.de" <marco.liebsch@netlab.nec.de>
CC: "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] Light review of draft-ietf-dmm-fpc-cpdp-12
Thread-Index: AQHUc/cbj3BltSpVTUGT4N2sBB3EJaX+IEcAgACRK4I=
Date: Wed, 06 Mar 2019 03:35:43 +0000
Message-ID: <DM5PR05MB29222F7EC72FDA9A31175B7AA4730@DM5PR05MB2922.namprd05.prod.outlook.com>
References: <150435e971341cb3918d2c55c18c29dc88348065.camel@it.uc3m.es>, <LEXPR01MB066908572C4910E25345A00ED1720@LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE>
In-Reply-To: <LEXPR01MB066908572C4910E25345A00ED1720@LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Lyle.T.Bertz@sprint.com;
x-originating-ip: [136.63.67.169]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ec7d769b-d833-4a8e-2804-08d6a1e4d059
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(4618075)(2017052603328)(7153060)(7193020); SRVR:DM5PR05MB3643;
x-ms-traffictypediagnostic: DM5PR05MB3643:
x-ms-exchange-purlcount: 2
x-microsoft-exchange-diagnostics: 1; DM5PR05MB3643; 23:czkUUYlij8pf2Cx659R6LHSYYx5iVzRzJ7ALKzblRnyjpEdPWI/3p3ekDP5JJWmecMK4rRsijwUcUC8FlT7YjTTQJ/4c3xlSazVWYnDAkxtHSR9joyGmuIO4lX2oqq0DyfmTxH7XAav3M11Gf5JYPvgZtgxyt2Gw3D2Uo0a01C7wbQ7sMLjsoB5m1ey5rornb9Lo7TbM7CGskwxECFnHexVzZhw34t72q0XkmGOfxKWeca+nIQD25HKkZuhY6K0tOaPWDxaViadHPi53GDLjfLhPGzAnzdRG4iNndC/1i2wuzjkmiQiwSbLptp0N1A8j1j6bEZ9AHKy46pp7/k3LDvwxDclvoD0+CLarLBJ35HyfeN2XReMqwNthpLc7Bf/Qf8xyYA+nvzh7M/QsAhv+Fu1ZkpW9TpfGTw6/fAfcI6/POTtdZ7GNl44Cwfh4ry5XH/B3zG92EgYa2F8ulQWm6HHYsbnBCT4LDdfbqv4HJcGdNsc+cvhowZNYZkeVSf5olPFHTH8Nr96Zkiu11BUO3js8pUEISfRkmJVnXoIuCx+RoG0tvYw12QKHPbbZZ3cINuyxxyMXtD7gmeB03navhy+5QSxvjMne4so9ztIwU7ofDvmxXVa6YxtQMFAaj2vaxscoYEmiUKsF8oCejsW5mrIaWPYU2S1dWoIsaEzoMQ2barb0E2+qh6b19mPwEm+mTrQHw9wByUFlNkTXPjkePSC1PQwqPrboAtv3+BY0OmRTjKUmBo6RtpFEr0As2YxymVxN6G+9Bg9WxDUcRxFJLXpLBwnZpfI5biAzRT90IUXM+vd1deC98fLqiMy9GtmilFIBXlIBiJhxgvfFUzcDso8KMRP4Q1reneJZ4skj227wuOqQrw5d82rElqGYTJKO28WG5ofurRQxodqhBtqjVYKzimkqYE4tg6McjEyssWwa2nyy81pcZCoDlpkswggByHW0YGVINuEQOQxWAdU09OwkdJFnP/W3iE7d1nXTbli1u+2I0UTAvtTO9Ti72R/uSq2G5+Z8nXSCxESDPt2JmHG3YhFfjIwQRqKjd0jA7gMeHu2HGcJsp3IHcOfaVFJRrmYrL4kvjpzVs+5/AaJohKnvNOvybNgzpVL5GIj70IQTV6bIoLkRNYxK30YOdQtLCW6XegkVR0KxdcLdU1AGZ0ANuZqJ/BVejBH/XwqhMP743votuDh8MhdqcpueLuL56SQyboJSpz80zXkOelKYb5QI9AizRSRFlcyh/AzEQ3ykoLbExPLE6M98vuw1/bPbKMrdP+UrEGBDOncItUkFFgvZXIj74qbz+jGT75JK1SZuGUQFKvv23BOanhItqJf5rmvZs/PzAZ2Sm/c5kUU5pvML7/qOuq4F3WoosfTzawoZ9PAOWyotuM47WesVaFSBa5Rm8b8ATtWdyFNIfgt7R3WxKX60qFZyEVKq3rgCgkPh1R/fWa9qGH5F6yXX6khfIednewEbWOxXE4l2v3D0ow==
x-microsoft-antispam-prvs: <DM5PR05MB36430D61B3B7A7C3E4E33C28A4730@DM5PR05MB3643.namprd05.prod.outlook.com>
x-forefront-prvs: 0968D37274
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(136003)(346002)(366004)(39860400002)(13464003)(189003)(199004)(2906002)(14454004)(97736004)(3846002)(7736002)(476003)(446003)(478600001)(66066001)(966005)(11346002)(6606003)(6116002)(2201001)(71200400001)(256004)(486006)(74316002)(14444005)(81166006)(8676002)(33656002)(81156014)(71190400001)(5024004)(86362001)(105586002)(106356001)(110136005)(45080400002)(53546011)(26005)(54896002)(6306002)(6436002)(9686003)(236005)(7696005)(8936002)(102836004)(4326008)(53936002)(25786009)(6506007)(68736007)(6246003)(186003)(66574012)(19627405001)(2501003)(316002)(55016002)(99286004)(229853002)(5660300002)(52536013)(606006)(76176011)(72206003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3643; H:DM5PR05MB2922.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: sprint.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: bh/bGo34FGlbq/zeU+raIHHi4vueFsWljzXTymzkWRIi0HnWezLFmw/0egTsHbVrWNhnX0K/DB+xX6JYny7zq/ILvdnz2r+WL1B5QuDtZImCOtBE5CvjzuYryf/WQq5ULVTH6yHDl8uIOjf/Bbp3gRw6Z5EHG4rflUSpaf4iGIjKblcBVCz1lxjkBQ8IfW9DOSL9H7DW+2/ntsPWlWRpIZa7WN4UGjYuyIpF7xIkcDXIaCpv+88drZFTRJuUOOD9/WDhiYpArd70srNfu7Ch6g/zRHVOOYKQQpchzcdbtwzIEAXCjeqgYTd0bAiggy+8pc5++BVin9JfqkPJICF4HYuNayjcwwHvNOUTsr6vcKDLI0ZhcqtOVMtM06+Ch/HisJIbmdlzcT+N4hUKNISHRi7hNocaRdRdkh7za6b3yiA=
Content-Type: multipart/alternative; boundary="_000_DM5PR05MB29222F7EC72FDA9A31175B7AA4730DM5PR05MB2922namp_"
MIME-Version: 1.0
X-OriginatorOrg: sprint.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ec7d769b-d833-4a8e-2804-08d6a1e4d059
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2019 03:35:43.8702 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f8bc0ac-bd78-4bf5-b55f-1b31301d9adf
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3643
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/ex_UFx7BNoanfMs3jJapoO9UwAo>
Subject: Re: [DMM] Light review of draft-ietf-dmm-fpc-cpdp-12
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: Wed, 06 Mar 2019 03:35:56 -0000

Dirk,


It is not difficult to extend FPC for BNG as most of the rules are similar in structure.   My team built an FPC agent and we are now building Sx (3GPP CUPS PFCP) but it is at best a subset of FPC and has some holes.  I am unsure I would materially update FPC based on what I have learned implementing the Sx protocol PFCP.


Generally extending the forward actions and filters, assuming you actually need to extend beyond the filter-rule which is based on RFC 5777 and a very generic structure, is not a difficult task.  The base structure is quite generic but many people get hung up on the 3GPP support and extensions later in the spec.


The spec can be overwhelming as the use cases for forwarding, integration with charging, ID allocation for forward, etc, is not trivial.


Lyle



________________________________
From: dmm <dmm-bounces@ietf.org> on behalf of Dirk.von-Hugo@telekom.de <Dirk.von-Hugo@telekom.de>
Sent: Tuesday, March 5, 2019 12:49:04 PM
To: cjbc@it.uc3m.es; lyleb551144@gmail.com; marco.liebsch@netlab.nec.de
Cc: dmm@ietf.org
Subject: Re: [DMM] Light review of draft-ietf-dmm-fpc-cpdp-12

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Dear all,
searching for update on this (meanwhile expired) draft I only found the 103 minutes quoting Charlie with " We should get a solid architectural and informational yang that should be applicable."
I also read Carlos' comment on more general applicability and wonder whether the topic of CUPS addressed might also apply to the recently approved BoF at #104 on BNG Control-plane And User-plane Separation (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fwg%2Fbcause%2Fabout%2F&amp;data=02%7C01%7Clyle.t.bertz%40sprint.com%7C6e37a6bda84549e8c97708d6a19b4837%7C4f8bc0acbd784bf5b55f1b31301d9adf%7C0%7C0%7C636874085646715585&amp;sdata=700Fi5IEAkBMenqn1ecqN9kzWOzDtZ5IziwBGhQngrg%3D&amp;reserved=0) as a 'disruptive approach' ;-)
BBF in liaison with 3GPP on 5GWWC (FMC) might also search for a more universal approach to DP/UP nodes as BNG ...
What do you think?
Kind regards
Dirk


-----Original Message-----
From: dmm <dmm-bounces@ietf.org> On Behalf Of Carlos Jesús Bernardos Cano
Sent: Samstag, 3. November 2018 04:59
To: Lyle Bertz <lyleb551144@gmail.com>; Marco Liebsch <marco.liebsch@netlab.nec.de>
Cc: dmm <dmm@ietf.org>
Subject: [DMM] Light review of draft-ietf-dmm-fpc-cpdp-12

Hi Lyle, Marco,

I committed to perform a review of the FPC draft. Though I have not been able to perform an in-depth one in time for Bangkok, please find attached a light one (among other things, I have not gone through the annexes).

I don't have major comments. I think the use of normative text should be improved, as there are parts that are not clear if the text is supposed to be normative or not.

Thanks, talk to you next week.

Carlos
_______________________________________________
dmm mailing list
dmm@ietf.org
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fdmm&amp;data=02%7C01%7Clyle.t.bertz%40sprint.com%7C6e37a6bda84549e8c97708d6a19b4837%7C4f8bc0acbd784bf5b55f1b31301d9adf%7C0%7C0%7C636874085646715585&amp;sdata=Q3F1FcxIGfE5KAetjKXyCnXfGVtpcv4Qlu5D8NRGzsA%3D&amp;reserved=0