[KEYPROV] FW: [IANA #381285] RFC-to-be draft-ietf-keyprov-pskc-09.txt
"Philip Hoyer" <phoyer@actividentity.com> Wed, 01 September 2010 16:22 UTC
Return-Path: <phoyer@actividentity.com>
X-Original-To: keyprov@core3.amsl.com
Delivered-To: keyprov@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8EFE63A677E for <keyprov@core3.amsl.com>; Wed, 1 Sep 2010 09:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.305
X-Spam-Level:
X-Spam-Status: No, score=-1.305 tagged_above=-999 required=5 tests=[AWL=0.944, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S15Kjqig9idT for <keyprov@core3.amsl.com>; Wed, 1 Sep 2010 09:22:42 -0700 (PDT)
Received: from frhub1.activcard.fr (frhub1.activcard.fr [92.103.229.143]) by core3.amsl.com (Postfix) with ESMTP id 80DE33A695B for <keyprov@ietf.org>; Wed, 1 Sep 2010 09:22:41 -0700 (PDT)
Received: from sur-corp-ex-02.corp.ad.activcard.com (sur-corp-ex-02.corp.ad.activcard.com [192.168.33.40]) by frhub1.activcard.fr (Postfix) with ESMTP id C8345183964; Wed, 1 Sep 2010 18:23:10 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 01 Sep 2010 18:22:04 +0200
Message-ID: <5BFE9E473DBFC24CA87F18F29B3F0AC406890C18@sur-corp-ex-02.corp.ad.activcard.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [IANA #381285] RFC-to-be draft-ietf-keyprov-pskc-09.txt
Thread-Index: ActABL15rER7bVZhRwmEjl3mF43cNQJ7LXtw
From: Philip Hoyer <phoyer@actividentity.com>
To: Phillip Hallam-Baker <hallam@gmail.com>, "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>, Sean Turner <turners@ieca.com>
Cc: keyprov@ietf.org
Subject: [KEYPROV] FW: [IANA #381285] RFC-to-be draft-ietf-keyprov-pskc-09.txt
X-BeenThere: keyprov@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Provisioning of Symmetric Keys \(keyprov\)" <keyprov.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyprov>, <mailto:keyprov-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyprov>
List-Post: <mailto:keyprov@ietf.org>
List-Help: <mailto:keyprov-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyprov>, <mailto:keyprov-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 16:22:43 -0000
All, Could you check the below for one thing. I vaguely remember that ages ago we discussed the fact that IANA should create a registry for algorithms URIs. The below does not do that it defines a registry for PSKC profiles only. Am I missing something here or did we discuss that we would drop the requirement for creation for a algorithm registry? Philip -----Original Message----- From: Amanda Baber via RT [mailto:drafts-approval@iana.org] Sent: Thursday, August 19, 2010 6:09 PM Cc: Philip Hoyer; mpei@verisign.com; smachani@diversinet.com; keyprov-chairs@tools.ietf.org; keyprov-ads@tools.ietf.org Subject: [IANA #381285] RFC-to-be draft-ietf-keyprov-pskc-09.txt Dear Authors: ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED We have completed the IANA Actions for RFC-to-be draft-ietf-keyprov-pskc-09.txt ACTION 1: IANA has registered the following application media type: pskc+xml [RFC-ietf-keyprov-pskc-09] Please see http://www.iana.org/assignments/media-types/application/ ACTION 2: IANA has registered the following in the XML NS registry: keyprov:pskc urn:ietf:params:xml:ns:keyprov:pskc http://www.iana.org/assignments/xml-registry/ns/keyprov/pskc.txt [RFC-ietf-keyprov-pskc-09] Please see http://www.iana.org/assignments/xml-registry/ns.html ACTION 3: IANA has registered the following in the XML schema registry: keyprov:pskc urn:ietf:params:xml:ns:keyprov:pskc http://www.iana.org/assignments/xml-registry/schema/keyprov/pskc.xsd [RFC-ietf-keyprov-pskc-09] Please see http://www.iana.org/assignments/xml-registry/schema.html ACTION 4: IANA has created the following registries at http://www.iana.org/assignments/pskc-parameters PSKC Algorithm Profiles Reference [RFC-ietf-keyprov-pskc-09] Registration Procedures Specification Required Common Name: HOTP Class: OTP URI: urn:ietf:params:xml:ns:keyprov:pskc:hotp Identifier Definition: [RFC4226] Algorithm Definition: [RFC-ietf-keyprov-pskc-09] Registrant Contact: IESG Deprecated: FALSE PSKC Profiling: The <KeyPackage> element MUST be present and the <ResponseFormat> element, which is a child element of the <AlgorithmParameters> element, MUST be used to indicate the OTP length and the value format. The <Counter> element (see Section 4.1) MUST be provided as meta-data for the key. The following additional constraints apply: + The value of the <Secret> element MUST contain key material with a length of at least 16 octets (128 bits), if it is present. + The <ResponseFormat> element MUST have the 'Format' attribute set to "DECIMAL", and the 'Length' attribute MUST indicate a length value between 6 and 9 (inclusive). + The <PINPolicy> element MAY be present but the 'PINUsageMode' attribute cannot be set to "Algorithmic". An example can be found in Figure 3. Reference: [RFC-ietf-keyprov-pskc-09] Common Name: PIN Class: Symmetric static credential comparison URI: urn:ietf:params:xml:ns:keyprov:pskc:pin Identifier Definition: Section 5.1 Algorithm Definition: [RFC-ietf-keyprov-pskc-09] Registrant Contact: IESG Deprecated: FALSE PSKC Profiling: The <Usage> element MAY be present but no attribute of the <Usage> element is required. The <ResponseFormat> element MAY be used to indicate the PIN value format. The <Secret> element (see Section 4.1) MUST be provided. See the example in Figure 5. Reference: [RFC-ietf-keyprov-pskc-09] PSKC Versions Reference [RFC-ietf-keyprov-pskc-09] Registration Procedures Standards Action PSKC Version Reference 1.0 [RFC-ietf-keyprov-pskc-09] Key Usage Registry Reference [RFC-ietf-keyprov-pskc-09] Registration Procedures Expert Review Key Usage Specification Deprecated Reference OTP Section 5 FALSE [RFC-ietf-keyprov-pskc-09] CR Section 5 FALSE [RFC-ietf-keyprov-pskc-09] Encrypt Section 5 FALSE [RFC-ietf-keyprov-pskc-09] Integrity Section 5 FALSE [RFC-ietf-keyprov-pskc-09] Verify Section 5 FALSE [RFC-ietf-keyprov-pskc-09] Unlock Section 5 FALSE [RFC-ietf-keyprov-pskc-09] Decrypt Section 5 FALSE [RFC-ietf-keyprov-pskc-09] KeyWrap Section 5 FALSE [RFC-ietf-keyprov-pskc-09] Unwrap Section 5 FALSE [RFC-ietf-keyprov-pskc-09] Derive Section 5 FALSE [RFC-ietf-keyprov-pskc-09] Generate Section 5 FALSE [RFC-ietf-keyprov-pskc-09] Please let us know whether the above IANA Actions look OK. As soon as we receive your confirmation, we'll notify the RFC Editor that this document's IANA Actions are complete. (If this document has a team of authors, one reply on behalf of everyone will suffice.) Thanks, Amanda Baber IANA
- [KEYPROV] FW: [IANA #381285] RFC-to-be draft-ietf… Philip Hoyer
- Re: [KEYPROV] FW: [IANA #381285] RFC-to-bedraft-i… andrea.doherty
- Re: [KEYPROV] FW: [IANA #381285] RFC-to-bedraft-i… Philip Hoyer
- Re: [KEYPROV] FW: [IANA #381285]RFC-to-bedraft-ie… andrea.doherty