Adding public key information to UBL party definition?

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

Fellow Security SC members,

In our current UBL 2.1 PRD1 party definition:

http://docs.oasis-open.org/ubl/prd1-UBL-2.1/mod/summary/reports/UBL-AllDocuments-2.1.html#t-CommonLibrary-1179

... there is no provision for storing public keys associated with the 
party.  Much like an email address or a telephone number, it is a 
public piece of information that might be useful to know about the party.

Is the same true for any certificates associated with the party?

I'm not proposing any tie between these constructs and the signature 
extension, because the signature extension is going to contain any 
needed key and certificate information in the actual <ds:Signature> 
construct found in the extension.

Does it make sense to propose this addition for PRD2 as a property of 
a party that might be useful to the recipient?

Perhaps not, since it won't be used by the extension, but maybe 
someone else on the Security SC can see a use for having such 
information available to the recipient for a party to provide when it 
is describing itself.

Perhaps it will be useful because it will be needed to decode or 
validate email messages that are signed with the party's private key?

Happy holidays and happy new year to all!

. . . . . . . . . . . Ken

--
Contact us for world-wide XML consulting & instructor-led training
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal