Document Action: 'Diameter Policy Processing Application' to Informational RFC

The IESG <iesg-secretary@ietf.org> Thu, 06 March 2008 20:11 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5EDAC3A6AA6; Thu, 6 Mar 2008 12:11:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.062
X-Spam-Level:
X-Spam-Status: No, score=-101.062 tagged_above=-999 required=5 tests=[AWL=-0.763, BAYES_00=-2.599, MANGLED_SAVELE=2.3, 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 CTyFfooQNOrA; Thu, 6 Mar 2008 12:11:04 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 257443A6DAF; Thu, 6 Mar 2008 12:10:59 -0800 (PST)
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id E8DA13A6E45; Thu, 6 Mar 2008 12:10:57 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Diameter Policy Processing Application' to Informational RFC
Message-Id: <20080306201057.E8DA13A6E45@core3.amsl.com>
Date: Thu, 06 Mar 2008 12:10:57 -0800
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

The IESG has approved the following document:

- 'Diameter Policy Processing Application '
   <draft-brenner-dime-peem-01.txt> as an Informational RFC

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Dan Romascanu.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-brenner-dime-peem-01.txt

Technical Summary

   This document describes the need for a new IANA Diameter Command Code
   to be used in a vendor-specific new application for invocation of
   Policy Processing (Policy Evaluation, or Evaluation and Enforcement).
   This application is needed as one of the implementations of the Open
   Mobile Aliance (OMA) Policy Evaluation, Enforcement and Management
   (PEEM) enabler, namely for the PEM-1 interface used to send a
   request/responses for Policy Processing.

Working Group Summary

   This is an Area Director sponsored individual submission, which was 
   written following a discussion in the IESG about the best way to 
   support the allocation of the command code required by the OMA.  
   

Document Quality

    The original document that defines the new application was discussed
    and approved by the OMA. 

Personnel

    The sponsoring Area Director was Dan Romascanu. Hannes Tschofenig 
    reviewed the document on behalf of the Diameter Extensions (DIME) WG.

    The document was also reviewed by IANA. 

RFC Editor Note

    Please make the following change: 

OLD: 

5.1.  Command Codes

   This specification assigns the value TBD-Cmd-code from the Command
   Code namespace defined in [RFC3588].  See Section 5.4.1.3.1 of
   [PEM-1-TS] for the assignment of the TBD-Cmd-code.

5.2.  AVP Codes

   This specification assigns the value TBD-AVP-Code for the Policy-Data
   AVP, in the OMA Vendor-ID (PEN) AVP namespace.  See Section 5.4.1.3.3
   of [PEM-1-TS] for the assignment of the namespace in this
   specification.

5.3.  Application Identifier

   This specification uses the value 16777243 in the Application
   Identifier namespace as registered in IANA for the Policy Processing
   Application.  See Section 5.4.1.3 of [PEM-1-TS] for more information.

NEW: 

5.1.  Command Codes

   This specification assigns the value TBD-Cmd-code from the Command
   Code namespace defined in [RFC3588].  See Section 5.4.1.3.1 of
   [PEM-1-TS] for the assignment of the TBD-Cmd-code.

   Upon approval of this document, the IANA will make the 
   following assignments in the "Authentication, Authorization, 
   and Accounting
   (AAA) Parameters" registry located at
   http://www.iana.org/assignments/aaa-parameters
   sub-registry "Command Codes"

   Code Value          Name Reference
   --------------             ------------------------------- --------- 
  [TBD-Cmd-code]   PDR / PDA [RFC-brenner-dime-peem-01]

5.2.  AVP Codes

   This specification uses the value  1 for the Policy-Data
   AVP, in the OMA Vendor-ID (PEN) AVP namespace.  See Section 5.4.1.3.3
   of [PEM-1-TS] for the assignment of the namespace in this
   specification. No IANA Action is required. 

   

5.3.  Application Identifier

   This specification uses the value 16777243 in the Application
   Identifier namespace as registered in IANA for the Policy Processing
   Application.  See Section 5.4.1.3 of [PEM-1-TS] for more information.
   No IANA action is required.

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce