HTTP Integrity Header
draft-hallambaker-httpintegrity-00

Abstract

The HTTP Integrity header provides a means of authenticating HTTP requests and responses using a Message Authentication Code (MAC). This document defines the HTTP integrity header and specifies its use to authenticate and verify specific parts of an HTTP message. the means by which the symmetric or asymmetric keys used to authenticate the messages is outside the scope of this document.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http:/⁠/⁠datatracker.ietf.org/⁠drafts/⁠current/⁠.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on April 03, 2013.

Copyright Notice

Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http:/⁠/⁠trustee.ietf.org/⁠license-⁠info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 1.1. Use in Web Services
• 1.1.1. Multiparty Transactions
• 1.1.2. End to End Authentication
• 1.2. User Authentication
• 2. Syntax and options
• 2.1. Attribute ticket=[base64(value)]
• 2.2. Attribute mac=[base64(value)]
• 2.3. Attribute content=[true|false]
• 2.4. Attribute status=[true|false]
• 2.5. Attribute start=[true|false]
• 2.6. Attribute header=[escaped(headers)]
• 3. Security Considerations
• 3.1. Data outside authentication scope is not authenticated
• 3.2. Truncated Hash Algorithms
• 3.3. Randomness of Secret Key
• 3.4. Weak Ciphers
• 4. IANA Considerations
• 5. References
• Author's Address

1. Introduction

1.1. Use in Web Services

1.1.1. Multiparty Transactions

1.1.2. End to End Authentication

1.2. User Authentication

2. Syntax and options

2.1. Attribute ticket=[base64(value)]

2.2. Attribute mac=[base64(value)]

2.3. Attribute content=[true|false]

2.4. Attribute status=[true|false]

2.5. Attribute start=[true|false]

2.6. Attribute header=[escaped(headers)]

3. Security Considerations

3.1. Data outside authentication scope is not authenticated

3.2. Truncated Hash Algorithms

3.3. Randomness of Secret Key

3.4. Weak Ciphers

4. IANA Considerations

5. References

Author's Address