IETF Logo Mail Archive

Re: Long Name Requirements

Russ Housley <housley@vigilsec.com> Mon, 23 February 2009 15:39 UTC

Return-Path: <owner-ietf-pkix@mail.imc.org>
X-Original-To: ietfarch-pkix-archive@core3.amsl.com
Delivered-To: ietfarch-pkix-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96EDD28C142 for <ietfarch-pkix-archive@core3.amsl.com>; Mon, 23 Feb 2009 07:39:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.044
X-Spam-Level:
X-Spam-Status: No, score=-102.044 tagged_above=-999 required=5 tests=[AWL=-0.248, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 bbJ9cKDj4DTR for <ietfarch-pkix-archive@core3.amsl.com>; Mon, 23 Feb 2009 07:39:54 -0800 (PST)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 6F62D28C149 for <pkix-archive@ietf.org>; Mon, 23 Feb 2009 07:39:54 -0800 (PST)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n1NFIfHn095380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Feb 2009 08:18:41 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n1NFIfsb095379; Mon, 23 Feb 2009 08:18:41 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n1NFIU4m095367 for <ietf-pkix@imc.org>; Mon, 23 Feb 2009 08:18:40 -0700 (MST) (envelope-from housley@vigilsec.com)
Message-Id: <200902231518.n1NFIU4m095367@balder-227.proper.com>
Received: (qmail 1865 invoked by uid 0); 23 Feb 2009 15:18:27 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (96.255.144.212) by woodstock.binhost.com with SMTP; 23 Feb 2009 15:18:27 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 23 Feb 2009 10:06:30 -0500
To: egulacti@uekae.tubitak.gov.tr, ietf-pkix@imc.org
From: Russ Housley <housley@vigilsec.com>
Subject: Re: Long Name Requirements
In-Reply-To: <20090223134310.1C3482258026@postaci.uekae.tubitak.gov.tr>
References: <20090223134310.1C3482258026@postaci.uekae.tubitak.gov.tr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ietf-pkix@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>

Characters or octets?

At 08:41 AM 2/23/2009, egulacti@uekae.tubitak.gov.tr wrote:

>Hi,
>
>I have read through the PKIX mailing list archives to find a method for
>using name components longer than 64 characters in the Subject field of an
>X.509 v3 certificate. Unfortunately I could not find a solution which
>satisfies RFC 5280 (3280) by using standard CN, Title, O or OU components.
>
>Now I plan to use a custom attribute-value pair in the Subject field. Is
>there any widely used OID for really long names in the Subject field? I
>need to put full company titles, up to 500 characters long, in the Subject
>field.
>
>Regards,
>
>Ersin

v2.23.0 | Report a Bug | By Email