IETF Logo Mail Archive

[radext] [Technical Errata Reported] RFC8045 (5009)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 02 May 2017 13:44 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 EE81A1316E8 for <radext@ietfa.amsl.com>; Tue, 2 May 2017 06:44:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.304
X-Spam-Level:
X-Spam-Status: No, score=-2.304 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 84G1bxGzdVVC for <radext@ietfa.amsl.com>; Tue, 2 May 2017 06:44:31 -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 E7D071314DE for <radext@ietf.org>; Tue, 2 May 2017 06:40:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2A74EB80E97; Tue, 2 May 2017 06:40:27 -0700 (PDT)
To: dean.cheng@huawei.com, jouni.nospam@gmail.com, mohamed.boucadair@orange.com, ssenthil@cisco.com, bclaise@cisco.com, warren@kumari.net, lionel.morand@orange.com, stefan.winter@restena.lu
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: andrew.feren@plixer.com, radext@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20170502134027.2A74EB80E97@rfc-editor.org>
Date: Tue, 02 May 2017 06:40:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/t9z-lU_nHcN4hNMdnG_PgQXWvfk>
X-Mailman-Approved-At: Tue, 02 May 2017 22:11:13 -0700
Subject: [radext] [Technical Errata Reported] 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: Tue, 02 May 2017 13:44:33 -0000

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

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

--------------------------------------
Type: Technical
Reported by: Andrew Feren <andrew.feren@plixer.com>

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.

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  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
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

v2.23.0 | Report a Bug | By Email