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

Kent Watsen <kent+ietf@watsen.net> Tue, 26 February 2019 19:47 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 0878E130EBA for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Feb 2019 11:47:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5
X-Spam-Level:
X-Spam-Status: No, score=-5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 clg2HioOv4_Y for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 26 Feb 2019 11:47:32 -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 2E84C1200D8 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Tue, 26 Feb 2019 11:47:32 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9D945B80678; Tue, 26 Feb 2019 11:47:12 -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 6EC1DB80678 for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 11:47:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 jZ1YnpzwIM8a for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 11:47:09 -0800 (PST)
Received: from a8-88.smtp-out.amazonses.com (a8-88.smtp-out.amazonses.com [54.240.8.88]) by rfc-editor.org (Postfix) with ESMTPS id C1CDAB80675 for <rfc-interest@rfc-editor.org>; Tue, 26 Feb 2019 11:47:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1551210447; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=BLz49T7jYawYe8KW9iIsWYXMGsCl2AnbC9UrAKNmcLc=; b=f5bPZH6xLirUXL6+iGNz5o8EqDooc+Tp/HN3/P9TeDEbZCKTvhsM3f3BbG0V2WbU W6pkWCJnq4KfYPbXTwexC9YlOb5WQGelnNsxDAnB3WS4K/jYW3QTryL9x4P5V7hsJth DBzyiy+Nj9bq7mAlzfBzbDUk6/91CT7shHlC0HQs=
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <add6a423-7c4a-61b6-bef3-0f36bfac82cd@levkowetz.com>
Date: Tue, 26 Feb 2019 19:47:27 +0000
Message-ID: <010001692b5900b0-a1d0677a-0979-421e-b4c1-c054cdbfbab8-000000@email.amazonses.com>
References: <155112114000.10633.2593235416875795961.idtracker@ietfa.amsl.com> <01000169261421c7-978ecbf5-dcc4-4738-ba58-f409ce6adaf1-000000@email.amazonses.com> <0100016926dbd0be-1c4219e8-5389-433c-9326-c17addd023c6-000000@email.amazonses.com> <05d6799b-b4ee-9f04-e77e-dd4f8ea4e3aa@levkowetz.com> <010001692afbb77c-4e1fe666-0631-48e5-aa44-54e477da77d2-000000@email.amazonses.com> <add6a423-7c4a-61b6-bef3-0f36bfac82cd@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.02.26-54.240.8.88
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Hi Henrik,

Just responding to your comment about the "name" attribute (all your other comments were on the level).

While RFC 7991's description of the "name" attribute is compellingly close to the intended need, it doesn't explicitly state that "name" MAY or MUST NOT include relative directory paths.  My naive reading/understanding is that the "name" is just the name of the file itself, the so called "basename" of a complete filepath value.    At least, having "name" be defined to have this concrete purpose seems to have cross-cutting value.   

My purpose seems twisted by comparison, to the extent that I question if any other tool would want or need to know an inclusion's original filepath value.   On the other hand, "originalSrc" is semantically perfect for my needs.  Let me turn this around and ask, why does preptool use "originalSrc" as opposed to "name" and, that being the case, how is it any different for xiax?

Regards,
Kent


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