[radext] [Errata Verified] RFC8045 (5009)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 27 July 2017 14:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DA65131FF1; Thu, 27 Jul 2017 07:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 PqRlJKTG-5xm; Thu, 27 Jul 2017 07:00:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51F17131C8F; Thu, 27 Jul 2017 07:00:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9C48BB80CF9; Thu, 27 Jul 2017 07:00:14 -0700 (PDT)
To: andrew.feren@plixer.com, dean.cheng@huawei.com, jouni.nospam@gmail.com, mohamed.boucadair@orange.com, ssenthil@cisco.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: bclaise@cisco.com, iesg@ietf.org, radext@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20170727140014.9C48BB80CF9@rfc-editor.org>
Date: Thu, 27 Jul 2017 07:00:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/irWm3kEukuOFB6iQ-mzUm0e65WA>
Subject: [radext] [Errata Verified] RFC8045 (5009)
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jul 2017 14:00:27 -0000

The following errata report has been verified for RFC8045,
"RADIUS Extensions for IP Port Configuration and Reporting". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5009

--------------------------------------
Status: Verified
Type: Technical

Reported by: Andrew Feren <andrew.feren@plixer.com>
Date Reported: 2017-05-02
Verified by: Benoit Claise (IESG)

Section: 7.1

Original Text
-------------
   o  sourceTransportPortsLimit:

      *  Name: sourceTransportPortsLimit

      *  Element ID: 458

      *  Description: This Information Element contains the maximum
         number of IP source transport ports that can be used by an end
         user when sending IP packets; each user is associated with one
         or more (source) IPv4 or IPv6 addresses.  This Information
         Element is particularly useful in address-sharing deployments
         that adhere to REQ-4 of [RFC6888].  Limiting the number of
         ports assigned to each user ensures fairness among users and
         mitigates the denial-of-service attack that a user could launch
         against other users through the address-sharing device in order
         to grab more ports.

      *  Data type: unsigned16

      *  Data type semantics: totalCounter

Corrected Text
--------------
   o  sourceTransportPortsLimit:

      *  Name: sourceTransportPortsLimit

      *  Element ID: 458

      *  Description: This Information Element contains the maximum
         number of IP source transport ports that can be used by an end
         user when sending IP packets; each user is associated with one
         or more (source) IPv4 or IPv6 addresses.  This Information
         Element is particularly useful in address-sharing deployments
         that adhere to REQ-4 of [RFC6888].  Limiting the number of
         ports assigned to each user ensures fairness among users and
         mitigates the denial-of-service attack that a user could launch
         against other users through the address-sharing device in order
         to grab more ports.

      *  Data type: unsigned16

      *  Data type semantics: quantity

Notes
-----
Only change is 

      *  Data type semantics: totalCounter
to
      *  Data type semantics: quantity

The description is pretty clear that this IE is a maximum value and not a counter.

--------------------------------------
RFC8045 (draft-ietf-radext-ip-port-radius-ext-17)
--------------------------------------
Title               : RADIUS Extensions for IP Port Configuration and Reporting
Publication Date    : January 2017
Author(s)           : D. Cheng, J. Korhonen, M. Boucadair, S. Sivakumar
Category            : PROPOSED STANDARD
Source              : RADIUS EXTensions
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG