IETF Logo Mail Archive

Re: [pkix] CORRECTED: Request for allocation of extended key purpose identifiers

Suresh Krishnan <suresh.krishnan@ericsson.com> Wed, 10 February 2010 17:57 UTC

Return-Path: <suresh.krishnan@ericsson.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 535A93A777B for <pkix@core3.amsl.com>; Wed, 10 Feb 2010 09:57:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.569
X-Spam-Level:
X-Spam-Status: No, score=-6.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 AuMm2+LPz+zj for <pkix@core3.amsl.com>; Wed, 10 Feb 2010 09:57:16 -0800 (PST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 6CE0A28C159 for <pkix@ietf.org>; Wed, 10 Feb 2010 09:57:16 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o1AHxU4e028159; Wed, 10 Feb 2010 11:59:30 -0600
Received: from [142.133.10.113] (147.117.20.212) by eusaamw0712.eamcs.ericsson.se (147.117.20.182) with Microsoft SMTP Server id 8.1.375.2; Wed, 10 Feb 2010 12:58:00 -0500
Message-ID: <4B72F299.2040800@ericsson.com>
Date: Wed, 10 Feb 2010 12:53:29 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Stephen Kent <kent@bbn.com>
References: <4B72DDA9.5040700@ericsson.com> <p0624080bc79892ec13bb@[128.89.89.170]>
In-Reply-To: <p0624080bc79892ec13bb@[128.89.89.170]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "pkix@ietf.org" <pkix@ietf.org>, "csi-chairs@tools.ietf.org" <csi-chairs@tools.ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [pkix] CORRECTED: Request for allocation of extended key purpose identifiers
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: Wed, 10 Feb 2010 17:57:17 -0000

Hi Steve,

On 10-02-10 11:46 AM, Stephen Kent wrote:
> Suresh,
> 
> Section 3.9.5 of the SIDR document does not provide any detail about 
> how these EKUs will be used.  Is there a SeND I-D that you can cite, 
> and for which you can  provide section-level references that explains 
> how these EKUs will be used?

The usage of these values is described in section 5.2. of

http://tools.ietf.org/html/draft-ietf-csi-send-cert-01


I have reproduced the appropriate text here

    The inclusion of the router authorization value indicates that the
    certificate has been issued for allowing the router to advertise
    prefix(es) that are mentioned using the X.509 extensions for IP
    addresses and AS identifiers [RFC3779]

    The inclusion of the proxy authorization value indicates that the
    certificate has been issued for allowing the proxy to perform
    proxying of neighbor discovery messages for the prefix(es) that are
    mentioned using the X.509 extensions for IP addresses and AS
    identifiers [RFC3779]

    The inclusion of the owner authorization value indicates that the
    certificate has been issued for allowing the node to use the
    address(es) or prefix(es) that are mentioned using the X.509
    extensions for IP addresses and AS identifiers [RFC3779]


Thanks
Suresh

v2.23.0 | Report a Bug | By Email