IETF Logo Mail Archive

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

Kent Watsen <kent+ietf@watsen.net> Tue, 26 February 2019 16:52 UTC

Return-Path: <010001692ab8ef80-96b79bab-c831-4917-b5a2-edc3a37ab952-000000@amazonses.watsen.net>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5490212D4F2 for <ietf-and-github@ietfa.amsl.com>; Tue, 26 Feb 2019 08:52:40 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 ka6ibmWQiCj5 for <ietf-and-github@ietfa.amsl.com>; Tue, 26 Feb 2019 08:52:38 -0800 (PST)
Received: from a8-64.smtp-out.amazonses.com (a8-64.smtp-out.amazonses.com [54.240.8.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FD5F131000 for <ietf-and-github@ietf.org>; Tue, 26 Feb 2019 08:52:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1551199957; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=ZBN7KUzuhK7DiedWvX8V+vGNv5IneheF5ueMYdSgmrs=; b=hOsGzY/1Q8ZjHMwvpSI8Tu2Si07fW9DRzVP22Uafv8HSGHZ8U4YhuUk3Mtc/5zBf 5Hs7mcoFOGmlI+23rcGzjnEtkg92uX5nSMlgMawBc00UkvqmcD9FdMkhKo6vGL74+dU jLM+OOz25yeN72WWpQx4mdnf/ucIhVAKwYWu3DsU=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <010001692ab8ef80-96b79bab-c831-4917-b5a2-edc3a37ab952-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BF7BC02F-4E97-45DC-A240-6234DF204455"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 26 Feb 2019 16:52:36 +0000
In-Reply-To: <ea32731b-55cf-aa67-a87a-184dfbad6d49@gmx.de>
Cc: ietf-and-github@ietf.org, RFC Interest <rfc-interest@rfc-editor.org>
To: Julian Reschke <julian.reschke@gmx.de>
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>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.02.26-54.240.8.64
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/4FwrMFMPsUo1KrbMDCQmWzMkiNI>
Subject: Re: [Ietf-and-github] [rfc-i] New Version Notification for draft-kwatsen-git-xiax-automation-00.txt
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2019 16:52:41 -0000


> The original reason for "CODE BEGINS" etc was for licensing (to clarify that part of the content is considered to be a "code component").


Perhaps and, if so, then the markers may still have a purpose.   

That said, I only know the markers coming from https://tools.ietf.org/html/rfc8407#section-3.2 <https://tools.ietf.org/html/rfc8407#section-3.2>, which came from https://tools.ietf.org/html/rfc6087#section-3.1 <https://tools.ietf.org/html/rfc6087#section-3.1>.   As the co-chair and shepherd for these drafts, I assure you that my limited understanding for the original motivation is correct.   It's not intended to have any relationship to copyrights, though RFC6087 conflates both a module-level copyright (inside the YANG module) and markers (outside the YANG module) in Section 3.1, which we de-conflicted in RFC8407.

Kent

v2.23.0 | Report a Bug | By Email