IETF Logo Mail Archive

Re: [lp-wan] authorize position 0

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Sat, 20 July 2019 22:30 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 AACB01201F0 for <lp-wan@ietfa.amsl.com>; Sat, 20 Jul 2019 15:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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=Jg2+iaRW; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=VnIfYdDU
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 4mBkSPmUkCUi for <lp-wan@ietfa.amsl.com>; Sat, 20 Jul 2019 15:30:35 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 597901201E6 for <lp-wan@ietf.org>; Sat, 20 Jul 2019 15:30:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8970; q=dns/txt; s=iport; t=1563661835; x=1564871435; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=sB1o9sJVW/OcJ2yu+bkVGOfJI2ng22qh0KCUPlhcLE8=; b=Jg2+iaRWIvTJ/xTCpCak55hxduiBA1myL7APrX3wel6z1+cw+FW0OYyF o1J9Dx1Q3BEOWPllTIVkA7EgFZYWDmBd61AiErRL+/E6PqINjNbakU9qH nPMt//Z9jChPwsuLH9FAj38Ogg4bKUG8I0J1wNnixNlLj2F4snf0J/JhR s=;
IronPort-PHdr: 9a23:fRl6NRLOJXEZOlV78tmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeBvKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXFXnLOPgYjYmNM9DT1RiuXq8NBsdFQ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BxAAA6lTNd/5hdJa1mHAEBAQQBAQcEAQGBVAYBAQsBgRQvUANtVSAECyqEHYNHA419TIIPknuEVYEugSQDVAkBAQEMAQEtAgEBhEACF4I7IzUIDgEDAQEEAQECAQZthR4MhUoBAQEBAxIRChMBATgPAgEIEQQBASsCAgIwHQgCBAESCBqDAYEdTQMdAQKfPQKBOIhgcYEygnkBAQWEfxiCEwmBNAGLXheBQD+BEUaCTD6ERoMJMoImjAKCdoR+lnEJAoIZi0aIYZgKjTWXUAIEAgQFAg4BAQWBUgE1KoEucBWDJ4JCDBeDTopTcoEpjlwBAQ
X-IronPort-AV: E=Sophos;i="5.64,288,1559520000"; d="scan'208,217";a="603890225"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 20 Jul 2019 22:30:34 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x6KMUYYi017957 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 20 Jul 2019 22:30:34 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 20 Jul 2019 17:30:33 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 20 Jul 2019 17:30:33 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sat, 20 Jul 2019 18:30:32 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WXlsWitFt01EVaGCi/ZC7fTRGRrryjgwTo2ED0FfwU/ezqtqPUdgv203ThPe+WBmAVwWO3t/Uma9wabl/hzNvrB40iym6Aruew1aiuFD6kV57fcjXjBhiwZ5BlPLfeRoza02EiW1k9bGSS+hS1yj35hfZ2nMJMFXnqrsZ92sLJ2f6X+q5epsQAHyLqSaSOvUg7LaL3G+ckQC8dzbYY65CgCSZ4r2fR5BWuT3B7ZlG70Jf/Nwq63r6h5lVLdI9qRle7UX1lrSiGOal6WmfxBbBNsgUZeWqeIIQJ7pMQoZtrJU+LtfSHpaRbGw+fVo0qq2enzTybkFTp/D9kIEuNn9gw==
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=sB1o9sJVW/OcJ2yu+bkVGOfJI2ng22qh0KCUPlhcLE8=; b=LuqbTU4+ilYnQmhppLqxWDhE1bTfTX1/M939R2jCQHsQeI4lRvZxHpTsbqQUFjvy6TVsLV8qfItntimnhWhsgfQIEBcEOkeZkywQPUgjf+p4sezmxIEbnPNNC+Qre0iFXjnJcBBsMdLfJbn4NLmxAslOcZtHN5sjYaFFOGjNhTuk3JQiqYHEwyXxyy5F9/CmDiyIU033LV5u5NpDbOVlGdnPc3HoleLp/MfTpAltx/MprPSMXp6KqtlXhLiNPCcFWdafK03PTRpY5VeGMLdg/48M0QVjv1USE7/khEtuWofaSI8kX/uDoyhPPYYagGhUNt8zN5u6fB/jvcSy/YTWyw==
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=sB1o9sJVW/OcJ2yu+bkVGOfJI2ng22qh0KCUPlhcLE8=; b=VnIfYdDUIrvpX/v+VhSUDgdZENSHgF8NP11hkXRlFUP01Wsc4C4w+2MHdUdoIRn3FeDWJY4fkdvckJU3sovNAlN2sYl3oYHn/kCV25IFlOmrrshldlqn13QYitcotSkBgLeVRtuujitAt3hkG7FNDlX9rTB7MBgNb7WBGjQbC5E=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4128.namprd11.prod.outlook.com (20.179.150.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.16; Sat, 20 Jul 2019 22:30:31 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::1ce9:1582:146c:c50a]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::1ce9:1582:146c:c50a%6]) with mapi id 15.20.2073.012; Sat, 20 Jul 2019 22:30:31 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Laurent Toutain <laurent.toutain@imt-atlantique.fr>, lp-wan <lp-wan@ietf.org>
Thread-Topic: [lp-wan] authorize position 0
Thread-Index: AQHVPzB5Ane4OkDbt0CzllxWTBbetabUFkgA
Date: Sat, 20 Jul 2019 22:30:12 +0000
Deferred-Delivery: Sat, 20 Jul 2019 22:29:13 +0000
Message-ID: <MN2PR11MB356571FBE56DF9E65C0D2459D8CA0@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <CABONVQbffR+CW+HxSvxN_PH-1n-nBaxxVkW7WUkbCx8YBcs4Zw@mail.gmail.com>
In-Reply-To: <CABONVQbffR+CW+HxSvxN_PH-1n-nBaxxVkW7WUkbCx8YBcs4Zw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [2001:420:c0c0:1003::ba]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f6ac898e-e98c-4f02-a232-08d70d61dfeb
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB4128;
x-ms-traffictypediagnostic: MN2PR11MB4128:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB4128D75854DF6B42F1007F0ED8CA0@MN2PR11MB4128.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0104247462
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(396003)(346002)(39860400002)(376002)(189003)(199004)(54896002)(9686003)(86362001)(6436002)(2906002)(55016002)(790700001)(6116002)(6306002)(6246003)(561944003)(81166006)(33656002)(81156014)(68736007)(8936002)(53936002)(14454004)(5660300002)(71200400001)(71190400001)(14444005)(229853002)(6666004)(76176011)(476003)(316002)(11346002)(446003)(66446008)(64756008)(66556008)(66476007)(478600001)(256004)(25786009)(76116006)(66946007)(52536014)(8676002)(486006)(6506007)(53546011)(110136005)(46003)(7696005)(7736002)(186003)(102836004)(74316002)(99286004); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4128; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 7oZZY76nUY3OCiO2iHuOQj9pc2Hpqd3vZC3U3KoZ8RROkFSRXy3oV8JxQ7DrfOWMQYf4k6BEeJYV7lM5uMrV8UkFgny5pGyhJW1ORUYiMeAH8UctpV6tNq+oWIUs3leQoUui6aimPsH/9O4BUknVofLF8Q599GZAC1QkrOUwySDiymLfolhjpYsTOb2wMGCG4uBZ+tlkybpqcZH8syyaptYnlMt27YGv4fq4RRUDfA3QEqLRQEDU2U6tDkYVpfuKzCTCgMvzq+PB3DUnzQTWOxgqSCmAXNTfElEn/1BIok04aJgBcv2c7LKJ6PolnAZCpdpHtpBvtwIx5ND8ifto7uzX45nXDEjOIaBxxq9PPKXTf7qX+iMyBy2rtvxLmRZrJf+IiYvORANu3HZHtvBXDB7XgPvo+4jA2LuFYxHubng=
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB356571FBE56DF9E65C0D2459D8CA0MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f6ac898e-e98c-4f02-a232-08d70d61dfeb
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jul 2019 22:30:31.4525 (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: pthubert@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4128
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.29, xch-aln-019.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/WXktthiOcXu7gzOIZglQpyTX7WE>
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: Sat, 20 Jul 2019 22:30:38 -0000

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> On Behalf Of Laurent Toutain
Sent: samedi 20 juillet 2019 12:21
To: lp-wan <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

v2.23.0 | Report a Bug | By Email