IETF Logo Mail Archive

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

Sabrina Tanamal via RT <iana-matrix@iana.org> Sat, 17 February 2024 00:42 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 5CAE5C1516E2 for <dmm@ietfa.amsl.com>; Fri, 16 Feb 2024 16:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.634
X-Spam-Level:
X-Spam-Status: No, score=-0.634 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MISSING_HEADERS=1.021, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 tq7PBVRIFEz8 for <dmm@ietfa.amsl.com>; Fri, 16 Feb 2024 16:42:16 -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 4F3A1C15155E for <dmm@ietf.org>; Fri, 16 Feb 2024 16:42:16 -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 09661E16DA; Sat, 17 Feb 2024 00:42:16 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id E6C6B503F2; Sat, 17 Feb 2024 00:42:15 +0000 (UTC)
RT-Owner: sabrina.tanamal
From: Sabrina Tanamal via RT <iana-matrix@iana.org>
Reply-To: iana-matrix@iana.org
In-Reply-To: <rt-5.0.3-566622-1707247695-1364.1303225-37-0@icann.org>
References: <RT-Ticket-1303225@icann.org> <20240112082837.D84C01996026@rfcpa.amsl.com> <rt-5.0.3-1510019-1705436206-1729.1303225-37-0@icann.org> <rt-5.0.3-245032-1706219988-710.1303225-37-0@icann.org> <rt-5.0.3-566622-1707247695-1364.1303225-37-0@icann.org>
Message-ID: <rt-5.0.3-118308-1708130535-984.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
CC: 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: Sat, 17 Feb 2024 00:42:15 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/Ri25s1nxpn6wmTEKgYvPeALWee0>
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: Sat, 17 Feb 2024 00:42:20 -0000

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

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-
> 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-
> > 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-
> > > 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