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