Subject: Re: [KEYPROV] [pskc] Latest draft of PSKC

From: "Philip Hoyer" <[email-masked]>
Date: Sat, 19 Apr 2008 08:30:47 +0200

I have not submitted yet so please make the changes.

I suggest we use urn:ietf:params:xml:ns:keyprov:container:1.0

Alse please add URI for PIN and KeyContainer.

Then send back to me.

I will add Phillips suggested section on Data semantics on monday and then submit.

Philip

----- Original Message -----
From: Pei, Mingliang <[email-masked]>
To: Philip Hoyer; Salah Machani <[email-masked]>; Hallam-Baker, Phillip <[email-masked]>; Hannes Tschofenig <[email-masked]>
Cc: [email-masked] <[email-masked]>; Turner, Sean P. <[email-masked]>; [email-masked] <[email-masked]>
Sent: Sat Apr 19 04:57:10 2008
Subject: RE: [pskc] Latest draft of PSKC

In the IANA section shall we use the same URI for the schema that we have early defined (see schema section)? 
 
urn:ietf:params:xml:ns:keyprov:container:1.0
 
vs
 
urn:ietf:params:xml:ns:pskc1
 
I am fine with the algorithm URIs in registration section. We need to add ones for "KeyContainer" and "PIN" type.
 
We need to change examples and schema section to match the registration section. I can make those changes by next Monday if you can hold on submission. Please comment on the schema URI choice.
 
Thanks,
 
- Ming

________________________________

From: Philip Hoyer [mailto:[email-masked]] 
Sent: Friday, April 18, 2008 9:17 AM
To: Pei, Mingliang; Salah Machani; Hallam-Baker, Phillip; Hannes Tschofenig
Cc: [email-masked]; Turner, Sean P.; [email-masked]
Subject: [pskc] Latest draft of PSKC

Ladies and Gentlemen,

Please find attached the latest PSKC draft in xml and .txt form including the latest schema and a list of changes.

Missing bits are:

*	Decision to use schema derivation for KeyProperties from KeyBase (please see other email) current proposed schema does just introduce a new XML type called KeyProperties without using schema derivation (I am proposing not to use it and leave as in current proposal and attached schema) 
*	Should we use String or bas64binary for unencrypted values.(maybe leave as is to maintain compatibility with -03 version) 
*	Phillip Hallam Bakers section for IANA registry for the Data semantics 
*	Some outstanding clarification on Andrea’s comments. 

The rest has been addressed.

Please note that currently unless you used CardAppPersoProfileId the spec is functionally (message) compatible with the one in version -03

Unless you have major comments I like to submit this ASAP.

Philip

________________________________

Philip Hoyer 

Senior Architect - Office of CTO

ActivIdentity (UK)

109 Borough High Street

London SE1 1NL

Telephone: +44 (0) 20 7744 6248

Direct: +44 (0) 20 7744 6455

Fax: +44 (0) 20 7744 6249

Private and confidential: This message and any attachments may contain

privileged / confidential information. If you are not an intended recipient,

you must not copy, distribute, discuss or take any action in reliance on it.

If you have received this communication in error, please notify the sender

and delete this message immediately.

_______________________________________________
KEYPROV mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/keyprov