[Dime] Publication request for Diameter Priority Attribute Value Pairs - draft-ietf-dime-priority-avps-03.txt

<lionel.morand@orange-ftgroup.com> Thu, 31 March 2011 00:12 UTC

Return-Path: <lionel.morand@orange-ftgroup.com>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16E4728C1C5; Wed, 30 Mar 2011 17:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.248
X-Spam-Level:
X-Spam-Status: No, score=-103.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gGZ5OZpwZMuu; Wed, 30 Mar 2011 17:12:26 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 9DE3628C1B7; Wed, 30 Mar 2011 17:12:25 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 862BA858003; Thu, 31 Mar 2011 02:20:04 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id 78C13778002; Thu, 31 Mar 2011 02:20:04 +0200 (CEST)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Thu, 31 Mar 2011 02:14:01 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBEF38.89ACF7D8"
Date: Thu, 31 Mar 2011 02:14:00 +0200
Message-ID: <B11765B89737A7498AF63EA84EC9F5777355F5@ftrdmel1>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Publication request for Diameter Priority Attribute Value Pairs - draft-ietf-dime-priority-avps-03.txt
Thread-Index: Acvu5mQcGepS5GeSQMKNoT9Ozwe2ZgATeB9g
From: <lionel.morand@orange-ftgroup.com>
To: <iesg-secretary@ietf.org>
X-OriginalArrivalTime: 31 Mar 2011 00:14:01.0558 (UTC) FILETIME=[89940F60:01CBEF38]
Cc: dime@ietf.org, dime-chairs@tools.ietf.org
Subject: [Dime] Publication request for Diameter Priority Attribute Value Pairs - draft-ietf-dime-priority-avps-03.txt
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 31 Mar 2011 00:12:28 -0000

Dear Secretary,

 

This is a request for publication of
draft-ietf-dime-priority-avps-03.txt

as a standards track RFC.

Please find below the document shepherd proto write-up.

 

Best Regards.

 

Lionel

 

==============================================

 PROTO WRITEUP for draft-ietf-dime-priority-avps-03.txt

============================================== 

 

http://www.ietf.org/id/draft-ietf-dime-priority-avps-03.txt

 

 

  (1.a) Who is the Document Shepherd for this document? Has the

        Document Shepherd personally reviewed this version of the 

        document and, in particular, does he or she believe this 

        version is ready for forwarding to the IESG for publication? 

 

         --

         Lionel Morand (lionel.morand@orange-ftgroup.com)

         is the Document Shepherd, Dime co-chair. He has done a review

         on the document and believes it is ready to be forwarded to

         IESG for publication.

 

  (1.b) Has the document had adequate review both from key WG members 

        and from key non-WG members? Does the Document Shepherd have 

        any concerns about the depth or breadth of the reviews that 

        have been performed?  

 

         --

         The document has had an extensive review by the DIME WG. This 

         document has been also reviewed and discussed by people from
3GPP.

        The lastest version is the result of the consensus reached

         after discussion. 

                     

         The shepherd has reviewed the document himself and has no

         issue with it. Nor the shepherd has issues with the reviews

         done by others.

 

  (1.c) Does the Document Shepherd have concerns that the document 

        needs more review from a particular or broader perspective, 

        e.g., security, operational complexity, someone familiar with 

        AAA, internationalization or XML? 

 

         --

         No.

 

 

  (1.d) Does the Document Shepherd have any specific concerns or 

        issues with this document that the Responsible Area Director

        and/or the IESG should be aware of? For example, perhaps he 

        or she is uncomfortable with certain parts of the document, or 

        has concerns whether there really is a need for it. In any 

        event, if the WG has discussed those issues and has indicated 

        that it still wishes to advance the document, detail those 

        concerns here. Has an IPR disclosure related to this document 

        been filed? If so, please include a reference to the 

        disclosure and summarize the WG discussion and conclusion on 

        this issue. 

 

         --

         No.

 

 

  (1.e) How solid is the WG consensus behind this document? Does it 

        represent the strong concurrence of a few individuals, with 

        others being silent, or does the WG as a whole understand and 

        agree with it?   

 

         --

         There is Dime WG consensus behind the document.

 

 

  (1.f) Has anyone threatened an appeal or otherwise indicated extreme 

        discontent? If so, please summarise the areas of conflict in 

        separate email messages to the Responsible Area Director. (It 

        should be in a separate email because this questionnaire is 

        entered into the ID Tracker.) 

 

         --

         No.

 

  (1.g) Has the Document Shepherd personally verified that the 

        document satisfies all ID nits? (See the Internet-Drafts
Checklist 

        and http://tools.ietf.org/tools/idnits/). Boilerplate checks are


        not enough; this check needs to be thorough. Has the document 

        met all formal review criteria it needs to, such as the MIB 

        Doctor, media type and URI type reviews? 

 

         --

         The shepherd has checked the document with the idnits tool and

         found no critical issues. However several lines exceed the
maximum

         length of 72 characters.

 

         The document does not need MIB doctor review.

         The document does not contain any media and URI types.

 

  (1.h) Has the document split its references into normative and 

        informative? Are there normative references to documents that 

        are not ready for advancement or are otherwise in an unclear 

        state? If such normative references exist, what is the 

        strategy for their completion? Are there normative references 

        that are downward references, as described in [RFC3967]? If 

        so, list these downward references to support the Area 

        Director in the Last Call procedure for them [RFC3967]. 

 

         --

         References are split accordingly. There is a normative
reference 

         to a draft (draft-ietf-tsvwg-emergency-rsvp-14) but this draft
is already 

         in the RFC ed queue. There are no other references to documents
with 

         unclear status or are in progress.

 

  (1.i) Has the Document Shepherd verified that the document IANA 

        consideration section exists and is consistent with the body 

        of the document? If the document specifies protocol 

        extensions, are reservations requested in appropriate IANA 

        registries? Are the IANA registries clearly identified? If 

        the document creates a new registry, does it define the 

        proposed initial contents of the registry and an allocation 

        procedure for future registrations? Does it suggest a 

        reasonable name for the new registry? See [RFC5226]. If the 

        document describes an Expert Review process has Shepherd 

        conferred with the Responsible Area Director so that the IESG 

        can appoint the needed Expert during the IESG Evaluation? 

 

         --

         This document defines 10 new Diameter AVP codes and requests
IANA for

         code value assignment in an existing registry.

 

         This document defines several new Diameter AVPs. 

         IANA is requested to allocate values for the AVP codes.

         No new registry is defined..

 

 

  (1.j) Has the Document Shepherd verified that sections of the 

        document that are written in a formal language, such as XML 

        code, BNF rules, MIB definitions, etc., validate correctly in 

        an automated checker? 

 

         --

         Yes. Note that the ABNF used in this document follows the

         modified ABNF syntax defined in RFC3588.

         

         

  (1.k) The IESG approval announcement includes a Document 

        Announcement Write-Up. Please provide such a Document 

        Announcement Write-Up? Recent examples can be found in the

        "Action" announcements for approved documents. The approval 

        announcement contains the following sections: 

 

     Technical Summary 

 

         --

        

        This document defines Attribute-Value Pair (AVP) containers for
various

        priority parameters for use with Diameter and the AAA framework.
The

        parameters themselves are defined in several different protocols
that

        operate at either the network or application layer.

         

         

     Working Group Summary 

 

         ---

         The document was discussed for more than one year in the WG and


         the document captures the results of the collaborative WG work.

 

     Document Quality 

 

         ---

         The document is complete, straightforward, simple and
well-written.