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

"Black, David" <David.Black@dell.com> Wed, 20 February 2019 22:23 UTC

Return-Path: <David.Black@dell.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 7C3E1130E84; Wed, 20 Feb 2019 14:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dell.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 w3-qVhsmdPcQ; Wed, 20 Feb 2019 14:23:39 -0800 (PST)
Received: from esa5.dell-outbound.iphmx.com (esa5.dell-outbound.iphmx.com [68.232.153.95]) (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 7715F129AA0; Wed, 20 Feb 2019 14:23:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1550701408; x=1582237408; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=G3m0zCEKmIQ0r6Utl4zwwHaLbeAwew+ZwnZq1+4e+Fs=; b=TWUZJ3riAOcmQw+vJfF4CpKrsBYmFYCYiWPvHX8UXFNdvL7fOyOgXQof XtQVqNuWHJjoA1kGH3hhq+V9FOrB2oUTZUkSSU0YnVbmjIkXHWOgBB1yl ijXZnRi+XM98ITGAgD65xkaTvZt+ySKRBcNj/szDejRbPPEPaGoAUa8X8 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2EBAADV0W1chyWd50NkGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBDSMkBYEAEYEDJwqDfYgaX40WiS2ObxSBZwsBASMLhD4CF4NeIjQJDQEDAQECAQECAQECEAEBAQoLCQgpIwyCOikBFE1rAQEBAQEBIwJELAEBAQQSEQoyCAsHEAIBCBEEAQELGQQDAgICHxEUCQgCBAENBQgagn4BgQ5MAxUBDqF+PQJtgQGJBwEBAW+BL4QzAg5BgwANghkFjESBWD6BEUaCTIJXRwEBAgEBgSUFAQsHAQcaNIJTMYIEIgKQL4cDFItTMwMEAgKHOodig1WBcIVXhQKGPYMohx+FTYEtiwoCBAIEBQIUgUeBHnFwgzyCNhxtAQKHXIU/QTGNPg8XgQiBHwEB
X-IPAS-Result: A2EBAADV0W1chyWd50NkGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBDSMkBYEAEYEDJwqDfYgaX40WiS2ObxSBZwsBASMLhD4CF4NeIjQJDQEDAQECAQECAQECEAEBAQoLCQgpIwyCOikBFE1rAQEBAQEBIwJELAEBAQQSEQoyCAsHEAIBCBEEAQELGQQDAgICHxEUCQgCBAENBQgagn4BgQ5MAxUBDqF+PQJtgQGJBwEBAW+BL4QzAg5BgwANghkFjESBWD6BEUaCTIJXRwEBAgEBgSUFAQsHAQcaNIJTMYIEIgKQL4cDFItTMwMEAgKHOodig1WBcIVXhQKGPYMohx+FTYEtiwoCBAIEBQIUgUeBHnFwgzyCNhxtAQKHXIU/QTGNPg8XgQiBHwEB
Received: from mx0b-00154901.pphosted.com ([67.231.157.37]) by esa5.dell-outbound.iphmx.com with ESMTP/TLS/AES256-SHA256; 20 Feb 2019 16:20:29 -0600
Received: from pps.filterd (m0089483.ppops.net [127.0.0.1]) by mx0b-00154901.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x1KMDWlF118700; Wed, 20 Feb 2019 17:20:57 -0500
Received: from esa5.dell-outbound2.iphmx.com (esa5.dell-outbound2.iphmx.com [68.232.153.203]) by mx0b-00154901.pphosted.com with ESMTP id 2qscs60x5f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 20 Feb 2019 17:20:56 -0500
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwhop.emc.com ([168.159.213.141]) by esa5.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-SHA256; 21 Feb 2019 04:20:32 +0600
Received: from maildlpprd04.lss.emc.com ([10.253.24.36]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id x1KMKbYX024102 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Feb 2019 17:20:43 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com x1KMKbYX024102
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd04.lss.emc.com (RSA Interceptor); Wed, 20 Feb 2019 17:20:30 -0500
Received: from MXHUB319.corp.emc.com ([10.146.3.97]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id x1KMKUZw024943 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Wed, 20 Feb 2019 17:20:30 -0500
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB319.corp.emc.com ([10.146.3.97]) with mapi id 14.03.0415.000; Wed, 20 Feb 2019 17:20:30 -0500
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Heather Flanagan <rse@rfc-editor.org>
CC: Sandy Ginoza <sginoza@amsl.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, IESG <iesg@ietf.org>, tsvwg-chairs <tsvwg-chairs@ietf.org>
Thread-Topic: [tsvwg] MISSREF*R(1G) document in C238 has been overtaken by draft in IESG Evaluation - what now? :-)
Thread-Index: AQHUyV80GlYWnuka7ESIHCZ+mdTyfaXpjVUAgAAFjoD//64vEA==
Date: Wed, 20 Feb 2019 22:20:28 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493630468CAE@MX307CL04.corp.emc.com>
References: <CAKKJt-eYF+MhUqvOtRaHkhO8=texevfYi9rgcTPjiseasw1xsA@mail.gmail.com> <F21F402F-ED73-4072-A7D5-F3915BBD2FEF@rfc-editor.org> <CAKKJt-fYrSo8KQUyybWqDqKCvWf7hqhguuZTxk8Vz_HAAUuVjQ@mail.gmail.com>
In-Reply-To: <CAKKJt-fYrSo8KQUyybWqDqKCvWf7hqhguuZTxk8Vz_HAAUuVjQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.238.21.131]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D2432779493630468CAEMX307CL04corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-02-20_17:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1902200149
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/7iVbdQuqN9si9ocByq-aCJNOB14>
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:23:42 -0000

One small addition on the relationship between the two drafts …

Thanks, --David

From: tsvwg <tsvwg-bounces@ietf.org> On Behalf Of Spencer Dawkins at IETF
Sent: Wednesday, February 20, 2019 5:09 PM
To: Heather Flanagan
Cc: Sandy Ginoza; tsvwg@ietf.org; IESG; tsvwg-chairs
Subject: Re: [tsvwg] MISSREF*R(1G) document in C238 has been overtaken by draft in IESG Evaluation - what now? :-)


[EXTERNAL EMAIL]
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/ 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