RFC 7562 on Transport Layer Security (TLS) Authorization Using Digital Transmission Content Protection (DTCP) Certificates
rfc-editor@rfc-editor.org Thu, 09 July 2015 22:39 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6CD51A1B3E for <ietf-announce@ietfa.amsl.com>; Thu, 9 Jul 2015 15:39:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h78lwSY5pVzT for <ietf-announce@ietfa.amsl.com>; Thu, 9 Jul 2015 15:39:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 5047C1A1B3D for <ietf-announce@ietf.org>; Thu, 9 Jul 2015 15:39:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8F393180206; Thu, 9 Jul 2015 15:36:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7562 on Transport Layer Security (TLS) Authorization Using Digital Transmission Content Protection (DTCP) Certificates
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150709223600.8F393180206@rfc-editor.org>
Date: Thu, 09 Jul 2015 15:36:00 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/REHgutYyNBk7zor52z_dpY8gVXk>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2015 22:39:40 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7562 Title: Transport Layer Security (TLS) Authorization Using Digital Transmission Content Protection (DTCP) Certificates Author: D. Thakore Status: Informational Stream: Independent Date: July 2015 Mailbox: d.thakore@cablelabs.com Pages: 15 Characters: 32576 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-dthakore-tls-authz-08.txt URL: https://www.rfc-editor.org/info/rfc7562 DOI: http://dx.doi.org/10.17487/RFC7562 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). INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC