datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Definition of Managed Objects for SAVI Protocol
draft-an-savi-mib-06

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-12-17
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

SAVI                                                               C. An
Internet-Draft                                                   J. Yang
Intended status: Informational                                     J. Wu
Expires: June 20, 2014                                             J. Bi
                                                                  CERNET
                                                       December 17, 2013

            Definition of Managed Objects for SAVI Protocol
                          draft-an-savi-mib-06

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it defines objects for managing SAVI (Source Address
   Validation Improvements) protocol instance.

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 June 20, 2014.

Copyright Notice

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

An, et al.                Expires June 20, 2014                 [Page 1]
Internet-Draft                  SAVI-MIB                   December 2013

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  The Internet-Standard Management Framework . . . . . . . . . .  3
   3.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   4.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   5.  Structure of the MIB Module  . . . . . . . . . . . . . . . . .  4
     5.1.  The SAVI System Table  . . . . . . . . . . . . . . . . . .  4
     5.2.  The SAVI Port Table  . . . . . . . . . . . . . . . . . . .  5
     5.3.  The SAVI Binding Table . . . . . . . . . . . . . . . . . .  6
     5.4.  The SAVI Filtering Table . . . . . . . . . . . . . . . . .  7
   6.  Textual Conventions  . . . . . . . . . . . . . . . . . . . . .  8
   7.  Relationship to Other MIB Modules  . . . . . . . . . . . . . .  8
     7.1.  Relationship to the INET-ADDRESS-MIB . . . . . . . . . . .  8
     7.2.  Relationship to the IF-MIB . . . . . . . . . . . . . . . .  8
     7.3.  MIB modules required for IMPORTS . . . . . . . . . . . . .  9
   8.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  9
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 23
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 24
   11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 24
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 24
     12.2. Informative References . . . . . . . . . . . . . . . . . . 25
     12.3. URL References . . . . . . . . . . . . . . . . . . . . . . 26
   Appendix A.  Change Log  . . . . . . . . . . . . . . . . . . . . . 26
   Appendix B.  Open Issues . . . . . . . . . . . . . . . . . . . . . 27

An, et al.                Expires June 20, 2014                 [Page 2]
Internet-Draft                  SAVI-MIB                   December 2013

1.  Introduction

   The Source Address Validation Improvement protocol was developed to
   complement ingress filtering with finer-grained, standardized IP
   source address validation(refer to [RFC7039]).A SAVI protocol
   instance is located on the path of hosts' packets, enforcing the
   hosts' use of legitimate IP source addresses.

   SAVI protocol determines whether the IP address obtaining process is
   legitimate according to IP address assignment method.  For links with

[include full document text]