Re: [xml2rfc-dev] V3 breakage in formatting internet draft references

"Martin Thomson" <mt@lowentropy.net> Fri, 11 October 2019 05:25 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5698E120047 for <xml2rfc-dev@ietfa.amsl.com>; Thu, 10 Oct 2019 22:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=N7UazETE; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=jaXQsQyF
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 hkt7e1RDNHrZ for <xml2rfc-dev@ietfa.amsl.com>; Thu, 10 Oct 2019 22:25:06 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A040312003E for <xml2rfc-dev@ietf.org>; Thu, 10 Oct 2019 22:25:06 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id BE9D321F1E for <xml2rfc-dev@ietf.org>; Fri, 11 Oct 2019 01:25:05 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Fri, 11 Oct 2019 01:25:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm3; bh=O4P1d Ez5R4sSgaPwAEci2/Z9Mh220kdp22uFBPReAXI=; b=N7UazETEsz1TFfbAy/KN4 N6Xi2CW79dNbYHOTcW3LWBYbDA91jadHrEFpVTmUAeYcp9c4mC/R48jflkqMrB0P eY4Aezc+xz5NoubE/0iAZ2tVLNR8SMkExbAmYH77bfJp9YF8K14QBIYT722aUM5a Ct+6bYF3+kEz6QYA5wrfe6nnAy2LYoKjD+s6g++m5x183M2HxdB8leEla5awI88X bK48tr6f1+oc954WUn4Shge70aek/sfTjV67qXt3wqm7T1dFxTWhi0LETarHZPUi 8ZMcwmA3xZpuBvOS4ZregDBU18eaYDdiHwXAo2LDU8V+Yr/jiBSrVbF8zUrvIcfN A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=O4P1dEz5R4sSgaPwAEci2/Z9Mh220kdp22uFBPReA XI=; b=jaXQsQyFMWioAkIkoKrsh4gywnLeoFmkn9EBq1MfL7lyC6AmyR4s+JUFA ODDPnzMuZCJxuKIgFVsomI3dwW35qGqT8VblYaWEKMdo6OjSAWc1bi5HlZGSahNh Glmz7I7p4lcj2wJWwZbGtD48Cn3ASy/LKgj47kYheTrjqqA92mRnIFF6pPnb5lhw jM3fRWQ8ZFAyBDKyJu2JjLrF5Yz0hPAbncFS+uU4VxHnw8iU2pkqdsC9Oyrxw6Yj i9dzCD/FN87Q6OKpNtu76h9F0KqrrbzlE1UijTBP7Y8IyVG20ZoKCBT8zSDfJL6F zvF1eMQdMEF/YRKe9wAfJ5HsBDvow==
X-ME-Sender: <xms:MRKgXdYWhSG0oTfHgQXq4R-QLDRhQ7tJwU3a98hnOLCLfnA32zh_Yg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrieeggdelhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgsehtqh ertderreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucffohhmrghinheprhhftgdqvgguihhtohhrrdhorh hgpdhivghtfhdrohhrghenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghn thhrohhphidrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:MRKgXQ1-Bl0uxsiw-I9B-7rMFE7QDKhRPnsDitMUg9Tud834J0HM-A> <xmx:MRKgXXOk3fW7r_B0WkKj_damTRE35Gd4T1hBrPjz22_ARncvRWasbg> <xmx:MRKgXSJzd-JqpTABZibnKpvIglctbzrR9UEcO36Spy1K39bxkDP0bQ> <xmx:MRKgXQ2XTbubeG0ALpr3Afm4ElRExTkkLp7qNR7F5KgkgyI7_shpew>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4F545E00A5; Fri, 11 Oct 2019 01:25:05 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-360-g7dda896-fmstable-20191004v2
Mime-Version: 1.0
Message-Id: <1b0187cc-e6ae-424e-8814-29ebb2756980@www.fastmail.com>
In-Reply-To: <db200ee8-e042-cdc1-2058-5afcc4d4cd57@gmx.de>
References: <7e8bb742-1939-b48c-e7f7-03f3bec6bd63@gmx.de> <6F5868A8-56F3-4E26-B297-2CE0BD765397@rfc-editor.org> <b750c06e-caab-40e9-617d-57e0f79ff585@gmx.de> <DD4A3091-9E2B-417A-AF3A-8A44AFBBE60E@rfc-editor.org> <db200ee8-e042-cdc1-2058-5afcc4d4cd57@gmx.de>
Date: Fri, 11 Oct 2019 16:24:46 +1100
From: Martin Thomson <mt@lowentropy.net>
To: xml2rfc-dev@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/xuOSuWr0tLaqb8dI5lyDkJ0FOic>
Subject: Re: [xml2rfc-dev] V3 breakage in formatting internet draft references
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Oct 2019 05:25:09 -0000

On Wed, Oct 2, 2019, at 13:45, Julian Reschke wrote:
> > Well, there are always things the authors don’t provide that are
> > automatically added. And since we’ve been talking about making sure that
> > internal links to specific sections are included (which perforce MUST go
> > to tools references) the thought was to be consistent and have the
> > reference point to the same place that the internal section pointers are
> > going to send people. I think it would be confusing to have one set of
> > links go one place, and another set of links to somewhere entirely
> > different.
> 
> Well.
> 
> Right now the tools target is only inserted when none is specified, so
> this is not in line what you're arguing for.
> 
> Also, for RFCs the target uses https://www.rfc-editor.org/info/rfcNNNN,
> which also is not the URI used for the section links.

I'm with Julian here.  There is no right answer, so don't provide one.  For me, today, if I was forced to pick, I'd probably pick the tools.ietf.org URL, but I don't think that that holds true once we start publishing decent HTML copies so that I can use real HTML over a txt2html conversion.  And others will of course have different preferences.

In this context, the bare name is sufficient for identification.