Security at the Attribute-Value Pair (AVP) Level for Non-neighboring Diameter Nodes: Scenarios and Requirements
draft-ietf-dime-e2e-sec-req-05

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: lionel.morand@orange.com, dime-chairs@ietf.org, draft-ietf-dime-e2e-sec-req@ietf.org, dime@ietf.org, "The IESG" <iesg@ietf.org>, rfc-editor@rfc-editor.org, stephen.farrell@cs.tcd.ie
Subject: 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/

Ballot Text

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.

RFC Editor Note