The following errata report has been rejected for RFC6275, "Mobility Support in IPv6".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid5898 -------------------------------------- Status: Rejected Type: Technical Reported by: Jen Linkova <[email protected]> Date Reported: 2019-11-08 Rejected by: Eric Vyncke (IESG) Section: GLOBAL Original Text ------------- Corrected Text -------------- It should say: Updates: 4861 [in RFC header] Notes ----- RFC4861 Section 6.2.1 says that "MaxRtrAdvInterval ..MUST be no less than 4 seconds" and "MinRtrAdvInterval...MUST MUST be no less than 3 seconds" RFC6275 Section 7.5. changes those requirements to: "Routers supporting mobility SHOULD be able to be configured with a smaller MinRtrAdvInterval value and MaxRtrAdvInterval value to allow sending of unsolicited multicast Router Advertisements more often. The minimum allowed values are: o MinRtrAdvInterval 0.03 seconds o MaxRtrAdvInterval 0.07 seconds " so it should be flagged as a formal update to RFC4861. --VERIFIER NOTES-- Deviation from RFC 4861 are allowed by its section 6.2.1: " The default values for some of the variables listed below may be overridden by specific documents that describe how IPv6 operates over different link layers." -------------------------------------- RFC6275 (draft-ietf-mext-rfc3775bis-13) -------------------------------------- Title : Mobility Support in IPv6 Publication Date : July 2011 Author(s) : C. Perkins, Ed., D. Johnson, J. Arkko Category : PROPOSED STANDARD Source : Mobility EXTensions for IPv6 Area : Internet Stream : IETF Verifying Party : IESG _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
