Re: [Sat] SATP Core document has expired
Wes Hardaker <wjhns1@hardakers.net> Wed, 24 January 2024 21:32 UTC
Return-Path: <wjhns1@hardakers.net>
X-Original-To: sat@ietfa.amsl.com
Delivered-To: sat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55FD7C151095 for <sat@ietfa.amsl.com>; Wed, 24 Jan 2024 13:32:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (1024-bit key) header.d=hardakers.net
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 FcxQz52w8TV5 for <sat@ietfa.amsl.com>; Wed, 24 Jan 2024 13:32:40 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 5C946C15152B for <sat@ietf.org>; Wed, 24 Jan 2024 13:32:40 -0800 (PST)
Received: from localhost (unknown [10.0.0.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 1F79926B45; Wed, 24 Jan 2024 13:32:40 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 1F79926B45
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1706131960; bh=dyUyIGVTWda/LpSL4qwWaF5st4TtvAnblJV4QUT34W4=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=HlM4do2pizr7lxtgmDijR8ct0eP0mfC191HPWNLZsL7/ISI7arR27PFBUGcwXa1q1 wawpT8Dimco6KLKFv2lZ+hG8zBKKytJgdceHA8at1s6EhO2DDzhZLKty4xsqJFOIMM E0+jQxefScKKcPh9K9dzGWq7vMRY//zXEIoeYoY4=
From: Wes Hardaker <wjhns1@hardakers.net>
To: VENKATRAMAN RAMAKRISHNA <vramakr2@in.ibm.com>
Cc: Rafael Belchior <rafael.belchior@tecnico.ulisboa.pt>, "sat@ietf.org" <sat@ietf.org>
In-Reply-To: <SJ0PR15MB51329F42E9C3CECE077B5BBFB8752@SJ0PR15MB5132.namprd15.prod.outlook.com> (VENKATRAMAN RAMAKRISHNA's message of "Mon, 22 Jan 2024 14:50:43 +0000")
References: <SJ0PR15MB5132D9DB7C2FC322998121D8B8752@SJ0PR15MB5132.namprd15.prod.outlook.com> <B04DEB0B-5DBB-476B-BA65-3F8D1C177412@tecnico.ulisboa.pt> <SJ0PR15MB51329F42E9C3CECE077B5BBFB8752@SJ0PR15MB5132.namprd15.prod.outlook.com>
Date: Wed, 24 Jan 2024 13:32:39 -0800
Message-ID: <yblttn24du0.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/sat/4AUip1NYtGWMng9kF44PpTSPADw>
Subject: Re: [Sat] SATP Core document has expired
X-BeenThere: sat@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "The purpose of this mailing-list is to discuss the secure asset transfer \(SAT\) protocol and related aspects." <sat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sat>, <mailto:sat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sat/>
List-Post: <mailto:sat@ietf.org>
List-Help: <mailto:sat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sat>, <mailto:sat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2024 21:32:44 -0000
VENKATRAMAN RAMAKRISHNA <vramakr2@in.ibm.com> writes: > That makes sense, but I thought it was an IETF requirement for an unexpired > copy of the draft to be present at all times on the website. It's certainly preferred, and we do try to stick to that especially for WG officially accepted drafts. We no one is perfect. A hard requirement is that drafts to be discussed at a meeting need to exist. The barrier to publishing drafts is so low there is rarely a reason not to publish one immediately, possibly with a caveat at the top that it's under heavy editing at the moment. -- Wes Hardaker USC/ISI
- [Sat] SATP Core document has expired VENKATRAMAN RAMAKRISHNA
- Re: [Sat] SATP Core document has expired Rafael Belchior
- Re: [Sat] SATP Core document has expired VENKATRAMAN RAMAKRISHNA
- Re: [Sat] SATP Core document has expired Thomas Hardjono
- Re: [Sat] SATP Core document has expired Thomas Hardjono
- Re: [Sat] SATP Core document has expired VENKATRAMAN RAMAKRISHNA
- Re: [Sat] SATP Core document has expired Wes Hardaker
- Re: [Sat] SATP Core document has expired Wes Hardaker