Re: [Dime] Ben Campbell's No Objection on draft-ietf-dime-congestion-flow-attributes-01: (with COMMENT)

"Ben Campbell" <ben@nostrum.com> Thu, 02 July 2015 22:46 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 EDB451AC449; Thu, 2 Jul 2015 15:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 ykNeydcEEjOz; Thu, 2 Jul 2015 15:46:18 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBD121AC40F; Thu, 2 Jul 2015 15:46:18 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t62Mk7HY005384 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 2 Jul 2015 17:46:18 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: Ben Campbell <ben@nostrum.com>
To: "Bertz, Lyle T [CTO]" <Lyle.T.Bertz@sprint.com>
Date: Thu, 02 Jul 2015 17:46:07 -0500
Message-ID: <C1ACF798-E72E-43DB-89D2-CAAA23C392F7@nostrum.com>
In-Reply-To: <7c2281e81c8c4f7592d8fcd8478211bd@PLSWE13M07.ad.sprint.com>
References: <20150609185615.7145.32430.idtracker@ietfa.amsl.com> <7c2281e81c8c4f7592d8fcd8478211bd@PLSWE13M07.ad.sprint.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.1r5084)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/5WyG_tCYAHeQoJzoYHyKdvGid_w>
Cc: "dime-chairs@ietf.org" <dime-chairs@ietf.org>, "dime@ietf.org" <dime@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [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
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 02 Jul 2015 22:46:20 -0000

Thanks for the response. I've removed sections for points that do not 
seem to need further discussion.

Ben.

On 15 Jun 2015, at 11:43, Bertz, Lyle T [CTO] wrote:

[...]

>
> substantive:
>
> -- Abstract: I concur with Stephen that the abstract doesn't really 
> address the heart of the matter. (It also seems longer than needed.)
>
>>>>> We responded to Stephen's comments regarding the intro.  If you 
>>>>> could give your feedback on that thread it would be much 
>>>>> appreciated.

The first paragraph of the abstract in version 2 is better. If it were 
me, I'd move the rest to the introduction, if they are not already 
covered, and keep the abstract to one paragraph. But that's up to you.


>
> --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.)
>
>>>>> Ok.  Bigger update here.

[...]

The new security considerations are considerably improved, thanks!

[...]