Re: [wpkops] Preliminary Next Version of Browser Behavior Draft
i-barreira@izenpe.net Mon, 09 June 2014 08:29 UTC
Return-Path: <i-barreira@izenpe.net>
X-Original-To: wpkops@ietfa.amsl.com
Delivered-To: wpkops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 067AD1A0012 for <wpkops@ietfa.amsl.com>; Mon, 9 Jun 2014 01:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] 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 NP9C91sJh6Jy for <wpkops@ietfa.amsl.com>; Mon, 9 Jun 2014 01:29:06 -0700 (PDT)
Received: from ektmail2iron2.euskaltel.es (ektmail2iron2.euskaltel.es [212.142.144.26]) by ietfa.amsl.com (Postfix) with ESMTP id 51ABD1A001E for <wpkops@ietf.org>; Mon, 9 Jun 2014 01:29:05 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEEADZvlVPUNwh3/2dsb2JhbABZyHEBgSd1hAMBAQEEMAwBNQcMBAIBCBEEAQEBCgYXAQYBRQkIAgUSCIg+AclKF447HRQHBoMlgRYBA5ohk0WDPg
X-IPAS-Result: AqEEADZvlVPUNwh3/2dsb2JhbABZyHEBgSd1hAMBAQEEMAwBNQcMBAIBCBEEAQEBCgYXAQYBRQkIAgUSCIg+AclKF447HRQHBoMlgRYBA5ohk0WDPg
X-IronPort-AV: E=Sophos;i="4.98,1001,1392159600"; d="scan'208";a="165382584"
Received: from ektmail2mta2.euskaltel.es (HELO correo.euskaltel.es) ([212.55.8.119]) by ektmail2iron2.euskaltel.es with ESMTP; 09 Jun 2014 10:13:06 +0200
Received: from ejlp024.ejgv ([62.99.63.247]) by ektmail2mta2.euskaltel.es (Sun Java System Messaging Server 6.2-9.09 (built Jan 8 2008)) with ESMTP id <0N6W000E47KFQVL0@ektmail2mta2.euskaltel.es> for wpkops@ietf.org; Mon, 09 Jun 2014 10:29:03 +0200 (MEST)
Received: from afe02.ejsarea.net (afe02 [10.200.192.15]) by ejlp024.ejgv (8.13.1/8.13.1) with ESMTP id s598T3oC025278; Mon, 09 Jun 2014 10:29:03 +0200
Received: from AEX06.ejsarea.net ([10.200.198.17]) by afe02.ejsarea.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 09 Jun 2014 10:29:02 +0200
Date: Mon, 09 Jun 2014 10:29:01 +0200
From: i-barreira@izenpe.net
In-reply-to: <003701cf81b7$d0cb5ae0$726210a0$@digicert.com>
To: ben@digicert.com, bruce.morton@entrust.com
Message-id: <763539E260C37C46A0D6B340B5434C3B09939A2F@AEX06.ejsarea.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: quoted-printable
Content-class: urn:content-classes:message
Thread-topic: [wpkops] Preliminary Next Version of Browser Behavior Draft
Thread-index: AQHAGq9YUAUY845vOYYDLXX689oZPAIbE3NYATl0SmABw3ilUgIjEPfBm0lfIVCABAsYEA==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <001901cf6ec2$376461b0$a62d2510$@digicert.com> <059501cf79f0$69ba9060$3d2fb120$@digicert.com> <538F795F.3020008@mozilla.org> <5B68A271B9C97046963CB6A5B8D6F62CE819DE1D@SOTTEXCH11.corp.ad.entrust.com> <53907A4C.7070307@mozilla.org> <003701cf81b7$d0cb5ae0$726210a0$@digicert.com>
X-OriginalArrivalTime: 09 Jun 2014 08:29:02.0604 (UTC) FILETIME=[DE7084C0:01CF83BC]
Archived-At: http://mailarchive.ietf.org/arch/msg/wpkops/kyD_4CK-koDZBDoUSIn8lFwdEsE
Cc: wpkops@ietf.org, gerv@mozilla.org, tim.moses@entrust.com
Subject: Re: [wpkops] Preliminary Next Version of Browser Behavior Draft
X-BeenThere: wpkops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <wpkops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wpkops>, <mailto:wpkops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wpkops/>
List-Post: <mailto:wpkops@ietf.org>
List-Help: <mailto:wpkops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wpkops>, <mailto:wpkops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 08:29:09 -0000
Hi Ben, The current text of the trust models document already identifies the way a browser and a root store provider work together but not the relation with the crypto libraries. I don´t understand your question exactly because I don´t see why these libraries are of interest for a trust model. Do you mean that a trust model can differ depending on which library is used? The trust model document is more on a "functional" view than a technical one. I need more clarification on what you think to be added Regards Iñigo Barreira Responsable del Área técnica i-barreira@izenpe.net 945067705 ERNE! Baliteke mezu honen zatiren bat edo mezu osoa legez babestuta egotea. Mezua badu bere hartzailea. Okerreko helbidera heldu bada (helbidea gaizki idatzi, transmisioak huts egin) eman abisu igorleari, korreo honi erantzuna. KONTUZ! ATENCION! Este mensaje contiene informacion privilegiada o confidencial a la que solo tiene derecho a acceder el destinatario. Si usted lo recibe por error le agradeceriamos que no hiciera uso de la informacion y que se pusiese en contacto con el remitente. -----Mensaje original----- De: Ben Wilson [mailto:ben@digicert.com] Enviado el: viernes, 06 de junio de 2014 20:48 Para: Barreira Iglesias, Iñigo; bruce.morton@entrust.com CC: wpkops@ietf.org; 'Gervase Markham'; 'Tim Moses' Asunto: RE: [wpkops] Preliminary Next Version of Browser Behavior Draft Iñigo and Bruce, Perhaps we should revise the Trust Model document to describe how browser, root store, and cryptolibrary are related? In addressing Gerv's comments, I am thinking of starting with the following "This document reviews the current processing behaviors of cryptolibraries, and the browsers they support, with respect to SSL/TLS session establishment between a server and a browser, ..." or something along those lines. Thoughts? Thanks, Ben >-----Original Message----- >From: wpkops [mailto:wpkops-bounces@ietf.org] On Behalf Of Gervase Markham >Sent: Thursday, June 5, 2014 8:10 AM >To: Tim Moses; ben@digicert.com >Cc: wpkops@ietf.org >Subject: Re: [wpkops] Preliminary Next Version of Browser Behavior Draft > >On 05/06/14 14:37, Tim Moses wrote: >> Hi Ben. We want to move this document to WG draft status. Do you >> want to address Gerv's comments before we hold a ballot? I suggest we >> do that. > >Again, apologies for lack of knowledge of the process, but: the doc is full of "to be expanded", > "we plan to..." etc. So there will be lots of further change. Is that what "Draft" means? > >My two examples were two of many; they were actually given to try and get clarity on the >purpose and goals of the document. If that's written up somewhere, do point me to it. :-) > >Gerv > >
- [wpkops] Preliminary Next Version of Browser Beha… Ben Wilson
- Re: [wpkops] Preliminary Next Version of Browser … Ben Wilson
- Re: [wpkops] Preliminary Next Version of Browser … i-barreira
- Re: [wpkops] Preliminary Next Version of Browser … Gervase Markham
- Re: [wpkops] Preliminary Next Version of Browser … Tim Moses
- Re: [wpkops] Preliminary Next Version of Browser … Gervase Markham
- Re: [wpkops] Preliminary Next Version of Browser … Tim Moses
- Re: [wpkops] Preliminary Next Version of Browser … Ben Wilson
- Re: [wpkops] Preliminary Next Version of Browser … Ben Wilson
- Re: [wpkops] Preliminary Next Version of Browser … Tim Moses
- Re: [wpkops] Preliminary Next Version of Browser … i-barreira
- Re: [wpkops] Preliminary Next Version of Browser … i-barreira
- Re: [wpkops] Preliminary Next Version of Browser … Ben Wilson
- Re: [wpkops] Preliminary Next Version of Browser … i-barreira
- Re: [wpkops] Preliminary Next Version of Browser … Ben Wilson
- Re: [wpkops] Preliminary Next Version of Browser … Rick Andrews
- Re: [wpkops] Preliminary Next Version of Browser … Ben Wilson
- Re: [wpkops] Preliminary Next Version of Browser … Stephen Kent
- Re: [wpkops] Preliminary Next Version of Browser … Ben Wilson