< draft-nayak-intarea-probe-by-vfi-00.txt   draft-nayak-intarea-probe-by-vfi-01.txt >
INTAREA WG M. Nayak INTAREA WG M. Nayak
Internet-Draft R. Bonica Internet-Draft R. Bonica
Updates: 8335 (if approved) R. Puttur Updates: 8335 (if approved) R. Puttur
Intended status: Standards Track Juniper Networks Intended status: Standards Track Juniper Networks
Expires: August 5, 2019 February 1, 2019 Expires: February 15, 2020 August 16, 2019
Probing IP Interfaces By Virtual Function Index Probing IP Interfaces By Vendor Specific Identifiers
draft-nayak-intarea-probe-by-vfi-00 draft-nayak-intarea-probe-by-vfi-01
Abstract Abstract
This document enhances the PROBE diagnostic tool so that it can This document enhances the PROBE diagnostic tool so that it can
identify the probed interface by Virtual Function Index. In order to identify the probed interface by Vendor Specific Identifiers.
achieve that goal, this document also extends the Interface In order to achieve that goal, this document also extends the
Identification Object. The Interface Identification Object is an Interface Identification Object. The Interface Identification
ICMP Extension Object class. Object is an ICMP Extension Object class.
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.
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 August 5, 2019. This Internet-Draft will expire on February 15, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 35 skipping to change at page 2, line 35
PROBE [RFC8335] is a diagnostic tool that can be used to query the PROBE [RFC8335] is a diagnostic tool that can be used to query the
status of an interface. PROBE sends an ICMP Extended Echo Request status of an interface. PROBE sends an ICMP Extended Echo Request
message to a proxy interface. The ICMP Extended Echo Request message message to a proxy interface. The ICMP Extended Echo Request message
contains an ICMP Extension Structure and the ICMP Extension Structure contains an ICMP Extension Structure and the ICMP Extension Structure
contains an Interface Identification Object. The Interface contains an Interface Identification Object. The Interface
Identification Object identifies the probed interface by name, Identification Object identifies the probed interface by name,
ifIndex or address. ifIndex or address.
When the proxy interface receives the ICMP Extended Echo Request, the When the proxy interface receives the ICMP Extended Echo Request, the
node upon which it resides executes access control procedures. If node upon which it resides executes access control procedures as per
access is granted, the node determines the status of the probed [RFC8335] security considerations. If access is granted, the node
interface and returns an ICMP Extended Echo Reply message. The ICMP determines the status of the probed interface and returns an ICMP
Extended Echo Reply indicates the status of the probed interface. Extended Echo Reply message. The ICMP Extended Echo Reply indicates
the status of the probed interface.
Virtualized instance of the network adapter are created out of a
Network Interface Card to enable efficient sharing of Network
Interface Card in a virtualization environment. These Virtualized
instances of the network adapter are implemented in the hardware and
assigned a Vendor Specific Identifier to uniquely identify the
Virtualized instance of the network adapter.
This document enhances the PROBE so that it can identify the probed This document enhances the PROBE so that it can identify the probed
interface by Virtual Function Index (VFI) [SR-IOV]. In order to interface by Vendor Specific Identifiers. This probe type is
achieve that goal, this document extends the Interface Identification necessary when none of the other probe types of PROBE (i.e., probe
Object. The Interface Identification Object is an ICMP Extension interface by name, probe interface by address, etc) work.
Object class. Virtual Function Index (VFI) [SR-IOV] is one (but not the only)
instance of Vendor Specific Identifiers. Vendor Specific Identifiers,
hereinafter referred to as VSI in the remaining part of this document.
In order to achieve PROBE's enhancement, this document extends the
Interface Identification Object. The Interface Identification Object
is an ICMP Extension Object class.
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. ICMP Extended Echo Request Message 3. ICMP Extended Echo Request Message
Section 2.1 of [RFC8335] defines the ICMP Extended Echo Request Section 2 of [RFC8335] defines the ICMP Extended Echo Request
message. As per [RFC8335], the ICMP Extended Echo Request message message. As per [RFC8335], the ICMP Extended Echo Request message
contains the following fields: contains the following fields:
o Type o Type
o Code o Code
o Checksum o Checksum
o Identifier o Identifier
skipping to change at page 4, line 20 skipping to change at page 4, line 20
o (0) Reserved o (0) Reserved
o (1) Identifies Interface by Name o (1) Identifies Interface by Name
o (2) Identifies Interface by Index o (2) Identifies Interface by Index
o (3) Identifies Interface by Address o (3) Identifies Interface by Address
This document defines the following, new C-Type: This document defines the following, new C-Type:
o (value TBD by IANA) Identifies Interfaces by Virtual Function o (value TBD by IANA) Identifies Interfaces by Vendor Specific
Index (VFI) Identifier (VSI)
If the Interface Identification Object identifies the probed Every vendor specific ID needs to be N-bits long and the vendor
interface by Virtual Function Index, the length is equal to 8 and the gets to have exactly one of them (i.e, either VFI or some other
payload contains the Virtual Function Index. Vendor Specific Identifiers). If the Interface Identification
Object identifies the probed interface by VSI (Vendor Specific
Identfier), the payload is as depicted in Figure 1.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| enterprise-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ .
. identifier(variable length) .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: VSI Format
This VSI consists of the 4-octet vendor's registered Private
Enterprise Number as maintained by IANA [IANA-PEN] followed by a
unique identifier assigned by the vendor.
Payload fields are defined as follows:
o Identifier Length: Number of significant bytes contained by the
VSI. (The VSI field contains significant bytes and padding
bytes.)
o Reserved: This field MUST be set to 0 and ignored upon receipt.
o Identifier: This variable-length field represents an Identifier
associated with the probed interface. If the Identifier field
would not otherwise terminate on a 32-bit boundary, it MUST be
padded with zeroes.
5. ICMP Extended Echo Reply Message 5. ICMP Extended Echo Reply Message
Section 3 of [RFC8335] defines the ICMP Extended Echo Reply message. Section 3 of [RFC8335] defines the ICMP Extended Echo Reply message.
This document does not change that definition. This document does not change that definition.
6. ICMP Message Processing 6. ICMP Message Processing
Section 4 of [RFC8335] defines the ICMP message processing. This Section 4 of [RFC8335] defines the ICMP message processing. This
document does not change that definition. document does not change that definition.
skipping to change at page 4, line 49 skipping to change at page 5, line 27
Section 2 of [RFC8335] states: Section 2 of [RFC8335] states:
"If the L-bit is set, the Interface Identification Object can "If the L-bit is set, the Interface Identification Object can
identify the probed interface by name, index, or address. If the identify the probed interface by name, index, or address. If the
L-bit is clear, the Interface Identification Object MUST identify the L-bit is clear, the Interface Identification Object MUST identify the
probed interface by address." probed interface by address."
This document updates that text as follows: This document updates that text as follows:
"If the L-bit is set, the Interface Identification Object can "If the L-bit is set, the Interface Identification Object can
identify the probed interface by name, index, address, or Virtual identify the probed interface by name, index, address, or Vendor
Function Index (VFI). If the L-bit is clear, the Interface Specific Identifier (VSI). If the L-bit is clear, the Interface
Identification Object MUST identify the probed interface by address." Identification Object MUST identify the probed interface by address."
8. IANA Considerations 8. IANA Considerations
IANA is requested to add the following a new C-type: IANA is requested to add the following a new C-type:
o (value TBD by IANA) Identifies Interfaces by Virtual Function o (value TBD by IANA) Identifies Interfaces by Vendor Specific
Index (VFI) Identifier (VSI)
This new C-Type is to be added to the Interface Identification Object This new C-Type is to be added to the Interface Identification Object
under the "ICMP Extension Object Classes and Class Sub-types" under the "ICMP Extension Object Classes and Class Sub-types"
registry. registry.
9. Security Considerations 9. Security Considerations
This documen neither extends nor mitigates any of the security This document neither extends nor mitigates any of the security
considerations mentioned in [RFC8335]. considerations mentioned in [RFC8335].
10. Acknowledgements 10. Acknowledgements
The authors wish to acknowledge Ross Callon for his helpful comments. The authors wish to acknowledge Ross Callon for his helpful comments.
11. References 11. References
11.1. Normative References 11.1. Normative References
skipping to change at page 5, line 46 skipping to change at page 5, line 72
DOI 10.17487/RFC4884, April 2007, DOI 10.17487/RFC4884, April 2007,
<https://www.rfc-editor.org/info/rfc4884>. <https://www.rfc-editor.org/info/rfc4884>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8335] Bonica, R., Thomas, R., Linkova, J., Lenart, C., and M. [RFC8335] Bonica, R., Thomas, R., Linkova, J., Lenart, C., and M.
Boucadair, "PROBE: A Utility for Probing Interfaces", Boucadair, "PROBE: A Utility for Probing Interfaces",
RFC 8335, DOI 10.17487/RFC8335, February 2018, RFC 8335, DOI 10.17487/RFC8335, February 2018,
<https://www.rfc-editor.org/info/rfc8335>. <https://www.rfc-editor.org/info/rfc8335>
11.2. Informative References 11.2. Informative References
[SR-IOV] PCI-SIG, ., "Single Root I/O Virtualization and Sharing [SR-IOV] PCI-SIG, ., "Single Root I/O Virtualization and Sharing
Specification Revision 1.1", January 2010, Specification Revision 1.1", January 2010,
<https://members.pcisig.com/wg/PCI-SIG/document/ <https://members.pcisig.com/wg/PCI-SIG/document/
download/8238>. download/8238>.
Authors' Addresses Authors' Addresses
 End of changes. 13 change blocks. 
28 lines changed or deleted 73 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/