Register http headers for TIGRESS draft

[dimmyvi]

Please confirm that:

• You have read and understood the requirements for registration.
• [X ] You have checked the registry and found no current value that meets your needs.
• Your specification reference URL is stable; ideally, managed by a widely-recognised standards development organisation (e.g., published as an RFC). Otherwise, please give additional information below.

If so, please provide the details of your request below.

• Field name: Mailbox-Request-ID

• Status: permanent

• Specification document(s): https://datatracker.ietf.org/doc/charter-ietf-tigress/

• Comments: Mailbox Request Identifier for TIGRESS IETF draft to track requests and help recognize duplicate requests

• Field name: Mailbox-Device-Claim

• Status: permanent

• Specification document(s): https://datatracker.ietf.org/doc/charter-ietf-tigress/

• Comments: Mailbox Device Claim for TIGRESS IETF draft to bind mobile devices to a mailbox

• Field name: Mailbox-Device-Attestation

• Status: permanent

• Specification document(s): https://datatracker.ietf.org/doc/charter-ietf-tigress/

• Comments: Mailbox Device Attestation for TIGRESS IETF draft to proof authenticity and validity of the content to be stored in a new mailbox

Any additional information (this will not be included in the registry)?

[mnot]

I'll leave this open until the drafts are available and stable; we can start the registration process when you get to IETF LC.