Re: [Mip4] [Editorial Errata Reported] RFC5944 (3438)

Brian Haberman <brian@innovationslab.net> Wed, 02 January 2013 16:36 UTC

Return-Path: <brian@innovationslab.net>
X-Original-To: mip4@ietfa.amsl.com
Delivered-To: mip4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A30121F8659 for <mip4@ietfa.amsl.com>; Wed, 2 Jan 2013 08:36:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Level:
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PZN5M6D7nUcL for <mip4@ietfa.amsl.com>; Wed, 2 Jan 2013 08:36:05 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 8D89621F8635 for <mip4@ietf.org>; Wed, 2 Jan 2013 08:36:05 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 6B9EB880D1; Wed, 2 Jan 2013 08:36:05 -0800 (PST)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id C103E130019; Wed, 2 Jan 2013 08:36:04 -0800 (PST)
Message-ID: <50E461F3.9030309@innovationslab.net>
Date: Wed, 02 Jan 2013 11:36:03 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: charliep@computer.org, rdroms.ietf@gmail.com, henrik@levkowetz.com, mccap@petoni.org
References: <20121227092922.5E302B1E003@rfc-editor.org>
In-Reply-To: <20121227092922.5E302B1E003@rfc-editor.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mip4@ietf.org
Subject: Re: [Mip4] [Editorial Errata Reported] RFC5944 (3438)
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mip4>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 16:36:06 -0000

All,
      This seems like a valid erratum to me and should be marked as 
Verified?  Any objections?

Regards,
Brian

On 12/27/12 4:29 AM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5944,
> "IP Mobility Support for IPv4, Revised".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5944&eid=3438
>
> --------------------------------------
> Type: Editorial
> Reported by: Pritish Aherrao <pritish_aherrao@yahoo.com>
>
> Section: 3.7.3.2
>
> Original Text
> -------------
> A Registration Reply that satisfies the validity checks of Section
> 3.8.2.1 is relayed to the mobile node.
>
> Corrected Text
> --------------
> A Registration Reply that satisfies the validity checks of Section
> 3.7.3.1 is relayed to the mobile node.
>
> Notes
> -----
> Currently, the incorrect cross reference is provided.
> The Foreign Agent would perform the validity checks mentioned in Section 3.7.3.1 upon receiving the Registration Reply and would relay the Registration Reply that satisfies the validity checks.
>
> 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.
>
> --------------------------------------
> RFC5944 (draft-ietf-mip4-rfc3344bis-10)
> --------------------------------------
> Title               : IP Mobility Support for IPv4, Revised
> Publication Date    : November 2010
> Author(s)           : C. Perkins, Ed.
> Category            : PROPOSED STANDARD
> Source              : Mobility for IPv4
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG
>