Framework for Interface to Network Security Functions
draft-ietf-i2nsf-framework-09
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (i2nsf WG) | |
Last updated | 2017-11-12 (latest revision 2017-10-10) | ||
Replaces | draft-merged-i2nsf-framework | ||
Stream | IETF | ||
Intended RFC status | Informational | ||
Formats | pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Yoav Nir | ||
Shepherd write-up | Show (last changed 2017-10-11) | ||
IESG | IESG state | IESG Evaluation::AD Followup | |
Consensus Boilerplate | Yes | ||
Telechat date |
Needs a YES. |
||
Responsible AD | Kathleen Moriarty | ||
Send notices to | "Adrian Farrel" <adrian@olddog.co.uk>, Yoav Nir <ynir.ietf@gmail.com>, Adrian Farrel <adrian@olddog.co.uk> | ||
IANA | IANA review state | Version Changed - Review Needed |
I2NSF D. Lopez Internet-Draft Telefonica I+D Intended status: Informational E. Lopez Expires: May 12, 2018 Curveball Networks L. Dunbar J. Strassner Huawei R. Kumar Juniper Networks November 12, 2017 Framework for Interface to Network Security Functions draft-ietf-i2nsf-framework-09 Abstract This document describes the framework for the Interface to Network Security Functions (I2NSF), and defines a reference model (including major functional components) for I2NSF. Network security functions (NSFs) are packet-processing engines that inspect and optionally modify packets traversing networks, either directly or in the context of sessions to which the packet is associated. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on May 12, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents Lopez, et al. Expires May 12, 2018 [Page 1] Internet-Draft I2NSF Framework November 2017 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions used in this document . . . . . . . . . . . . . . 3 2.1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 3. I2NSF Reference Model . . . . . . . . . . . . . . . . . . . . 4 3.1. I2NSF Consumer-Facing Interface . . . . . . . . . . . . . 6 3.2. I2NSF NSF-Facing Interface . . . . . . . . . . . . . . . . 6 3.3. I2NSF Registration Interface . . . . . . . . . . . . . . . 7 4. Threats Associated with Externally Provided NSFs . . . . . . . 7 5. Avoiding NSF Ossification . . . . . . . . . . . . . . . . . . 8 6. The Network Connecting I2NSF Components . . . . . . . . . . . 9 6.1. Network Connecting I2NSF Users and I2NSF Controller . . . 9 6.2. Network Connecting the Controller and NSFs . . . . . . . 10 6.3. Interface to vNSFs . . . . . . . . . . . . . . . . . . . . 11 6.4. Consistency . . . . . . . . . . . . . . . . . . . . . . . 12 7. I2NSF Flow Security Policy Structure . . . . . . . . . . . . . 12 7.1. Customer-Facing Flow Security Policy Structure . . . . . . 12 7.2. NSF-Facing Flow Security Policy Structure . . . . . . . . 13 7.3. Differences from ACL Data Models . . . . . . . . . . . . . 15 8. Capability Negotiation . . . . . . . . . . . . . . . . . . . . 16 9. Registration Considerations . . . . . . . . . . . . . . . . . 16 9.1. Flow-Based NSF Capability Characterization . . . . . . . . 16 9.2. Registration Categories . . . . . . . . . . . . . . . . . 17 10. Manageability Considerations . . . . . . . . . . . . . . . . 20 11. Security Considerations . . . . . . . . . . . . . . . . . . 21 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 14.1. Normative References . . . . . . . . . . . . . . . . . . . 21 14.2. Informative References . . . . . . . . . . . . . . . . . . 22Show full document text