Network Access Control List (ACL) YANG Data Model
draft-ietf-netmod-acl-model-00

The information below is for an old version of the document
Document Type Active Internet-Draft (netmod WG)
Last updated 2014-11-11
Replaces draft-bogdanovic-netmod-acl-model
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Jan 2018 - Submit draft-ietf-ne... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
NETMOD WG                                                  D. Bogdanovic
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                           K. Sreenivasa
Expires: May 10, 2015                      Brocade Communications System
                                                                L. Huang
                                                                D. Blair
                                                           Cisco Systems
                                                        November 6, 2014

           Network Access Control List (ACL) YANG Data Model
                     draft-ietf-netmod-acl-model-00

Abstract

   This document describes a data model of Access Control List (ACL)
   basic building blocks.

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 10, 2015.

Copyright Notice

   Copyright (c) 2014 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
   (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

Bogdanovic, et al.        Expires May 10, 2015                  [Page 1]
Internet-Draft               ACL YANG model                November 2014

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Definitions and Acronyms  . . . . . . . . . . . . . . . .   3
   2.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Design of the ACL Model . . . . . . . . . . . . . . . . . . .   3
     3.1.  ACL Modules . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  ACL YANG Models . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  IETF-ACL module . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Packet Header module  . . . . . . . . . . . . . . . . . .  10
     4.3.  A company proprietary module example  . . . . . . . . . .  15
     4.4.  An ACL Example  . . . . . . . . . . . . . . . . . . . . .  17
   5.  Example of extending existing model for route filtering . . .  18
   6.  Linux nftables  . . . . . . . . . . . . . . . . . . . . . . .  20
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  22
   10. Change log [RFC Editor: Please remove]  . . . . . . . . . . .  22
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  22
     11.2.  Informative References . . . . . . . . . . . . . . . . .  22
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23

1.  Introduction

   Access Control List (ACL) is one of the basic elements to configure
   device forwarding behavior.  It is used in many networking concepts
   such as Policy Based Routing, Firewalls etc.

   An ACL is an ordered set of rules that is used to filter traffic on a
   networking device.  Each rule is represented by an Access Control
   Entry (ACE).

   Each ACE has a group of match criteria and a group of action
   criteria.

   The match criteria consist of a tuple of packet header match criteria
   and metadata match criteria.

   o  Packet header matches apply to fields visible in the packet such
      as address or class of service or port numbers.

   o  Metadata matches apply to fields associated with the packet but
      not in the packet header such as input interface or overall packet
      length

Bogdanovic, et al.        Expires May 10, 2015                  [Page 2]
Internet-Draft               ACL YANG model                November 2014

   The actions specify what to do with the packet when the matching
   criteria is met.  These actions are any operations that would apply
   to the packet, such as counting, policing, or simply forwarding.The
Show full document text