[Dime] Ben Campbell's No Objection on draft-ietf-dime-congestion-flow-attributes-01: (with COMMENT)
"Ben Campbell" <ben@nostrum.com> Tue, 09 June 2015 18:56 UTC
Return-Path: <ben@nostrum.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61E651B2E9E; Tue, 9 Jun 2015 11:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 XjhunUfhg6yH; Tue, 9 Jun 2015 11:56:16 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F41ED1B2E99; Tue, 9 Jun 2015 11:56:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Ben Campbell <ben@nostrum.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150609185615.7145.32430.idtracker@ietfa.amsl.com>
Date: Tue, 09 Jun 2015 11:56:15 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/Suvp3KYTaGillse-oIR2CFQntLU>
Cc: dime-chairs@ietf.org, dime@ietf.org
Subject: [Dime] Ben Campbell's No Objection on draft-ietf-dime-congestion-flow-attributes-01: (with COMMENT)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2015 18:56:17 -0000
Ben Campbell has entered the following ballot position for draft-ietf-dime-congestion-flow-attributes-01: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-dime-congestion-flow-attributes/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- This mostly looks good. I have a few comments that are not show stoppers: substantive: -- Abstract: I concur with Stephen that the abstract doesn't really address the heart of the matter. (It also seems longer than needed.) -- 5.2: I don’t see the Congestion-Treatment AVP actually used in the example. At least if it is, it’s not called out. I think it would be helpful to explicitly show it. Also, can you add a reference for Excess-Treatment? "If Excess-Treatment or Congestion-Treatment has occurred..." Does this mean “if the conditions associated with Excess-Treatment or Congestion-Treatment have occurred”, or “Excess-Treatment or Congestion-Treatment have been sent in a Diameter message”? --6, first sentence. I’d like to see a little more “show your work" here. These AVPs carry new kinds of content. That, in itself, might add new security considerations (e.g. is the content privacy-sensitive, especially damaging if tampered with, etc). Please consider adding a few sentences describing the new content, and why you believe that content does or does not have new security considerations. You kind of do that for ECN-IP-Codepoint and Congestion-Treatment, but I don't see anything for the other two new AVPs. (I'm probably the other person that Stephen mentioned consider such sentences as a red flag.) Editorial: -- Abstract: Please expand ECN and AVP on first mention (both in abstract and in body.) -- 3.2, first paragraph "In case..." I suggest either "If..." or "In the case that..." -- 5.1: There are several instances of "ECP-IP-Codepoint" that I assume should be "ECN..."
- [Dime] Ben Campbell's No Objection on draft-ietf-… Ben Campbell
- [Dime] Ben Campbell's No Objection on draft-ietf-… Ben Campbell
- Re: [Dime] Ben Campbell's No Objection on draft-i… Bertz, Lyle T [CTO]
- Re: [Dime] Ben Campbell's No Objection on draft-i… Ben Campbell