Re: [Secdispatch] Marking SPKAC as Historic

Arnaud Taddei <arnaud.taddei@broadcom.com> Thu, 10 November 2022 19:32 UTC

Return-Path: <arnaud.taddei@broadcom.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A887BC1522C9 for <secdispatch@ietfa.amsl.com>; Thu, 10 Nov 2022 11:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.675
X-Spam-Level:
X-Spam-Status: No, score=-7.675 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.571, 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_HELO_NONE=0.001, SPF_NONE=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=broadcom.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 c2uAN5XT-A0J for <secdispatch@ietfa.amsl.com>; Thu, 10 Nov 2022 11:32:14 -0800 (PST)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (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 EC48EC14F74C for <secdispatch@ietf.org>; Thu, 10 Nov 2022 11:32:14 -0800 (PST)
Received: by mail-pj1-x1029.google.com with SMTP id m6-20020a17090a5a4600b00212f8dffec9so2687963pji.0 for <secdispatch@ietf.org>; Thu, 10 Nov 2022 11:32:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=cc:to:subject:message-id:date:in-reply-to:references:mime-version :from:from:to:cc:subject:date:message-id:reply-to; bh=FIFxJYkhBXXUOULP7p5fTTLPEf7nDS5ic6vE4dtDAuU=; b=YUN8IFkeyQ72fuWOLY7r4+k1JvZIpHCzrCr4KATHZ5UZvgmAISiqsMsCeKbnMsMnBw LVCoKCMa0AhZGMSxyWxQkDugQq3AJAd5BClI21Z6xmofsMxf2Hpxi2GyDKpYkRfU2Y14 2reAzUtp2/DKxZRVSvXUCMGR5QZzUYf7+uxYo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:in-reply-to:references:mime-version :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=FIFxJYkhBXXUOULP7p5fTTLPEf7nDS5ic6vE4dtDAuU=; b=Cpz2gxvF+c1RwGhGQK7JU2x2oJlYvz/MZWEq/lbVNdLbn7qngAGzZYXjuUwCIWCPKU SLGuwxGS9cBS6z0ZqIH/J20zcNrC67kKYefFjIO/WEt36wSgzvHwwBPnuG3wEWb0Pr4S D5pwbukq1pTFmCdCv1+U9ivD+G3A+SwHjdaVGTCuBJsEdc4nZkz+qKpV43DD/lnsSjqL S1qHwxeUIdG3V+tEAJyUH23YSXYqcwSkKZuaCeuUsZIuFJ54SYol+tQXTcVgc0PKMdqE oY7veAbW5t6H101smLOZpE98/P6KOdOIIxfulHvnSlH9IvQ3sn1sRuI2nranT7us3Xcc YBdA==
X-Gm-Message-State: ACrzQf2g+N5XvWjMDLN+VNk5CT8Fe6ObfyN3klJQsbX7UAMPSHGugT8o PghhoBR/ZTAIWujbZ3jc0yyXplmHDOCYWeYKGWamo6KWdYhMZAsIzIHFR0xIW/S9wQdZ9gileW4 oFuy8mWiRW2WivpTZ/tVx
X-Google-Smtp-Source: AMsMyM6MmAfuphO01OQ2A9UzyrnMnBn8lTA2xljDxz32xjhIlvlsT4mSMY7ED7VU9jNIgTj3IcMyoqhzUslTm5SPBqc=
X-Received: by 2002:a17:902:c403:b0:187:222d:1ede with SMTP id k3-20020a170902c40300b00187222d1edemr55408204plk.150.1668108733525; Thu, 10 Nov 2022 11:32:13 -0800 (PST)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Thu, 10 Nov 2022 11:32:11 -0800
From: Arnaud Taddei <arnaud.taddei@broadcom.com>
Mime-Version: 1.0 (1.0)
References: <CAHbrMsAPOw-PRHOh9OO1fU3tkN2ywWvAihG-2xWyu_SPgTYzLQ@mail.gmail.com>
In-Reply-To: <CAHbrMsAPOw-PRHOh9OO1fU3tkN2ywWvAihG-2xWyu_SPgTYzLQ@mail.gmail.com>
Date: Thu, 10 Nov 2022 11:32:11 -0800
Message-ID: <CAMTNNNcoDuj3MtfwGGOFBY8xxufXcjbBxeKD8hiaEw_ROYyVsA@mail.gmail.com>
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
Cc: secdispatch@ietf.org, Roman Danyliw <rdd@cert.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="0000000000008aa7bc05ed22d488"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/kN_D5QfMg6DLHnGrr0RiCrmrnuA>
Subject: Re: [Secdispatch] Marking SPKAC as Historic
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2022 19:32:18 -0000

Sounds reasonable and clean given this context.

Sent from my iPhone

> On 10 Nov 2022, at 17:59, Ben Schwartz <bemasc=40google.com@dmarc.ietf.org> wrote:
>
> 
> I want to float the idea of marking the SPKAC Informational draft as Historic, assuming it is completed and published.  I think that might accurately reflect the consensus of the IETF regarding SPKAC.
>
> Marking a document Historic at the time of publication is unusual, but it seems logical when we are (finally) describing a format that has seen little use since the 90s and is not recommended today.
>
> I imagine that the sponsoring AD can choose the status without too much process overhead.
>
> --Ben Schwartz
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.