* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Timeframe IETF 79 (Beijing)

Current schedule of "Important Dates" requires that all BOF proposal requests be submitted to Area Directors (ADs) by 17:00 PST (01:00 UTC/GMT) on Monday, 13 Sept. 2010. The IAB and IESG will hold a joint teleconference to discuss the proposals on <TBD>. ADs will be expected to approve or disapprove the BOF request on that teleconferece, ensuring that the Secretariat has all of the information to put the first draft of the agenda together on or before Wednesday, 6 Oct. 2010.

Applications

WEBSEC - Web Security

BOF Chairs: Tobias Gondrom
Number of people: 50-80
Length of session: 2
Conflicts to avoid: AppArea?, HTTPBIS, HTTPSTATE, HYBI, OAUTH, SAAG, TLS
Does it require WebEX? No
Responsible AD: Peter Saint-Andre
Goal: WG formation is currently in IESG review based on HASMAT BoF at IETF 78; this BoF request is merely a placeholder pending IESG approval of the WG
Agenda and drafts: [to follow]
Mailing list: http://www.ietf.org/mail-archive/web/hasmat/current/maillist.html
Status: Approved as BOF, WG formation is pending

General

IDDTSPEC - Review of Datatracker Specifications to Follow Internet-Draft Activities

BOF Chairs: Paul Hoffman
Number of people: 75
Length of session: 2 1/2 hours
Conflicts to avoid: apparea, intarea, tsvarea, rtgarea, opsarea, saag
Does it require WebEX? No
Responsible AD: Russ Housley
Goal: Review specifications for Datatracker enhancements that allow IETF Participants to easily follow the activities associated with particular Internet-Drafts.
Agenda and drafts: TBD
Mailing list: ietf@ietf.org
Status: Approved

Internet

DMM - Distributed Mobility Management

BOF Chairs: TBD (Organizer: Dapeng Liu)
Number of people: 100
Length of session: 2
Conflicts to avoid: MEXT, NETEXT, MULTIMOB, INTAREA
Does it require WebEX? No
Responsible AD: Jari Arkko
Goal: description
Agenda and drafts: agenda draft-liu-distributed-mobility
Mailing list: http://www.ietf.org/mail-archive/web/dmm/current/maillist.html
Status: Not approved as BoF, but will be discussed in the MEXT WG

ARMD - Address Resolution for Massive amount of hosts in cloud/internet Data center

BOF Chairs: TBD (Organizer: Linda Dunbar)
Number of people: 60
Length of session: 2
Conflicts to avoid: INTAREA, LEDBAT, TRILL, DHC, L2VPN, L3VPN, IDR
Does it require WebEX? No
Responsible AD: Ralph Droms
Goal:

As server virtualization is introduced to data centers, the number of hosts in a data center can grow dramatically. Each physical server, which used to host one end-station, now can host hundreds of end-stations or virtual machines (VMs). Virtual machines (VMs) can be easily added and/or deleted and moved among physical servers. The VM’s flexible addition, deletion, and (or) migration make it possible to combine pool of servers into one huge single resource entity for ease of management and better resource utilization. It also provides foundation for virtual hosts and virtual desktops offered by Cloud Computing services.
This rapid growth of virtual hosts could tremendously impact networks and servers. One major issue is frequent ARP (IPv4) or neighbor discovery (IPv6) requests from hosts.
The goal of this working group is to develop interoperable solutions to solve the above problems within the Data Center and multi-site Data Center environments. This could involve multi-domain (multi-company), multi-site and multi-vendor environments.

See attached proposed charter , for more details

Agenda and drafts:

  1. Blue sheets, scribe, agenda bashing
    Chairs (5 min)
  2. Problem statement
    https://datatracker.ietf.org/doc/draft-dunbar-armd-problem-statement
    Linda Dunbar (30 minutes)
  3. Problem scope (and non-scope)
    TBD (30 minutes)
  4. Existing and potential solutions
    TBD (30 minutes)
  5. Open discussion
    (15 minutes)
  6. Next steps
    ADs (10 minutes)

    Mailing list: https://www.ietf.org/mailman/listinfo/armd
    Status: Approved

LWIP - Light-Weight IP Protocol Design

BOF Chairs: TBD (Organizer: Zhen Cao)
Number of people: 50-80
Length of session: 2
Conflicts to avoid: 6LOWPAN, ROLL, CORE, HIPRG, IPSECME, INTAREA
Does it require WebEX? No
Responsible AD: Jari Arkko
Goal: description
Agenda and drafts: agenda

draft-deng-lwip-ps draft-chen-lwip-implementation
draft-ma-lwip-stack-analysis
draft-chen-lwip-rd-mg
draft-moskowitz-hip-rg-dex

Mailing list: http://www.ietf.org/mail-archive/web/lwip/current/maillist.html
Status: Approved

Operations and Management

Network Stratum Query (NSQuery)

BOF Chairs: Sue Hares, Young Lee
Number of people: 75
Length of session: 2 hours
Conflicts to avoid: apparea, intarea, tsvarea, opsarea
Does it require WebEX? No
Responsible AD: Ron Bonica
Goal:

Data Centers offer application services to end-users such as video gaming, cloud computing and others. As the application servers are distributed geographically in many Data Centers for various reasons, the decision as where to instantiate services needs to be optimized across end-user experience and data center economy.

User experience is impacted by Intra Data Center factors such as server load conditions, and connectivity within Data Center as well as the underlying network behavior (such as congestion, jitter, latency and loss) between end-user and the hosting Data Center and between Data Centers.

The Working Group will design and specify a communication protocol and associated mechanisms that will allow the application to do a whole network query of information at the network-stratum so that synchronized monitoring would be enabled across application and network.

The network stratum is described as non-application resources (as shown in diagram 1) that includes transport to physical layer. The scope is across many boxes in multiple domains (physical, link, network, and transport domains). Application stratum includes multiple applications at the application layer across multiple domains.

Application protocols will use this network protocol mechanism to manage the network.

Agenda and drafts: TBD
Mailing list: cso@ietf.org
Draft charter: http://trac.tools.ietf.org/bof/trac/attachment/wiki/TracGuide/NS_query_Charter.txt
Status: Withdrawn

Nameserver Control Protocol (nscp)

BOF Chair(s): Jelte Jansen
Responsible AD: Ron Bonica
Number of people: 30-50
Length of session: 1.5 hours
Conflicts to avoid: dnsop, dnsext
WebEX: no
Goal: draft charter
Mailinglist: (to be created) nscp@ietf.org
Drafts: draft-ietf-dnsop-name-server-management-reqs draft-dickinson-dnsop-nameserver-control
Status: Withdrawn

RAI

Routing

Security

KIDNS - cryptographically secured communication by using information in DNS (former name KEYASSURE)

BoF Chairs: Ondřej Surý, Warren Kumari
People expected: 30-50
Length of session: 1 - 1.5 hours
Conflicts to avoid: dnsext,dnsop,opsec,tls,pkix,saag. Please not on Friday (BOF chair unavailable).
WebEX: No
Proposed charter draft: http://trac.tools.ietf.org/area/sec/trac/wiki/Keyassure
Responsible AD: Tim Polk'
Goal: Charter a WG
Agenda: TBD
Drafts: http://tools.ietf.org/html/draft-hoffman-keys-linkage-from-dns and http://tools.ietf.org/html/draft-josefsson-keyassure-tls (more will probably follow)
Draft Charter: http://trac.tools.ietf.org/area/sec/trac/wiki/Keyassure
Mailing List: keyassure@ietf.org
Mailing List Archive: http://www.ietf.org/mail-archive/web/keyassure/
Status: Approved.

SCAP - Synergy of SCAP Program and IETF Activities

BOF Chairs: Steve Hanna, Kent Landfield
Number of people: 75
Length of session: 2 hours
Conflicts to avoid: SAAG, NEA, OPSAREA, NETCONF, ISMS
Does it require WebEX? No
Responsible AD: Sean Turner
Goal:

Introduce the IETF community to the Security Content Automation Protocol (SCAP), discuss areas of synergy and overlap with IETF activities, and consider whether this technology is sufficiently mature for standardization. Finally, explore whether the IETF would be an appropriate venue for such standardization when ready.

Agenda: TBD
Drafts:

IETF drafts in development. NIST and Mitre specifications are publicly available now.
Base website is http://scap.nist.gov/revision/1.0/index.html which includes links to core documents and associated mailing lists. Specific documents include

  • The Technical Specification for the Security Content Automation Protocol (SCAP): SCAP Version 1.0
  • Specification for the Extensible Configuration Checklist Description Format (XCCDF) Version 1.1.4
  • Open Vulnerability and Assessment Language Version 5.3
  • Common Platform Enumeration (CPE)
  • Common Vulnerabilities and Exposures (CVE)
  • The Common Vulnerability Scoring System (CVSS)

Mailing list: scap_interest@ietf.org
To join mailing list: https://www.ietf.org/mailman/listinfo/scap_interest
Mailing List Archive: http://www.ietf.org/mail-archive/web/scap_interest/
Status: Approved

Transport

HOMENET - Home Networking

Description:

The broad purpose of the home networking (HOMENET) working group is to describe the home network IP architecture and to work on clarifications and improvements to IETF protocols to allow the home network to better meet present and anticipated future requirements. The HOMENET working group will deliver recommendations related to the use of IETF-specified technologies such as TCP, IPv6, DNS, and IP routing protocols and will not overlap with specifications related to system-level or link-layer technologies developed by other standards bodies.

BoF Chairs: BOF Proponents: Ray Bellis (ray.bellis@nominet.org.uk), Mark Townsley (townsley@cisco.com)
People expected: 120
Length of session: 1.5 hours
Conflicts to avoid: LEDBAT, DECADE, ALTO, SPEERMINT, 6LOWPAN, TSVWG, INTAREA, DNSEXT, DNSOPS, SOFTWIRE, 6MAN, V6OPS, PCN, BEHAVE, ROLL, CORE
WebEX: Yes
Responsible AD: David Harrington'
Goal: Charter a WG
Agenda: http://trac.tools.ietf.org/area/tsv/trac/wiki/HOMEGATE
Drafts:
Draft Charter: http://trac.tools.ietf.org/area/tsv/trac/wiki/HOMEGATE
Mailing List: homegate@ietf.org
Mailing List Archive: http://www.ietf.org/mail-archive/web/homegate/
Status: Approved

NBS - Name-Based Sockets

BOF Chairs: TBD (Organizer: Javier Ubillos)
Number of people: 100
Length of session: 2
Conflicts to avoid: MPTCP, MEXT, RRG, INTAREA, TSVAREA, TSVWG, APPAREA
Does it require WebEX? No
Responsible AD: David Harrington
Agenda: http://www.sics.se/nbs/bof/agenda.txt
Potential charter: description
Drafts:

*http://www.ietf.org/id/draft-ubillos-name-based-sockets-03.txt
*http://www.ietf.org/id/draft-xu-name-shim6-00.txt

Mailing list: https://www.ietf.org/mailman/listinfo/nbs
Status: Approved