[Roll] [Editorial Errata Reported] RFC6550 (4219)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 05 January 2015 15:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 042421A00C5 for <roll@ietfa.amsl.com>; Mon, 5 Jan 2015 07:36:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.912
X-Spam-Level:
X-Spam-Status: No, score=-103.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2EUbPBBBUBr9 for <roll@ietfa.amsl.com>; Mon, 5 Jan 2015 07:36:12 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 030591A0199 for <roll@ietf.org>; Mon, 5 Jan 2015 07:36:12 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B504A181C64; Mon, 5 Jan 2015 07:35:50 -0800 (PST)
To: wintert@acm.org, pthubert@cisco.com, abr@sdesigns.dk, jhui@archrock.com, kelsey@ember.com, pal@cs.stanford.edu, kpister@dustnetworks.com, rstruik.ext@gmail.com, jpv@cisco.com, roger.alexander@cooperindustries.com, akatlas@gmail.com, adrian@olddog.co.uk, maria.ines.robles@ericsson.com, mcr+ietf@sandelman.ca
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150105153550.B504A181C64@rfc-editor.org>
Date: Mon, 5 Jan 2015 07:35:50 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/iApyff7H3PIVh6rKJSPwZ6j_XyM
X-Mailman-Approved-At: Tue, 06 Jan 2015 22:54:46 -0800
Cc: mcr+ietf@sandelman.ca, roll@ietf.org, rfc-editor@rfc-editor.org
Subject: [Roll] [Editorial Errata Reported] RFC6550 (4219)
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jan 2015 15:36:14 -0000

The following errata report has been submitted for RFC6550,
"RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6550&eid=4219

--------------------------------------
Type: Editorial
Reported by: pronounciation of RPL <mcr+ietf@sandelman.ca>

Section: 1.0

Original Text
-------------
This document specifies the IPv6 Routing Protocol for LLNs (RPL).
Note that although RPL was specified according to the requirements
set forth in the aforementioned requirement documents, its use is in
no way limited to these applications.

Corrected Text
--------------
This document specifies the IPv6 Routing Protocol for LLNs (RPL).  
The acronym RPL is used extensively in other documents and in 
other acronyms,and it is pronounced "ripple". As such, it is 
appropriate to write "a RPL root" as if the acronym was pronounced, 
rather than "an RPL root" if the letters were spelt out "arr peee ell".

Note that although RPL was specified according to the requirements
set forth in the aforementioned requirement documents, its use is in
no way limited to these applications.

Notes
-----
newcomers to the IoT space do not know what "ripple" is.
this is recorded as errata so that it does not get lost on 6550bis.

Instructions:
-------------
This erratum 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. 

--------------------------------------
RFC6550 (draft-ietf-roll-rpl-19)
--------------------------------------
Title               : RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks
Publication Date    : March 2012
Author(s)           : T. Winter, Ed., P. Thubert, Ed., A. Brandt, J. Hui, R. Kelsey, P. Levis, K. Pister, R. Struik, JP. Vasseur, R. Alexander
Category            : PROPOSED STANDARD
Source              : Routing Over Low power and Lossy networks
Area                : Routing
Stream              : IETF
Verifying Party     : IESG