IETF Logo Mail Archive

Re: [Ietf-and-github] Tracking drafts

"STARK, BARBARA H" <bs7652@att.com> Fri, 14 February 2020 13:36 UTC

Return-Path: <bs7652@att.com>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6EBD12087D for <ietf-and-github@ietfa.amsl.com>; Fri, 14 Feb 2020 05:36:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 h6RfqeVW_yL4 for <ietf-and-github@ietfa.amsl.com>; Fri, 14 Feb 2020 05:36:27 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 5F298120866 for <ietf-and-github@ietf.org>; Fri, 14 Feb 2020 05:36:27 -0800 (PST)
Received: from pps.filterd (m0049459.ppops.net [127.0.0.1]) by m0049459.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 01EDTUku008755; Fri, 14 Feb 2020 08:36:24 -0500
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049459.ppops.net-00191d01. with ESMTP id 2y59gtx2e3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 14 Feb 2020 08:36:24 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 01EDaMBU023641; Fri, 14 Feb 2020 08:36:23 -0500
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [135.47.91.179]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 01EDaIxl023458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 14 Feb 2020 08:36:18 -0500
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [127.0.0.1]) by zlp30484.vci.att.com (Service) with ESMTP id AE8B54009E6C; Fri, 14 Feb 2020 13:36:18 +0000 (GMT)
Received: from GAALPA1MSGHUBAC.ITServices.sbc.com (unknown [130.8.218.152]) by zlp30484.vci.att.com (Service) with ESMTPS id 992B04009E66; Fri, 14 Feb 2020 13:36:18 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.85]) by GAALPA1MSGHUBAC.ITServices.sbc.com ([130.8.218.152]) with mapi id 14.03.0468.000; Fri, 14 Feb 2020 08:36:18 -0500
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Eric Rescorla'" <ekr@rtfm.com>, "'Martin Thomson'" <mt@lowentropy.net>
CC: "'ietf-and-github@ietf.org'" <ietf-and-github@ietf.org>
Thread-Topic: [Ietf-and-github] Tracking drafts
Thread-Index: AQHV2UcaMfmeyGImVEyYSI4BlSiVIqgHkgkAgAAhjYCAALMfgIAAOQmAgADGSQCAAPhqgIAEa0CAgAaGTgCAAkm4AIAAfCGA///CjyiAAJukAIAA6I0AgACvmgCAAALSAIAABOkAgAEDkID//6z2cA==
Date: Fri, 14 Feb 2020 13:36:17 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6115377B924@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <611506f3-82d4-32e9-5ee2-93e1cd3a6a8a@joelhalpern.com> <0661b222-669f-2904-f7e5-ddbbff5073bd@gmail.com> <c8035f5b-6ff8-594a-2527-fece1955bf35@joelhalpern.com> <3E6E2046-E0C7-46B8-859A-F2B0BC5ADF52@akamai.com> <4ae774ff-0cd5-13e5-6d05-620649a32a17@gmail.com> <da3dcddf-383f-411d-92bb-1f77f64aac4b@www.fastmail.com> <6980b3b7-c287-6b17-f7d0-bbbbc20934da@gmail.com> <CAKKJt-fdk957Zte2ygpvbQgyNh1KpWUJM-fugo2zHd_PA170+g@mail.gmail.com> <08122fcd-771b-4df3-a766-8f7591ef0db0@www.fastmail.com> <CAChr6SykhVyekjfVGH3b+0pXhDtuFBrvDgwStinVCfc2yQ_sCA@mail.gmail.com> <0E1EEFBF-F77B-4202-B54C-CBF9A222C1AD@akamai.com> <7AF2D81C-704A-48C0-A6B2-FF2AE42B6DE2@att.com> <ba7a8858-f961-42ff-a9b1-a8e8686ccdcb@www.fastmail.com> <CAChr6SwBV8xMJKoOqw87k4cQWRLxqk1B_=2hDUrBBPv-H+U9oQ@mail.gmail.com> <CAKKJt-ebEA1LJ91ZF0XUDoe_gsBRqP8xQ54AjGkmJt8jxmFfAA@mail.gmail.com> <ea4aedaf-0edc-478f-a7ed-3f71c28da4d9@www.fastmail.com> <25f9fdae-0bdb-416c-ad61-3824e3af8e06@www.fastmail.com> <CABcZeBPpyvsFg74JPfMuSs5WK_0PR9EM3iJPkgYm2DK6djXAVg@mail.gmail.com>
In-Reply-To: <CABcZeBPpyvsFg74JPfMuSs5WK_0PR9EM3iJPkgYm2DK6djXAVg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.73.239]
Content-Type: multipart/alternative; boundary="_000_2D09D61DDFA73D4C884805CC7865E6115377B924GAALPA1MSGUSRBF_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-02-14_04:2020-02-12, 2020-02-14 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 mlxlogscore=999 impostorscore=0 phishscore=0 mlxscore=0 spamscore=0 lowpriorityscore=0 priorityscore=1501 bulkscore=0 suspectscore=0 adultscore=0 malwarescore=0 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2002140106
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/h3mMp5eXs-1zjUgrm0R5jMBr_h0>
Subject: Re: [Ietf-and-github] Tracking drafts
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2020 13:36:36 -0000

+1
I agree with everything Eric said here.
Barbara

From: Ietf-and-github <ietf-and-github-bounces@ietf.org> On Behalf Of Eric Rescorla

I can understand the motivation for this, but I think it just confuses things as-is.

In general, we've long had a tradition that editors have a lot of discretion in how they prepare documents, with the assumption being that if they make changes without WG consensus, then those changes need to be taken to the WG. And of course the editor could have private conversations about the document, or even public ones outside the WG. So in some respects GH is like that. In any case, I think the Design Team analogy is confusing. I would simply say:

Work done in GitHub -- even when there is extensive discussion -- has no special status. That is, the output of any activity using GitHub needs to be taken into the Working Group
and subject to approval, rejection or modification by the Working Group as with any other input.

Note that I have removed the "mailing list" text as well, because 2418 is actually somewhat vague on exactly how work done offline in drafts is to be brought to the WG. The key point is that this is like any such input.

-Ekr


On Thu, Feb 13, 2020 at 2:03 PM Martin Thomson <mt@lowentropy.net<mailto:mt@lowentropy.net>> wrote:
On Fri, Feb 14, 2020, at 08:45, Martin Thomson wrote:
> +A choice to use GitHub is similar to the formation of a design
> +team (see Section 6.5 of {{!RFC2418}}) provided that the work uses a public
> +repository.  That is, the output of any activity using GitHub needs to be taken
> +to the Working Group mailing list and subject to approval, rejection, or
> +modification by the Working Group as with any other input.

Updated as per Rich and Rob.  Thanks for the prompt review.

v2.8.7 | Report a Bug | By Email