Subject: [appsdir] Fwd: Last Call: <draft-ietf-i2rs-protocol-security-requirements-06.txt> (I2RS Security Related Requirements) to Informational RFC

From: Eliot Lear <[email-masked]>
Date: Tue, 2 Aug 2016 12:15:39 +0200

Would anyone care to review draft-ietf-i2rs-protocol-security-requirements?

I think the key thing here is to confirm that none of the requirements
are impracticable in an application context.  This is a pretty short read.

Eliot

Subject: Last Call: <draft-ietf-i2rs-protocol-security-requirements-06.txt> (I2RS Security Related Requirements) to Informational RFC
From: The IESG <[email-masked]>
To: "IETF-Announce" <[email-masked]>
Cc: [email-masked], [email-masked], [email-masked], [email-masked]
Date: Mon, 01 Aug 2016 07:40:52 -0700
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>

The IESG has received a request from the Interface to the Routing System
WG (i2rs) to consider the following document:
- 'I2RS Security Related Requirements'
  <draft-ietf-i2rs-protocol-security-requirements-06.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
[email-masked] mailing lists by 2016-08-15. Exceptionally, comments may be
sent to [email-masked] instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

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

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-i2rs-protocol-security-requirements/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-i2rs-protocol-security-requirements/ballot/

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