From dunbar.ll@gmail.com Wed Jun 1 10:52:48 2011 Return-Path: X-Original-To: armd@ietfa.amsl.com Delivered-To: armd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 158F0E0957 for ; Wed, 1 Jun 2011 10:52:48 -0700 (PDT) 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UxyjZp-PRyMA for ; Wed, 1 Jun 2011 10:52:44 -0700 (PDT) Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 44960E07E6 for ; Wed, 1 Jun 2011 10:52:29 -0700 (PDT) Received: by bwz13 with SMTP id 13so297605bwz.31 for ; Wed, 01 Jun 2011 10:52:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=2veeofpTfUBgfaQELqMVr1WsYGS7J7JS4YbHRsTO1Ak=; b=uMf6Bd/t8eKFcRzQ9uFpgdSOhtUqNnwXZSxnmyp6p916L0+OXPKBbZkA8aHjB9GeAg 4J0Z2fkb4XFtiLTEyksBce2lr4h/Yf+rJSF0ww/AscPkRU7FTJveXeoTTetVmDtYpr3h /WH+KiGBEfeNSMfRkp+qlSnM6Cl5FDoPdwXDw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Zdd546dwz+sEFRSlS1QFBnyZkmfMrG6tuCgx2uC8u7czjUyrDm8cJyihWRw/VZQt6b ZZtEZXQjk51j4fJYQ/Mbqwu79M7UjRVFI+xN/V3P7UQT01yk/Pmm3yZ5Ka+FO6KiblUL 6O+dBRwhbYu2L8jqHG2njq/CBhetJUX++Ixrs= MIME-Version: 1.0 Received: by 10.204.189.74 with SMTP id dd10mr1316950bkb.174.1306950748118; Wed, 01 Jun 2011 10:52:28 -0700 (PDT) Received: by 10.204.38.6 with HTTP; Wed, 1 Jun 2011 10:52:28 -0700 (PDT) In-Reply-To: <20110531155510.28180.18677.idtracker@ietfa.amsl.com> References: <20110531155510.28180.18677.idtracker@ietfa.amsl.com> Date: Wed, 1 Jun 2011 12:52:28 -0500 Message-ID: From: Linda Dunbar To: armd@ietf.org Content-Type: multipart/alternative; boundary=20cf3033451d149e5204a4aa2f8b Subject: [armd] Fwd: I-D Action: draft-ietf-armd-call-for-investigation-00.txt 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2011 17:52:48 -0000 --20cf3033451d149e5204a4aa2f8b Content-Type: text/plain; charset=ISO-8859-1 Benson and I have arranged an ARMD session at June NANOG for data center operators to talk about address resolution scaling issues in their data centers. Here are speakers for the session (June 14, 4:30pm~6pm): > * Igor Gashinsky (Yahoo!) > * Michael K. Smith (Adhost) > * Scott Whyte (Google) > * Jimmy Williams (Facebook) > * Manish Karir (Merit) > * K.K. Ramakrishnan (AT&T Research) Linda & Benson ---------- Forwarded message ---------- From: Date: Tue, May 31, 2011 at 10:55 AM Subject: [armd] I-D Action: draft-ietf-armd-call-for-investigation-00.txt To: i-d-announce@ietf.org Cc: armd@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Address Resolution for Massive numbers of hosts in the Data center Working Group of the IETF. Title : ARMD Call for Investigation Author(s) : Benson Schliesser Linda Dunbar Filename : draft-ietf-armd-call-for-investigation-00.txt Pages : 5 Date : 2011-05-31 This document is a call for investigation into the topic of address resolution in massive datacenters. It describes the intended work of the ARMD working group, providing both context and direction for investigating the issues outlined in the working group's charter. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-armd-call-for-investigation-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-armd-call-for-investigation-00.txt _______________________________________________ armd mailing list armd@ietf.org https://www.ietf.org/mailman/listinfo/armd --20cf3033451d149e5204a4aa2f8b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Benson and I have arranged an ARMD session at June NANOG for data cent= er operators to talk about address resolution scaling issues in their data = centers.
=A0
Here are speakers for the session (June 14, =A04:30pm~6pm):
=A0

> * Igor Gashinsky (Yahoo!)

> * Michael K. Smith (Adhost)

> * Scott Whyte (Google)

> * Jimmy Williams (Facebook)

> * Manish Karir (Merit)

> * K.K. Ramakrishnan (AT&T Research)

Linda & Benson


---------- Forwarded message ----------
From:= <internet-drafts@ietf.org>
Date: = Tue, May 31, 2011 at 10:55 AM
Subject: [armd] I-D Action: draft-ietf-armd-call-for-investigation-00.txtTo: i-d-announce@ietf.orgCc: armd@ietf.org


A New In= ternet-Draft is available from the on-line Internet-Drafts directories. Thi= s draft is a work item of the Address Resolution for Massive numbers of hos= ts in the Data center Working Group of the IETF.

=A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : ARMD Call for Investigation<= br>=A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Benson Schliesser
=A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Linda Dunbar
=A0 =A0 =A0 =A0Filen= ame =A0 =A0 =A0 =A0: draft-ietf-armd-call-for-investigation-00.txt
=A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 5
=A0 =A0 =A0 =A0Date =A0 =A0= =A0 =A0 =A0 =A0: 2011-05-31

=A0 This document is a call for investi= gation into the topic of address
=A0 resolution in massive datacenters. = =A0It describes the intended work of
=A0 the ARMD working group, providing both context and direction for
=A0= investigating the issues outlined in the working group&#39;s charter.<= br>

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-armd-call-for-in= vestigation-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/in= ternet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-iet= f-armd-call-for-investigation-00.txt
_______________________________________________
armd mailing list
armd@ietf.org
https://www.ietf.org/mailm= an/listinfo/armd

--20cf3033451d149e5204a4aa2f8b-- From bschlies@cisco.com Thu Jun 2 10:35:37 2011 Return-Path: X-Original-To: armd@ietfa.amsl.com Delivered-To: armd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE55E06FB for ; Thu, 2 Jun 2011 10:35:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.25 X-Spam-Level: X-Spam-Status: No, score=-10.25 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zpJdOiz+MK3H for ; Thu, 2 Jun 2011 10:35:35 -0700 (PDT) Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfa.amsl.com (Postfix) with ESMTP id D52E0E05D3 for ; Thu, 2 Jun 2011 10:35:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bschlies@cisco.com; l=730; q=dns/txt; s=iport; t=1307036135; x=1308245735; h=date:subject:from:to:message-id:mime-version: content-transfer-encoding; bh=ETK96W51b4kdBAMxsRRyCvMJCfzQoY8mSt27GMdUfD8=; b=f8HVV2gvOaAsRo6wmh2+GR9b0kF4lgUgc+FEJol2WiLvsyUVtB/H3Cc0 x7t7pqX++Ye9dIReZ1iBg0tQi1ubLyEkr5IWBdFGkUZg7Kjivb9Q9HplN XpJNixx3pJ093PsZzzjYjemKIUPygsY6x4Lhpu8xPP8iUpnfh3zX0sEA7 w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhoFACTJ502tJXG+/2dsb2JhbABTpjpwB6ougR2dZYYhBIZpiX6ETosA X-IronPort-AV: E=Sophos;i="4.65,310,1304294400"; d="scan'208";a="369092607" Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by sj-iport-2.cisco.com with ESMTP; 02 Jun 2011 17:35:35 +0000 Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id p52HZZ5u017802 for ; Thu, 2 Jun 2011 17:35:35 GMT Received: from xmb-rcd-206.cisco.com ([72.163.62.213]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 2 Jun 2011 12:35:34 -0500 Received: from 10.21.122.246 ([10.21.122.246]) by XMB-RCD-206.cisco.com ([72.163.62.213]) via Exchange Front-End Server email.cisco.com ([128.107.191.114]) with Microsoft Exchange Server HTTP-DAV ; Thu, 2 Jun 2011 17:35:35 +0000 User-Agent: Microsoft-Entourage/12.29.0.110113 Date: Thu, 02 Jun 2011 12:37:04 -0500 From: Benson Schliesser To: "armd@ietf.org" Message-ID: Thread-Topic: Scheduling ARMD meeting for IETF 81 Thread-Index: AcwhS6+lLuaWeZeKd0WEbadPeKHKYQ== Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable X-OriginalArrivalTime: 02 Jun 2011 17:35:35.0032 (UTC) FILETIME=[7A9DAF80:01CC214B] Subject: [armd] Scheduling ARMD meeting for IETF 81 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 17:35:37 -0000 As you may be aware, the next IETF meeting (IETF 81 in Quebec) is quickly approaching. In order to plan for an ARMD session, Linda and I would like to hear from anybody that plans to request time on the agenda. There has been very little ARMD activity since our previous meeting in Prague, and no new document submissions =AD this makes it hard to determine how much time to request for our session. If you intend to request agenda time, please send a note ASAP to armd-chairs@tools.ietf.org expressing interest and describing your topic. (Please note that we will probably ask you to submit an I-D before granting an agenda timeslot, so be sure to mention any draft submission plans.) Thanks, -Benson and Linda From ning.so@verizonbusiness.com Thu Jun 2 12:36:18 2011 Return-Path: X-Original-To: armd@ietfa.amsl.com Delivered-To: armd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B319DE0898 for ; Thu, 2 Jun 2011 12:36:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4gjfJHZLRbPC for ; Thu, 2 Jun 2011 12:36:18 -0700 (PDT) Received: from ashesmtp01.verizonbusiness.com (ashesmtp01.verizonbusiness.com [198.4.8.163]) by ietfa.amsl.com (Postfix) with ESMTP id 1E672E0897 for ; Thu, 2 Jun 2011 12:36:17 -0700 (PDT) Received: from pdcismtp02.vzbi.com ([unknown] [166.40.77.70]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LM600FTCH4DTS80@firewall.verizonbusiness.com> for armd@ietf.org; Thu, 02 Jun 2011 19:36:14 +0000 (GMT) Received: from pdcismtp02.vzbi.com ([unknown] [127.0.0.1]) by pdcismtp02.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LM600HH6H4D3T00@pdcismtp02.vzbi.com> for armd@ietf.org; Thu, 02 Jun 2011 19:36:13 +0000 (GMT) Received: from ASHSRV142.mcilink.com ([unknown] [153.39.68.168]) by pdcismtp02.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0LM600H76H4D3V00@pdcismtp02.vzbi.com> for armd@ietf.org; Thu, 02 Jun 2011 19:36:13 +0000 (GMT) Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV142.mcilink.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 02 Jun 2011 19:36:13 +0000 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Date: Thu, 02 Jun 2011 19:36:11 +0000 Message-id: <14584D6EE26B314187A4F68BA2060600079092A9@ASHEVS008.mcilink.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-topic: Scheduling ARMD meeting for IETF 81 Thread-index: AcwhS6+lLuaWeZeKd0WEbadPeKHKYQAEE9Dw From: "So, Ning" To: Benson Schliesser , armd@ietf.org X-OriginalArrivalTime: 02 Jun 2011 19:36:13.0819 (UTC) FILETIME=[5544ECB0:01CC215C] Subject: Re: [armd] Scheduling ARMD meeting for IETF 81 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2011 19:36:18 -0000 Benson and Linda, Thanks for the reminder. I intend to submit a draft on Address Resolution for VPN-oriented Cloud Service before the deadline (nothing gets done if no deadlines). I will send an official slot request after draft submission. =20 =20 Best regards, =20 Ning So Network Evolution Planning Verizon, Inc. (office) 972-729-7905 (Cell) 972-955-0914 =20 -----Original Message----- From: armd-bounces@ietf.org [mailto:armd-bounces@ietf.org] On Behalf Of Benson Schliesser Sent: Thursday, June 02, 2011 12:37 PM To: armd@ietf.org Subject: [armd] Scheduling ARMD meeting for IETF 81 As you may be aware, the next IETF meeting (IETF 81 in Quebec) is quickly approaching. In order to plan for an ARMD session, Linda and I would like to hear from anybody that plans to request time on the agenda. There has been very little ARMD activity since our previous meeting in Prague, and no new document submissions - this makes it hard to determine how much time to request for our session. If you intend to request agenda time, please send a note ASAP to armd-chairs@tools.ietf.org expressing interest and describing your topic. (Please note that we will probably ask you to submit an I-D before granting an agenda timeslot, so be sure to mention any draft submission plans.) Thanks, -Benson and Linda _______________________________________________ armd mailing list armd@ietf.org https://www.ietf.org/mailman/listinfo/armd From mkarir@merit.edu Fri Jun 3 20:33:53 2011 Return-Path: X-Original-To: armd@ietfa.amsl.com Delivered-To: armd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9412CE06D1 for ; Fri, 3 Jun 2011 20:33:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WC9VSgYUNccM for ; Fri, 3 Jun 2011 20:33:52 -0700 (PDT) Received: from int-mailstore01.merit.edu (int-mailstore01.merit.edu [207.75.116.232]) by ietfa.amsl.com (Postfix) with ESMTP id A7B21E06C5 for ; Fri, 3 Jun 2011 20:33:52 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by int-mailstore01.merit.edu (Postfix) with ESMTP id C2AA33083A4D; Fri, 3 Jun 2011 23:33:51 -0400 (EDT) X-Virus-Scanned: amavisd-new at int-mailstore01.merit.edu Received: from int-mailstore01.merit.edu ([127.0.0.1]) by localhost (int-mailstore01.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wXNktRY-m6Mc; Fri, 3 Jun 2011 23:33:51 -0400 (EDT) Received: from int-mailstore01.merit.edu (int-mailstore01.merit.edu [10.108.1.232]) by int-mailstore01.merit.edu (Postfix) with ESMTP id 79A903055F93; Fri, 3 Jun 2011 23:33:51 -0400 (EDT) References: <14584D6EE26B314187A4F68BA2060600079092A9@ASHEVS008.mcilink.com> Content-Transfer-Encoding: quoted-printable From: Manish Karir Content-Type: text/plain; charset=us-ascii In-Reply-To: <14584D6EE26B314187A4F68BA2060600079092A9@ASHEVS008.mcilink.com> Message-Id: <563DC091-FDFD-478D-AE51-FD1E9AF47F98@merit.edu> Date: Fri, 3 Jun 2011 23:33:49 -0400 (EDT) To: "armd@ietf.org" Mime-Version: 1.0 X-Mailer: Zimbra 6.0.10_GA_2692 (MobileSync - Apple-iPad2C1/810.2) Subject: Re: [armd] Scheduling ARMD meeting for IETF 81 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 03:33:53 -0000 We have been running some simple measurements of arp/nd traffic under diffe= rent scenarios and would like to share our preliminary results with the com= munity and get feedback.=20 Thanks.=20 -manish >=20 > -----Original Message----- > From: armd-bounces@ietf.org [mailto:armd-bounces@ietf.org] On Behalf Of > Benson Schliesser > Sent: Thursday, June 02, 2011 12:37 PM > To: armd@ietf.org > Subject: [armd] Scheduling ARMD meeting for IETF 81 >=20 > As you may be aware, the next IETF meeting (IETF 81 in Quebec) is > quickly approaching. In order to plan for an ARMD session, Linda and I > would like to hear from anybody that plans to request time on the > agenda. >=20 > There has been very little ARMD activity since our previous meeting in > Prague, and no new document submissions - this makes it hard to > determine how much time to request for our session. If you intend to > request agenda time, please send a note ASAP to > armd-chairs@tools.ietf.org expressing interest and describing your > topic. (Please note that we will probably ask you to submit an I-D > before granting an agenda timeslot, so be sure to mention any draft > submission plans.) >=20 > Thanks, > -Benson and Linda >=20 > _______________________________________________ > armd mailing list > armd@ietf.org > https://www.ietf.org/mailman/listinfo/armd > _______________________________________________ > armd mailing list > armd@ietf.org > https://www.ietf.org/mailman/listinfo/armd From bernard_aboba@hotmail.com Sun Jun 5 10:19:40 2011 Return-Path: X-Original-To: armd@ietfa.amsl.com Delivered-To: armd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26E0211E809B for ; Sun, 5 Jun 2011 10:19:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.739 X-Spam-Level: X-Spam-Status: No, score=-100.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iV1ZewPIJVRa for ; Sun, 5 Jun 2011 10:19:39 -0700 (PDT) Received: from blu0-omc4-s34.blu0.hotmail.com (blu0-omc4-s34.blu0.hotmail.com [65.55.111.173]) by ietfa.amsl.com (Postfix) with ESMTP id 86D8811E809A for ; Sun, 5 Jun 2011 10:19:39 -0700 (PDT) Received: from BLU152-W2 ([65.55.111.137]) by blu0-omc4-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 5 Jun 2011 10:19:39 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_ee5a5b1a-d42e-43d5-8ad2-f31be3dc2df0_" X-Originating-IP: [75.164.145.100] From: Bernard Aboba To: Date: Sun, 5 Jun 2011 10:19:38 -0700 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 05 Jun 2011 17:19:39.0283 (UTC) FILETIME=[C02F3630:01CC23A4] Subject: [armd] For your consideration: DNA 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2011 17:19:40 -0000 --_ee5a5b1a-d42e-43d5-8ad2-f31be3dc2df0_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable When analyzing the behavior of ARP and ND within the context of ARMD=2C may= I suggest that the WG consider DNA:=20 DNAv4: RFC 4436 DNAv6: RFC 6059 DNA was designed to allow rapid network re-configuration for mobile hosts. = Since it utilizes unicast ARP/ND rather than multicast=2C it has somewhat= different scaling properties than classic ARP/ND.=20 Since DNAv4 is now widely implemented within flat L2 networks where dense d= eployments have been experienced (e.g. on college campuses with tens of tho= usands of iPhone/iPad users)=2C information on deployment experiences may b= e available.=20 = --_ee5a5b1a-d42e-43d5-8ad2-f31be3dc2df0_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable When analyzing the behavior of ARP and ND within the context of ARMD=2C may= I suggest that the WG consider DNA:

DNAv4: =3B RFC 4436
DNA= v6: =3B RFC 6059

DNA was designed to allow rapid network re-conf= iguration for mobile hosts. =3B =3B Since it utilizes unicast ARP/N= D rather than multicast=2C it has somewhat different scaling properties tha= n classic ARP/ND.

Since DNAv4 is now widely implemented within flat= L2 networks where dense deployments have been experienced (e.g. on college= campuses with tens of thousands of iPhone/iPad users)=2C information on de= ployment experiences may be available.
= --_ee5a5b1a-d42e-43d5-8ad2-f31be3dc2df0_-- From bernard_aboba@hotmail.com Sun Jun 5 15:20:00 2011 Return-Path: X-Original-To: armd@ietfa.amsl.com Delivered-To: armd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0835821F84D0 for ; Sun, 5 Jun 2011 15:20:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.999 X-Spam-Level: X-Spam-Status: No, score=-100.999 tagged_above=-999 required=5 tests=[AWL=0.999, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_65=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FnwbW7unH+qy for ; Sun, 5 Jun 2011 15:19:59 -0700 (PDT) Received: from blu0-omc4-s13.blu0.hotmail.com (blu0-omc4-s13.blu0.hotmail.com [65.55.111.152]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9F321F84CE for ; Sun, 5 Jun 2011 15:19:59 -0700 (PDT) Received: from BLU152-W7 ([65.55.111.136]) by blu0-omc4-s13.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 5 Jun 2011 15:19:58 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_fad87f2a-ff8f-4b0e-a58d-f8e481433d30_" X-Originating-IP: [64.134.134.41] From: Bernard Aboba To: , Date: Sun, 5 Jun 2011 15:19:58 -0700 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 05 Jun 2011 22:19:58.0714 (UTC) FILETIME=[B49A2DA0:01CC23CE] Subject: Re: [armd] For your consideration: DNA 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2011 22:20:00 -0000 --_fad87f2a-ff8f-4b0e-a58d-f8e481433d30_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable DNAv4 is implemented in Mac OS X as well as iOS and is turned on by default= . It has been available commercially since the first iPhone. If you have = a Mac=2C iPhone=2C iPad=2C iPod Touch=2C etc. you are most likely running D= NAv4.=20 Within current implementations=2C traces appear indicate that exchanges and= subsequent IP stack re-configuration complete within ~5 ms.=20 While much of RFC 4436 focuses on mobile scenarios=2C Section 2.4 addresses= the static addressing case.=20 Date: Sun=2C 5 Jun 2011 13:35:49 -0700 Subject: Re: [armd] For your consideration: DNA From: anoop@alumni.duke.edu To: bernard_aboba@hotmail.com With respect to data centers=2C is this basically suggesting that the ARP/N= Drefreshes to prevent the ARP/ND cache entries from timing out be donevia u= nicast rather than by broadcast/multicast? If so=2C are that OSes actually implement this? Thanks=2CAnoop On Sun=2C Jun 5=2C 2011 at 10:19 AM=2C Bernard Aboba wrote: When analyzing the behavior of ARP and ND within the context of ARMD=2C may= I suggest that the WG consider DNA:=20 DNAv4: RFC 4436 DNAv6: RFC 6059 DNA was designed to allow rapid network re-configuration for mobile hosts. = Since it utilizes unicast ARP/ND rather than multicast=2C it has somewhat= different scaling properties than classic ARP/ND.=20 Since DNAv4 is now widely implemented within flat L2 networks where dense d= eployments have been experienced (e.g. on college campuses with tens of tho= usands of iPhone/iPad users)=2C information on deployment experiences may b= e available.=20 =20 _______________________________________________ armd mailing list armd@ietf.org https://www.ietf.org/mailman/listinfo/armd = --_fad87f2a-ff8f-4b0e-a58d-f8e481433d30_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable DNAv4 is implemented in Mac OS X as well as iOS and is turned on by default= . =3B It has been available commercially since the first iPhone. = =3B If you have a Mac=2C iPhone=2C iPad=2C iPod Touch=2C etc. you are most = likely running DNAv4.

Within current implementations=2C traces appe= ar indicate that exchanges and subsequent IP stack re-configuration complet= e within ~5 ms.

While much of RFC 4436 focuses on mobile scenarios= =2C Section 2.4 addresses the static addressing case.

Date: Sun=2C 5 Jun 2011 13:35:49 -0700
Subject: Re: [armd] Fo= r your consideration: DNA
From: anoop@alumni.duke.edu
To: bernard_abo= ba@hotmail.com

With respect to data centers=2C is this basically sug= gesting that the ARP/ND
refreshes to prevent the ARP/ND cache entries f= rom timing out be done
via unicast rather than by broadcast/multi= cast?

If so=2C are that OSes actually implement this?

Thanks=2C
Anoop

On Sun=2C= Jun 5=2C 2011 at 10:19 AM=2C Bernard Aboba <=3Bbernard_aboba@hotmail.com>=3B wrote:
When analyzing the behavior of ARP and ND within the context of ARMD=2C may= I suggest that the WG consider DNA:

DNAv4: =3B RFC 4436
DNA= v6: =3B RFC 6059

DNA was designed to allow rapid network re-conf= iguration for mobile hosts. =3B =3B Since it utilizes unicast ARP/N= D rather than multicast=2C it has somewhat different scaling properties tha= n classic ARP/ND.

Since DNAv4 is now widely implemented within flat L2 networks where den= se deployments have been experienced (e.g. on college campuses with tens of= thousands of iPhone/iPad users)=2C information on deployment experiences m= ay be available.

_______________________________________________
armd mailing list
armd@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/armd


= --_fad87f2a-ff8f-4b0e-a58d-f8e481433d30_-- From christopher.morrow@gmail.com Tue Jun 7 08:36:12 2011 Return-Path: X-Original-To: armd@ietfa.amsl.com Delivered-To: armd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 793EB11E815A for ; Tue, 7 Jun 2011 08:36:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.3 X-Spam-Level: X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rkCGjg-vYnT4 for ; Tue, 7 Jun 2011 08:36:11 -0700 (PDT) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id D373A11E8118 for ; Tue, 7 Jun 2011 08:36:11 -0700 (PDT) Received: by pzk5 with SMTP id 5so2848166pzk.31 for ; Tue, 07 Jun 2011 08:36:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hwvFesVmgKECAq3MkVSKJ+ZQCFdY3Of9zcsyslCpow8=; b=CXqs2Xl2dG/zGPjkfw4AoNtE+vtvcd5g/j0Xpdgu4MUnj+AC3HhmSfyB65CNkJWl8C ApRzeSCzlESIMCSGiLOp6teYy8ZSpc/Cz7v4OvtGU3o3TcTAnNfG135U/srXYMpw7VGS q2zJObr7UxgzN1N9Ib7NLP4e+DmwpKVfQj+Fg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=pKGGf/gPajRfbqPyZT4IteZz0KLpaN9aIyig1SCTSYFDmm1CDsBXz8Q9TJMQGx4/uQ pfsd/djuAacsBtwvISqPnF3D/a5Hwu85d1ZYJ47CrNhL8kwW/H/oZQBqV+ltNaZQyy9Z XMqjDVbA4lrrk+wuy7fEqYW55ewFrrHZOb3SE= MIME-Version: 1.0 Received: by 10.68.38.133 with SMTP id g5mr208452pbk.83.1307460971498; Tue, 07 Jun 2011 08:36:11 -0700 (PDT) Sender: christopher.morrow@gmail.com Received: by 10.68.44.106 with HTTP; Tue, 7 Jun 2011 08:36:11 -0700 (PDT) In-Reply-To: References: Date: Tue, 7 Jun 2011 11:36:11 -0400 X-Google-Sender-Auth: _YRXkTMH8fx8QAojpVuXpgJ3-iM Message-ID: From: Christopher Morrow To: Bernard Aboba Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: armd@ietf.org Subject: Re: [armd] For your consideration: DNA 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 15:36:12 -0000 On Sun, Jun 5, 2011 at 6:19 PM, Bernard Aboba w= rote: > DNAv4 is implemented in Mac OS X as well as iOS and is turned on by > default.=A0 It has been available commercially since the first iPhone.=A0= If you > have a Mac, iPhone, iPad, iPod Touch, etc. you are most likely running > DNAv4. > > Within current implementations, traces appear indicate that exchanges and > subsequent IP stack re-configuration complete within ~5 ms. > This is the wrong side of the equation isn't it? (the router side at least in the meeting was the focus area initially?) Unicast or Multicast at the router side (default-gw) isn't likely to matter, it still has to decide for southbound packets with no neighbor in the table what to do, and reply to northbound requests from local hosts for NS/etc. -chris > While much of RFC 4436 focuses on mobile scenarios, Section 2.4 addresses > the static addressing case. > > ________________________________ > Date: Sun, 5 Jun 2011 13:35:49 -0700 > Subject: Re: [armd] For your consideration: DNA > From: anoop@alumni.duke.edu > To: bernard_aboba@hotmail.com > > With respect to data centers, is this basically suggesting that the ARP/N= D > refreshes to prevent the ARP/ND cache entries from timing out be done > via unicast rather than by broadcast/multicast? > If so, are that OSes actually implement this? > Thanks, > Anoop > > On Sun, Jun 5, 2011 at 10:19 AM, Bernard Aboba > wrote: > > When analyzing the behavior of ARP and ND within the context of ARMD, may= I > suggest that the WG consider DNA: > > DNAv4:=A0 RFC 4436 > DNAv6:=A0 RFC 6059 > > DNA was designed to allow rapid network re-configuration for mobile hosts= . > Since it utilizes unicast ARP/ND rather than multicast, it has somewhat > different scaling properties than classic ARP/ND. > > Since DNAv4 is now widely implemented within flat L2 networks where dense > deployments have been experienced (e.g. on college campuses with tens of > thousands of iPhone/iPad users), information on deployment experiences ma= y > be available. > > _______________________________________________ > armd mailing list > armd@ietf.org > https://www.ietf.org/mailman/listinfo/armd > > > > _______________________________________________ > armd mailing list > armd@ietf.org > https://www.ietf.org/mailman/listinfo/armd > > From bschlies@cisco.com Fri Jun 24 21:22:20 2011 Return-Path: X-Original-To: armd@ietfa.amsl.com Delivered-To: armd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35E1221F8489 for ; Fri, 24 Jun 2011 21:22:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OpxRoCdG7iVA for ; Fri, 24 Jun 2011 21:22:18 -0700 (PDT) Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by ietfa.amsl.com (Postfix) with ESMTP id 089E321F8488 for ; Fri, 24 Jun 2011 21:22:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bschlies@cisco.com; l=652; q=dns/txt; s=iport; t=1308975738; x=1310185338; h=date:subject:from:to:message-id:mime-version: content-transfer-encoding; bh=82cA36y9LR6WvSRN+qWz7RkgmRXUz6KqWc9zi1Bxk84=; b=KWUImL0J9IUhCdNPexnqXq8PhsgoPlcI/G9Rjnoi4fBK4Y0LutsVqh+t L2kH/kWEd2ZssdnkbFfLSeadtWYLXy9o7E32rQtEGqQ6ZDXKYIiMu7hGD fp9gf271+zUD+t60X6JcfJE0+fCw4cDVWUmPfwqzuMR5FryCsXEa1g5Dp E=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsEGANdhBU6tJXHB/2dsb2JhbABSp0JwB6s4gR2dZoYwBIcsilSEcYs/ X-IronPort-AV: E=Sophos;i="4.65,422,1304294400"; d="scan'208";a="238253700" Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rtp-iport-2.cisco.com with ESMTP; 25 Jun 2011 04:22:17 +0000 Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id p5P4MHe3026018 for ; Sat, 25 Jun 2011 04:22:17 GMT Received: from xmb-rcd-206.cisco.com ([72.163.62.213]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 24 Jun 2011 23:22:16 -0500 Received: from 10.21.95.169 ([10.21.95.169]) by XMB-RCD-206.cisco.com ([72.163.62.213]) via Exchange Front-End Server email.cisco.com ([128.107.191.32]) with Microsoft Exchange Server HTTP-DAV ; Sat, 25 Jun 2011 04:22:16 +0000 User-Agent: Microsoft-Entourage/12.30.0.110427 Date: Fri, 24 Jun 2011 23:24:14 -0500 From: Benson Schliesser To: "armd@ietf.org" Message-ID: Thread-Topic: Call for Agenda Items Thread-Index: Acwy77034xRVNJbDFUWevZBlcnLHgQ== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 25 Jun 2011 04:22:17.0083 (UTC) FILETIME=[77874CB0:01CC32EF] Subject: [armd] Call for Agenda Items 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jun 2011 04:22:20 -0000 The first-draft agenda for IETF 81 has been published and ARMD is currently assigned a slot on Friday, Morning Session I 0900-1130; please see https://datatracker.ietf.org/meeting/81/agenda.html for updates. If you would like time on the agenda, please send an email to the chairs (armd-chairs@tools.ietf.org) or the ARMD mailing list. Agenda requests must be received by 12-July-2011. Please note that the initial document (-00) cut-off is just over a week away, on 04-July-2011. All ARMD presentations are expected to have an active draft; exceptions to this rule will only be allowed in exceptional circumstances. -Benson & Linda From linda.dunbar@huawei.com Mon Jun 27 11:33:36 2011 Return-Path: X-Original-To: armd@ietfa.amsl.com Delivered-To: armd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A89C211E807B for ; Mon, 27 Jun 2011 11:33:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YL0R3svw3C29 for ; Mon, 27 Jun 2011 11:33:36 -0700 (PDT) Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by ietfa.amsl.com (Postfix) with ESMTP id 30D3F11E8142 for ; Mon, 27 Jun 2011 11:33:24 -0700 (PDT) Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNG00IRROVN32@usaga04-in.huawei.com> for armd@ietf.org; Mon, 27 Jun 2011 13:33:23 -0500 (CDT) Received: from dfweml202-edg.china.huawei.com ([172.18.4.104]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNG006POOVM6W@usaga04-in.huawei.com> for armd@ietf.org; Mon, 27 Jun 2011 13:33:23 -0500 (CDT) Received: from DFWEML401-HUB.china.huawei.com (10.193.5.101) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 27 Jun 2011 11:33:23 -0700 Received: from DFWEML503-MBX.china.huawei.com ([169.254.3.159]) by DFWEML401-HUB.china.huawei.com ([fe80::f07f:889f:78ef:8df3%13]) with mapi id 14.01.0270.001; Mon, 27 Jun 2011 11:33:22 -0700 Date: Mon, 27 Jun 2011 18:33:08 +0000 From: Linda Dunbar X-Originating-IP: [10.192.11.51] To: "armd@ietf.org" Message-id: <4A95BA014132FF49AE685FAB4B9F17F605164668@dfweml503-mbx.china.huawei.com> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-language: en-US Content-transfer-encoding: 7BIT Accept-Language: en-US Thread-topic: Please help the Nomcom Thread-index: AQHMMrCZOS7IWbIcT0OAhzI3kd8+oZTRi/jQ X-MS-Has-Attach: X-MS-TNEF-Correlator: Subject: [armd] FW: Please help the Nomcom 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2011 18:33:36 -0000 FYI -----Original Message----- From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf Of NomCom Chair Sent: Friday, June 24, 2011 1:35 PM To: Working Group Chairs Subject: Please help the Nomcom Hi WG chairs, We have had a good response to the first call for volunteers but the rate at which new volunteers are coming in is slowing down. The Nomcom process is best served by a large pool of volunteers drawn from a wide spectrum of IETF attendees. Where else would we find this wide spectrum if not in the WG mailing lists. I would really appreciate it if you can forward the message onto your working group mailing lists. The latest volunteer status and the second call for volunteers can be found at https://datatracker.ietf.org/ann/nomcom/2964/ Thanks in advance for your help. Suresh Krishnan Nomcom Chair 2011-2012 Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com