idnits 2.17.1 draft-walton-bgp-hostname-capability-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 18 instances of too long lines in the document, the longest one being 12 characters in excess of 72. == There are 5 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 5 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 6, 2016) is 3032 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Walton 3 Internet-Draft D. Dutt 4 Intended status: Standards Track Cumulus Networks 5 Expires: July 9, 2016 January 6, 2016 7 Hostname Capability for BGP 8 draft-walton-bgp-hostname-capability-02 10 Abstract 12 In this document, we introduce a new BGP capability that allows the 13 advertisemnet of a BGP speaker's hostname. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on July 9, 2016. 32 Copyright Notice 34 Copyright (c) 2016 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 1. Introduction 49 BGP is increasingly used inside the data center. Due to the sheer 50 scale of devices involved, simplifying troubleshooting BGP would be 51 very useful. One simple way to ease the troubleshooting is to 52 display the hostname of the speaker in addition to the speaker's IP 53 address. This document defines a new BGP capability that allows the 54 exchange of a speaker's FQDN. 56 2. Specification of Requirements 58 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 59 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 60 document are to be interpreted as described in [RFC2119]. 62 3. FQDN Capability 64 The FQDN Capability is a new BGP capability [RFC5492]. The 65 Capability Code for this capability is specified in the IANA 66 Considerations section of this document. The Capability Length field 67 of this capability is variable. The Capability Value field consists 68 of the following: 70 +--------------------------------+ 71 | Hostname Length (1 octet) | 72 +--------------------------------+ 73 | Hostname (variable) | 74 +--------------------------------+ 75 | Domain Name Length (1 octet) | 76 +--------------------------------+ 77 | Domain Name (variable) | 78 +--------------------------------+ 80 Hostname Length: 82 The number of characters in the Hostname 84 Hostname: 86 The hostname encoded via UTF-8 88 Domain Name Length: 90 The number of characters in the Domain Name 92 Domain Name: 94 The domain name encoded via UTF-8 96 4. Operation 98 The FQDN Capability SHOULD only be used for displaying the hostname 99 and/or domain name of a speaker in order to make troubleshooting 100 easier. The hostname and domain name used are assumed to be 101 extracted from the hostname and domain name set on the device. While 102 there are other ways to potentially obtain the same information, 103 having standard BGP show commands use the hostname makes the use of 104 this option quite powerful. 106 An example of showing hostname in various displays is show below in 107 the output of the summary of BGP peering relationships, the first 108 being the typical display today, and the second the display when 109 displaying hostnames is enabled: 111 cumulus@r1$ sudo cl-bgp summary 112 BGP router identifier 10.0.0.1, local AS number 10 113 BGP table version 7000 114 RIB entries 7999, using 937 KiB of memory 115 Peers 16, using 268 KiB of memory 116 Peer groups 4, using 224 bytes of memory 118 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 119 10.0.0.2 4 10 103 204 0 0 0 00:01:21 1000 120 10.0.0.3 4 10 103 204 0 0 0 00:01:21 1000 121 10.0.0.4 4 10 203 204 0 0 0 00:01:21 2000 122 20.1.1.6 4 20 403 589 0 0 0 00:01:37 1000 123 20.1.1.7 4 20 403 589 0 0 0 00:01:35 1000 124 40.1.1.2 4 40 403 689 0 0 0 00:01:40 1000 125 40.1.1.6 4 40 403 689 0 0 0 00:01:48 1000 126 40.1.1.10 4 40 403 689 0 0 0 00:01:40 1000 128 Total number of neighbors 8 129 cumulus@r1$ 130 cumulus@r1$ sudo cl-bgp summary 131 BGP router identifier 10.0.0.1, local AS number 10 132 BGP table version 7000 133 RIB entries 7999, using 937 KiB of memory 134 Peers 16, using 268 KiB of memory 135 Peer groups 4, using 224 bytes of memory 137 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 138 r2(10.0.0.2) 4 10 104 205 0 0 0 00:02:05 1000 139 r3(10.0.0.3) 4 10 104 205 0 0 0 00:02:05 1000 140 r4(10.0.0.4) 4 10 204 205 0 0 0 00:02:05 2000 141 r6(20.1.1.6) 4 20 404 590 0 0 0 00:02:21 1000 142 r7(20.1.1.7) 4 20 404 590 0 0 0 00:02:19 1000 143 r8(40.1.1.2) 4 40 404 690 0 0 0 00:02:24 1000 144 r9(40.1.1.6) 4 40 404 690 0 0 0 00:02:32 1000 145 r10(40.1.1.10) 4 40 404 690 0 0 0 00:02:24 1000 147 Total number of neighbors 8 148 cumulus@r1$ 150 5. IANA Considerations 152 IANA has assigned capability number 73 for the FQDN Capability 153 described in this document. This registration is in the BGP 154 Capability Codes registry. 156 6. Security Considerations 158 This document introduces no new security concerns to BGP or other 159 specifications referenced in this document. 161 7. References 163 7.1. Normative References 165 [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement 166 with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February 167 2009, . 169 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 170 Requirement Levels", BCP 14, RFC 2119, 171 DOI 10.17487/RFC2119, March 1997, 172 . 174 7.2. Implementation References 176 [quagga] Dutt, D., "Quagga - BGP FQDN Capability", January 2016, 177 . 180 Authors' Addresses 182 Daniel Walton 183 Cumulus Networks 184 3701 NW Cary Parkway, Suite #300 185 Cary, NC 27513 186 US 188 Email: dwalton@cumulusnetworks.com 190 Dinesh Dutt 191 Cumulus Networks 192 185 E. Dana Street 193 Mountain View, CA 94041 194 US 196 Email: ddutt@cumulusnetworks.com