S/MIME Mail Security (smime)

Paul Hoffman | 22 Dec 2008 17:50

Re: consisten use of top-level oid branch name joint-iso-itu-t(2)


At 3:48 PM +0000 12/22/08, John Larmouth wrote:
>However, the recent introduction of Unicode labels, as normative and unambigous names gives a new naming
scheme to the (same) OID tree that enables names (Unicode labels) to be used in machine communication if
desired. 

Note that this scheme has not been adopted by PKIX nor S/MIME, nor has it even been proposed to either of the
working groups.

>The ASN.1 type is called OID_IRI and provides for node identification using Unicode labels.

Paging Peter Gutmann....

--Paul Hoffman, Director
--VPN Consortium

headers

John Larmouth | 23 Dec 2008 12:12

Re: consisten use of top-level oid branch name joint-iso-itu-t(2)

Please note my use of "if desired" below. This presents an opportunity, not a requirement.

Nothing has been removed from the old OID capability.

I agree that the use of Unicode labels has not been adopted by PKIX or S/MIME (and may well never be), nor presented to them. However, unless or until the "oid" IRI format is accepted by URI-review, it would be premature for PKIX or SMIME to even consider it.

John L

Paul Hoffman wrote:

At 3:48 PM +0000 12/22/08, John Larmouth wrote:
However, the recent introduction of Unicode labels, as normative and unambigous names gives a new naming scheme to the (same) OID tree that enables names (Unicode labels) to be used in machine communication if desired.
Note that this scheme has not been adopted by PKIX nor S/MIME, nor has it even been proposed to either of the working groups.
The ASN.1 type is called OID_IRI and provides for node identification using Unicode labels.
Paging Peter Gutmann.... --Paul Hoffman, Director --VPN Consortium

-- Prof John Larmouth Larmouth T&PDS Ltd (Training and Protocol Design Services Ltd) 1 Blueberry Road Bowdon j.larmouth <at> btinternet.com Altrincham Cheshire WA14 3LS England Tel: +44 161 928 1605