[Dime] Document Action: 'AVP Level Security for Non-neighboring Diameter Nodes: Scenarios and Requirements' to Informational RFC (draft-ietf-dime-e2e-sec-req-05.txt)

The IESG <iesg-secretary@ietf.org> Fri, 22 July 2016 09:58 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
Message-ID: <20160722095804.12182.70157.idtracker@ietfa.amsl.com>
Date: Fri, 22 Jul 2016 02:58:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/KB49Yc2yYj2y6kuuCrByp6EcgNw>
Cc: draft-ietf-dime-e2e-sec-req@ietf.org, dime-chairs@ietf.org, dime@ietf.org, The IESG <iesg@ietf.org>, rfc-editor@rfc-editor.org
Subject: [Dime] Document Action: 'AVP Level Security for Non-neighboring Diameter Nodes: Scenarios and Requirements' to Informational RFC (draft-ietf-dime-e2e-sec-req-05.txt)

The IESG has approved the following document:
- 'AVP Level Security for Non-neighboring Diameter Nodes: Scenarios and
   Requirements'
  (draft-ietf-dime-e2e-sec-req-05.txt) as Informational RFC

This document is the product of the Diameter Maintenance and Extensions
Working Group.

The IESG contact persons are Stephen Farrell, Benoit Claise and Joel
Jaeggli.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dime-e2e-sec-req/




Summary

The document shepherd is Lionel Morand. The responsible Area Director is 
Stephen Farrell.

If Diameter provides a hop-by-hop security (using TLS, DTLS or IPSec) 
between peers, the Diameter base protocol does not provide a mechanism 
for end-to-end security.

This document describes a set of requirements for providing Diameter 
security at the level of individual Attribute-Value Pairs.

Intended Status: Informational
This document will be used to evaluate future candidate solutions.

[Dime] Document Action: 'AVP Level Security for N… The IESG