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:04 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 4E682130F11 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Feb 2019 10:04:18 -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 cgkPMiITfegU for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Feb 2019 10:04:16 -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 7FD3B130EE2 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 26 Feb 2019 10:04:16 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EC4BAB80FB4; Tue, 26 Feb 2019 10:03:56 -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 A227AB80FAD for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 10:03:55 -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 DOD9eizdKeCB for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 10:03:54 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by rfc-editor.org (Postfix) with ESMTPS id 8A298B80F9E for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 10:03:53 -0800 (PST)
Received: from [192.168.178.124] ([91.61.52.137]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MLelb-1gyxvn1QAt-000wIo; Tue, 26 Feb 2019 19:03:52 +0100
To: Henrik Levkowetz <henrik@levkowetz.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> <755b6d47-663b-f333-fdc4-9acada6ee591@levkowetz.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <033402b8-84ae-0327-35b5-54f21a8d76dc@gmx.de>
Date: Tue, 26 Feb 2019 19:03: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: <755b6d47-663b-f333-fdc4-9acada6ee591@levkowetz.com>
Content-Language: en-US
X-Provags-ID: V03:K1:9fcIOylDN8y+Le1Z0V1RZd/REi56tL5O6/O5CCEqorNMk+bdvhl HOEyaTAqXzt4vQWKdspl3wfnIvQhLjDrVU2GYxLBse5j2B1zlLdwd+YYd3V5tT7SW/Py4mh tqIQBUfDq5xhHRXU0zgXt2qeUu06Z3WEgtwuJ+Q3vdnli1UPlVaWfPn2i98mRCGFUXKIZXq lXiawHXd2/zznw03Mlqvw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:ChuRJRPpA+Q=:1OnkB2U3W0khsSjKWXunQY ubQxqAjTu/BkOWzVyZjAZXz6dOR0h3vHPbXZoTKTDHugi6aqav0jAms3ypnMEg5AtaBlnugQI jFV70LUonke4swCOJr6LLoNvRgquKDZat8yjQ8q6FbUFZ32uR3bGen+zy9eCaBi+6ZMo9Myev FijmdsqWQgztdn5wC1orhVAxEP+QIdRsuPVFA1BjfRR4aIij983CODTbmTZwqlLIgdcONWuLX jg5YqroK3TwhkRQkYvW5lsfUJyjYMyv0hhz1nL4lSTljvABjSsTc+BwWWtsIUPC4CLiReGxPc YpHTvTxm7rDBjEHnVPpPwALeU8+FQfj4crJbrF814a5K7Kxf6L4pP3bc8GnbgIWTUB4YGuG8J srzvB+sqIBzOj9QzSuWhOrH72kB2BR8ViikBof9/DuJJiMjgOs3wGskc2DJiaXPXcaLubVBMH kllIAYfCGzRn6oQOnQSHtsdO4wv3IjOrIIY7s0sn3agVar7JLGDfC8B/128vu70gQm+rqJFO0 zhqjFx+/k4I1Tbm1mkxinAxYv1qZ4uSLfdDwcP2Z4se+8K0KivdQO7CvdVAq/2aQ2qjE+14uJ sQ67d9WY2Ei6XbE0mcwi2f/2u3ER2cfvdH26BbE0EbxRVJw2+ue5/m8j4uKldt0Up0yA9N+O3 nKqiGiD/LofXNhRgaiziInLR50IJwLvmDOuy594YzT6IDJHPOEatThmOWJ9rxQs3SVNooQvEs c8Bzu9DPQejKcE5zbfO8Z+3+DWqzjvH1Q3GISKuz7ofiFtb5XUCD4+YI7TaezLN6vu5JmuAEE zwZYC/VeAsyEYoKj0J8UySx8lkkKbez9y/48HkgV85d/RbtDtPCsM3hd98l7RHIY1o2IPdJl9 OgyfVOvaAHrYNW5C2dciOu9LyKdzww6RFGCRif1lI6BEVSK5SqIcI321Ew3sdrMoekxqOi3Cs sNyyM/F2wsQ==
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 17:47, Henrik Levkowetz wrote:
> 
> On 2019-02-26 17:33, Julian Reschke wrote:
>> On 26.02.2019 17:24, Kent Watsen wrote:
>>> ...
>>> I hadn't seen this issue before, but I did see Henrik's comments about
>>> markers in
>>> draft-levkowetz-xml2rfc-v3-implementation-notes.  FWIW, the
>>> "xiax:markers" attribute
>>> is primarily only to support xml2rfc v2 documents; v3 documents can just
>>> use the built-in
>>> "markers" attribute.
>>>
>>> That said, I think that markers are, in general, a mistake.  That they
>>> were only put their
>>> for tools scrapping plain-text documents.   Assuming tools extract from
>>> XML, then no
>>> markers are needed, neither for framing (to aid the scraping process) or
>>> for capturing
>>> the file's name (which is better served by the aforementioned "name"
>>> attribute.
>>> ...
>>
>> The original reason for "CODE BEGINS" etc was for licensing (to clarify
>> that part of the content is considered to be a "code component").
> 
> No, it was not.  The original reason was to delimit code for other purposes.
> The association with licencing came later

The oldest RFC I see containing "CODE BEGINS" is RFC 5403, dated 
February 2009.

The oldest "code components" list mentioned on 
<https://trustee.ietf.org/trust-legal-provisions.html> is dated November 
2008.

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