Original text:
HTTP Signing signature header <del> OAuth PoP key proof authentication header </del> Additional proofing methods are defined by IANA. All key binding methods used by this specification MUST cover all The verifier MUST validate the signature against the expected key of the signer. <del> 7.3.5. This method is indicated by "oauthpop" in the "proof" field.  The signer creates an HTTP Authorization PoP header as described in I- D.ietf-oauth-signed-http-request section 4, with the following additional requirements: The "at" (access token) field MUST be omitted unless this method is being used in conjunction with an access token as in use- access-token.  [[ See issue #112 [47] ]] The "b" (body hash) field MUST be calculated and included, if the message includes an entity body (such as a PUT or PATCH request). All components of the URL MUST be calculated and included, including query parameters "q", path "p", and host "u". The "m" (method) field MUST be included In this example, the request message body is the following JSON object The JOSE header for the PoP token is the following: After calculating the hashes for the body, headers, and URL components, the JWS Payload is the following: This leads to the following HTTP message request: [[ See issue #113 [48] ]] The verifier MUST parse the JWS object of the PoP header.  The verifier MUST validate the signature of the header against the expected key of the signer.  The verifier MUST ensure that all required parts of the message are covered by the signature.  The verifier MUST ensure that all components of the signature contain correct values. </del> 8. GNAP provides a rich structure for describing the protected resources [45] https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/109 [46] https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/110 <del> [47] https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/112 [48] https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/113 </del>

Reviewer comments:
remove OAuth DPoP binding. Described why on IETF mailing list: OAuth PoP: expired draft, due to be replaced with new draft based on HTTP Message Signatures. Also closing and
:heavycheckmark: Deploy Preview for gnap-core-protocol-editors-draft ready! :hammer: Explore the source changes: a47cdeabae554f3636d63a0ce8e0f8b52ff53693 :mag: Inspect the deploy log: :sunglasses: Browse the preview:
Removed autoindent in my editor to fix the issue
OAuth Proof of Possession (PoP): Editor's note: This is a stale draft from the OAuth working group, but it does at least provide some basic functionality for protecting HTTP messages with a signature. This work is likely to be subsumed by the general-purpose HTTP message signature mechanism in Section 8.5.
OAuth Proof of Possession (PoP): Editor's note: This is in contradiction to the referenced spec which makes this field mandatory.

Revised text:
HTTP Signing signature header  Additional proofing methods are defined by IANA. All key binding methods used by this specification MUST cover all The verifier MUST validate the signature against the expected key of the signer.  8. GNAP provides a rich structure for describing the protected resources [45] https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/109 [46] https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/110