Re: [arp222] ARP222 Charter statement and milestones

[Anoop Ghanwani <[e-mail]>]

Linda,

If it broadcasts from one client controlled subnet do not
show up in another client controlled subnet, then this
should be a non-issue, no?

Anoop

From: Linda Dunbar [mailto:[e-mail]]
Sent: Monday, August 23, 2010 2:33 PM
To: Anoop Ghanwani; [e-mail]
Subject: RE: [arp222] ARP222 Charter statement and milestones

Anoop,

No, it shouldn't.

Linda

________________________________
From: Anoop Ghanwani [mailto:[e-mail]]
Sent: Friday, August 13, 2010 6:19 PM
To: Linda Dunbar; [e-mail]
Subject: RE: [arp222] ARP222 Charter statement and milestones

Linda,

Do broadcasts from one client controlled subnet show up
in a different client controlled subnet?

Anoop

From: Linda Dunbar [mailto:[e-mail]]
Sent: Friday, August 13, 2010 2:44 PM
To: Anoop Ghanwani; [e-mail]
Subject: RE: [arp222] ARP222 Charter statement and milestones

Anoop,

The scenario is Cloud Computing service selling client controlled (virtual) subnets to clients. All the (virtual) hosts within the client controlled subnets have their own IP addresses. The communications among those (virtual) hosts are client specific. There might be same IP addresses in different client controlled subnets. All those hosts will be assigned as a virtual machine to a physical server and assigned to a VLAN in the actual network in data center(s). There will be cases when one VLAN ends up having (virtual) hosts with same IP address (but different MAC address).

Linda

________________________________
From: Anoop Ghanwani [mailto:[e-mail]]
Sent: Friday, August 13, 2010 4:02 PM
To: Linda Dunbar; [e-mail]
Subject: RE: [arp222] ARP222 Charter statement and milestones

Hi Linda,

Would it be possible to provide references to actual protocols
that require duplicate IP addresses behind different MAC addresses?

Anoop

From: [e-mail] [mailto:[e-mail]] On Behalf Of Linda Dunbar
Sent: Friday, August 13, 2010 12:42 PM
To: [e-mail]
Subject: Re: [arp222] ARP222 Charter statement and milestones

I forgot to clarify in my previous email that the charter statement and milestones posted is for soliciting feedback before submitting to IESG to request for a BOF for IETF79 (Beijing).
We think the problem domain belongs to Internet Area. Therefore, once I get your feedback, I will send the Charter Statement and milestones to the Internet ADS (Ralph and Jari) to request for a BOF at the IETF79 (Beijing). Our target is to have a working group by IETF 80.

Linda Dunbar

________________________________
From: Linda Dunbar [mailto:[e-mail]]
Sent: Thursday, August 12, 2010 6:14 PM
To: '[e-mail]'
Subject: ARP222 Charter statement and milestones

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