[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LAST CALL:draft-ietf-pkix-time-stamp-05.txt
> Denis,
>
> let me clarify our position:
>
> It is NOT the intention of the ISO working group to introduce patented
> mechanisms, our approach is to allow for MULTIPLE mechanism to be used
> for time stamping.
Roland,
Since you said that you want multiple mechanisms to be used and that
it is NOT the intention of the ISO working group to introduce
patented mechanisms, would you be able to provide at least one
useful example of such a binding mechanism that is not patented ?
Denis
> That's why we introced a mechanism identifier. This
> ISO draft does NOT suggest the IETF use or endorse any other mechanism,
> it is just for interoperability reasons.
>
> We are also trying to have common data structures to achieve a common
> base that allows for further extensions (for the IETF and the ISO
> protocols) of time stamping protocols but may be used for schemes as
> already introduced in part 2 of our working draft.
>
> I hope that this clarifies our requested changes.
>
> Roland
>
> --------------------------------------------------------------------
>
> Mueller, Roland <roland@tuvit.net>
> TUVIT Inc.
>
> Mueller, Roland
> TUVIT Inc. <roland@tuvit.net>
> 8716 North MoPac Suite 220;Austin;Texas;78759;U.S.A. Télécopie: (512) 795-0495
> Bureau: (512) 795-0494