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

"Susan Hares" <shares@ndzh.com> Wed, 04 June 2014 18:49 UTC

Return-Path: <shares@ndzh.com>
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 B673F1A03A1 for <i2rs@ietfa.amsl.com>; Wed, 4 Jun 2014 11:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no
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 EsgsRJKhu55R for <i2rs@ietfa.amsl.com>; Wed, 4 Jun 2014 11:49:47 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 64E831A0390 for <i2rs@ietf.org>; Wed, 4 Jun 2014 11:49:47 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.189.161;
From: Susan Hares <shares@ndzh.com>
To: i2rs@ietf.org
References: <20140604174423.25048.19110.idtracker@ietfa.amsl.com>
In-Reply-To: <20140604174423.25048.19110.idtracker@ietfa.amsl.com>
Date: Wed, 04 Jun 2014 14:49:29 -0400
Message-ID: <005101cf8025$b7cc2b70$27648250$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHsFk5zAvf2vS9rxXc9LGt7Dvw7qJsoHcbA
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
X-IsFriend: <shares@ndzh.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/ImNlK5lj7f2_qvxS50IkY_jyea8
Cc: "'Keyur Patel (keyupate)'" <keyupate@cisco.com>, Hannes Gredler <hannes@juniper.net>, Russ White <russw@riw.us>, 'Susan Hares' <skh@ndzh.com>, rex@cisco.com
Subject: [i2rs] FW: I-D Action: draft-keyupate-i2rs-bgp-usecases-02.txt
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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 18:49:48 -0000

Jeff and Ed: 

This updated draft has all the changes that Keyur Patel promised and updates
to the reference the current i2rs internet drafts.  

Would you please do a Working Group adoption call? 

Thank you, 
Sue Hares 


-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of
internet-drafts@ietf.org
Sent: Wednesday, June 04, 2014 1:44 PM
To: i-d-announce@ietf.org
Cc: i2rs@ietf.org
Subject: [i2rs] I-D Action: draft-keyupate-i2rs-bgp-usecases-02.txt


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/

_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs