IETF Logo Mail Archive

Re: Embedded certificate image

"Timothy J. Miller" <tmiller@mitre.org> Fri, 31 July 2009 17:34 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 7D3C33A6D6E for <ietfarch-pkix-archive@core3.amsl.com>; Fri, 31 Jul 2009 10:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level:
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 6JxbTQSPJznG for <ietfarch-pkix-archive@core3.amsl.com>; Fri, 31 Jul 2009 10:34:35 -0700 (PDT)
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 B34BD3A6D92 for <pkix-archive@ietf.org>; Fri, 31 Jul 2009 10:33:49 -0700 (PDT)
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 n6VGvRsP093471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jul 2009 09:57:27 -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 n6VGvRbq093470; Fri, 31 Jul 2009 09:57:27 -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 smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n6VGvFup093457 for <ietf-pkix@imc.org>; Fri, 31 Jul 2009 09:57:25 -0700 (MST) (envelope-from tmiller@mitre.org)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n6VGvEmH018308 for <ietf-pkix@imc.org>; Fri, 31 Jul 2009 12:57:15 -0400
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n6VGvE9s018305; Fri, 31 Jul 2009 12:57:14 -0400
Received: from [172.31.17.57] (172.31.17.57) by imchub2.MITRE.ORG (129.83.29.74) with Microsoft SMTP Server (TLS) id 8.1.375.2; Fri, 31 Jul 2009 12:57:14 -0400
Message-ID: <4A732267.2040204@mitre.org>
Date: Fri, 31 Jul 2009 11:57:11 -0500
From: "Timothy J. Miller" <tmiller@mitre.org>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Santosh Chokhani <SChokhani@cygnacom.com>
CC: Stefan Santesson <stefan@aaa-sec.com>, ietf-pkix <ietf-pkix@imc.org>
Subject: Re: Embedded certificate image
References: <4A71BD2B.60606@mitre.org> <C697B3BD.3A6E%stefan@aaa-sec.com> <FAD1CF17F2A45B43ADE04E140BA83D48C73CD1@scygexch1.cygnacom.com> <4A7203A6.20903@mitre.org> <FAD1CF17F2A45B43ADE04E140BA83D48C73CF8@scygexch1.cygnacom.com> <4A720A76.8010107@mitre.org> <FAD1CF17F2A45B43ADE04E140BA83D48C73CFE@scygexch1.cygnacom.com>
In-Reply-To: <FAD1CF17F2A45B43ADE04E140BA83D48C73CFE@scygexch1.cygnacom.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha1"; boundary="------------ms030407070107010104000405"
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>

Santosh Chokhani wrote:

> RFC says "The relationship between the subject organization and the
> subject
>    organization logotype, and the relationship between the issuer and
>    either the issuer organization logotype or the community logotype,
>    are relationships asserted by the issuer."
> 
> It tends to imply that the logotype is predefined data and not in the
> certificate request payload.

I'd feel better if it were explicit that the subject logotype is 
provided by the issuer.

As it is, I think it can be read either way.  The issuer asserts 
everything in the cert, after all, but it didn't create it all; much was 
provided by the applicant.

-- Tim

v2.46.0 | Report a Bug | By Email | System Status