ACL YANG model
draft-bogdanovic-netmod-acl-model-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-06-16
Replaced by draft-ietf-netmod-acl-model, rfc8519
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
NETMOD WG                                                  D. Bogdanovic
Internet-Draft                                          Juniper Networks
Intended status: Informational                             K. Sreenivasa
Expires: December 18, 2014                 Brocade Communications System
                                                                D. Blair
                                                           Cisco Systems
                                                           June 16, 2014

                             ACL YANG model
                  draft-bogdanovic-netmod-acl-model-00

Abstract

   This document describes information and 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 December 18, 2014.

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Bogdanovic, et al.      Expires December 18, 2014               [Page 1]
Internet-Draft               ACL YANG model                    June 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Definitions and Acronyms  . . . . . . . . . . . . . . . .   3
   2.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Design of the ACL Model . . . . . . . . . . . . . . . . . . .   4
     3.1.  ACL Modules . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  ACL YANG Models . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  IETF-ACL module . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Packet Header module  . . . . . . . . . . . . . . . . . .  10
     4.3.  A company proprietary module example  . . . . . . . . . .  13
     4.4.  An ACL Example  . . . . . . . . . . . . . . . . . . . . .  14
   5.  Linux nftables  . . . . . . . . . . . . . . . . . . . . . . .  15
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   9.  Change log [RFC Editor: Please remove]  . . . . . . . . . . .  16
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Access Control List (ACL) are 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 tuple of match criteria and metadata
   matching.

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

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

   The actions specify what to do with the packet when the matching
   criteria is met.  These can be any sort of thing from counting to
   policing or simply forwarding.The list of potential actions is
   endless depending on the innovations of the networked devices.

Bogdanovic, et al.      Expires December 18, 2014               [Page 2]
Internet-Draft               ACL YANG model                    June 2014

1.1.  Definitions and Acronyms

   ACE: Access Control Entry

   ACL: Access Control List

   AFI: Address Field Identifier

   ARP: Address Resolution Protocol

   CoS: Class of Service

   DSCP: Differentiated Services Code Point
Show full document text