Re: [tsvwg] Ben Campbell's Discuss on draft-ietf-tsvwg-le-phb-09: (with DISCUSS)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 20 February 2019 18:18 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D61D9130E57; Wed, 20 Feb 2019 10:18:57 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 0Nv0CDf_8Sl5; Wed, 20 Feb 2019 10:18:55 -0800 (PST)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 69BB7130E2F; Wed, 20 Feb 2019 10:18:55 -0800 (PST)
Received: by mail-lf1-x12e.google.com with SMTP id g2so18273923lfh.11; Wed, 20 Feb 2019 10:18:55 -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=XtJyJKlwczPvJuyOWFZA82dovxqtgxEH0tonRDWBIn0=; b=KjVcYxUZ/IrspmWcAipuan/or25a+P4NZw91zTZK4a1kf8UdzUHmPljUFy3UVctY1c l7iQcg6C2uaHzoxXH/RzeVdYjZaLua9tzKIYdcmgNljhwfl3lsCaKzIDDPNgkLNN/4zu 0d1sjXjkp+JdvnAwkgnt25TZ2Mc1vKSJTod35+F2AiiPdEIlLRkSdhMUs3G061wHZiHG MFQWoV5VEh5b9F6i6CGI1Ub0VZm1BeSqoj+ajgZzyQ7S/zVNZintQpNh7LWtr1naNRQn p05WDsafmlgpqJ/ZA95Dd4qVi4U2tYTaQt0/TsyAgaWTVWoakmhxv0rX/MD6eOgXLoYU AKHw==
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=XtJyJKlwczPvJuyOWFZA82dovxqtgxEH0tonRDWBIn0=; b=qcsWudP5utzf0OqaL6GtgBT0Cqvb2p/S4vg4jPjsqVBAY7H9/UH6YfVv4KN8skgEOr 0oyf46ZxaoGUlhH0h9e5eOfs3uqMFGeSau0oTLkDMbOH/TL6BGNiTcGbjdqAwrdMFE71 G4opaWxM2lmMm3velzA+6HpK+L1gT+9VII6Xqm2DH6cf92GGENYuYpVqiW3XGvzXcYod +ubPQyuPvvZTN5i8aBzbbhkeyp+DWHafr3SFOis36QZo/s00XV5mTaPqruUdYaD8mXTT 8fSXT3+B/Nv+YNm+7CSZAxQSXEx8SdeZ3QlJPis40nJG4zlWnhrbpShUJkLU85nSA/Qm HbVw==
X-Gm-Message-State: AHQUAuY/AOL2m7DvJ89ujxoqZFaQtrqs7Z3wMcsLh8JyfLNJilLnA6rW AEOl6gFyRDbkFtRftQzHU+uk6CnO5gPCew/GNvc=
X-Google-Smtp-Source: AHgI3IaVL2Q5+KO/Sc9MR8nWWKLgvmAHvNxNdpFQMqveoGUSDlM07sv3HO8hFlau7is5jEwUYWmZupmJ9kqvrZxpjbk=
X-Received: by 2002:ac2:51bc:: with SMTP id f28mr22890708lfk.123.1550686733195; Wed, 20 Feb 2019 10:18:53 -0800 (PST)
MIME-Version: 1.0
References: <155068474129.31466.15846713019514634227.idtracker@ietfa.amsl.com>
In-Reply-To: <155068474129.31466.15846713019514634227.idtracker@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 20 Feb 2019 12:18:42 -0600
Message-ID: <CAKKJt-c9OypSeE30iP=bVvecJfLLHsHH1O2J=oD2wVKqxyjbzQ@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: The IESG <iesg@ietf.org>, tsvwg@ietf.org, "Black, David" <david.black@dell.com>, tsvwg-chairs <tsvwg-chairs@ietf.org>, draft-ietf-tsvwg-le-phb@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e3de3c05825763ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/V6HIro0wFKxfZxLIidEAeeJwBhM>
Subject: Re: [tsvwg] Ben Campbell's Discuss on draft-ietf-tsvwg-le-phb-09: (with DISCUSS)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2019 18:18:58 -0000

Dear TSVWG Chairs,

On Wed, Feb 20, 2019 at 11:45 AM Ben Campbell <ben@nostrum.com> wrote:

> Ben Campbell has entered the following ballot position for
> draft-ietf-tsvwg-le-phb-09: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-le-phb/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Thanks for this effort. The draft appears to be in good shape overall; I
> just
> have one process point I would like to DISCUSS before approval:
>
> Section 12 appears to be an update to draft-ietf-tsvwg-rtcweb-qos, which is
> currently in the RFC Editor queue in the MISSREF state. It's not clear to
> me
> what the intent of this section is, but if the idea is to formally update a
> _draft_, then please do not do that. The right way to proceed would be to
> pull
> draft-ietf-tsvwg-rtcweb-qos from the RFC editor queue and make the changes
> there.
>
> The UPDATES relationship is intended for updating RFCs, which are otherwise
> immutable. Drafts, even post-IESG approval and in the RFC editor queue can
> still be changed. Making readers figure out the update between two
> different
> RFCs when there is an option to just fix the draft would be a disservice to
> readers.
>

That would be fine with me. Is it fine with TSVWG?

All - please note that resolving this question Really Quick would be
awesome, because there is only one more telechat after the one tomorrow,
and as of Wednesday of IETF 104, the ballots for draft-ietf-tsvwg-le-phb
from outgoing ADs "go away", including my Yes ballot ...

Spencer, who is wondering how many of the incoming ADs are familiar with
cluster C238 in the RFC Editor queue ...