[armd] Gen-art] review: draft-ietf-armd-problem-statement-03

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 10 August 2012 02:28 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: armd@ietfa.amsl.com
Delivered-To: armd@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 81CB721F8646; Thu, 9 Aug 2012 19:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id qpZ8ls+y1mzc; Thu, 9 Aug 2012 19:28:55 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net []) by ietfa.amsl.com (Postfix) with ESMTP id 054BE21F8644; Thu, 9 Aug 2012 19:28:55 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net []) by morbo.tigertech.net (Postfix) with ESMTP id D79AF557F2F; Thu, 9 Aug 2012 19:28:54 -0700 (PDT)
Received: from localhost (localhost []) by mailc2.tigertech.net (Postfix) with ESMTP id 072541619C1; Thu, 9 Aug 2012 19:28:54 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [] (c-71-204-207-35.hsd1.de.comcast.net []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 159421619C0; Thu, 9 Aug 2012 19:28:52 -0700 (PDT)
Message-ID: <502471DB.80303@joelhalpern.com>
Date: Thu, 09 Aug 2012 22:28:43 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <50243C05.3080006@nostrum.com>
In-Reply-To: <50243C05.3080006@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, "armd@ietf.org" <armd@ietf.org>
Subject: [armd] Gen-art] review: draft-ietf-armd-problem-statement-03
X-BeenThere: armd@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion of issues associated with large amount of virtual machines being introduced in data centers and virtual hosts introduced by Cloud Computing." <armd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/armd>, <mailto:armd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/armd>
List-Post: <mailto:armd@ietf.org>
List-Help: <mailto:armd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/armd>, <mailto:armd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 02:28:55 -0000

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-armd-problem-statement-03
     Problem Statement for ARMD
Reviewer: Joel M. Halpern
Review Date: 9-Aug-2012
IETF LC End Date: 23-Aug-2012
IESG Telechat date: N/A

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

Major issues:
     The use of the term "switch" seems confusing.  I had first assumed 
that it meant an ethernet switch (which might have  abit of L3 smarts, 
or might not.  I was trying not to be picky.)  But then, in section 6.3 
it refers to "core switches ... are the data center gateways to external 
networks" which means that those are routers.

Moderate Issue:
    The document seems to be interestingly selective in what modern 
technologies it chooses to mention.  Mostly it seems to be describing 
problems with data center networks using technology more than 5 years 
old.  Since that is the widely deployed practice, that is defensible. 
But then the document chooses to mention new work such as OpenFlow, 
without mentioning the work IEEE has done on broadcast ad multicast 
containment for data centers.  It seems to me that we need to be 
consistent, either describing only the widely deployed technology, or 
including a fair mention of already defined and productized solutions 
that are not yet widely deployed.

     On a related note, the document assumes that multicast NDs are 
delivered to all nodes, while in practice I believe existing techniques 
to filter such multicast messages closer to the source are widely 
deployed.  (Section 5.)

Minor issues:
     I presume that section 6.4.2 which describes needing to enable all 
VLANs on all aggregation ports is a description of current practice, 
since it is not a requirement of current technologies, either via VLAN 
management or orchestration?

     Section 6.4.4 seems very odd.  The title is "overlays".  Are there 
widely deployed overlays?  If so, it would be good to name the 
technologies being referred to here.  If this is intended to refer to 
the overlay proposal in IETF and IEEE, I think that the characterization 
is somewhat misleading, and probably is best simply removed.

     Is the fifth paragraph of section 71. on ARP processing and 
buffering in the absence of ARP cache entries accurate?  I may well be 
out of date, but it used to be the case that most routers dropped the 
packets, and some would buffer 1 packet deep at most.  This description 
indicates a rather more elaborate behavior.

     Given that this document says it is a general document about 
scaling issues for data centers, I am surprised that the security 
considerations section does not touch on the increased complexity of 
segregating subscriber traffic (customer A can not talk to customer B) 
when there are very large numbers of customers, and the itneraction of 
this with L2 scope.

Nits/editorial comments: