Re: Show support for HTTP Signatures at IETF

>The HTTP Message Signatures specification standardizes how you digitally
sign the content of HTTP Messages. Any authentication or authorization
protocol will depend on this specification (DID Auth HTTP Binding,
Authorization Capabilities for EDVs, DIDComm HTTP Binding).

I don't think this work is relevant to the DIDComm binding for HTTP.
DIDComm is transport-independent; its security can't depend on mechanisms
that are unique to one transport.



On Mon, Jan 20, 2020 at 11:29 AM Manu Sporny <msporny@digitalbazaar.com>
wrote:

> We need your help to advance one of the W3C CCG's work items[1] to go on
> the official standards track at the Internet Engineering Task Force
> (IETF) -- the standards setting body for the Internet. The deadline for
> helping is Jan 31st 2020 (in ~10 days).
>
> The IETF HTTP Working Group is considering the adoption of the HTTP
> Signatures specification as a work item. This specification is currently
> a W3C CCG work item (recently transferred from the W3C DVCG).
>
> This is very good news, because the W3C CCG depends on this eventually
> becoming an IETF Standard for one of the Authorization mechanisms used
> for Encrypted Data Vaults (ZCAP-LD) and the Authorization mechanism that
> some DID Ledgers might use (Veres One, for example).
>
> The HTTP Message Signatures specification standardizes how you digitally
> sign the content of HTTP Messages. Any authentication or authorization
> protocol will depend on this specification (DID Auth HTTP Binding,
> Authorization Capabilities for EDVs, DIDComm HTTP Binding).
>
> Here is the IETF HTTP WG Call for Adoption:
>
> https://lists.w3.org/Archives/Public/ietf-http-wg/2020JanMar/0002.html
>
> To note your support of the specification:
>
> 1. Go here and click "subscribe to this list":
>      https://lists.w3.org/Archives/Public/ietf-http-wg/
> 2. Verify your subscription by checking your email and clicking on the
>    link that is mailed to you.
> 3. Go here and click "respond to this message"
>
> https://lists.w3.org/Archives/Public/ietf-http-wg/2020JanMar/0002.html
> 4. Write an email stating:
>      4.1 That you support the adoption of the draft.
>      4.2 Why you support the adoption of the draft.
>      4.3 How you plan to make use the specification, either directly, or
>          indirectly (via someone else's software).
> 5. Set up an email filter to put all mail sent to ietf-http-wg@w3.org
>    into its own folder. The mailing list averages ~350 emails/month. You
>    can also leave the mailing list immediately after sending the email
>    above if that amount of email traffic is unacceptable to you.
>
> For an example of the type of email you could write, see this:
>
> https://lists.w3.org/Archives/Public/ietf-http-wg/2020JanMar/0018.html
>
> -- manu
>
> [1] https://github.com/w3c-ccg/http-signatures
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Veres One Decentralized Identifier Blockchain Launches
> https://tinyurl.com/veres-one-launches
>
>