[Dime] Last Call: <draft-ietf-dime-e2e-sec-req-04.txt> (Diameter AVP Level Security End-to-End Security: Scenarios and Requirements) to Informational RFC

The IESG <iesg-secretary@ietf.org> Thu, 28 April 2016 14:08 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20160428140848.27837.40252.idtracker@ietfa.amsl.com>
Date: Thu, 28 Apr 2016 07:08:48 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/69CGNNp358QETcLNGzkQ3L9UpF4>
Cc: draft-ietf-dime-e2e-sec-req@ietf.org, dime@ietf.org, dime-chairs@ietf.org
Subject: [Dime] Last Call: <draft-ietf-dime-e2e-sec-req-04.txt> (Diameter AVP Level Security End-to-End Security: Scenarios and Requirements) to Informational RFC
Reply-To: ietf@ietf.org

The IESG has received a request from the Diameter Maintenance and
Extensions WG (dime) to consider the following document:
- 'Diameter AVP Level Security End-to-End Security: Scenarios and
   Requirements'
  <draft-ietf-dime-e2e-sec-req-04.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-05-12. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This specification discusses requirements for providing Diameter
   security at the level of individual Attribute-Value Pairs.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dime-e2e-sec-req/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dime-e2e-sec-req/ballot/


No IPR declarations have been submitted directly on this I-D.

[Dime] Last Call: <draft-ietf-dime-e2e-sec-req-04… The IESG