idnits 2.17.1 draft-nayak-intarea-probe-by-vfi-00.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 : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** There are 4 instances of too long lines in the document, the longest one being 1 character in excess of 72. -- The draft header indicates that this document updates RFC8335, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 1, 2019) is 1911 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: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTAREA WG M. Nayak 3 Internet-Draft R. Bonica 4 Updates: 8335 (if approved) R. Puttur 5 Intended status: Standards Track Juniper Networks 6 Expires: August 5, 2019 February 1, 2019 8 Probing IP Interfaces By Virtual Function Index 9 draft-nayak-intarea-probe-by-vfi-00 11 Abstract 13 This document enhances the PROBE diagnostic tool so that it can 14 identify the probed interface by Virtual Function Index. In order to 15 achieve that goal, this document also extends the Interface 16 Identification Object. The Interface Identification Object is an 17 ICMP Extension Object class. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on August 5, 2019. 36 Copyright Notice 38 Copyright (c) 2019 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2 55 3. ICMP Extended Echo Request Message . . . . . . . . . . . . . 3 56 4. Interface Identification Object . . . . . . . . . . . . . . . 3 57 5. ICMP Extended Echo Reply Message . . . . . . . . . . . . . . 4 58 6. ICMP Message Processing . . . . . . . . . . . . . . . . . . . 4 59 7. Updates To RFC 8335 . . . . . . . . . . . . . . . . . . . . . 4 60 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 61 9. Security Considerations . . . . . . . . . . . . . . . . . . . 5 62 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 63 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 11.1. Normative References . . . . . . . . . . . . . . . . . . 5 65 11.2. Informative References . . . . . . . . . . . . . . . . . 5 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 68 1. Problem Statement 70 PROBE [RFC8335] is a diagnostic tool that can be used to query the 71 status of an interface. PROBE sends an ICMP Extended Echo Request 72 message to a proxy interface. The ICMP Extended Echo Request message 73 contains an ICMP Extension Structure and the ICMP Extension Structure 74 contains an Interface Identification Object. The Interface 75 Identification Object identifies the probed interface by name, 76 ifIndex or address. 78 When the proxy interface receives the ICMP Extended Echo Request, the 79 node upon which it resides executes access control procedures. If 80 access is granted, the node determines the status of the probed 81 interface and returns an ICMP Extended Echo Reply message. The ICMP 82 Extended Echo Reply indicates the status of the probed interface. 84 This document enhances the PROBE so that it can identify the probed 85 interface by Virtual Function Index (VFI) [SR-IOV]. In order to 86 achieve that goal, this document extends the Interface Identification 87 Object. The Interface Identification Object is an ICMP Extension 88 Object class. 90 2. Requirements Language 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 94 "OPTIONAL" in this document are to be interpreted as described in BCP 95 14 [RFC2119] [RFC8174] when, and only when, they appear in all 96 capitals, as shown here. 98 3. ICMP Extended Echo Request Message 100 Section 2.1 of [RFC8335] defines the ICMP Extended Echo Request 101 message. As per [RFC8335], the ICMP Extended Echo Request message 102 contains the following fields: 104 o Type 106 o Code 108 o Checksum 110 o Identifier 112 o Reserved 114 o L (local) 116 o ICMP Extension Structure 118 Section 7 of [RFC4884] defines the ICMP Extension Structure. As per 119 [RFC4884], the Extension Structure contains exactly one Extension 120 Header followed by one or more objects. When applied to the ICMP 121 Extended Echo Request message, the ICMP Extension Structure contains 122 exactly one instance of the Interface Identification Object. 123 Section 2.1 of [RFC8335] defines the Interface Identification Object. 124 Section 4 of this document extends that definition. 126 If the L-bit is set, the Interface Identification Object can identify 127 the probed interface by name, index, address or VFI. If the L-bit is 128 clear, the Interface Identification Object identifies the probed 129 interface by address. 131 4. Interface Identification Object 133 Section 2.1 of [RFC8335] defines the Interface Identification Object. 134 The Interface Identification Object identifies the probed interface 135 by name, index, or address. Like any other ICMP Extension Object, it 136 contains an Object Header and Object Payload. The Object Header 137 contains the following fields: 139 o Class-Num: Interface Identification Object. The value is 3. 141 o C-Type: Determines how the probed interface is identified. 143 o Length: Length of the object, measured in octets, including the 144 Object Header and Object Payload. 146 Currently, the following values are defined for C-Type: 148 o (0) Reserved 150 o (1) Identifies Interface by Name 152 o (2) Identifies Interface by Index 154 o (3) Identifies Interface by Address 156 This document defines the following, new C-Type: 158 o (value TBD by IANA) Identifies Interfaces by Virtual Function 159 Index (VFI) 161 If the Interface Identification Object identifies the probed 162 interface by Virtual Function Index, the length is equal to 8 and the 163 payload contains the Virtual Function Index. 165 5. ICMP Extended Echo Reply Message 167 Section 3 of [RFC8335] defines the ICMP Extended Echo Reply message. 168 This document does not change that definition. 170 6. ICMP Message Processing 172 Section 4 of [RFC8335] defines the ICMP message processing. This 173 document does not change that definition. 175 7. Updates To RFC 8335 177 Section 2 of [RFC8335] states: 179 "If the L-bit is set, the Interface Identification Object can 180 identify the probed interface by name, index, or address. If the 181 L-bit is clear, the Interface Identification Object MUST identify the 182 probed interface by address." 184 This document updates that text as follows: 186 "If the L-bit is set, the Interface Identification Object can 187 identify the probed interface by name, index, address, or Virtual 188 Function Index (VFI). If the L-bit is clear, the Interface 189 Identification Object MUST identify the probed interface by address." 191 8. IANA Considerations 193 IANA is requested to add the following a new C-type: 195 o (value TBD by IANA) Identifies Interfaces by Virtual Function 196 Index (VFI) 198 This new C-Type is to be added to the Interface Identification Object 199 under the "ICMP Extension Object Classes and Class Sub-types" 200 registry. 202 9. Security Considerations 204 This documen neither extends nor mitigates any of the security 205 considerations mentioned in [RFC8335]. 207 10. Acknowledgements 209 The authors wish to acknowledge Ross Callon for his helpful comments. 211 11. References 213 11.1. Normative References 215 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 216 Requirement Levels", BCP 14, RFC 2119, 217 DOI 10.17487/RFC2119, March 1997, 218 . 220 [RFC4884] Bonica, R., Gan, D., Tappan, D., and C. Pignataro, 221 "Extended ICMP to Support Multi-Part Messages", RFC 4884, 222 DOI 10.17487/RFC4884, April 2007, 223 . 225 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 226 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 227 May 2017, . 229 [RFC8335] Bonica, R., Thomas, R., Linkova, J., Lenart, C., and M. 230 Boucadair, "PROBE: A Utility for Probing Interfaces", 231 RFC 8335, DOI 10.17487/RFC8335, February 2018, 232 . 234 11.2. Informative References 236 [SR-IOV] PCI-SIG, ., "Single Root I/O Virtualization and Sharing 237 Specification Revision 1.1", January 2010, 238 . 241 Authors' Addresses 243 Manoj Nayak 244 Juniper Networks 245 Bangalore, KA 560103 246 India 248 Email: manojnayak@juniper.net 250 Ron Bonica 251 Juniper Networks 252 Herndon, Virginia 20171 253 USA 255 Email: rbonica@juniper.net 257 Rafik Puttur 258 Juniper Networks 259 Bangalore, KA 560103 260 India 262 Email: rafikp@juniper.net