IETF Logo Mail Archive

Long Name Requirements

egulacti@uekae.tubitak.gov.tr Mon, 23 February 2009 14:13 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 34F0D3A67EC for <ietfarch-pkix-archive@core3.amsl.com>; Mon, 23 Feb 2009 06:13:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.664
X-Spam-Level:
X-Spam-Status: No, score=-1.664 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_TR=0.935]
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 P4WZqJg2TDfh for <ietfarch-pkix-archive@core3.amsl.com>; Mon, 23 Feb 2009 06:13:25 -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 308BB3A69A7 for <pkix-archive@ietf.org>; Mon, 23 Feb 2009 06:13:21 -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 n1NDhPdg089560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Feb 2009 06:43:25 -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 n1NDhPcj089559; Mon, 23 Feb 2009 06:43:25 -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 postaci.uekae.tubitak.gov.tr (postaci.uekae.tubitak.gov.tr [193.140.74.8]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n1NDhDQe089547 for <ietf-pkix@imc.org>; Mon, 23 Feb 2009 06:43:24 -0700 (MST) (envelope-from egulacti@uekae.tubitak.gov.tr)
Received: from webmail.uekae.tubitak.gov.tr (hitit.uekae.tubitak.gov.tr [192.168.5.6]) by postaci.uekae.tubitak.gov.tr (UEKAE_MAIL_SERVER_V4) with ESMTP id 0F4CA2258026 for <ietf-pkix@imc.org>; Mon, 23 Feb 2009 15:43:09 +0200 (EET)
Received: from 193.140.71.1 (SquirrelMail authenticated user egulacti) by webmail.uekae.tubitak.gov.tr with HTTP; Mon, 23 Feb 2009 15:41:53 +0200 (EET)
Date: Mon, 23 Feb 2009 15:41:53 +0200
Subject: Long Name Requirements
From: egulacti@uekae.tubitak.gov.tr
To: ietf-pkix@imc.org
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-9"
X-Priority: 3 (Normal)
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Message-Id: <20090223134310.1C3482258026@postaci.uekae.tubitak.gov.tr>
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>

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