[nvo3] Comments on draft-ietf-nvo3-vxlan-gpe
Greg Mirsky <gregimirsky@gmail.com> Fri, 12 April 2019 06:50 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDA6F12011C; Thu, 11 Apr 2019 23:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 InAmAHhY84DP; Thu, 11 Apr 2019 23:50:46 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 885B11200BA; Thu, 11 Apr 2019 23:50:46 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id w23so6622460lfc.9; Thu, 11 Apr 2019 23:50:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=oWv/Lj4kYc6i1g5r9KJEo6BmTHihuufiwSzmf++XGi8=; b=bPO/h0OnDcTAYMSCVwrSaIWFBeKo5/unpEZc4MCNGTTcuaCq1uxra7dUvs3lgi9JwG mH4dFu7I3xP/fzWBQao18CNeNP1z88I+12bwKzNe6hYLv5Dpuk6KPWI01MqdomnaoS1F ZWURH+85za8Ss5AeJ0kQk6sNyvLaiIuySigysCF5HembBLW6Bpg22agJq6CeumJMDlzn li4FUBHkqcrF5Wd+uArvZIW99Z2yBKCezZuqVhSBfimdmabRY0zBYOEH0t97Kf1kMPDg 5/OIiOPXU+lMKQWZD3b5PZknpgMvhWeVAdTpN5oCJkh9HKD/+N6zAkIZ6gca3HcZJIkB E5Xw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oWv/Lj4kYc6i1g5r9KJEo6BmTHihuufiwSzmf++XGi8=; b=jP1WwHPuM43UM2I4NQ5SYGTADEsj839m4l9+oidGHFHgF5aEANJWCoa9AdSib9ZOst sHf0kMFzjIhdY6IX/rER02TwTrqyouwWS7GSUgaMorLYsW6tQbVMcG1BEpmr5kSsOtG4 xBRta4MZE+1HDcpUSMGtj51Fp7ULjtTBiQOh4ts/0UwiDKuvW9olldWIjmi2Ybn2voqQ Ve2lXd4D4Q7bX8yxHDpZF7WbO2XgJkisTtKFGbmMhhJoJaZ+xYCPTE8XQdeSeQ/K0wvp PZs1smVzAJDiWUnIqpGwCNYQ4T5AhUZFA1ptJy3aZIhzgFTswPhtKsZ23hQwmpyO+WEI c4tw==
X-Gm-Message-State: APjAAAXZKL7a+KadJpIBXgq8Mi/Cy7du6bzX2PLm1cW9GcPKqhkAd+93 QEpJlR1fOyhLnaUdO4G6mdHhJ94yytKJUuKucY5LX8ESHDo=
X-Google-Smtp-Source: APXvYqyn2m6n4oPYCNekKj+mY8XbXHjbh75lTR0WL2V5PQQ6yqUQt6uS/XSSGfzrd8CvhE8fb/s41yiU48K/rSGPYcs=
X-Received: by 2002:ac2:4303:: with SMTP id l3mr10673271lfh.61.1555051844076; Thu, 11 Apr 2019 23:50:44 -0700 (PDT)
MIME-Version: 1.0
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 12 Apr 2019 08:50:34 +0200
Message-ID: <CA+RyBmV5R+jsPNn9-HooGcJzobD5mrxEwjbxn_o+hn2QcoiZNQ@mail.gmail.com>
To: draft-ietf-nvo3-vxlan-gpe@ietf.org, NVO3 <nvo3@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c608eb05864fb851"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/wBGkzWgm-OZGTZvEOS3pl3LUXgk>
Subject: [nvo3] Comments on draft-ietf-nvo3-vxlan-gpe
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.29
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: <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: Fri, 12 Apr 2019 06:50:53 -0000
Dear Editors, et al., I've read the latest -07 version and would like to share my comments and questions with you: - in the earlier version of the draft, the O-bit was introduced and defined as: OAM Flag Bit (O bit): The O bit is set to indicate that the packet is an OAM packet. At the same time, in the latest version, the new Next Protocol value (0x81) to identify iOAM Data was introduced. Hence are my questions: - What must be the value of the O-bit when the value of the Next Protocol field is iOAM? - Do you plan to define the Next Protocol values for active OAM protocols, e.g., Echo Request/Reply, BFD, Performance Monitoring? - How to interpret the situation when the O-bit value is 1 but the value of the Next Protocol field is, for example, NSH, i.e., not any of OAM protocols? - I believe that the use of the dedicated OAM flag and the Next Protocol field for a fixed-size header that cannot include meta-data is unwarranted and adds unnecessary complexity. I suggest not to use O-bit in the VXLAN-GPE header and release it into the Reserved field. I don't see the apparent benefit of using the flag, as the VXLA-GPE uses the fixed size header and the header cannot carry OAM data in it. The only role the VXLAN-GPE header must perform, in my opinion, is to unambiguously identify the payload type that immediately follows the header as OAM (demultiplexing OAM protocols may be done in OAM Header shim). Much appreciate your consideration. Regards, Greg
- [nvo3] Comments on draft-ietf-nvo3-vxlan-gpe Greg Mirsky
- Re: [nvo3] Comments on draft-ietf-nvo3-vxlan-gpe Carlos Pignataro (cpignata)
- Re: [nvo3] Comments on draft-ietf-nvo3-vxlan-gpe Greg Mirsky
- Re: [nvo3] Comments on draft-ietf-nvo3-vxlan-gpe Carlos Pignataro (cpignata)
- Re: [nvo3] Comments on draft-ietf-nvo3-vxlan-gpe Greg Mirsky
- Re: [nvo3] [SUSPICIOUS] Re: Comments on draft-iet… Carlos Pignataro (cpignata)
- Re: [nvo3] [SUSPICIOUS] Re: Comments on draft-iet… Greg Mirsky
- Re: [nvo3] [SUSPICIOUS] Re: Comments on draft-iet… Carlos Pignataro (cpignata)