Re: [tsvwg] MISSREF*R(1G) document in C238 has been overtaken by draft in IESG Evaluation - what now? :-)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 20 February 2019 23:46 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 2227B1274D0; Wed, 20 Feb 2019 15:46:01 -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 eesJ1uNq7JjQ; Wed, 20 Feb 2019 15:45:58 -0800 (PST)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 B9CBD12D7EA; Wed, 20 Feb 2019 15:45:57 -0800 (PST)
Received: by mail-lf1-x129.google.com with SMTP id p1so268893lfk.9; Wed, 20 Feb 2019 15:45:57 -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=gKRKkeVsEaxihK4mXZMriXayG7GW+XKlAhenvN3JHD4=; b=Oh7+Hsi7u0QJ2Y6rEAMZhgEUfCSL9awfRwNL/7urN5kUYN9xv74gfURhDp6QUGJSs7 F3EhMjkPE5DwU62K/JwiqC3hFgux0ObI9aNInMEfgjr4+87voLEuaViy9GsSuPomNXJl 9uFe1YYCbZwXQgNYY0O6jFjFEmyqWMqXsTCMebiRnVUVJfVTfCNrfTbYv+fBn5igpO7P gKF7q5iqWzPIHDirfp5hNb95+82WNJTKkO8X3ftOMPK8YsVmgR7tjk2UhF89/pNKV74p kEIoDupA5x8aleEo2Sf89IIPxqZGQN/U+Rvq0ct0Vk6VpbP0iIAkUPsqDzQBbVTQnSKD jYnA==
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=gKRKkeVsEaxihK4mXZMriXayG7GW+XKlAhenvN3JHD4=; b=IofBxfLJ5R42sGmv29pJMlaPYtr3wrRPQl8ItnS04m/z8Cjnuix6ntqg2opT2GqZCN keUUuYKEQ+r/KGEarBK5jWpoHDpq55f9fOGSE0BwbsSSNxjm5AMkMqDkMh+HLdntIJ5F uQcg01qg8Jt9HVluDXDEmdqFwpHjOUs4/uABi8VyxsGu+YuZ5yjHKGVcFb5ByhzMG/mI 3vBYn6sRXB0EgbVMFCWHuZ8U2XWY8u7JIZI92qtRn9uYvhSY7Ti6ise+sjPPej395tbN ELv/ecuPbgPSWh0afyI/SH6wj0ceVvvwU4JjAw5hDRYDKh7z2LuXtd5gegBrkzs1iV7b D7GQ==
X-Gm-Message-State: AHQUAuZMp0Qs0L15tcvwSguXkGXF3ntdM57oSdltrLhkX2782oFYUsbO ClGxqd68mxzFyxOLiiS42HCjRTSq+Z5B1YxJWGWwZE6y
X-Google-Smtp-Source: AHgI3IYr3pTIZYDKgpp3HvyISJPUw7zrljRN3MjrP8xeGsN3IOD4Kq5QpASuMU6lHTVitzKOOSRxQoSLCK6lEKl7msE=
X-Received: by 2002:a19:4851:: with SMTP id v78mr21556230lfa.98.1550706351368; Wed, 20 Feb 2019 15:45:51 -0800 (PST)
MIME-Version: 1.0
References: <CAKKJt-eYF+MhUqvOtRaHkhO8=texevfYi9rgcTPjiseasw1xsA@mail.gmail.com> <F21F402F-ED73-4072-A7D5-F3915BBD2FEF@rfc-editor.org> <CAKKJt-fYrSo8KQUyybWqDqKCvWf7hqhguuZTxk8Vz_HAAUuVjQ@mail.gmail.com> <FC97549B-FD6A-442C-9DFA-9BBA5D8F5F3D@amsl.com>
In-Reply-To: <FC97549B-FD6A-442C-9DFA-9BBA5D8F5F3D@amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 20 Feb 2019 15:45:39 -0800
Message-ID: <CAKKJt-cHcgAfuBWOBRFtp0A1QBdtRfY0WEO0fzMbKD_V1mJvxg@mail.gmail.com>
To: Sandy Ginoza <sginoza@amsl.com>
Cc: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>, IESG <iesg@ietf.org>, tsvwg-chairs <tsvwg-chairs@ietf.org>, tsvwg@ietf.org
Content-Type: multipart/alternative; boundary="00000000000039715f05825bf538"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/1DvXRopAK_pq6-1J0yGkcTe8RrQ>
Subject: Re: [tsvwg] MISSREF*R(1G) document in C238 has been overtaken by draft in IESG Evaluation - what now? :-)
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 23:46:01 -0000

Hi, Sandy,

On Wed, Feb 20, 2019, 14:40 Sandy Ginoza <sginoza@amsl.com wrote:

> Hi all,
>
> In this case, sending email to the RFC Editor or adding an RFC Editor note
> both work for us.  In the note or email for draft-ietf-tsvwg-rtcweb-qos,
> please also include the addition of a normative reference to
> draft-ietf-tsvwg-le-phb that David mentioned.
>
> Is it correct that you want the updates from Section 12
> draft-ietf-tsvwg-le-phb to be included in draft-ietf-tsvwg-rtcweb-qos and
> that Section 12 of draft-ietf-tsvwg-le-phb should be removed from the
> document?  If that’s the case, I think having an additional RFC Editor note
> in draft-ietf-tsvwg-le-phb asking us to remove Section 12 would be helpful.
>
>

That is the case.

I'll include all these details in the RFC Editor Note in
draft-ietf-tsvwg-le-phb.

And thank you for your help!

Spencer

Does this work?
>
> Thanks,
> Sandy
>
>
> On Feb 20, 2019, at 2:09 PM, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
> Hi, Heather,
>
> On Wed, Feb 20, 2019 at 3:49 PM Heather Flanagan <rse@rfc-editor.org>
> wrote:
>
>> Hi Spencer,
>>
>> I know it’s rude to answer a question with a question… but I have a few
>> questions.
>>
>> Draft-ietf-tsvwg-le-phb is not in our queue yet, right? Will it become
>> part of C238 when it is in our queue?
>>
>
> draft-ietf-tsvwg-le-phb is on the telechat agenda for tomorrow.
>
> I believe the only connection with draft-ietf-tsvwg-rtcweb-qos are the
> instructions in Section 12 - so if those instructions are carried out by
> the RFC Editor, draft-ietf-tsvwg-le-phb shouldn't need to be part of C238.
>
> [David>] In addition. draft-ietf-tsvwg-rtcweb-qos will acquire a normative
> reference to draft-ietf-tsvwg-le-phb as a result of these edits.
> Fortunately, that will **not** make draft-ietf-tsvwg-le-phb part of C238.
>
>
>
>
>> When the text in draft-ietf-tsvwg-rtcweb-qos is changed, will that text
>> then be removed from draft-ietf-tsvwg-le-phb?
>>
>
> That would make sense to me.
>
>
>> Will there still be any kind of Updates relationship between
>> draft-ietf-tsvwg-le-phb and draft-ietf-tsvwg-rtcweb-qos when this change is
>> made?
>>
>
> I don't believe so. The theory I'm using is that TSVWG is changing the
> text of a draft that hasn't been issued as an RFC yet (with instructions in
> another draft that will be removed), so no kind of Updates relationship
> would exist - there won't be any text in draft-ietf-tsvwg-le-phb that
> updates draft-ietf-tsvwg-rtcweb-qos.
>
>>
>> If draft-ietf-tsvwg-le-phb is not in our queue and will not be part of
>> C238, then I think an RFC Editor Note would be very useful for that draft.
>> If we haven’t started editing draft-ietf-tsvwg-rtcweb-qos, then an RFC
>> Editor Note there would be useful to. I defer to Sandy, though, as to what
>> the editors will find most useful to make sure this change is captured
>> during the editing process.
>>
>
> Hi, Sandy :-)
>
> I can add the RFC Editor Note to draft-ietf-tsvwg-le-phb. Could you let me
> know if I should also add an RFC Editor note to draft-ietf-tsvwg-rtcweb-qos?
>
> Thanks!
>
> Spencer
>
> Thanks,
>> Heather
>>
>> On Feb 20, 2019, at 12:59 PM, Spencer Dawkins at IETF <
>> spencerdawkins.ietf@gmail.com> wrote:
>>
>> Dear Heather,
>>
>> The IESG has https://datatracker.ietf.org/doc/draft-ietf-tsvwg-le-phb/
>> in IESG Evaluation for this week's telechat, and this draft
>> updates draft-ietf-tsvwg-rtcweb-qos, which I'm sure you recognize because
>> it's in Cluster C238, and has been hanging in the RFC Editor queue for some
>> number of years.
>>
>> We THINK we don't want to have draft-ietf-tsvwg-rtcweb-qos published as
>> an RFC and immediately have another RFC published that updates it - right?
>>
>> We THINK the instructions in
>> https://tools.ietf.org/html/draft-ietf-tsvwg-le-phb-09#section-12
>> describe the changes to draft-ietf-tsvwg-rtcweb-qos clearly.
>>
>> What is the proper way for the IESG to tell the RFC Editor to go ahead
>> and make the changes to draft-ietf-tsvwg-rtcweb-qos?
>>
>> Our guesses include, but are not limited to,
>>
>>    - Adding an RFC Editor Note to draft-ietf-tsvwg-le-phb (the draft
>>    with instructions about updating draft-ietf-tsvwg-rtcweb-qos)
>>    - Adding an RFC Editor Note to draft-ietf-tsvwg-rtcweb-qos (the draft
>>    to be updated)
>>    - Sending an e-mail to the RFC Editor requesting that the text
>>    changes be applied to draft-ietf-tsvwg-rtcweb-qos before it is published
>>
>> but I bet that you know what will make live easiest for you and the RFC
>> editor staff ... please let me know.
>>
>> Thanks,
>>
>> Spencer
>>
>> Spencer
>>
>>
>>
>