Re: [Editorial Errata Reported] RFC6434 (3091)

Brian Haberman <brian@innovationslab.net> Tue, 17 January 2012 18:16 UTC

Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6BCB21F84D7 for <ipv6@ietfa.amsl.com>; Tue, 17 Jan 2012 10:16:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 2JuBZrhzZU-3 for <ipv6@ietfa.amsl.com>; Tue, 17 Jan 2012 10:16:43 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1639D21F8463 for <ipv6@ietf.org>; Tue, 17 Jan 2012 10:16:42 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 2C87E88130; Tue, 17 Jan 2012 10:16:40 -0800 (PST)
Received: from clemson.local (unknown [75.94.92.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 98DA91368114; Tue, 17 Jan 2012 10:16:38 -0800 (PST)
Message-ID: <4F15BB0C.5040108@innovationslab.net>
Date: Tue, 17 Jan 2012 13:16:44 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [Editorial Errata Reported] RFC6434 (3091)
References: <20120116232606.377C8B1E007@rfc-editor.org>
In-Reply-To: <20120116232606.377C8B1E007@rfc-editor.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: john.loughney@nokia.com, narten@us.ibm.com, ipv6@ietf.org, bob.hinden@gmail.com, rdroms.ietf@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 18:16:43 -0000

On 1/16/12 6:26 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC6434,
> "IPv6 Node Requirements".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6434&eid=3091
>
> --------------------------------------
> Type: Editorial
> Reported by: Sam Silvester<sam.silvester@gmail.com>
>
> Section: 5.10.
>
> Original Text
> -------------
> Nodes supporting applications that expect to only take advantage of MLDv2's INCLUDE functionality as well as Any-Source Multicast will find it sufficient to support MLDv2 as defined in [RFC5790].
>
> Corrected Text
> --------------
> Nodes supporting applications that expect to only take advantage of MLDv2's INCLUDE functionality as well as Any-Source Multicast will find it sufficient to support Lightweight MLDv2 as defined in [RFC5790].
>
> Notes
> -----
> MLDv2 is RFC3810, and has both INCLUDE and EXCLUDE filter modes (as per previous paragraph.
>
> RFC5790 (Lightweight MLDv2) is sufficient for nodes supporting application using only INCLUDE and Any-Source Multicast.
>
> 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.
>
> --------------------------------------
> RFC6434 (draft-ietf-6man-node-req-bis-11)
> --------------------------------------
> Title               : IPv6 Node Requirements
> Publication Date    : December 2011
> Author(s)           : E. Jankiewicz, J. Loughney, T. Narten
> Category            : INFORMATIONAL
> Source              : IPv6 Maintenance
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG

I am not sure there is a benefit to adding a single adjective to the 
noted sentence.  The actual reference is correct, so the reader will be 
correctly directed to the Lightweight MLD specification.

Regards,
Brian