Re: [arp222] ARP222 Charter statement and milestones

Benson Schliesser <bensons@queuefull.net> Thu, 26 August 2010 20:11 UTC

Return-Path: <bensons@queuefull.net>
X-Original-To: arp222@core3.amsl.com
Delivered-To: arp222@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5649C3A68F3 for <arp222@core3.amsl.com>; Thu, 26 Aug 2010 13:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level:
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cuUgjqcGa3o9 for <arp222@core3.amsl.com>; Thu, 26 Aug 2010 13:11:22 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id B74B23A69AD for <arp222@ietf.org>; Thu, 26 Aug 2010 13:11:21 -0700 (PDT)
Received: by gwb20 with SMTP id 20so1005365gwb.31 for <arp222@ietf.org>; Thu, 26 Aug 2010 13:11:54 -0700 (PDT)
Received: by 10.151.141.12 with SMTP id t12mr860508ybn.89.1282853513954; Thu, 26 Aug 2010 13:11:53 -0700 (PDT)
Received: from [192.168.1.105] (24-241-105-11.static.stls.mo.charter.com [24.241.105.11]) by mx.google.com with ESMTPS id q21sm3094757ybk.23.2010.08.26.13.11.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 26 Aug 2010 13:11:52 -0700 (PDT)
From: Benson Schliesser <bensons@queuefull.net>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-44--396367245
Date: Thu, 26 Aug 2010 15:11:50 -0500
In-Reply-To: <00f901cb3a74$1bb07e80$5d0c7c0a@china.huawei.com>
To: Linda Dunbar <ldunbar@huawei.com>, arp222@ietf.org
References: <00f901cb3a74$1bb07e80$5d0c7c0a@china.huawei.com>
Message-Id: <1188AC2B-0E47-45FD-8CA3-F755B24A0E2E@queuefull.net>
X-Mailer: Apple Mail (2.1081)
Subject: Re: [arp222] ARP222 Charter statement and milestones
X-BeenThere: arp222@ietf.org
X-Mailman-Version: 2.1.9
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." <arp222.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/arp222>, <mailto:arp222-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/arp222>
List-Post: <mailto:arp222@ietf.org>
List-Help: <mailto:arp222-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/arp222>, <mailto:arp222-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Aug 2010 20:11:23 -0000

Linda -

I'd like to see a few modifications to the charter you've outlined:

1) I've already explained why I think the last design goal (overlapping IP addresses within a single VLAN) should be removed.  I won't reiterate that here.

2) The goal to "not break DHCP" should be modified to include any broadcast and/or multicast protocols.  (Alternatively, broadcast and multicast support can be required by a new goal to be added.)

3) The goal of supporting interconnect scenarios should explicitly include L3VPN.  In case it isn't clear, that implies a goal of support for overlapping IP addresses within the datacenter. (Albeit in different broadcast domains, my comments in #1 above notwithstanding.)

4) A new goal should include a performance analysis of all solutions considered.  This might explicitly acknowledge a role for negative caching approaches, but that shouldn't be a requirement.

Cheers,
-Benson



On 12 Aug 10, at 6:14 PM, Linda Dunbar wrote:

> Thank you all for coming to ARP222 Bar BOF at the 78th IETF and giving us comments and suggestions on and between sessions.
>  
> I put together the initial ARP222 Charter Statement and Milestones. Please provide comments and suggestions.  
>  
>  
>  
>  
> ARP 222: Address Resolution Protocol for Layer 2 to Anything to Layer 2
>  
> Description of Working Group:
> As server virtualization is introduced to data centers, the number of hosts in a data center can grow dramatically because each physical server, which used to host one end-station, now can host many end-stations, or Virtual Machines (20, 30, or hundreds of). Virtual Machines, with its flexible add/delete and mobility features, not only makes it possible for achieving better performance and better utilization on servers, they are also a very important building block for Cloud Computing service to offer virtual subnets and virtual hosts. The virtual subnets offered by Cloud Computing service could allow clients to define their own subnets with its own IP addresses and policies.
> 
> This rapid growth of virtual hosts could tremendously impact to networks and servers. One huge issue is frequent address resolution (IPv4) or neighbor discovery (IPv6) requests from hosts. All hosts frequently send out those requests due to their cache being aged out in minutes. With tens of thousands of hosts (each with a distinct MAC address) in one Data Center, the amount of address resolution packets per second is potentially more than 1,000 to 10,000/second. This rate imposes tremendous computational burden on many hosts.
> 
> Another big issue associated with huge number of virtual hosts in a data center is potentially duplicated IP addresses within one VLAN which will make traditional ARP or ND not working properly. Some load balance design requires multiple hosts serving the same application to have the same IP address but with different MAC addresses. Cloud Computing service could allow users to have their own subnets with IP addresses and self defined policies among those subnets. Some network designs need to put multiple client subnets into one VLAN because the number of client subnets could be in hundreds of thousands which is much more than 4095 VLANs. Under this scenario, there could be duplicated IP addresses which are from different client subnets ending up in one VLAN. 
> 
> The goal of this working group is to develop interoperable solutions to solve those problems. 
> 
> The design should consider the following properties:
> All solutions developed by ARP222 WG should not expect any behavior changes on hosts, applications, or Virtual Machines being deployed in the market.
> All solutions developed should not break DHCP.
> Evaluating the impact to IPv6 ND, and develop solutions accordingly if needed.
> Should consider variety of solutions, including directory based, proxy based, or cache based solutions.
> Include analysis of security concerns of IPv4 ARP requests from malicious users. Evaluating potential security solutions and conclude if the security threat can justify solutions.
> ARP222 assumes the direct links to individual hosts and virtual machines are IEEE802.3 Ethernet links. 
> Should consider scenarios of one Ethernet network being interconnected by another network, which can be L2VPN, pure IP, Ethernet, or others.
> Should consider address resolution solutions for one VLAN with small number of duplicated IP addresses.  
>  
> Here are the items which should not be in the scope of the working group:
> Re-define DHCP behavior
> Re-define security concern to IPv6 ND
> Direct links from hosts and virtual hosts are non Ethernet links
>  
>  
> Goals and Milestones:
> Charter statement
> Problem Statements
> Gap analysis
> Study of NHRP (RFC2332) & SCSP,  and their applicability to Ethernet networks
> Study and Analysis of MOOSE as a potential solution
> Study and Analysis of SEATTLE as a potential solution.
>  
>  
> Best Regards, Linda Dunbar
>  
> _______________________________________________
> arp222 mailing list
> arp222@ietf.org
> https://www.ietf.org/mailman/listinfo/arp222