Re: [lp-wan] FWD: Draft SCHC for CoAP -Title

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 10 June 2021 12:39 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: lp-wan@ietfa.amsl.com
Delivered-To: lp-wan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7C13A11AE for <lp-wan@ietfa.amsl.com>; Thu, 10 Jun 2021 05:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.594
X-Spam-Level:
X-Spam-Status: No, score=-9.594 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=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=CE7igj+E; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Z2BblGBS
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 XnGVJOhZ-wu9 for <lp-wan@ietfa.amsl.com>; Thu, 10 Jun 2021 05:39:40 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C40103A11AA for <lp-wan@ietf.org>; Thu, 10 Jun 2021 05:39:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=63518; q=dns/txt; s=iport; t=1623328779; x=1624538379; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=8BaKGM7uIgLdMITGP8jk5uOGThDLT9ozDWHTQtHxVO0=; b=CE7igj+EotMo8MbpKxEvughURAY9DZkeZBR21b9GVVPhS1ter5pMsyUF 4o9T/P0R/s2DysclojmVrUhmIvIsSDoP3pDThdkadrOUL+Lxx7bmjCNmw 9P5iEZSUDk014rlEYqwPI99oBrdnN8V7/3uKyPkvw7Mt+OBSWJTW5Bm9i Q=;
X-IPAS-Result: A0D7BACFB8Jgl4MNJK1aHgEBCxIMgzowUX5aNzGESINIA4U5iHYDmhiBQoEPAgNUCwEBAQ0BAT8CBAEBhFACF4JRAiU4EwIEAQEBAQMCAwEBAQEFAQEFAQEBAgEGBBQBAQEBAQEBAWiFaA2GRQEBAQQSEQQGEwEBNwEPAgEIEQMBAQEhAQYDAgICMBQJCAIEDgUIGoJPAYF+VwMvAZxSAYE6Aoofen8zgQGCBwEBBgQEhRcYgjEJgTqCe4JxU0gBAYZhJxyBSUSBFUOBYIEAPoJiBIEkPB4WgmE2gi6BfoEPECYEGIEhJpMggwmIDzWeaAqDHJ4PEoNekUqQPLUICIRyAgICAgQFAg4BAQaBayItgS5wFRqDClAXAg6OHxmDV4pecwI2AgYBCQEBAwl8iHYBAQ
IronPort-PHdr: A9a23:lO4RORGlO2XtNKlKz8HU8p1Gfs4Y04WdBeZdwpsil/dHbqCq+YjjJ VHSo/t33xfFXoTevvRDjeee86XtQncJ7pvJtnceOIdNWBkIhYRz/UQgDceJBFe9IKvsaCo3T 8VHSBps43WyN1RUAdvzIVPI8TW+6DcIEUD5Mgx4bu3+Bo/ViZGx0Oa/nv+bYwhBiDenJ71oK xDjpgTKvc5Qioxnec4M
IronPort-HdrOrdr: A9a23:Y6LbMazHN/etT0lBS8/aKrPxkeskLtp133Aq2lEZdPULSK2lfp GV8sjziyWatN9IYgBfpTiBUJPwJk80hqQFkLX5XI3SHDUO3VHJEGgM1/qY/9VvcReOjNK1uZ 0QFpSWTeeAcmSS7vyKozVQcexQveVvmZrA7Yy1ohsdLnAJV0gj1XYENu/xKDwReOAyP+tAKH Pq3Ls/m9PPQwVyUu2LQl0+G8TTrdzCk5zrJTQcAQQ81QWIhTS0rJbnDhmxxH4lInFy6IZn1V KAvx3y562lvf3+4ATbzXXv45Nfn8ak4sdfBfaLltMeJlzX+0OVjcVaKvm/VQIO0aeSAWUR4Y DxStAbTpxOAkbqDyaISN3WqlLdOXgVmiXfIBSj8AveSITCNUEH4ox69N9kmt+z0Tt+gDm6u5 g7g15x/qAnfy/ojWDz4cPFWAptkVfxqX0+kfQLh3gaSocGbqRNxLZvs3+9Pa1wUR4S0rpXXN WGzfusrMp+YBefdTTUr2NvyNujUjA6GQqHWFELvoiQ3yJNlH50wkMEzIhH901wta4VWt1B/a DJI65onLZBQosfar98Hv4IRY+yBnbWSRzBPWqOKRDsFb0BOXjKt5nriY9Fqt1CuKZ4hqfava 6xGW+wmVRCDH4GOPf+l6GjqCq9NFlVdQ6dvP22yaIJz4HBeA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.83,263,1616457600"; d="scan'208,217";a="731790755"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Jun 2021 12:39:38 +0000
Received: from mail.cisco.com (xbe-aln-002.cisco.com [173.36.7.17]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 15ACdcGc025958 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 10 Jun 2021 12:39:38 GMT
Received: from xfe-aln-003.cisco.com (173.37.135.123) by xbe-aln-002.cisco.com (173.36.7.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Thu, 10 Jun 2021 07:39:38 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xfe-aln-003.cisco.com (173.37.135.123) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.792.15; Thu, 10 Jun 2021 07:39:37 -0500
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.18 via Frontend Transport; Thu, 10 Jun 2021 08:39:37 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RbJ3Podapha7bTXQB+fWFsEE39bh7AckbPwrP2a6M6XPzIqwOdMff9Y4v76Jl2B1GETfUU7BufcPUL29qM8WrKTzMUVPulclJY0hssYVj6UkOSxykRHLIA+UqPVWVtflG63TodAFzDTA76EaxZKohrhPlOZLY7Kkr9M2mp9iQKKysUUm6rfRmYXzoaJELDeNVssT9gjrAWOl2B5j39xrleLg74PxwcbsDTQgS1lZV2fIUxd4nHg7j4Lzc4nqnc8mbJLO4NTXR7EWNPmbyBn78a+ryYhk7opNdwY0CfCCjyWdKmY4epK/OlqcsoJvnzT5dwmbTM5XO9/arbx+CZIIyw==
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=8BaKGM7uIgLdMITGP8jk5uOGThDLT9ozDWHTQtHxVO0=; b=C8dydjLX+4VRjJd4c+bBks19gODsibKbCYdZQ1SNArjuI3dx5HQLrcpF52qIEMv/m4owZoWjbMhhoUNYbxKWpQjeKU5sdlIxSPkYx78ikXoIbPR25KkXyTfakAnJSOrj2xwO/Dpdu4ai5uhzAvCEgX5uiwllJeJEThaHRMyOhh8CRsO/yB0CTgNHt8NSZ5PoJVQ4i5rSJygq9drC/NWhfQ41QD0efuzX84kh7EdZ1PeXkXqCR6ZhGaeeaNDgbLmbgZNM52CcRj/mBtmpTAJG+KeOPKckMRQ7RRN4XNiwm2dxmf1RbpMx4TlqGUGrM+CQNIl2iagnttaDO0Mmlh0ufw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8BaKGM7uIgLdMITGP8jk5uOGThDLT9ozDWHTQtHxVO0=; b=Z2BblGBSnB3klw/3ey4LdxV96TgjyI6dfXA7wSBJSHhqU32093oCf+7wXJO3IvQDZtMrxhWgLR0sHG+c9T41vfqYokhtYKifdpQFFi8ArzPIIRjuthxfd1KRCEJOqBP3lQfZey8Yht2Q0wp4OKLJgPCA6JGkEdj06BVUD9tT2MI=
Received: from CO1PR11MB4881.namprd11.prod.outlook.com (2603:10b6:303:91::20) by MWHPR11MB1343.namprd11.prod.outlook.com (2603:10b6:300:20::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4219.23; Thu, 10 Jun 2021 12:39:35 +0000
Received: from CO1PR11MB4881.namprd11.prod.outlook.com ([fe80::54ac:6c31:6cdc:c38e]) by CO1PR11MB4881.namprd11.prod.outlook.com ([fe80::54ac:6c31:6cdc:c38e%5]) with mapi id 15.20.4195.032; Thu, 10 Jun 2021 12:39:35 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Laurent Toutain <laurent.toutain@imt-atlantique.fr>
CC: Ana Minaburo <ana@ackl.io>, "lp-wan@ietf.org" <lp-wan@ietf.org>, "randreasen@fi.uba.ar" <randreasen@fi.uba.ar>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Thread-Topic: [lp-wan] FWD: Draft SCHC for CoAP -Title
Thread-Index: AQHXWFhfTM6HRBrt3EeL6PBlueGnVasCKvIAgAsKXYCAAAHkoA==
Date: Thu, 10 Jun 2021 12:39:33 +0000
Deferred-Delivery: Thu, 10 Jun 2021 12:39:23 +0000
Message-ID: <CO1PR11MB488127CAF34ED3BF1F24B9DFD8359@CO1PR11MB4881.namprd11.prod.outlook.com>
References: <CAAbr+nQJzZ242B9EhzqgaW40VMA=iXhpn743wC1PdQE2kDzZ=Q@mail.gmail.com> <CO1PR11MB4881BC3131F02FB61ECCFB16D83C9@CO1PR11MB4881.namprd11.prod.outlook.com> <CABONVQYk4TH66r4OhvxPjQit2FPLBFZ-9vf_AEUBEL1oOZV+9w@mail.gmail.com>
In-Reply-To: <CABONVQYk4TH66r4OhvxPjQit2FPLBFZ-9vf_AEUBEL1oOZV+9w@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: imt-atlantique.fr; dkim=none (message not signed) header.d=none;imt-atlantique.fr; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2a01:cb1d:4ec:2200:80a:5c4c:b6a4:ff38]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4bc3bf10-0d75-496c-8cdf-08d92c0cce08
x-ms-traffictypediagnostic: MWHPR11MB1343:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <MWHPR11MB13436B06FBD76C4E03175F72D8359@MWHPR11MB1343.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: WfLXKlhsEZf6pBZrpWl9Tyge0VEmWlcnFS3RedNGZ2HzHofQNYtNqcE+FOQD5zqLSoQXu8Uv+xmyf5Qjs3Xr3iRUwUwTdaRtUPMZj5V5wl2s/vnwsmCCD1fFQqBDN9G/0t5T1U0WtJF4K91/HtGCKSNWiZe4rXZfCKOl3EU0Hx1AQPms0p0FZunzo1QDaJ3DN8VCulARm228qmGsuWtIkVrMMtSjv11+MriyKVJ4Y0VptdrzPakTr+xVBHJ+QRwTwk0JVIbCa+E5aSLcKIC5hfUUGY+18zdFNxaaHrMzCMQ+rWoNjnkqtziAnaLM+4gck3FgwbKui9/5q1na98inSSG+zw1PoRQz2XUEjdAYDX2IJu+op5Kk+czlw9ubR7F5KouXXqWK2eUxr4FpyLgH8S781HILaF5DGIaN5XdGzzQwM+HzwBGAx+/scYtCtxRudDlcNd2LwbqXVkrHDWng7Jm0OwyKhEgx1/t3FsCwdoim2wgl3iQBrctCtMAwkX71FRbT4uqZaCZEQadINdACH22DhqOzK8zDXDROyadizN9eZ6lStsvBIZeqvQpFbwIEVdnr6vRAram4IZ1WlFczqtXfBfUQMSjpJCWkMv0Jx5Q=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CO1PR11MB4881.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(136003)(396003)(346002)(39860400002)(376002)(366004)(107886003)(8676002)(4326008)(8936002)(7696005)(478600001)(6916009)(54906003)(66556008)(66946007)(66476007)(64756008)(86362001)(5660300002)(66446008)(316002)(122000001)(52536014)(38100700002)(71200400001)(33656002)(83380400001)(9686003)(53546011)(6506007)(55016002)(186003)(76116006)(2906002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: 46cHT/VSehL7TeHY7ep5kTpJ/vHf302oYiYUuakHrCvtCLGSkGFleoi+TiLuvU/0JgXkzm+i2i5VIP81w0iX2xqh5S/89dpJuFcOuAd9X8MhkL8LgEu08Vo5qjFf95ExW/DAbErrf7hmElpytm4y8guqo4dU/ILlkQq2NlS7MXX8OyxCcBA3saiB/J2o/7Q6KF4WbZTcSmKzbx9BZRfyVT6aq3ZMKfxqt8SJ71g3yIWZIoK7F/VxmeKZ5KuhNEuaQm4un/KD4CuMuH/ZJlZZ4XEk4Gf1F/g6F0o6Jjll0oxo8VOtz1e2DxznnDcrze3dfiIm1LttkWfEAMxTAp3dXLgOUdzjlLTtT1jT5XlEzv0alOyH0hQKjkPMX3Rru+KQtpw1tq+aiUUbMWm5RsE3g/ny6tNjvOZ7iHkU0UhQzMept+cvqCOUWx24ONYHdG6OZb0GsQ56uFYTxqT8vDxcAwrPD6S81RLOiN+Vez24NbNDUU7fcgizMog+k7XLhzgiMSCFbuSMy+vA3rmR+IdQTMQkR5QC8lPY8CDAyA9GpBdplOGs/ik4Sw0jsgoAsYeQ51ZLq6OCKaYs4U9QwPIKoScvCSACVYiwfFXJLkFmtgG7SBjdpfG5hlXBxPEvNH/nhr9nlXFfoueZVx33kMEYO5+HchVBj5hHzXcAKz+YMpQ5/fdThSq2224iS2BZBzvX4kpRqVPEWRNAdkXs7f0jyL+5NgNKkv7MXK45CvGnl0Jjr2fM1tiSl35t8iwvUmEpBrFQDKLwLoYyxE8RmM7z6rfID1tEoQhGkwqncm1bmjQ8kLIs9yGCu6EhEvhNuJr6AYRAv4Usl+WfJdbdAG8mynfyg+EmhRyTHuAFG3m577ix1R3XXQRiSgJXvTWYcUYBKhQk+Fyqv/T5+bhrJ/lXE27RrAVwbESwnkKNTBMqptbrOz9oV8YBUQMwJII66EXH8mhKYl3JY8I3RoIrnlqFH7zJP0frH28myoH4k+FICEbpR8pe6MIfX8lKPFv8XFqygEFjUcqHJK6IDMM5LpwhsjA2j26xb5HYtbI2LkAgkGx9uNzSdK+RF7T3+ZZlRe97+xW4qFD2GXQAa6Ry5EZPhOZQf93IrJsuU0RRIili0hwa1svT5gKPMeQfhg/ep8MpEUaZYqNq1OiPfex9UJa9UcwhmXXe5RGUNzgZaY997Y2ZRsddCjgrB+zM5Y5OAwHLMd+sTdcsU2GiRtuoDrLeWOtFiPYs7J3X7xLkRPCK/xJwH9mjvGfcdmn6lHJsmAU+0U3cyiAUZ8lOEEwrFeB1OOIb2lBb1L4lxQ4CV4xSvmfgkIfJdmNxhYWZnXIenv6t6mNbLDF4qiK82HHyQdECn6odIewwqewKmD6mnVqfkgue4J3QEiaj9W1dAXwFp5YC
Content-Type: multipart/alternative; boundary="_000_CO1PR11MB488127CAF34ED3BF1F24B9DFD8359CO1PR11MB4881namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CO1PR11MB4881.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4bc3bf10-0d75-496c-8cdf-08d92c0cce08
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jun 2021 12:39:35.5541 (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-CrossTenant-userprincipalname: sDCdAxC3WMi6APiGd/rr/nlmMeWJJK9t5d4YT5qi0ssj02tyAbPQqpmnWLlmnTCBvxiR3hPbqdcuwUl3F/II8A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1343
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.17, xbe-aln-002.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/C7HQpAETyZPFSlvJUQsX1TUasdU>
Subject: Re: [lp-wan] FWD: Draft SCHC for CoAP -Title
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Low-Power Wide Area Networking \(LP-WAN\), also known as LPWA or Low-Rate WAN \(LR-WAN\)" <lp-wan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lp-wan/>
List-Post: <mailto:lp-wan@ietf.org>
List-Help: <mailto:lp-wan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jun 2021 12:39:45 -0000

Hello Laurent:

So on the table (with and without acronym expansion) we have

Laurent + Ana: “SCHC for CoAP”
Dominique+Carles+me: “Compression of CoAP using the SCHC framework”

I believe that discussing whether SCHC is a protocol or a framework is already behind us, with the title of RFC 8724 becoming the de-facto definition of what SCHC is.

Q: can the draft be used for fragmentation? If not it does not leverage the whole framework but just the compression. In my book that pleads for Dominique’s proposal.

I’ll have a “Coteau du Layon” if you do not mind, very cold. I can’t seem to  like beer however hard I try.

Take care;

Pascal


From: Laurent Toutain <laurent.toutain@imt-atlantique.fr>
Sent: jeudi 10 juin 2021 14:20
To: Pascal Thubert (pthubert) <pthubert@cisco.com>
Cc: Ana Minaburo <ana@ackl.io>; lp-wan@ietf.org; randreasen@fi.uba.ar; Eric Vyncke (evyncke) <evyncke@cisco.com>
Subject: Re: [lp-wan] FWD: Draft SCHC for CoAP -Title

Hi,

I would not like to reopen a long debate; this is the only step before an RFC and drink some beers.

I understand the RFC8724 got a long and subtile name with framework and fragmentation on it since it reflects the reality. For 8824, it like "SCHC for CoAP" with and without acronym expansion, it's simple and officialize the fact that SCHC become a name and we will not continue to say some long paraphrases.

Laurent



On Thu, Jun 3, 2021 at 1:50 PM Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Hello Ana

I thought we agreed that we’d refer to SCHC as a framework to indicate it  includes compression and fragmentation.
This term framework is really weird. Seems everyone understands it in a different way. .. If someone has the official definition I’m interested!
Also, we now insist that we can compress the L7 if people want to. So why should we insist on “header”? That’s where it started but that’s not where we are now, it is?

Keep safe;

Pascal
From: lp-wan <lp-wan-bounces@ietf.org<mailto:lp-wan-bounces@ietf.org>> On Behalf Of Ana Minaburo
Sent: jeudi 3 juin 2021 11:10
To: lp-wan@ietf.org<mailto:lp-wan@ietf.org>; laurent.toutain@imt-atlantique.fr<mailto:laurent.toutain@imt-atlantique.fr>; randreasen@fi.uba.ar<mailto:randreasen@fi.uba.ar>
Cc: Eric Vyncke (evyncke) <evyncke@cisco.com<mailto:evyncke@cisco.com>>; ana@ackl.io<mailto:ana@ackl.io>
Subject: [lp-wan] FWD: Draft SCHC for CoAP -Title

Dear Dominique, Carles, and Pascal, and all,

I take this discussion out from the RFC-Editor Subject, if not I will be lost again.

We agree to eliminate the term LPWAN from the title during the interim meeting, and I've answered the RFC-Editor with this option that I like:
Full-extended:
"Static Context Header Compression and Fragmentation (SCHC) for Constrained Application Protocol (CoAP)"
Full-abbreviated:
"SCHC for CoAP"

I'm afraid I have to disagree with Dominique's proposition in two things. First, starting with Compression, the title is ambiguous because it can be interpreted as data compression and no header compression. Second, I'm not sure SCHC is a framework, or neither it becomes one.

Dominique proposition: "Compression of the Constrained Application Protocol (CoAP) using the Static Context Header Compression and fragmentation (SCHC) framework"

Cheers,
Ana

---

>From: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>
>Date: Wed, Jun 2, 2021 at 11:14 AM
>Subject: RE: [AD] Re: AUTH48 [LB]: RFC 8824 <draft-ietf-lpwan-coap-static->context-hc-19.txt> NOW AVAILABLE
>To: dominique.barthel@orange.com<mailto:dominique.barthel@orange.com> <dominique.barthel@orange.com<mailto:dominique.barthel@orange.com>>, >ana@ackl.io<mailto:ana@ackl.io> <ana@ackl.io<mailto:ana@ackl.io>>, Eric Vyncke (evyncke) <evyncke@cisco.com<mailto:evyncke@cisco.com>>
>Cc: lp-wan@ietf.org<mailto:lp-wan@ietf.org> <lp-wan@ietf.org<mailto:lp-wan@ietf.org>>, laurent.toutain@imt-atlantique.fr<mailto:laurent.toutain@imt-atlantique.fr>
><laurent.toutain@imt-atlantique.fr<mailto:laurent.toutain@imt-atlantique.fr>>, randreasen@fi.uba.ar<mailto:randreasen@fi.uba.ar>
><randreasen@fi.uba.ar<mailto:randreasen@fi.uba.ar>>
>
>
>Perfect!
>
>>From: Carles Gomez Montenegro <carlesgo@entel.upc.edu<mailto:carlesgo@entel.upc.edu>>
>>Date: Wed, Jun 2, 2021 at 11:02 AM
>>Subject: Re: [lp-wan] [AD] Re: AUTH48 [LB]: RFC 8824 <draft-ietf-lpwan-
>>coap-static-context-hc-19.txt> NOW AVAILABLE
>>To: <dominique.barthel@orange.com<mailto:dominique.barthel@orange.com>>
>>Cc: Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org<mailto:40cisco.com@dmarc.ietf.org>>, >>ana@ackl.io<mailto:ana@ackl.io> <ana@ackl.io<mailto:ana@ackl.io>>, Eric Vyncke (evyncke) <evyncke@cisco.com<mailto:evyncke@cisco.com>>, >>lp-wan@ietf.org<mailto:lp-wan@ietf.org> <lp-wan@ietf.org<mailto:lp-wan@ietf.org>>, laurent.toutain@imt-atlantique.fr<mailto:laurent.toutain@imt-atlantique.fr>
>><laurent.toutain@imt-atlantique.fr<mailto:laurent.toutain@imt-atlantique.fr>>, randreasen@fi.uba.ar<mailto:randreasen@fi.uba.ar>
>><randreasen@fi.uba.ar<mailto:randreasen@fi.uba.ar>>
>>
>>
>>Hello Dominique, (all,)
>>
>>I support your proposal below!
>>
>>In my opinion, it addresses nicely the comment being considered.
>>
>>Cheers,
>>
>>Carles
>>
>>
>>
>>
>>
>>
>>>From: <dominique.barthel@orange.com<mailto:dominique.barthel@orange.com>>
>>>Date: Tue, Jun 1, 2021 at 5:14 PM
>>>Subject: RE: [AD] Re: AUTH48 [LB]: RFC 8824 <draft-ietf-lpwan-coap->>>static-context-hc-19.txt> NOW AVAILABLE
>>>To: Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org<mailto:40cisco.com@dmarc.ietf.org>>, >>>ana@ackl.io<mailto:ana@ackl.io> <ana@ackl.io<mailto:ana@ackl.io>>, Eric Vyncke (evyncke) <evyncke@cisco.com<mailto:evyncke@cisco.com>>
>>>Cc: lp-wan@ietf.org<mailto:lp-wan@ietf.org> <lp-wan@ietf.org<mailto:lp-wan@ietf.org>>, laurent.toutain@imt-atlantique.fr<mailto:laurent.toutain@imt-atlantique.fr>
>>><laurent.toutain@imt-atlantique.fr<mailto:laurent.toutain@imt-atlantique.fr>>, randreasen@fi.uba.ar<mailto:randreasen@fi.uba.ar>
>>><randreasen@fi.uba.ar<mailto:randreasen@fi.uba.ar>>
>>>
>>>
>>>Hello authors, all,
>>>
>>>Following our interim meeting today, here is my contribution to
>>>comment 3 by RFC Ed
>>>> 3) <!-- [rfced] Abstract and subsequent:  "SCHC compression",
>>>>where
>>>> used generally as a noun, looks odd.  We suggest rephrasing where
>>>>appropriate.
>>>>
> >>>We see that RFC 8724 defines "SCHC" as "Static Context Header
>>>> Compression and fragmentation".  Because this document defines
>>>>"SCHC"
>>>>as "Static Context Header Compression", "SCHC compression"
>>>>would then
>>>> read as "Static Context Header Compression compression".
>>>>
>>>> Should we expand "SCHC" as "Static Context Header
>>>>Compression and
>>>> fragmentation" per RFC 8724, instead of using the current "Static
>>>> Context Header Compression"?  That would solve the "Static
>>>>Context Header Compression compression" situation. -->
>>>
>>>This document should not redefine SCHC.
>>>Hence, I propose the following
>>>- Full title
>>>"Compression of the Constrained Application Protocol (CoAP) using >>>the Static Context Header Compression and fragmentation (SCHC) >>>framework"
>>>- Abstract
>>>"This draft defines how to compress the Constrained Application >>>Protocol (CoAP) using the Static Context Header Compression and >>>fragmentation (SCHC) framework. SCHC defines a header >>>compression mechanism tailored for Constrained Devices."
 >>>- Introduction, 2nd paragraph
>>>"[RFC8724] defines the SCHC famework, which includes a header >>>compression mechanism for the LPWAN network, based on a static >>>context."
>>>
>>>With the above changes, which are consistent with RFC8724 and are >>>inline with the RFC Editors suggestion, "SCHC compression" no >>>longer looks odd, and the 25 instances can remain unchanged.
>>>
>>>Best regards
>>>
>>>Dominique
>>>