Me too.
b) for both.
----- Original Message -----
> From: "Peter Reed" <>
> To: "Mike Yoder" <>, "Tim Hudson" <>,
> Sent: Friday, October 26, 2012 7:07:30 AM
> Subject: RE: [kmip] XML and/or JSON
>
> Mike's comments go for me too.
>
> b) for both
>
> -----Original Message-----
> From: [mailto:] On
> Behalf Of Mike Yoder
> Sent: Thursday, October 25, 2012 7:29 PM
> To: Tim Hudson;
> Subject: RE: [kmip] XML and/or JSON
>
> > If you could either reply to me or to the list with your thoughts
> > on
> > JSON and/or XML along these lines that would be ideal.
> > Given this is a topic we have covered off on before I don't think
> > we
> > need a straw poll - just an indication that there is some support
> > for
> > it.
>
> b) for both for me. Being naïve, when I first learned about KMIP I
> was surprised that it *didn't* use SOAP or the like. Anything that
> can speed the adoption of the standard by making the communication
> part easier to program is, IMHO, a good thing.
>
> -Mike Yoder
> Vormetric, Inc.
>
> > 1) JSON
> > a) we think it should be supported as an optional encoding format
> > b) we plan to add this to our implementation
> > c) object to adding anything other than TTLV format being specified
> > d) don't have a strong opinion for or against
> >
> > 2) XML
> > a) we think it should be supported as an optional encoding format
> > b) we plan to add this to our implementation
> > c) object to adding anything other than TTLV format being specified
> > d) don't have a strong opinion for or against
> >
> > Given that to date the previous times this has been raised and
> > presented
> > there was insufficient interest or support from the group I haven't
> > written this up as a formal proposal - just as a description as to
> > what
> > is involved. There are full examples of the entire test case set
> > online
> > at http://interop.cryptsoft.com/kmip_uc/ showing the JSON and XML
> > representation of each request and response message (and the end of
> > each time step where it is displayed in a range of formats).
> >
> > This isn't a proposal for a concept - this is actual documentation
> > of
> > something which has been implemented in multiple products and is in
> > production use in multiple organisations.
> >
> > If there is enough interest expressed I will create separate
> > proposals
> > or a single proposal for review and then a ballot.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
> The information contained in this electronic mail transmission
> may be privileged and confidential, and therefore, protected
> from disclosure. If you have received this communication in
> error, please notify us immediately by replying to this
> message and deleting it from your computer without copying
> or disclosing it.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
>
