Re: [rfc-i] archiving outlinks in RFCs
Eric Rescorla <ekr@rtfm.com> Tue, 25 April 2023 23:56 UTC
Return-Path: <ekr@rtfm.com>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37E0AC1522BE for <rfc-interest@ietfa.amsl.com>; Tue, 25 Apr 2023 16:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level:
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20221208.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mTCgSKNJXRYc for <rfc-interest@ietfa.amsl.com>; Tue, 25 Apr 2023 16:56:15 -0700 (PDT)
Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05349C1516E3 for <rfc-interest@rfc-editor.org>; Tue, 25 Apr 2023 16:56:15 -0700 (PDT)
Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-5529f3b8623so48069727b3.2 for <rfc-interest@rfc-editor.org>; Tue, 25 Apr 2023 16:56:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20221208.gappssmtp.com; s=20221208; t=1682466974; x=1685058974; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=c/tpPwwbXuniM9yc6jsCmKUXrA1GdYMXrBkKipl1rVs=; b=yVOoPPaHi8u0La1CmHiM4c/2qthoZNE75IvQ7WGoNzvwFBPcCDYxDekIDWUH3IR46B rhqd1X6MgEEZ5hSc30Y5oxGsbOF+0Aq7J9DGFk60MXOBiPBoZaUhXiax4KHpbAuwVny2 R8YxN6ziMS/X73wENzR0PuECen/a9z9rmLbhirQOUbIQQNEp8g0OLWxNDdr0VU2BPzTS QZ2hjIQ5fXaktF2+3Hq12oLTKIkrjbaaGhKcz0UPa4+ycmIpXLWNEhKBS5KA7XZA44i2 2JsymVTupur2hZm37XDh5MOvgPnkj/F/kfZRCVDj6pdhTAKWHcllDp1NZJ9KegLbYHqj +uEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682466974; x=1685058974; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=c/tpPwwbXuniM9yc6jsCmKUXrA1GdYMXrBkKipl1rVs=; b=UjSjIV3VdfrqPcFRDJSGtEvx8MaypULnYIg9D4Fs2qcwNwcISiQ6rsjkF3V78s7WMv wyon5vJYBnKQG5Z/vJCBYakBGPsItdRQk3Z8jQfEdSOPgY+GCcQW/miLx19c/8xhkExa AFb/57o9aeHgDJFm9ECId6zVxaXU83TJzjHint4yW8RRUIqKKstJa9rdP0QN3+M9mshQ KVsGYGIFDE33zrnGh07Jak6TsZVWe+nCKXCjZ141LHhBTtu499RDnWOwjJg4LFceMWl6 a0En3DfnHQyQGhhlNjFwC25PZx5ITpL6ULY7GcT+h3Kr0+q3XZ1u8v1I2wmTPkf/Ma1u jEHg==
X-Gm-Message-State: AAQBX9dYf3xOResNLLmMk+oWtWDF/MLnX4CesOS0y8MvhsBuSWapIXGO KPttOKQaRAEyXpU0Y0+P7eKv/7XtAn37AGqtb/ZZy4dINPOvb9RI
X-Google-Smtp-Source: AKy350YuqDcRrMdavQF9yfxAkq/d2jNAGykXfBioPQCqelTuaANFyRvJQgNW+tPvEyyy0mzMrzFfv0DZp7mdO29kdGU=
X-Received: by 2002:a81:a094:0:b0:54f:bc13:202d with SMTP id x142-20020a81a094000000b0054fbc13202dmr12355091ywg.28.1682466973902; Tue, 25 Apr 2023 16:56:13 -0700 (PDT)
MIME-Version: 1.0
References: <E024D9AC-2B92-4720-9713-519592D2362B@rfc-editor.org> <30c30c2f-4e96-560a-73dd-a51ba8d04714@comcast.net> <771B7586-FFBB-49E4-9B99-5578863FBD8B@rfc-editor.org> <CABcZeBOevOj8cWY7dacWxzwZS82+iAjf1p+DZWF=7WZ9JydnrQ@mail.gmail.com> <48de4d92-e279-4c26-ab3c-15dd854b56f8@betaapp.fastmail.com>
In-Reply-To: <48de4d92-e279-4c26-ab3c-15dd854b56f8@betaapp.fastmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 25 Apr 2023 16:55:37 -0700
Message-ID: <CABcZeBPqePQwPAq5pWda1pGaY_=kLkcOxCjZWmOv9yRZ_MNb7g@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: rfc-interest@rfc-editor.org
Content-Type: multipart/alternative; boundary="000000000000537d1c05fa31de20"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/cRTsN0O027v7_Tw9Qy7AFG0fbj4>
Subject: Re: [rfc-i] archiving outlinks in RFCs
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2023 23:56:19 -0000
Hmm... I don't think this is right. Obviously the line between "style" and "content" is a fine, but istm that the line you propose to draw would allow the RPC to take all the MUSTs, style them out with CSS, and replace them with MUST NOTs. ISTM that the links are part of the semantics of the document and so having different links is a question for the RSWG. -Ekr On Tue, Apr 25, 2023 at 4:48 PM Martin Thomson <mt@lowentropy.net> wrote: > On Wed, Apr 26, 2023, at 09:41, Eric Rescorla wrote: > > I think the RPC could *probably* choose to publish a separate version > > that had archival links > > on its own, but I think the default version would again be a question > > for the RSWG. > > If this were a question of publishing, maybe RSWG has a role to play. > However, we don't object to different renderings and this might not be too > far from that. That is, you might make HTML available that had two links > for some references (canonical plus archival) maybe with strikethrough > styling on broken links. > > I don't think that we are in a position to set policy there. Any more > than we are in a position to set policy on what decorations or styling are > added in renderings. The metadata header on rfc-editor.org or the > sidebar on datatracker.ietf.org are examples of "decoration" along these > lines. > > _______________________________________________ > rfc-interest mailing list > rfc-interest@rfc-editor.org > https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest >
- Re: [rfc-i] archiving outlinks in RFCs Martin Thomson
- Re: [rfc-i] archiving outlinks in RFCs Paul Kyzivat
- [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Stephen Farrell
- Re: [rfc-i] archiving outlinks in RFCs Eric Rescorla
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Eric Rescorla
- Re: [rfc-i] archiving outlinks in RFCs Martin Thomson
- Re: [rfc-i] archiving outlinks in RFCs Eric Rescorla
- Re: [rfc-i] archiving outlinks in RFCs Brian E Carpenter
- Re: [rfc-i] archiving outlinks in RFCs Martin J. Dürst
- Re: [rfc-i] archiving outlinks in RFCs Martin J. Dürst
- [rfc-i] standards for references/URLs in RFCs ? (… Toerless Eckert
- Re: [rfc-i] archiving outlinks in RFCs Jay Daley
- Re: [rfc-i] standards for references/URLs in RFCs… Jay Daley
- Re: [rfc-i] archiving outlinks in RFCs tom petch
- Re: [rfc-i] archiving outlinks in RFCs Ted Hardie
- Re: [rfc-i] standards for references/URLs in RFCs… Brian Carpenter
- Re: [rfc-i] archiving outlinks in RFCs Michael Richardson
- Re: [rfc-i] archiving outlinks in RFCs Michael Richardson
- Re: [rfc-i] archiving outlinks in RFCs Michael Richardson
- Re: [rfc-i] archiving outlinks in RFCs Larry Masinter
- Re: [rfc-i] standards for references/URLs in RFCs… Jean Mahoney
- Re: [rfc-i] standards for references/URLs in RFCs… Jean Mahoney
- Re: [rfc-i] standards for references/URLs in RFCs… Brian E Carpenter
- Re: [rfc-i] archiving outlinks in RFCs Brian E Carpenter
- Re: [rfc-i] archiving outlinks in RFCs Ted Hardie
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Brian E Carpenter
- Re: [rfc-i] archiving outlinks in RFCs Marc Petit-Huguenin
- Re: [rfc-i] archiving outlinks in RFCs Eliot Lear
- Re: [rfc-i] archiving outlinks in RFCs Brian E Carpenter
- Re: [rfc-i] archiving outlinks in RFCs Ted Hardie
- Re: [rfc-i] archiving outlinks in RFCs Brian Carpenter
- Re: [rfc-i] archiving outlinks in RFCs Jay Daley
- Re: [rfc-i] archiving outlinks in RFCs Ted Hardie
- [rfc-i] IANA, too (Re: archiving outlinks in RFCs) Carsten Bormann
- Re: [rfc-i] archiving outlinks in RFCs Jay Daley
- Re: [rfc-i] archiving outlinks in RFCs Ted Hardie
- Re: [rfc-i] archiving outlinks in RFCs Jay Daley
- Re: [rfc-i] archiving outlinks in RFCs Eliot Lear
- Re: [rfc-i] archiving outlinks in RFCs Paul Kyzivat
- Re: [rfc-i] archiving outlinks in RFCs Paul Kyzivat
- Re: [rfc-i] IANA, too (Re: archiving outlinks in … tom petch
- Re: [rfc-i] IANA, too (Re: archiving outlinks in … Carsten Bormann
- Re: [rfc-i] archiving outlinks in RFCs Jean Mahoney
- Re: [rfc-i] IANA, too (Re: archiving outlinks in … tom petch
- Re: [rfc-i] archiving outlinks in RFCs Michael Richardson
- Re: [rfc-i] archiving outlinks in RFCs Stephen Farrell
- Re: [rfc-i] archiving outlinks in RFCs Brian E Carpenter
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Stephen Farrell
- Re: [rfc-i] archiving outlinks in RFCs Paul Hoffman
- Re: [rfc-i] archiving outlinks in RFCs Ted Hardie
- Re: [rfc-i] archiving outlinks in RFCs Christian Huitema
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Stephen Farrell
- Re: [rfc-i] archiving outlinks in RFCs Paul Hoffman
- Re: [rfc-i] archiving outlinks in RFCs Michael Richardson
- Re: [rfc-i] archiving outlinks in RFCs Brian E Carpenter
- Re: [rfc-i] archiving outlinks in RFCs Stephen Farrell
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Paul Hoffman
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Alexis Rossi
- Re: [rfc-i] archiving outlinks in RFCs Paul Hoffman
- Re: [rfc-i] archiving outlinks in RFCs Martin Thomson
- Re: [rfc-i] archiving outlinks in RFCs Brian E Carpenter
- Re: [rfc-i] IANA, too (Re: archiving outlinks in … Alexis Rossi