[i2rs] I-D Action: draft-ietf-i2rs-protocol-security-requirements-12.txt
internet-drafts@ietf.org Mon, 26 September 2016 22:19 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i2rs@ietf.org
Delivered-To: i2rs@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1A812B01C; Mon, 26 Sep 2016 15:19:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147492836510.5000.17247455883069029938.idtracker@ietfa.amsl.com>
Date: Mon, 26 Sep 2016 15:19:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/04yRMKvP_8UczMCVaf1mXDGZWNY>
Cc: i2rs@ietf.org
Subject: [i2rs] I-D Action: draft-ietf-i2rs-protocol-security-requirements-12.txt
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Sep 2016 22:19:25 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Interface to the Routing System of the IETF. Title : I2RS Security Related Requirements Authors : Susan Hares Daniel Migault Joel Halpern Filename : draft-ietf-i2rs-protocol-security-requirements-12.txt Pages : 21 Date : 2016-09-26 Abstract: This presents security-related requirements for the I2RS protocol which provides a new interface to the routing system described in the I2RS architecture document (RFC7921). The I2RS protocol is a re-use protocol implemented by re-using portions of existing IETF protocols and adding new features to these protocols. The I2RS protocol re- uses security features of a secure transport (E.g. TLS, SSH, DTLS) such as encryption, message integrity, mutual peer authentication, and replay protection. The new security features I2RS adds are: a priority mechanism to handle multi-headed write transactions, an opaque secondary identifier which identifies an application using the I2RS client, and an extremely constrained read-only non-secure transport. This document provides the detailed requirements for these security features. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-i2rs-protocol-security-requirements/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-i2rs-protocol-security-requirements-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-i2rs-protocol-security-requirements-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [i2rs] I-D Action: draft-ietf-i2rs-protocol-secur… internet-drafts