IETF Logo Mail Archive

Re: An IETF repository for working code in our protocols?

"Salz, Rich" <rsalz@akamai.com> Thu, 20 August 2020 18:31 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 705F43A124D for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 11:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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=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 2glN7cPuK4cM for <wgchairs@ietfa.amsl.com>; Thu, 20 Aug 2020 11:31:12 -0700 (PDT)
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 A9C313A1252 for <wgchairs@ietf.org>; Thu, 20 Aug 2020 11:31:12 -0700 (PDT)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id 07KIJPmW022948; Thu, 20 Aug 2020 19:31:11 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=fiNI1QGSwcYlq+57iV0aHifc+y+q1giz3mO0AwXwE2E=; b=e4YwIuK2kbPu193oABiESLcrelF2+nR7eVQ/xtZZ68y/MeOrKMeGRgbSLkZyhCzquJB8 5cfbZJ20MSl1o0NEpSmxn/ys1QQ94WT+H2EDjSwpw3nPu4LZZlZVKAsD0Z4vGC1kez2S TbC0qrSv/Rf8pwKnoysKiIheUjWRLdZnEKb/n8mQiUtVCd+HXLFKxkO5HTiVEo97MXlf RgEqB8jz/KuEJDd7DVeB8t5KBeMA0ARG4NmVdT4Cg+t6zYGrPb5XygEpBxkrUbMp4+j0 Lxt0fjfjL1W8PjpZXDqYBiQzjrrB/uBqksmGvrOxpMwDIxSq/FxKpk7pWvnxiP3l8+Pm wA==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 3304hu2rsf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 20 Aug 2020 19:31:11 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.42/8.16.0.42) with SMTP id 07KIUROf031523; Thu, 20 Aug 2020 14:31:10 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.53]) by prod-mail-ppoint2.akamai.com with ESMTP id 32xb1xuqk7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 20 Aug 2020 14:31:10 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 20 Aug 2020 14:31:10 -0400
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.1497.006; Thu, 20 Aug 2020 14:31:09 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Vijay Gurbani <vijay.gurbani@gmail.com>, Mark Nottingham <mnot@mnot.net>
CC: IETF WG Chairs <wgchairs@ietf.org>
Subject: Re: An IETF repository for working code in our protocols?
Thread-Topic: An IETF repository for working code in our protocols?
Thread-Index: AQHWdjshEJs1gjG/bkCcVmORhaVpJ6lAeXgAgAEcAgD//74zAA==
Date: Thu, 20 Aug 2020 18:31:09 +0000
Message-ID: <7B2534FB-5044-45A3-94E0-F81483E8F743@akamai.com>
References: <CAMMTW_+Di=ZBJFLNPaVK6f3w3Yq-V-qau8G_rfGt96SX_aYAAA@mail.gmail.com> <8193D927-DDA8-4C74-BBD3-1AF6C9AFE98B@mnot.net> <CAMMTW_KVRVaz0tUXLaAQH2V0bY2ws+CZDy=XUKC=Jc3aiAU58w@mail.gmail.com>
In-Reply-To: <CAMMTW_KVRVaz0tUXLaAQH2V0bY2ws+CZDy=XUKC=Jc3aiAU58w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.39.20071300
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.39.29]
Content-Type: multipart/alternative; boundary="_000_7B2534FB504445A394E0F81483E8F743akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-08-20_03:2020-08-19, 2020-08-20 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 mlxscore=0 bulkscore=0 spamscore=0 mlxlogscore=778 adultscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2008200148
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-08-20_03:2020-08-19, 2020-08-20 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 malwarescore=0 spamscore=0 mlxscore=0 phishscore=0 impostorscore=0 lowpriorityscore=0 priorityscore=1501 suspectscore=0 clxscore=1015 mlxlogscore=721 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2008200148
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/HKGRG4ACY5Veu65Pfo-3X2oPPzo>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Aug 2020 18:31:14 -0000

  *   I maintain that the average developer who is implementing an RFC will not, on the average, have the required background to know where in the ietf.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__ietf.org&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=7OS-Ssh5clxZ5_hRwIAmZPGsyCme5AoxJiHn5hU9ysc&s=UCRGl3jyjE8QIb-sDIRsf66T4SAPkjdN5TecABoYqR8&e=> domain it should go to in order to find all of these additions.  They will only know one thing, the RFC.  They will know the errata associated with the RFC because a link to the errata is on the RFC title masthead.  It will be great if there was a link to some starter code for new protocols.

RFC’s can trivially have a non-normative appendix of links.

v2.23.0 | Report a Bug | By Email