[nvo3-dt-encap] Discussion summary - 1/10/2017
Pankaj Garg <ipankajg@gmail.com> Wed, 11 January 2017 15:25 UTC
Return-Path: <ipankajg@gmail.com>
X-Original-To: nvo3-dt-encap@ietfa.amsl.com
Delivered-To: nvo3-dt-encap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87FA9129468 for <nvo3-dt-encap@ietfa.amsl.com>; Wed, 11 Jan 2017 07:25:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4yqarEiYhDVO for <nvo3-dt-encap@ietfa.amsl.com>; Wed, 11 Jan 2017 07:25:55 -0800 (PST)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5AAF12948C for <nvo3-dt-encap@ietf.org>; Wed, 11 Jan 2017 07:25:54 -0800 (PST)
Received: by mail-oi0-x22d.google.com with SMTP id u143so181539305oif.3 for <nvo3-dt-encap@ietf.org>; Wed, 11 Jan 2017 07:25:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mime-version:content-disposition :user-agent; bh=A37gFe/KJi+1rNSpfc3bw+AbqiXw0Y/s+02exIVCQf8=; b=nYbgbrXOqUIqzUfJt0GhxpochU4Vuxy/dHCk3dPRclfS2LJFGlBotnH84yQucLTVTj 0I+4gSPrRPn/Wqe8l9VMvbunN8VwL/GWPcIWl9ZQa7nTcdoq2ld2STxkE4OMCqjfS4YM 7F1x2r/pcJHH0nL5B81oLGkLbzDA913Fljl1/LIE7yCGOSVX6QYsWVdv6qR506gMM3S2 6V7K4MpFDRnVD7NNA9F7JvKaa6NFSAc5xNMXgcQleksF9KvUQehS68phqSYHcehQ+Og2 15NMKutO4Y72rtGjIGuyOHrAVXrUnkeDR5mw7IJ6ec4NG9s7LCklb8mleW7UrsQm+bxZ z+BA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=A37gFe/KJi+1rNSpfc3bw+AbqiXw0Y/s+02exIVCQf8=; b=eoHzs8VQPBNuzCFj51115T+02TVADWiMhOMkLu1xu3k5tYv4YfFWWrHtwdIVtq8iPE frRi/W0tAirPEEemTqdal1fnwFwkRqEoZt/dJL9x7tJubuiE92YVguHC2dp6d5qeTE+l 7QWJfXj/KyF8/Hc0qCgD7pRQq3EFNV46T8rxGJoA9FXTxt1adrluc6WbSOF2hPAyx3ms mnHxnc9plS23GS29L4u2xiN4FwkQmFHhCTRpr/NEr92Ou4gyNw8aGWWm6PpxI+Gdbje0 koImOtNONyHqR/LvcM77moic6Hs2DjEwlMS82dYRE8K+VYXoMlqEJXzem4fV41T3YoZV x+aA==
X-Gm-Message-State: AIkVDXK474qkJu4+PN8ccfaEPh3lh6adcN1T26l3sYEqT3ArJuX1Cd88f10juuMl8E4LlQ==
X-Received: by 10.202.220.139 with SMTP id t133mr4144055oig.176.1484148354002; Wed, 11 Jan 2017 07:25:54 -0800 (PST)
Received: from pg-wrk (99-13-224-41.lightspeed.sntcca.sbcglobal.net. [99.13.224.41]) by smtp.gmail.com with ESMTPSA id l6sm2518835oia.22.2017.01.11.07.25.53 for <nvo3-dt-encap@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jan 2017 07:25:53 -0800 (PST)
Date: Wed, 11 Jan 2017 07:25:53 -0800
From: Pankaj Garg <ipankajg@gmail.com>
To: nvo3-dt-encap@ietf.org
Message-ID: <20170111152553.GA27420@pg-wrk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.7.1 (2016-10-04)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3-dt-encap/fXW2s9Ws_uW6JraxyRXuYBC705o>
Subject: [nvo3-dt-encap] Discussion summary - 1/10/2017
X-BeenThere: nvo3-dt-encap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Private mailing list for internal NVO3 Encapsulation Design Team discussions <nvo3-dt-encap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3-dt-encap>, <mailto:nvo3-dt-encap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3-dt-encap/>
List-Post: <mailto:nvo3-dt-encap@ietf.org>
List-Help: <mailto:nvo3-dt-encap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3-dt-encap>, <mailto:nvo3-dt-encap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2017 15:25:56 -0000
Hi All, Thanks for attending the call. My curated notes are below. Participants: Erik Nordmark (Arista) Michael Smith (Cisco) Ignas Bagdonas (Equinix) Ilango Ganga (Intel) Sami Boutros (VMware) Tal Mizrahi (Marvell) David Mozes (Mellanox) Pankaj Garg (Microsoft) 1. We discussed the text for requiring at minimum 64-bytes to be supported in Geneve. There is consensus that we should propose a text to Geneve authors on minimum option length requirement. This would ensure there is common minimum support from all compliant Geneve implementations. 2. We discussed the idea of TLV0 further and upon discussion it was realized that it adds more confusion without any significant gain. Hence design team agreed to drop this from the proposed changes. 3. We agreed that we should put some text either in Geneve draft or design team report around supporting option ordering in Geneve implemnentations. The idea is that if a hardware can process options in TCAM but it can only process the first TLV, then control plane in a deployment can use this capability by ensuring a specific TLV is always the first one in the packet. We need someone to write this text. 4. We discussed split-NVE case and agreed that we need to ask WG whether in split-NVE case, options needs to be carried in other packet formats such as 802.1q and if they do, then would carrying Geneve frame in 802.1q be needed? Based on WG recommendation, an ETYPE and/or IP protocol number can be allocated for Geneve as well. Erik has agreed to write text around this question. Thanks Erik. 5. Sami has volunteered to write the initial draft for design team report. This report would contain our rationale for proposing a specific encapsulation and few specific extension use cases and how propose encapsulation meet those requirements. Thanks Sami. 6. Pankaj would send one extension use case around diagnostics. We would check with Tom on extension around security. Those will probably be two use cases we would cover in our design report. Please let me know if I missed anything. Thanks, Pankaj (on behalf of NVO3 Encap Design Team)
- [nvo3-dt-encap] Discussion summary - 1/10/2017 Pankaj Garg
- Re: [nvo3-dt-encap] Discussion summary - 1/10/2017 Rajeev Manur
- Re: [nvo3-dt-encap] Discussion summary - 1/10/2017 Pankaj Garg
- Re: [nvo3-dt-encap] Discussion summary - 1/10/2017 Sami Boutros
- Re: [nvo3-dt-encap] Discussion summary - 1/10/2017 David Mozes
- Re: [nvo3-dt-encap] Discussion summary - 1/10/2017 Tal Mizrahi
- Re: [nvo3-dt-encap] Discussion summary - 1/10/2017 Michael Smith (michsmit)