IETF Logo Mail Archive

Re: [rfc-i] 3rd party SDO cross-referencing of IETF work (was: Re: Chair/datatracker tracking expired WG documents ?)

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 25 March 2022 20:55 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 ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0952F3A0B42 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 25 Mar 2022 13:55:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1648241743; bh=be3VNv7tVNleSFUKuHFm4FQNA2oQkbjdBgIDJ24HO5g=; h=To:References:From:Date:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Cc; b=pdH99nNk8fCbOL6TPmAzZrR+wpi51U7xOlcCY/TlxOFhd2Jhuf7PDOewRpbc9kxkV V71watvw4eold98c2PHfEmhwobiOHmTv74RAGYRvpSIaiOFRl8aAU/TkDrh2D1TlTQ uSpmuTEnQcpUGCOXWi1JSVdxXAWNPEyXnT0Rhrg0=
X-Mailbox-Line: From rfc-interest-bounces@rfc-editor.org Fri Mar 25 13:55:34 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2393A0B3E; Fri, 25 Mar 2022 13:55:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1648241729; bh=be3VNv7tVNleSFUKuHFm4FQNA2oQkbjdBgIDJ24HO5g=; h=To:References:From:Date:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Cc; b=yA+LkqnoK0P3DOyw7JCOaMyZQfkHdHvkPyENRUQXf/XEifx1sYjkvdQZJt1f3IdHK 4tpYqHzhgVvi/ctHdeakzScrP3xByEDOriQKrw868ULRhOixx1uJbNLGUWUXpF5QvU Fv4U5uRYjs9SgbjMrrr6GsLJLazgT0ao/wxVSrRc=
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 E24973A0AE5 for <rfc-interest@ietfa.amsl.com>; Fri, 25 Mar 2022 13:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.444
X-Spam-Level:
X-Spam-Status: No, score=-1.444 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Se3YFCW5qAAo for <rfc-interest@ietfa.amsl.com>; Fri, 25 Mar 2022 13:55:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B36E3A0AB4 for <rfc-interest@ietfa.amsl.com>; Fri, 25 Mar 2022 13:55:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix) id 724703BAA5; Fri, 25 Mar 2022 13:55:23 -0700 (PDT)
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 6FEB31BA49E3 for <rfc-interest@rfc-editor.org>; Fri, 25 Mar 2022 13:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 IaKzU8OH6JWx for <rfc-interest@rfc-editor.org>; Fri, 25 Mar 2022 13:55:19 -0700 (PDT)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) by rfc-editor.org (Postfix) with ESMTPS id B7E693BAA5 for <rfc-interest@rfc-editor.org>; Fri, 25 Mar 2022 13:55:19 -0700 (PDT)
Received: by mail-pj1-x102a.google.com with SMTP id o6-20020a17090a9f8600b001c6562049d9so9459811pjp.3 for <rfc-interest@rfc-editor.org>; Fri, 25 Mar 2022 13:55:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=v5d/64a3zVaKpuGB6Okg6s5gi6h8xlONkqe7yMtDuOU=; b=E6Wc2M4iLqpJOlR+tyap3bL7/5RVHqYSexUgIP8eyZBQCC88rfuLWzUHpKEo+z71qy bQiJ5CvoSfSIdNPDhV+xQFiKG8MUsvOtZ87Dp1xiBCdagbRfdJmAyDd0DM1PBJ9EOCkk IDCMJL8Qsqk8VNlQLdivLXMTn/BK3LBj3Y9OQBaLSuAw0AKkShFgyUxrLNiVq+EGEO5O mIt68gDahiCJ8Oe4R8U99EKwiKIA2ss/i6D8fPR8Mv9aolirb4p3LCyjpZbXtaVpY/0o qt/8w+No7nhJvPNAKE/MgJ+OJLpYpTsvKzwl0wYJWLnNp9cCCyttXXzkIedyrY7Xb2jC Xt+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=v5d/64a3zVaKpuGB6Okg6s5gi6h8xlONkqe7yMtDuOU=; b=347G3dUNlzSHJs7P5gYebJ1a9GGSd/WT7fbftXgP4Lu5wrbrxZcTUfASl9SLDUXpfm 2cXPJ2cGlULo2Mh50vS7z4yRlu8zygutd005AT6nOumswy5sQYXGjG+fh27Y3pNIe4jJ ZqZtyVlMQsaCTNsoxXkK07IRIcmRIH2NOiXMW6mgguoTwKExkZgaHPmAyshnyu8lLZl1 Ptu0JAadph0IajsS8H187789F/1MrEWJKXPk8tuuuqemwTqdGSrq29C7hIriHRY81OZb HcrYfQEvT4DtmKPNme/JZVWoDAY6kC6fdlzPqdL1nYm8ceofj15CMS0UW2rk6968vOqn 2i3A==
X-Gm-Message-State: AOAM531PQDOrwBw8EbTUIDroIUM8j2qfzZYMsC/4jEr9+ZCmY5U6xfPZ 5S+dDIz0VBlVcxXhK0Xa+TgoNAQZ4jcGiw==
X-Google-Smtp-Source: ABdhPJwggD98HPuum9ibKXeSeqS+JitzAlxs2kKAqO1snPFPp2fgQYc3LgKMoOJ0RZ3FM/BZ34+dFA==
X-Received: by 2002:a17:90a:4306:b0:1b9:80b3:7a3d with SMTP id q6-20020a17090a430600b001b980b37a3dmr27184884pjg.66.1648241718406; Fri, 25 Mar 2022 13:55:18 -0700 (PDT)
Received: from ?IPv6:2406:e003:1005:b501:80b2:5c79:2266:e431? ([2406:e003:1005:b501:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id lr6-20020a17090b4b8600b001c7730210e5sm13021924pjb.6.2022.03.25.13.55.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Mar 2022 13:55:17 -0700 (PDT)
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, 'Toerless Eckert' <tte@cs.fau.de>, "Joel M. Halpern" <jmh@joelhalpern.com>
References: <Yj2d4DJMFWJOxoZa@faui48e.informatik.uni-erlangen.de> <317196df-3363-36c9-2421-02d9e229f664@joelhalpern.com> <Yj2wI/nc+gzbIBMF@faui48e.informatik.uni-erlangen.de> <9C68473E-4C39-4EFA-ACBF-7968676DDEB8@akamai.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <2f94852a-abe1-7a67-45ae-dbfbd8dd6513@gmail.com>
Date: Sat, 26 Mar 2022 09:55:12 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <9C68473E-4C39-4EFA-ACBF-7968676DDEB8@akamai.com>
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/tsorwf2EdhOEvGrWHejNJ7EO1GE>
Subject: Re: [rfc-i] 3rd party SDO cross-referencing of IETF work (was: Re: Chair/datatracker tracking expired WG documents ?)
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://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>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.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>

Why should we care if some other SDO is happy to publish a "standard" with a normative dependency on a document whose preamble includes these words:

'Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."'

This is not our problem.

Trying to maintain cited-by pointers is approximately impossible. TimBL knew that, which is why the Web succeeded where other distributed hypertext projects failed. While I see why Toerless would like it, I don't think we can have it in the real world.

Regards
    Brian Carpenter

On 26-Mar-22 01:21, Salz, Rich wrote:
> This could be useful information to know. Does the liaison program not handle it?
> 
>>    But of course, if an external SDO does choose to ignore our recommendation
>      and is actually referrring to a draft in a published spec, then i still would
>      rather like to know about it via such an explicit tracking mechanism than
>      not to know about it.
> 
> A potential problem is that, unless people (who, that's also a problem) are diligent about following up and discouraging such use, then it is very easy for the misbehaving SDO to say "but you never complained so we assumed it's okay."
> 
> 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
> 

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

v2.8.7 | Report a Bug | By Email