[dc] Comment of draft-dalela-dc-requirements
Lizhong Jin <lizho.jin@gmail.com> Mon, 09 January 2012 15:00 UTC
Return-Path: <lizho.jin@gmail.com>
X-Original-To: dc@ietfa.amsl.com
Delivered-To: dc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E581221F8783 for <dc@ietfa.amsl.com>; Mon, 9 Jan 2012 07:00:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uya3WfLKvjPD for <dc@ietfa.amsl.com>; Mon, 9 Jan 2012 07:00:11 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA5D21F877A for <dc@ietf.org>; Mon, 9 Jan 2012 07:00:11 -0800 (PST)
Received: by qadz3 with SMTP id z3so2213523qad.10 for <dc@ietf.org>; Mon, 09 Jan 2012 07:00:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=QUJkVHUr0un7X2X36SEexRcbkuDEJqEjqN3RQIxmPDI=; b=LcfQOXY8iStMLx2tDPYj7W4G780vSigtlaU28nb/KX3b1rt/6oDljBBjMmACZBKQVe 3ENQBkT724fWRK9t8cop1YITDSec2HRLZRCkMH5NZA+ht5IisfdVuttsi83Tkb5hRz5s 37dLjCnv2RjmUXGbcX/ug+k25tadNn471d60Y=
MIME-Version: 1.0
Received: by 10.224.31.202 with SMTP id z10mr19144405qac.96.1326121210773; Mon, 09 Jan 2012 07:00:10 -0800 (PST)
Received: by 10.224.52.200 with HTTP; Mon, 9 Jan 2012 07:00:10 -0800 (PST)
Date: Mon, 09 Jan 2012 23:00:10 +0800
Message-ID: <CAH==cJxfmae0u0bSF4cn_haLgY1T-vnw2102PApzYtj5Aty=GQ@mail.gmail.com>
From: Lizhong Jin <lizho.jin@gmail.com>
To: adalela@cisco.com
Content-Type: multipart/alternative; boundary="20cf3074b14cb2814b04b619a7b4"
X-Mailman-Approved-At: Mon, 09 Jan 2012 08:27:37 -0800
Cc: Lizhong Jin <lizhong.jin@zte.com.cn>, dc@ietf.org
Subject: [dc] Comment of draft-dalela-dc-requirements
X-BeenThere: dc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Data Center Mailing List <dc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dc>, <mailto:dc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dc>
List-Post: <mailto:dc@ietf.org>
List-Help: <mailto:dc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dc>, <mailto:dc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jan 2012 15:00:12 -0000
Hi Ashish, I have several comments to this requirement. Thanks. Section 5.3, Multi-tenancy problem. From my side, the multi-tenancy problem is not only the scalability of segmentation-ID problem, it is also required to isolate performance and security among multi-tenant. For example, one tenant should not suffer denial-of-service attacks by other tenant within same datacenter. A detailed example is, the huge broadcast traffic from one tenant should not influence the performace and availability of other tenants. Section 5.3, "The use of L3 VRFs also poses similar challenges of scaling". The challenge for VRF is quite different with VLAN. The challenge for VRF is the scalability of forwarding table. And you also said:"With VRFs, these entries will be present even if there is no traffic from a host to other hosts in the VRF". I think this could be optimized that the FIB would store only active route entries, while the RIB would store all route entries. Section 5.5, last paragraph about mobility. It seems that this paragraph is not much related with "network convergence", but is about "host mobility impact to the network resource". While I find that, section 5.1 is about the "host mobility impact to L2/3 forwarding", 5.10 is about the "host mobility impact to forwarding tables". Suggest to re-organize the three parts which are all related with impact of host mobility. Regards Lizhong
- [dc] Comment of draft-dalela-dc-requirements Lizhong Jin
- Re: [dc] Comment of draft-dalela-dc-requirements Ashish Dalela (adalela)
- Re: [dc] Comment of draft-dalela-dc-requirements Lizhong Jin
- Re: [dc] Comment of draft-dalela-dc-requirements Bhumip Khasnabish
- [dc] draft-khasnabish-vmmi-problems-00.txt Thomas Narten
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Bhumip Khasnabish
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Christopher LILJENSTOLPE
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Thomas Narten
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Steven Blake
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Ashish Dalela (adalela)
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Steven Blake
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Thomas Narten
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Ashish Dalela (adalela)
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Ashish Dalela (adalela)
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Christopher LILJENSTOLPE
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Melinda Shore
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt david.black
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Ashish Dalela (adalela)
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Ashish Dalela (adalela)
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Melinda Shore
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Ashish Dalela (adalela)
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Joel M. Halpern
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Ashish Dalela (adalela)
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Melinda Shore
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Joel M. Halpern
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt vishwas.ietf
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Ashish Dalela (adalela)
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Ashish Dalela (adalela)
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Melinda Shore
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Thomas Narten
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Vishwas Manral
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Melinda Shore
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Christopher LILJENSTOLPE
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Vishwas Manral
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Christopher LILJENSTOLPE
- [dc] OVF "control plane" - Not a good idea david.black
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Vishwas Manral
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Juergen Schoenwaelder
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Bhumip Khasnabish
- Re: [dc] OVF "control plane" - Not a good idea Bhumip Khasnabish
- Re: [dc] OVF "control plane" - Not a good idea david.black
- Re: [dc] OVF "control plane" - Not a good idea Bhumip Khasnabish
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Donald Eastlake
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Bhumip Khasnabish
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Juergen Schoenwaelder