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

Timeframe IETF 74 (San Francisco)

NOTE: The BOF call for IETF74 is passed and all these BOFs proposed have been approved or not. The information below is now potentially out-of-date so don't expect to find the latest version of a charter below.

Applications

  • YAM: Advancing core mail standards
    • responsible AD: Lisa
    • Charter: YamCharter -- note 'contract' on minimal changes
    • Work items:
    • Chairs: Tony Hansen and John Klensin

General

  • IETF Rights in Contributions before RFC5378 BOF (PRE5378)
    • Status: Approved
    • Responsible AD: Russ Housley
    • Co-chairs: Ed Juskevicius and Scott Bradner
    • Charter: Not a WG forming BOF
    • Background: See IETF Discussion List from Oct 2008 to Feb 2009
    • Mailing List: ipr-wg@ietf.org (To Subscribe: ipr-wg-request@ietf.org)
    • BOF Goals:
      • Explore the scope and severity of the "pre-5378 content in new contributions" problem identified by Sam Hartman during Q&A at the IETF 73 Administrative Plenary in November 2008
      • Identify impacts on the community of not fixing the problem
      • Discuss proposed solutions for a permanent fix to the "pre-5378 problem" in: http://www.ietf.org/internet-drafts/draft-carpenter-5378-old-text-01.txt
      • Seek rough consensus on next steps and/or ways to move forward
    • BOF Agenda:

Internet

  • Multiple Interfaces BOF (MIF)
  • Experimental Lisp BOF (LISP)
    • Status: Approved; but also waiting for list discussion to determine whether (a) there is support for a WG, given changes after Dublin or if (b) more discussion is needed in a BOF. In Dublin we did not spend too much time in debating whether to create the WG and we were also also somewhat confused about what is being proposed, but the room at the time felt that this probably belongs more in the research space than in IETF. It was clear, however, that the community wanted a place to talk about this topic. Since Dublin what is new is that ... fill in here ...
    • Responsible AD: Jari Arkko
    • Charter: proposed charter in IETF review
    • AD's background summary: Jari's message
    • Agenda: agenda
    • Discussion: https://www.ietf.org/mailman/listinfo/lisp
    • Goal: Working group to publish experimental RFCs about the LISP protocol that helps with routing scalability and traffic engineering problems. Exact charter is currently under discussion.
    • Documents: rfc4984, base, alt, openlisp, interworking, dht, and multicast.

Operations and Management

RAI

Routing

Security

Transport