[nvo3] Follow up on draft-tissa-nvo3-oam-fm

"Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com> Mon, 03 March 2014 16:02 UTC

Return-Path: <tsenevir@cisco.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F4291A00AF for <nvo3@ietfa.amsl.com>; Mon, 3 Mar 2014 08:02:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.047
X-Spam-Level:
X-Spam-Status: No, score=-10.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 QHZuqWp0aXbw for <nvo3@ietfa.amsl.com>; Mon, 3 Mar 2014 08:02:00 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 04FE31A0051 for <nvo3@ietf.org>; Mon, 3 Mar 2014 08:01:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5636; q=dns/txt; s=iport; t=1393862517; x=1395072117; h=from:to:subject:date:message-id:mime-version; bh=m0BBhoCd05fuHWKw/zKOh3R7abm9aZ9E775t7ie2LjA=; b=O8aA+K906l/K1HE7k+gZc5o6fe7K23Y9+bs0paotMlorLkHRHjo8ff/d VzD/yUw80xx9QXoJ9NPsZVaWlfo34k8QB4VdPrcp+des9nLjQSBfqgY9a pnhfiuA6oVRVXJ0ozjKsjq4mxwqnOO2PptbqC97vcrpsXgSG0k4z407HZ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFABCnFFOtJV2Z/2dsb2JhbABagkJEO1fAUIEiFnSCJwEELV4BKlYmAQQbh3GdAK84F44og1yBFASqZ4Mtgio
X-IronPort-AV: E=Sophos; i="4.97,578,1389744000"; d="scan'208,217"; a="24510365"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-3.cisco.com with ESMTP; 03 Mar 2014 16:01:56 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s23G1u0d000305 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <nvo3@ietf.org>; Mon, 3 Mar 2014 16:01:56 GMT
Received: from xmb-rcd-x08.cisco.com ([169.254.8.225]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Mon, 3 Mar 2014 10:01:56 -0600
From: "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
To: "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: Follow up on draft-tissa-nvo3-oam-fm
Thread-Index: Ac82+eQBP6jEt4uuQP61iazhiH0AqQ==
Date: Mon, 03 Mar 2014 16:01:56 +0000
Message-ID: <FBEA3E19AA24F847BA3AE74E2FE193562AF82CA9@xmb-rcd-x08.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.75.203]
Content-Type: multipart/alternative; boundary="_000_FBEA3E19AA24F847BA3AE74E2FE193562AF82CA9xmbrcdx08ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/vKl7XX-c4kN1DW092iFHOHb-VPo
Subject: [nvo3] Follow up on draft-tissa-nvo3-oam-fm
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Mar 2014 16:02:02 -0000

There was a question on why payload sample is needed in OAM.

Firstly it is an optional field and not always required.

It is expected to be useful when using L2VNI + L3VNI at the same NVE to provide L3 gateway services to clients on L2VNI. Reference is draft-ietf-nvo3-dataplane-requirements-02, section 3.2.2 second last paragraph, please see below section for reference. At the L2VNI/L3VNI GW the sample payload is needed to make the ECMP path selection on the next domain (i.e L3VNI when L2VNI to L3VNI and vise versa).

Reference second last paragraph of section 3.2.2 of draft-ietf-nvo3-dataplane-requirements-02
"       L2 and L3 VNIs can be deployed in isolation or in combination to
       optimize traffic flows per tenant across the overlay network. For
       example, an L2 VNI may be configured across a number of NVEs to
       offer L2 multi-point service connectivity while a L3 VNI can be co-
       located to offer local routing capabilities and gateway
       functionality. In addition, integrated routing and bridging per
       tenant MAY be supported on an NVE. An instantiation of such service
       may be realized by interconnecting an L2 VNI as access to an L3 VNI
       on the NVE."