[PCN] [Technical Errata Reported] RFC5559 (3164)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 23 March 2012 20:54 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pcn@ietfa.amsl.com
Delivered-To: pcn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6812221E8085 for <pcn@ietfa.amsl.com>; Fri, 23 Mar 2012 13:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.455
X-Spam-Level:
X-Spam-Status: No, score=-102.455 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 C6kp5A8yevFf for <pcn@ietfa.amsl.com>; Fri, 23 Mar 2012 13:54:35 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id D93A621E804E for <pcn@ietf.org>; Fri, 23 Mar 2012 13:54:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 981B9B1E002; Fri, 23 Mar 2012 13:53:27 -0700 (PDT)
To: philip.eardley@bt.com, wes@mti-systems.com, ietfdbh@comcast.net, sob@harvard.edu, slblake@petri-meat.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20120323205327.981B9B1E002@rfc-editor.org>
Date: Fri, 23 Mar 2012 13:53:27 -0700
Cc: pcn@ietf.org, rfc-editor@rfc-editor.org
Subject: [PCN] [Technical Errata Reported] RFC5559 (3164)
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 20:54:36 -0000

The following errata report has been submitted for RFC5559,
"Pre-Congestion Notification (PCN) Architecture".

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

--------------------------------------
Type: Technical
Reported by: Bob Briscoe <bob.briscoe@bt.com>

Section: 4.2

Original Text
-------------
   o  Police - police, by dropping any packets received with a DSCP
      indicating PCN transport that do not belong to an admitted flow.
      (A prospective PCN-flow that is rejected could be blocked or
      admitted into a lower-priority behaviour aggregate.)


Corrected Text
--------------
   o  Police - drop or re-mark to a lower-priority behaviour aggregate
      i) packets received with a DSCP indicating PCN transport that do not
      belong to an admitted flow and ii) packets that are part of a flow
      that asked to be admitted as a PCN-flow but was rejected.


Notes
-----
In the original text the first sentence contradicts the parenthesis. It could be interpreted to mean that dropping is the only allowed policing action, whereas the parenthesis shows that downgrading was also considered appropriate.

Also the original text used the term 'blocking' as a different action to 'downgrading', whereas Section 3.6 just above this text has said '"Blocking" means it is dropped or downgraded to a lower-priority behaviour aggregate,...'

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. 

--------------------------------------
RFC5559 (draft-ietf-pcn-architecture-11)
--------------------------------------
Title               : Pre-Congestion Notification (PCN) Architecture
Publication Date    : June 2009
Author(s)           : P. Eardley, Ed.
Category            : INFORMATIONAL
Source              : Congestion and Pre-Congestion Notification
Area                : Transport
Stream              : IETF
Verifying Party     : IESG