Document Action: 'I2RS Security Related Requirements' to Informational RFC (draft-ietf-i2rs-protocol-security-requirements-17.txt)

The IESG <> Mon, 03 October 2016 17:15 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id D67DB12942F; Mon, 3 Oct 2016 10:15:35 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'I2RS Security Related Requirements' to Informational RFC (draft-ietf-i2rs-protocol-security-requirements-17.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 03 Oct 2016 10:15:35 -0700
Archived-At: <>
Cc:,,, The IESG <>,,
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 03 Oct 2016 17:15:36 -0000

The IESG has approved the following document:
- 'I2RS Security Related Requirements'
  (draft-ietf-i2rs-protocol-security-requirements-17.txt) as
Informational RFC

This document is the product of the Interface to the Routing System
Working Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah

A URL of this Internet Draft is:

Technical Summary

This presents security-related requirements for the I2RS protocol for
   mutual authentication, transport protocols, data transfer and

Working Group Summary

Working consensus for requirements was honed over 6 months (May -Nov 2015).
WG LC done with All of requirement drafts 10/6/2015 to 10/20/2015 

Document Quality

This draft comes out of discussion with the I2RS WG and
various security experts, and security directorate reviewers. 
The last SEC-DIR messages on this topic was:
last message: 

It has been reviewed by the NETCONF WG (July 2015, Nov 2015), and
all issues were declared resolved as of November 2015. 
 A significant number of vendors have indicated their plan to 
 expand existing protocols to create an IRS amalgamate protocol. 
 A list includes the following: Cisco, Juniper, Huawei, Ericsson, 
Google, Packetdesign (Client software) and others. 


Document shepherd:  Jeff Haas 
AD: Alia Atlas