[I2nsf] comments about I2NSF framework draft://答复: Progress with draft-ietf-i2nsf-framework-05

Hi Adrian, I2NSFers,
I reviewed the latest draft again and thinks it's in a very good shape now. So, it can be a foundation for all the other drafts.

Of course, I also have some comments about it as below:
1. nits: P18 " Table 1: Subject Capability Index " should change to " Table 1: Packet Content Matching Capability Index ",  P19, " Table 2: Object Capability Index " should change to " Table 2: context matching Capability Index ";
2. Section 11 of Security Considerations: this section is a little bit simple without considering the possible threats like: unauthenticated connections between users and controller, and between controller and NSFs, DoS attacks from malicious users or NSFs, etc;
3. question: should section 7.3 move to the I2NSF gap analysis draft?
4. I think remote attestation function should be described as a part into the whole I2NSF framework;
5. Section 3.2, by my understanding, notification is just part of the monitor functions, such as: syslog, netconf. Is it necessary to divide them into two interfaces?

B.R.
Frank

-----邮件原件-----
发件人: I2nsf [mailto:i2nsf-bounces@ietf.org] 代表 Adrian Farrel
发送时间: 2017年5月19日 1:49
收件人: i2nsf@ietf.org
主题: [I2nsf] Progress with draft-ietf-i2nsf-framework-05

Hi WG,

I am about to do a document shepherd review prior to starting a WG last call. In conversation with Linda just now I think I spotted a few areas where I am going to make chunky suggestions for additional text, but overall the document looks sound.

If you care deeply about this work and haven't looked at the framework for a while, now would be a good time. Don't wait for WG last call.

Thanks,
Adrian

_______________________________________________
I2nsf mailing list
I2nsf@ietf.org
https://www.ietf.org/mailman/listinfo/i2nsf