IETF Logo Mail Archive

Re: [Ietf-and-github] Tracking drafts

Fred Baker <fredbaker.ietf@gmail.com> Sun, 02 February 2020 19:48 UTC

Return-Path: <fredbaker.ietf@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 314A812004D for <ietf-and-github@ietfa.amsl.com>; Sun, 2 Feb 2020 11:48:35 -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, SPF_HELO_NONE=0.001, 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 RpwRNr0mb2Eq for <ietf-and-github@ietfa.amsl.com>; Sun, 2 Feb 2020 11:48:33 -0800 (PST)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (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 BCCA7120033 for <ietf-and-github@ietf.org>; Sun, 2 Feb 2020 11:48:33 -0800 (PST)
Received: by mail-pj1-x1032.google.com with SMTP id 12so5405773pjb.5 for <ietf-and-github@ietf.org>; Sun, 02 Feb 2020 11:48:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=jcwn0RDOv2CT8ySpaQd8EHfkU6xcmdk4+6Um6pL0r1U=; b=jH7F4kWTrocDn23EF7SdlQgF5fpfXkxosIf2hwjnMTz9j5sBnbt8wVuK2kAwuvDfj2 0lZoP6WSOkuKSrAzqnXZhIGbLuYIZycw0LwJBSB8t/nxGmD2525cfpjmc4/Ap9741dQO x+I5ZIHBHbluUHBMjpgmImyFkgC0hA/hsNTPASOn/4/GoBAUfQ6l6HJpSyqYiQ3HxiNM KT1YaM3mfqZ8xRpulHA9sBvi4WKg7g0hqBWIM6Oc9x+yCsf9sOm5E+vfRpJT5qgGZoHc hSyO4s/yRVCgmh2HaqQ6RqbvF8Jk+AF7E2rV+Nq02aOi14yxwpsr3HnVqnnNIxcCRfZu fxIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=jcwn0RDOv2CT8ySpaQd8EHfkU6xcmdk4+6Um6pL0r1U=; b=YRBnkEB3lw0feBg8Vs9PVWj9XVs9Yy167ICU1vLJoCUfJ4qAbNx92KOSFSvCITsob2 b3l2Qf32i/9jWQ6Y3AXfuat1UrT1N2sb5hcMY8srXjLWmWRkyHnmGFJcNKhB/mSXc0GF ksI7kGyk0GHOK/HOVMHoBN02u5U09ostJQvBT9ZILpdJeHSDqGAIa1XabQxBQ2SuGk3H mEOfMRoCV90T2cTwdPznJjMBROWbnsW1mTdTEl6ju4vs68GWUqsIJh384EkMtHMfzSD2 0FHjUF2dd6ghmrFf+jHrPYrkEJ1Z06ErtYhJuTIT0DSW6XQ2mBWICkXn7RzWw8hwV6fm ewMA==
X-Gm-Message-State: APjAAAWWd/BYSTh8ifaCM+jVHDxYlJpMDg0MrMOAiZxxR2UvdcVDdoXO eJquUpoQWSdx9opr6ZLjVpE=
X-Google-Smtp-Source: APXvYqxUPe9VHZ0dDhrqKovkJ62xPa5SnptJbeYdYJlnKS+JJog7rvjb/u4tkKedMFG2JmTP3sROhw==
X-Received: by 2002:a17:902:b68c:: with SMTP id c12mr19780797pls.160.1580672912889; Sun, 02 Feb 2020 11:48:32 -0800 (PST)
Received: from ?IPv6:2607:fb90:5624:d5cb:d188:4a17:33ec:522? ([2607:fb90:5624:d5cb:d188:4a17:33ec:522]) by smtp.gmail.com with ESMTPSA id q17sm9036868pfg.123.2020.02.02.11.48.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 02 Feb 2020 11:48:32 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <4ae774ff-0cd5-13e5-6d05-620649a32a17@gmail.com>
Date: Sun, 2 Feb 2020 11:48:31 -0800
Cc: "Salz, Rich" <rsalz@akamai.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
Message-Id: <92EABB82-5C7E-4C80-9927-BB608B181199@gmail.com>
References: <4ae774ff-0cd5-13e5-6d05-620649a32a17@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/jB1UXvIPz635AC_Iv9d1qtwuzes>
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:48:35 -0000

>> Do we have written advice on when a design group should put its work up?
> 
> 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. 

I agree, but I think I might say it a little differently. The point isn’t “we’re done”; the point is “we need the comments of the working group, which might be that we’re done”.

So the time to file the draft is when all known viewpoints have been addressed, and the document is in readable form. The draft might contain “TBD” sections, or questions. It is, if you will, a request for comments, and a viewpoint that may evoke dispute or commentary, but is designed to bring the group a step closer to consensus on a problem.

v2.8.7 | Report a Bug | By Email