Re: [Mip4] [Editorial Errata Reported] RFC5944 (3438)
"Charles E. Perkins" <charliep@computer.org> Wed, 02 January 2013 18:21 UTC
Return-Path: <charliep@computer.org>
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 1A82A21F8678 for <mip4@ietfa.amsl.com>; Wed, 2 Jan 2013 10:21:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.519
X-Spam-Level:
X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599]
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 vmWckkc33bBi for <mip4@ietfa.amsl.com>; Wed, 2 Jan 2013 10:21:02 -0800 (PST)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 53D2621F868E for <mip4@ietf.org>; Wed, 2 Jan 2013 10:20:59 -0800 (PST)
Received: from [107.1.141.74] (helo=[192.168.253.71]) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charliep@computer.org>) id 1TqSvg-00007O-TW; Wed, 02 Jan 2013 13:20:41 -0500
Message-ID: <50E47A75.4040106@computer.org>
Date: Wed, 02 Jan 2013 10:20:37 -0800
From: "Charles E. Perkins" <charliep@computer.org>
Organization: Saratoga Blue Skies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <20121227092922.5E302B1E003@rfc-editor.org> <50E461F3.9030309@innovationslab.net>
In-Reply-To: <50E461F3.9030309@innovationslab.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956d5d4673fe7faad864ea58d0efea96138a27e1ed10c7d9695350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Cc: mccap@petoni.org, mip4@ietf.org, rdroms.ietf@gmail.com, henrik@levkowetz.com
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 18:21:05 -0000
Hello folks, Yes, this is a valid erratum. Will the .xml file also be corrected? Regards, Charlie P. On 1/2/2013 8:36 AM, Brian Haberman wrote: > 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 >> > -- Regards, Charlie P.
- [Mip4] [Editorial Errata Reported] RFC5944 (3438) RFC Errata System
- Re: [Mip4] [Editorial Errata Reported] RFC5944 (3… Brian Haberman
- Re: [Mip4] [Editorial Errata Reported] RFC5944 (3… Henrik Levkowetz
- Re: [Mip4] [Editorial Errata Reported] RFC5944 (3… Charles E. Perkins