IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] Fwd: PKCS#9 and #10

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Fri, 15 January 2021 16:37 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F5B3A0CFA; Fri, 15 Jan 2021 08:37:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 8dSpTy9Zrgda; Fri, 15 Jan 2021 08:37:43 -0800 (PST)
Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF1783A0CF9; Fri, 15 Jan 2021 08:37:43 -0800 (PST)
Received: by mail-ua1-x92c.google.com with SMTP id n18so3084866ual.9; Fri, 15 Jan 2021 08:37:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MiSyiyQLov0ncq/UZ96ygyp2Ox4jG2kxDW2KWlKmWXU=; b=q3WnOgCcYleBQGPFh/w5Ggewte1N11NDl+tmCdhFY+gXuedsYgL1DoD1w/XxpW/pnB ThvE20hHND8qGG2hE6/Hjga+VisZDR2R3MPuJ+3Gi9SVaa14jRJTwIo2PBpfxwlNZW7a 5IPkMEgQPnCciSDjxNVdv9VEbIcZnBw9hxi1K1LU7T1Z3dzGUpHBy9IXx1Lh7NhTchjD uOwAj5rkz1JYSQRb5+xLycjNzZipyLBN+vp3GcgEMigDQUCUsjMqzccBmniu4M5hLRbm JHEBsyTE/TQLje9w+/9sB65zxVRYxC3SCn/BhuAkbwwZ+MQXl/F/m7/jKmheHGX6VwjF aybg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MiSyiyQLov0ncq/UZ96ygyp2Ox4jG2kxDW2KWlKmWXU=; b=FY94tYhdjwsidLdcv+dVDQQjaz0SIh54UIRrOzrlqTuJBgO2CJZyDSbYwi2eeqjIIa lX3mveXBLMHUhlRrn/PpbsjqDyPVMW/YKgYwGjlRVv5LAnC/uKoX8Jm6N/EyVxCchbTt IYpwy51/YmM86cz/Xzao2Jaopkpxfr6EOBeXra7GsWhPLPk88Uf/x9cnDADh0ob5exUa UfD0vLLZQS1SIaLZsVyTe7/fpEVRRzYyowIidDnoNywJ+XBcXJFv/iVdS6WDpCopgRO+ A9mnlv4wI347wTgiCBwSKPzsDJxh6J9kW6VFA4jIiqHl8XwFrVru+xeQPFLKvvtR0n6E w7Fg==
X-Gm-Message-State: AOAM532O2QzWh6uanTFLdaFOSf4Eb8bCd+MGD0HGb5fAl/x+1xnPbzGE /xy3H+2u74q9EMGgMRAdLcy7eYGJRvzw9g+7oi7BJd7n
X-Google-Smtp-Source: ABdhPJxGTYlwKvS9so08hWCjKQVYluJuOBH3JLN15EyrlW4hu0aHjolIXN5xYJfKJXjLR3NmJw8EtGA/+gyEdoScloA=
X-Received: by 2002:ab0:48ed:: with SMTP id y42mr10379043uac.3.1610728662577; Fri, 15 Jan 2021 08:37:42 -0800 (PST)
MIME-Version: 1.0
References: <E8CEA61867EF1E4A9BD05D64D74F76B250F9EE68@MX307CL02.corp.emc.com> <CAHbuEH4YWd_J9+XFUdWUq4kUkiURLEgvoXTT+G9ucdEkVuzP7Q@mail.gmail.com> <f0f7dbbd-9295-3065-5644-e89b3182696f@levkowetz.com>
In-Reply-To: <f0f7dbbd-9295-3065-5644-e89b3182696f@levkowetz.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Fri, 15 Jan 2021 11:37:06 -0500
Message-ID: <CAHbuEH7XmEVGwcUcXgETB35gdve9N8xBvd3W7+c3OFbs6BDFww@mail.gmail.com>
To: Henrik Levkowetz <henrik@levkowetz.com>, Benjamin Kaduk <kaduk@mit.edu>
Cc: IETF Tools Development <tools-development@ietf.org>, Trustees Trustees <trustees@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c336ec05b8f2fd14"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/YlSB1luJUwknzBCE8kHrggRtQr0>
Subject: Re: [TOOLS-DEVELOPMENT] Fwd: PKCS#9 and #10
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development mail list <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2021 16:37:45 -0000

Hello,

Is there any way we can address this?  Ben, current AD is assuming the
transfer didn't happen even though it was complete.  There's no marker
attached to the datatracker record to indicate the transfer for these 2
documents happened.

Thank you,
Kathleen

On Wed, Jul 31, 2019 at 12:00 PM Henrik Levkowetz <henrik@levkowetz.com>
wrote:

> Hi Kathleen,
>
> On 2019-07-30 21:29, Kathleen Moriarty wrote:
> > Hello!
> >
> > I am not sure how I can attach this change in the copyright and change
> > control status to RFC2985 and RFC2986.  The IPR disclosure page doesn't
> > quite fit as the license is specific to the standard and opening it up
> > further for use.  For the other PKCS documents, we did a revision of the
> > RFC.  I'd like this to not be lost with me and for others doing work with
> > these standards to know that it is fine for them to do so.  Any ideas?
>
> IPR declarations carry forward through "obsoletes" and "replaces" document
> relationships, so if a new RFC marks the previous one as obsoleted, the
> IPR declaration should show up for any new RFCs for the same standard.
>
> Registering the change for the current RFCs seems to be the right thing
> to do.
>
>
> Best regards,
>
>         Henrik
>
>

-- 

Best regards,
Kathleen

v2.23.0 | Report a Bug | By Email