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

Timeframe IETF 83 (Paris)

Current schedule of "Important Dates" requires that all BOF proposal requests be submitted to Area Directors (ADs) by 17:00 PT Monday, February 13 (01:00 UTC Tuesday, February 14). The IAB and IESG will hold a joint teleconference to discuss the proposals. 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 Thursday, February 16.

Applications

Simple Cloud Identity Management (SCIM)

  • Description: A WG-forming BoF to gauge momentum and interest in working on protocols and other specifications for managing user identity in cloud based applications and services.
  • Responsible AD: Peter Saint-Andre
  • BoF Chair: Steve Bellovin and Eliot Lear
  • Number of people expected to attend: 75
  • Length of session: 90 minutes
  • Conflicts to avoid (whole Areas and/or WGs): oath, appsawg, websec, httpbis, hybi, pkix, kitten, tls
  • WebEX: No
  • Charter: Currently in discussion: http://www.ietf.org/mail-archive/web/scim/current/msg00003.html
  • I-Ds: none
  • Mail list: scim@ietf.org
  • Related URL: http://www.simplecloud.info/
  • Status: Approved

Worthwhile Extensible Internet Registration Data Service (WEIRDS)

General

Remote Participation System Requirements (RPSREQS)

  • Description: Non WG forming BoF to discuss experiences during the week
  • Responsible AD: Russ Housley
  • BoF Chair: Paul Hoffman
  • Number of people expected to attend: 50
  • Length of session: 2 hours
  • Schedule preference: Please put in last slot on Friday
  • Conflicts to avoid (whole Areas and/or WGs): None
  • WebEX: Not needed
  • I-Ds: draft-ietf-genarea-rps-reqs
  • Mail list: vmeet@ietf.org
  • Status: Approved

Does the IETF need an Anti-Trust Policy (Antitrust)

  • Description: Non WG forming BoF to discuss the way forward
  • Responsible AD: Russ Housley
  • BoF Chairs: Marshall Eubanks and John Levine
  • Number of people expected to attend: 50
  • Length of session: 2 hours
  • Schedule preference: Tuesday (but not right after lunch) or Wednesday
  • Conflicts to avoid (whole Areas and/or WGs): 6man
  • WebEX: Yes, WebEX is needed for this session
  • I-Ds: none
  • Mail list: antitrust-policy@ietf.org
  • Status: Approved

RFC Format (rfcform)

  • Description: Discussion on RFC formatting
  • Responsible AD: Russ Housley
  • BoF Chairs: Heather Flanagan
  • Number of people expected to attend:
  • Length of session: 1 hour
  • Conflicts to avoid (whole Areas and/or WGs):
  • WebEX:
  • I-Ds: none
  • Mail list: rfc-interest@rfc-editor.org
  • Status: Approved

Internet

ITS (Intelligent Transport Systems)

Operations and Management

RAI

SIP Session-ID (sessionid)

  • Description: Placeholder for WG whose formation will be considered before Paris
  • Responsible AD: Robert Sparks
  • BoF Chair: TBD
  • Number of people expected to attend: 50
  • Length of session: 1 hour
  • Schedule preference: treat as a WG for scheduling
  • Conflicts to avoid (whole Areas and/or WGs): RAI
  • WebEX: Not needed
  • Charter: Will be provided soon. Will likely be based on <http://www.ietf.org/mail-archive/web/dispatch/current/msg03647.html>
  • Mail list: dispatch@ietf.org (for now)
  • Status: Approved; may be WG before Paris

Routing

NVO3 - Overlay Networking

Description: This BOF proposal is for discussing potential IETF work related to providing overlay network services (e.g., L2 over L3).
Length of session: 120 minutes
Responsible AD: Stewart Bryant
Chairs: Matthew Bocci and Benson Schliesser
Main driver: Thomas Narten
Expected Attendees: 150
Conflicts to avoid: OPSAREA, RTGAREA, RTGWG, L2VPN, L3VPN, ARMD, TRILL, PWE3
Mailing list: https://www.ietf.org/mailman/listinfo/nvo3
Agenda: http://www.ietf.org/proceedings/83/agenda/agenda-83-nvo3.html
WebEx requested: No
Charter: http://www.ietf.org/mail-archive/web/nvo3/current/msg00148.html
Status: Approved;

Security

Security Automation and Continuous Monitoring - SACM (pronounced as Sack-em)

  • BOF Chairs: TBD
  • Description: A WG-forming BoF to gauge momentum and interest on protocol and other specification development related to security automation and continuously monitoring for security state and events.
  • Responsible AD: Sean Turner
  • Number of People Expected to Attend: 40
  • Length of Session: 1.5 hours
  • Conflicts to Avoid: saag, nea, opsarea, netconf, isms, pkix and mile
  • Does it require WebEx?: No - request MeetEcho? instead after the BOF is approved
  • Agenda: TBD
  • Drafts: IETF drafts are in development. Related NIST documents are publicly available at: http://scap.nist.gov/revision/1.2/index.html. This site includes links to core documents and associated mailing lists. Documents to be initially considered include:
    • XCCDF 1.2.1
    • Security automation core element specifications (CPE may be one of the first drafts for the BoF)
    • Connection between the MILE efforts and this work
    • A draft pertaining to developing Checking languages for integrating with XCCDF.
  • Mail list: scap_interest@ietf.org
  • Status: Not approved.

Transport

  • Name: Infrastructure-to-application information exposure (i2aex)
  • Description: A non-WG-forming BoF to investigate infrastructure- to-application information exposure and communications requirements in fully controlled (e.g., data centers) or partially controlled environments (e.g. CDN). ALTO was designed to provide network infrastructure information to applications that may not be under by the same administrative control as the network. ALTO only reveals limited information about the network infrastructure. By comparison, SNMP, IGP, BGP and other protocols that monitor and manage infrastructure may reveal much more information, but are typically only accessible to the operators of the network infrastructure. CDNs and data center applications have some requirements to operate over the Internet, possibly between administrative domains. ALTO was initially designed to address peer-to-peer application requirements, but was designed to be extensible. This BOF seeks input from the IETF community about whether ALTO (with possible extensions) or other protocols might be most appropriate to satisfy the information access requirements of CDN and Data Center applications. As this is not a WG-forming BOF, but is an input-gathering exercise, discussion of proposed work in this BOF should not lead to any expectation that any specific proposed work will be authorized.
  • Responsible AD: David Harrington (and Martin Stiemerling)
  • BoF Chairs: Spencer Dawkins and Vijay Gurbani
  • Expected attendance: 50-100
  • Length of session: 90 minutes
  • Conflicts to avoid: First priority: TSV WGs, OPS WGs, cuss, xmpp, appsawg Second priority: IRTF RGs, rtgwg, and possibly, since he's the APP advisor, Peter Saint-Andre's WGs (core, httpbis, bybi, iri, paws, umbis, vcarddav, websec)
  • WebEX: No
  • I-Ds: http://trac.tools.ietf.org/html/draft-marocco-alto-next

http://tools.ietf.org/html/draft-seedorf-i2aex-alto-cdni-perpective-00
http://trac.tools.ietf.org/html/draft-seedorf-alto-for-cdni-00
http://trac.tools.ietf.org/html/draft-jenkins-alto-cdn-use-cases-02
http://trac.tools.ietf.org/html/draft-penno-alto-cdn-03
http://trac.tools.ietf.org/html/draft-bernstein-alto-large-bandwidth-cases-00
http://trac.tools.ietf.org/html/draft-dulinski-alto-inter-problem-statement-01
http://trac.tools.ietf.org/html/draft-medved-alto-svr-apis-00
http://trac.tools.ietf.org/html/draft-sun-alto-notification-02