Re: [Ietf-and-github] Tracking drafts
Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 02 February 2020 19:30 UTC
Return-Path: <brian.e.carpenter@gmail.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 09C9B1200B1
for <ietf-and-github@ietfa.amsl.com>; Sun, 2 Feb 2020 11:30:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 k9COM-pP8iq1 for <ietf-and-github@ietfa.amsl.com>;
Sun, 2 Feb 2020 11:30:41 -0800 (PST)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com
[IPv6:2607:f8b0:4864:20::42e])
(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 54FF7120033
for <ietf-and-github@ietf.org>; Sun, 2 Feb 2020 11:30:41 -0800 (PST)
Received: by mail-pf1-x42e.google.com with SMTP id q8so6364493pfh.7
for <ietf-and-github@ietf.org>; Sun, 02 Feb 2020 11:30:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-language:content-transfer-encoding;
bh=xKIejd+d7uipT2uiU9Fipm4Bl6frGHJNegtyXvNm4KU=;
b=vW2JwdFt/0BFO1TYQN+HjnjxMfoglmHbDhDecycBxfsDvAfY8rGEhx8pTQvp8TTjYx
crSTHAoc/j73T0C1+6jn1XbxZ6Nlv+vpa3xUdZp2mN58vWwKPrR226H5lJrfLFn+dLj8
CmJ2VUHHybXOkaEbWcT/VpWRLBzW70tRl1R2v2UmJKxnEAweWmsWHRBVT9CDMYFzay3m
dVKTQf+SibGZINto92ARKNQZ7n/nNUcZK/P8ouytwrIyq25E/W97TbK4Dxuf2FYRYKKN
CJiWox0c1px0ge6w1nhYAvDl1AXEDdXfi0Tk9YZVfM194MQdNA+BkH6Tv0cU7iKKyATf
YvoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-language
:content-transfer-encoding;
bh=xKIejd+d7uipT2uiU9Fipm4Bl6frGHJNegtyXvNm4KU=;
b=TnhZU1fcU4QHj4iORW3BoCx1YMi96aey9mFLqglnYUvdC59pmjSwcPKFJmEePMWv6f
ug5O6uX5+ZPTtcUbEhI1Gtab7HrGxQmV4lyzDqIlnP93vqydpHDEiXBeWPdXTiHctavx
WWVf/w1UmAU23j2AmsmRin6UwmYM9FZJvLHOL5WXD5vN5qArRenUsr8QhsOnLsVPTmQh
F09oUwxtO3hyQdacZL7HfbLkomqaHn616psW1vUBGp702c788SuNTn1WYKMoPmP7oCo0
zw/wwHzUcmPcPLH7EMfn9kQkk3nAORJlGaq1Fv28d0uR5pLo9bS8iCzhIAuW+tp90N1s
y2CA==
X-Gm-Message-State: APjAAAWLxRbnQ32my/xplsmjxwg7mxfQEYMQXy6pAXMKOdcEzcKVGcRj
ewKMyN2a1QKqhaBI/Ge3Y8eJQSe7
X-Google-Smtp-Source: APXvYqxRHhQ5d63ABpdgE7G9JqXkajWnQCSanSSZipWef6XA8SEHY7fA186t8FRMgILNHJDog9o58w==
X-Received: by 2002:a63:a1e:: with SMTP id 30mr11962634pgk.238.1580671840553;
Sun, 02 Feb 2020 11:30:40 -0800 (PST)
Received: from [192.168.178.30] (88.161.69.111.dynamic.snap.net.nz.
[111.69.161.88])
by smtp.gmail.com with ESMTPSA id l69sm1837698pgd.1.2020.02.02.11.30.37
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Sun, 02 Feb 2020 11:30:39 -0800 (PST)
To: "Salz, Rich" <rsalz@akamai.com>, "Joel M. Halpern" <jmh@joelhalpern.com>,
"ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <4ae774ff-0cd5-13e5-6d05-620649a32a17@gmail.com>
Date: Mon, 3 Feb 2020 08:30:35 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <3E6E2046-E0C7-46B8-859A-F2B0BC5ADF52@akamai.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/TAWLQBT5L_pssnZ5Z8gkTUH4Sfk>
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: Sun, 02 Feb 2020 19:30:43 -0000
On 03-Feb-20 05:06, Salz, Rich wrote: >> I do not see a note giving this advice in the draft that is currently up > for publication. I hope I am merely missing something. > > Do we have written advice on when a design group should put its work up? Good question. I don't think we do. https://tools.ietf.org/html/rfc2418#section-6.5 just says "The output of a design team is always subject to approval, rejection or modification by the WG as a whole." And indeed, the question of when a design team should expose its output to the WG has always been a bit unclear. Something like "When you have something worth saying to the WG, say it as an I-D" perhaps. > Why do you think this is different, other than being a more open design group? I don't think it is. On the contrary, I think github is an excellent tool for design teams to use; much better than private email. I think that Joel's point applies more generally, not just to github. Regards Brian
- [Ietf-and-github] Tracking drafts Joel M. Halpern
- Re: [Ietf-and-github] Tracking drafts Brian E Carpenter
- Re: [Ietf-and-github] Tracking drafts Joel M. Halpern
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts Joel M. Halpern
- Re: [Ietf-and-github] Tracking drafts Joel M. Halpern
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts Brian E Carpenter
- Re: [Ietf-and-github] Tracking drafts Fred Baker
- Re: [Ietf-and-github] Tracking drafts Joel M. Halpern
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Brian E Carpenter
- Re: [Ietf-and-github] Tracking drafts Spencer Dawkins at IETF
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Brian E Carpenter
- Re: [Ietf-and-github] Tracking drafts Rob Sayre
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts STARK, BARBARA H
- Re: [Ietf-and-github] Tracking drafts Rob Sayre
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Rob Sayre
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts Spencer Dawkins at IETF
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts Rob Sayre
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Eric Rescorla
- Re: [Ietf-and-github] Tracking drafts STARK, BARBARA H
- Re: [Ietf-and-github] Tracking drafts Rob Sayre
- Re: [Ietf-and-github] Tracking drafts Martin Thomson
- Re: [Ietf-and-github] Tracking drafts Salz, Rich
- Re: [Ietf-and-github] Tracking drafts Christopher Wood