Return-Path: X-Original-To: rohc@ietfa.amsl.com Delivered-To: rohc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE10120448 for ; Thu, 4 Apr 2019 00:49:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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 H3_olXAJvMlf for ; Thu, 4 Apr 2019 00:49:08 -0700 (PDT) Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10080.outbound.protection.outlook.com [40.107.1.80]) (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 A5D31120058 for ; Thu, 4 Apr 2019 00:49:07 -0700 (PDT) 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=skn54GT2HnBJnJa53PIx5/vsK54c29CerCyg9nJAKJc=; b=l98bbgNHuYr6irKngFEJOcCDhg/KTeIQ25q3qlU7aWaGcPyizNTCCVg2lAOpwA+KcD6dabElcNWY6IYHatRoojqWJshxCoBt6DyFZYFnErrN1yjlIEDPymisYc3bYCOqUIvv0ONKrY99fkfrh7NTqWI8vuEPveJonNpTVrFPrJM= Received: from HE1PR0701MB2522.eurprd07.prod.outlook.com (10.168.128.149) by HE1PR0701MB2860.eurprd07.prod.outlook.com (10.168.94.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.7; Thu, 4 Apr 2019 07:49:04 +0000 Received: from HE1PR0701MB2522.eurprd07.prod.outlook.com ([fe80::107c:5f27:2ef:8505]) by HE1PR0701MB2522.eurprd07.prod.outlook.com ([fe80::107c:5f27:2ef:8505%5]) with mapi id 15.20.1771.006; Thu, 4 Apr 2019 07:49:04 +0000 From: Magnus Westerlund To: Carsten Bormann CC: "rohc@ietf.org" Thread-Topic: [rohc] Proposed response to LS from 3GPP RAN2 Thread-Index: AQHU5G8KkDGCN6sEwkOs7gxt32K9ug== Date: Thu, 4 Apr 2019 07:49:04 +0000 Message-ID: References: Accept-Language: sv-SE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=magnus.westerlund@ericsson.com; x-originating-ip: [192.176.1.83] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: f38f3062-0f9a-4ec0-de86-08d6b8d20274 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:HE1PR0701MB2860; x-ms-traffictypediagnostic: HE1PR0701MB2860: x-ms-exchange-purlcount: 4 x-microsoft-antispam-prvs: x-forefront-prvs: 0997523C40 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(376002)(366004)(39860400002)(396003)(346002)(51914003)(189003)(199004)(74316002)(7696005)(71200400001)(256004)(66066001)(44832011)(6436002)(14444005)(6116002)(316002)(105586002)(52536014)(6306002)(8676002)(106356001)(7736002)(229853002)(305945005)(97736004)(6916009)(55016002)(478600001)(8936002)(14454004)(5660300002)(2906002)(33656002)(6246003)(9686003)(71190400001)(81166006)(53936002)(99286004)(53546011)(86362001)(446003)(186003)(476003)(966005)(68736007)(3846002)(6506007)(81156014)(25786009)(4326008)(26005)(102836004)(76176011)(486006); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2860; H:HE1PR0701MB2522.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: PeB3ifA6qRFxgA1kIEt9Y/e7mBIF6IHUH95Z4ojXpCdZ93zn551vGiamuy2fpRQZH6rNoK0JyY6+X6Gf5KB5UqDAXdht+bK9p3IenUTuf1rkx2C3Asd5AIFEb1B1DbUYGJ0gvQHEUW9Sixa8CdFX6v7BG1hEsB6TTqe3YIj3D6GLYoo0GdbBD8OO+0XA8Fz3afBSuu1mmq+kcWG1wChixZ6JwzHn/OvBGA9MbJ/xaoL8FYHXWph1VcT/YGErAvuYr2UFc4WfkLn4GadaS+k4N1ZfVWJcmLTcBdj4xIkILSHlZms/09+bSOu6x7km/XMaFqRLPxkReXsXkCmyHvNtVYW69zch0la6E321CNkyjKIFfU7zzfhMHKrgVqSR+w6KpmHKX++xMWqTiWPNDkRf6JQrFjl5Hal/gfg1y+4GXrU= Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: ericsson.com X-MS-Exchange-CrossTenant-Network-Message-Id: f38f3062-0f9a-4ec0-de86-08d6b8d20274 X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2019 07:49:04.1308 (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-Transport-CrossTenantHeadersStamped: HE1PR0701MB2860 Archived-At: Subject: Re: [rohc] Proposed response to LS from 3GPP RAN2 X-BeenThere: rohc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Robust Header Compression List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Apr 2019 07:49:12 -0000 Hi,=0A= =0A= Thanks for the feedback, unfortunately it was too late. The LS was=0A= approved on Friday and have been sent.=0A= https://datatracker.ietf.org/liaison/1638/=0A= =0A= I will work with my informal contacts with the people working on this to=0A= request that they inform me and the ROHC list about progress.=0A= =0A= Cheers=0A= =0A= Magnus=0A= =0A= On 2019-03-30 22:31, Carsten Bormann wrote:=0A= > Sorry for the late response (too much mail backlog from IETF104):=0A= > Maybe it would be worth to also encourage involving the ROHC mailing list= even before a version is sent for registration and expert review (as in = =93avoid late surprises=94).=0A= >=0A= > Thank you for taking care of this.=0A= >=0A= > Gr=FC=DFe, Carsten=0A= >=0A= >=0A= >> On Mar 27, 2019, at 08:31, Magnus Westerlund wrote:=0A= >>=0A= >> Hi, =0A= >> The IESG is targeting to approve the response on Friday sometime after 1= 3:00 CET. Appreciate any comment you may have. =0A= >> Cheers=0A= >>=0A= >> Magnus=0A= >>=0A= >> Title: In Response to 3GPP RAN2=92s LS on RoHC utilization for Ethernet = header compression=0A= >> To: 3GPP RAN2=0A= >> Cc: IEEE 802=0A= >> From: IETF=0A= >> From Contact: Magnus Westerlund=0A= >> Purpose: In Response=0A= >> Reference: R2-1902372=0A= >> =0A= >> Body:=0A= >> Greetings,=0A= >> =0A= >> The IETF appreciate 3GPP RAN2 reaching out to IETF on the topic of robus= t header compression (ROHC). We are happy to answer your questions. See bel= ow for our response to your questions. But let us first provide some backgr= ound information.=0A= >> It has been 9 years since the ROHC WG was closed, IETF currently has no = established community working on ROHC. However, for minor work adding a wor= k item to the TSVWG would be a possibility. The IETF could also consider fo= rming a new WG if there would be good reasons for more substantial work on = header compression. However, for a single ROHC profile there are no necessi= ty for such work in IETF. In case 3GPP would see a need for combining compr= ession of ethernet with several sets of high layer protocols, for example E= thernet/IPv6/UDP and Ethernet/IPv6/TCP etc. there might be wider interest w= hich may motivate doing such work in IETF.=0A= >> The ROHC framework is defined to allow for additional profiles and allow= s registration of ROHC profiles from both IETF and external bodies, such as= 3GPP. The IANA registry for ROHC Profile Identifiers (https://www.iana.org= /assignments/rohc-pro-ids/rohc-pro-ids.xhtml#rohc-pro-ids-1) is operating u= nder the Specification Required policy defined in RFC 8126.=0A= >> =0A= >> Q1: Does IETF or IEEE have any concerns with 3GPP defining new RoHC prof= ile for Ethernet header compression?=0A= >>=0A= >> Answer: IETF has no issues with 3GPP defining a ROHC profile as long it = is registered with IANA.=0A= >>=0A= >> Q3: In case 3GPP is allowed to develop RoHC profile for Ethernet header = compression, does it have to be registered with IANA. If yes, how long can = such process take?=0A= >>=0A= >> Answer: For 3GPP to be assigned a ROHC profile identifier the new profil= e needs to be registered with IANA. This registry operates under a Specific= ation Required policy. A 3GPP technical specification meet the formal requi= rements of this policy and enable registration.=0A= >>=0A= >> There is also an IANA expert review, this review is to verify that the r= egistration is for a ROHC profile with an interoperable description. The IA= NA registration process should be accomplished from submitted request to co= mpletion in a couple of weeks (2-4) given no issues are identified. When th= e expert has approved the registration the IANA will assign the profile an = identifier.=0A= >>=0A= >> Q4: According to IETF, what are the actions needed of 3GPP to specify an= d maintain a ROHC profile?=0A= >>=0A= >> 3GPP defines and documents the ROHC profile in a technical specification= . When the content of the specification is mature and describes a solution = that fits the ROHC framework RFC 5795 and enables interoperable implementat= ion, then 3GPP can submit a registration request to IANA (https://www.iana.= org/protocols/apply) for a ROHC Profile Identifier. If there are any issues= the expert will communicate such issues to the 3GPP contact person request= ing the registration, so they can communicate these to the 3GPP RAN2 WG so = that they can be resolved. When registration has been approved, IANA will a= ssign a profile identifier that can be added to the 3GPP specification. Con= tinued maintenance of the ROHC profile is solely under 3GPP responsibility.= =0A= >> Please note that the registration request can be sent prior to the 3GPP = specification is 100% complete, but the ROHC profile description needs to b= e mature enough for the expert to determine that the profile will result in= interoperable implementations.=0A= >>=0A= >> -- =0A= >>=0A= >> Magnus Westerlund =0A= >>=0A= >> ----------------------------------------------------------------------= =0A= >> Network Architecture & Protocols, Ericsson Research=0A= >> ----------------------------------------------------------------------= =0A= >> Ericsson AB | Phone +46 10 7148287=0A= >> Torshamnsgatan 23 | Mobile +46 73 0949079=0A= >> SE-164 80 Stockholm, Sweden | mailto: =0A= >> magnus.westerlund@ericsson.com=0A= >>=0A= >> ----------------------------------------------------------------------= =0A= >>=0A= >> _______________________________________________=0A= >> Rohc mailing list=0A= >> Rohc@ietf.org=0A= >> https://www.ietf.org/mailman/listinfo/rohc=0A= >=0A= =0A= -- =0A= =0A= Magnus Westerlund =0A= =0A= ----------------------------------------------------------------------=0A= Network Architecture & Protocols, Ericsson Research=0A= ----------------------------------------------------------------------=0A= Ericsson AB | Phone +46 10 7148287=0A= Torshamnsgatan 23 | Mobile +46 73 0949079=0A= SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com=0A= ----------------------------------------------------------------------=0A= =0A=