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

Yoshifumi Nishida <nsd.ietf@gmail.com> Fri, 24 January 2020 08:06 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 57BA4120019; Fri, 24 Jan 2020 00:06:40 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 Knac_7BHUuy7; Fri, 24 Jan 2020 00:06:37 -0800 (PST)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (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 0A6B5120041; Fri, 24 Jan 2020 00:06:14 -0800 (PST)
Received: by mail-vs1-xe35.google.com with SMTP id p6so668662vsj.11; Fri, 24 Jan 2020 00:06:14 -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=uwDZS95ncEZ+sE9cBW51jdd1EYIX49fKtWXn1o56ahI=; b=TVq5DTzUggeDzB1F/cqRKP+mf9ISfBURBwpq/uJ3Wt/DqUZ1Q1b2rphyIopRT5t+/8 O6EtQsx4gzJl2g67XYkG7wuFW1+Eer2OKNdKSKtUOx4mbz9Ox8H9DbglTlbATTnJmqPp Wvsloq4OfltdDit91ZWKadhNCvJVevVmUHoHP85hnTUugmLC0zDwsXZKJKqsZIY2lvcy heuboIR7Et1u6o47HdmDEjt9/UM6l3NuFufWtaRamg9Ki6KSpNZedg8bTgLikY1Xgayj 5nw8aT3HFro98BFOiIcnMBu0Fv2h59YEp2fWZHx1j4uR8nZJCLeJ8BRN7mA52R9nQ5W3 5ZTg==
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=uwDZS95ncEZ+sE9cBW51jdd1EYIX49fKtWXn1o56ahI=; b=ZtA+wz89Vt6gn6Ssedq4NZjBOQ4ySmA/IkpSQJ5cAFdK0QDD4oNj/Q90MyKg8uJMBU i/ZZ0hWQk/h1Ul+WPdlERkpxuoz2Dsx9S49foUGp37USyB9CqTyRItsIgUelcOX1gANY 8nblm1TXfVzS1B7g3i+9r1xU/c31+YElr6WhluCqrXy0PwfFKb/VmA0oOYbeuvWPXkQT MyTTS5mCkfVp6EgZC0Jd9Bj07cE0/sSiQPC9xEupetyS9uGcO+io8kXpmeQEcIr4l38o oStAshHnNW1v8D00EGhlxgi19uxXPRuo98Uvmt2Ll73xDWRnYUEItAtbVQmnAeqDuoaL 1rew==
X-Gm-Message-State: APjAAAVr1pGXH6aRgdZkyxyPgYJkftr8VI/ffxVyX4YIEH7EN8JnkziJ 3Zaa8vhyntXweIvxlKwvHDPfp5rjLS8v865syAFuIMyD
X-Google-Smtp-Source: APXvYqxqsXHrTR/wviS1a0z/TT3LTOzpv5JyaLfyt5fytEe2kmiP6vXxIjSVIccZ+THGcXku89Hgd1OlX3x400CX2Tw=
X-Received: by 2002:a67:ec12:: with SMTP id d18mr1373401vso.129.1579853173380; Fri, 24 Jan 2020 00:06:13 -0800 (PST)
MIME-Version: 1.0
References: <CAAK044Qxf+ap=rPhuh8BxzS38woLHNqms_S--Eo348Fd4D+yuQ@mail.gmail.com>
In-Reply-To: <CAAK044Qxf+ap=rPhuh8BxzS38woLHNqms_S--Eo348Fd4D+yuQ@mail.gmail.com>
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Fri, 24 Jan 2020 00:06:02 -0800
Message-ID: <CAAK044Q1++XTfmBY7bGzbDzgfVLCR0qq7JsAogfOrjVPd0ZiUw@mail.gmail.com>
To: "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Cc: tcpm-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000325d71059cde3b7b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/ZnPn-mNb2q1QTE9JhGRi3AZ_bPg>
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: Fri, 24 Jan 2020 08:06:40 -0000

Hi everyone,

Sorry for taking long time. After several discussions among the chairs,
we've concluded the rough consensus of the WG is that this document should
target PS.

As tcpm is a relatively small community, it's sometimes not easy to assess
the consensus in the group.
However, as far as we've checked, most of people don't have issues on
publishing it as a PS doc.

This will mean the updated version of this draft will require further
detailed reviews since the current version was written for an experimental
doc. This might take extra time compared to publishing an EXP draft.
In addition, there are possibilities that other ECN proposals will be
published in the future (and they can be PS as well). This draft should be
carefully reviewed not to prevent such activities.

Thanks,
--
Yoshi on behalf of tcpm co-chairs


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.
>
>
>