IETF Logo Mail Archive

[DMM] [IANA #1303225] [Errata Verified] RFC5555 (3463)

Sabrina Tanamal via RT <iana-matrix@iana.org> Tue, 16 January 2024 20:16 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE199C15109C; Tue, 16 Jan 2024 12:16:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.656
X-Spam-Level:
X-Spam-Status: No, score=-1.656 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R-BuJcr_Wlzp; Tue, 16 Jan 2024 12:16:47 -0800 (PST)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC5E5C14CF09; Tue, 16 Jan 2024 12:16:47 -0800 (PST)
Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 87375E1A08; Tue, 16 Jan 2024 20:16:47 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id 844F0552BB; Tue, 16 Jan 2024 20:16:47 +0000 (UTC)
RT-Owner: sabrina.tanamal
From: Sabrina Tanamal via RT <iana-matrix@iana.org>
Reply-To: iana-matrix@iana.org
In-Reply-To: <20240112082837.D84C01996026@rfcpa.amsl.com>
References: <RT-Ticket-1303225@icann.org> <20240112082837.D84C01996026@rfcpa.amsl.com>
Message-ID: <rt-5.0.3-1510019-1705436207-557.1303225-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1303225
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: sabrina.tanamal@icann.org
To: rfc-editor@rfc-editor.org
CC: r.kuntz@ipflavors.com, iesg@ietf.org, Hesham@elevatemobile.com, evyncke@cisco.com, dmm@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Tue, 16 Jan 2024 20:16:47 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/1rOREpqREa7BILPe_5VgfZT7isU>
Subject: [DMM] [IANA #1303225] [Errata Verified] RFC5555 (3463)
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2024 20:16:51 -0000

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-parameters): 

144	MIPV6-ID-MISMATCH	[RFC4285]

Thanks,

Sabrina Tanamal
Lead IANA Services Specialist

On Fri Jan 12 08:28:40 2024, rfc-editor@rfc-editor.org 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
> 
> --------------------------------------
> Status: Verified
> Type: Technical
> 
> Reported by: Romain Kuntz <r.kuntz@ipflavors.com>
> 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-
> 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

v2.23.0 | Report a Bug | By Email