Re: [mif] [Editorial Errata Reported] RFC6418 (3057)

Margaret Wasserman <mrw@lilacglade.org> Thu, 22 December 2011 00:13 UTC

Return-Path: <mrw@lilacglade.org>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B394821F8A4E for <mif@ietfa.amsl.com>; Wed, 21 Dec 2011 16:13:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level:
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0FHQcw94OqOF for <mif@ietfa.amsl.com>; Wed, 21 Dec 2011 16:13:36 -0800 (PST)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 425F121F89BA for <mif@ietf.org>; Wed, 21 Dec 2011 16:13:36 -0800 (PST)
Received: from [10.36.0.36] (pool-108-7-232-64.bstnma.fios.verizon.net [108.7.232.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id C826720134; Wed, 21 Dec 2011 19:13:30 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <20111222000527.5A49F72E004@rfc-editor.org>
Date: Wed, 21 Dec 2011 19:13:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC003F2F-4A8E-4A53-B854-49EB47DB83B8@lilacglade.org>
References: <20111222000527.5A49F72E004@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.1084)
Cc: mif@ietf.org, denghui02@hotmail.com
Subject: Re: [mif] [Editorial Errata Reported] RFC6418 (3057)
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 00:13:36 -0000

This erratum looks right to me.  I think we should accept it.

Margaret


On Dec 21, 2011, at 7:05 PM, RFC Errata System wrote:

> 
> The following errata report has been submitted for RFC6418,
> "Multiple Interfaces and Provisioning Domains Problem Statement".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6418&eid=3057
> 
> --------------------------------------
> Type: Editorial
> Reported by: Zhou Sujing <zhou.sujing@zte.com.cn>
> 
> Section: 4.4
> 
> Original Text
> -------------
> For instance, the network may perform HTTP redirection or modify DNS behavior (Section 4.1) until the user has not authenticated.
> 
> 
> 
> Corrected Text
> --------------
> For instance, the network may perform HTTP redirection or modify DNS behavior (Section 4.1) until the user has been authenticated.
> 
> 
> Notes
> -----
> 
> 
> 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. 
> 
> --------------------------------------
> RFC6418 (draft-ietf-mif-problem-statement-15)
> --------------------------------------
> Title               : Multiple Interfaces and Provisioning Domains Problem Statement
> Publication Date    : November 2011
> Author(s)           : M. Blanchet, P. Seite
> Category            : INFORMATIONAL
> Source              : Multiple Interfaces
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG