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/eid9276/ -------------------------------------- Type: Technical Reported by: Wenbin Zhou <[email protected]> Section 6.9 says: Original Text ------------- If the 'PKT HMAC ID' field does not match the Requested HMAC ID, the ITR MUST discard the Map-Reply and send, according to rate-limitation policies defined in [RFC9301], a new Map-Request with a different Requested HMAC ID, according to ITR's local policy or until all HMAC IDs supported by the ITR have been attempted. Corrected Text -------------- If the ITR did indicate a Requested HMAC ID and the 'PKT HMAC ID' field is different, or if the ITR did not indicate a Requested HMAC ID and the 'PKT HMAC ID' field is not supported, the ITR MUST discard the Map-Reply and send, according to rate-limitation policies defined in [RFC9301], a new Map-Request with a different Requested HMAC ID, according to ITR's local policy or until all HMAC IDs supported by the ITR have been attempted. Notes ----- This sentence requires discarding any Map-Reply whose 'PKT HMAC ID' does not match the Requested HMAC ID, but Section 6.4 allows the ITR to send NONE (0), meaning it has no preferred HMAC ID. With 0 in the Requested HMAC ID field, no registered PKT HMAC ID (1 or 2 in Section 8.3) can match, so every Map-Reply would be discarded and retried "until all HMAC IDs supported by the ITR have been attempted", and the ITR could never accept a protected Map-Reply. The preceding paragraph of Section 6.9 uses a two-branch rule conditioned on whether the ITR indicated a Requested HMAC ID. The correction applies the same two-branch structure to the PKT HMAC ID. 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]
