[lp-wan] authorize position 0
Laurent Toutain <laurent.toutain@imt-atlantique.fr> Sat, 20 July 2019 19:21 UTC
Return-Path: <laurent.toutain@imt-atlantique.fr>
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 C6E9A12001B for <lp-wan@ietfa.amsl.com>; Sat, 20 Jul 2019 12:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=imt-atlantique.fr
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 JrGYcaJj5aJb for <lp-wan@ietfa.amsl.com>; Sat, 20 Jul 2019 12:21:31 -0700 (PDT)
Received: from zproxy130.enst.fr (zproxy130.enst.fr [IPv6:2001:660:330f:2::c2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 953FA12004F for <lp-wan@ietf.org>; Sat, 20 Jul 2019 12:21:31 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by zproxy130.enst.fr (Postfix) with ESMTP id BDBAC1209EF for <lp-wan@ietf.org>; Sat, 20 Jul 2019 21:21:29 +0200 (CEST)
Received: from zproxy130.enst.fr ([IPv6:::1]) by localhost (zproxy130.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id DyUPEoGJX4t2 for <lp-wan@ietf.org>; Sat, 20 Jul 2019 21:21:29 +0200 (CEST)
Received: from localhost (localhost [IPv6:::1]) by zproxy130.enst.fr (Postfix) with ESMTP id 430EF120AAA for <lp-wan@ietf.org>; Sat, 20 Jul 2019 21:21:29 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy130.enst.fr 430EF120AAA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1563650489; bh=HcdAUFFW6+tedomHK90qGGZTTMBPJK4YlHEU0iDyT64=; h=MIME-Version:From:Date:Message-ID:To; b=LL1SVVJUcyTxPkz1tax+sFtus77uTi16/WggBs6vIap7tfD1Z11U9byKE/u3VR0z0 VzfZ6gjaagWgglfVb3RNKSCysivpFqOglIHLgJCUdHHd2N5L1z7xNf46LIRU6YTqhI Y72RfXgQG6Tb+O3U5MCmcpwXrxdFT7wn6zMjgbnA=
X-Virus-Scanned: amavisd-new at zproxy130.enst.fr
Received: from zproxy130.enst.fr ([IPv6:::1]) by localhost (zproxy130.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id MYv1eNLrevP8 for <lp-wan@ietf.org>; Sat, 20 Jul 2019 21:21:29 +0200 (CEST)
Received: from mail-yw1-f51.google.com (mail-yw1-f51.google.com [209.85.161.51]) by zproxy130.enst.fr (Postfix) with ESMTPSA id E8C4E1209EF for <lp-wan@ietf.org>; Sat, 20 Jul 2019 21:21:28 +0200 (CEST)
Received: by mail-yw1-f51.google.com with SMTP id b143so14572999ywb.7 for <lp-wan@ietf.org>; Sat, 20 Jul 2019 12:21:28 -0700 (PDT)
X-Gm-Message-State: APjAAAWXoChVXYwfMdoByoBiUgQfmg8jrgEZ9oX9kyLm/wqzyDGo4+sV St67LFbzyuZfrFvHCgqNNi+AP4Wuk6WWdfVQeiA=
X-Google-Smtp-Source: APXvYqx1F2mI4QwyTF+LQi9TK/WkdpRDFXIoKAmUnNz/x+6ygHHhIEy94ojRLwaze/q2yDsmRdB01vAkqyGMWFUlKQU=
X-Received: by 2002:a81:6588:: with SMTP id z130mr33771389ywb.44.1563650487693; Sat, 20 Jul 2019 12:21:27 -0700 (PDT)
MIME-Version: 1.0
From: Laurent Toutain <laurent.toutain@imt-atlantique.fr>
Date: Sat, 20 Jul 2019 21:20:51 +0200
X-Gmail-Original-Message-ID: <CABONVQbffR+CW+HxSvxN_PH-1n-nBaxxVkW7WUkbCx8YBcs4Zw@mail.gmail.com>
Message-ID: <CABONVQbffR+CW+HxSvxN_PH-1n-nBaxxVkW7WUkbCx8YBcs4Zw@mail.gmail.com>
To: lp-wan <lp-wan@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000df3798058e21bf4d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/GO6p2bIqK2dMbJNetYinp1umHEA>
Subject: [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: Sat, 20 Jul 2019 19:21:34 -0000
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
- [lp-wan] authorize position 0 Laurent Toutain
- Re: [lp-wan] authorize position 0 Pascal Thubert (pthubert)
- Re: [lp-wan] authorize position 0 dominique.barthel