John, In the draft-ietf-i2nsf-terminology-02, you have
[cid:[email protected]] Can I2NSF controller also be the "Consumers of NSF data and services"? Will it be clearer to say that the interface is for expressing users or tenants (i.e. consumers) oriented policies or rules? Those policies may not use actual bits carried in data packets as criteria because packet headers might change when the user's applications migrate to different locations. One of the pain points expressed by the members of the ONUG (Open Network User Group) Software Defined Security Service group, which primarily consists of enterprises users, is the "policy lifetime management", i.e. they want to be able to specify security policies that won't need to be changed when their applications move (from on-premises to cloud, or from one cloud to another). As all other I2NSF drafts depend on the "draft-ietf-i2nsf-terminology" being complete (i.e. pass the WGLC), can you find time to address this as soon as possible? Thank you very much. Linda
_______________________________________________ I2nsf mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2nsf
