Subject: [Dime] Fwd: New Version Notification for draft-campbell-dime-overload-issues-01.txt

From: Ben Campbell <[email-masked]>
Date: Mon, 15 Jul 2013 16:54:50 -0500

Hi Everyone,

I just submitted an update to my Diameter overload issues draft. The changes were mostly about organization and clarification:

1) Switched the section order to emphasize the non-adjacent overload reporting discussion. 

2) Gave up on trying to fit the scope types into a taxonomy. That seemed to create more confusion than clarity in the previous version.

3) Added a scope-type summary table.

4) Various editorial and clarification changes.

Thanks!

Ben.

Begin forwarded message:

> From: [email-masked]
> Subject: New Version Notification for draft-campbell-dime-overload-issues-01.txt
> Date: July 15, 2013 4:49:25 PM CDT
> To: Ben Campbell <[email-masked]>
> 
> 
> A new version of I-D, draft-campbell-dime-overload-issues-01.txt
> has been successfully submitted by Ben Campbell and posted to the
> IETF repository.
> 
> Filename:	 draft-campbell-dime-overload-issues
> Revision:	 01
> Title:		 Diameter Overload Control Solution Issues
> Creation date:	 2013-07-15
> Group:		 Individual Submission
> Number of pages: 20
> URL:             http://www.ietf.org/internet-drafts/draft-campbell-dime-overload-issues-01.txt
> Status:          http://datatracker.ietf.org/doc/draft-campbell-dime-overload-issues
> Htmlized:        http://tools.ietf.org/html/draft-campbell-dime-overload-issues-01
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-campbell-dime-overload-issues-01
> 
> Abstract:
>   The Diameter Maintenance and Extensions (DIME) working group has
>   undertaken an "overload control" work item, with the goal of
>   standardizing a mechanism to allow Diameter nodes to report overload
>   information among themselves.  Requirements currently include, among
>   others, the need to accurately report the scope of overload
>   conditions, and the ability to report overload information between
>   nodes that are not directly connected at the transport layer.  These
>   requirements introduce complex issues.  This document describes those
>   issues, in the hope that it will assist the working group's decision
>   process.
> 
> 
> 
> 
> The IETF Secretariat
>