[Mip4] [Editorial Errata Reported] RFC5454 (1720)
RFC Errata System <rfc-editor@rfc-editor.org> Sun, 15 March 2009 18:40 UTC
Return-Path: <web-usrn@ISI.EDU>
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CC3C3A6A7E for <mip4@core3.amsl.com>; Sun, 15 Mar 2009 11:40:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.256
X-Spam-Level:
X-Spam-Status: No, score=-17.256 tagged_above=-999 required=5 tests=[AWL=0.343, 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 crZKsbKmTCXc for <mip4@core3.amsl.com>; Sun, 15 Mar 2009 11:40:09 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 97FC028C0FF for <mip4@ietf.org>; Sun, 15 Mar 2009 11:40:09 -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 n2FIeWuP017483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 15 Mar 2009 11:40:33 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n2FIeW70017482; Sun, 15 Mar 2009 11:40:32 -0700 (PDT)
Date: Sun, 15 Mar 2009 11:40:32 -0700
Message-Id: <200903151840.n2FIeW70017482@boreas.isi.edu>
To: tsirtsis@googlemail.com, vpark@qualcomm.com, hesham@elevatemobile.com, rdroms@cisco.com, jari.arkko@piuha.net, townsley@cisco.com, henrik@levkowetz.com, pete.mccann@motorola.com
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
X-Mailman-Approved-At: Mon, 16 Mar 2009 10:08:53 -0700
Cc: ah@TR-Sys.de, mip4@ietf.org, rfc-editor@rfc-editor.org
Subject: [Mip4] [Editorial Errata Reported] RFC5454 (1720)
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 15 Mar 2009 18:40:15 -0000
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=1720 -------------------------------------- Type: Editorial Reported by: Alfred Hoenes <ah@TR-Sys.de> Section: 3.6,pp.13/14 Original Text ------------- When IPv6 runs over an IPv4 tunnel, the IPv6 tunnel endpoints can treat the IPv4 tunnel as a single hop link as defined in [RFC4213]. The two tunnel endpoints, e.g., mobile node and home agent, MUST configure link-local IPv6 addresses as defined in Section 3.7 of [RFC4213], while they MUST also adhere to the neighbor discovery requirements of the same specification, Section 3.8, and the hop | limit requirements of Section 3.3. Corrected Text -------------- When IPv6 runs over an IPv4 tunnel, the IPv6 tunnel endpoints can treat the IPv4 tunnel as a single hop link as defined in [RFC4213]. The two tunnel endpoints, e.g., mobile node and home agent, MUST configure link-local IPv6 addresses as defined in Section 3.7 of [RFC4213], while they MUST also adhere to the neighbor discovery requirements of the same specification, Section 3.8, and the hop | limit requirements of Section 3.3 in [RFC4213]. Notes ----- Rationale: The text should also make clear to which document (this RFC or RFC 4213) the last section number given refers. Pointing to RFC 4213 twice (but not in the final case) could be misunderstood, in particular due to the presence of the comma in front of the "and" in a two-item list. 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] [Editorial Errata Reported] RFC5454 (1720) RFC Errata System