Re: [certid] open issue: wildcards in component fragments
Matt McCutchen <matt@mattmccutchen.net> Fri, 08 October 2010 01:16 UTC
Return-Path: <matt@mattmccutchen.net>
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 6995B3A6768 for <certid@core3.amsl.com>;
Thu, 7 Oct 2010 18:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level:
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032,
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 Abg39kHyW23P for
<certid@core3.amsl.com>; Thu, 7 Oct 2010 18:16:07 -0700 (PDT)
Received: from homiemail-a6.g.dreamhost.com (caiajhbdccah.dreamhost.com
[208.97.132.207]) by core3.amsl.com (Postfix) with ESMTP id C90B43A63D3 for
<certid@ietf.org>; Thu, 7 Oct 2010 18:16:07 -0700 (PDT)
Received: from homiemail-a6.g.dreamhost.com (localhost [127.0.0.1]) by
homiemail-a6.g.dreamhost.com (Postfix) with ESMTP id 8910859806C;
Thu, 7 Oct 2010 18:17:11 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=mattmccutchen.net; h=subject:from
:to:cc:in-reply-to:references:content-type:date:message-id
:mime-version:content-transfer-encoding; q=dns; s= mattmccutchen.net;
b=rvVO7wDxBDvLeLDWWw8gsX6qRSbG7GgLmdzV7eXldEv
pJKFUP0jFL+d3jjcK+Qg0oX49pKR/YA0VyfdOk8nwL48M5KGDnba3vZR5CD6VZu3
2Rdvmbdn/zesyLOZt0AIRofF2Dw534luweEq1eVG8rVHuZsUIa3XrJmECV9JJuK4 =
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=mattmccutchen.net;
h= subject:from:to:cc:in-reply-to:references:content-type:date
:message-id:mime-version:content-transfer-encoding; s= mattmccutchen.net;
bh=Q3RCxOrsaiuojuaDyTH4Vqh4E9Y=;
b=ImTbGITw5t 7+aJRRFATz/DotK3lMimJKYdfYsGACwujPzjN7iTCnY2tNFze27yBv9ISHCuRV+l
Cu6b8zpVvvs0wVaJWTH8KytRmt2RUmfucPJq4evDv/rKiSUn37qfrGT/56TGx/Ks
XWLvye+TeQyNvAmzWWQKD2UbJIZ0+eBmE=
Received: from [129.2.249.209] (ml2.student.umd.edu [129.2.249.209])
(Authenticated sender: matt@mattmccutchen.net) by
homiemail-a6.g.dreamhost.com (Postfix) with ESMTPA id 4587B598069;
Thu, 7 Oct 2010 18:17:11 -0700 (PDT)
From: Matt McCutchen <matt@mattmccutchen.net>
To: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <4CAE3AFF.9020804@stpeter.im>
References: <4CACEEBC.8010109@stpeter.im> <20101007125754.GA11638@eltex.net>
<4CAE3122.9080504@stpeter.im> <20101007211208.GA9771@eltex.net>
<4CAE3AFF.9020804@stpeter.im>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 07 Oct 2010 21:17:10 -0400
Message-ID: <1286500630.1912.43.camel@mattlaptop2.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.4
Content-Transfer-Encoding: 7bit
Cc: IETF cert-based identity <certid@ietf.org>
Subject: Re: [certid] open issue: wildcards in component fragments
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: Fri, 08 Oct 2010 01:16:09 -0000
On Thu, 2010-10-07 at 15:26 -0600, Peter Saint-Andre wrote: > The intended status of this document is BCP = Best Current Practice. > That "B" is in there for a reason. The question is: does allowing *oo > and f*o and foo* (and maybe even f*b*r) as wildcard fragments truly > represent a "best" current practice, or only "current" practice? It > doesn't strike me as a most excellent, effective, desirable, suitable, > appropriate, or useful practice, although I freely grant that it is in > common and general use at the present time. Is it? I have never seen a certificate with a wildcard that is not a whole label on a public web site. -- Matt
- [certid] open issue: wildcards in component fragm… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… ArkanoiD
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… ArkanoiD
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… Martin Rex
- Re: [certid] open issue: wildcards in component f… Matt McCutchen
- Re: [certid] open issue: wildcards in component f… Matt McCutchen
- Re: [certid] open issue: wildcards in component f… Martin Rex
- Re: [certid] open issue: wildcards in component f… Martin Rex
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… Martin Rex
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… Joe Orton
- Re: [certid] open issue: wildcards in component f… Matt McCutchen
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… Jeffrey A. Williams
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… Martin Rex
- Re: [certid] open issue: wildcards in component f… Matt McCutchen
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… Matt McCutchen
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… Martin Rex
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… =JeffH
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre
- Re: [certid] open issue: wildcards in component f… Jeffrey A. Williams
- Re: [certid] open issue: wildcards in component f… Martin Rex
- Re: [certid] open issue: wildcards in component f… Peter Saint-Andre