IETF Logo Mail Archive

Re: [rfc-i] [Ietf-and-github] New Version Notification for draft-kwatsen-git-xiax-automation-00.txt

Julian Reschke <julian.reschke@gmx.de> Tue, 26 February 2019 18:13 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 localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD8D130EE2 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Feb 2019 10:13:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.181
X-Spam-Level:
X-Spam-Status: No, score=-5.181 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.018, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 ypVJRH2J7dxR for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Feb 2019 10:13:24 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44E55130ECD for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 26 Feb 2019 10:13:24 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9ED04B82054; Tue, 26 Feb 2019 10:13:04 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 16ECDB82050 for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 10:13:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ckeMknFcSsE for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 10:13:01 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by rfc-editor.org (Postfix) with ESMTPS id 223C5B81E77 for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 10:13:00 -0800 (PST)
Received: from [192.168.178.124] ([91.61.52.137]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Mc8Pz-1ggLYX1WJr-00JXIb; Tue, 26 Feb 2019 19:12:54 +0100
To: Henrik Levkowetz <henrik@levkowetz.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, Kent Watsen <kent+ietf@watsen.net>
References: <155112114000.10633.2593235416875795961.idtracker@ietfa.amsl.com> <01000169261421c7-978ecbf5-dcc4-4738-ba58-f409ce6adaf1-000000@email.amazonses.com> <2e4a853c-6622-81e8-adf5-02deb3e1d6e3@gmx.de> <010001692a9f8f0f-a4ba1870-6959-4518-8503-6e30424b1ac9-000000@email.amazonses.com> <ea32731b-55cf-aa67-a87a-184dfbad6d49@gmx.de> <010001692ab8ef80-96b79bab-c831-4917-b5a2-edc3a37ab952-000000@email.amazonses.com> <c0ecb9bc-793e-fa36-c916-1027ec12ddea@joelhalpern.com> <ef58bede-02b8-dcb8-1ffd-eef921e9a715@levkowetz.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <cb8b78e5-dc0a-5877-6011-16bfbda2540e@gmx.de>
Date: Tue, 26 Feb 2019 19:12:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <ef58bede-02b8-dcb8-1ffd-eef921e9a715@levkowetz.com>
Content-Language: en-US
X-Provags-ID: V03:K1:vrPZvFzeAsrFSDc2Kzv+AUoSlrJBJm8xMBEOQvTZ2SPeNmY8yWK zXWf+EJqKRwgbNTxUt4A6xyaSZ57bmiFthY1eFJdxwS1WsMQX2kjVrTM7j0zZAur1KFTViJ T101g9N1Z61g5JE/6ETcndLbT3Rff9chwu9YkySq7mLg6oXgZVobHNIlfQRMn+kHUB5yi0E P0rF+/tQV1rajJ6vkgxAQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:HpiXbeI+7LE=:Ez77nrgQwe+mcEww2RKPaA SqZLl1ojpthmdwRETAY5maYrSESYvYGGUO/sg9uWrov7jQirxbHHGU3bqunxSgOwq9BMrS6tK MT+k31x79ptIp3eSg0v7khp+l5QnGAeUG/QEpppVh7cS41AdjvtnpcTIAo3SISOV9qetJ3mHq RbYNoyDBP5FPwK+4lTVwGlJUleogbrqpqEAnw9yYmyYNimVXx1yHCwfXVCUeUY5Tt9NkM0Hy5 U9Tk0AfZSdjSRhPfmiIZEqgvkonJOJZUKl1yunmOWxB2Lgq14H8W/6XLtQe+C++8J79AqGMyj sEVgpCjKH2j8PnatCuoPusTxhDHWlyLaKrrJQg/hdhpbsD1ynAIFecPiDyq596rxdc036CmyE iO95O1drESlMCQ24AOXL3ROM9ssObw1oD/QcEdSr9JOCJ+ygTqeVgmIhzzhh3yDh8GKJ/1bTr aI70aNYR03qShg48JRzqEUFprhFvaRLHwq0uw6C01QAOzpRkVcWcN2+E9bOsmXvd3lNKy5H5l 4PMh1kaDHkh19LTipPs8XwABKwBt7dVorJ1jXXbqfOD+CuckgmX8x0xUZmorLuB6Bu9cq2flo 69QFzgr/6Fk+xbpspP+nL91wkxJwfX8K0By/jZM5wZmd9o2rdnWYM6vSzHUmT4kh6NTNsCxM7 VUbMHqWr3jo/gj23OQ/jZQ9CuTkIJQQGYlfh+NzSKhEXxpFxxTgR+vEYlSHgZH7bw24T+g3Gi WHe8XNwCYas27U/oF8aIgdtzgkpur5QTMyKa4A22aPbdGbU8wRiJiIwZS//kPyh2X25/qFHXz O1o7MZvAo9i8M6po5g0iCju370SOeCYxJ7D51Z2pKGaTFTwonwufoJsfHgtVfkLeayhFtA427 3PTL58+IkC51Ep9mFcnT/J3qI7xyn34BswCU8gmnfL1xMYZm2uXmU2grfTcMPsaztGxtylQfW I1acUESlliw==
Subject: Re: [rfc-i] [Ietf-and-github] New Version Notification for draft-kwatsen-git-xiax-automation-00.txt
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: RFC Interest <rfc-interest@rfc-editor.org>, ietf-and-github@ietf.org
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 26.02.2019 18:25, Henrik Levkowetz wrote:
> Hi Joel,
> 
> On 2019-02-26 18:19, Joel M. Halpern wrote:
>> RFC 5377 section 4.3 calls out that code has different copyright grants
>> than other parts of the document.  It describes various examples of
>> code, and then asks the IETF Trust to specify textual marking for code
>> so that authors can be explicit and can mark things that may not be
>> obvious by the examples.
>>
>> So it goes back a lot earlier than 6087.
>> And as far as I know goes back to before there was any tooling support
>> for the markings.
> 
> Indeed.  And later, when there was discussion about possible code markings,
> I proposed that we use the <CODE BEGINS>, <CODE ENDS> introduced by RFC 6087,
> rather than inventing something new.
> ...

Those were introduced much earlier, and exactly for the reason I stated. 
That's at least how I read the historic documents, and it also matches 
my memory.

But wait, we even discussed it on xml2rfc - see 
<https://mailarchive.ietf.org/arch/msg/xml2rfc/7jfoO9KlNkiASuztADbtB9cmHew>, 
dated September 2009.

Best regards, Julian
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email