Re: [pkix] I-D Action:draft-ietf-pkix-new-asn1-07.txt

Stefan Santesson <stefan@aaa-sec.com> Tue, 01 September 2009 00:49 UTC

Return-Path: <stefan@aaa-sec.com>
X-Original-To: pkix@core3.amsl.com
Delivered-To: pkix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2DD03A6EDE for <pkix@core3.amsl.com>; Mon, 31 Aug 2009 17:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.968
X-Spam-Level:
X-Spam-Status: No, score=-3.968 tagged_above=-999 required=5 tests=[AWL=2.078, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 eR19sosv+gHK for <pkix@core3.amsl.com>; Mon, 31 Aug 2009 17:49:57 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 21B283A6A93 for <pkix@ietf.org>; Mon, 31 Aug 2009 17:49:56 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.114]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n810o6So049748 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-pkix@imc.org>; Mon, 31 Aug 2009 17:50:08 -0700 (MST) (envelope-from stefan@aaa-sec.com)
Received: (qmail 536 invoked from network); 31 Aug 2009 23:45:18 -0000
Received: from s34.loopia.se (HELO s24.loopia.se) ([194.9.94.70]) (envelope-sender <stefan@aaa-sec.com>) by s87.loopia.se (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for <ietf-pkix@imc.org>; 31 Aug 2009 23:45:18 -0000
Received: (qmail 89211 invoked from network); 31 Aug 2009 23:45:09 -0000
Received: from 213-64-142-97-no153.business.telia.com (HELO [192.168.1.4]) (stefan@fiddler.nu@[213.64.142.97]) (envelope-sender <stefan@aaa-sec.com>) by s24.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <phoffman@imc.org>; 31 Aug 2009 23:45:09 -0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Tue, 01 Sep 2009 01:45:08 +0200
From: Stefan Santesson <stefan@aaa-sec.com>
To: Paul Hoffman <phoffman@imc.org>, Sean Turner <turners@ieca.com>, ietf-pkix@imc.org
Message-ID: <C6C22D24.43DF%stefan@aaa-sec.com>
Thread-Topic: [pkix] I-D Action:draft-ietf-pkix-new-asn1-07.txt
Thread-Index: AcoqlRJcZmxB73CCH0arQRbCe8wEbw==
In-Reply-To: <p06240808c6c1d5f72291@[10.20.30.158]>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [pkix] I-D Action:draft-ietf-pkix-new-asn1-07.txt
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2009 00:49:58 -0000

On a second thought I think I agree with Paul.

The OID error is unfortunate, but the ASN.1 document is not the place to
correct it.

/Stefan


On 09-08-31 9:39 PM, "Paul Hoffman" <phoffman@imc.org> wrote:

> At 3:10 PM -0400 8/31/09, Sean Turner wrote:
>> During the updates to RFC 3281 it was noted that the wrong OID was used for
>> id-at-clearance.  We fixed this in draft-ietf-pkix-3281bis.  I would like to
>> make sure we incorporate the same fix in draft-ietf-pkix-new-asn1.  If we
>> don't, then we'll need to do another ID that incorporates this one change in
>> an '02 ASN.1 module.  What I'm proposing is that make the following change:
>> 
>> OLD:
>> 
>> id-at-clearance              OBJECT IDENTIFIER ::=
>>              { joint-iso-ccitt(2) ds(5) module(1)
>>                selected-attribute-types(5) clearance (55) }
>> 
>> NEW:
>> 
>>  id-at-clearance              OBJECT IDENTIFIER ::= {
>>      joint-iso-ccitt(2) ds(5) attributeType(4) clearance (55) }
>> 
>>    -- Uncomment the following declaration and comment the above line if
>>    -- using the id-at-clearance attribute as defined in [RFC3281]
>> 
>>    --  id-at-clearance              OBJECT IDENTIFIER ::= {
>>    --    joint-iso-ccitt(2) ds(5) module(1) selected-attribute-types(5)
>>    --    clearance (55) }
> 
> draft-ietf-pkix-new-asn1 has a module for RFC 3281. Jim and I believe that the
> module in our draft matches RFC 3281 correctly.
> 
> We can add another module that reflects draft-ietf-pkix-3281update-05.txt
> (there is no draft-ietf-pkix-3281bis). However, we do not have any Internet
> Drafts in draft-ietf-pkix-new-asn1, and I personally think that it is unwise
> for us to add one at this late state. We could also wait for
> draft-ietf-pkix-3281update-05.txt to be published as an RFC and add a module
> for it to draft-ietf-pkix-new-asn1.
> 
> Personally, I think it is wrong to change the module for RFC 3281 to change
> bits on the wire from what is represented in RFC 3281.
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix