Re: [nvo3] Opsdir last call review of draft-ietf-nvo3-vmm-03
"Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com> Wed, 04 July 2018 08:55 UTC
Return-Path: <matthew.bocci@nokia.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 653C5124C04; Wed, 4 Jul 2018 01:55:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 Xm2-h5Lh1K9f; Wed, 4 Jul 2018 01:54:59 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-ve1eur02on070b.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe06::70b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76006130DC1; Wed, 4 Jul 2018 01:54:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rb970gDPGhaBCvfxFi+FTIkzY5b89eBiq/ZAPjPC+VU=; b=JE3M7NvO8RDMwWVvK+t2i87ZcwSvkNFQgq7efFn9WNnKeosH8Zz5Xf6HF6FUievMLYMBSJ3DFrdzkTRtJH7y2bgudIUhdR/6tY1lgwwZ+rOLCj6mWXZOJhSpYILWlycgjvg7VeGJywFZ4v9gBxR6uCsLHBMRV/lqGDOyxBbNiIY=
Received: from AM6PR0702MB3622.eurprd07.prod.outlook.com (52.133.24.24) by AM6PR0702MB3831.eurprd07.prod.outlook.com (52.133.25.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.930.11; Wed, 4 Jul 2018 08:54:52 +0000
Received: from AM6PR0702MB3622.eurprd07.prod.outlook.com ([fe80::a9c4:6a95:761a:1868]) by AM6PR0702MB3622.eurprd07.prod.outlook.com ([fe80::a9c4:6a95:761a:1868%2]) with mapi id 15.20.0930.016; Wed, 4 Jul 2018 08:54:52 +0000
From: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-nvo3-vmm.all@ietf.org" <draft-ietf-nvo3-vmm.all@ietf.org>
Thread-Topic: Opsdir last call review of draft-ietf-nvo3-vmm-03
Thread-Index: AQHUEogTuXZLKoRsckeMWD/WB5pmf6R+1QoA
Date: Wed, 04 Jul 2018 08:54:52 +0000
Message-ID: <9EF82C41-A9A1-4A46-A67C-84F2382EC962@nokia.com>
References: <153059287199.16100.3846223755017785805@ietfa.amsl.com>
In-Reply-To: <153059287199.16100.3846223755017785805@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.e.1.180613
authentication-results: spf=none (sender IP is ) smtp.mailfrom=matthew.bocci@nokia.com;
x-originating-ip: [81.108.178.133]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM6PR0702MB3831; 7:qaUp7hiD9I+WIdebMcyTGZ8bh7keSyhYKALFNJ6a2MsSBFNm/jbIbDBZxWMGoZ0oSlvlm/BvAkMS7uv4fZhgtHDeKa6jsfHOCMCjONOakZqkoh8DUARk+DXzdAdQiGHoeM0dHHeO6lOwwNSj2aZ6i+W2oJvkbynH1mC9Tw1j0sjssYFDizyXKjRdZJWIUUiciFRjqnb9iAJokr9rVmcdAued4XZ5K1sEFzRz3nkEIa3vM7Z3n20tKDdxXQJU2Hpa
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 861bcb9e-8f3c-4d4a-8d91-08d5e18bcecd
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(48565401081)(4534165)(7168020)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7167020)(7193020); SRVR:AM6PR0702MB3831;
x-ms-traffictypediagnostic: AM6PR0702MB3831:
x-microsoft-antispam-prvs: <AM6PR0702MB3831ACC3CF5A757B27D5F8BBEB410@AM6PR0702MB3831.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231254)(11241501184)(806099)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:AM6PR0702MB3831; BCL:0; PCL:0; RULEID:; SRVR:AM6PR0702MB3831;
x-forefront-prvs: 0723A02764
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(136003)(39860400002)(396003)(346002)(376002)(199004)(189003)(45924002)(26005)(33656002)(81166006)(316002)(97736004)(561944003)(11346002)(8676002)(6506007)(81156014)(68736007)(110136005)(54906003)(478600001)(58126008)(55236004)(2900100001)(446003)(82746002)(476003)(486006)(102836004)(86362001)(14454004)(83716003)(106356001)(8936002)(105586002)(3846002)(2616005)(6116002)(4326008)(39060400002)(6486002)(25786009)(2501003)(5250100002)(5660300001)(2906002)(76176011)(99286004)(6246003)(36756003)(6512007)(229853002)(14444005)(186003)(53936002)(305945005)(256004)(7736002)(6436002)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM6PR0702MB3831; H:AM6PR0702MB3622.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: MI75W9BJAOtd4tGHCob7bUsEwmv/FA9HrwBMc9J1IqQUqgmTrWC/3cxqiTE8ZNAgpySBmZP04zch1KzGimMFaCfpqv5/aJGqN2zc8gvpn/saQalZe2rF/jkEhBTzQmJJX/kIEanipllQUofuXW6TAYYgnoQjdWVSl9juTmFVPfMu/zuu9wLM2f6Mt6FDzLabvhQFiyHFDAx6waNZImOnfnfZG+PzNhsQb6uGixwc4mto8tOlwezZ8RAvXy8jC9MSaWGiEhFnYnhJIpUAXJdeGC7QeAzOeedY+Yt6z8D5wbdzii/fH2Gvu0TY5m1XdaI9hciiFeoez23mT8g4rsEAu7Q6Yu9vXDrU0HvT+yHIqKxqW2ihgp4gQk5CtsjNNi5M/7CSUrpGN2DkohjDJ8IKmw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <51326D46D4F80443A341A51F49FAB088@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 861bcb9e-8f3c-4d4a-8d91-08d5e18bcecd
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jul 2018 08:54:52.7873 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR0702MB3831
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/1mecmPId48rqyUSRweMeelouXG0>
Subject: Re: [nvo3] Opsdir last call review of draft-ietf-nvo3-vmm-03
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 04 Jul 2018 08:55:02 -0000
Mahesh Many thanks for your review. Authors: Please can you treat these as WG last call comments and respond to them in that context. Regards Matthew On 03/07/2018, 05:41, "Mahesh Jethanandani" <mjethanandani@gmail.com> wrote: Reviewer: Mahesh Jethanandani Review result: Has Issues I have reviewed this document as part of the Operational directorate’s ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. Document reviewed: draft-ietf-nvo3-vmm-03 Summary: This document describes a virtual machine mobility protocol commonly used in data centers built with overlay-based network virtualization approach. For layer 2, it is based on using a Network Virtualization Authority (NVA)-Network Virtualization Edge (NVE) protocol to update Address Resolution Protocol (ARP) table or neighbor cache entries at the NVA and the source NVEs tunneling in-flight packets to the destination NVE after the virtual machine moves from source NVE to the destination NVE. For Layer 3, it is based on address and connection migration after the move. Document Status: Has Issues. Comments: General Considerations: The document could do with some much needed rewrite, as it is very hard to understand its content. There is extensive use of terms like “this virtual machine”, “those VMs”, and “those NVEs”, without being specific of which virtual machine or NVE one is referring to. By the end of the fourth paragraph of Section 4.1, it is very difficult to understand which VM one is talking about, the source or the destination. The same is true about the NVE. Is it the old or the new NVE? The next paragraph starts by saying that RARP is not used by VMs because VM already knows about its IP address. It then goes on to describe how a end-user client (a new term, not defined before) goes about getting the same IP address using RARP. It concludes by saying that that is how IP address assignment is completed for a migrating VM. s/central directory at the NVA/central directory of the NVA/ s/recorded to the entry/recorded in the entry/ Also who is “we” in Section 4.2, first paragraph? Also what is “guests”? Would strongly suggest that the authors discuss the Connection migration strategy with TCPM WG to understand if their proposal makes sense, as I do not understand the term “reopen dropped connections”, nor how a connection can be “paused”. Finally, in Section 7, the document claims that in a hot standby option, the VMs in both primary and secondary domains have identical information and can provide services simultaneously. Does it mean that a TCP connection can talk to two different VMs at the same time? If so, who is replicating the information to the two VMs and how is the duplicate information coming from either of the sources quashed? The following comments look at the document both from an operational perspective as well as a management perspective. Operational Considerations: Operational considerations include installation and initial setup, migration path, requirements on other protocols, impact on network operations and verification of correct operation. The document is a BCP, so it is not expected to provide any operational considerations. Management Considerations: Management considerations include interoperability, fault management, configuration management, accounting, performance and security. The document is a BCP, so it is not expected to provide any management considerations.
- [nvo3] Opsdir last call review of draft-ietf-nvo3… Mahesh Jethanandani
- Re: [nvo3] Opsdir last call review of draft-ietf-… Bocci, Matthew (Nokia - GB)
- Re: [nvo3] Opsdir last call review of draft-ietf-… Behcet Sarikaya