Subject: [i2rs] Comments on draft-ietf-i2rs-security-environment-reqs-00

From: "Russ White" <[email-masked]>
Date: Sat, 30 Jan 2016 20:25:56 -0500

Y'all --

Some comments from my weekend fun time reading... Not really, but, you know.
These are all nits, but still might improve readability.

:-)

Russ

==
various I2RS Client, but additional mechanisms might eventually be required
so I2RS Client can

Client/Clients

This seems to be common throughout (?).

==
channel does not fulfill enough security requirements. For example, the it
should be able to reject

"it" can be removed.

==
However, such mechanism may

mechanism/mechanisms

==
all Applications: In the case the I2RS Agent has a single I2RS Client. Such
architecture results in I2RS Client

the/this, I think.

==
granted -- the default rule-- should be denied.

Spacing around the --'s

==
the various transaction they perform,

transaction/transactions

==
over the I2RS plane - like all the I2RS

Double dash, I think, to indicate an em?

==
Application SHOULD be provided means and methods...

This doesn't seem to be worded right -- perhaps inject a "the" after "be?"

==
6.2.1. DoS

DoS should be "Denial of Service" here.