IETF Logo Mail Archive

Re: [Ietf-and-github] Tracking drafts

"Salz, Rich" <rsalz@akamai.com> Sun, 02 February 2020 16:06 UTC

Return-Path: <rsalz@akamai.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 365BD120125 for <ietf-and-github@ietfa.amsl.com>; Sun, 2 Feb 2020 08:06:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=akamai.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 4CHhm6XNWrub for <ietf-and-github@ietfa.amsl.com>; Sun, 2 Feb 2020 08:06:31 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 BD30712004D for <ietf-and-github@ietf.org>; Sun, 2 Feb 2020 08:06:31 -0800 (PST)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 012G3xNC004021; Sun, 2 Feb 2020 16:06:30 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=qBre+PtfjQvKFFeIpAhIilze/teU9DcDcBg5KmbVxb0=; b=VJfrfnkxgR2VyuwLSeS1Ta6elBUiWd2KXAqklaqtxr4980kTaigdKa6Svsnz1Tuq0mEY rKXgtseuqKucjofr31/WY+CRtc9qoP1FYQDZW/XErTRSxvji56USSjTxOtBf4LPY1Dn1 QWQ4mQriF7iWFeHYH/jHq3a8oKK74kldNxXuUKhY1/SvnYtz7akj49GZiNoWtfphCz5f Y8ha9PobheC/2Ovef0wgXM6f3h5YFUsP3+yCI57l80wJXig1O8a1Sj/RUT96q9x3CD0X XHS8CT3NI6WsbrKaMm0qqTf7B/l9ozMV8DlOLhoDlq+spXwquUS7Dlso74c8ztl+Evty eg==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 2xw7a843xd-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 02 Feb 2020 16:06:30 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 012G2agG018082; Sun, 2 Feb 2020 11:06:29 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint2.akamai.com with ESMTP id 2xw5hyknbj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 02 Feb 2020 11:06:28 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 2 Feb 2020 11:06:27 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([172.27.123.103]) by usma1ex-dag1mb3.msg.corp.akamai.com ([172.27.123.103]) with mapi id 15.00.1473.005; Sun, 2 Feb 2020 11:06:27 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
Thread-Topic: [Ietf-and-github] Tracking drafts
Thread-Index: AQHV2Uc56V4TzOgwFE+xHVK0ygF1RKgHkgkAgAAhjYCAAF9MAA==
Date: Sun, 2 Feb 2020 16:06:27 +0000
Message-ID: <3E6E2046-E0C7-46B8-859A-F2B0BC5ADF52@akamai.com>
References: <611506f3-82d4-32e9-5ee2-93e1cd3a6a8a@joelhalpern.com> <0661b222-669f-2904-f7e5-ddbbff5073bd@gmail.com> <c8035f5b-6ff8-594a-2527-fece1955bf35@joelhalpern.com>
In-Reply-To: <c8035f5b-6ff8-594a-2527-fece1955bf35@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.21.0.200113
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.80.176]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C79107327E569E4D8D32601EBB5523CC@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2020-02-02_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=839 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-2002020129
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-02-02_04:2020-01-31, 2020-02-02 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 priorityscore=1501 phishscore=0 spamscore=0 clxscore=1011 suspectscore=0 adultscore=0 bulkscore=0 impostorscore=0 mlxlogscore=811 malwarescore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1911200001 definitions=main-2002020129
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/CitCHuMweS14h8W9IDhaLnLG_6s>
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 16:06:33 -0000

>    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?

Why do you think this is different, other than being a more open design group?

v2.8.7 | Report a Bug | By Email