Dear all, As one of the authors, I agree that this erratum should be verified. Section 8.5 registers value 0 as NOPREF, and the second paragraph of Section 6.4 already uses that name.
Note that the same inconsistency appears in the preceding paragraph of Section 6.4, for the HMAC ID: "A HMAC ID value of NONE (0) MAY be used...", while Section 8.3 registers value 0 as NOPREF. It would make sense to fix both. Since the meaning does not change, it could also be classified as editorial. Best regards, Albert Cabellos On Thu, Oct 15, 2026 07:17 PM, [email protected] wrote: > The following errata report has been submitted for RFC9303, > "Locator/ID Separation Protocol Security (LISP-SEC)" > > -------------------------------------- > You may review the report below and at: > https://errata.rfc-editor.org/eid9221/ > > -------------------------------------- > Type: Technical > Reported by: Wenbin Zhou <[email protected]> > > Section 6.4 says: > > Original Text > ------------- > A KDF value of NONE (0) may be used to specify that the ITR has no > preferred KDF ID. > > Corrected Text > -------------- > A KDF value of NOPREF (0) may be used to specify that the ITR has no > preferred KDF ID. > > Notes > ----- > Section 8.5 of this document ("Key Derivation Functions") registers > value 0 with the name "NOPREF", and Section 6.2 uses "A KDF value of > NOPREF (0)" with that meaning. Using the name "NONE" here for the same > registry value is inconsistent and may confuse implementers checking > the IANA registry. > > Instructions: > ------------- > This erratum is currently posted as "Reported". Please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > will log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC9303 (draft-ietf-lisp-sec) > -------------------------------------- > Title : Locator/ID Separation Protocol Security (LISP-SEC) > Publication Date : October 2022 > Author(s) : F. Maino, V. Ermagan, A. Cabellos, D. Saucez > Category : Proposed Standard > Source : lisp (rtg) > Stream : IETF > Verifying Party : IESG > _______________________________________________ > lisp mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
