Re: [lp-wan] authorize position 0

<dominique.barthel@orange.com> Sun, 21 July 2019 02:24 UTC

Return-Path: <dominique.barthel@orange.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 13CF71200B2 for <lp-wan@ietfa.amsl.com>; Sat, 20 Jul 2019 19:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 jmzZ7wgCJ1q9 for <lp-wan@ietfa.amsl.com>; Sat, 20 Jul 2019 19:24:20 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 028EF12007C for <lp-wan@ietf.org>; Sat, 20 Jul 2019 19:24:20 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 45rpTZ0Sczz2xnM; Sun, 21 Jul 2019 04:24:18 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.38]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id 45rpTY6dHqz2xCM; Sun, 21 Jul 2019 04:24:17 +0200 (CEST)
Received: from OPEXCAUBM21.corporate.adroot.infra.ftgroup ([fe80::d42b:2e80:86c2:5905]) by OPEXCAUBM5C.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0439.000; Sun, 21 Jul 2019 04:24:17 +0200
From: dominique.barthel@orange.com
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Laurent Toutain <laurent.toutain@imt-atlantique.fr>, lp-wan <lp-wan@ietf.org>
Thread-Topic: [lp-wan] authorize position 0
Thread-Index: AQHVPzBcYNQH5NfsE0iaY0baKYHGw6bT9XsA///+UQA=
Date: Sun, 21 Jul 2019 02:24:17 +0000
Message-ID: <23588_1563675857_5D33CCD1_23588_370_1_D95944D2.637B6%dominique.barthel@orange.com>
References: <CABONVQbffR+CW+HxSvxN_PH-1n-nBaxxVkW7WUkbCx8YBcs4Zw@mail.gmail.com> <MN2PR11MB356571FBE56DF9E65C0D2459D8CA0@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB356571FBE56DF9E65C0D2459D8CA0@MN2PR11MB3565.namprd11.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.3.170325
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_D95944D2637B6dominiquebarthelorangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/GS2BJUuNPL9joPk4baS-LosAm8c>
Subject: Re: [lp-wan] authorize position 0
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: Sun, 21 Jul 2019 02:24:22 -0000

Hello all,

Sure, that's an easy one.
I'll publish a new version on Monday, so that people have the time to review the change by our meeting on Friday.
Thanks

Dominique

De : lp-wan <lp-wan-bounces@ietf.org<mailto:lp-wan-bounces@ietf.org>> on behalf of Pascal Thubert <pthubert@cisco.com<mailto:pthubert@cisco.com>>
Date : Saturday 20 July 2019 18:30
À : Laurent Toutain <laurent.toutain@imt-atlantique.fr<mailto:laurent.toutain@imt-atlantique.fr>>, lp-wan <lp-wan@ietf.org<mailto:lp-wan@ietf.org>>
Objet : Re: [lp-wan] authorize position 0

Looks like a great idea Laurent; we need to retrofit it in SCHC before its published.
Do you think you can do that Dominique?

Pascal

From: lp-wan <lp-wan-bounces@ietf.org<mailto:lp-wan-bounces@ietf.org>> On Behalf Of Laurent Toutain
Sent: samedi 20 juillet 2019 12:21
To: lp-wan <lp-wan@ietf.org<mailto:lp-wan@ietf.org>>
Subject: [lp-wan] authorize position 0

Hi,

I've a  proposal to make for coap compression. We process the same way uri-path and the uri-query and we have a position field in the rule telling where we find the elements. For instance

/foo/bar

will generate on a simplified rule containing the FID, the FP and the TV

URI-PATH 1 foo ...
URI-PATH 2 bar

The position is important to avoid confusion with /bar/foo.

But for the query we may not need this order, for instance, it looks that date=monday&value=max
maybe equivalent to value=max&date=monday

so we may have something like:

URI-QUERY 0 value=
URI-QUERY 0 date=

where a rule will be selected if these 2 elements are present ignoring the order. The decompressed message will follow the order given by the rule.

What do you think of that change? if you find interest, do we make the change on -19 or un the coap draft ?

Laurent



_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.