Re: [dc] Work items for this group

"Luyuan Fang (lufang)" <lufang@cisco.com> Fri, 16 December 2011 19:43 UTC

Return-Path: <lufang@cisco.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 5E8E611E8093 for <dc@ietfa.amsl.com>; Fri, 16 Dec 2011 11:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level:
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4]
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 2lk4prEh1yk8 for <dc@ietfa.amsl.com>; Fri, 16 Dec 2011 11:43:13 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 614DB11E8089 for <dc@ietf.org>; Fri, 16 Dec 2011 11:43:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lufang@cisco.com; l=4846; q=dns/txt; s=iport; t=1324064593; x=1325274193; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=1JwrFblvHYl0xTqkqPL6CoVqz4KHKzEcyA2pJ7Tu2pM=; b=llzIBUbKxUbNgIN40RaFQqTsH5kltw4fYqiVDdvJu0pTr2L4SFTg/l27 7XY0ZLFg2EhzkUfHHu2TiR4iwq/rnLL85lMp3CAQIzHfO5T5vIsxnw82w uB/nBW7mryb1cWaP5lmhfU0y1UwCCNjI/6aW48w6FTRh842gStn5bM6aJ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoUAAHue606tJXHB/2dsb2JhbABEmwmQS4EFgXIBAQEDAQEBAQ8BHQo0EAcEAgEIEQEDAQELBhcBBgEmHwMGCAIEARIIEweHWAiZVAGeNYshYwSINJ8N
X-IronPort-AV: E=Sophos;i="4.71,364,1320624000"; d="scan'208";a="44670169"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-2.cisco.com with ESMTP; 16 Dec 2011 19:43:13 +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 pBGJhCL9018966; Fri, 16 Dec 2011 19:43:12 GMT
Received: from xmb-rcd-201.cisco.com ([72.163.62.208]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 16 Dec 2011 13:43:12 -0600
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: Fri, 16 Dec 2011 13:43:10 -0600
Message-ID: <238542D917511A45B6B8AA806E875E2507850D69@XMB-RCD-201.cisco.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F61A67AA4F@dfweml505-mbx>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dc] Work items for this group
Thread-Index: AQHMu/T73M2yuZR6J06DZ8EmnClWQZXey4uwgAAJxuA=
References: <201112161315.pBGDFP9X009939@cichlid.raleigh.ibm.com> <4A95BA014132FF49AE685FAB4B9F17F61A67AA4F@dfweml505-mbx>
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, Thomas Narten <narten@us.ibm.com>, dc@ietf.org
X-OriginalArrivalTime: 16 Dec 2011 19:43:12.0634 (UTC) FILETIME=[F247C5A0:01CCBC2A]
Subject: Re: [dc] Work items for this group
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: Fri, 16 Dec 2011 19:43:14 -0000

This takes us back to the dc list scope discussion.

Regarding ARMD, I thought Benson commended before: "if one wishes to
discuss ARMD issues, I suggest using the armd@ietf.org mailing list. But
there is much that is out of ARMD's scope, which might be more
appropriate for discussion on dc@ietf.org instead."

Are you suggesting a different approach? Or these new ARMD drafts are
out of scope of ARMD?
Same goes with the TRILL drafts...

If the scope of the dc list is to cover every topic in ietf related to
dc, regardless there is already WG or not, we have several more WGs to
pull in, I think we will have scale and focus issues.

Luyuan

> -----Original Message-----
> From: dc-bounces@ietf.org [mailto:dc-bounces@ietf.org] On Behalf Of
> Linda Dunbar
> Sent: Friday, December 16, 2011 2:01 PM
> To: Thomas Narten; dc@ietf.org
> Subject: Re: [dc] Work items for this group
> 
> Thomas,
> 
> Thanks for starting the list.
> There are several drafts in ARMD for Data Center. The first two drafts
> have been discussed at the 82nd IETF meeting in Taipei, therefore
might
> not need to be discussed again at the DC Interim meeting. But they are
> very good documents in describing Data Center general architecture and
> address resolution issues in data centers, which people on this mail
> list should be interested in.
> 
> http://datatracker.ietf.org/doc/draft-ietf-armd-problem-statement/
> http://datatracker.ietf.org/doc/draft-karir-armd-datacenter-reference-
> arch/
> http://datatracker.ietf.org/doc/draft-karir-armd-statistics/
> 
> This draft hasn't been discussed yet due to scope issues.  Therefore,
> they are suited for DC Interim meeting.
> http://datatracker.ietf.org/doc/draft-shah-armd-arp-reduction/
> 
> Here is another draft in ARMD, which is interesting.
> http://datatracker.ietf.org/doc/draft-so-armd-vdcs-ar/
> 
> 
> 
> Here are a couple of drafts in TRILL targeted for the data center
> environment:
> 
> http://datatracker.ietf.org/doc/draft-dunbar-trill-directory-assisted-
> edge/
> 
> http://datatracker.ietf.org/doc/draft-dunbar-trill-directory-assisted-
> encap/
> 
> There will be an ARMD draft on BCP for ARP/ND Scaling for Large Data
> Centers to be uploaded soon, which are relevant.
> 
> Linda Dunbar
> 
> > -----Original Message-----
> > From: dc-bounces@ietf.org [mailto:dc-bounces@ietf.org] On Behalf Of
> > Thomas Narten
> > Sent: Friday, December 16, 2011 7:15 AM
> > To: dc@ietf.org
> > Subject: [dc] Work items for this group
> >
> > Joel jaeggli <joelja@bogus.com> writes:
> >
> > > So far it's been an impressively low traffic list for a cross area
> > > intersection of interests gearing up to discuss documents at an
> > interim.
> >
> > Fair point.
> >
> > And with that, I'd like to start with a summary of the potential
work
> > items that might be covered here. By "work items", I'd like to see a
> > grouping of IDs/presentations into (potential) work areas. The goal
> > would be to talk about each work area somewhat separately. If we
> > aren't able to organize work into mostly self-contained areas (i.e.,
> > WGs), we'll never get anywhere.
> >
> > So far, the ones I know of include:
> >
> > NVO3
> >     draft-narten-nvo3-overlay-problem-statement-01.txt
> > SDN
> >     draft-nadeau-sdn-problem-statement-01.txt
> >
> >   Use Case/Examples:
> >     draft-stiliadis-sdnp-framework-use-cases-01.txt
> >     draft-pan-sdn-bod-problem-statement-and-use-case-01.txt
> >     draft-pan-sdn-dc-problem-statement-and-use-cases-01.txt
> >     draft-mcdysan-sdnp-cloudbursting-usecase-00.txt
> >
> >   Solutions/Approachs:
> >     draft-nadeau-sdn-framework-01.txt
> >     draft-marques-sdnp-flow-spec-00.txt
> > VPN4DC
> >
http://tools.ietf.org/html/draft-fang-vpn4dc-problem-statement-00
> >
> >     http://tools.ietf.org/html/draft-bitar-datacenter-vpn-
> > applicability-01
> >     http://tools.ietf.org/html/draft-so-vpn4dc-00
> >     http://datatracker.ietf.org/doc/draft-so-vdcs-01
> >
http://tools.ietf.org/html/draft-dunbar-vpn4dc-problem-statement-
> 00
> >     http://tools.ietf.org/html/draft-ko-dsi-problem-statement-00
> >
http://tools.ietf.org/html/draft-jin-l3vpn-vpn4dc-interconnect-00
> >     http://tools.ietf.org/html/draft-yong-vpn4dc-protocol-gap-
> analysis-
> > 00
> >     http://tools.ietf.org/html/draft-zeng-vpn4dc-example-solution-00
> >     http://tools.ietf.org/html/draft-marques-l3vpn-end-system-02
> >
> > Are there others?
> >
> > Thomas
> >
> > _______________________________________________
> > dc mailing list
> > dc@ietf.org
> > https://www.ietf.org/mailman/listinfo/dc
> _______________________________________________
> dc mailing list
> dc@ietf.org
> https://www.ietf.org/mailman/listinfo/dc