[Chapter-delegates] Internet Society's Rough Guide to IETF 87's Hot Topics

Fri Jul 26 01:53:48 PDT 2013

Hello,

Please find below the Internet Society's Rough Guide to IETF 87. It is also available at:

http://www.internetsociety.org/rough-guide-ietf87

Best regards,

-Greg

-----------------------------------------------
Internet Society's Rough Guide to IETF 87's Hot Topics 
-----------------------------------------------

IETF 87 in Berlin is rapidly approaching (28 July - 2 August 2013). Newcomers' training and technical tutorials take place on Sunday (28 July), with the working group (WG), Birds of a Feather (BoF), and plenary sessions happening during the week.

Once again, the Internet Society is pleased to bring you a Rough Guide to the IETF 87 sessions most relevant to our current work. The online version of this Rough Guide will be updated as the IETF 87 session agendas are finalized:

http://www.internetsociety.org/rough-guide-ietf87

At this IETF meeting, we are focusing our attention to the following broad categories:

- Trust technologies
- Authentication/Authorization
- Infrastructure/Support
- IPv6
- Bandwidth

(All times are local: CEST, UTC +1 hour.)

In addition to the WG and BoF sessions listed below, these sessions are of general interest:

+ Plenary Technical Topic

OPUS Codec

The OPUS codec, defined in RFC 6716, was developed within the IETF to provide an open, royalty-free, and extremely versatile wideband audio codec suitable for a wide range of audio applications, including voice-over-IP (VoIP), videoconferencing, in-game chat, and live music or speech performances. The Opus codec can scale from low bit-rate narrowband speech to very high-quality stereo music and adapt to a wide range of bandwidth conditions.  This technical plenary session covers the past and future of Opus as well as the lessons learned that could apply to future IETF work. Panelists will also discuss future work and the state of current Opus deployment within VoIP, WebRTC, and other environments.  

As an example of the IETF's commitment to "running code", an experimental mechanism will be available for remote attendees where they will be able to use any WebRTC-capable web browser, such as the latest versions of Google Chrome or Mozilla Firefox, to listen to the plenary using the actual Opus codec.

Agenda: http://trac.tools.ietf.org/group/iab/trac/wiki/IETF-87
Remote participation:  http://www.meetecho.com/ietf87/tech_plenary
Opus specification: http://tools.ietf.org/html/rfc6716
Opus information: http://www.opus-codec.org/

(29 July 2013, 1740-1940)

--------------

+ ISOC at IETF 87 Briefing Panel: Improving Internet Experience: All together, now.

As Internet use and user expectations grow, it is natural that network and service providers, as well as software developers, are all looking to provide the best experience possible for their users and customers. However, performance issues (especially those related to transient congestion) tend to have collateral effects. In fact, server or client software developers' assumptions about network conditions may lead to disastrously wrong choices in managing network traffic if software elsewhere in the network is making different and countervailing assumptions and choices.

This panel will explore some of the different approaches being developed, between website, network transport and server developers, their assumptions about network performance and potential collision of strategies. Panelists will also further elaborate existing work in measuring and developing (and deploying!) standards-based transport layer strategies for robustly improving overall performance.

More information on the briefing panel is posted at:

http://www.internetsociety.org/internet-society-briefing-panel-ietf-87

(30 July 2013, 1145-1245)

--------------

irtfopen (IRTF Open Meeting)

The IRTF Open Meeting will feature talks from the latest Applied Networking Research Prize winners for 2013. Te-Yuan Huang was awarded for insights into the difficulties of rate adaptation for streaming video. (Te-Yuan Huang, Nikhil Handigol, Brandon Heller, Nick McKeown and Ramesh Johari. Confused, Timid, and Unstable: Picking a Video Streaming Rate is Hard. Proc. ACM Internet Measurement Conference (IMC), November 2012, Boston, MA, USA). Laurent Vanbever was awarded for proposing a framework to allow seamless BGP reconfigurations (Stefano Vissicchio, Laurent Vanbever, Cristel Pelsser, Luca Cittadini, Pierre Francois and Olivier Bonaventure. Improving Network Agility with Seamless BGP Reconﬁgurations. Proc. IEEE/ACM Transactions on Networking (TON), To Appear).

The ANRP call for nominations is now open: Submit nominations for the 2014 award period of the Applied Networking Research Prize until 30 November 30 at: 
http://irtf.org/anrp/2014/

Agenda: https://datatracker.ietf.org/meeting/87/agenda/irtfopen/
Charter: http://irtf.org/
(30 July 2013, 0900-1130)

--------------

IETF Journal

The IETF Journal v9.1 provides a summary of many sessions from IETF 86, as well as in depth articles on developments related to the work of the IETF:

http://www.internetsociety.org/publications/ietf-journal-july-2013

Learn about developments around IETF by subscribing to the IETF Journal at:

https://www.internetsociety.org/ietfjournal-subscribe

_____________________________________
Trust technologies
Trust technologies are those that enable trust in the Internet infrastructure and user or application space. This includes encryption technologies and mechanisms for communicating trust in various forms.
_____________________________________

jose (Javascript Object Signing and Encryption) WG

The jose WG was originally chartered to develop two security services, integrity protection and encryption, for data being carried in the JSON format. After the March 2013 IETF meeting, the charter was expanded to include serialization, key representation, and use cases. The use case document (http://tools.ietf.org/html/draft-ietf-jose-use-cases-03) has completed working group last call (WGLC) and will be submitted to the IESG shortly for review and approval. The four core specification documents, including JSON Web Algorithms (JWA), JSON Web Encryption (JWE), JSON Web Key (JWK), and JSON Web Signature (JWS), have made substantial progress since the last IETF in Orlando. An interim face to face meeting and a series of conference calls held since that IETF have been focused at closing open issues as documented in the issue tracker (http://trac.tools.ietf.org/wg/jose/trac/report/1). The upcoming IETF meeting will focus on closing the remaining open issues and preparing the set of specifications for WGLC. 

Agenda: http://tools.ietf.org/wg/jose/agenda?item=agenda-87-jose.html
Charter: http://tools.ietf.org/wg/jose/charters
(30 July 2013, 1300-1500)

--------------

json (Javascript Object Notation) WG

Javascript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard and was published in RFC 4627, as an Informational RFC. Since then, JSON has come into very broad use. A JSON working group has been chartered since the last IETF that would work to bring JSON onto the Standards Track while addressing errors and inconsistencies in the current documentation. Any additional proposals for changes and more significant revisions of JSON are being collected but will not be part of this update. There is a current draft and extensive discussion on the mailing list (http://trac.tools.ietf.org/html/draft-ietf-json-rfc4627bis-02).

Agenda: http://tools.ietf.org/wg/json/agenda
Charter: http://tools.ietf.org/wg/json/charters
(1 August 2013, 0900-1020)

--------------

dmarc (Domain-based Message Authentication, Reporting & Conformance) BoF

Email abuse often relies on unauthorized use of a domain name, such as one belonging to a well-known company (or its "brand"). SPF (RFC4408) and DKIM (RFC6376) provide basic domain name authentication methods for email. A recent industry effort has added a trust-oriented layer, called Domain-based Message Authentication, Reporting & Conformance (dmarc.org). It allows a sender to indicate that their emails are protected by SPF and/or DKIM, and tells a receiver what to do if neither of those authentication methods passes; it also provides a reporting mechanism, from receivers back to domain owners.

The existing base specification has been developed by a non-IETF group dmarc.org and is already being deployed. The BoF is intended to discuss the scope of work to be done regarding the base specification as well as future enhancements. Based on that a decision whether to form a a WG will be made.

Agenda: http://tools.ietf.org/agenda/87/agenda-87-dmarc.html
Charter: N/A
(30 July 2013, 1520-1650)

--------------

dane (DNS-based Authentication of Named Entities) WG

The dane working group was chartered to look at the use of DNSSEC to facilitate the establishment of cryptographically secure communications for Internet applications. This was accomplished by using information distributed through DNSSEC for discovering and authenticating public keys associating a service located at a domain name. Building upon the implementation and deployment of DNSSEC, this work seeks to use the chain of trust established in the DNS to enable on-demand establishment of secure channels for a multiplicity of applications. The dane working group has successfully completed the use case document (published as RFC 6394) and the protocol document (published as RFC 6698). The working group is focusing on the use of DANE. Documents under discussion include implementation and operational guidance, harmonizing how applications specify DANE usage, and vocabulary. The working group is currently addressing proposals for the use of DANE for associating OpenPGP keys and OTR public keys to email addresses, SMIME users certificates to domains, securing SMTP and SIP. 

From the perspective of ISOC's interests, the importance of DANE is that it provides a mechanism that increases the level of trust in certificates and public keys needed for communication between applications.

Agenda: http://tools.ietf.org/wg/dane/agenda?item=agenda-87-dane.html
Charter: http://tools.ietf.org/wg/dane/charters
(1 August 2013, 1700-1830)

_____________________________________
Authentication/Authorization 
Authentication (AuthN) and Authorization (AuthZ) are key components of any managed identity exchange (above or below the Web). ISOC's interest in the work called out here is in the approaches to AuthN/AuthZ; some of the specific activities are described above in our Trust interests. This work is done in conjunction with efforts in the W3C, OASIS, and other specifications groups to create solutions for both end users and intermediaries.
_____________________________________

scim (System for Cross-domain Identity Management) WG

The scim working group was chartered to standardize methods for creating, reading, searching, modifying, and deleting user identities and identity-related objects across administrative domains, with the goal of simplifying common tasks related to user identity management in services and applications. Since the last IETF, the design team has been opened up and regular working group calls have been held. Updated drafts of the core working group documents are expected in time for Berlin. In addition, it is expected that possible interoperability testing along with the proposed OAuth 2.0 SCIM client registration profile will be discussed. 

Agenda: http://tools.ietf.org/wg/scim/agenda?item=agenda-87-scim.html
Charter: http://tools.ietf.org/wg/scim/charters
(1 August 2013, 1700-1830)

--------------

kitten (Common Authentication Technology Next Generation) WG

The kitten Working Group develops extensions and improvements to the Generic Security Service Application Program Interface (GSS-API), shepherds specific GSS-API security mechanisms, and provides guidance for any new Simple Authentication and Security Layer (SASL)-related submissions. This meeting will focus on progressing exiting working group items on namespace and registries for GSS-API extensions, SAML-enhanced client SASL and GSS-API mechanisms, PKIINT algorithm agility, and an information model for Kerberos version 5.  The working group will also discuss plans to update OAuth, OpenID, and SAML specifications based on the GS2 update. 

Agenda: https://datatracker.ietf.org/meeting/86/agenda/kitten/
Charter: http://tools.ietf.org/wg/kitten/agenda?item=agenda-87-kitten.html
(1 August 2013, 1520-1650)

--------------

httpauth (Hypertext Transfer Protocol Authentication) WG

The current HTTP authentication mechanisms, basic and digest, are considered to be insecure. There is a need for improved mechanisms that can replace or augment HTTP authentication without the need to rely on transport layer security. The httpauth WG has been recently chartered to investigate a small number of HTTP user authentication schemes that might address some of the current weaknesses. This working group will document a few of these schemes, including a description of when the mechanism is appropriate, as Experimental or Information RFCs. After additional successful experimentation, the working group may be rechartered to produce standards track specifications. There are a number of existing proposals on the table for consideration. 

Agenda: http://tools.ietf.org/wg/httpauth/agenda?item=agenda-87-httpauth.html
Charter:  http://tools.ietf.org/wg/httpauth/charters
(31 July 2013, 1300-1500)

--------------

oauth (Web Authorization Protocol) WG

The Open Authentication Protocol is a mechanism that allows a user to give third-party websites or applications access to protected resources without providing them access to their long term credentials or resources. The ouath WG was chartered to update and improve the security mechanisms in the original OAUTH protocol. With the core protocol work now finished, the working group will be spending some time on discussions related to rechartering and future work. In addition, there are a number of drafts close to completion including the OAuth assertion framework, dynamic client registration, and JSON tokens. Topics requiring further discussion within the working group include MAC tokens and the OAuth 2.0 SCIM client registration profile.

Agenda: http://tools.ietf.org/wg/oauth/agenda?item=agenda-87-oauth.html
Charter: http://tools.ietf.org/wg/oauth/charters
(31 July 2013, 0900-1130)

--------------

abfab (Application Bridging for Federated Access Beyond web) WG

The abfab Working Group is chartered to specify a federated identity mechanism for use by other Internet protocols not based on HTML/HTTP, such as IMAP, XMPP, SSH, and NFS. The design combines existing protocols, specifically the Extensible Authentication Protocol (EAP - RFC 3748), Authentication, Authorization and Account Protocols (RADIUS - RFC 2865 and Diameter - RFC 3588), and the Security Assertion Markup Language (SAML). Three working group documents (use cases, a GSS-API mechanism for EAP, and naming attributes for the GSS-API mechanism) have been completed and forwarded to the RFC Editor. The EAP applicability document has been forwarded to the IESG for consideration, and the remaining documents for discussion are the core architecture document and the RADIUS document. 

Agenda: https://datatracker.ietf.org/meeting/86/agenda/abfab/
Charter: https://datatracker.ietf.org/doc/charter-ietf-abfab/
(30 July 2013, 1520-1650)

--------------

posh (PKIX over Secure HTTP) BoF

Establishing an encrypted channel over TLS depends on the ability to verify a server's identity using its PKIX certificate. However, enterprises often outsource the hosting of various sites and services to a third party hosting service. When this happens, either the hosting service needs the original domain's private key or the client needs to understand that the hosting service is actually the original domain. Neither of these is particularly secure. DNSSEC and DANE will potentially solve this problem in the future; however, full deployment of this solution is still years away. Hosting services and the domains that they host need a solution that can be deployed in the interim. The PKIX Over Secure HTTP (POSH) BoF is proposing a working group to specify a way to solve the problem using HTTPS URIs and JSON Web Keys. 

Agenda: N/A
Charter: N/A
(29 July 2013, 1620-1720)

--------------

Secure Telephone Identity Revisited  (STIR) BoF

As telecommunications moves from traditional phone networks to IP communications, one of the challenges is determining how to securely identify the origin of a phone call so that you can know who is calling.  Given concerns about robocalling, phishing and other communications security issues, this new BoF is being created to consider what work can be done within the IETF to provide a mechanism for "secure origin identification" within the Session Initiation Protocol (SIP) standard used for voice over IP (VoIP). This BoF session will outline the identified problem, briefly explain several potential solutions and then seek agreement on the scope of work that can be done within the IETF and on a potential charter for a new working group focused on this topic.

Agenda: http://tools.ietf.org/agenda/87/agenda-87-stir.html
Charter (draft): http://www.ietf.org/mail-archive/web/stir/current/msg00785.html
(30 July 2013, 0900-1130)

_____________________________________
Infrastructure/Support
Internet infrastructure -- from managed resources to collaborative efforts such as routing -- continues to evolve to meet current needs. Of particular interest this time around are ongoing efforts to secure the routing infrastructure (SIDR).
_____________________________________

i2rs (Interface to the Routing System) WG

Following a successful BoF at IETF85, a new WG is being formed. From the draft charter:

I2RS facilitates real-time or event driven interaction with the routing system through a collection of protocol-based control or management interfaces. These allow information, policies, and operational parameters to be injected into and retrieved (as read or by notification) from the routing system while retaining data consistency and coherency across the routers and routing infrastructure, and among multiple interactions with the routing system. The I2RS interfaces will co-exist with existing configuration and management systems and interfaces.

The group met for an interim meeting in April and continue to focus on
the problem statement, high-level architecture and use cases.

Agenda: http://tools.ietf.org/wg/i2rs/agenda?item=agenda-87-i2rs.html
Charter: http://tools.ietf.org/wg/i2rs/charters
(1 August 2013, 1300-1500)

--------------

sidr (Secure Inter-Domain Routing) WG

The SIDR WG is focusing on securing inter-domain routing. The overall architecture is based on a Resource PKI (RPKI) which adds an authentication framework to BGP requiring a certificate management infrastructure. This is a key technology for improving trust in the
routing infrastructure.

In its current phase the group is working on the BGPSEC requirements and protocol. Still discussions continue around issues, like scalability of the repository system, and best practices for RPKI origin validation.

Agenda: http://tools.ietf.org/wg/sidr/agenda?item=agenda-87-sidr.html
Charter: http://tools.ietf.org/wg/sidr/charters
(31 July 2013, 1510-1610; 2 August 2013, 1120-1220, 1230-1330)

--------------

grow (Global Routing Operations) WG

The purpose of the GROW is to consider the operational problems associated with the IPv4 and IPv6 global routing systems, such as routing table growth, the effects of the interactions between interior and exterior routing protocols, and the effect of address allocation policies and practices on the global routing system. GROW also advises other working groups, including IDR and SIDR, with respect to whether it is addressing the relevant operational needs, and where appropriate,suggest course corrections.

Currently under discussion are drafts related to so-called "route leaks" and their implications for routing security (draft-grow-simple-leak-attack-bgpsec-no-help) and a draft, cataloging past issues influencing the efficacy of Internet Routing Registries
(IRR) for inter domain routing policy specification and application in the global routing system (draft-ietf-grow-irr-routing-policy-considerations).

Agenda: http://tools.ietf.org/wg/grow/agenda?item=agenda-87-grow.html
Charter: http://tools.ietf.org/wg/grow/charters
(30 July 2013, 1700-1830)

--------------

dnsop (Domain Name System Operations) WG

The dnsop WG develops guidelines and publishes operational procedures related to overall operations of the DNS infrastructure. In this meeting there will be an important discussion of two different approaches for managing the communication between child zones and parent zones when a DNSSEC Key Signing Key (KSK) is updated in order to maintain the global "chain of trust". One proposal (http://tools.ietf.org/html/draft-kumari-ogud-dnsop-cds )  involves the creation of a new CDS record and polling by the parent zone. The other proposal (http://tools.ietf.org/html/draft-hardaker-dnsop-csync ) suggests the creation of a new CSYNC record type that also uses polling but is broader in scope than only DNSSEC-related records.  The discussion will explore both proposals and focus on where the group goes from here.

Agenda: http://tools.ietf.org/wg/dnsop/agenda?item=agenda-87-dnsop.html
Charter: http://tools.ietf.org/wg/dnsop/charters
(1 August 2013, 1520-1650)

--------------

opsec (Operational Security Capabilities for IP Network
Infrastructure) WG

The opsec WG documents operational issues and best current practices with regard to network security. In particular, efforts are made to clarify the rationale supporting current operational practice, address gaps in currently understood best practices for forwarding, control plane, and management plane security and clarify liabilities inherent in security practices where they exist. The outputs of the WG are BCPs and Informational documents as well as taxonomy and problem statement documents. Issues under WG consideration include BGP security best practices, implications of traffic filtering bases on 'options' field in the IPv4 packet header, as well as maintains a a snapshot of the current efforts to define or apply security requirements in various Standards
Developing Organizations (SDO) (http://tools.ietf.org/html/draft-ietf-opsec-efforts).

Agenda: http://tools.ietf.org/wg/opsec/agenda?item=agenda-87-opsec.html
Charter: http://tools.ietf.org/wg/opsec/charters
(29 July 2013, 0900-1130)

_____________________________________
IPv6
The Internet relies on a single addressing framework in order to have global reach and integrity. IPv4 address space is insufficient for today's Internet, and IPv6 has been developed as its successor. While the standard for IPv6 has long-since been finished, there are ongoing discussions of IPv6 operational issues and management, as well as possible uses in home networks and very large scale networks (of small scale devices).
_____________________________________

v6ops (IPv6 Operations) WG

A number of drafts, many individual submissions, have come in or been updated since the last IETF meeing. One, draft-chen-v6ops-ipv6-roaming-analysis-00 (http://tools.ietf.org/html/draft-chen-v6ops-ipv6-roaming-analysis-00), has the potential to become something interesting. It attempts to document all the failure cases of roaming in mobile networks with IPv6 enabled with IPv6 capable. Right now it fails to document why there are particular failures during roaming (standards shortcoming, implementation errors, failure to implement features, failure to deploy features) but it could provide a useful framework for determining actions that could be taken to accelerate deployment of
IPv6 for mobile networks.

Another draft, draft-kumari-long-headers (http://tools.ietf.org/html/draft-wkumari-long-headers-00) has generated a lot of discussion on the WG mailing list. It proposes that filtering not be performed based on the IPv6 header chain length if that is 128 bytes or less and makes no recommendation for header chains longer than that. The document provides a useful perspective on operational requirements of forwarding and filtering based on layer 3 and layer 4 in routers at larger edge networks. Discussion of these assertions has generated some of the traffic on the WG mailing list.

It is related to a discussion in 6man on a draft limiting the size of the IPv6 header chain (see below). A request for input from the v6ops WG on this document also generated a lot of email traffic. 

Much discussion on the WG mailing list these days is about what is ideal and what is realistic in terms of v6 forwarding behavior. It will be interesting to see how that plays
out over the next few months.

Agenda: http://tools.ietf.org/wg/v6ops/agenda?item=agenda-87-v6ops.html
Charter: https://datatracker.ietf.org/wg/v6ops/charter/
(29 July 2013, 1300-1530; 2 August 2013 0900-1100)

--------------

6man (IPv6 Maintenance) WG

Preceding the discussion in v6ops on the Kumari draft about long headers there was a discussion of revising (or reviving) the draft--oversized-header-chain.  The outcome of that discussion was not at all clear but also served to highlight for folks some of the operational reality of packet processing at edges of the Internet.

Another item that generated a lot of discussion on the mailing list was Ron Bonicas draft recommending the deprecation of the IPv6 fragment header.  The recommendation was to require that no new protocols make use of it, new implementations may support it but are not required to, and that routers may filter IPv6 fragments.  There is some support for this but folks raised a couple of examples of usage where recommending this could be detrimental (SIIT and OSPF in particular).

Agenda: http://tools.ietf.org/wg/6man/agenda?item=agenda-87-6man.html
Charter: https://datatracker.ietf.org/doc/charter-ietf-6man/
(29 July 2013, 1510-1610, 1620-1720)

--------------

6lo BoF
This Birds of a Feather session is intended to lead to a WG that will focus effort in the INT area to IPv6 standardization needed specifically for resource constrained (e.g. low power) networks. It will include IPv6 adaptation layers for specific low power link technologies, related MIBS, etc. The expectation is for this WG to coordinate closely with 6man to do work that is more particularly focused to low power networks than general IPv6 work is or needs to be.

Agenda: http://tools.ietf.org/agenda/87/agenda-87-6lo.html
Charter: N/A
(1 August 2013, 1700-1830)

--------------

sunset4 (Sunsetting IPv4) WG

The sunset4 Working Group focuses on areas of concern and provides recommendations to help facilitate the graceful "sunsetting" of the IPv4 Internet in areas where IPv6 has been deployed. This includes the act of shutting down IPv4 itself, as well as the ability of IPv6-only portions of the Internet to continue to connect with portions of the Internet that remain IPv4-only. At IETF 87 there will be two back-to-back meetings of the sunset4 WG. The first session will address a number of topics such as the gap analysis (http://tools.ietf.org/html/draft-ietf-sunset4-gapanalysis) as well as an interesting draft about IPv6/IPv4 interworking in VoIP (http://tools.ietf.org/html/draft-klatsky-dispatch-ipv6-impact-ipv4). 

The second session is a joint meeting with the DHC WG to look at how DHCP can best be used in an IPv6 environment to communicate the degree of available IPv4 connectivity. One draft proposes a new DHCP option to tell a host to disable IPv4 while other drafts look at passing IPv4 configuration information over IPv6 and also prioritizing the preference of DNS servers in an IPv4/IPv6 environment.

Agenda: http://tools.ietf.org/wg/sunset4/agenda?item=agenda-87-sunset4.html
Charter: http://tools.ietf.org/wg/sunset4/charters
(31 July 2013, 1510-1610, 1620-1720)

_____________________________________
Bandwidth
The public policy world is full of discussions of appropriate (and inappropriate) management of bandwidth in the face of growing network usage. The IETF and IRTF have a number of efforts underway to explore and address more sophisticated ways to make use of available bandwidth, and otherwise get content to where it needs to be, efficiently.
_____________________________________

tcpm (TCP Maintenance and Minor Extensions) WG

TCP is currently the Internet's predominant transport protocol. TCPM is the working group within the IETF that handles small TCP changes, i.e., minor extensions to TCP algorithms and protocol mechanisms. The group are working on a number of modifications to TCP that could significantly improve Internet performance as perceived by the average end user.

Agenda: https://datatracker.ietf.org/meeting/87/agenda/tcpm/
Charter: https://datatracker.ietf.org/wg/tcpm/charter/
(30 July 2013, 0900-1130)

--------------

iccrg (Internet Congestion Control Research Group)
This is the IRTF home for work on congestion control and the meeting will include interesting discussion of novel proposals for improving the algorithms used on the Internet to control congestion and thereby manage and optimise application performance for Internet users.

Agenda: https://datatracker.ietf.org/meeting/87/agenda/iccrg/
Charter: http://irtf.org/iccrg 
(29 July 2013, 1620-1720 & 31 July 2013, 1300-1500)

--------------

lmap (Large-Scale Measurement of Broadband Performance) WG

Following the successful BoF meeting at IETF86, lmap is now a chartered working group. The working group will standardize the LMAP measurement system for performance measurements of broadband access devices such as home and enterprise edge routers, personal computers, mobile devices, set top box, whether wired or wireless.

Agenda: https://datatracker.ietf.org/meeting/87/agenda/lmap/
Charter: https://datatracker.ietf.org/wg/lmap/charter/
(30 July 2013, 0900-1130)

--------------

aqm (Active Queue Management and Packet Scheduling) BoF

Following on from the discussion at the transport area open meeting during IETF86, this BoF proposes to form a working group to develop algorithms for proactively managing queues (or buffers) in networking equipment in order to:

(1) help flow sources control their sending rates before the onset of necessary losses, e.g. through ECN
(2) help minimize delays for interactive applications
(3) help protect flows from negative impacts of other more aggressive or misbehaving flows

If widely deployed, better active queue management and packet scheduling algorithms could have a huge impact on the responsiveness, resilience and usability of the Internet for diverse applications.

Agenda: http://tools.ietf.org/agenda/87/agenda-87-aqm.html
Draft charter: www.ietf.org/mail-archive/web/aqm/current/msg00127.html
(30 July 2013, 1700-1830)

--------------

ippm (IP Performance Metrics) WG

The ippm WG has recently been re-chartered and also has new leadership. Near-term milestones for the re-chartered group include:

1. Advancement of protocols for one- and two-way metrics (OWAMP and TWAMP
respectively) along the standards track.
2. Update of the IPPM framework document (RFC 2330) to reflect experience
with the framework, and to cover planned future metric development.
3. Definition of a registry of metric definitions to improve the
equivalency of metric results across multiple implementations.
4. Publication of a rate measurement problem statement.
5. Publication of documents supporting the use of IPSec to protect OWAMP /
TWAMP.
6. Publication of documents related to model-based TCP bulk transfer
capacity metrics.

Agenda: https://datatracker.ietf.org/meeting/87/agenda/ippm/
Charter: https://datatracker.ietf.org/wg/ippm/charter/
(31 July 2013, 0900-1130)

==================================================================