[CHANNEL-BINDING] registration for channel binding unique prefix "tls-server-end-point"

Larry Zhu <lzhu@windows.microsoft.com> Wed, 11 June 2008 15:11 UTC

Return-Path: <channel-binding-bounces@ietf.org>
X-Original-To: channel-binding-archive@optimus.ietf.org
Delivered-To: ietfarch-channel-binding-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAD0D3A6A69; Wed, 11 Jun 2008 08:11:31 -0700 (PDT)
X-Original-To: channel-binding@core3.amsl.com
Delivered-To: channel-binding@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C4CF3A6AEA for <channel-binding@core3.amsl.com>; Tue, 10 Jun 2008 13:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hs-4SWy9MS8Q for <channel-binding@core3.amsl.com>; Tue, 10 Jun 2008 13:43:52 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 4C0F53A6AB3 for <channel-binding@ietf.org>; Tue, 10 Jun 2008 13:43:49 -0700 (PDT)
Received: from tk5-exhub-c103.redmond.corp.microsoft.com (157.54.88.96) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.1.251.2; Tue, 10 Jun 2008 13:44:12 -0700
Received: from TK5-EXMLT-W605V.wingroup.windeploy.ntdev.microsoft.com (157.54.18.79) by tk5-exhub-c103.redmond.corp.microsoft.com (157.54.88.96) with Microsoft SMTP Server id 8.1.240.5; Tue, 10 Jun 2008 13:44:07 -0700
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com ([fe80::8de9:51a2:cd62:f122]) by TK5-EXMLT-W605V.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.79]) with mapi; Tue, 10 Jun 2008 13:44:02 -0700
From: Larry Zhu <lzhu@windows.microsoft.com>
To: "channel-binding@ietf.org" <channel-binding@ietf.org>
Date: Tue, 10 Jun 2008 13:44:01 -0700
Thread-Topic: registration for channel binding unique prefix "tls-server-end-point"
Thread-Index: AcjLOraEMvTjzXJ1QFyjLKdOIoAVyQ==
Message-ID: <AB1E5627D2489D45BD01B84BD5B900460618301EF4@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 11 Jun 2008 08:11:30 -0700
Cc: "iana@iana.org" <iana@iana.org>, "Nicolas.Williams@sun.com" <Nicolas.Williams@sun.com>
Subject: [CHANNEL-BINDING] registration for channel binding unique prefix "tls-server-end-point"
X-BeenThere: channel-binding@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of channel binding IANA registry requests and specifications <channel-binding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/channel-binding>, <mailto:channel-binding-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/channel-binding>
List-Post: <mailto:channel-binding@ietf.org>
List-Help: <mailto:channel-binding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/channel-binding>, <mailto:channel-binding-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: channel-binding-bounces@ietf.org
Errors-To: channel-binding-bounces@ietf.org

Subject: Registration of TLS server end-point channel bindings
Channel binding unique prefix: tls-server-end-point
Channel binding type: end-point
Channel type: TLS
Published specification: none
Channel binding is secret: no
Description: The hash of the TLS server's end entity certificate as it
        appears, octet for octet, in the server's Certificate message
        (note that the Certificate message contains a certificate_list,
        the first element of which is the server's end entity
        certificate.  The hash function to be used is as follows: if the
        certificate's signature hash algorithm is either MD5 or SHA-1,
        then use SHA-256, otherwise use the certificate's signature hash
        algorithm.
        The reason for using a hash of the certificate is that some
        implementations need to track the channel binding of a TLS
        session in kernel-mode memory, which is often at a premium.
Intended usage: COMMON
Person and email address to contact for further information:
        Larry Zhu(lzhu@microsoft.com)
Owner/Change controller name and email address:
        Larry Zhu(lzhu@microsoft.com)
Expert reviewer name and contact information: Nicolas Williams
        (Nicolas.Williams@sun.com)
Note: This registration was initially authored by Nicolas Williams
        (Nicolas.Williams@sun.com).
_______________________________________________
CHANNEL-BINDING mailing list
CHANNEL-BINDING@ietf.org
https://www.ietf.org/mailman/listinfo/channel-binding