Transport Layer Security (TLS) Authorization Using DTCP Certificate
draft-dthakore-tls-authz-02
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Darshak Thakore
|
|
Last updated |
|
2013-01-23
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
IETF conflict review |
|
conflict-review-dthakore-tls-authz |
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Transport Layer Security D. Thakore
Internet-Draft CableLabs
Intended status: Informational January 2013
Expires: July 03, 2013
Transport Layer Security (TLS) Authorization Using DTCP Certificate
draft-dthakore-tls-authz-02
Abstract
This document specifies the use of DTCP certificate as an
authorization extension in the Transport Layer Security Handshake
Protocol, according to guidelines in RFC 5878. Extensions carried in
the client and server Hello messages confirm that both parties
support the desired authorization data types. Then if supported by
both the client and server, DTCP certificates are exchanged in the
supplemental data handshake TLS handshake message as specified in
RFC4680.
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 July 03, 2013.
Copyright Notice
Copyright (c) 2013 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.
Table of Contents
1. Introduction
1.1. Use Case for using DTCP Certificates
1.2. Conventions
2. Overview
2.1. Overview of DTCP Certificates
2.2. Overview of Supplemental Data handshake
2.3. Overview of authorization extensions
2.4. Overview of supplemental data usage for authorization
3. DTCP Authorization Data Format
3.1. DTCP Authorization Type
3.2. DTCP Authorization Data
3.3. Usage rules for clients to exchange DTCP Authorization data
3.4. Usage rules for servers to exchange DTCP Authorization data
3.5. Alert Messages
4. Acknowledgements
5. IANA Considerations
6. Security Considerations
7. References
7.1. Normative References
7.2. Informative References
Appendix A. Additional Stuff
Author's Address
Transport Layer Security D. Thakore
Internet-Draft CableLabs
Intended status: Informational January 2013
Expires: July 03, 2013
Transport Layer Security (TLS) Authorization Using DTCP Certificate
draft-dthakore-tls-authz-02
Abstract
This document specifies the use of DTCP certificate as an
authorization extension in the Transport Layer Security Handshake
Protocol, according to guidelines in RFC 5878. Extensions carried in
the client and server Hello messages confirm that both parties
support the desired authorization data types. Then if supported by
both the client and server, DTCP certificates are exchanged in the
supplemental data handshake TLS handshake message as specified in
RFC4680.
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 July 03, 2013.
Copyright Notice
Copyright (c) 2013 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.
1. Introduction
The Transport Layer Security (TLS) protocol (TLS1.0 [RFC2246], TLS1.1
Show full document text