[CCAMP] [Technical Errata Reported] RFC6003 (2552)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 12 October 2010 17:27 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E3533A6822 for <ccamp@core3.amsl.com>; Tue, 12 Oct 2010 10:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.255
X-Spam-Level:
X-Spam-Status: No, score=-102.255 tagged_above=-999 required=5 tests=[AWL=0.345, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 lzPByYhJ8NRW for <ccamp@core3.amsl.com>; Tue, 12 Oct 2010 10:27:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id B4B243A6910 for <ccamp@ietf.org>; Tue, 12 Oct 2010 10:27:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A408AE06D7; Tue, 12 Oct 2010 10:29:08 -0700 (PDT)
To: dimitri.papadimitriou@alcatel-lucent.be, stbryant@cisco.com, adrian.farrel@huawei.com, lberger@labn.net, dbrungard@att.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20101012172908.A408AE06D7@rfc-editor.org>
Date: Tue, 12 Oct 2010 10:29:08 -0700
Cc: ah@TR-Sys.de, ccamp@ietf.org, rfc-editor@rfc-editor.org
Subject: [CCAMP] [Technical Errata Reported] RFC6003 (2552)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 17:27:54 -0000

The following errata report has been submitted for RFC6003,
"Ethernet Traffic Parameters".

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

--------------------------------------
Type: Technical
Reported by: Alfred Hoenes <ah@TR-Sys.de>

Section: 4.1, pg.7

Original Text
-------------
   Index: 8 bits

      [...]

      A given index value j can be associated to at most N Class-Type
      values CTi (i =< N) of the EXTENDED_CLASSTYPE object.  This
|     association applies when a set of one or more CTIs maps to a
      single (shared) BW profile.  An example of value setting consists
      in assigning an arbitrary value comprised within the range
      [0x08,0xF8] associated to a set of CTi, the values in the range
|     [0xF8,0xFF] being selected for reserved sets.  This allows mapping
      to one of 248 predefined CTi sets.


Corrected Text
--------------
   Index: 8 bits

      [...]

      A given index value j can be associated to at most N Class-Type
      values CTi (i =< N) of the EXTENDED_CLASSTYPE object.  This
|     association applies when a set of one or more CTis maps to a
      single (shared) BW profile.  An example of value setting consists
      in assigning an arbitrary value comprised within the range
      [0x08,0xF8] associated to a set of CTi, the values in the range
|     [0xF9,0xFF] being selected for reserved sets.  This allows mapping
      to one of 248 predefined CTi sets.


Notes
-----
Rationale:
a) consistent use of "CTi" -- 'i' essentially is a subscript index;
b) avoid ambiguity due to overlap in ranges given

[The first item is Editorial, but the second one clearly Technical;
 to simplify Errata management, only a single, combined report is
 submitted covering both.]

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. 

--------------------------------------
RFC6003 (draft-ietf-ccamp-ethernet-traffic-parameters-10)
--------------------------------------
Title               : Ethernet Traffic Parameters
Publication Date    : October 2010
Author(s)           : D. Papadimitriou
Category            : PROPOSED STANDARD
Source              : Common Control and Measurement Plane
Area                : Routing
Stream              : IETF
Verifying Party     : IESG