[nvo3] Suresh Krishnan's Discuss on draft-ietf-nvo3-geneve-14: (with DISCUSS and COMMENT)
Suresh Krishnan via Datatracker <noreply@ietf.org> Thu, 05 December 2019 13:37 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: nvo3@ietf.org
Delivered-To: nvo3@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F581120147; Thu, 5 Dec 2019 05:37:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-nvo3-geneve@ietf.org, Matthew Bocci <matthew.bocci@nokia.com>, nvo3-chairs@ietf.org, matthew.bocci@nokia.com, nvo3@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.111.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Suresh Krishnan <suresh@kaloom.com>
Message-ID: <157555307725.16433.6835620814626902819.idtracker@ietfa.amsl.com>
Date: Thu, 05 Dec 2019 05:37:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/MOMMl6CTRVjG5twyeUerU5U34Bs>
Subject: [nvo3] Suresh Krishnan's Discuss on draft-ietf-nvo3-geneve-14: (with DISCUSS and COMMENT)
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 05 Dec 2019 13:38:00 -0000
Suresh Krishnan has entered the following ballot position for draft-ietf-nvo3-geneve-14: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-nvo3-geneve/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- * Section 3.3. This might be an easy DISCUSS to resolve. Since the specification requires the Destination port to be configurable, it is not clear to me how the "transit" devices will identify Geneve packets being sent to a non-default port (i.e. not 6081). Can you please clarify? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I support Ben's DISCUSS position and I would like to ensure that the concerns brought up regarding transit devices and UDP zero checksums are resolved. I would also like to ensure that RFC8200 is used as the reference for the IPv6 protocol as stated in Eric's DISCUSS. * Section 3.3 Have you considered the use of the flow label instead of source port for in the IPv6 tunnel case? I highly recommend looking at [RFC6438] for further details as it is specifically addresses ECMP for IP-in-IPv6 tunneled traffic.
- [nvo3] Suresh Krishnan's Discuss on draft-ietf-nv… Suresh Krishnan via Datatracker
- Re: [nvo3] Suresh Krishnan's Discuss on draft-iet… Ganga, Ilango S
- Re: [nvo3] Suresh Krishnan's Discuss on draft-iet… Suresh Krishnan