Re: [Dime] Fwd: New Version Notification for draft-donovan-dime-drmp-00.txt

I am finally looking at this document in detail.

At the highest level, what strikes me is that it doesn't have a lot of 
specificity on the requirements it is intended to meet.

Since you reference the analogy with SIP RPH (RFC4412), it might make 
sense to look at the requirements specs that led to RPH (RFC -3487 
“Requirements for Resource Priority Mechanisms for the Session Initiation 
Protocol (SIP)” and RFC-3689 “ETS General Requirements” - which is more 
generally about priority marking), and see which, if any, are relevant for 
Diameter.

Janet

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to 
any order or other contract unless pursuant to explicit written agreement 
or government initiative expressly permitting the use of e-mail for such 
purpose.

Steve Donovan <srdonovan@usdonovans.com> 
Sent by: "DiME" <dime-bounces@ietf.org>
03/06/2015 11:52 AM

To
"dime@ietf.org" <dime@ietf.org>
cc

Subject
[Dime] Fwd: New Version Notification for draft-donovan-dime-drmp-00.txt

All,

I have submitted a draft proposing work on defining Diameter routing 
message priority.  The primary use case for the draft is to give the 
ability to mark different requests with different priorities, giving 
Diameter nodes making DOIC throttling decisions additional information on 
which requests should be throttled first.

The draft outlines a number of considerations on the design of the 
mechanism, should the working group decide to take on the work.

I will be requesting adding this as a DIME working group milestone at the 
Dallas IETF meeting.

Regards,

Steve

-------- Forwarded Message -------- 
Subject: 
New Version Notification for draft-donovan-dime-drmp-00.txt
Date: 
Fri, 06 Mar 2015 08:47:36 -0800
From: 
internet-drafts@ietf.org
To: 
Steve Donovan <srdonovan@usdonovans.com>, Steve Donovan 
<srdonovan@usdonovans.com>

A new version of I-D, draft-donovan-dime-drmp-00.txt
has been successfully submitted by Steve Donovan and posted to the
IETF repository.

Name:                            draft-donovan-dime-drmp
Revision:                00
Title:                           Diameter Routing Message Priority
Document date:           2015-03-06
Group:                           Individual Submission
Pages:                           11
URL:            
http://www.ietf.org/internet-drafts/draft-donovan-dime-drmp-00.txt
Status:         https://datatracker.ietf.org/doc/draft-donovan-dime-drmp/
Htmlized:       http://tools.ietf.org/html/draft-donovan-dime-drmp-00

Abstract:
   When making routing and resource allocation decisions, Diameter nodes
   currently have no generic mechanism to determine the relative
   priority of Diameter requests.  This document defines a mechanism to
   allow Diameter endpoints to indicate the relative priority of
   Diameter requests/transactions/messages.  With this information
   Diameter nodes can factor the relative priority of
   requests/transactions/messages into routing, resource allocation and
   overload abatement decisions.

Please note that it may take a couple of minutes from the time of 
submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime