Hi Sabrina, We will review this and get back to you. Thanks
Sri On 2/16/24, 4:42 PM, "dmm on behalf of Sabrina Tanamal via RT" <[email protected] <mailto:[email protected]> on behalf of [email protected] <mailto:[email protected]>> wrote: Hi Eric, all, (resending this message) Should this errata report be listed as an additional reference for the following registration? Status Codes registry (https://www.iana.org/assignments/mobility-parameters <https://www.iana.org/assignments/mobility-parameters>): 144 MIPV6-ID-MISMATCH [RFC4285] Thanks, Sabrina Tanamal Lead IANA Services Specialist On Tue Feb 06 19:28:15 2024, sabrina.tanamal wrote: > Hi Eric, all, > (resending this message) > > Should this errata report be listed as an additional reference for the > following registration? > > Status Codes registry (https://www.iana.org/assignments/mobility- > <https://www.iana.org/assignments/mobility-> > parameters): > > 144 MIPV6-ID-MISMATCH [RFC4285] > > Thanks, > > Sabrina Tanamal > Lead IANA Services Specialist > > On Thu Jan 25 21:59:48 2024, sabrina.tanamal wrote: > > Hi Eric, all, > > (resending this message) > > > > Should this errata report be listed as an additional reference for > > the > > following registration? > > > > Status Codes registry (https://www.iana.org/assignments/mobility- > > <https://www.iana.org/assignments/mobility-> > > parameters): > > > > 144 MIPV6-ID-MISMATCH [RFC4285] > > > > Thanks, > > > > Sabrina Tanamal > > Lead IANA Services Specialist > > > > On Tue Jan 16 20:16:47 2024, sabrina.tanamal wrote: > > > Hi Eric, all, > > > > > > Should this errata report be listed as an additional reference for > > > the > > > following registration? > > > > > > Status Codes registry (https://www.iana.org/assignments/mobility- > > > <https://www.iana.org/assignments/mobility-> > > > parameters): > > > > > > 144 MIPV6-ID-MISMATCH [RFC4285] > > > > > > Thanks, > > > > > > Sabrina Tanamal > > > Lead IANA Services Specialist > > > > > > On Fri Jan 12 08:28:40 2024, [email protected] > > > <mailto:[email protected]> wrote: > > > > The following errata report has been verified for RFC5555, > > > > "Mobile IPv6 Support for Dual Stack Hosts and Routers". > > > > > > > > -------------------------------------- > > > > You may review the report below and at: > > > > https://www.rfc-editor.org/errata/eid3463 > > > > <https://www.rfc-editor.org/errata/eid3463> > > > > > > > > -------------------------------------- > > > > Status: Verified > > > > Type: Technical > > > > > > > > Reported by: Romain Kuntz <[email protected] > > > > <mailto:[email protected]>> > > > > Date Reported: 2013-01-17 > > > > Verified by: Éric Vyncke (IESG) > > > > > > > > Section: GLOBAL > > > > > > > > Original Text > > > > ------------- > > > > with error code 144 > > > > > > > > Corrected Text > > > > -------------- > > > > > > > > > > > > Notes > > > > ----- > > > > Binding acknowledgement error status 144 is referenced in > > > > sections > > > > 4.4.2 and 4.5 to specify that MN should not use UDP > > > > encapsulation. > > > > However, there is no mention of this status number in the IANA > > > > Considerations section (section 8). > > > > > > > > -- Verifier note (EV) --- > > > > > > > > The MIPv6 Status code 144 does not appear in > > > > https://www.iana.org/assignments/mobility-parameters/mobility- > > > > <https://www.iana.org/assignments/mobility-parameters/mobility-> > > > > parameters.xhtml#mobility-parameters-6 > > > > > > > > Even worse, it is actually assigned to MIPV6-ID-MISMATCH by a > > > > previous > > > > RFC 4285 (and the semantics of MIPV6-ID-MISMATCH probably does > > > > not > > > > match RFC 5555 semantics). > > > > > > > > -------------------------------------- > > > > RFC5555 (draft-ietf-mext-nemo-v4traversal-10) > > > > -------------------------------------- > > > > Title : Mobile IPv6 Support for Dual Stack Hosts > > > > and > > > > Routers > > > > Publication Date : June 2009 > > > > Author(s) : H. Soliman, Ed. > > > > Category : PROPOSED STANDARD > > > > Source : Mobility EXTensions for IPv6 > > > > Area : Internet > > > > Stream : IETF > > > > Verifying Party : IESG _______________________________________________ dmm mailing list [email protected] <mailto:[email protected]> https://www.ietf.org/mailman/listinfo/dmm <https://www.ietf.org/mailman/listinfo/dmm> _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
