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

Bob Briscoe <in@bobbriscoe.net> Fri, 03 January 2020 13:49 UTC

Return-Path: <in@bobbriscoe.net>
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 63456120086 for <tcpm@ietfa.amsl.com>; Fri, 3 Jan 2020 05:49:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_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=bobbriscoe.net
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 Jue3j21DwZoT for <tcpm@ietfa.amsl.com>; Fri, 3 Jan 2020 05:49:01 -0800 (PST)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 333C2120077 for <tcpm@ietf.org>; Fri, 3 Jan 2020 05:49:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=fi5r+5lD1h8FsAESCXEDQ0hEeQoq0li9dvrdCZnp/6w=; b=gyNhzsa3Dw2w+MLkQKyrFQqZW dhCxa06irD+tHxVNmU+fn6pzssyInF5gwMqh7JvLEfKFMkjJkh85/YrxmE4bCc7vQlYX/VoypLyN4 kC+YT8jOOblCIz+4ENyLxW9GVfuNf+4fq+ftuMbeKS8LlWO4wtuShCVZ93ktCrEu8ehnY8N4s/gZB FXn7TSwJgO04AL8cjqqsXKnJdXvFBDIDD9O09hOnxhEHxvXJ++8xQMve8EihrTjji9SJJ2ZX68bdX vJrDY/Dsax1QDmFIeLlZ2dzv9pOFTBqJJvqg1h4V3BJnTYlcg1bSXlwaQhXpRTdrxIyLt6/St+jAj vH5jmMYnw==;
Received: from [31.185.135.151] (port=46940 helo=[192.168.0.5]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <in@bobbriscoe.net>) id 1inNJy-0007Ex-Nb; Fri, 03 Jan 2020 13:48:58 +0000
To: Yoshifumi Nishida <nsd.ietf@gmail.com>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>
References: <CAAK044Qxf+ap=rPhuh8BxzS38woLHNqms_S--Eo348Fd4D+yuQ@mail.gmail.com> <CAAK044ReXkrgds2F+LL-60+PhKzkUziFGqZrjzD+UyvqeHzeaA@mail.gmail.com>
From: Bob Briscoe <in@bobbriscoe.net>
Message-ID: <34288421-58db-78ba-2083-f2418f3bff70@bobbriscoe.net>
Date: Fri, 03 Jan 2020 13:48:58 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CAAK044ReXkrgds2F+LL-60+PhKzkUziFGqZrjzD+UyvqeHzeaA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------B96646D480E38BA27E7109CA"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/rfWSFzplETmmvmehMQ-sQRR3qVc>
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, 03 Jan 2020 13:49:05 -0000

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 
> <mailto: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 list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/