[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Qualified Certificates and the 43:d IETF Meeting
We decided during Orlando to go with dnQualifier instead of serialNumber.
It seams that there is a majority supporting that choice.
/Stefan
At 04:14 PM 12/11/98 -0500, Ella P. Gardner wrote:
>Some folks don't like the fact that the X.500 standard unique identifier is
>a bit string. That's why we used dnQualifier in the Allied Communications
>Publication 133.
>
>Ella
>
>At 01:04 PM 12/10/98 -0500, david chadwick wrote:
>>
>>
>>Russ Housley wrote:
>>
>>> Nick & Stefan:
>>>
>>> >>2)The standard attribute dnQualifier could be used instead of
>serialNumber
>>> >>(Th attribute "serialNumber is defined in RFC 2256 as being the serial
>>> >>number of a device).
>>> >>
>>> >
>>
>>The X.500 standard defines a uniqueIdentifier attribute that might be better
>>suited to the semantics than either serial number or dnQualifier.
>>David
>>
>>
>>>
>>> >Yes, the SN is not in complete harmony regarding its definition and its
>>> >use. However several other standardisation proposal has choosen SN for
>>> >personal identifiers. The rationale behind that choice have been that
most
>>> >applications support and displays this attribute in a correct way.
>>> >
>>> >Is there an installed base using "dnQualifier" ?
>>>
>>> We include support of dnQualifier.
>>>
>>> I strongly prefer dnQualifier over serialNumber.
>>>
>>> Russ
>>
>>
>>
>
>
>
-------------------------------------------------------------------
Stefan Santesson <stefan@accurata.se>
Accurata Systemsäkerhet AB
Lotsgatan 27 D Tel. +46-40 152211
216 42 Malmö Fax. +46-40 150790
Sweden Mobile +46-70 5247799
PGP fingerprint: 89BC 6C79 5B3D 591B 8547 1512 7D11 DBF4 528F 29A0
-------------------------------------------------------------------