Re: [lp-wan] augment coupond-ack
Alexander Pelov <a@ackl.io> Mon, 15 November 2021 08:46 UTC
Return-Path: <alexander@ackl.io>
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 6173B3A1085
for <lp-wan@ietfa.amsl.com>; Mon, 15 Nov 2021 00:46:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
HTML_MESSAGE=0.001, 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=ackl-io.20210112.gappssmtp.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 Gjr2We0YFqJO for <lp-wan@ietfa.amsl.com>;
Mon, 15 Nov 2021 00:46:06 -0800 (PST)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com
[IPv6:2607:f8b0:4864:20::135])
(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 1935F3A1084
for <lp-wan@ietf.org>; Mon, 15 Nov 2021 00:46:05 -0800 (PST)
Received: by mail-il1-x135.google.com with SMTP id i9so15729639ilu.8
for <lp-wan@ietf.org>; Mon, 15 Nov 2021 00:46:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=ackl-io.20210112.gappssmtp.com; s=20210112;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=SSQYG9dWkTLGSyUu0chdTmA4LunBi6uoBR0Qod2RpRI=;
b=7uO1AWsEU1RS2DLMJhR+pn7tWT3g4mDOGjuEjUwXookAuAQTo1/j/6sJYjVtstY8PL
yZ8doggXzpVgBKB0ez8owBPznzQ43Mqyvd59IogCJT+9gyE77cZZw92JBhEQ1wAqQgGj
9dzFZFlH9Y3wXII4RJDSfFwcaEzajWGpYqAePPJqxSxfAYeK5W4SGI0lLnh5d3XNLqxj
Alq/El+OsKjgcjKWUkRxyUN5OfAcLzCQuRODYw8Iw/Oyo25Y/q4mwhT2w8POuerJ7O8+
dLTBj0XIxgnVTXxDFd7hFbAsOWchE77HgMcpMf4NHnnzqwqXOZynKFR+uHPmvXIbYsAd
RZgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=SSQYG9dWkTLGSyUu0chdTmA4LunBi6uoBR0Qod2RpRI=;
b=vI+yjGgBglkc4tLiPhxJyyneXtSm2lJmFxtd9gGMZLjZirud9LBsi1K0gYBnIamZLI
xjYa0XGPoMh/gy2yyzC3WmrRIAe9kTK5z0HJfCn/9PsU3JFtx+2OdiOwJ2Q4CVPExCW2
O/8IrxQ+U9g4azPU6srTSxnAITdXRlxGS8U9av63SPWcJFmH4xRxGNdzbc0mmF6xV2H8
npIKregGF91tApZ+fm1DONWeaCzma2eD7IEJt3owzbRiaXstOQA81IIeF0HeXrbXsRtC
MtZRCbnR3MWLVR2fFzAkPiYonbxQgA8/VytzIuoL6o/I1RS14U4tJcupPW1EvZfB7cnX
U0ew==
X-Gm-Message-State: AOAM532tmNDQ0BijiH7/Hs6wvC2glwIXIunY5z7Es7DroPwZTxSkr5bq
SHUjxyUKxViYEuDsgacN5waAZnSmZmVJ4rWId3Y98Q==
X-Google-Smtp-Source: ABdhPJwDJPjGNeKdbwROGcJNKxzo3vRtCj88DM26SuQj2x+sN7bJRNnQLc+RJ74EiAn/Z/yIZ7DUSFnve2WKW44dsN8=
X-Received: by 2002:a05:6e02:19ca:: with SMTP id
r10mr22086018ill.319.1636965963774;
Mon, 15 Nov 2021 00:46:03 -0800 (PST)
MIME-Version: 1.0
References: <CABONVQbemxhkU85NM9iU_KBS+0YpARPcqauGQMoOX8mkeXoY7w@mail.gmail.com>
<CACQW0ErZakm+nfR6HzWAJWtuK0Vs7kaCEWXWURGsUjffP9W52g@mail.gmail.com>
<CABONVQYTUeXa=bYW20QKqTzqMCbmPyph0j+N9u278Tb1Q2BiNA@mail.gmail.com>
<5ADCC7DE-E1D0-466E-8A66-B98AB0330579@cisco.com>
In-Reply-To: <5ADCC7DE-E1D0-466E-8A66-B98AB0330579@cisco.com>
From: Alexander Pelov <a@ackl.io>
Date: Mon, 15 Nov 2021 09:45:53 +0100
Message-ID: <CACQW0EoLRDkG=04Hz-GfxcERcLB5mxcr8zp_nLXG=z2c3czTPQ@mail.gmail.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: Laurent Toutain <laurent.toutain@imt-atlantique.fr>,
lp-wan <lp-wan@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c7cfcc05d0cfd639"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/FM9DgGCPhJIS3E8NBbUbl7Bq1ic>
Subject: Re: [lp-wan] augment coupond-ack
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: Mon, 15 Nov 2021 08:46:11 -0000
Thanks for the clarification, Laurent ! (chair hat off) +1 on Eric's position - option 1) Cheers, Alex Le lun. 15 nov. 2021 à 09:32, Eric Vyncke (evyncke) <evyncke@cisco.com> a écrit : > And without any hat except some familiarity with YANG, I also support the > approach of having the data model pristine and let the YANG augmentation in > the compound-ack I-D > > > > -éric > > > > *From: *lp-wan <lp-wan-bounces@ietf.org> on behalf of Laurent Toutain < > laurent.toutain@imt-atlantique.fr> > *Date: *Monday, 15 November 2021 at 09:30 > *To: *Alexander Pelov <a@ackl.io> > *Cc: *lp-wan <lp-wan@ietf.org> > *Subject: *Re: [lp-wan] augment coupond-ack > > > > yes > > > > On Mon, Nov 15, 2021 at 9:08 AM Alexander Pelov <a@ackl.io> wrote: > > Dear Laurent, > > > > Thanks for getting the ball rolling on this one so quickly after the IETF! > > > > On 1) - when you say "ignore the compound-ack from RFC8724" - there is no > compound-ack in RFC8724. > > Do you mean this to be - keep the Yang Data Model aligned with RFC8724 and > not include compound-ack in it? > > > > (and thus -> define an extension in the SCHC-Compound-Ack draft ?) > > > > Cheers, > > Alex > > > > > > > > On Mon, Nov 15, 2021 at 8:51 AM Laurent Toutain < > laurent.toutain@imt-atlantique.fr> wrote: > > Dear lpwaners, > > > > During the last IETF meeting, it was asked to detach the compound-ack from > the RFC8724 model. I see to ways of doing it. > > > > 1) ignore completely the compound-ack from the RFC8724 data model and > augment this model such as: > > > > augment > "/schc:schc/schc:rule/schc:nature/schc:fragmentation/schc:mode/schc:ack-on-error" > { > > leaf bitmap-format { > > type compound-ack:bitmap-format-type; > > when "derived-from(../schc:fragmentation-mode, > 'schc:fragmentation-mode-ack-on-error')"; > > default "compound-ack:bitmap-RFC8724"; > > description > > "How the bitmaps are included in the Ack message."; > > } > > } > > > > > > Where we create the leaf and a specific identityref for compound-ack. > > > > 2) create the leaf in RFC8724 datamodel but just a default value and just > define the compound ack value in the compound ack model. > > > > Personally, I prefer the first approach, since we cannot guess all the > time what will be extended, but I would like to have your point of view on > the subject. > > > > Laurent > > _______________________________________________ > lp-wan mailing list > lp-wan@ietf.org > https://www.ietf.org/mailman/listinfo/lp-wan > >
- [lp-wan] augment coupond-ack Laurent Toutain
- Re: [lp-wan] augment coupond-ack Alexander Pelov
- Re: [lp-wan] augment coupond-ack Laurent Toutain
- Re: [lp-wan] augment coupond-ack Eric Vyncke (evyncke)
- Re: [lp-wan] augment coupond-ack Alexander Pelov
- Re: [lp-wan] augment coupond-ack Pascal Thubert (pthubert)
- Re: [lp-wan] augment coupond-ack Laurent Toutain