Re: draft-ietf-dnsext-dnssec-gost

Sean Turner <turners@ieca.com> Fri, 12 February 2010 19:22 UTC

Return-Path: <turners@ieca.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B61228C1DE for <ietf@core3.amsl.com>; Fri, 12 Feb 2010 11:22:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 MCR0ysT+Cq1q for <ietf@core3.amsl.com>; Fri, 12 Feb 2010 11:22:29 -0800 (PST)
Received: from smtp101.biz.mail.re2.yahoo.com (smtp101.biz.mail.re2.yahoo.com [68.142.229.215]) by core3.amsl.com (Postfix) with SMTP id 7716F28C1E0 for <ietf@ietf.org>; Fri, 12 Feb 2010 11:22:29 -0800 (PST)
Received: (qmail 20913 invoked from network); 12 Feb 2010 19:23:46 -0000
Received: from pool-96-241-8-5.washdc.east.verizon.net (turners@96.241.8.5 with plain) by smtp101.biz.mail.re2.yahoo.com with SMTP; 12 Feb 2010 11:23:46 -0800 PST
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
X-YMail-OSG: 5A.YBM4VM1ncfVplxfSX.rmdK1eQVCbvJOzCi_PJ1fB0yihNXDtYAg_af128c87fRr4juwnTcNSc6blBPbQ578JK1pyHlIkihF.fXjGvB22eY9xonxxu0eTzUB63cPGkd70uFFOOnAmHzSlrwI1T.i8vQg4Eo9DlR1BNkyLmYJG5mnU9n3F1wjF1OeLVDWahwwyKHwufxh2SQYAeL6P5Dm6Z5PDpnH6P6X7TFOTcPQX2qx_.Y0rBati4OYSMmEH2CxQ_AjQwg_tzQEw3rPTk7WO.PyLcP3YUd31Iw7GCd7aMytjnteAADZqmnJqp30EZSjIf8_OuyX6j04wbH0xfpF1vS.aUmWabI7tGMjxbzAvZXoJIl8VGRHhL.ra3BiVu29qFgceYPeW3m4ScfXuVu7ViqsksS.K8atWq7EqVmh.zgHM90HP1M3qN3xw8_66IQKDFe_bA
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4B75AAC1.5020709@ieca.com>
Date: Fri, 12 Feb 2010 14:23:45 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: draft-ietf-dnsext-dnssec-gost
References: <p06240806c799d87e7406@[128.89.89.170]> <4B74646F.3080904@ogud.com> <p06240805c79b294d87a8@[192.168.1.5]> <a06240800c79b554ba0e0@[10.31.200.127]>
In-Reply-To: <a06240800c79b554ba0e0@[10.31.200.127]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: iesg@iesg.org, Stephen Kent <kent@bbn.com>, Olafur Gudmundsson <ogud@ogud.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2010 19:22:30 -0000

Edward Lewis wrote:
> At 10:57 -0500 2/12/10, Stephen Kent wrote:
> 
>> If we look at what the CP developed in the SIDR WG for the RPKI says, the
>> answer is the IESG (going forward, after an initial set of algs are 
>> adopted
>> based on the SIDR WG process). In the IPSEC, TLS, and SMIME contexts, 
>> the WGs
>> themselves have made the decisions, which the IESG then approves by 
>> virtue of
>> the usual standards track RFC approval process. I do not believe that the
>> criteria have been documented uniformly across these WGs.
> 
> What is "CP?"

Certificate Policy: http://www.ietf.org/id/draft-ietf-sidr-cp-08.txt

spt