IETF Logo Mail Archive

Re: [Gen-art] Ge-ART LC review of draft-ietf-nvo3-framework-06

"LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com> Fri, 30 May 2014 07:46 UTC

Return-Path: <marc.lasserre@alcatel-lucent.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 216671A098C; Fri, 30 May 2014 00:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-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 PUmWo47CARY8; Fri, 30 May 2014 00:46:36 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61A591A0791; Fri, 30 May 2014 00:46:36 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s4U7kT35013013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 30 May 2014 02:46:31 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s4U7kSKF013560 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 30 May 2014 09:46:28 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.131]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Fri, 30 May 2014 09:46:28 +0200
From: "LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-nvo3-framework.all@tools.ietf.org" <draft-ietf-nvo3-framework.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Thread-Topic: Ge-ART LC review of draft-ietf-nvo3-framework-06
Thread-Index: Ac971XQVfkgPIzO6RGeICJVxgYwW8wAA32ZA
Date: Fri, 30 May 2014 07:46:27 +0000
Message-ID: <B30152B129674240ADF67727A967301408B68A@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <000a01cf7bd5$7bd76d40$738647c0$@gmail.com>
In-Reply-To: <000a01cf7bd5$7bd76d40$738647c0$@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.38]
Content-Type: multipart/alternative; boundary="_000_B30152B129674240ADF67727A967301408B68AFR711WXCHMBA03zeu_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/AWlFmZ--E6oZFm7OL_RrIwrhH7s
X-Mailman-Approved-At: Fri, 30 May 2014 05:51:05 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Ge-ART LC review of draft-ietf-nvo3-framework-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 May 2014 07:46:39 -0000

Hi Roni,

Thanks for your feedback. See my replies below.

Marc

________________________________
From: Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: Friday, May 30, 2014 9:05 AM
To: draft-ietf-nvo3-framework.all@tools.ietf.org; ietf@ietf.org
Cc: gen-art@ietf.org
Subject: Ge-ART LC review of draft-ietf-nvo3-framework-06

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Please resolve these comments along with any other Last Call comments you may receive.

Document:  draft-ietf-nvo3-framework-06

Reviewer: Roni Even

Review Date:2014-5-30

IETF LC End Date: 2014-6-4

IESG Telechat date:



Summary: This draft is almost ready for publication as an Informational RFC.





Major issues:



Minor issues:



I think that the first sentence in section 1 is more in line with the title of the document than the abstract. Propose to change the abstract to mention Data Center.



Agreed. The abstract will be changed to:



This document provides a framework for Data Center (DC) Network Virtualization Overlays (NVO3) and it defines a reference model along with logical components required to design a solution.


Nits/editorial comments:


  1.  In section 1.2 ToR and EoR are given as example. Are these well known or is there a need for reference?

ToR and EoR switches are well-known in the DC space. There is no standards definition of these terms that I know of.

  1.  Section 4.1 title is Pros and Cons. My reading of the section is that is more about "general issues and challenges of the overlay" as written in section 4 above 4.1. Section 4.2 is about specific issues to consider.

The begining of section 4.1 describes the benefits of overlays and the latter part of 4.1 discusses general challenges. Hence the title of this section.

  1.  In section 5 "When an NVE receives data from a TS", this is the first time the abbreviation appears in the document maybe just change to Tennant System.

  Agreed. It will be changed to Tenant System.

v2.23.0 | Report a Bug | By Email