BGP Link-State Information Distribution Implementation Report
draft-ietf-idr-ls-distribution-impl-01

Abstract

This document is an implementation report for the BGP Link-State Information Distribution protocol as defined in [I-D.ietf-idr-ls-distribution]. The editors did not verify the accuracy of the information provided by respondents. The respondents are experts with the implementations they reported on, and their responses are considered authoritative for the implementations for which their responses represent. Respondents were asked to only use the YES answer if the feature had at least been tested in the lab.

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 March 20, 2015.

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.

Table of Contents

• 1. Introduction
• 2. Implementation Forms
• 3. NLRI subtypes
• 4. Link NLRI TLV support
• 5. Node NLRI TLV support
• 6. Prefix NLRI TLV support
• 7. Interoperable Implementations
• 7.1. Cisco Implementation
• 7.2. Juniper Implementation
• 7.3. OpenDaylight Implementation
• 8. IANA Considerations
• 9. Security considerations
• 10. Acknowledgements
• 11. Informative References
• Authors' Addresses

1. Introduction

In order to share network link-state and traffic engineering information collected with external components using the BGP routing protocol a new BGP Network Layer Reachability Information (NLRI) encoding format is required.

This document provides an implementation report for the BGP Link-State Information Distribution NLRI Format as defined in [I-D.ietf-idr-ls-distribution].

The scope of the interoperability test is sucessful encoding and decoding of BGP-LS advertisements. No application specific logic has been verified.

The editors did not verify the accuracy of the information provided by respondents or by any alternative means. The respondents are experts with the implementations they reported on, and their responses are considered authoritative for the implementations for which their responses represent. Respondents were asked to only use the YES answer if the feature had at least been tested in the lab.

2. Implementation Forms

Contact and implementation information for person filling out this form:

IOS-XR

Name: Manish Bhardwaj
Email:manbhard@cisco.com
Vendor: Cisco Systems, Inc.
Release: IOS-XR
Protocol Role: Sender, Receiver, Originator

JUNOS

Name: Balaji Rajagopalan
Email: balajir@juniper.net
Vendor: Juniper Networks, Inc.
Release: JUNOS
Protocol Role: Sender, Receiver, Originator

OpenDaylight

Name: Dana Kutenicsova
Email: dkutenic@cisco.com
Vendor: OpenDaylight Project, Inc.
Release: ODL Hydrogen
Protocol Role: Receiver

3. NLRI subtypes

Does the implementation support the Network Layer Reachability (NLRI) subtypes as described in Section 3.2 of [I-D.ietf-idr-ls-distribution] ?

N1:

Node NLRI

N2:

Link NLRI

N3:

IPv4 Topology Prefix NLRI

N4:

IPv6 Topology Prefix NLRI

4. Link NLRI TLV support

Does the implementation support the TLVs described in Section 7 of [I-D.ietf-idr-ls-distribution] ?

TLV 256:

Local Node Descriptor

TLV 257:

Remote Node Descriptor

TLV 258:

Link Local/Remote Identifier

TLV 259:

IPv4 Interface address

TLV 260:

IPv4 Neighbor address

TLV 261:

IPv6 Interface address

TLV 262:

IPv6 Neighbor address

TLV 263:

Multi-Topology IDs

TLV 512:

Autonomous System

TLV 513:

BGP-LS Identifier

TLV 514:

Area ID

TLV 515:

IGP Router ID

TLV 1028:

IPv4 router-ID of Local Node

TLV 1029:

IPv6 router-ID of Local Node

TLV 1030:

IPv4 router-ID of Remote Node

TLV 1031:

IPv6 router-ID of Remote Node

TLV 1088:

Administrative group (color)

TLV 1089:

Maximum link bandwidth

TLV 1090:

Maximum reservable link bandwidth

TLV 1091:

Unreserved link bandwidth

TLV 1092:

TE default Metric

TLV 1093:

Link Protection Type

TLV 1094:

MPLS Protocol Mask

TLV 1095:

IGP Metric

TLV 1096:

Shared Risk Link Group

TLV 1097:

Opaque Link attribute

TLV 1098:

Link name attribute

5. Node NLRI TLV support

Does the implementation support the TLVs described in Section 7 of [I-D.ietf-idr-ls-distribution] ?

TLV 256:

Local Node Descriptor

TLV 263:

Multi-Topology IDs

TLV 512:

Autonomous System

TLV 513:

BGP-LS Identifier

TLV 514:

Area ID

TLV 515:

IGP Router ID

TLV 1024:

Node flag bits

TLV 1025:

Opaque Node properties

TLV 1026:

Node name

TLV 1027:

IS-IS Area Identifier

TLV 1028:

IPv4 router-ID of Local Node

TLV 1029:

IPv6 router-ID of Local Node

6. Prefix NLRI TLV support

Does the implementation support the TLVs described in Section 7 of [I-D.ietf-idr-ls-distribution] ?

TLV 256:

Local Node Descriptor

TLV 263:

Multi-Topology IDs

TLV 264:

OSPF route type

TLV 265:

IP Reachability information

TLV 1152:

IGP Flags

TLV 1153:

Route Tag

TLV 1154:

Extended Tag

TLV 1155:

Prefix Metric

TLV 1156:

OSPF Forwarding Address

TLV 1157:

Opaque Prefix Atrribute

7. Interoperable Implementations

List other implementations that you have tested interoperability of BGP-LS Protocol Implementation.

7.1. Cisco Implementation

Cisco: The Cisco Systems, Inc. IOS-XR implementation should be interoperable with other vendor BGP-LS Protocol implementations. In particular, we have tested our interoperability with Juniper's JUNOS implementation.

7.2. Juniper Implementation

Juniper: The Juniper Networks, Inc. JUNOS implementation should be interoperable with other vendor BGP-LS Protocol implementations. In particular, we have tested our interoperability with the Cisco Systems, Inc. IOS-XR implementation and the Opendaylight implementation.

7.3. OpenDaylight Implementation

Opendaylight: The Opendaylight implementation should be interoperable with other vendor BGP-LS Protocol implementations. In particular, we have tested our interoperability with Juniper's JUNOS implementation and the Cisco Systems, Inc. IOS-XR implementation. BGP receiver is implemented in the OpenDaylight Hydrogen release. BGP sender functionality is planned in the upcoming Helium release.

8. IANA Considerations

This document makes no request of IANA.

Note to RFC Editor: The IANA has requested that this section remain in the document upon publication as an RFC. This note to the RFC Editor, however, may be removed.

9. Security considerations

No new security issues are introduced by the BGP Link-State Information Distribution Protocol defined in [I-D.ietf-idr-ls-distribution].

10. Acknowledgements

The authors would like to thank Stefano Previdi and Jan Medved for their contributions to this document.

11. Informative References

Authors' Addresses