Transport Layer Security (TLS) Authorization Using DTCP Certificate
draft-dthakore-tls-authz-07
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2014-11-11
(latest revision 2014-07-30)
|
|
Stream |
|
ISE
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
IETF conflict review |
|
conflict-review-dthakore-tls-authz |
| Stream |
ISE state
|
|
In ISE Review
Awaiting Reviews
|
|
Consensus Boilerplate |
|
Unknown
|
|
Document shepherd |
|
Nevil Brownlee
|
|
Shepherd write-up |
|
Show
(last changed 2014-10-30)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
"Nevil Brownlee" <rfc-ise@rfc-editor.org>
|
| IANA |
IANA review state |
|
IANA OK - Actions Needed
|
|
IANA action state |
|
None
|
Transport Layer Security D. Thakore
Internet-Draft CableLabs
Intended status: Informational July 2014
Expires: December 31, 2014
Transport Layer Security (TLS) Authorization Using DTCP Certificate
draft-dthakore-tls-authz-07
Abstract
This document specifies the use of Digital Transmission Content
Protection (DTCP) certificates as an authorization data type in the
authorization extension for the Transport Layer Security (TLS)
Protocol. This is in accordance with the guidelines for
authorization extensions as specified in [RFC5878]. As with other
TLS extensions, this authorization data can be included in the client
and server Hello messages to confirm that both parties support the
desired authorization data types. If supported by both the client
and the server, DTCP certificates are exchanged in the supplemental
data TLS handshake message as specified in RFC4680. This
authorization data type extension is in support of devices containing
DTCP certificates, issued by the Digital Transmission Licensing
Administrator [DTLA].
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 December 31, 2014.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
Thakore Expires December 31, 2014 [Page 1]
Internet-Draft TLS Auth Using DTCP July 2014
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Applicability Statement . . . . . . . . . . . . . . . . . 3
1.2. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Overview of DTCP Certificates . . . . . . . . . . . . . . 3
2.2. Overview of Supplemental Data handshake . . . . . . . . . 4
2.3. Overview of authorization extensions . . . . . . . . . . . 5
2.4. Overview of supplemental data usage for authorization . . 6
3. DTCP Authorization Data Format . . . . . . . . . . . . . . . . 6
3.1. DTCP Authorization Type . . . . . . . . . . . . . . . . . 6
3.2. DTCP Authorization Data . . . . . . . . . . . . . . . . . 6
3.3. Usage rules for clients to exchange DTCP Authorization data 7
3.4. Usage rules for servers to exchange DTCP Authorization data 8
3.5. TLS message exchange with dtcp_authz_data . . . . . . . . 8
3.6. Alert Messages . . . . . . . . . . . . . . . . . . . . . . 9
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . . 11
7.2. Informative References . . . . . . . . . . . . . . . . . . 12
Appendix A. Additional Stuff . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
The Transport Layer Security (TLS) protocol (TLS1.0 [RFC2246], TLS1.1
[RFC4346], TLS1.2 [RFC5246]) is being used in an ever increasing
variety of operational environments, the most common among which is
its use in securing HTTP traffic ([RFC2818]). [RFC5878] introduces
extensions that enable TLS to operate in environments where
authorization information needs to be exchanged between the client
and the server before any protected data is exchanged. The use of
these TLS authorization extensions is especially attractive since it
Show full document text