Re: [netmod] Liaison statement to ORAN - v2

Scott Mansfield <scott.mansfield@ericsson.com> Tue, 24 November 2020 16:29 UTC

Return-Path: <scott.mansfield@ericsson.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B959A3A11F1 for <netmod@ietfa.amsl.com>; Tue, 24 Nov 2020 08:29:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 iTmFKiO2gEkd for <netmod@ietfa.amsl.com>; Tue, 24 Nov 2020 08:29:57 -0800 (PST)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2067.outbound.protection.outlook.com [40.107.236.67]) (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 7374A3A11EC for <netmod@ietf.org>; Tue, 24 Nov 2020 08:29:56 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Ow5r/hcSC+4690eEq6LZmsAXjyPJg791YsIq8Cw9DJZKlFq4XjFyCsbxnWjPwUdlFSAD2irq3GqOCqtPMAzIO3mH7CkJ9w6zqhDVe3bCn6TyVutOmC+YPNRSOY1KG4NcXFo1NCrppxf23zqAzimyqx2F3+Cn5UWEXRFJAhj/EhoK0WQNaG2ogvXIRag5wnaqU9URV7Bt7sUUdWr1WFBr/q2tpM+47g9ElFMFqKo3vOJHVVInFF487+MDMAph6P14+0VV1V0P4ob/ZrLXcB49tiMdI7N3xtnnw3qfn92g98IHhvat4pkyce3sMBWYSJFxXpknr/bYGW6CsAYfV71Sbw==
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-SenderADCheck; bh=ZqsbFdGWCZcf/ghRDhC0MrlUOsmAqwVYt17S3/sWTwY=; b=B5dYU0FPsycijZd1iKaltASTv+VKYjd2lc63kqvLMQWhCROXFY8BxTWv4hY/zRG5Mn4rI8VyhDfxQ8TuNLcBsNA8D0/OYvhRB5Z4X4Xx5Z25OIWSxFuczEdFP7Ev2UnxLfJg4JebfXgwi1HInub3lrx8nzimCe1n3ZIiji+5duBTTeotL2urCYiUp1SixVQbgxUkWwZ7YgT8wc5EPiqYgAG6+mr6PPyw2ieKevrubG1llAPF6t/AOofKyiJgMJK9amfb4XDqz+4Xx6LkoMs+mENbOBDarM5wcTraQ296pazSnyVojI6TPhR0hSZMqRCVvVs4mxWzfVxJP/8bQot6tw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZqsbFdGWCZcf/ghRDhC0MrlUOsmAqwVYt17S3/sWTwY=; b=cOX55CzZVVK22AiUQ2h/1qh/1ORDQ9fkoQg9dKtMdQ1QbDcAb1zwy+imiA4TvMjTr9oJaw03xxA1cVP6MKCpftIy+0AEQsKGLnU29fYs5eA0TiXb89u214uMykUnZCT7bKxxELn6r6g+/rDhMfMPIbTk6uK/2oSsOzPTpWMoSw4=
Received: from BL0PR1501MB4130.namprd15.prod.outlook.com (2603:10b6:208:86::17) by BLAPR15MB3908.namprd15.prod.outlook.com (2603:10b6:208:279::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3589.21; Tue, 24 Nov 2020 16:29:53 +0000
Received: from BL0PR1501MB4130.namprd15.prod.outlook.com ([fe80::4d38:46de:48d0:c434]) by BL0PR1501MB4130.namprd15.prod.outlook.com ([fe80::4d38:46de:48d0:c434%4]) with mapi id 15.20.3589.030; Tue, 24 Nov 2020 16:29:53 +0000
From: Scott Mansfield <scott.mansfield@ericsson.com>
To: =?utf-8?B?QmFsw6F6cyBMZW5neWVs?= <balazs.lengyel@ericsson.com>, "Jan Lindblad (jlindbla)" <jlindbla@cisco.com>
CC: Robert Petersen <robert.petersen@ericsson.com>, Jacqueline Beaulac S <jacqueline.s.beaulac@ericsson.com>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Liaison statement to ORAN - v2
Thread-Index: AdbCe25WlTo4vbcGQO2T+xrgG1s6eQAAb/6Q
Date: Tue, 24 Nov 2020 16:29:52 +0000
Message-ID: <BL0PR1501MB4130552AA36B4A4DB85B56978BFB0@BL0PR1501MB4130.namprd15.prod.outlook.com>
References: <AM6PR0702MB3557D375BD21E08D7C94F630F0FB0@AM6PR0702MB3557.eurprd07.prod.outlook.com>
In-Reply-To: <AM6PR0702MB3557D375BD21E08D7C94F630F0FB0@AM6PR0702MB3557.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: ericsson.com; dkim=none (message not signed) header.d=none;ericsson.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [24.112.244.55]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 00818bdc-bfc5-4797-3739-08d890962bf7
x-ms-traffictypediagnostic: BLAPR15MB3908:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BLAPR15MB39084A099328A5D3C644AE498BFB0@BLAPR15MB3908.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:1303;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: laGi8bEFLX0LgV833nnjIzadwr5uJx/wYofD/oalMSnrKBQ6S1li/3DFN+ujYKYFwb259km9prjROlJI3eX1/zeQgESVHrjg6kpyDEt82xDZloZK89RFb6CaphwtT4+RF1RGjmy0ZJ5K2NdA4WV7VB/4IPK5XYyZ9D9DhLJJ9sgtoclbr3I6RE2n8rNo3yxYahN5U0ksYFbpqU4TY64zA1EZPirqtL0xpfV4N8PRc4LYTIxYahOfCSu181yUHlVjY2eoUlTBJFTM15WMVSzscgvf9NCFNM6mhf4FcIt07gpojehDu8vJstVp704AMN0Yu4fymcZrz2zyDBM8f4kqcQ6GbEAgztYjbltZlVp9Tlh/h8Y7wE0dsDgrfzsdX7EqOqjdMw5Igi77/hqIH5vVzA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BL0PR1501MB4130.namprd15.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(376002)(396003)(346002)(136003)(39860400002)(54906003)(76116006)(166002)(8936002)(66616009)(2906002)(66446008)(66946007)(66476007)(7696005)(5660300002)(26005)(83380400001)(316002)(86362001)(64756008)(6506007)(110136005)(71200400001)(66574015)(53546011)(66556008)(186003)(4326008)(99936003)(33656002)(52536014)(55016002)(478600001)(44832011)(8676002)(9686003)(966005); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: EjDaucOCaOGofuoLLo7Pp1VQ4PglMVzelBqMpXF3XyZFdCaAfpC0f7bD+tCkH5CCzDQf4LB6RWJJVYXzB7O4dlvfx/u9iYt5Mh/KYSyUcq0l3LK/kdLWNtC5VfCIr9BB373UMSHc9beqsgb+Ov4vGgnlPgXhu7nT72SeSevIQOiGd5JTv6TrLEESIFjw/EBt3Mv+9ZCAaRPt27cHFM5z01P6PheqCMnNqsNlKfiY+Gw5sPnyQ/LlLYPgNF5/0T2JvSBMXwBus3YAz4fLON20cSHfkdDP9KYXSC2s07Qn6AxHPMluJ0qmU5IgprGlDCjSYrkLGq/rWihBfX5WtDExUr+gl+VDdVdqVpmK5U95DABFSGl0xbxPmynoCcjIsnFFJDgZBaTyM/BFrhnGkRc05lMBcH2QlbBQZ6mKLd2Llw+WcuLXGzpU5zdZDptmgRPT5foyO4zJWmWg3frau7yFLmFBv+8nMkPoklENSODhpLvN/rYobTGBjxiwjf3/U/Ej+uRU9yck8dGdp1WWYF1mUF6pgDr2Rb5uBiyMmNgE8pSAnOCtBuoemjH7AF98bEYj+N1oT0PoMmdd/ujoPLFFhfu7Zc5J3e/rIJ4DQYVg4JQg5022ShHKW10ykIinWuBNCPX5UrLcr3SyC5gNxlyAFGeaebQFt49FglQMVeuMEW//ue2jUAj3NhuLthB+ZOi7wmSQgnNjrh3LTG34lzeHefy2OE8Qgt9BNotOt00aOMrChD3mxarUPu/0VHckg6b8mwdh3at+kDvBfYiFXxW+UIyVn90teoEG59Cd51iTeQNNmlsiS4eHhmn4voQ63KLVnsYWoAXm2W1f1Bvl5fKI9Qhx6pTu379On7thi5piLJ8Xei6VmQdL534KnrT9Zn59Z96Tp8klVAbOydA3RrbATA==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0139_01D6C255.1EEE49F0"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BL0PR1501MB4130.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 00818bdc-bfc5-4797-3739-08d890962bf7
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Nov 2020 16:29:52.8572 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: CpqdokZdMrMj05zdxssc5OXuLMpyNr6NXit5MF2BhT6eDyXSiyr8SDjaN+EuBqM1gY+w/IEg2TBwQMh7hMeBT+R8yrzci0UQbhUsX1ox8yI=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLAPR15MB3908
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/S85vNc4bCfdHnbZA4BMiiZ9Nzyw>
Subject: Re: [netmod] Liaison statement to ORAN - v2
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2020 16:30:00 -0000

Thanks Balázs, 

 

Editorial:  The group is call O-RAN Alliance and should be abbreviated O-RAN.

 

So..  suggestions including boiler plate…

 

<liaison>

>From Groups     netmod

>From Contact     Scott Mansfield

To Group             O-RAN Alliance (SDFG, WG1, WG4, WG5, WG9)

To Contacts        Brian Daly: brian.k.daly@att.com <mailto:brian.k.daly@att.com> ; Xiaofei Xu: xuxiaofei@chinamobile.com <mailto:xuxiaofei@chinamobile.com> ; Paul Smith, ps7360@att.com <mailto:ps7360@att.com> ; Jinri Huang, huangjinri@chinamobile.com <mailto:huangjinri@chinamobile.com> ; Anil Umesh umesyu@nttdocomo.com <mailto:umesyu@nttdocomo.com> ; Shankar Venkataraman Shankar.Venkatraman@VerizonWireless.com <mailto:Shankar.Venkatraman@VerizonWireless.com> ; Mohamad Yassin mohamad.yassin@orange.com <mailto:mohamad.yassin@orange.com> ; Kunihiko Teshima kunihiko.teshima.hg@nttdocomo.com <mailto:kunihiko.teshima.hg@nttdocomo.com> ; Elena Myhre elena.myhre@ericsson.com <mailto:elena.myhre@ericsson.com> ; Abdellah Tazi at8551@att.com <mailto:at8551@att.com> ; Dechao Zhang zhangdechao@chinamobile.com <mailto:zhangdechao@chinamobile.com> ; Reza Vaez-Ghaemi reza.vaezghaemi@viavisolutions.com <mailto:reza.vaezghaemi@viavisolutions.com> 

Cc OPS ad, netmod wg

Response Contact            scott.mansfield@ericsson.com

Technical Contact             scott.mansfield@ericsson.com

Purpose               For information

Attachments      

Body

IETF NETMOD working group requests O-RAN avoid using deviations as part of its specification. When O-RAN plans to reuse specifications from other standard bodies or industry groups it should not remove or change functionality.  If variations are needed compared to a base model, O-RAN should ask the original group to include feature statements in the original YANG module.

 

As documented in https://tools.ietf.org/html/rfc7950#section-7.20.3  “... deviations MUST never be part of a published standard, since they are the mechanism for learning how implementations vary from the standards.”

As documented in  <https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-01#section-5.8.1> https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-01#section-5.8.1 the usage of deviations would prevent:

*	Vendors to claim conformance to both O-RAN and 3GPP specifications (which are in some cases used as a base for the O-RAN YANG models)
*	Vendors to implement their own deviations for the same YANG schema nodes

 

Note: The problems with deviations exists even if YANG modules are used without YANG packages.

 

</liaison>

 

Regards,

-scott.

 

From: netmod <netmod-bounces@ietf.org> On Behalf Of Balázs Lengyel
Sent: Tuesday, November 24, 2020 11:04 AM
To: Jan Lindblad (jlindbla) <jlindbla=40cisco.com@dmarc.ietf.org>rg>; Balázs Lengyel <balazs.lengyel=40ericsson.com@dmarc.ietf.org>
Cc: Robert Petersen <robert.petersen@ericsson.com>om>; Jacqueline Beaulac S <jacqueline.s.beaulac@ericsson.com>om>; netmod@ietf.org
Subject: Re: [netmod] Liaison statement to ORAN - v2

 

Hello, 

Based on discussion here is version2 of the proposed liaison text:

 

Liaison text v2:

 

IETF NETMOD working group requests ORAN to avoid using deviations as part of its specification. When ORAN plans to reuse specifications from other standard bodies or industry groups it should not remove or change functionality.  If variations are needed compared to a base model, ORAN should ask the original group to include feature statements in the original YANG module.

 

As documented in https://tools.ietf.org/html/rfc7950#section-7.20.3  “... deviations MUST never be part of a published standard, since they are the mechanism for learning how implementations vary from the standards.”

As documented in  <https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-01#section-5.8.1> https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-01#section-5.8.1 the usage of deviations would prevent:

*	Vendors to claim conformance to both ORAN and 3GPP specifications (which are in some cases used as a base for the ORAN YANG models)
*	Vendors to implement their own deviations for the same YANG schema nodes
*	 

Note: The problems with deviations exists even if YANG modules are used without using YANG packages.

 

 

Regards Balazs

 

From: netmod <netmod-bounces@ietf.org <mailto:netmod-bounces@ietf.org> > On Behalf Of Jan Lindblad (jlindbla)
Sent: 2020. november 19., csütörtök 11:00
To: Balázs Lengyel <balazs.lengyel=40ericsson.com@dmarc.ietf.org <mailto:balazs.lengyel=40ericsson.com@dmarc.ietf.org> >
Cc: Robert Petersen <robert.petersen@ericsson.com <mailto:robert.petersen@ericsson.com> >; Jacqueline Beaulac S <jacqueline.s.beaulac@ericsson.com <mailto:jacqueline.s.beaulac@ericsson.com> >; netmod@ietf.org <mailto:netmod@ietf.org> 
Subject: Re: [netmod] Liaison statement to ORAN

 

Balázs, 

 

+1

I think this is an important message to O-RAN, and I know similar ideas have been up for discussions in other SDOs as well. I think your proposed way of conveying the message is good.  

 

Best Regards,

/jan

 

 

On 18 Nov 2020, at 09:09, Balázs Lengyel <balazs.lengyel=40ericsson.com@dmarc.ietf.org <mailto:balazs.lengyel=40ericsson.com@dmarc.ietf.org> > wrote:

 

Hello,

In connection to the draft  <https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-01> https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-01 I propose to send a liaison statement from IETF Netmod to ORAN.

 

The issue: 3GPP is standardizing a good number of YANG modules as part of the 3gpp TS 28.541 and 28.623 ( <https://protect2.fireeye.com/v1/url?k=de649d27-81ffa5c5-de64ddbc-86073b36ea28-bd22f142f9b85dd6&q=1&e=5a78b7c7-b77b-4866-87e7-f206e86f6f2b&u=https%3A%2F%2Fforge.3gpp.org%2Frep%2Fsa5%2FMnS%2Ftree%2FRel17-draft%2Fyang-models> https://forge.3gpp.org/rep/sa5/MnS/tree/Rel17-draft/yang-models). 

ORAN plans to re-use this models, but possibly refine them in some ways. They are considering using deviations to do this. 

E.g. change config=true schemas node to config=false. This creates problems as documented in  <https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-01%23section-5.8.1> https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-01#section-5.8.1

 

-   Deviations by an SDO (standard defining organization) prevent implementations from reporting their own deviations for the same nodes.

-   Deviations by an SDO prevent implementations from conforming to the standards specified by both SDOs.

 

To avoid these problems I propose to send the following text to ORAN:

 

“IETF NETMOD working group requests ORAN to avoid using deviations as part of its specification. As documented in  <https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-01%23section-5.8.1> https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-01#section-5.8.1 the usage of deviations would prevent:

*	Vendors to implement their own deviations for the same YANG schema nodes
*	Vendors to claim conformance to both ORAN and 3GPP specifications which are in some cases used as a base for the ORAN YANG models

Note: These problems with deviations exists even if YANG modules are used without using YANG packages.

Regards Balazs

 

-- 

Balazs Lengyel                    Senior Specialist                       Ericsson Hungary Ltd. 

Mobile: +36-70-330-7909              email:  <mailto:Balazs.Lengyel@ericsson.com> Balazs.Lengyel@ericsson.com

 

_______________________________________________
netmod mailing list
 <mailto:netmod@ietf.org> netmod@ietf.org
 <https://www.ietf.org/mailman/listinfo/netmod> https://www.ietf.org/mailman/listinfo/netmod