Re: Embedded certificate image

[Anders Rundgren <[e-mail]>]

In the "competing" proposal, certificate images are locally stored
but not embedded in certificates.  This is a viable solution when
images are only to be consumed by the end-user.  For external
consumption (which I consider an entirely different use-case),
the existing I-D seems quite sufficient.

Anders

Stefan Santesson wrote:
> This is the first of two unresolved issues listed in the Certimage draft.
>
> Is there any reason to provide any means to embed certificate images 
> in a certificate.
>
> The reason why this might be a valid option is because we often use 
> certificates in environments that have sufficient bandwidth and memory 
> capacity to allow certificate images to be stored in the certificate 
> itself. By storing the image in the certificate, we could save a 
> network retrieval.
>
> The main counter argument is that it would be a serious disadvantage 
> if a certificate occasionally needs to be used in a constrained 
> environment and the fact that the base standard that we are updating 
> (RFC 3709) simply does not allow embedded images.
>
> One way to do this could be to store images in a separate extension 
> and then define  a way to reference that image from the logotype 
> extension through an internal reference.
>
> My proposed resolution is to exclude local storage from the current draft.
> Defining local embedding is adding unnecessary complexity to the draft.
>
> If a strong reason emerges to allow local storage, then this can be 
> defined in a separate draft.
>
> /Stefan