Comments on (draft-ietf-pkix-logotypes-05.txt)

["David Cross" <dcross@xxxxxxxxxxxxx>]

I hate to re-visit this late in the game, but...

I would like to strongly propose the following:

Section 3 - Support for the audio format should be optional for clients.
Again, this is a matter of practical implementation and I would like to
esnure that clients and compliant CA MAY support the audio file
logotype.

Section 4.1 - The indirect addressing scheme should be optional for
clients.  The indirect adressing schema MAY be supported by clients and
compliant CA.  I am afraid that unless pre-caching is performed by
clients, this option will not be practical to implement.

Section 7 - Security considerations.  Clients especially should be
cognizant that the URI of a logotype may point to an unusually large
binary object or contain executable code.  Clients MAY impose
constraints on the size or time to download a particular logotype.

Regards,
 
David B. Cross


-----Original Message-----
From: Internet-Drafts@xxxxxxxx [mailto:Internet-Drafts@xxxxxxxx] 
Sent: Thursday, September 19, 2002 4:47 AM
Cc: ietf-pkix@xxxxxxx
Subject: I-D ACTION:draft-ietf-pkix-logotypes-05.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories. This draft is a work item of the Public-Key Infrastructure
(X.509) Working Group of the IETF.

	Title		: Internet X.509 Public Key Infrastructure:
Logotypes in
                          X.509 certificates
	Author(s)	: S. Santesson, R. Housley, T. Freeman
	Filename	: draft-ietf-pkix-logotypes-05.txt
	Pages		: 19
	Date		: 2002-9-18
	
This document specifies a certificate extension for including logotypes
in public key certificates and attribute certificates. Please send
comments on this document to the ietf-pkix@xxxxxxx mailing list.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pkix-logotypes-05.txt