Re: [KEYPROV] Second Last Call: draft-ietf-keyprov-symmetrickeyformat (Symmetric Key Package Content Type) to Proposed Standard

I am not sure if the reference is definitively normative. Looks to me
as if implementers can implement without reading the Luhn patent

However, ISO/IEC 7812 is the same as the Luhn patent so how about we
make [LUHN] informative and Annex B of ISO/IEC 7812 normative?

       o checkDigit indicates whether a device needs to check the
        appended Luhn check digit, as defined in [LUHN], contained in a
        challenge.  The checkDigit MUST NOT be present if the encoding
        value is anything other than 'DECIMAL'.  A value of TRUE
        indicates that the device will check the appended Luhn check
        digit in a provided challenge.  A value of FALSE indicates that
        the device will not check the appended Luhn check digit in the
        challenge.

On the downref issue, the binary format is being used in real code so
should not be considered experimental at this point in my view. I
would like to see the binary time RFC upgraded to standard.
On Wed, Apr 28, 2010 at 4:12 PM, Sam Hartman <hartmans-ietf <at> mit.edu> wrote:
>>>>>> "Simon" == Simon Josefsson <simon <at> josefsson.org> writes:
>
>    Simon> This document appears to have a normative reference to a
>    Simon> patent:
>
>    Simon>    [LUHN] Luhn, H., "Luhn algorithm", US Patent 2950048,
>    Simon> August 1960, http://patft.uspto.gov/netacgi/nph-
>    Simon> Parser?patentnumber=2950048.
>
>    Simon> I cannot find a patent disclosure about this on file with the
>    Simon> IETF: