Requirements for Client-Facing Interface to Security Controller
draft-ietf-i2nsf-client-facing-interface-req-05

Document Type Expired Internet-Draft (i2nsf WG)
Last updated 2018-11-28 (latest revision 2018-05-27)
Replaces draft-kumar-i2nsf-client-facing-interface-req
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-i2nsf-client-facing-interface-req-05.txt

Abstract

This document captures requirements for Client-Facing interface to the Security Controller as defined by [RFC8327]. The interface is expressed using objects and constructs understood by Security Admin as opposed to vendor or device specific expressions associated with individual product and feature. This document identifies a broad set of requirements needed to express Security Policies based on User- constructs which are well understood by the User Community. This gives ability to decouple policy definition from policy enforcement on a specific security functional element, be it a physical or virtual.

Authors

Rakesh Kumar (rakeshkumarcloud@gmail.com)
Anil Lohiya (alohiya@juniper.net)
Dave Qi (dqi@bloomberg.net)
Nabil Bitar (nabil.bitar@nokia.com)
Senad Palislamovic (senad.palislamovic@nokia.com)
Liang Xia (frank.xialiang@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)