[Dime] FW: Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS)

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 30 November 2011 15:55 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FAA521F8801 for <dime@ietfa.amsl.com>; Wed, 30 Nov 2011 07:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.249
X-Spam-Level:
X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 CiPo6hfL3vD1 for <dime@ietfa.amsl.com>; Wed, 30 Nov 2011 07:55:00 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id DF65D21F84B7 for <dime@ietf.org>; Wed, 30 Nov 2011 07:54:59 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArMAANxQ1k6HCzI1/2dsb2JhbABEhQOVbY8agQiBBYFyAQEBAQMSEQ0EUQYBCA0EBAEBAwIGBgwLAQICAwFEBwEBBQQBBBMIARmHbZg5hBSJbpFngTCGW4F/M2MEmjqMLg
X-IronPort-AV: E=Sophos;i="4.69,597,1315195200"; d="scan'208";a="317188014"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 30 Nov 2011 10:54:59 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 30 Nov 2011 10:43:14 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Wed, 30 Nov 2011 16:54:57 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0405AD5C19@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS)
Thread-Index: AcyvdwkxjsoVUpLUTVu5ZoopbiUlbQAAUUjA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: dime@ietf.org
Subject: [Dime] FW: Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Wed, 30 Nov 2011 15:55:02 -0000

Document editors and shepherd, 

Please address the issues raised by Robert Sparks in his DISCUSS. 

Thanks and Regards,

Dan




-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of Robert Sparks
Sent: Wednesday, November 30, 2011 5:45 PM
To: The IESG
Cc: dime-chairs@tools.ietf.org; draft-ietf-dime-priority-avps@tools.ietf.org
Subject: Robert Sparks' Discuss on draft-ietf-dime-priority-avps-05: (withDISCUSS)

Robert Sparks has entered the following ballot position for
draft-ietf-dime-priority-avps-05: Discuss

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 http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

The first paragraph of the Security Considerations section is unclear. It appears to instruct elements (not clear which elements) to ignore integrity protected values. Does it mean integrity protected values that fail integrity check? It indicates that protocol specific error messages should be sent when these values are ignored - which protocol(s)?  Is the paragraph trying to say something more than "local policy can override the policy requested by protocol messages"?