[Int-area] question about xping (draft-bonica-intarea-eping)

Sowmini Varadhan <sowmini.varadhan@oracle.com> Tue, 28 March 2017 21:32 UTC

Return-Path: <sowmini.varadhan@oracle.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBFED129A26 for <int-area@ietfa.amsl.com>; Tue, 28 Mar 2017 14:32:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.497
X-Spam-Level:
X-Spam-Status: No, score=-6.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LEWWpnEF6NZS for <int-area@ietfa.amsl.com>; Tue, 28 Mar 2017 14:32:29 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8DE11294B0 for <int-area@ietf.org>; Tue, 28 Mar 2017 14:32:10 -0700 (PDT)
Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v2SLW9ox008506 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 28 Mar 2017 21:32:09 GMT
Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id v2SLW8Fi017464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 28 Mar 2017 21:32:08 GMT
Received: from abhmp0015.oracle.com (abhmp0015.oracle.com [141.146.116.21]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id v2SLW8eL027261; Tue, 28 Mar 2017 21:32:08 GMT
Received: from oracle.com (/207.91.160.8) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 28 Mar 2017 14:32:08 -0700
Date: Tue, 28 Mar 2017 17:32:05 -0400
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: rbonica@juniper.net, rejithomas@juniper.net, furry@google.com, chris.lenart@verizon.com
Cc: int-area@ietf.org, sowmini.varadhan@oracle.com
Message-ID: <20170328213205.GC6413@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Source-IP: userv0022.oracle.com [156.151.31.74]
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/EbKsFMXPgLxlB89aOpPjsk6rzHY>
Subject: [Int-area] question about xping (draft-bonica-intarea-eping)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 21:32:38 -0000

Hi,

The draft says 
   ".. the destination and probed
   interfaces must be local to one another (i.e., both interfaces must
   belong to the same node)."

However, virtualization raises some questions about how this should work,
and maybe the draft should nail down some of the details with more 
clarity.

What if the probed interface is assigned to a different VRF than the
destination interface? e.g, What is the expected xping response
if I receive 
     # xping-I red0/0/0.0 10.10.10.1
on interface blue0 in the "blue" vrf, and red0 is in "red" VRF?
Does the answer change if the destination interface is on the
management VRF?

similar question for other forms of virtualization, e.g,,
What if the probed interface is assigned to a different 
network-namespace than the destination interface of an xping req?
Does it matter if the above xping is received on the default 
network namespace vs some other network namespace? 

One could argue that all the physical intefaces are owned by the "node"
(the management VRF? default netns?) but virtual interfaces like
tunnels and macvlans are a grayer area (unlike physical interfaces,
the latter do not default back to the mgmt VRF or default netns when
the virtual object is destroyed, so their ownership is unclear).

How should xping work in the face of virtual interfaces, e.g.,
the linux macvlan? How does it work when an interface is renamed?
Will xping allow me to probe for "tun0" or "Portchannel1"?

--Sowmini