Re: [CGA-EXT] Next steps

Roque Gagliano <roque@lacnic.net> Wed, 18 November 2009 14:07 UTC

Return-Path: <roque@lacnic.net>
X-Original-To: cga-ext@core3.amsl.com
Delivered-To: cga-ext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D98F23A6BC2 for <cga-ext@core3.amsl.com>; Wed, 18 Nov 2009 06:07:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level:
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599]
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 wMa3dcY5RWtc for <cga-ext@core3.amsl.com>; Wed, 18 Nov 2009 06:07:21 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [200.7.84.3]) by core3.amsl.com (Postfix) with ESMTP id A6AB93A6BAF for <cga-ext@ietf.org>; Wed, 18 Nov 2009 06:06:48 -0800 (PST)
Received: from [IPv6:2001:4300:abcd::225:ff:fe4b:94a8] (unknown [IPv6:2001:4300:abcd:0:225:ff:fe4b:94a8]) by mail.lacnic.net.uy (Postfix) with ESMTP id 7AC2E3084F4 for <cga-ext@ietf.org>; Wed, 18 Nov 2009 12:06:30 -0200 (UYST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
From: Roque Gagliano <roque@lacnic.net>
In-Reply-To: <4B03C4C7.2090708@it.uc3m.es>
Date: Wed, 18 Nov 2009 16:05:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <075252F1-D10D-4FFA-8EEE-C2D185DA5626@lacnic.net>
References: <4B03C4C7.2090708@it.uc3m.es>
To: cga-ext@ietf.org
X-Mailer: Apple Mail (2.1077)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck:
X-LACNIC.uy-MailScanner-From: roque@lacnic.net
Subject: Re: [CGA-EXT] Next steps
X-BeenThere: cga-ext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: CGA and SeND Extensions <cga-ext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/cga-ext>, <mailto:cga-ext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cga-ext>
List-Post: <mailto:cga-ext@ietf.org>
List-Help: <mailto:cga-ext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cga-ext>, <mailto:cga-ext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2009 14:07:25 -0000

Marcelo,

I would like to start the discussion on how the host should fetch the CRLs. This will serve as a base for a future I-D.

We have at least three options:

1) To specify the  "Certificate Revocation Solicitation /  Certificate Revocation Advertisement" messages just like in SEND to request certificates.

	Advantages:
		- The router could cache the CRLs, which will be the same ones for most of the hosts. More-over the certs and the CRL may be pre-loaded by the router which only needs to check for a new CRL before the "next update".
		- Lightweight implementation at the hosts.
	
	Disadvantages:
		- Need specification, probable changes to RFC 3971.

2) To use the default fetching mechanism at the CRL Distribution Points extension for each CA. Today the only mandatory fetching mechanism is RSYNC.
	Advantages:
		- no changes in the current specifications.

	Disadvantages:
		- need to implement RSYNC client in hosts.
		- no cache, the same CRL will be fetch by every host from the source. 

3) To modify the Certification Path Advertisement Message in the sense that every time a certificate is sent to the host, it will also include the CRL shown in its  CRL Distribution Points extension. So, you asked for a CERT, I send you both the CERT and the CRL (for signed with the same key).

What does the WG think?

Roque.

-------------------------------------------------------------
Roque Gagliano
LACNIC
roque@lacnic.net
GPG Fingerprint: E929 06F4 D8CD 2AD8 9365  DB72 9E4F 964A 01E9 6CEE