From nobody Tue Sep 14 05:38:44 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9218F3A19BE for ; Tue, 14 Sep 2021 05:38:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 H2apiI_3Et6M for ; Tue, 14 Sep 2021 05:38:38 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 93FB43A19BC for ; Tue, 14 Sep 2021 05:38:38 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id ED33E6250B for ; Tue, 14 Sep 2021 08:37:35 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id qUJa6iAijZYt for ; Tue, 14 Sep 2021 08:37:29 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id D25DD62434 for ; Tue, 14 Sep 2021 08:37:26 -0400 (EDT) To: "xml2rfc@ietf.org" From: Robert Moskowitz Message-ID: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> Date: Tue, 14 Sep 2021 08:38:18 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 12:38:42 -0000 I have a script on github, https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/master/hhit-gen.py That I want to reference in a draft.  I don't want to include the script, too big and it will grow still. Is there any common practice for such an informative reference? thanks From nobody Tue Sep 14 05:41:43 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDA13A19E4 for ; Tue, 14 Sep 2021 05:41:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 (1024-bit key) header.d=gmx.net 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 l56nYLAWBw1r for ; Tue, 14 Sep 2021 05:41:37 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 7ADD03A19E1 for ; Tue, 14 Sep 2021 05:41:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1631623292; bh=EVftj8HFxALLdVy98pHdhg7ToGIEfmVQImcJ0yOnjWg=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=X2G7LTTHebGzvF4qVry/mm58nFMT5FHBl/KZVEGRr/YGs1R1nPAqybrxfa7P1LKhq DAUKAcOjiJb66ExKqB2d+3r75H1l1g30nxj8BvKLQjRsPjT8AmpGwkVbPXho8Hzoz3 hmlI2eqFBmdTdfwv3wtyDleuLvMNo7uEirpwbsU0= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.1.220] ([217.91.35.233]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MFbW0-1mhBha331C-00H9N8 for ; Tue, 14 Sep 2021 14:41:32 +0200 To: xml2rfc@ietf.org References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> From: Julian Reschke Message-ID: <36a74861-0dac-b9bf-8c95-ff1ec83da14c@gmx.de> Date: Tue, 14 Sep 2021 14:41:31 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:MEo7gYowbZ22NTqfG0bjraJTv7CVUFKJWzw6Eqs7+5bToDDFGBr 9PiTtFZFwIhfb/DIR3klcEVYKccXZa8qEW2OBYNhbVhVj1/0/zVkZGSFGuzkGFsRkOj3KAn VFCtgFsyqW2HM+DyBf4ko/0Jh1arngD+Eki+A6e1z1wviEwMFLynZLMvkSuNlvC4C9V81a3 15LGcwxIbQV0s4rYIeydg== X-UI-Out-Filterresults: notjunk:1;V03:K0:+fPByQiZIX0=:HbNd6061QVni7ejKL4ds5s 85seAtnip9voQtfQS5yGyi/DOcEOJJr+m0/gEZyJZ4tkMyM4xRcaN/brveW/Skephmq+qQS6Z YCroBd5aCBtxJE9zOwZhT5ZYqNK3FRtHDhQPgjjueD+X6eKGOhsLPIEvCLA1ckZ1V48hUTDwY 3hqFYTZOAfUgcog1kSGwrzgIv/z3kmvQ8wUZNW1XrqIPj045XEJY5VVIsrut0UBfvOSGNC621 N+Oz3g5cZ8BfVGlzXmMsrA/8HiPz2MBj4v8xRs2GQbX0Rk9v/Ah2W64+AKW4uP9LqF23dwjtI xZdaVHNnhyhntBXUmXSJsxxoMrkwS7y4yWJzNTzdRwP8WhRnc71kGMu9iiUKY4poRSgOAW0dv qWXe95Vp7HZXybIvXMPSnuDsJyquue8VOqo0oIIva6gRED9wvJn7gusm8c6O1JP9yfDX93l9Q H0vW0m5pWTR8EFUX4Jc61LvNvl31Vt/oB7uR+EjM1tacoHJbl1F3foWoKveBeYPm7iUt6kC6E RN5aqG24RS18klHgTl3HQM0bnqyVgiUHbuumTbzLpuBcfMHq6VrrQS1OxUAbWtNw0eRqXg4eD CUhs7GEiqQkfN9N5JDBmSvfi9MBsrb649X+0HEDhAegtct8rx/AObNlS0ScbFXYSZL2F0cb6W 7u2Fn5gmFHCF94z3sLiEKhmyBpZ8eBXtWgbs554WA8/DiEc/2tuWSllXkWIk0jPhGaY8hZsH9 FhUXb4MSNW8AGHD9lbvgt/KS/6Iehf/koNaEpLBrCRDW/70bkXKY4Hqhda1/F6UlLY0O5eB90 lFk7Z5hY72F4JXCSidyr8/jiTujwMWs1aTfGLCOTZD+SXDPo9JvVomkW55tbPWOsYQMNOGVGU AwFeUR2F4eR+DiXZ6q4YCc7CHbwYIVWwcXxDFdcV8k/aU/ZiszOLls5bBFJSc0VV3xXUjx3KT cmLn//VON+ULX+85MMaOUG9luo91iw2vRN5FN7zN8ZtNTYUx/AGyl5ldkkGWu8YZX7LIAoXUm FP6C6YZX7a2jziL5OzzPtMHjeCmOGnnwLw2GpSDKmNnkOabn2j075cbQPiPlupW/q0ILpM5OY j7YHSz303ZxPR8= Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 12:41:42 -0000 Am 14.09.2021 um 14:38 schrieb Robert Moskowitz: > I have a script on github, > > https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/master/hhit-gen= .py > > That I want to reference in a draft.=C2=A0 I don't want to include the > script, too big and it will grow still. > > Is there any common practice for such an informative reference? This might help: https://datatracker.ietf.org/doc/html/draft-flanagan-7322bis-07#section-4.= 8.6.9 Best regards, Julian From nobody Tue Sep 14 05:45:54 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C7A83A1A25 for ; Tue, 14 Sep 2021 05:45:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.89 X-Spam-Level: X-Spam-Status: No, score=-0.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch 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 u2uLdXEP37nd for ; Tue, 14 Sep 2021 05:45:26 -0700 (PDT) Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (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 1D17F3A1A20 for ; Tue, 14 Sep 2021 05:45:23 -0700 (PDT) Received: from [IPv6:2001:420:c0c0:1011::4] ([IPv6:2001:420:c0c0:1011:0:0:0:4]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 18ECjFeK117187 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 14 Sep 2021 14:45:15 +0200 Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1631623515; bh=ZMYV2UE4lAUFQaZttFxs3fV6MGtQJ4XP7UT/ZCUZSko=; h=Subject:To:References:From:Date:In-Reply-To:From; b=HYlm5AHhQa/k+2CMiG1gRvnSv6DzsTMcS+lO2HezgnJOGTsp941dFXjrEIX3R4CrN 4pYpvK4tTn9/kZA39uSt8aPez3b+IMk8rUtYzCfVmTPVjdjARq1EIva5q/sqsHVLO7 b90YitLAKMBOtsQqiDzXWtPekPSVotNoJQ5kwgEI= To: Robert Moskowitz , "xml2rfc@ietf.org" References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> From: Eliot Lear Message-ID: Date: Tue, 14 Sep 2021 14:45:14 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lXGgFxJaArxUNCmZ8lOuyXhGyKpRwY3r2" Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 12:45:31 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --lXGgFxJaArxUNCmZ8lOuyXhGyKpRwY3r2 Content-Type: multipart/mixed; boundary="NSfOd4EZTUBC7c4sBJv4Xm1CKR2YDOAKy"; protected-headers="v1" From: Eliot Lear To: Robert Moskowitz , "xml2rfc@ietf.org" Message-ID: Subject: Re: [xml2rfc] Any recommended way to reference code on github? References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> In-Reply-To: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> --NSfOd4EZTUBC7c4sBJv4Xm1CKR2YDOAKy Content-Type: multipart/alternative; boundary="------------E8E40BA3FD0767D68373393F" Content-Language: en-US This is a multi-part message in MIME format. --------------E8E40BA3FD0767D68373393F Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Reference code should be informational, and eref can do the job. The=20 only question is whether to include a hash a'la: The benefit of this is that it won't change in ways that might be=20 incompatible with a static specification such as an RFC. Eliot On 14.09.21 14:38, Robert Moskowitz wrote: > I have a script on github, > > https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/master/hhit-ge= n.py=20 > > > That I want to reference in a draft.=C2=A0 I don't want to include the = > script, too big and it will grow still. > > Is there any common practice for such an informative reference? > > thanks > > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc > --------------E8E40BA3FD0767D68373393F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Reference code should be informational, and eref can do the job.=C2= =A0 The only question is whether to include a hash a'la:

<eref target=3D"https://github= =2Ecom/project/repo/tree/15350a39f3ae82abba663292450aba611e4e8ff3">= ;

The benefit of this is that it won't change in ways that might be incompatible with a static specification such as an RFC.

Eliot

On 14.09.21 14:38, Robert Moskowitz wrote:
I= have a script on github,

https://github.com/ietf-wg= -drip/draft-ietf-drip-rid/blob/master/hhit-gen.py

That I want to reference in a draft.=C2=A0 I don't want to include = the script, too big and it will grow still.

Is there any common practice for such an informative reference?

thanks

_______________________________________________
xml2rfc mailing list
xml2rfc@ietf.org
https://www.ietf.org/mailman/listinfo/xml2rfc

--------------E8E40BA3FD0767D68373393F-- --NSfOd4EZTUBC7c4sBJv4Xm1CKR2YDOAKy-- --lXGgFxJaArxUNCmZ8lOuyXhGyKpRwY3r2 Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAmFAmVoFAwAAAAAACgkQh7ZrRtnSejPD 1gf/ewitmu+9LE1aGRBwYANk7D28JSIDIJLtMgoBYOBO527snjxF0XBJw4Y9xH1uNSpKP63fzPxu Ws7KYib84dxeQ/h4cSByGgasC9QMmN7kp6vUIleOmc3pvLPvui2mGjGXllrvO8IhIp8RBckP0nXI YbDqaDDt/+EWHUjPjBieYu0rUDRlw4Iy4gKVe0QEvMxLSGvAK7AeSKErOTfkjPWlR0Y3kzPiOljd X4GThnrUT6GMn9MHkYEg4X7ZEITh6/MOkxLLGxD6U3D+TF6WrzfGXefzshmm7eWBqZkfdIFiQunL +Z9NnhAGY2XUZgrK2pzrWUUXwhPy2stsBwUoDIWvzg== =vzu7 -----END PGP SIGNATURE----- --lXGgFxJaArxUNCmZ8lOuyXhGyKpRwY3r2-- From nobody Tue Sep 14 05:46:44 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF3F83A1A37 for ; Tue, 14 Sep 2021 05:46:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.891 X-Spam-Level: X-Spam-Status: No, score=-0.891 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch 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 LfVqkGjwLv-b for ; Tue, 14 Sep 2021 05:46:36 -0700 (PDT) Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (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 3ECD53A1A3D for ; Tue, 14 Sep 2021 05:46:36 -0700 (PDT) Received: from [IPv6:2001:420:c0c0:1011::4] ([IPv6:2001:420:c0c0:1011:0:0:0:4]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 18ECkTI0117210 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 14 Sep 2021 14:46:29 +0200 Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1631623589; bh=Q3GeU0hfe2F24eeRoRtKg1AAa7OpqCAypyUYjY70QGI=; h=Subject:From:To:References:Date:In-Reply-To:From; b=HmHOY8i+vefdorPU0psM9sXyUwaRoGcjG1iew+k74V819iLOpv3eA0iW/3dKvpuO2 ocwi9dLL5eXPmAAniHLRqktVTTJDyQdYwOa1BCsyYmQHwYlbxPnWHY05U4IJ7dbChI eZZ3NxO8n6AvmY/9VdChx1A8Prtxyc1wX8EaIFMc= From: Eliot Lear To: Robert Moskowitz , "xml2rfc@ietf.org" References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> Message-ID: <2cd58ddb-6808-c235-ede1-d28af085649f@lear.ch> Date: Tue, 14 Sep 2021 14:46:28 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="93MO0LDZ6UaQhuzsmO5CLoRHhlYb5USQJ" Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 12:46:41 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --93MO0LDZ6UaQhuzsmO5CLoRHhlYb5USQJ Content-Type: multipart/mixed; boundary="YbxGTUSL2m7CcRDy2gzVrZSYX14sytNV2"; protected-headers="v1" From: Eliot Lear To: Robert Moskowitz , "xml2rfc@ietf.org" Message-ID: <2cd58ddb-6808-c235-ede1-d28af085649f@lear.ch> Subject: Re: [xml2rfc] Any recommended way to reference code on github? References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> In-Reply-To: --YbxGTUSL2m7CcRDy2gzVrZSYX14sytNV2 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US Just following up on this in another way, should we want to support PURLs= ? --YbxGTUSL2m7CcRDy2gzVrZSYX14sytNV2-- --93MO0LDZ6UaQhuzsmO5CLoRHhlYb5USQJ Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAmFAmaQFAwAAAAAACgkQh7ZrRtnSejPR XQf/d6ayPhT8PfHZOo87RiGJ9IssMY6hy0k0wrExmQ63SH8hqZtqXifpLAg5ycxt9rDDFEbup+/+ laNCpZQv9yCVaQRc3hDe1pJLKGWHRPE9EnUPSwxBKE4UfwWsuOfT78a/A3jGGljJnhE4whNs0vYP BheXyutRP33TB9X7phRyqy+yIk4QTbPE12MfUw8B3SHYM7PNFC/wrIxEddppmhGq7e23wlzs+0gg y7kuVPNEUv9nSi0OfxUHAIDKEn4FCNOVdEE51PeDEIjGnqcyNTknd1147wjfjcd2zmPjitwv4hrv IdiR8UEjYbvC9xrhp4IXifM1H+nfoSkdThl+jr6c8g== =Xhf3 -----END PGP SIGNATURE----- --93MO0LDZ6UaQhuzsmO5CLoRHhlYb5USQJ-- From nobody Tue Sep 14 07:08:20 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 482073A203F for ; Tue, 14 Sep 2021 07:08:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 Abbu6VUHcvmT for ; Tue, 14 Sep 2021 07:08:15 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 2AF7B3A203E for ; Tue, 14 Sep 2021 07:08:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 6458F62569; Tue, 14 Sep 2021 10:07:13 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0Bf-y+ugKEYE; Tue, 14 Sep 2021 10:07:10 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 9CA776250B; Tue, 14 Sep 2021 10:07:10 -0400 (EDT) To: Julian Reschke , xml2rfc@ietf.org References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> <36a74861-0dac-b9bf-8c95-ff1ec83da14c@gmx.de> From: Robert Moskowitz Message-ID: <444489d0-0293-f7b8-5c07-18c9e51db871@htt-consult.com> Date: Tue, 14 Sep 2021 10:08:09 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <36a74861-0dac-b9bf-8c95-ff1ec83da14c@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 14:08:18 -0000 On 9/14/21 8:41 AM, Julian Reschke wrote: > Am 14.09.2021 um 14:38 schrieb Robert Moskowitz: >> I have a script on github, >> >> https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/master/hhit-gen.py >> >> >> That I want to reference in a draft.  I don't want to include the >> script, too big and it will grow still. >> >> Is there any common practice for such an informative reference? > > This might help: > > > https://datatracker.ietf.org/doc/html/draft-flanagan-7322bis-07#section-4.8.6.9 > Thanks Julian. The example includes a short commit hash.  I see what looks like such a hash for my script, c4b7d1b, but it is a link that is a real long string.  Do I just include this short string as in the example? From nobody Tue Sep 14 07:08:33 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 806063A2054 for ; Tue, 14 Sep 2021 07:08:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 adulDeldHAb1 for ; Tue, 14 Sep 2021 07:08:26 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 5A2843A2050 for ; Tue, 14 Sep 2021 07:08:26 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id E19F262569; Tue, 14 Sep 2021 10:07:25 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id uj1s67nMSDVa; Tue, 14 Sep 2021 10:07:22 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 152296250B; Tue, 14 Sep 2021 10:07:22 -0400 (EDT) To: Eliot Lear , "xml2rfc@ietf.org" References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> From: Robert Moskowitz Message-ID: Date: Tue, 14 Sep 2021 10:08:21 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------389AFE5F89F4BD22FB16412C" Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 14:08:31 -0000 This is a multi-part message in MIME format. --------------389AFE5F89F4BD22FB16412C Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Eliot, On 9/14/21 8:45 AM, Eliot Lear wrote: > > Reference code should be informational, and eref can do the job.  The > only question is whether to include a hash a'la: > > target="https://github.com/project/repo/tree/15350a39f3ae82abba663292450aba611e4e8ff3"> > > The benefit of this is that it won't change in ways that might be > incompatible with a static specification such as an RFC. > You mean like: https://github.com/ietf-wg-drip/draft-ietf-drip-rid/commit/c4b7d1b5d99e409f4843189b8bd26797aafe75c2 ? > Eliot > > On 14.09.21 14:38, Robert Moskowitz wrote: >> I have a script on github, >> >> https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/master/hhit-gen.py >> >> >> That I want to reference in a draft.  I don't want to include the >> script, too big and it will grow still. >> >> Is there any common practice for such an informative reference? >> >> thanks >> >> _______________________________________________ >> xml2rfc mailing list >> xml2rfc@ietf.org >> https://www.ietf.org/mailman/listinfo/xml2rfc >> --------------389AFE5F89F4BD22FB16412C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Eliot,

On 9/14/21 8:45 AM, Eliot Lear wrote:

Reference code should be informational, and eref can do the job.  The only question is whether to include a hash a'la:

<eref target="https://github.com/project/repo/tree/15350a39f3ae82abba663292450aba611e4e8ff3">

The benefit of this is that it won't change in ways that might be incompatible with a static specification such as an RFC.


You mean like:

https://github.com/ietf-wg-drip/draft-ietf-drip-rid/commit/c4b7d1b5d99e409f4843189b8bd26797aafe75c2

?

Eliot

On 14.09.21 14:38, Robert Moskowitz wrote:
I have a script on github,

https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/master/hhit-gen.py

That I want to reference in a draft.  I don't want to include the script, too big and it will grow still.

Is there any common practice for such an informative reference?

thanks

_______________________________________________
xml2rfc mailing list
xml2rfc@ietf.org
https://www.ietf.org/mailman/listinfo/xml2rfc


--------------389AFE5F89F4BD22FB16412C-- From nobody Tue Sep 14 07:22:29 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 231F63A210A for ; Tue, 14 Sep 2021 07:22:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 DIjejFlDkWHo for ; Tue, 14 Sep 2021 07:22:21 -0700 (PDT) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82E7B3A2108 for ; Tue, 14 Sep 2021 07:22:21 -0700 (PDT) Received: from smtpclient.apple (p548dcf6e.dip0.t-ipconnect.de [84.141.207.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4H85CF1bmMz2xM0; Tue, 14 Sep 2021 16:22:17 +0200 (CEST) Content-Type: multipart/alternative; boundary="Apple-Mail=_DA5FE563-C276-482C-8BAE-AC5FA23965FD" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) From: Carsten Bormann In-Reply-To: Date: Tue, 14 Sep 2021 16:22:13 +0200 Cc: Eliot Lear , "xml2rfc@ietf.org" Message-Id: <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> To: Robert Moskowitz X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 14:22:26 -0000 --Apple-Mail=_DA5FE563-C276-482C-8BAE-AC5FA23965FD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 14. Sep 2021, at 16:08, Robert Moskowitz wrote: >=20 >> Reference code should be informational, and eref can do the job. The = only question is whether to include a hash a'la: >>=20 >> > >>=20 >> The benefit of this is that it won't change in ways that might be = incompatible with a static specification such as an RFC. >>=20 >=20 > You mean like: >=20 > = https://github.com/ietf-wg-drip/draft-ietf-drip-rid/commit/c4b7d1b5d99e409= f4843189b8bd26797aafe75c2 = I thought that the point was that the code can still change. Giving a commit ID, but pointing to the mutable document, gets the best = of both worlds. Gr=C3=BC=C3=9Fe, Carsten --Apple-Mail=_DA5FE563-C276-482C-8BAE-AC5FA23965FD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 On = 14. Sep 2021, at 16:08, Robert Moskowitz <rgm@htt-consult.com>= wrote:

Reference code should = be informational, and eref can do the job.  The only question is = whether to include a hash a'la:

<eref target=3D"https://github.com/project/repo/tree/15350a39f3a= e82abba663292450aba611e4e8ff3">

The = benefit of this is that it won't change in ways that might be = incompatible with a static specification such as an = RFC.


You mean like:

https://github.com/ietf-wg-drip/draft-ietf-drip-rid/commit/c4b7d1b5d= 99e409f4843189b8bd26797aafe75c2

I thought = that the point was that the code can still change.
Giving a = commit ID, but pointing to the mutable document, gets the best of both = worlds.

Gr=C3=BC=C3=9Fe, = Carsten

= --Apple-Mail=_DA5FE563-C276-482C-8BAE-AC5FA23965FD-- From nobody Tue Sep 14 07:30:31 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E39DF3A2171 for ; Tue, 14 Sep 2021 07:30:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 6a3xua2gSlwe for ; Tue, 14 Sep 2021 07:30:24 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 433543A216E for ; Tue, 14 Sep 2021 07:30:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 14F536250B; Tue, 14 Sep 2021 10:29:23 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xyimO2jnmXLX; Tue, 14 Sep 2021 10:29:15 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id CB37762434; Tue, 14 Sep 2021 10:29:14 -0400 (EDT) To: Carsten Bormann Cc: Eliot Lear , "xml2rfc@ietf.org" References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> From: Robert Moskowitz Message-ID: Date: Tue, 14 Sep 2021 10:30:08 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> Content-Type: multipart/alternative; boundary="------------93AB921D45B09B819F52BC84" Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 14:30:30 -0000 This is a multi-part message in MIME format. --------------93AB921D45B09B819F52BC84 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 9/14/21 10:22 AM, Carsten Bormann wrote: > On 14. Sep 2021, at 16:08, Robert Moskowitz > wrote: >> >>> Reference code should be informational, and eref can do the job.  >>> The only question is whether to include a hash a'la: >>> >>> >>> >>> The benefit of this is that it won't change in ways that might be >>> incompatible with a static specification such as an RFC. >>> >> >> You mean like: >> >> https://github.com/ietf-wg-drip/draft-ietf-drip-rid/commit/c4b7d1b5d99e409f4843189b8bd26797aafe75c2 > > I thought that the point was that the code can still change. > Giving a commit ID, but pointing to the mutable document, gets the > best of both worlds. I see your point and for this script I definitely agree.  We plan on improving this script. --------------93AB921D45B09B819F52BC84 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

On 9/14/21 10:22 AM, Carsten Bormann wrote:
On 14. Sep 2021, at 16:08, Robert Moskowitz <rgm@htt-consult.com> wrote:

Reference code should be informational, and eref can do the job.  The only question is whether to include a hash a'la:

<eref target="https://github.com/project/repo/tree/15350a39f3ae82abba663292450aba611e4e8ff3">

The benefit of this is that it won't change in ways that might be incompatible with a static specification such as an RFC.


You mean like:

https://github.com/ietf-wg-drip/draft-ietf-drip-rid/commit/c4b7d1b5d99e409f4843189b8bd26797aafe75c2

I thought that the point was that the code can still change.
Giving a commit ID, but pointing to the mutable document, gets the best of both worlds.

I see your point and for this script I definitely agree.  We plan on improving this script.


--------------93AB921D45B09B819F52BC84-- From nobody Tue Sep 14 07:36:57 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83DC63A21BD for ; Tue, 14 Sep 2021 07:36:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 RyRhzoIS4MML for ; Tue, 14 Sep 2021 07:36:50 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 800753A21B9 for ; Tue, 14 Sep 2021 07:36:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 6F51F62434; Tue, 14 Sep 2021 10:35:49 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id y2flw9npOv9W; Tue, 14 Sep 2021 10:35:44 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 3C8FF6250B; Tue, 14 Sep 2021 10:35:44 -0400 (EDT) To: Carsten Bormann Cc: Eliot Lear , "xml2rfc@ietf.org" References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> From: Robert Moskowitz Message-ID: Date: Tue, 14 Sep 2021 10:36:38 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> Content-Type: multipart/alternative; boundary="------------B458B5F96E0114347FC1B91F" Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 14:36:56 -0000 This is a multi-part message in MIME format. --------------B458B5F96E0114347FC1B91F Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 9/14/21 10:22 AM, Carsten Bormann wrote: > On 14. Sep 2021, at 16:08, Robert Moskowitz > wrote: >> >>> Reference code should be informational, and eref can do the job.  >>> The only question is whether to include a hash a'la: >>> >>> >>> >>> The benefit of this is that it won't change in ways that might be >>> incompatible with a static specification such as an RFC. >>> >> >> You mean like: >> >> https://github.com/ietf-wg-drip/draft-ietf-drip-rid/commit/c4b7d1b5d99e409f4843189b8bd26797aafe75c2 > > I thought that the point was that the code can still change. > Giving a commit ID, but pointing to the mutable document, gets the > best of both worlds. As I am constructing the ref xml, I am thinking what date I put in. the date of the commit or the date we wrote the script?  And how do I get that commit hash into the reference? thanks --------------B458B5F96E0114347FC1B91F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

On 9/14/21 10:22 AM, Carsten Bormann wrote:
On 14. Sep 2021, at 16:08, Robert Moskowitz <rgm@htt-consult.com> wrote:

Reference code should be informational, and eref can do the job.  The only question is whether to include a hash a'la:

<eref target="https://github.com/project/repo/tree/15350a39f3ae82abba663292450aba611e4e8ff3">

The benefit of this is that it won't change in ways that might be incompatible with a static specification such as an RFC.


You mean like:

https://github.com/ietf-wg-drip/draft-ietf-drip-rid/commit/c4b7d1b5d99e409f4843189b8bd26797aafe75c2

I thought that the point was that the code can still change.
Giving a commit ID, but pointing to the mutable document, gets the best of both worlds.

As I am constructing the ref xml, I am thinking what date I put in.  the date of the commit or the date we wrote the script?  And how do I get that commit hash into the reference?

thanks

--------------B458B5F96E0114347FC1B91F-- From nobody Tue Sep 14 09:12:27 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72FFF3A246E for ; Tue, 14 Sep 2021 09:12:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 Gh2kIdlYk_04 for ; Tue, 14 Sep 2021 09:12:17 -0700 (PDT) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C7323A246A for ; Tue, 14 Sep 2021 09:12:17 -0700 (PDT) Received: from [192.168.217.118] (p548dcf6e.dip0.t-ipconnect.de [84.141.207.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4H87f60FZtz2xLd; Tue, 14 Sep 2021 18:12:14 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) From: Carsten Bormann In-Reply-To: Date: Tue, 14 Sep 2021 18:12:13 +0200 Cc: Eliot Lear , "xml2rfc@ietf.org" X-Mao-Original-Outgoing-Id: 653328733.453666-33e2aadcbf6a62e54f1a64c7c4d8c8b7 Content-Transfer-Encoding: quoted-printable Message-Id: References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> To: Robert Moskowitz X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 16:12:24 -0000 On 2021-09-14, at 16:36, Robert Moskowitz wrote: >=20 > As I am constructing the ref xml, I am thinking what date I put in. =20= Date of last commit, I=E2=80=99d say. > the date of the commit or the date we wrote the script? And how do I = get that commit hash into the reference? Like this: hhit-py: target: = https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/master/hhit-gen.p= y title: draft-ietf-drip-rid/hhit-gen.py at master =C2=B7 = ietf-wg-drip/draft-ietf-drip-rid date: 2021-09-10 rc: commit c4b7d1b (Or, in XML: draft-ietf-drip-rid/hhit-gen.py at master =C2=B7 = ietf-wg-drip/draft-ietf-drip-rid commit c4b7d1b This is what you get: [hhit-py] "draft-ietf-drip-rid/hhit-gen.py at master =C2=B7 = ietf-wg-drip/ draft-ietf-drip-rid", commit c4b7d1b, 10 September 2021, . Gr=C3=BC=C3=9Fe, Carsten From nobody Tue Sep 14 09:29:38 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D59863A2508 for ; Tue, 14 Sep 2021 09:29:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 bpAgum6KJoa4 for ; Tue, 14 Sep 2021 09:29:18 -0700 (PDT) Received: from implementers.org (implementers.org [IPv6:2001:4b98:dc0:45:216:3eff:fe7f:7abd]) (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 9EFFE3A24EB for ; Tue, 14 Sep 2021 09:29:17 -0700 (PDT) Received: from [IPv6:2601:204:e600:411:d250:99ff:fedf:93cd] (unknown [IPv6:2601:204:e600:411:d250:99ff:fedf:93cd]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 497CCAE269; Tue, 14 Sep 2021 18:29:09 +0200 (CEST) To: Carsten Bormann , Robert Moskowitz Cc: "xml2rfc@ietf.org" References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> From: Marc Petit-Huguenin Message-ID: Date: Tue, 14 Sep 2021 09:29:06 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 16:29:32 -0000 On 9/14/21 9:12 AM, Carsten Bormann wrote: > On 2021-09-14, at 16:36, Robert Moskowitz wrote: >> >> As I am constructing the ref xml, I am thinking what date I put in. > > Date of last commit, I’d say. > >> the date of the commit or the date we wrote the script? And how do I get that commit hash into the reference? > > Like this: > > hhit-py: > target: https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/master/hhit-gen.py > title: draft-ietf-drip-rid/hhit-gen.py at master · ietf-wg-drip/draft-ietf-drip-rid > date: 2021-09-10 > rc: commit c4b7d1b > > (Or, in XML: > > > > > draft-ietf-drip-rid/hhit-gen.py at master · ietf-wg-drip/draft-ietf-drip-rid > > > > > > commit c4b7d1b > > This is what you get: > > [hhit-py] "draft-ietf-drip-rid/hhit-gen.py at master · ietf-wg-drip/ > draft-ietf-drip-rid", commit c4b7d1b, 10 September 2021, > rid/blob/master/hhit-gen.py>. You do not need to indicate the branch -- the commit-id is unique in a repository. > > Grüße, Carsten > > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc > -- Marc Petit-Huguenin Email: marc@petit-huguenin.org Blog: https://marc.petit-huguenin.org Profile: https://www.linkedin.com/in/petithug From nobody Tue Sep 14 11:24:04 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CD623A2812 for ; Tue, 14 Sep 2021 11:24:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 (1024-bit key) header.d=gmx.net 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 V6erx-joQ00B for ; Tue, 14 Sep 2021 11:23:56 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 F27983A280F for ; Tue, 14 Sep 2021 11:23:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1631643833; bh=UmBxbnMl6waijv1ArIxvU5j6v53/9OZV9Kxze17LMBE=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=Of4C39BsDyzKFkQluk/Z079vsZdIxzP8izVs5H/4iExOl7V8s1bL1zMlmdwI7HfVm Ct6QtVXZw51h1r018Bg9CehJxTLRUOX3hmHhKyxW8rOILGCHgltgclRE6BIIMxjEbd B7RdUOAKJvMm9uxg7SUy62FTJdBaX8NqhO8gg54E= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.182] ([84.171.156.148]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MrQIv-1nENsU2m4F-00oVXN for ; Tue, 14 Sep 2021 20:23:53 +0200 To: xml2rfc@ietf.org References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> From: Julian Reschke Message-ID: <3ab312f9-7081-1952-a4bf-786050f3b373@gmx.de> Date: Tue, 14 Sep 2021 20:23:52 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:1yFay+UfdV3A1/O436hhNi0PwHXgdWDTOwP193twcOcVnH3/Hz9 G0w1cmz8jjvrPtyfjDlXLXLJlv3ggiqTDsBT/OHzG1Jc2tuc7lIAn/BlhkReOIg7KICF85g YOFpB4Ya+Kl9c6ZYU13VN74wPwAnp03oddNOrZ2G1piJGYKiQ+Bbt1Eb5c+hWSmpSqG2uGp ai2znQiZl0a7x0449dtvQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:hTBLDdVJRII=:c9a79OB2e75bSmfVCro7VM JDjp1hb+94nV/1Om2E0m8m1YDkVffaLzZDo6JulFWJsdAooJdIy9ufURPlaO0/xWmA/B/7Kui cPQNKaHC6wnxAnk5Tb9Z7p5K+PfKdCUc7iW48tgsdadCABqWlMATtt/v5eoMWZJE7sP5YrhY0 jsb/lwIZz7lRnIRhTvlD/bpDqNu3YEagc6OU9s3iEp7WleAv8UaCSdphKDdoSwNQ9bALimoFP ZEpTZDDtoLjTM+wItQeLxVzAqq9MM86z4F4EF3DDYR9jbTCHKRfSyF/8gJo44qJNIz9BZhkWR 3X0KaCVfqjGVqIyxXIqEroeBfv6+au+f+Prma5+e4N/mWEw1ENZqD8SOCN/zjjdPCClsYa/oZ V4TuIAEtenubeg6H8a5/ZzAE0FJG/+Myp3hmW1gxUJ4DFU1v0IAQLL3Cn1Jw6DTGSSeVADeYf UDU4kcQssUM97vH/3FT0SDnCGdHa2f+5BHSoOEndTQIwVGfzAqrdR+Szjhzsfj9pc8mlqdNM7 wLSCyBeecw2DSI7d51JR4XoHsD2kRdIKjc33HGf1tPDT9nA7BHp7pgHGiSX8Aqm2hUAoH6J2T PoY25ojn61M+ep7NHlmK3ip6v1qxzpIv/ofUN3FZ5+rg2AmyvSjqWCIoPCquvm6HMa2kQ5kVv wNXN+Ev+JY3MK1KisnCnGE+Va6Uqu6VhSVT4g9xACZaQrtDiA84gktuuJc67XPwm2JZjXPpDB qmp/M0kJejg9iyfP9jVwbw8D8YKy3wYuuvA6XOpBUNGoR7h8FjSi9phxh4h/TY3730XcpjEcx Xf0JeBGxTI0hRXZLoluD1Ib96WhmHfnt3BiKUaMv3wlY07ffW0n6nH1H4cSPXNqSbDl3+U9sE wOLdFyZ4yVLQOjXhxTK6EjKrsnzk0CG07USfQl3L33BkTHVRiQIV0yKne5pZcvcAlgLv+5wuh hO3kxPzPeAEH8cOJVh9Vs38/9cjhYUwTtMJJX0GckHZAGxySQ1fu4moLVtmaHzu8FxpQ/MPR4 hYJinLeS4jXHywMkBvf5NrcmdJeX+fV5VzoJni6n+q7LdITNMilpOC4vxvVIWR9WZWtlZzRlL wIPCzj+24c8sPs= Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 18:24:02 -0000 Am 14.09.2021 um 18:12 schrieb Carsten Bormann: > On 2021-09-14, at 16:36, Robert Moskowitz wrote: >> >> As I am constructing the ref xml, I am thinking what date I put in. > > Date of last commit, I=E2=80=99d say. > >> the date of the commit or the date we wrote the script? And how do I g= et that commit hash into the reference? > > Like this: > > hhit-py: > target: https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/ma= ster/hhit-gen.py > title: draft-ietf-drip-rid/hhit-gen.py at master =C2=B7 ietf-wg-dri= p/draft-ietf-drip-rid > date: 2021-09-10 > rc: commit c4b7d1b > > (Or, in XML: > > > > > draft-ietf-drip-rid/hhit-gen.py at master =C2=B7 ietf-wg-dri= p/draft-ietf-drip-rid > > > > > > commit c4b7d1b > ... Or, simpler: reference anchor=3D"hhit-py" target=3D"https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/master/= hhit-gen.py"> draft-ietf-drip-rid/hhit-gen.py at master =C2=B7 ietf-wg-drip/draft-ietf-drip-rid commit c4b7d1b From nobody Tue Sep 14 11:29:28 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB813A27ED for ; Tue, 14 Sep 2021 11:29:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 gsqWNbuIy2Ru for ; Tue, 14 Sep 2021 11:29:22 -0700 (PDT) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 268A13A209F for ; Tue, 14 Sep 2021 11:29:20 -0700 (PDT) Received: from smtpclient.apple (p548dcf6e.dip0.t-ipconnect.de [84.141.207.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4H8BhD1rCLz2xLr; Tue, 14 Sep 2021 20:29:16 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) From: Carsten Bormann In-Reply-To: Date: Tue, 14 Sep 2021 20:29:15 +0200 Cc: Robert Moskowitz , "xml2rfc@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: <401E9A5D-8475-45FB-9A37-26B9F3D1AD64@tzi.org> References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> To: Marc Petit-Huguenin X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 18:29:27 -0000 On 14. Sep 2021, at 18:29, Marc Petit-Huguenin = wrote: >=20 > You do not need to indicate the branch -- the commit-id is unique in a = repository. Again, the point was that this is a reference to a document that is = being updated (and, to make the librarians happy, to a specific version = of it as well). Gr=C3=BC=C3=9Fe, Carsten From nobody Tue Sep 14 12:00:08 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDB493A2926 for ; Tue, 14 Sep 2021 12:00:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 5rCgoK5cFf8M for ; Tue, 14 Sep 2021 12:00:01 -0700 (PDT) Received: from implementers.org (implementers.org [92.243.22.217]) (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 B15003A2928 for ; Tue, 14 Sep 2021 12:00:00 -0700 (PDT) Received: from [IPv6:2601:204:e600:411:d250:99ff:fedf:93cd] (unknown [IPv6:2601:204:e600:411:d250:99ff:fedf:93cd]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id EF49EAE269; Tue, 14 Sep 2021 20:59:51 +0200 (CEST) To: Carsten Bormann Cc: Robert Moskowitz , "xml2rfc@ietf.org" References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> <401E9A5D-8475-45FB-9A37-26B9F3D1AD64@tzi.org> From: Marc Petit-Huguenin Message-ID: <669641c5-6e7e-e420-2a4d-77c555b831f2@petit-huguenin.org> Date: Tue, 14 Sep 2021 11:59:49 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <401E9A5D-8475-45FB-9A37-26B9F3D1AD64@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 19:00:06 -0000 On 9/14/21 11:29 AM, Carsten Bormann wrote: > On 14. Sep 2021, at 18:29, Marc Petit-Huguenin wrote: >> >> You do not need to indicate the branch -- the commit-id is unique in a repository. > > Again, the point was that this is a reference to a document that is being updated (and, to make the librarians happy, to a specific version of it as well). > Sure, in that case use only the branch but not the commit-id. This is similar to an Internet-Draft reference -- either use the name with the version number at the end, which means use that precise version of the Internet-Draft (this is equivalent of using the commit-id); or use the I-D without the version prefix, which means use that whatever is the latest version of that internet-draft, including the final RFC (this is equivalent of using the branch). -- Marc Petit-Huguenin Email: marc@petit-huguenin.org Blog: https://marc.petit-huguenin.org Profile: https://www.linkedin.com/in/petithug From nobody Tue Sep 14 12:57:31 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D417E3A2B8B for ; Tue, 14 Sep 2021 12:57:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 810--iA0utue for ; Tue, 14 Sep 2021 12:57:24 -0700 (PDT) Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 7A9793A2B8F for ; Tue, 14 Sep 2021 12:57:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id DA1D26250B; Tue, 14 Sep 2021 15:56:22 -0400 (EDT) X-Virus-Scanned: amavisd-new at htt-consult.com Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3KAt+40CvqPD; Tue, 14 Sep 2021 15:56:18 -0400 (EDT) Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 5205C62434; Tue, 14 Sep 2021 15:56:18 -0400 (EDT) To: Marc Petit-Huguenin , Carsten Bormann Cc: "xml2rfc@ietf.org" References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> <401E9A5D-8475-45FB-9A37-26B9F3D1AD64@tzi.org> <669641c5-6e7e-e420-2a4d-77c555b831f2@petit-huguenin.org> From: Robert Moskowitz Message-ID: <54bed175-1d07-3cc8-6486-b716c68ca80d@htt-consult.com> Date: Tue, 14 Sep 2021 15:57:11 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <669641c5-6e7e-e420-2a4d-77c555b831f2@petit-huguenin.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 19:57:29 -0000 On 9/14/21 2:59 PM, Marc Petit-Huguenin wrote: > On 9/14/21 11:29 AM, Carsten Bormann wrote: >> On 14. Sep 2021, at 18:29, Marc Petit-Huguenin >> wrote: >>> >>> You do not need to indicate the branch -- the commit-id is unique in >>> a repository. >> >> Again, the point was that this is a reference to a document that is >> being updated (and, to make the librarians happy, to a specific >> version of it as well). >> > > Sure, in that case use only the branch but not the commit-id. This is > similar to an Internet-Draft reference -- either use the name with the > version number at the end, which means use that precise version of the > Internet-Draft (this is equivalent of using the commit-id); or use the > I-D without the version prefix, which means use that whatever is the > latest version of that internet-draft, including the final RFC (this > is equivalent of using the branch). > Ah, got it.  So as we expect this script to improve (the programmer as already putting final touches on next ver), then leave of the commit ID.  Though for something like this it would be "nice" to get the date from Github, as the date would need to be updated with each new ver of the script. From nobody Tue Sep 14 16:19:20 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1D063A3622 for ; Tue, 14 Sep 2021 16:19:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 LGWP3hTPkYkx for ; Tue, 14 Sep 2021 16:19:12 -0700 (PDT) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D77243A33A9 for ; Tue, 14 Sep 2021 16:19:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id B0855389EC1; Tue, 14 Sep 2021 16:19:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsvnFevh03M2; Tue, 14 Sep 2021 16:19:12 -0700 (PDT) Received: from 2603-8000-9603-b513-514a-0c7e-6c38-2428.res6.spectrum.com (2603-8000-9603-b513-514a-0c7e-6c38-2428.res6.spectrum.com [IPv6:2603:8000:9603:b513:514a:c7e:6c38:2428]) by c8a.amsl.com (Postfix) with ESMTPSA id 86ED9389EBD; Tue, 14 Sep 2021 16:19:12 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Sandy Ginoza In-Reply-To: Date: Tue, 14 Sep 2021 16:19:11 -0700 Cc: Robert Moskowitz , "xml2rfc@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <462dd2c3-caa4-3fa6-6d60-5bca34d13402@htt-consult.com> <237AB3F7-8BCF-4EF6-95CB-D46F660E0129@tzi.org> To: Carsten Bormann X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [xml2rfc] Any recommended way to reference code on github? X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2021 23:19:18 -0000 Hi all, Just an fyi that Carsten=E2=80=99s suggestion aligns with the RFC Style = Guide as well:=20 https://www.rfc-editor.org/styleguide/part2/#ref_repo We use the date of the last commit to note what was available when the = document was published. The link enables readers to find the most = current documentation. =20 Thanks, Sandy=20 > On Sep 14, 2021, at 9:12 AM, Carsten Bormann wrote: >=20 > On 2021-09-14, at 16:36, Robert Moskowitz wrote: >>=20 >> As I am constructing the ref xml, I am thinking what date I put in. =20= >=20 > Date of last commit, I=E2=80=99d say. >=20 >> the date of the commit or the date we wrote the script? And how do I = get that commit hash into the reference? >=20 > Like this: >=20 > hhit-py: > target: = https://github.com/ietf-wg-drip/draft-ietf-drip-rid/blob/master/hhit-gen.p= y > title: draft-ietf-drip-rid/hhit-gen.py at master =C2=B7 = ietf-wg-drip/draft-ietf-drip-rid > date: 2021-09-10 > rc: commit c4b7d1b >=20 > (Or, in XML: >=20 >=20 > > > draft-ietf-drip-rid/hhit-gen.py at master =C2=B7 = ietf-wg-drip/draft-ietf-drip-rid > > > > > > commit c4b7d1b >=20 > This is what you get: >=20 > [hhit-py] "draft-ietf-drip-rid/hhit-gen.py at master =C2=B7 = ietf-wg-drip/ > draft-ietf-drip-rid", commit c4b7d1b, 10 September 2021, > rid/blob/master/hhit-gen.py>. >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc From nobody Wed Sep 15 15:40:59 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90F123A16E5 for ; Wed, 15 Sep 2021 15:40:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.847 X-Spam-Level: X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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=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 t9lyj-hMCTJJ for ; Wed, 15 Sep 2021 15:40:53 -0700 (PDT) Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (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 04C023A16E2 for ; Wed, 15 Sep 2021 15:40:52 -0700 (PDT) Received: by mail-yb1-xb34.google.com with SMTP id c6so8958199ybm.10 for ; Wed, 15 Sep 2021 15:40:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:reply-to:from:date:message-id:subject:to; bh=awN/6xQGkDpN9wAKnUP3rTSBWMC2dMrENlGitnLSHtE=; b=F8wijZijeosM08ZNr6drUqF4f0HxSDfjuESy7W+QKGH/iJUvht5CsDuz2rtGZOxSTX 1YrNBHNxuoK/pEdyscqjyW+2Cet8Vj9cvktTFtGC0d1zi/EQhoebisA6PNGPPdWoGVjK AbLIYwy7MRi7RyuctwqaqcbGxo1qbjFfG2l8yoRsoLiD66gl1uoYd97dWFpyfSrg67El A+uWmpLxh9KvOVafnDBYbpc95/RR1BVBZ4eBPxbiT5bBszKSozHsSQoaGKR6ZyoOrL0v TsFG6hEN/RiIRF5yJKmLMUOeL5Ziw4PrFRbAZLJc9Ze1TScDQYRGvEzbnAmDXkqpncPC hGcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to; bh=awN/6xQGkDpN9wAKnUP3rTSBWMC2dMrENlGitnLSHtE=; b=CWGC22Xd73Zg6nYutpV0sn3qOKNl/gtrt7AuJlaH8R1Lv3ezZ/1A8BmUcQBZk7I38h AcGGYuHt6gUkRoz58NLDJpKOqEHDtlFE0ocq9j7lTNymynXsZ5v30kKSdxmEPWfnDydm 1bESvNIqGJ5pUZwTSTSZeswZuabl1M79+fPk7Y5n1oXJa3axj9+QmoV1AeHI1GHl/lRx TtjoV1Hf4edwic/pa0Iu9z8OYGdIxpwm4QPNBmdinA/7rPyQTwDUd593JVRx5ntFFOw6 vtH2aAhaGCcuy9fJAMQCjblGiVFUNBGA48zdu0SjWskpNxzGq3G7opAgKL6eX21b0P6H PuPg== X-Gm-Message-State: AOAM5302GmQt/+y2k2/wMVuBVtD/hGi/5CXNktn/63TqcGfXuObKy0rp xSYWAiv40xB4LXXHfBGhLOI4lWg4slrQbeSUr7sh+CZ5y61Pvw== X-Google-Smtp-Source: ABdhPJzqlm79HJontff2en2Wci/zTt+KLORK5jB9fM5gMX+L+yvv36fCpzahM95UsZQMtl+J+dy0fPAGxphK1k9D/f4= X-Received: by 2002:a25:b28a:: with SMTP id k10mr3246173ybj.398.1631745651436; Wed, 15 Sep 2021 15:40:51 -0700 (PDT) MIME-Version: 1.0 Reply-To: sarikaya@ieee.org From: Behcet Sarikaya Date: Wed, 15 Sep 2021 17:40:40 -0500 Message-ID: To: xml2rfc@ietf.org Content-Type: multipart/alternative; boundary="000000000000eaefb405cc1063c8" Archived-At: Subject: [xml2rfc] Nroff Edit tool X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Sep 2021 22:40:58 -0000 --000000000000eaefb405cc1063c8 Content-Type: text/plain; charset="UTF-8" Folks anybody has a working Mac nroffedit app? I tried the one here, couldn't make it work: http://aaasec.com/nroffedit Thanks, Behcet --000000000000eaefb405cc1063c8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Folks anybody= =C2=A0

has a working Mac nro= ffedit=C2=A0app?

I tried the= one here, couldn't make it work:

http://aaasec.com/nroffed= it


Thanks,


Behcet

--000000000000eaefb405cc1063c8-- From nobody Tue Sep 21 11:12:50 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 331AD3A1405; Tue, 21 Sep 2021 11:12:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.079 X-Spam-Level: X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 kML1PPIhdoLg; Tue, 21 Sep 2021 11:12:31 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 A70003A1403; Tue, 21 Sep 2021 11:12:30 -0700 (PDT) Received: from 84d908c3c732 ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 18LICTYC052815 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 21 Sep 2021 13:12:29 -0500 (CDT) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1632247950; bh=BFChTCLKfr8OkAmlUVuvPyR3DbUTlpyXJdYX4XQStU0=; h=From:To:Subject:Cc:Date; b=RY0p8Ny4rMU/3+rQRuEhoHwKXc95/10wSV9m2IhxcrNkfVbjxtt8Nl2mBo5Q+6L9o UI73I2iL7IJ6HyD/okiZl+ugLZhWJXUR2HEVg7EMxspGAyPU8qvae7weXfZJ8xYgtH +PKm/07W6OIMmX1rWsruyRNw8JN8z5rgm/Tucbmw= X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be 84d908c3c732 Received: from rjsparks by 84d908c3c732 with local (Exim 4.92) (envelope-from ) id 1mSkFk-00005r-6j; Tue, 21 Sep 2021 18:12:24 +0000 From: rjsparks@nostrum.com To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org Cc: rfc-markdown@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Message-Id: Date: Tue, 21 Sep 2021 18:12:24 +0000 Archived-At: Subject: [xml2rfc] New xml2rfc release: v3.10.0 X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2021 18:12:37 -0000 Hi, This is an automatic notification about a new xml2rfc release, v3.10.0, generated when running the mkrelease script. Release notes: xml2rfc (3.10.0) ietf; urgency=low * Merged in [4043] from krathnayake@ietf.org: Fixes Python compatibility issues in bin/uglifycall. * Merged in [4042] and [4045] from krathnayake@ietf.org: Updates docker/run command to support Apple M1. Fixes #675. * Merged in [4041] from krathnayake@ietf.org: Adds missing line joiner settings for
    and
      . Fixes #673. * Merged in [4040] from jennifer@painless-security.com: Fix Makefile rule precedence and repair canonical.xml test to work with yestest. Fixes #671. * Merged in [4037] from krathnayake@ietf.org: Changes RFC regression test to be a seperate test. * Merged in [4036] from krathnayake@ietf.org: Adds RFC regression tests. Fixes #667. * Merged in [4016] from krathnayake@ietf.org: Fix for bad PDF breaks. * pin weasyprint<53 for tox tests * Merged in [4020] from krathnayake@ietf.org: Sort class values in HTML output. Fixes #553. * Merged in [4018] and [4019] from jennifer@painless-security.com: Keep pns from incoming xml when present; handle case that an author does not have an after-next element. Fixes #664. * Merged in [4012] from krathnayake@ietf.org: Remove quotes from the text rendering of . Fixes #600 and #647. * Merged in [4011] from krathnayake@ietf.org: Fix info block runoff issue in PDFs. Fixes #606. * Merged in [4010] from krathnayake@ietf.org: Remove unicode entity replacement step from v2v3 conversion. Fixes #641. * Merged in [4009] from krathnayake@ietf.org: Cache XML XInclude files with referencegroup. Fixes #653. -- Robert Sparks 21 Aug 2021 19:02:15 +0000 The preferred way to install xml2rfc is by doing 'pip install xml2rfc', and 'pip install --upgrade xml2rfc' to upgrade. If there are system- installed python modules which pip will not upgrade, you may have to use 'pip install --upgrade --no-deps xml2rfc' and install dependencies manually. The new version is also available through SVN checkout, with 'svn checkout https://svn.ietf.org/svn/tools/xml2rfc/tags/cli/3.10.0' Documentation for this release is built-in, and also available at: https://xml2rfc.tools.ietf.org/xml2rfc-doc-3.10.0.html Regards, Robert Sparks (via the mkrelease script) From nobody Fri Sep 24 08:57:15 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 479063A07D2 for ; Fri, 24 Sep 2021 08:57:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.887 X-Spam-Level: X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.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 PT9F6r8KpXoo for ; Fri, 24 Sep 2021 08:57:08 -0700 (PDT) Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 85BFE3A07DB for ; Fri, 24 Sep 2021 08:57:08 -0700 (PDT) Received: by mail-io1-xd2f.google.com with SMTP id m11so13242513ioo.6 for ; Fri, 24 Sep 2021 08:57:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:mime-version:subject:message-id:date:to; bh=xvjba584CHdAvUBJmP0xKh8FI1umjJJj8OPPwJdU9nM=; b=wdFBoRwL1Ctkc7S+57pT3NhCqwpErrILrU+QPbXpXgYqXbcDBGXCO+C7n6nnv9QTor 4r8hxoiNHEOYbWoOrDgcQVnfCdO7HsydHU/G4CRr5LNifhVIJTBEBPcdZVyKjJ1hzKFo oUUSDeLSVaBsdcg8usuGHjNZ80TktblEYOQ0XhP4WPxNnLLt/KCr7uaAzhb0/DmsS3iB C+uDbWvRkAzjmdEyHIr7KOgtM1sIG+iTukk6D2PGUiUrPG87iYHwnBQzPeVJYlX9AiMZ FT1BmGF+GVJRIWeJ50rTSjZJ9xzpqXGI0BL9vVwqBgavVtDHjxJW0heo/N7JuSw44g+i d26w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=xvjba584CHdAvUBJmP0xKh8FI1umjJJj8OPPwJdU9nM=; b=Nw0mVjOv7Wckb/+KsfJJaDBpGH3HcuJgdX+fjLwLDy0PGURGJsLVsucJrHKL51mZwE YXniDJUtZHbGUMRefp+sCABPgbwVJEi2m51Eio5X/RmSewtct6ug0irxJgPYwVy0/llu wB7YP5Lsu65EhZ3XaHqcxSCFG5YYWbH1kWYe6OPIzVpKP97Uktff4rgq2k/wWttMzHU2 +BezHgkK7gP4a2Mm9JvFamyoRPy3a+fZCyzmii5cL8EMdQ7DubSBArJyZKNkgQI1E0my EQngVpA70ck1SUsF2URxqi9zMcpATpVtG/HUHn9nZTLzQVvNMhcjVjNbejp/hBWBlN05 uoCA== X-Gm-Message-State: AOAM532wMUiU9sNX7lIQn4rkebSK72N2VPDcSzYSuivJQ60fPduxyvSl Cx825451IgsTA9yd6mLz6EVTiJtE6haMHA5q X-Google-Smtp-Source: ABdhPJz9ngNmapHhbgoxfzVuI4Cqv64ZLxv7fN1wXPbqWVA6kS15WvSa5iQut6AzBHuMFDF1HwLUBA== X-Received: by 2002:a02:ccaa:: with SMTP id t10mr9994033jap.16.1632499027323; Fri, 24 Sep 2021 08:57:07 -0700 (PDT) Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id x5sm4057841ioa.35.2021.09.24.08.57.06 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Sep 2021 08:57:06 -0700 (PDT) From: Brian Rosen Content-Type: multipart/alternative; boundary="Apple-Mail=_398A332B-799F-4F3F-8DA2-7A0CE829C713" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Message-Id: <2EDA9A82-3559-45EA-ABD1-107A671C279E@brianrosen.net> Date: Fri, 24 Sep 2021 11:57:05 -0400 To: xml2rfc@ietf.org X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: [xml2rfc] Refs not sorting X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2021 15:57:13 -0000 --Apple-Mail=_398A332B-799F-4F3F-8DA2-7A0CE829C713 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I=E2=80=99m certain this is a =E2=80=9Cduh=E2=80=9D thing. My = references are not sorting. The beginning of the file is: sortrefs=3D=E2=80=9Ctrue=E2=80=9D is it, right? It was originally = =E2=80=9Cyes=E2=80=9D, no difference. The references section looks = like: Normative References --Apple-Mail=_398A332B-799F-4F3F-8DA2-7A0CE829C713 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I=E2=80= =99m certain this is a =E2=80=9Cduh=E2=80=9D thing.  My references = are not sorting.  The beginning of the file is:
      <?xml version=3D'1.0' = encoding=3D'utf-8'?>
      <?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' = ?>
      <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent" >
      <?rfc strict=3D"true" = ?>
      <?rfc = toc=3D"true" ?>
      <?rfc tocdepth=3D"4" ?>
      <?rfc symrefs=3D"true" ?>
      <?rfc sortrefs=3D"true" = ?>
      <?rfc = compact=3D"true" ?>
      <?rfc subcompact=3D"false" ?>
      <rfc xmlns:xi=3D"http://www.w3.org/2001/XInclude" category=3D"std" docName=3D"draft-ietf-rum-rue-08" ipr=3D"trust200902" obsoletes=3D"" updates=3D"" submissionType=3D"IETF" xml:lang=3D"en" version=3D"3" consensus=3D"yes">
        <!-- = ***** FRONT MATTER ***** -->
        <front>



      sortrefs=3D=E2=80=9Ctrue=E2=80=9D = is it, right?  It was originally =E2=80=9Cyes=E2=80=9D, no = difference.  The references section looks like:
       <back>
          <references>
          =   <name>Normative References</name>
            = <?rfc = include=3D"http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xm= l"?>
            = <?rfc = include=3D"http://xml.resource.org/public/rfc/bibxml/reference.RFC.8446.xm= l"?>

      = --Apple-Mail=_398A332B-799F-4F3F-8DA2-7A0CE829C713-- From nobody Fri Sep 24 09:17:34 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A9453A0B89 for ; Fri, 24 Sep 2021 09:17:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 Tj7t0ZG1cqRH for ; Fri, 24 Sep 2021 09:17:25 -0700 (PDT) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D5C23A0B87 for ; Fri, 24 Sep 2021 09:17:25 -0700 (PDT) Received: from smtpclient.apple (unknown [194.156.182.213]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4HGHHQ2FZsz31Mh; Fri, 24 Sep 2021 18:17:22 +0200 (CEST) Content-Type: multipart/alternative; boundary=Apple-Mail-BB418262-105F-4A1E-8138-06DE1359BFFE Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) From: Carsten Bormann In-Reply-To: <2EDA9A82-3559-45EA-ABD1-107A671C279E@brianrosen.net> Date: Fri, 24 Sep 2021 18:17:20 +0200 Cc: xml2rfc@ietf.org Message-Id: <426A09E6-F3B2-4EB0-A4D9-85EE73C103B4@tzi.org> References: <2EDA9A82-3559-45EA-ABD1-107A671C279E@brianrosen.net> To: Brian Rosen X-Mailer: iPhone Mail (18H17) Archived-At: Subject: Re: [xml2rfc] Refs not sorting X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2021 16:17:31 -0000 --Apple-Mail-BB418262-105F-4A1E-8138-06DE1359BFFE Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable V3 ignores PIs. These now go into the rfc tag as attributes.=20 A little warning might go a long way here=E2=80=A6 Sent from mobile, sorry for terse > On 24. Sep 2021, at 17:57, Brian Rosen wrote: >=20 > =EF=BB=BFI=E2=80=99m certain this is a =E2=80=9Cduh=E2=80=9D thing. My re= ferences are not sorting. The beginning of the file is: > > > > > > > > > > > > > >=20 >=20 >=20 > sortrefs=3D=E2=80=9Ctrue=E2=80=9D is it, right? It was originally =E2=80=9C= yes=E2=80=9D, no difference. The references section looks like: > > > Normative References > > >=20 > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc --Apple-Mail-BB418262-105F-4A1E-8138-06DE1359BFFE Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable V3 ignores PIs. These now go into the rfc t= ag as attributes. 

      A little warning might go a long w= ay here=E2=80=A6

      Sent from mobile, sorry for terse

      On 24. Sep 2021, at 17:57, Brian Rosen <br@brianrosen= .net> wrote:

      =EF=BB=BFI=E2=80=99m certain this is a =E2=80=9Cduh=E2=80=9D thing. &n= bsp;My references are not sorting.  The beginning of the file is:
      <?xml version=3D'1.0' encoding=3D'utf-8'?>
      <?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt' ?>=
      <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent" >= ;
      <?rfc strict=3D"true" ?>
      <?rfc toc=3D"true" ?>
      <?rfc tocdepth=3D"4" ?>
      <?rfc symrefs= =3D"true"= ?>
      <?rfc sortrefs=3D"true" ?>
      <?rfc compact=3D"true" ?>
      <= b class=3D""><?rfc subcompact=3D"false" ?>
      <rfc xmlns:xi=3D"http://www.w3.org/2001/XInclude= " category=3D"std"<= b class=3D""> docName=3D"draft-i= etf-rum-rue-08" ipr=3D= "trust200902" obsoletes=3D"" updates=3D"" submissionType=3D= "IETF" xml:lang=3D"en" version=3D"3" consensus=3D"yes">
        <!-- ***** FRONT MATT= ER ***** -->
        <front>



      sortrefs=3D=E2=80=9Ctrue=E2=80=9D is it, right?  = ;It was originally =E2=80=9Cyes=E2=80=9D, no difference.  The reference= s section looks like:
       <back>
          <references>
            <name>Normative References</name>= ;
            <?rfc include=3D"http://xml.resource.org/public/rfc/bibxml/r= eference.RFC.2119.xml"<= span style=3D"color: #9b2393" class=3D"">?>
        &= nbsp;   = <?rfc include=3D"http://xml.resource.org/public/rfc/bibxml/reference.RFC.8446= .xml"?>

      _______________________________________________
      xml2rfc mailing list
      xml2rfc@ietf.org
      = https://www.ietf.org/mailman/listinfo/xml2rfc
      = --Apple-Mail-BB418262-105F-4A1E-8138-06DE1359BFFE-- From nobody Fri Sep 24 09:36:10 2021 Return-Path: X-Original-To: xml2rfc@ietfa.amsl.com Delivered-To: xml2rfc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56F023A0EDE for ; Fri, 24 Sep 2021 09:36:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-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 (1024-bit key) header.d=gmx.net 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 G1IDy3zm9mM5 for ; Fri, 24 Sep 2021 09:36:01 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 1D58B3A0ED7 for ; Fri, 24 Sep 2021 09:36:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.net; s=badeba3b8450; t=1632501357; bh=wscWHyvYd9mQmHGt3BqfTwzy5IFcW4ccYKGw+GKelY8=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=Fz8qaM1sfdMePc7Zb/BqCYYjXiyzf1e/DmLiBlHMUNL9Y56i0n66PWbeUpKtktK0J uuVNiNb60PlpYki1R8sbRDhYHFTZCTPTCTza9NzOGQe9HoouNGvKX9QeqdvEj3wsUh z4Qt1PwqDZiGkDxRd0tLfGmcXxHWrot7IkCv4IsE= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.178.20] ([84.171.150.96]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N7iCW-1myteJ2zCc-014jMN for ; Fri, 24 Sep 2021 18:35:57 +0200 To: xml2rfc@ietf.org References: <2EDA9A82-3559-45EA-ABD1-107A671C279E@brianrosen.net> <426A09E6-F3B2-4EB0-A4D9-85EE73C103B4@tzi.org> From: Julian Reschke Message-ID: Date: Fri, 24 Sep 2021 18:35:55 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <426A09E6-F3B2-4EB0-A4D9-85EE73C103B4@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:2aWinnaecNalvAEUscRAXtX0KJgiYdg+xZWU6s2zoEJPQMLcy9l 6OiKdTfZsUEakeWVuJvwxSPxVyvIwXi8fr9wf99ABUjjXxppwIqrupQJsUEgCJ0aZN8gDfR QPd3SylBLE8rz3QYk1g3Mg7SH0PVeZwalGGP3j/dgi7TvdhVNsOJ27bopZVDczw3UPZwFKp LgDPo03lBLUFpINny7sdw== X-UI-Out-Filterresults: notjunk:1;V03:K0:nrJmu60pInw=:gw2yrE9Zz/VGuBACydQdy/ 3VFhwJdmY8MhQ8oFKBC+8G2kmbzL7ad8fjhkG4KVVr1lkpB87kp8udLclARQ+ayHqb5DDZ65z /8I9D4xolfRr7Ed8Worub6kyhh95ka2dLfHzhOiEsTSiJR1XKbCU6MiRmsLzwwowjfWhMD9Y2 RlvJjJcXYBSqzZENec6I/wL11D0bwFABKtuupLcYzOC+jD3R+nj4EUOubHJVl41rlCOghv1gL jq20rq2WlGWTxCgg4iRB50lDYEzC2Bo/SNkJYnxQUhbNXa5kVy47Wv8VbK4lg4n/U79bv9DfU rC9t8L6DbrvmsSh4+mPyMN8xF11GhqiKk3KTL55InC1WQSzTasGqaEXbiweJSu5mQe1ZX8sYf ns1wFdi+N5D1QjedA6gLkV1GQha8NIQhEc2WRFfdxAynXPIdlG/goS/PMbnJsky+8LRFsD295 Bf4KQB9Igm92b9gANMWzwR6wBGPdJfXfnDAFhqAdbqgZYcrSu89JFo8FWRClGQD8ztRggl0nD LnJiR3rVjXAsK1AG3qGw8Y99t5IcaTGb025d1nQE9uD3LvGm/jwk75JJ1wKm+43fYpMqFXCs+ BtPxEDvuPwByqUW4ZiQOl3nZGSvaRJrR0EPK1xFs5EjToB5g9LoRbUgZQcNgoGDuybo71uylM KT8MA7RE9tYnBz6y21kOrrKvIyiTcnbDyXybXnhB5Ypn3JOKjRpnL18bQoK58ZDA7DD0TVt1Q DE+Wpdhu9HcTJ+eOgI+a30Q9BxRjE4jOPxZMErN9SQdqgT0VhSppQHSU2pQ8D4ufkXNnVTzSM ASCodqtWopFmqvsPb78qJoMIFrN8JMMpZJDNLiIvZA+fEfrV0Ef2VkWIKxj0igBESwiL8oDKk h1ANaPXv/1u7t/rgJ6t14upKEfU967XlT6biPZ8q3T/bfSuwUx1eTnjUizv5fFZWVkVUgzwKe 9nxUHTH753OClLYFYnO4ujkAn2oq1dJ3hroVKTnAdHeapXkFegbAd9rAth20U2oSq3P1g/4fZ +huW2ldzh6i5pnB+pk9HXgNG/T6kc05GxuXjRPn9k2NUfsGkUXolGozGqWJnR7ryzlFACgsRh GpgfEK/zr7zlXg= Archived-At: Subject: Re: [xml2rfc] Refs not sorting X-BeenThere: xml2rfc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XML2RFC discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2021 16:36:07 -0000 Am 24.09.2021 um 18:17 schrieb Carsten Bormann: > V3 ignores PIs. These now go into the rfc tag as attributes. > ... Yep. Best regards, Julian