[pkix] Update on Request for allocation of extended key purpose identifiers for SEND

Roque Gagliano <rogaglia@cisco.com> Fri, 24 September 2010 11:07 UTC

Return-Path: <rogaglia@cisco.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 3B6733A6B22 for <pkix@core3.amsl.com>; Fri, 24 Sep 2010 04:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.996
X-Spam-Level:
X-Spam-Status: No, score=-5.996 tagged_above=-999 required=5 tests=[AWL=-3.397, 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 JeTYUlCLtnN7 for <pkix@core3.amsl.com>; Fri, 24 Sep 2010 04:07:54 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 94D213A6A1A for <pkix@ietf.org>; Fri, 24 Sep 2010 04:07:52 -0700 (PDT)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao4FAKsjnEyQ/khM/2dsb2JhbACUQ417cacwnCuFQwSKOoJ+
X-IronPort-AV: E=Sophos;i="4.57,229,1283731200"; d="scan'208";a="10068056"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 24 Sep 2010 11:08:23 +0000
Received: from [144.254.21.40] ([144.254.21.40]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id o8OB8NQc018448 for <pkix@ietf.org>; Fri, 24 Sep 2010 11:08:23 GMT
From: Roque Gagliano <rogaglia@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 24 Sep 2010 13:08:33 +0200
References: <20100924105545.B53443A6B42@core3.amsl.com>
To: pkix@ietf.org
Message-Id: <C5C98452-AD4D-498E-AFE2-38F5A257594B@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [pkix] Update on Request for allocation of extended key purpose identifiers for SEND
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: Fri, 24 Sep 2010 11:07:57 -0000

Dear PKIX WG,

On a previous request from the authors of draft-ietf-csi-send-cert, three EKU values were allocated for SEND. (see message http://www.ietf.org/mail-archive/web/pkix/current/msg27482.html ).

After IETF last call and several revisions from the Security Directorate, the particular section referring the  EKU values has been updated. In the current version (see http://www.ietf.org/id/draft-ietf-csi-send-cert-07.txt), we are now requiring four and not three EKU values. The change has been requested by the authors of the proxy-SEND document to differentiate the case of a proxy router vs a proxy owner.

Consequently, I request the allocation of an additional EKU value and the modification of the register from id-kp-sendProxy (id-kp 24) to id-kp-sendProxiedRouter (id-kp 24).

I look forward to hearing from you,

Best regards,

Roque

Old Request (current assignments):
id-kp-sendRouter               OBJECT IDENTIFIER ::= { id-kp 23 }
id-kp-sendProxy                OBJECT IDENTIFIER ::= { id-kp 24 }
id-kp-sendOwner                OBJECT IDENTIFIER ::= { id-kp 25 } 


Updated Request (current document):
id-kp-sendRouter 	OBJECT IDENTIFIER ::= { id-kp 23 }
id-kp-sendProxiedRouter 	OBJECT IDENTIFIER ::= { id-kp 24 }
id-kp-sendOwner OBJECT IDENTIFIER ::= { id-kp 25 }
id-kp-sendProxiedOwner OBJECT IDENTIFIER ::= { id-kp TBD }