W3C home > Mailing lists > Public > public-webid@w3.org > November 2013

Fwd: [apps-discuss] New version of certspec (01); request review and URN assignment

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Sun, 3 Nov 2013 09:16:18 +0100
Message-ID: <CAKaEYhKqQWLfGPZuJooOZObT85ZSjkL04ywVGV3SnmcMqYRRhg@mail.gmail.com>
To: public-rww <public-rww@w3.org>, public-webid <public-webid@w3.org>
FYI:

1.  Introduction

   Digital certificates are used in many systems and protocols to
   identify and authenticate parties.  Security considerations
   frequently require that the certificate must be identified with
   certainty, because selecting the wrong certificate will lead to
   validation errors (resulting in denial of service), or in improper
   credential selection (resulting in unwanted disclosure or
   substitution attacks).  The goal of this namespace is to provide a
   uniform syntax for identifying certificates with precision in Uniform
   Resource Identifiers (URIs), specifically Uniform Resource Names
   (URNs).

   Using this syntax, any protocol or system that refers to a
   certificate in a textual format can unambiguously identify that
   certificate by value or reference.  Implementers that parse these
   URNs can resolve them into actual certificates.

   Examples:
   urn:cert:SHA-1:3ea3f070773971539b9dbf1b98c54be3a4f0f3c8
   urn:cert:issuersn:cn=AcmeIssuingCompany,st=California,c=US;0134F1
   urn:cert:base64:MIICAS...



---------- Forwarded message ----------
From: Sean Leonard <dev+ietf@seantek.com>
Date: 3 November 2013 07:47
Subject: [apps-discuss] New version of certspec (01); request review and
URN assignment
To: urn-nid@ietf.org, saag@ietf.org, apps-discuss@ietf.org


Hello URN/Apps folks, and SAAG folks:

A new version of the Internet-Draft draft-seantek-certspec (01) has been
posted to the IETF repository. I would like to notify this list for
commentary, and utlimately to apply for the URN NID 'cert'.

Compared to 00 last year, this version adds discussion of the need for a
uniform way to identify certificates by name in a URI/URN, the differences
between this naming scheme and the ni: URI scheme (RFC 6920), and a
methodology to /resolve/ certain various classes of cert URNs to ni, http,
ldap, and other URI schemes.

Kind regards,

Sean

**************

A new version of I-D, draft-seantek-certspec-01.txt
has been successfully submitted by Sean Leonard and posted to the
IETF repository.

Filename:        draft-seantek-certspec
Revision:        01
Title:           A Uniform Resource Name (URN) Namespace for Certificates
Creation date:   2013-10-21
Group:           Individual Submission
Number of pages: 13
URL:
http://www.ietf.org/internet-drafts/draft-seantek-certspec-01.txt
Status:          http://datatracker.ietf.org/doc/draft-seantek-certspec
Htmlized:        http://tools.ietf.org/html/draft-seantek-certspec-01
Diff:            http://www.ietf.org/rfcdiff?url2=draft-seantek-certspec-01

Abstract:
  Digital certificates are used in many systems and protocols to
  identify and authenticate parties.  This document describes a Uniform
  Resource Name (URN) namespace that identifies certificates.  These
  URNs can be used when certificates need to be identified by value or
  reference.



Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat
_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss
Received on Sunday, 3 November 2013 08:16:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:54:46 UTC