[i2rs] I-D Action: draft-keyupate-i2rs-bgp-usecases-02.txt

internet-drafts@ietf.org Wed, 04 June 2014 17:44 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3021A0254; Wed, 4 Jun 2014 10:44:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id marjetv_XMhN; Wed, 4 Jun 2014 10:44:24 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 502501A0306; Wed, 4 Jun 2014 10:44:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140604174423.25048.19110.idtracker@ietfa.amsl.com>
Date: Wed, 04 Jun 2014 10:44:23 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/7jlgq5UtFBtE1gR6aPOlXPMhgwc
Cc: i2rs@ietf.org
Subject: [i2rs] I-D Action: draft-keyupate-i2rs-bgp-usecases-02.txt
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 17:44:26 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Interface to the Routing System Working Group of the IETF.

        Title           : Use Cases for an Interface to BGP Protocol
        Authors         : Keyur Patel
                          Rex Fernando
                          Hannes Gredler
                          Shane Amante
                          Russ White
                          Susan Hares
	Filename        : draft-keyupate-i2rs-bgp-usecases-02.txt
	Pages           : 17
	Date            : 2014-06-04

Abstract:
   A network routing protocol like BGP is typically configured and
   analyzed through some form of Command Line Interface (CLI) or
   NETCONF.  These interactions to control BGP and diagnose its
   operation encompass: configuration of protocol parameters, display of
   protocol data, setting of certain protocol state and debugging of the
   protocol.

   Interface to the Routing System's (I2RS) Programmatic interfaces, as
   defined in draft-ietf-i2rs-architecture, provides an alternate way to
   control and diagnose the operation of the BGP protocol.  I2RS may be
   used for the configuration, manipulation, analyzing or collecting the
   protocol data.  This document describes set of use cases for which
   I2RS can be used for BGP protocol.  It is intended to provide a base
   for the solution draft describing a set of interfaces to the BGP
   protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-keyupate-i2rs-bgp-usecases/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-keyupate-i2rs-bgp-usecases-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-keyupate-i2rs-bgp-usecases-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/