[MEXT] [Technical Errata Reported] RFC5555 (1805)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 08 July 2009 17:26 UTC
Return-Path: <web-usrn@ISI.EDU>
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B15793A6A92 for <mext@core3.amsl.com>; Wed, 8 Jul 2009 10:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.109
X-Spam-Level:
X-Spam-Status: No, score=-17.109 tagged_above=-999 required=5 tests=[AWL=0.490, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HeNOo1+3dBvU for <mext@core3.amsl.com>; Wed, 8 Jul 2009 10:26:22 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 05F633A69CE for <mext@ietf.org>; Wed, 8 Jul 2009 10:26:22 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n68HP2Fl012575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 8 Jul 2009 10:25:03 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n68HP1ZF012569; Wed, 8 Jul 2009 10:25:01 -0700 (PDT)
Date: Wed, 08 Jul 2009 10:25:01 -0700
Message-Id: <200907081725.n68HP1ZF012569@boreas.isi.edu>
To: hesham@elevatemobile.com, rdroms@cisco.com, jari.arkko@piuha.net, julien.laganier.IETF@googlemail.com, marcelo@it.uc3m.es
From: RFC Errata System <rfc-editor@rfc-editor.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
Cc: rfc-editor@rfc-editor.org, julien.laganier.ietf@googlemail.com, mext@ietf.org
Subject: [MEXT] [Technical Errata Reported] RFC5555 (1805)
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jul 2009 17:26:24 -0000
The following errata report has been submitted for RFC5555, "Mobile IPv6 Support for Dual Stack Hosts and Routers". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5555&eid=1805 -------------------------------------- Type: Technical Reported by: Julien Laganier <julien.laganier.ietf@googlemail.com> Section: 8 Original Text ------------- The IPv4 home address option described in Section 3.1.1 has been assigned value 29. This option is included in the mobility header described in [RFC3775]. The IPv4 address acknowledgement option described in Section 3.2.1 has been assigned value 29. This option is included in the mobility header described in [RFC3775]. Corrected Text -------------- The IPv4 home address option described in Section 3.1.1 has been assigned value 29. This option is included in the mobility header described in [RFC3775]. The IPv4 address acknowledgement option described in Section 3.2.1 has been assigned value 30. This option is included in the mobility header described in [RFC3775]. Notes ----- There's an error in the IANA section of the RFC: while both the IANA registry <http://www.iana.org/assignments/mobility-parameters/> and the section of the RFC describing the option <http://tools.ietf.org/html/rfc5555#section-3.2.1> have the correct type value for the IPv4 address acknowledgement option, i.e., 30, the IANA section <http://tools.ietf.org/html/rfc5555#section-8> assigns type value 29 to both the IPv4 home address option and IPv4 address acknowledgement option. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- 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
- [MEXT] [Technical Errata Reported] RFC5555 (1805) RFC Errata System