Re: [KEYPROV] FW: [IANA #381285] RFC-to-bedraft-ietf-keyprov-pskc-09.txt
<andrea.doherty@rsa.com> Wed, 01 September 2010 16:27 UTC
Return-Path: <andrea.doherty@rsa.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 4859B3A6A5E for <keyprov@core3.amsl.com>; Wed, 1 Sep 2010 09:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.09
X-Spam-Level:
X-Spam-Status: No, score=-5.09 tagged_above=-999 required=5 tests=[AWL=-1.046, BAYES_00=-2.599, FRT_PROFILE1=2.555, RCVD_IN_DNSWL_MED=-4]
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 kAFmLK+NGmfD for <keyprov@core3.amsl.com>; Wed, 1 Sep 2010 09:27:29 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id CF8C43A6A67 for <keyprov@ietf.org>; Wed, 1 Sep 2010 09:27:20 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id o81GRi4L002907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Sep 2010 12:27:44 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 1 Sep 2010 12:27:32 -0400
Received: from corpussmtp4.corp.emc.com (corpussmtp4.corp.emc.com [10.254.169.197]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id o81GRIWe031266; Wed, 1 Sep 2010 12:27:31 -0400
Received: from CORPUSMX10B.corp.emc.com ([128.221.14.92]) by corpussmtp4.corp.emc.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 1 Sep 2010 12:27:28 -0400
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 12:27:26 -0400
Message-ID: <9ED76AB595E4944BB33D8998DE448D110A9609C1@CORPUSMX10B.corp.emc.com>
In-Reply-To: <5BFE9E473DBFC24CA87F18F29B3F0AC406890C18@sur-corp-ex-02.corp.ad.activcard.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [KEYPROV] FW: [IANA #381285] RFC-to-bedraft-ietf-keyprov-pskc-09.txt
thread-index: ActABL15rER7bVZhRwmEjl3mF43cNQJ7LXtwAAA8UEA=
References: <5BFE9E473DBFC24CA87F18F29B3F0AC406890C18@sur-corp-ex-02.corp.ad.activcard.com>
From: andrea.doherty@rsa.com
To: phoyer@actividentity.com, hallam@gmail.com, hannes.tschofenig@nsn.com, turners@ieca.com
X-OriginalArrivalTime: 01 Sep 2010 16:27:28.0622 (UTC) FILETIME=[91BD80E0:01CB49F2]
X-EMM-MHVC: 1
X-EMM-MFVC: 1
Cc: keyprov@ietf.org
Subject: Re: [KEYPROV] FW: [IANA #381285] RFC-to-bedraft-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:27:34 -0000
The URI's are addressed here: http://datatracker.ietf.org/doc/draft-hoyer-keyprov-pskc-algorithm-profi les/ Is this what you are looking for? -----Original Message----- From: keyprov-bounces@ietf.org [mailto:keyprov-bounces@ietf.org] On Behalf Of Philip Hoyer Sent: Wednesday, September 01, 2010 12:22 PM To: Phillip Hallam-Baker; Tschofenig, Hannes (NSN - FI/Espoo); Sean Turner Cc: keyprov@ietf.org Subject: [KEYPROV] FW: [IANA #381285] RFC-to-bedraft-ietf-keyprov-pskc-09.txt 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 mailing list KEYPROV@ietf.org https://www.ietf.org/mailman/listinfo/keyprov
- [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