IETF Logo Mail Archive

Re: [core] Fwd: New Version Notification for draft-ietf-lpwan-coap-static-context-hc-08.txt

Thomas Fossati <tho.ietf@gmail.com> Thu, 30 May 2019 11:52 UTC

Return-Path: <tho.ietf@gmail.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E834C120100; Thu, 30 May 2019 04:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 rP8Y98uzPvhQ; Thu, 30 May 2019 04:52:45 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CCD1120019; Thu, 30 May 2019 04:52:45 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id n5so4779712ioc.7; Thu, 30 May 2019 04:52:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=i9eTVyUSyrgQSPCmuIj3P77o2iCO+rOZZsUvNMASEPA=; b=nwoLVeBncQlMiJYNvQ5qo9M8kupTJ+5GDqt//70Jc3NvPUFxc13JySz94q4esf21Ng 2Zm46sdSmTtPhRQQEIWXpXXZJtEbe4OuaZ++fMqzGbooPT106RuSk2v7M2vVTbkeP3Ho 2+l9AxKUhZEa5BAupKf7ihDbBCt92JT2ZU771/0AvzkZrAt3OAjiKhl44XB/c8xCdJC+ fokV8+pTbQLrdTssoZgmYK846UOKtoJ9dgElWy8kqbgXU1xNtjA8852pn3f3DCtGvQAi EHSJtEREG/PQ102YaJJMAcUqQOg0X43D4ww1oWnkg3oPH7GHiANvaYoH1OhLV3xpkih9 tNvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=i9eTVyUSyrgQSPCmuIj3P77o2iCO+rOZZsUvNMASEPA=; b=HYe1uwvK3uLrLhYWBAWpEEg94KLCBqyNJh81NExyCwCeuQYpusfK1aV3L4KBt9JpkV 0wFdbtsWaXL89pkhRDwiaLcaFnEShG3M5501DikNGnvwfeQRfG4aOUGM4XTN1/AswSEW zpkgNIPTo9H/RwRMZQuRpaKjpL7Waizi2u8he9iKRFRdbEzrP1a15dxLFJ+w3r7AxKSI 6dUnXavXMv5f2deyABaBKZiR9M8qCUl0OZlc2bMY7Wn9aNKPPuqQ+eLLGU3vKxCXiPg0 Fhtq92gG3bQKfP2RCKJUyxKRf5iottsFGyq/b1ZV8usBKVb1KoRKfyFqRacqvz1SCt+4 PPIQ==
X-Gm-Message-State: APjAAAVncw2tRuU5Y9nCg3UF0UR2Rvf08jwCxX1z2iDsGbx3e3GGmXBq oPC+8CJ5j1VqUXT47HRpvubmIrebB+39T2SEzbA=
X-Google-Smtp-Source: APXvYqzmdgbWmv16OkO2S3gJzTRyw61C3Z9e77bL8DykIQxxnsx7ocuYhYHps1dlWjyYT/VTCM1/1eZ4lysabL0+JIE=
X-Received: by 2002:a6b:7d49:: with SMTP id d9mr2546238ioq.50.1559217164511; Thu, 30 May 2019 04:52:44 -0700 (PDT)
MIME-Version: 1.0
References: <155915229337.5461.11045326859886255040.idtracker@ietfa.amsl.com> <CABONVQZoDpTXQeTkszptBGybg6yXYLquLkb5L8sn6aq4wJq_tw@mail.gmail.com>
In-Reply-To: <CABONVQZoDpTXQeTkszptBGybg6yXYLquLkb5L8sn6aq4wJq_tw@mail.gmail.com>
From: Thomas Fossati <tho.ietf@gmail.com>
Date: Thu, 30 May 2019 12:52:33 +0100
Message-ID: <CAObGJnPGK82RHt1rhUkAsrHe4StHkJbRTM0CJ5=tmPM=-_XUyw@mail.gmail.com>
To: Laurent Toutain <laurent.toutain@imt-atlantique.fr>
Cc: lp-wan <lp-wan@ietf.org>, "core@ietf.org WG" <core@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/YD2_p4vh9HsAReyqgTby2xR8_z8>
Subject: Re: [core] Fwd: New Version Notification for draft-ietf-lpwan-coap-static-context-hc-08.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2019 11:52:47 -0000

Hi Laurent,

On Wed, May 29, 2019 at 6:56 PM Laurent Toutain
<laurent.toutain@imt-atlantique.fr> wrote:
> We have issued a new version of the SCHC coap compression
> to remove an artifact due to a bad github manipulation.

I have taken a look at the draft but since I cannot claim compression
expertise I will only provide a couple of high level comments:
- Sec 3: "a proxy placed before the compressor may change some field
value".  You should qualify the "proxy" as a "CoAP proxy, explicitly
selected by the client" to avoid any ambiguity -- we certainly don't
want to recommend middle-box interference :-)
- Sec 4.1: "This field is bidirectional and MUST be elided during the
SCHC compression". This is a dangerous statement as it leads us
straight into CoAP ossification territory.  If you want SCHC to work
with CoAP v1 only what you really want to say here is "SHCH
compression MUST NOT be applied to CoAP packets with version different
from v1".  Granted that, a SCHC box deployed today could sit in the
field happily ever after.  If not, when a new CoAP version is rolled
out, endpoints wouldn’t be able to use this new version on any path
crossing an SCHC box.

Cheers!

v2.23.0 | Report a Bug | By Email