Re: [Mip4] [Technical Errata Reported] RFC5454 (1718)

George Tsirtsis <tsirtsis@googlemail.com> Mon, 16 March 2009 12:53 UTC

DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=jav2n54ZTIZNTif2bRGc66qSV8f14WNyzvfPZByim5sYXc3OBDwQ8XexKcLFkGgqcj sFgTdCWUmdGq5jIyzKaTD2LsSkHMogvmXVuYNrIyn77sWvMVARv16dwKLuTrE6tU+FVk cQLVe3PERpnd49izBvYMM0BmKYzRd1UAIHCC8=
MIME-Version: 1.0
In-Reply-To: <200903151827.n2FIRUD5013127@boreas.isi.edu>
References: <200903151827.n2FIRUD5013127@boreas.isi.edu>
Date: Mon, 16 Mar 2009 08:53:54 -0400
Message-ID: <d3886a520903160553o160143f9l93eb616554deb43b@mail.gmail.com>
From: George Tsirtsis <tsirtsis@googlemail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: ah@tr-sys.de, hesham@elevatemobile.com, pete.mccann@motorola.com, rdroms@cisco.com, mip4@ietf.org, jari.arkko@piuha.net, vpark@qualcomm.com, townsley@cisco.com, henrik@levkowetz.com
Subject: Re: [Mip4] [Technical Errata Reported] RFC5454 (1718)
Precedence: list

I verify that this is indeed an error and I agree with the proposed fix.

George

On Sun, Mar 15, 2009 at 2:27 PM, RFC Errata System
<rfc-editor@rfc-editor.org> wrote:
>
> The following errata report has been submitted for RFC5454,
> "Dual-Stack Mobile IPv4".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5454&eid=1718
>
> --------------------------------------
> Type: Technical
> Reported by: Alfred Hoenes <ah@TR-Sys.de>
>
> Section: 2.1, pg.5
>
> Original Text
> -------------
>   Prefix Length
>
>      A sixteen-byte field containing the Mobile IPv6 Network Prefix;
>      all insignificant (low-order) bits (beyond the Prefix Length) MUST
>      be set to 0 by the originator of the option and ignored by the
>      receiver.
>
>   Mobile IPv6 Network Prefix
>
>      A sixteen-byte field containing the Mobile IPv6 Network Prefix
>
>
> Corrected Text
> --------------
>   Prefix Length
>
> |     Indicates the prefix length of the prefix included in the Mobile
> |     IPv6 Network Prefix field.  A value of 255 indicates that a link-
> |     local address is included in the Mobile IPv6 Network Prefix field.
>
>   Mobile IPv6 Network Prefix
>
> |     A sixteen-byte field containing the Mobile IPv6 Network Prefix;
> |     all insignificant (low-order) bits (beyond the Prefix Length) MUST
> |     be set to 0 by the originator of the option and ignored by the
> |     receiver.
>
> Notes
> -----
> The replacement text apparently has been placed into the wrong
> field explanation.
> The text presented for "Prefix Length" is the text that should
> be specified for "Mobile IPv6 Network Prefix"; the correct text
> for "Prefix Length" (as shown above) is borrowed from Section 2.2.
>
> 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.
>
> --------------------------------------
> RFC5454 (draft-ietf-mip4-dsmipv4-10)
> --------------------------------------
> Title               : Dual-Stack Mobile IPv4
> Publication Date    : March 2009
> Author(s)           : G. Tsirtsis, V. Park, H. Soliman
> Category            : PROPOSED STANDARD
> Source              : Mobility for IPv4
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG
>

[Mip4] [Technical Errata Reported] RFC5454 (1718) RFC Errata System
Re: [Mip4] [Technical Errata Reported] RFC5454 (1… George Tsirtsis