Re: [IETF-PKIX] OCSP using ASN.1

[Ambarish Malpani <ambarish@xxxxxxxxxxxx>]

Hi Mike (and All),
    Didn't ever want to imply that the OCSP draft I posted had your
endorsement (I thought my preamble made that clear, but perhaps I should
have been clearer). Since I took a lot of material from your original
draft,
I didn't feel right about removing your name from the author list. If
this
was a breach of protocol, I apologize. I'll remove your name from the
author list in any future posts.

Would still be interested in your comments about the writeup itself.

Regards,
Ambarish

Michael Myers wrote:
>
> All,
>
> I want folks to know that the OCSP draft distributed by Ambarish does not
> have my endorsement.  My name was placed on it without my consent.  As the
> primary author of OCSP, I wish to point out that Ambarish's draft should be
> considered an individual submission.  The standards-track OCSP draft is
> available for review on the IETF web site.
>
> I have discussed the basis of the ASN.1 requirement with Rich Ankney, my
> co-author on the OCSP standards-track draft.  We agree that OCSP is and
> should remain a very simple protocol to solve a very simple problem and that
> the current OCSP syntax is sufficient for the requirements being addressed.
> We recognize however that it may not provide all the capabilities that an
> ASN.1-based version could address.  We further agree that the scope of
> problems addressed by this counter-proposal would actually be better couched
> as extensions to the Notary Protocol draft.
>
> Mike

--
---------------------------------------------------------------------
Ambarish Malpani
Architect                                              (650) 849-9880
ValiCert, Inc.                                  ambarish@valicert.com
3160 W. Bayshore Road                         http://www.valicert.com
Palo Alto, CA 94303