Signed-Headers or Signed-Fields

[ioggstream]

Question

Signed-Headers is defined as a response header field. I was guessing whether:

• constraining its usage to Headers might hinder the ability to evolve this specification in conjunction with other content-coding != mice. Ongoing Digest work for example allows using Digest in trailers, while there's an open discussion in http on mid-stream trailers;
• constraining its usage to responses could inhibit the integration between this specification and other signature-based specifications, eg. Misleading name for headers parameter httpwg/http-extensions#1181

A more general approach (eg. Signed-Fields) could make sense.