Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Transport Layer Security (TLS) Authorization Using Digital Transmission Content Protection (DTCP) Certificates (RFC7562)

IP.com Disclosure Number: IPCOM000242380D
Original Publication Date: 2015-Jul-01
Included in the Prior Art Database: 2015-Jul-10
Document File: 30 page(s) / 33K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Thakore: AUTHOR


The Transport Layer Security (TLS) protocol (see TLS 1.0 [RFC2246], TLS 1.1 [RFC4346], and 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 allows the client and server to determine the type of protected data to exchange based on the authorization information received in the extensions.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Independent Submission                                        D. Thakore Request for Comments: 7562                                     CableLabs Category: Informational                                        July 2015 ISSN: 2070-1721

            Transport Layer Security (TLS) Authorization Using       Digital Transmission Content Protection (DTCP) Certificates


   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 RFC 5878.  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 RFC 4680.  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 document is not an Internet Standards Track specification; it is    published for informational purposes.

   This is a contribution to the RFC Series, independently of any other    RFC stream.  The RFC Editor has chosen to publish this document at    its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7562.

Thakore                       Informational                     [Page 1]
 RFC 7562                   TLS Auth Using DTCP                 July 2015

 Copyright Notice

   Copyright (c) 2015 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 ....................................................3

      1.1. Applicability Statement ....................................3