Re: [tcpm] intended status of draft-ietf-tcpm-accurate-ecn

Yoshifumi Nishida <nsd.ietf@gmail.com> Sat, 04 January 2020 10:03 UTC

Return-Path: <nsd.ietf@gmail.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5618712081B for <tcpm@ietfa.amsl.com>; Sat, 4 Jan 2020 02:03:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=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 AtKFhwgwSU1r for <tcpm@ietfa.amsl.com>; Sat, 4 Jan 2020 02:03:06 -0800 (PST)
Received: from mail-vk1-xa29.google.com (mail-vk1-xa29.google.com [IPv6:2607:f8b0:4864:20::a29]) (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 9D180120860 for <tcpm@ietf.org>; Sat, 4 Jan 2020 02:03:06 -0800 (PST)
Received: by mail-vk1-xa29.google.com with SMTP id y184so11330559vkc.11 for <tcpm@ietf.org>; Sat, 04 Jan 2020 02:03:06 -0800 (PST)
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; bh=Nr6l3xpsKiMZZrsDNbtR7Iuf6to4kmxg34AAhMlD+A8=; b=DDhwfSNrl2fgHQe6v+d6VGsn1B8RVaz9Z0HqGbIaKTX7h3mBZGkbV8yz6oc5vHmK1s U/O4i5ZhNTVq2IBSy3jVklHBnO8b3ebH9YKjbL4IYYw8P3IaivYsBYe86+DfmY2Qdu1I PKJ6kmhGFI94439g7pDMy75dkyZozY6gOq8YGTBgRX3J4phI4yWvVNRiEuUJk97RIjAC cYPywDZIIcnrcw5ayymG94Ut9kuhUv7zA4mt0wMNh2Acjf+TVCN01N+JdN37s8KWTIK8 fgbb/4XM9ASf5ZT/asB8MrdFBsY4SNfljLi02v3+2wADzqN2FWudH1oeVPvKEwoo+YJ+ NcQA==
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; bh=Nr6l3xpsKiMZZrsDNbtR7Iuf6to4kmxg34AAhMlD+A8=; b=rW/Cy1LOC/IkR6VlSRqIrbFtkQLaaL5zCqwOIXAQVGTyJqouP8gN4mro5BTdI8tH2w 8oVX+RcWQ3Pd/z0MLHpo8w6IB0dYyaL1D/o2d/vMIcmTRX56mcmsCc7tE6FsPIL5b2HJ +NjwgzUPgQYC0na76vd5H/YRYkN4w+PinA+M9yKtUY2ViYv1GeOhmJNtQw339VLIMUUv qIGLz6FC+bE3uO7HPxsUmsifyM67MdIjBQ6J4Sam6z37VAvA/SRRVB7kTR1cLfCSaWvT 76aJSB711Ob5qLM6Fy6TChoaoa9gpZ7RihY5LiD/HuNOAjs6ZUtdY88w/Yk9g4R6MlU+ OIcw==
X-Gm-Message-State: APjAAAUCOmTEJBvGKz5TULdPFmw4EtLgrBCoQ5ItqShSubnuKjgUY21p HJaUfKXB0BqlHHbT4SiMAPtLCas5B4r1zGh1u+2m2w==
X-Google-Smtp-Source: APXvYqw6TnD43BgBqUCRDX1vIyYrI75vwNFkiKR+kcPtjbxQmvdcS/twxLvkeh35SC4XDqBnR9+WH9MjKSFcBJBWs6Y=
X-Received: by 2002:a1f:ea04:: with SMTP id i4mr48418784vkh.94.1578132185737; Sat, 04 Jan 2020 02:03:05 -0800 (PST)
MIME-Version: 1.0
References: <CAAK044Qxf+ap=rPhuh8BxzS38woLHNqms_S--Eo348Fd4D+yuQ@mail.gmail.com> <CAAK044ReXkrgds2F+LL-60+PhKzkUziFGqZrjzD+UyvqeHzeaA@mail.gmail.com> <34288421-58db-78ba-2083-f2418f3bff70@bobbriscoe.net>
In-Reply-To: <34288421-58db-78ba-2083-f2418f3bff70@bobbriscoe.net>
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Sat, 04 Jan 2020 02:02:54 -0800
Message-ID: <CAAK044Q6113hRz6=fduN2q-XEUzFDqcH6zheLYLZytfiS1SGUw@mail.gmail.com>
To: Bob Briscoe <in@bobbriscoe.net>
Cc: "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000056ecc3059b4d8812"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/KNTTfYee9p8g1d5H5JdwoSkaDo8>
Subject: Re: [tcpm] intended status of draft-ietf-tcpm-accurate-ecn
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2020 10:03:12 -0000

Hi Bob,

My intention was the later. For the folks who were not in the room at
Singapore meeting.
But, of course, people who were there can also express their opinions if
they want as it can stimulate other folks to speak up.

Thanks,
--
Yoshi

On Fri, Jan 3, 2020 at 5:48 AM Bob Briscoe <in@bobbriscoe.net> wrote:

> Yoshi,
>
> Are you expecting everyone who stuck their hand up at IETF-106 in
> Singapore to repeat their opinion? Or is the ML call primarily meant to
> look for people with opinions who were not present? So far, the only
> opinions on the ML have repeated those in the f2f mtg, for which the
> minutes said:
>
> Yoshi: PS: 8, EXP: 2, don't care: 8
>
> In context, "don't care" meant "either" (not "don't care about the draft").
>
> To repeat my opinion given verbally:
>
>    - I'm happy  with either PS or EXP.
>    - On balance, PS, 'cos when making a change to the TCP wire protocol
>    putting EXP or PS in an RFC header doesn't make any difference to whether
>    the change can be reversed. So, it's better to be clear how serious we have
>    to be about getting it right.
>    - Making it PS would make the header flags process faster, and add
>    weight to the internal corporate cases need to allocate time for
>    implementing this (and implementing supporting stuff like offload)
>    - but both those are less important than getting it right.
>
>
>
> Bob
>
> On 03/01/2020 09:17, Yoshifumi Nishida wrote:
>
> Hello,
>
> This might be because some folks are on winter break, but it seems that we
> don't have much feedback on this.
> I am thinking about this a bit and start wondering if this may mean our
> general feelings are "either status is fine" or there are some other
> reasons.
> If this is the case, I am thinking exp status might be suitable as PS
> generally requires explicit supports (such as the case for TCP RACK)
> If you could provide any opinions or comments, we will appreciate very
> much!
>
> Thanks,
> --
> Yoshi
>
> On Fri, Dec 13, 2019 at 1:17 AM Yoshifumi Nishida <nsd.ietf@gmail.com>
> wrote:
>
>> Hi folks,
>>
>> We would like to get feedback for the intended status
>> of draft-ietf-tcpm-accurate-ecn.
>> The current intended status of this draft is experimental, but we've seen
>> some voices that PS is more preferable for the draft during Singapore
>> meeting and on the ML. So, we would like to check the consensus on it.
>>
>> There are some on-going related discussions such as flag registration
>> policy, SCE, ECN++, etc, however, we believe the intended status
>> discussions is independent from them and can proceed it separately. (If you
>> have concerns on it, please share your opinion here)
>>
>> We appreciate your feedback.
>>
>> Thanks,
>> --
>> Yoshi on behalf of tcpm co-chairs.
>>
>>
>>
> _______________________________________________
> tcpm mailing listtcpm@ietf.orghttps://www.ietf.org/mailman/listinfo/tcpm
>
>
> --
> ________________________________________________________________
> Bob Briscoe                               http://bobbriscoe.net/
>
>