< draft-walton-bgp-hostname-capability-01.txt   draft-walton-bgp-hostname-capability-02.txt >
Network Working Group D. Walton Network Working Group D. Walton
Internet-Draft D. Dutt Internet-Draft D. Dutt
Intended status: Standards Track Cumulus Networks Intended status: Standards Track Cumulus Networks
Expires: January 7, 2016 July 6, 2015 Expires: July 9, 2016 January 6, 2016
Hostname Capability for BGP Hostname Capability for BGP
draft-walton-bgp-hostname-capability-01 draft-walton-bgp-hostname-capability-02
Abstract Abstract
In this document, we introduce a new BGP capability that allows the In this document, we introduce a new BGP capability that allows the
advertisemnet of a BGP speaker's hostname. advertisemnet of a BGP speaker's hostname.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 7, 2016. This Internet-Draft will expire on July 9, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 15 skipping to change at page 3, line 15
4. Operation 4. Operation
The FQDN Capability SHOULD only be used for displaying the hostname The FQDN Capability SHOULD only be used for displaying the hostname
and/or domain name of a speaker in order to make troubleshooting and/or domain name of a speaker in order to make troubleshooting
easier. The hostname and domain name used are assumed to be easier. The hostname and domain name used are assumed to be
extracted from the hostname and domain name set on the device. While extracted from the hostname and domain name set on the device. While
there are other ways to potentially obtain the same information, there are other ways to potentially obtain the same information,
having standard BGP show commands use the hostname makes the use of having standard BGP show commands use the hostname makes the use of
this option quite powerful. this option quite powerful.
An example of showing hostname in various displays is show below in
the output of the summary of BGP peering relationships, the first
being the typical display today, and the second the display when
displaying hostnames is enabled:
cumulus@r1$ sudo cl-bgp summary
BGP router identifier 10.0.0.1, local AS number 10
BGP table version 7000
RIB entries 7999, using 937 KiB of memory
Peers 16, using 268 KiB of memory
Peer groups 4, using 224 bytes of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.0.0.2 4 10 103 204 0 0 0 00:01:21 1000
10.0.0.3 4 10 103 204 0 0 0 00:01:21 1000
10.0.0.4 4 10 203 204 0 0 0 00:01:21 2000
20.1.1.6 4 20 403 589 0 0 0 00:01:37 1000
20.1.1.7 4 20 403 589 0 0 0 00:01:35 1000
40.1.1.2 4 40 403 689 0 0 0 00:01:40 1000
40.1.1.6 4 40 403 689 0 0 0 00:01:48 1000
40.1.1.10 4 40 403 689 0 0 0 00:01:40 1000
Total number of neighbors 8
cumulus@r1$
cumulus@r1$ sudo cl-bgp summary
BGP router identifier 10.0.0.1, local AS number 10
BGP table version 7000
RIB entries 7999, using 937 KiB of memory
Peers 16, using 268 KiB of memory
Peer groups 4, using 224 bytes of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
r2(10.0.0.2) 4 10 104 205 0 0 0 00:02:05 1000
r3(10.0.0.3) 4 10 104 205 0 0 0 00:02:05 1000
r4(10.0.0.4) 4 10 204 205 0 0 0 00:02:05 2000
r6(20.1.1.6) 4 20 404 590 0 0 0 00:02:21 1000
r7(20.1.1.7) 4 20 404 590 0 0 0 00:02:19 1000
r8(40.1.1.2) 4 40 404 690 0 0 0 00:02:24 1000
r9(40.1.1.6) 4 40 404 690 0 0 0 00:02:32 1000
r10(40.1.1.10) 4 40 404 690 0 0 0 00:02:24 1000
Total number of neighbors 8
cumulus@r1$
5. IANA Considerations 5. IANA Considerations
IANA has assigned capability number TBD for the FQDN Capability IANA has assigned capability number 73 for the FQDN Capability
described in this document. This registration is in the BGP described in this document. This registration is in the BGP
Capability Codes registry. Capability Codes registry.
6. Security Considerations 6. Security Considerations
This document introduces no new security concerns to BGP or other This document introduces no new security concerns to BGP or other
specifications referenced in this document. specifications referenced in this document.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
with BGP-4", RFC 5492, February 2009. with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February
2009, <http://www.rfc-editor.org/info/rfc5492>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
7.2. Implementation References 7.2. Implementation References
[quagga] Dutt, D., "Quagga - BGP FQDN Capability", May 2015, [quagga] Dutt, D., "Quagga - BGP FQDN Capability", January 2016,
<https://github.com/CumulusNetworks/quagga/ <https://github.com/CumulusNetworks/quagga/
commit/45d4b165b9d01c0e98082e7d1e90a3b1a60b1085>. commit/45d4b165b9d01c0e98082e7d1e90a3b1a60b1085>.
Authors' Addresses Authors' Addresses
Daniel Walton Daniel Walton
Cumulus Networks Cumulus Networks
3701 NW Cary Parkway, Suite #300 3701 NW Cary Parkway, Suite #300
Cary, NC 27513 Cary, NC 27513
US US
 End of changes. 9 change blocks. 
8 lines changed or deleted 55 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/