IETF Logo Mail Archive

Re: [sidr] upcoming wg calls

"Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov> Thu, 02 December 2010 22:36 UTC

Return-Path: <kotikalapudi.sriram@nist.gov>
X-Original-To: sidr@core3.amsl.com
Delivered-To: sidr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A458E3A6778 for <sidr@core3.amsl.com>; Thu, 2 Dec 2010 14:36:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 VXDC2XtdMRuq for <sidr@core3.amsl.com>; Thu, 2 Dec 2010 14:36:27 -0800 (PST)
Received: from smtp.nist.gov (rimp2.nist.gov [129.6.16.227]) by core3.amsl.com (Postfix) with ESMTP id E54543A6765 for <sidr@ietf.org>; Thu, 2 Dec 2010 14:36:25 -0800 (PST)
Received: from WSXGHUB2.xchange.nist.gov (wsxghub2.nist.gov [129.6.18.19]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id oB2MbX67021767; Thu, 2 Dec 2010 17:37:33 -0500
Received: from MBCLUSTER.xchange.nist.gov ([fe80::41df:f63f:c718:e08]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Thu, 2 Dec 2010 17:37:07 -0500
From: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
To: Sandra Murphy <sandy@sparta.com>
Date: Thu, 02 Dec 2010 17:37:32 -0500
Thread-Topic: Re: [sidr] upcoming wg calls
Thread-Index: AcuScYJe7pbLbaYlRlamLH+UqMr9iw==
Message-ID: <D7A0423E5E193F40BE6E94126930C4930846326E4D@MBCLUSTER.xchange.nist.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: kotikalapudi.sriram@nist.gov
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] upcoming wg calls
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Dec 2010 22:36:28 -0000

I support the last call of the following WG documents.

draft-ietf-sidr-roa-format-10
 draft-ietf-sidr-rpki-rtr-02
 draft-ietf-sidr-keyroll-04
 draft-ietf-sidr-res-certs-20
 draft-ietf-sidr-repos-struct-06
 draft-ietf-sidr-rescerts-provisioning-09
 draft-ietf-sidr-rpki-algs-04
 draft-ietf-sidr-rpki-manifests-09
 draft-ietf-sidr-roa-validation-10
 draft-ietf-sidr-signed-object-01
 draft-ietf-sidr-ta-06
 draft-ietf-sidr-arch-11

I support the adoption of the following items.

draft-rgaglian-sidr-algorithm-agility-00
draft-ymbk-ghostbusters-01
draft-ymbk-rpki-origin-ops-00

This draft is not ready for last call: draft-ietf-sidr-pfx-validate
Please see comments:
http://www.ietf.org/mail-archive/web/sidr/current/msg02204.html
I also request that it be an Informational RFC (rather than a standards track RFC)
just as draft-ietf-sidr-roa-validation already is. 
Please see comment (my reasons explained):
http://www.ietf.org/mail-archive/web/sidr/current/msg02203.html

Sriram

v2.23.0 | Report a Bug | By Email