idnits 2.17.1 draft-abraitis-bgp-version-capability-01.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 1 instance 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 (August 1, 2019) is 1729 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) == Missing Reference: 'RFC5492' is mentioned on line 77, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'FRRouting' Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Abraitis 3 Internet-Draft Hostinger 4 Intended status: Standards Track August 1, 2019 5 Expires: February 2, 2020 7 Version Capability for BGP 8 draft-abraitis-bgp-version-capability-01 10 Abstract 12 In this document, we introduce a new BGP capability that allows the 13 advertisement of a BGP speaker's version. 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 https://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 February 2, 2020. 32 Copyright Notice 34 Copyright (c) 2019 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 (https://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 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Specification of Requirements . . . . . . . . . . . . . . . . 2 51 3. Version Capability . . . . . . . . . . . . . . . . . . . . . 2 52 4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 54 6. Security Considerations . . . . . . . . . . . . . . . . . . . 3 55 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 7.1. Normative References . . . . . . . . . . . . . . . . . . 3 57 7.2. Informative References . . . . . . . . . . . . . . . . . 4 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 60 1. Introduction 62 In modern data center designs, we tend to have conventional hosts 63 participating in the routing process. And the fleet of hosts has 64 different versions of routing daemon. This means that 65 troubleshooting is a crucial part to quickly identify the root cause. 66 This document introduces new BGP capability to advertise the version 67 of routing daemon. 69 2. Specification of Requirements 71 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 72 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 73 document are to be interpreted as described in [RFC2119]. 75 3. Version Capability 77 The Version Capability is a new BGP capability [RFC5492]. 79 +--------------------------------+ 80 | Version Length (1 octet) | 81 +--------------------------------+ 82 | Version (variable) | 83 +--------------------------------+ 85 Figure 1 87 Version Length: 89 The number of characters in the Version 91 Version: 93 The Version encoded via UTF-8 95 4. Operation 97 The Version capability SHOULD only be used for displaying the version 98 of a speaker in order to make troubleshooting easier. You have a 99 bunch of routers with a number of upstreams each. All of them are 100 with a different operating system and routing daemon installed. 101 Assuming that a specific feature is not working or a bug which is not 102 fixed in an appropriate version, would allow us to quickly identify 103 the pattern which versions are affected. Below is an example of 104 implementation in [FRRouting] how it looks like with version 105 advertised by a BGP sender: 107 :~# vtysh -c 'show ip bgp neighbors 192.168.0.1 json' \ 108 > | jq '."192.168.0.1".neighborCapabilities.versions' 109 { 110 "advertisedVersion": "FRRouting 7.2-dev-MyOwnFRRVersion", 111 "receivedVersion": "FRRouting 7.2-dev-MyOwnFRRVersion-gc68bb14" 112 } 114 Figure 2 116 5. IANA Considerations 118 IANA is requested to assign a capability number for the Version 119 Capability in this document from the BGP Capabilities Codes registry. 121 6. Security Considerations 123 All drafts are required to have a security considerations section. 124 See RFC 3552 [RFC3552] for a guide. 126 7. References 128 7.1. Normative References 130 [FRRouting] 131 Abraitis, D., "FRRouting - BGP Version Capability", 2019, 132 . 135 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 136 Requirement Levels", BCP 14, RFC 2119, 137 DOI 10.17487/RFC2119, March 1997, 138 . 140 7.2. Informative References 142 [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC 143 Text on Security Considerations", BCP 72, RFC 3552, 144 DOI 10.17487/RFC3552, July 2003, 145 . 147 Author's Address 149 Donatas Abraitis 150 Hostinger 151 Jonavos g. 60C 152 Kaunas 44192 153 LT 155 Phone: +370 614 18958 156 Email: donatas.abraitis@hostinger.com