[core] TLS Cached Info
"Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com> Sun, 18 December 2011 12:14 UTC
Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A24FA21F84DF for <core@ietfa.amsl.com>; Sun, 18 Dec 2011 04:14:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.948
X-Spam-Level:
X-Spam-Status: No, score=-105.948 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5rAIaExjf2Ge for <core@ietfa.amsl.com>; Sun, 18 Dec 2011 04:14:24 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8107421F84DB for <core@ietf.org>; Sun, 18 Dec 2011 04:14:23 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id pBICEJYZ016264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <core@ietf.org>; Sun, 18 Dec 2011 13:14:19 +0100
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id pBICEHZ2029417 for <core@ietf.org>; Sun, 18 Dec 2011 13:14:19 +0100
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Sun, 18 Dec 2011 13:14:17 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCBD7E.905ACFE1"
x-cr-puzzleid: {41F0EE4B-9EBB-4B69-A33A-81B445D2DBEF}
x-cr-hashedpuzzle: Agyg BtYW CUC0 CuGK CwiU C7Gi EAWH ED/n EU+k EsDo F2ZF H/wj IQeI JnK+ J8Qz KG5q; 1; YwBvAHIAZQBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {41F0EE4B-9EBB-4B69-A33A-81B445D2DBEF}; aABhAG4AbgBlAHMALgB0AHMAYwBoAG8AZgBlAG4AaQBnAEAAbgBzAG4ALgBjAG8AbQA=; Sun, 18 Dec 2011 12:16:10 GMT; VABMAFMAIABDAGEAYwBoAGUAZAAgAEkAbgBmAG8A
Content-class: urn:content-classes:message
Date: Sun, 18 Dec 2011 14:16:10 +0200
Message-ID: <999913AB42CC9341B05A99BBF358718DE38085@FIESEXC035.nsn-intra.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: TLS Cached Info
Thread-Index: Acy9ftOPDh5N9RDnSx20Whcxqspp1A==
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: core@ietf.org
X-OriginalArrivalTime: 18 Dec 2011 12:14:17.0466 (UTC) FILETIME=[907ECDA0:01CCBD7E]
Subject: [core] TLS Cached Info
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2011 12:14:24 -0000
Hi all, since you may not be subscribed to the TLS working group mailing list I thought I should share some information about ongoing activities with relevance to you. During the Taipei IETF TLS meeting to remove the functionality of conveying a public key fingerprint from draft-wouters-tls-oob-pubkey. I did that already during that meeting with the submission of http://tools.ietf.org/html/draft-wouters-tls-oob-pubkey-02. I had posted a mail about this the currently ongoing consensus call (see http://www.ietf.org/mail-archive/web/tls/current/msg08290.html). The removed functionality is not gone but rather part of a different document, namely http://tools.ietf.org/html/draft-ietf-tls-cached-info-10 >From the abstract of the draft: " This extension allows the TLS client to inform a server of cached information from previous TLS handshakes, allowing the server to omit sending cached static information to the client during the TLS handshake protocol exchange. " This functionality is useful for the constrained environments you guys are working on. Receiving feedback from this community would be great. If you get confused by all this TLS stuff drop me a mail. Ciao Hannes
- [core] TLS Cached Info Tschofenig, Hannes (NSN - FI/Espoo)