Subject: [TLS] Fwd: New Version Notification for draft-perrin-tls-tack-02.txt

From: Trevor Perrin <[email-masked]>
Date: Mon, 7 Jan 2013 12:06:33 -0800

Hi,

We submitted a new TACK draft.

No major changes - just some renaming and text cleanup:

 - renamed "TACK key" -> "TACK signing key", aka "TSK"
 - renamed "rollover" -> "overlapping pins / tacks"
 - renamed "accepted/rejected" -> "confirmed/contradicted"
 - renamed "well-formed" -> "valid"

 - changed to allow reserved bits in activation_flags
 - tweaked advice on expiration time
 - fixed advice on overlapping pins (60 days vs 30 days)
 - added advice on nonrevokable tacks

 - trimmed abstract and introduction, and pin activation
 - clarified that TLS key is in the "end-entity" certificate
 - clarified 5.2 TLS negotiation
 - clarified pin activation

Trevor

---------- Forwarded message ----------
From: <[email-masked]>
Date: Mon, Jan 7, 2013 at 12:01 PM
Subject: New Version Notification for draft-perrin-tls-tack-02.txt
To: [email-masked]

A new version of I-D, draft-perrin-tls-tack-02.txt
has been successfully submitted by Trevor Perrin and posted to the
IETF repository.

Filename:        draft-perrin-tls-tack
Revision:        02
Title:           Trust Assertions for Certificate Keys
Creation date:   2013-01-07
WG ID:           Individual Submission
Number of pages: 21
URL:
http://www.ietf.org/internet-drafts/draft-perrin-tls-tack-02.txt
Status:          http://datatracker.ietf.org/doc/draft-perrin-tls-tack
Htmlized:        http://tools.ietf.org/html/draft-perrin-tls-tack-02
Diff:            http://www.ietf.org/rfcdiff?url2=draft-perrin-tls-tack-02

Abstract:
   This document defines a TLS Extension that enables a TLS server to
   support "pinning" to a self-chosen signing key.  A client contacting
   a pinned host will require the server to present a signature from the
   signing key over the TLS server's public key.

The IETF Secretariat