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/eid9277/ -------------------------------------- Type: Technical Reported by: Wenbin Zhou <[email protected]> Section 6.9 says: Original Text ------------- If the ITR did indicate a Requested HMAC ID in the Map-Request and the PKT HAMC ID in the corresponding Map-Reply is different, or if the ITR did not indicate a Requested HMAC ID in the Map-Request and the PKT HMAC ID in the corresponding Map-Reply is not supported, then 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' field, according to ITR's local policy. Corrected Text -------------- If the ITR did indicate a Requested HMAC ID in the Map-Request and the EID HMAC ID in the corresponding Map-Reply is different, or if the ITR did not indicate a Requested HMAC ID in the Map-Request and the EID HMAC ID in the corresponding Map-Reply is not supported, then 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' field, according to ITR's local policy. Notes ----- This paragraph verifies the EID-AD and names the 'EID HMAC ID' field as the algorithm to use, but its discard condition compares the Requested HMAC ID with the 'PKT HMAC ID' field. The 'PKT HMAC ID' identifies the algorithm protecting the PKT-AD, and that comparison is specified separately later in this section. As written, the 'EID HMAC ID' is never checked against the Requested HMAC ID, so a Map-Server that substitutes a different algorithm (Section 6.7.1 permits this) goes unnoticed by the ITR. The correction changes the field name in this condition to 'EID HMAC ID'; the spelling "HAMC" in the same sentence was already corrected by Errata ID 9226. 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]
