[certid] next steps for -tls-server-id-check ?
=JeffH <Jeff.Hodges@KingsMountain.com> Wed, 20 October 2010 17:06 UTC
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: certid@core3.amsl.com
Delivered-To: certid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id BAE2E3A6921 for <certid@core3.amsl.com>;
Wed, 20 Oct 2010 10:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.118
X-Spam-Level:
X-Spam-Status: No, score=-102.118 tagged_above=-999 required=5 tests=[AWL=0.147,
BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 DtnHzI7KzbiZ for
<certid@core3.amsl.com>; Wed, 20 Oct 2010 10:06:31 -0700 (PDT)
Received: from cpoproxy2-pub.bluehost.com (cpoproxy2-pub.bluehost.com
[67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id 5A4193A68D5 for
<certid@ietf.org>; Wed, 20 Oct 2010 10:06:31 -0700 (PDT)
Received: (qmail 20793 invoked by uid 0); 20 Oct 2010 17:08:04 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by
cpoproxy2.bluehost.com with SMTP; 20 Oct 2010 17:08:04 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com;
h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User;
b=NkIYtbMZaLE+WXuicWkp92JEpoBMAsYdgy9OnOzUCPzkZ+oBucwiCx7sPvNWDAQ6NjB2TDzC9VmbwzA6lMexp5ypJc91CJzGnTOgl77m0wP1/af9wbi7IrxRLui3cFBM;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.136.179]) by
box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69)
(envelope-from <Jeff.Hodges@KingsMountain.com>) id 1P8c8y-0003MM-93;
Wed, 20 Oct 2010 11:08:04 -0600
Message-ID: <4CBF21F4.6000008@KingsMountain.com>
Date: Wed, 20 Oct 2010 10:08:04 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com}
{sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Cc: IETF cert-based identity <certid@ietf.org>
Subject: [certid] next steps for -tls-server-id-check ?
X-BeenThere: certid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Representation and verification of identity in certificates
<certid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/certid>,
<mailto:certid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/certid>
List-Post: <mailto:certid@ietf.org>
List-Help: <mailto:certid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/certid>,
<mailto:certid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 17:06:32 -0000
So what are our next formal steps for -tls-server-id-check ? thanks, =JeffH
- [certid] next steps for -tls-server-id-check ? =JeffH
- Re: [certid] next steps for -tls-server-id-check ? Peter Saint-Andre
- Re: [certid] next steps for -tls-server-id-check ? Alexey Melnikov