RFC 7512 on The PKCS #11 URI Scheme

rfc-editor@rfc-editor.org Thu, 23 April 2015 03:15 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E10891B2E5B for <ietf-announce@ietfa.amsl.com>; Wed, 22 Apr 2015 20:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 41SmOaDans3W for <ietf-announce@ietfa.amsl.com>; Wed, 22 Apr 2015 20:15:22 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 31D471B2E70 for <ietf-announce@ietf.org>; Wed, 22 Apr 2015 20:14:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6570718046D; Wed, 22 Apr 2015 20:13:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7512 on The PKCS #11 URI Scheme
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150423031354.6570718046D@rfc-editor.org>
Date: Wed, 22 Apr 2015 20:13:54 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/GPTaF1E9zFF9A-_dnz4nS_8nH8s>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2015 03:15:26 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7512

        Title:      The PKCS #11 URI Scheme 
        Author:     J. Pechanec, D. Moffat
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2015
        Mailbox:    Jan.Pechanec@Oracle.COM, 
                    Darren.Moffat@Oracle.COM
        Pages:      20
        Characters: 48759
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-pechanec-pkcs11uri-21.txt

        URL:        https://www.rfc-editor.org/info/rfc7512

This memo specifies a PKCS #11 Uniform Resource Identifier (URI)
Scheme for identifying PKCS #11 objects stored in PKCS #11 tokens and
also for identifying PKCS #11 tokens, slots, or libraries.  The URI
scheme is based on how PKCS #11 objects, tokens, slots, and libraries
are identified in "PKCS #11 v2.20: Cryptographic Token Interface
Standard".

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and 
suggestions for improvements.  Please refer to the current edition of
the Official Internet Protocol Standards 
(https://www.rfc-editor.org/standards) for the standardization state and 
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC