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


HyBi -- bidirectional or server-initiated HTTP
Status: Approved
Chairs of BOF: Joe Hildebrand and Salvatore Loreto
Agenda: In progress
Draft Charter: http://www.ietf.org/mail-archive/web/hybi/current/msg00567.html
Drafts: http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol-40, http://tools.ietf.org/html/draft-lentczner-rhttp-00, http://bwtp.wikidot.com/main:proposal1, http://www.ietf.org/id/draft-loreto-http-bidirectional-00.txt
Mailing List: hybi@ietf.org
Responsible AD: Lisa Dusseault

Status: Approved
Goal: Update IRI definition with focus from multiple communities may require a WG to agree on common direction.
Agenda: IRI BOF Agenda
Draft Charter: IRI Bof Charter
Chairs: Ted Hardie and Pete Resnick
Drafts: http://tools.ietf.org/html/draft-duerst-iri-bis, http://tools.ietf.org/html/draft-duerst-mailto-bis
Mailing list: public-iri@w3.org
Responsible AD: Alexey Melnikov

GROBJ - Generic Referral Object
Status: Approved
The purpose of a referral is to enable a given entity in a multiparty application to pass information to another party. This BOF will consider a proposed Generic Referral Object (GRO) to be used for referrals.
Agenda: http://www.ietf.org/proceedings/09nov/agenda/grobj.txt
Chairs: Sheng Jiang, Dan Wing
Draft: http://tools.ietf.org/html/draft-carpenter-behave-referral-object
Mailing list: grobj@ietf.org
Subscribe: https://www.ietf.org/mailman/listinfo/grobj
Responsible AD: Alexey Melnikov
Note - Not a WG forming BOF at this time. Might not end up in Apps area.

DECADE - DECoupled Application Data Enroute
Status: Approved
Agenda: http://trac.tools.ietf.org/area/app/trac/wiki/DecadeAgenda
Initial Charter proposal: http://www.ietf.org/mail-archive/web/decade/current/msg00069.html
Chairs: Song Haibin and Richard Woundy
Drafts: http://www.ietf.org/internet-drafts/draft-song-decade-problem-statement-00.txt

Mailing list: decade@ietf.org
Responsible AD: Alexey Melnikov

Status: Approved. Draft charter in progress. See http://trac.tools.ietf.org/area/app/trac/wiki/6LowApp.
Agenda: http://www.ietf.org/mail-archive/web/6lowapp/current/msg00006.html
Initial Charter proposal: http://www.ietf.org/mail-archive/web/6lowapp/current/msg00015.html
BOF Chairs: Carsten Bormann and Cullen Jennings
Drafts: See http://trac.tools.ietf.org/area/app/trac/wiki/6LowApp
Mailing list: 6lowapp@ietf.org
Responsible AD: Lisa Dusseault / Dan Romascanu

Http-State: state management for HTTP
Status: Rejected for Hiroshima, the plan is to proceed to WG without a BOF.
Announcement: http://groups.google.com/group/http-state/browse_thread/thread/c9468d848a05a28e?pli=1 NOTE: see thread including followup; very little interest in meeting attendance though there is active list participation.
Agenda: TBD
Chair: TBD (possibly Jeff Hodges)
Drafts: http://groups.google.com/group/http-state/browse_thread/thread/d516974910167d4e#anchor_ff790c599a8b8e42
Mailing list: http-state@ietf.org
Responsible AD: Lisa Dusseault
Documents: Several documents are listed in the draft charter.

ARF - Abuse Report Format
Status: Decided to try to go straight to WG chartering without a BOF
Messaging anti-abuse operations between independent services often requires sending reports on observed fraud, spam virus or other abuse activity. A standardized report format enables automated processing. The purpose of this BOF is to talk about forming a WG for standardizing Abuse Reporting Format (ARF) and some extensions.
Initial Charter proposal: http://www.ietf.org/mail-archive/web/apps-discuss/current/msg00833.html
Agenda: TBD
Drafts: http://tools.ietf.org/html/draft-shafranovich-feedback-report-07
Mailing list: abuse-feedback-report at mipassoc.org
Subscribe: http://mipassoc.org/mailman/listinfo/abuse-feedback-report
For more information: http://www.mipassoc.org/arf/
Responsible AD: Alexey Melnikov



NAT66 -- IPv6 NATs
Status: a 2nd BOF proposal is being worked on
Agenda: TBD
Drafts: http://tools.ietf.org/html/draft-mrw-behave-nat66-02.txt
Mailing List: https://www.ietf.org/mailman/listinfo/nat66
Responsible AD: Ralph Droms

APLUSP -- IPv4 Address/port addressing
Status: approved
Chairs: Christian Jacquenet, Dan Wing
Agenda: http://www.ietf.org/proceedings/09nov/agenda/aplusp.html

Draft charter: http://trac.tools.ietf.org/bof/trac/attachment/wiki/BifIETF76/aplusp-charter.txt
Mailing list: shara@ietf.org (for BOF discussion and planning)
Responsible AD: Ralph Droms

Operations and Management


Status: Approved, meeting on Thursday, November 12, at 13:00
Description: At IETF 75, the IETF held a BoF about the possibility of forming a working group to develop one or more audio codecs that would be optimized for use in Internet applications and that could be widely implemented and easily distributed among application developers, service operators, and end users. The BoF at IETF 75 was inconclusive regarding the matter of forming a working group. Since then, the two main open issues have been addressed through publication and discussion of Internet-Drafts about the proposed work processes and technical requirements of a Codec WG (see links below). In addition, the IETF and ITU-T have held discussions pursuant to the liaison agreement in place regarding cooperation and coordination of activities related to media codecs. The BoF at IETF 76 will build on this work in an attempt to reach consensus about whether to charter a working group.
Summary of previous BoF: http://www.ietf.org/mail-archive/web/codec/current/msg00540.html
Proposed charter: http://trac.tools.ietf.org/bof/trac/attachment/wiki/BifIETF76/codec-charter.txt
Chairs: Eric Burger and Peter Saint-Andre
Proposed work process: draft-valin-codec-guidelines-02
Proposed requirements: draft-valin-codec-requirements-02
Submitted codecs: draft-spiritdsp-ipmr-00, draft-valin-celt-codec-01, draft-vos-silk-00
Other related drafts: draft-hoene-avt-acs-requirements-00
Mailing list: https://www.ietf.org/mailman/listinfo/codec
Responsible AD: Cullen Jennings
IAB Shepherd: Gregory Lebovitz


KARP - Keying and Authentication for Routing Protocols
Status: received
Many routing protocol deployments if they use authentication at all are using are using older (possibly deprecated) cryptographic algorithms and missing some modern security mechanisms, like replay protection, algorithm agility, or key rollover. In addition, many use the same key permanently. This needs to be fixed.
Additionally, key management for routing protocols need to be added to easily address the terminated-employee problem of compromised shared secrets. Such key management needs to work over multicast media, and needs to work directly over the link layer in some cases (since routing depends upon it).
Agenda: tbd
Charter: Draft sent to KARP email list (http://www.ietf.org/mail-archive/web/karp/current/msg00045.html).

Mailing list: karp@ietf.org
Responsible AD: Adrian Farrel or Ross Callon
Note - WG forming BOF.



Negotiation BOF
Status: denied this time
URL: http://www.ietf.org/mail-archive/web/tae/current/msg00109.html
Agenda: TBD
Drafts: TBD
Mailing list: https://www1.ietf.org/mailman/listinfo/tae
Responsible AD: Lars Eggert

Homegate - Broadband Home Gateway
Status: Approved
URL: http://trac.tools.ietf.org/bof/trac/raw-attachment/wiki/WikiStart/HomeGate%20BoF%20Proposal%20-%20IETF%2076%20-%20v3.pdf
Agenda: see URL
Drafts: TBD
Mailing list: https://www1.ietf.org/mailman/listinfo/homegate
Responsible AD: Lars Eggert

Re-ECN - Congestion Exposure
Status: Approved as ConEx?
Congestion Exposure (ConEx??) is a proposed new IETF activity to enable congestion to be exposed along the forwarding path of the Internet. By revealing expected congestion in the IP header of every packet, congestion exposure provides a generic network capability which allows greater freedom over how capacity is shared. Such information could be used for many purposes, including congestion policing, accountability and inter-domain SLAs. It may also open new approaches to QoS and traffic engineering. URL: http://trac.tools.ietf.org/area/tsv/trac/wiki/re-ECN
Agenda: TBD
Drafts: TBD
Mailing list: https://www1.ietf.org/mailman/listinfo/re-ecn
Responsible AD: Lars Eggert / Jari Arkko

PPSP (Peer to Peer Streaming Protocol)
Status: Approved
URL: http://trac.tools.ietf.org/area/tsv/trac/wiki/PPSP
Agenda: Draft: http://trac.tools.ietf.org/area/tsv/trac/wiki/PPSP
Drafts: draft-zhang-ppsp-problem-statement


Mailing list: https://www.ietf.org/mailman/listinfo/ppsp
Responsible AD: Lars Eggert / Magnus Westerlund