Re: [tsvwg] MISSREF*R(1G) document in C238 has been overtaken by draft in IESG Evaluation - what now? :-)
Sandy Ginoza <sginoza@amsl.com> Wed, 20 February 2019 22:40 UTC
Return-Path: <sginoza@amsl.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 79357130E8B; Wed, 20 Feb 2019 14:40:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 lB54BEMcebHe; Wed, 20 Feb 2019 14:40:45 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0F0512D4F0; Wed, 20 Feb 2019 14:40:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id EC9631C5ACB; Wed, 20 Feb 2019 14:40:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IP95I0z-R7LR; Wed, 20 Feb 2019 14:40:32 -0800 (PST)
Received: from [64.170.98.249] (unknown [64.170.98.249]) by c8a.amsl.com (Postfix) with ESMTPSA id B8D611C55DD; Wed, 20 Feb 2019 14:40:32 -0800 (PST)
From: Sandy Ginoza <sginoza@amsl.com>
Message-Id: <FC97549B-FD6A-442C-9DFA-9BBA5D8F5F3D@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EF3D299C-9ED1-436C-90B8-8D7A0EC46738"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 20 Feb 2019 14:40:28 -0800
In-Reply-To: <CAKKJt-fYrSo8KQUyybWqDqKCvWf7hqhguuZTxk8Vz_HAAUuVjQ@mail.gmail.com>
Cc: Heather Flanagan <rse@rfc-editor.org>, IESG <iesg@ietf.org>, tsvwg-chairs <tsvwg-chairs@ietf.org>, tsvwg@ietf.org
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
References: <CAKKJt-eYF+MhUqvOtRaHkhO8=texevfYi9rgcTPjiseasw1xsA@mail.gmail.com> <F21F402F-ED73-4072-A7D5-F3915BBD2FEF@rfc-editor.org> <CAKKJt-fYrSo8KQUyybWqDqKCvWf7hqhguuZTxk8Vz_HAAUuVjQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/HQgsR18vTMIRxt2O30jCJcQy-aM>
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 22:40:48 -0000
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. 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 <mailto: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 <mailto:spencerdawkins.ietf@gmail.com>> wrote: >> >> Dear Heather, >> >> The IESG has https://datatracker.ietf.org/doc/draft-ietf-tsvwg-le-phb/ <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 <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 >
- [tsvwg] MISSREF*R(1G) document in C238 has been o… Spencer Dawkins at IETF
- Re: [tsvwg] MISSREF*R(1G) document in C238 has be… Heather Flanagan
- Re: [tsvwg] MISSREF*R(1G) document in C238 has be… Spencer Dawkins at IETF
- Re: [tsvwg] MISSREF*R(1G) document in C238 has be… Black, David
- Re: [tsvwg] MISSREF*R(1G) document in C238 has be… Sandy Ginoza
- Re: [tsvwg] MISSREF*R(1G) document in C238 has be… Spencer Dawkins at IETF