1.2 Normative References DES - withdrawn standard

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: 3.1.1
    • Component/s: edits
    • None
    • Environment:

      References

    • Hide

      Move DES reference to 1.3 Non-normative references.

      Show
      Move DES reference to 1.3 Non-normative references.
    • Hide

      Resolved as issue 132 CSD04

      Show
      Resolved as issue 132 CSD04

      Section 1.2 Normative References reads in part:

      *****
      Data Encryption Standard (DES).

      http://csrc.nist.gov/publications/fips/fips46-3/fips46-3.pdf
      *****

      However, the document referenced now has this cover page:

      *****
      The attached publication,

      FIPS Publication 46-3
      (reaffirmed October 25, 1999),

      was withdrawn on May 19, 2005 and is provided here only
      for historical purposes.
      *****

      The purpose of a normative reference is to cite additional standards to which a conforming application must conform in order to conform to the citing specification.

      In this case the citing of DES implies that conformance to MQTT may require conformance to a withdrawn specification.

      Withdrawn specifications are allowable for non-normative references but should not be used as normative references.

      Section 5.2 Lightweight cryptography and constrained devices cites DES saying:

      *****
      Advanced Encryption Standard [AES] and Data Encryption Standard [DES] are widely adopted.
      *****
      I take that to be a non-normative statement, simply an observation and not a requirement for conformance to DES.

      I would move DES into the Non-normative reference section since it isn't required for conformance to MQTT.

            Assignee:
            Unassigned
            Reporter:
            Patrick Durusau
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: