BGP Model for Service Provider Networks
draft-ietf-idr-bgp-model-03

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03

draft-ietf-idr-bgp-model-03.txt:
xym 0.4:
Extracting 'ietf-bgp@2018-05-09.yang'
   Removed 0 empty lines
Extracting 'ietf-bgp-common@2018-05-09.yang'
   Removed 0 empty lines
Extracting 'ietf-bgp-common-multiprotocol@2018-05-09.yang'
   Removed 0 empty lines
Extracting 'ietf-bgp-common-structure@2018-05-09.yang'
   Removed 1 empty lines
Extracting 'ietf-bgp-peer-group@2018-05-09.yang'
   Removed 0 empty lines
Extracting 'ietf-bgp-neighbor@2018-05-09.yang'
   Removed 0 empty lines
Extracting 'ietf-bgp-global@2018-05-09.yang'
   Removed 0 empty lines
Extracting 'ietf-bgp-types@2018-05-09.yang'
   Removed 1 empty lines
Extracting 'ietf-bgp-policy@2018-05-09.yang'
   Removed 2 empty lines


ietf-bgp-common-multiprotocol@2018-05-09.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
err : Unable to parse submodule, parse the main module instead.


ietf-bgp-policy@2018-05-09.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
err : Data model "ieee802-dot1q-types" not found.
err : Importing "ieee802-dot1q-types" module into "ietf-if-l3-vlan" failed.
err : Module "ietf-if-l3-vlan" parsing failed.
err : Importing "ietf-if-l3-vlan" module into "ietf-routing-policy" failed.
err : Module "ietf-routing-policy" parsing failed.
err : Importing "ietf-routing-policy" module into "ietf-bgp-policy" failed.
err : Module "ietf-bgp-policy" parsing failed.


ietf-bgp-neighbor@2018-05-09.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
err : Unable to parse submodule, parse the main module instead.


ietf-bgp-peer-group@2018-05-09.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
err : Unable to parse submodule, parse the main module instead.


ietf-bgp-types@2018-05-09.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors


ietf-bgp-global@2018-05-09.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
err : Unable to parse submodule, parse the main module instead.


ietf-bgp-common@2018-05-09.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
err : Unable to parse submodule, parse the main module instead.


ietf-bgp-common-structure@2018-05-09.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
err : Unable to parse submodule, parse the main module instead.


ietf-bgp@2018-05-09.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
err : Data model "ieee802-dot1q-types" not found.
err : Importing "ieee802-dot1q-types" module into "ietf-if-l3-vlan" failed.
err : Module "ietf-if-l3-vlan" parsing failed.
err : Importing "ietf-if-l3-vlan" module into "ietf-routing-policy" failed.
err : Module "ietf-routing-policy" parsing failed.
err : Importing "ietf-routing-policy" module into "ietf-bgp" failed.
err : Module "ietf-bgp" parsing failed.

Interdomain Routing                                             K. Patel
Internet-Draft                                                    Arrcus
Intended status: Standards Track                         M. Jethanandani
Expires: November 11, 2018
                                                                S. Hares
                                                                  Huawei
                                                            May 10, 2018

                BGP Model for Service Provider Networks
                      draft-ietf-idr-bgp-model-03

Abstract

   This document defines a YANG data model for configuring and managing
   BGP, including protocol, policy, and operational aspects based on
   data center, carrier and content provider operational requirements.

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 https://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 November 11, 2018.

Copyright Notice

   Copyright (c) 2018 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
   (https://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

Patel, et al.           Expires November 11, 2018               [Page 1]
Internet-Draft                  BGP Model                       May 2018

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Goals and approach  . . . . . . . . . . . . . . . . . . .   2
   2.  Model overview  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  BGP protocol configuration  . . . . . . . . . . . . . . .   4
     2.2.  Policy configuration overview . . . . . . . . . . . . . .   6
   3.  Relation to other YANG data models  . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  URI Registration  . . . . . . . . . . . . . . . . . . . .   8
     5.2.  YANG Module Name Registration . . . . . . . . . . . . . .   8
   6.  YANG modules  . . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  BGP main module and submodule for base items  . . . . . . . .  10
   8.  BGP types . . . . . . . . . . . . . . . . . . . . . . . . . .  49
   9.  BGP policy data . . . . . . . . . . . . . . . . . . . . . . .  58
   10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  72
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  72
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  72
     12.1.  Normative references . . . . . . . . . . . . . . . . . .  72
     12.2.  Informative references . . . . . . . . . . . . . . . . .  74
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  74

1.  Introduction

   This document describes a YANG [RFC7950] data model for the BGP
   [RFC4271] protocol, including various protocol extensions, policy
   configuration, as well as defining key operational state data.  The
   model is intended to be vendor-neutral, in order to allow operators
   to manage BGP configuration in heterogeneous environments with
   routers supplied by multiple vendors.  The model is also intended to
   be readily mapped to existing implementations to facilitate support
   from as large a set of routing hardware and software vendors as
   possible.

1.1.  Goals and approach

   The model covers the base BGP features that are deployed across major
   implementations and the common BGP configurations in use across a
   number of operator network deployments.  In particular, this model
   attempts to cover BGP features defined in BGP [RFC4271], BGP
   Communities Attribute [RFC1997], BGP Route Reflection [RFC4456],
   Multiprotocol Extensions for BGP-4 [RFC4760], Autonomous System
   Confederations for BGP [RFC5065], BGP Route Flap Damping [RFC2439],

Patel, et al.           Expires November 11, 2018               [Page 2]