Re: [rfc-i] Handling of large code sections ...
Michael StJohns <msj@nthpermutation.com> Wed, 25 May 2022 21:21 UTC
Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D88F1C07AF8C for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 25 May 2022 14:21:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1653513667; bh=Ip4gLvWgB72Bg7qdGVce7ErkjcFaQA5bGGwN6SkkUOE=; h=Date:To:References:From:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=vUBRCY7Uql7VL213kQTCayj3Suf8O5kyLUtyuiwCn2Dki3gHIdNeOJlLtIzf37jna fsjS+evh1RWeFs44z/z1eiuHqI4vjEVu73b9rxow8Qm/geqKjMkycIO3IzRG7cx4r4 F5nHTRgWHN+k8hgJLAQ313ZYBoGH70oyrbOGCpqE=
X-Mailbox-Line: From rfc-interest-bounces@rfc-editor.org Wed May 25 14:21:07 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A586FC07B7BB; Wed, 25 May 2022 14:21:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1653513667; bh=Ip4gLvWgB72Bg7qdGVce7ErkjcFaQA5bGGwN6SkkUOE=; h=Date:To:References:From:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=vUBRCY7Uql7VL213kQTCayj3Suf8O5kyLUtyuiwCn2Dki3gHIdNeOJlLtIzf37jna fsjS+evh1RWeFs44z/z1eiuHqI4vjEVu73b9rxow8Qm/geqKjMkycIO3IzRG7cx4r4 F5nHTRgWHN+k8hgJLAQ313ZYBoGH70oyrbOGCpqE=
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96BA9C07B7BB for <rfc-interest@ietfa.amsl.com>; Wed, 25 May 2022 14:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.754
X-Spam-Level:
X-Spam-Status: No, score=-8.754 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X5D5UnGGpVae for <rfc-interest@ietfa.amsl.com>; Wed, 25 May 2022 14:21:02 -0700 (PDT)
Received: from mail-qv1-xf33.google.com (mail-qv1-xf33.google.com [IPv6:2607:f8b0:4864:20::f33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFCB8C07B7BA for <rfc-interest@rfc-editor.org>; Wed, 25 May 2022 14:21:02 -0700 (PDT)
Received: by mail-qv1-xf33.google.com with SMTP id l1so129653qvh.1 for <rfc-interest@rfc-editor.org>; Wed, 25 May 2022 14:21:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to; bh=EzTcJqwkBad5ckrDjoF83kl+gmnPxHbLxXil38O84qY=; b=W5rcvkgHqnvw87FL6ef04wKxY8DNDxv0SgKYuAZaEf6jHMfRHXM31T9hvVpEbRN6+A 19ekAwPsfKElmYNB/SZ4hblp3Mehb1wbku9yNnmSVHSbaKGKaEcHCvhVyuhYK8wjAKaC v/0nP/RNokD85sfSJd/h56WlwGY1VNZN9Y6+mZxAKCVaPSQs1PX4E5bvAeFqyOtt24tb 4HCVm7aqZZH9jWvc9cdRmSOpIX4cxPPz5HOWbJg6uQA94UOhuQcFhG8FqdGoSWZHca// 6J2LSs5w1Dh+2CqBUDazrF3PWD0B1cBXCADrxgiHeOheJof4wJtudJFVSUFHrW/lw71c xewA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=EzTcJqwkBad5ckrDjoF83kl+gmnPxHbLxXil38O84qY=; b=AihiRdQ3/HQSM1+vS1y/Dr6n7ILfgvLKGsOc2uyNfDBwbOxSpl44TNVW37B/4Jtrd9 Mwu6+CKMj/Q3HKOVp+gwJ6H3UYpSz1UJoWIGXYpTCIUU11AK6aurke+SyTFH8PUf+DIp ucmXztKnJXgAWCaQ1+KwM/YFuAvKC8H+FAMNPxboHdNr0xSIP/UQs7zrdQ//gQE2p0ZF 3mHX8nltopxHqBgmxHtDN2wtCzd5VVPTTjttx72vJdA6eJl+xcZPGQee48w9J9IvisPv a4edtBlUFN8Q17l2UYoTnuz9lzeLDoG9NzIbf79ujDc4aeg7xwBlE2PMYMtB0H/AGKcZ r8Pw==
X-Gm-Message-State: AOAM5332mK5VGdoUj1JyKprztFuMH/c3MvD1PXoal9ecXrsa7y6KnQSp 1gmuIi4Swuu+PB3gdS/CI5YVusuDIQHN/uze
X-Google-Smtp-Source: ABdhPJzDXA2Vms7OSf37o58D0AfJCbviIcXKhxoKNcxa/tbSK3v41XeCb0YkBQGgEhDEfzc9xDOqLg==
X-Received: by 2002:ad4:5bc4:0:b0:45b:13a:f3ef with SMTP id t4-20020ad45bc4000000b0045b013af3efmr27538288qvt.10.1653513660577; Wed, 25 May 2022 14:21:00 -0700 (PDT)
Received: from [192.168.1.23] (pool-108-51-200-187.washdc.fios.verizon.net. [108.51.200.187]) by smtp.gmail.com with ESMTPSA id j17-20020ac84411000000b002f940249151sm2230446qtn.73.2022.05.25.14.20.58 for <rfc-interest@rfc-editor.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 25 May 2022 14:20:59 -0700 (PDT)
Message-ID: <a06629f4-90cc-c96c-7e2b-9ab2f1fbda2b@nthpermutation.com>
Date: Wed, 25 May 2022 17:20:57 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
Content-Language: en-US
To: rfc-interest@rfc-editor.org
References: <MN2PR11MB3757B0F15629CB1B0C270E93B9D69@MN2PR11MB3757.namprd11.prod.outlook.com>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <MN2PR11MB3757B0F15629CB1B0C270E93B9D69@MN2PR11MB3757.namprd11.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/cqHc1dgjKqSTFm8PRKqtha1vBuY>
Subject: Re: [rfc-i] Handling of large code sections ...
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============4552012062018008873=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
On 5/25/2022 5:14 PM, Paul Duffy (paduffy) wrote: > > Folks > > Is it acceptable for a draft to externally reference large sections of > code (say, parked in Github) versus inlining into the draft? The > latter makes for easy access and input into the code’s respective tool > chain, versus messy cut/paste of the former. > > Cheers > > > _______________________________________________ > rfc-interest mailing list > rfc-interest@rfc-editor.org > https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest I would venture to guess that none of the current RFC editor tools would support such a model. And I'm not sure that you really want to force readers (or editors) off in that direction. A reference to the code is fine. A "live" reference, especially one you'd expect the readers to click through seems more than a bit problematic. Later, Mike
_______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Handling of large code sections ... Paul Duffy (paduffy)
- Re: [rfc-i] Handling of large code sections ... Michael StJohns
- Re: [rfc-i] Handling of large code sections ... John Levine
- Re: [rfc-i] Handling of large code sections ... Paul Kyzivat
- Re: [rfc-i] Handling of large code sections ... John R. Levine