Re: [xml2rfc] referencing an old ID as expired

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 05 May 2020 19:35 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E23363A005F for <xml2rfc@ietfa.amsl.com>; Tue, 5 May 2020 12:35:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.991
X-Spam-Level:
X-Spam-Status: No, score=-1.991 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_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 5hp1k6yFsr2n for <xml2rfc@ietfa.amsl.com>; Tue, 5 May 2020 12:35:23 -0700 (PDT)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-eopbgr700080.outbound.protection.outlook.com [40.107.70.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61D483A0061 for <xml2rfc@ietf.org>; Tue, 5 May 2020 12:35:23 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lOcF0VybshARNVZyQFGJJPBZ8O5Og+kvyTr114jjLODiSE75jqsjuSIahiEydw80NeQc0qhGGpsZMN8h9eFexG9PF3462KiIIfu9PLboeqv1tBy406/0lWSuSSZFpt4L7XsaOjncAiVadMXqxcUGkxfSrZw5Y2QXRWJTtny/dQ4BGitFJgLTmZgN4W1orqA+Gv9+YhwqJoLenXNIjO3kZ77eJ4ONG1vcpcyAHBPf32WTQaCmlMyeS7U6Ib5Jh5bL5O2awmEVNgcv/teqqP2HtGN/TT5Aot50g7YX52aBc5Ls2jSHQI1oFw0wQKWUA8lPJqf3EorfnLEF1q7faCm/Sw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=krIZ0vHdFHQphxfMoL6S93gZ+VsCHWxwtzaW1+jWCOI=; b=BJJ2WDbOvCGKEGKIykjoYZ3OBlFCNC4Hq8LYefC3NkQ+vvqFTOGh8usKTXESqk7nh1waKgFP8ovrfuSY9PIZif+4JEpQoQys+CnlK0wCF6FZgmjJnaLXJCL60i2DBJKbYdVQPqsw5+I8QMl8Hwfr56RqtwHsu2K3CUPzIo0tWg9jRrxqYMkU+IPbDVjPU3FsSvpWmWwDxR8NNXop/MYLhzYVMOY1/149Hm3EBG8D83I9CQ0rWXU4KnoazKUtxvvKC0dZHqLavNCSFkwNU9Rku7kWjsfdpOGU+B7FFPUIHEcty64XVhV+3cMzJq/NsuEB8L4V8+QkqWNiG3CMgFdkPw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=permerror (sender ip is 18.7.68.33) smtp.rcpttodomain=ietf.org smtp.mailfrom=alum.mit.edu; dmarc=none action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=krIZ0vHdFHQphxfMoL6S93gZ+VsCHWxwtzaW1+jWCOI=; b=WGVqAby+WHhPV6sKNzwJgrjCiwCqU8zXrylCUv/TZFjtaQ1o0j497auC9LojpNp/9f3KJFSlgjCq9i1qAaLnnempDMZEsWe52nt4VbSEtuHOy7kt4B3uE1sgTE17jpF+0aLuxn3FolCJ7D/z4A7l+68YordkzRS1qFVudz6SeQY=
Received: from MN2PR01CA0057.prod.exchangelabs.com (2603:10b6:208:23f::26) by BN6PR12MB1730.namprd12.prod.outlook.com (2603:10b6:404:ff::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2958.20; Tue, 5 May 2020 19:35:22 +0000
Received: from BL2NAM02FT025.eop-nam02.prod.protection.outlook.com (2603:10b6:208:23f:cafe::9b) by MN2PR01CA0057.outlook.office365.com (2603:10b6:208:23f::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2958.20 via Frontend Transport; Tue, 5 May 2020 19:35:22 +0000
Authentication-Results: spf=permerror (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=alum.mit.edu;
Received-SPF: PermError (protection.outlook.com: domain of alum.mit.edu used an invalid SPF mechanism)
Received: from outgoing-alum.mit.edu (18.7.68.33) by BL2NAM02FT025.mail.protection.outlook.com (10.152.77.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2958.27 via Frontend Transport; Tue, 5 May 2020 19:35:20 +0000
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id 045JZJil023805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <xml2rfc@ietf.org>; Tue, 5 May 2020 15:35:20 -0400
To: xml2rfc@ietf.org
References: <781a50a7-5faa-1043-56b2-f52b5ac91a80@htt-consult.com> <0ba7aad8-05c2-ad91-9c36-20d58ad5c082@gmx.de>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <04138b58-b7cb-b6b7-7d31-8025a5720902@alum.mit.edu>
Date: Tue, 05 May 2020 15:35:19 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <0ba7aad8-05c2-ad91-9c36-20d58ad5c082@gmx.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:18.7.68.33; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:outgoing-alum.mit.edu; PTR:outgoing-alum.mit.edu; CAT:NONE; SFTY:; SFS:(376002)(39860400002)(346002)(136003)(396003)(46966005)(33430700001)(2616005)(4744005)(6916009)(956004)(31696002)(336012)(86362001)(7596003)(5660300002)(31686004)(33440700001)(356005)(8676002)(8936002)(53546011)(82310400002)(36906005)(316002)(26005)(786003)(70586007)(70206006)(47076004)(478600001)(82740400003)(2906002)(186003)(75432002)(43740500002); DIR:OUT; SFP:1101;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: f8dbbb38-0208-41f2-465c-08d7f12b72f1
X-MS-TrafficTypeDiagnostic: BN6PR12MB1730:
X-Microsoft-Antispam-PRVS: <BN6PR12MB1730D62C744921C2B46AD5E1F9A70@BN6PR12MB1730.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:6430;
X-Forefront-PRVS: 0394259C80
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: xOgdrVK1CGmk5wQfMCwFXJRaBCTNw64u5/QAHSy7H9Wshx7sCbbAd3wMvZb1Qzjs67iFeX4n0N0j4M2+1pH2kEFqen0op8sKKHd1awBQfuE+YPOKoG8Alk3pbJKIaMcgxBHIoSlB0YB+/eeaEjVMYbYf6JPIK0qSJhTcjFT+OV5DdkHsIIi3Yo1N4oBcKMo6yL9naDEEqSfnKbUV9ufkkMJ4TC0y4juLM+LgXx5ox1omkqHFVbnXzYolW6YFwmQFPgDzlGQ+AqSdAxDDUepYl1xuDtL0Pl60fwfEuFwUzZzutIKeZ4lLZny9++2vTH3I5IOCStzzlMCMZyMk8wKbM+Ho6lgYC/O3VG9g54VKxVVBdMy+gRRauE97n7LdMQWBKZ/ww+2RmAsBRkZbziagm4TKwRbP+z9HDVdKLAItNzm7eUFzOfIauNi/vkGK6+8ew88xf4xjfnIBukFe52ouZpgamx4DtJbusRH3iDlpYnfNEDycioOj1buU32FadtwUAexhbg0RJPoMfSShtSYhxJVAnaOlalhyWL5ph+hfX/yO+SbpjUl+F3DvRpn+afqqiCaCzKwS/iUWbDgspx6zl5w1sEcia/Mo0gQ1ShMZ8tY=
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 May 2020 19:35:20.9947 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: f8dbbb38-0208-41f2-465c-08d7f12b72f1
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33]; Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR12MB1730
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/czFiCfBI0imeNx_vgdTogWCIFgs>
Subject: Re: [xml2rfc] referencing an old ID as expired
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 May 2020 19:35:26 -0000

On 5/5/20 11:12 AM, Julian Reschke wrote:
> On 05.05.2020 16:49, Robert Moskowitz wrote:
>> I want to reference an old ID for various reasons.  The ID is expired
>> and no xml.  So I created my own ref section:

I don't see much point in highlighting the fact that it is expired in 
the reference. *Any* time you reference a draft, even if it is active at 
the time you publish your document then it can eventually become 
expired. In some sense it remains a work in progress after it expires, 
it simply isn't making very much progress.

And after a draft has expired you can still post a next version of it.

Seems to be a distinction without a difference.

	Thanks,
	Paul