IETF 82 in Taipei is rapidly approaching (13-18 November 2011). Newcomers' training and technical tutorials take place on Sunday (13 November), with the working group, BoF, and plenary sessions happening during the week.
Once again, the Internet Society is pleased to bring you our regular Rough Guide to the sessions most relevant to our current work.
We continue to turn our attention to the following broad categories:
- Common and Open Internet
- Global Addressing
- Security and Stability
- Trust and Identity
(All times are local, UTC +8)
In addition to the WG and BoF sessions listed below, these sessions are of general interest:
+ IAB Technical Plenary
'Interconnecting Smart Objects with the Internet'
Prior to the IETF 72 meeting in Prague, the Internet Architecture Board held a workshop on 'Interconnecting Smart Objects with the Internet' and published a report soon afterwards:
The report illustrates some of the challenges the industry is facing in an attempt to improve interoperability in areas where IP has not been used before. This IAB technical plenary is devoted to the topic of smart objects and will summarize the workshop and solicit feedback from the wider IETF community stimulated via panel discussion. Hannes Tschofenig will moderate the plenary where Jari Arkko, Fred Baker, Zach Shelby, Carsten Bormann, and Robert Assimiti share their views with the community.
(14 November 2011, 1630-1930)
+ Internet Research Task Force (IRTF) Open Meeting
Applied Networking Research Prize (ANRP) winners will present their work and take questions during this meeting. Michio Honda was awarded for his research into determining the future extensibility of TCP: Is it Still Possible to Extend TCP? Nasif Ekiz was awarded for his analysis of misbehaving TCP receivers: Misbehaviors in TCP SACK Generation. For more details about the ANRP, see:
(15 November 2011, 1300-1500)
NOTE: IETF Journal v7.2 provides a summary of BoF sessions from IETF 81:
To receive regular information about the IETF, including a summary of BoF sessions from IETF 82 in the upcoming edition, you may wish to subscribe to the IETF Journal at:
Common and Open Internet
As P2P and VoIP technologies become more prevalent, and network usage patterns sometimes deviate from their architects' expectations, managing bandwidth to allow best use for customers becomes an increasingly important topic.
behave (Behavior Engineering for Hindrance Avoidance) WG
The behave Working Group creates documents to make NATs function as deterministically as possible. Much of the recent work has been to document the behavior of address translation, both IPv4/IPv4 and IPv6/IPv4. Potentially interesting could be the discussion of large-scale NATs (LSN) requirements and approaches to logging events in the LSN environment (when an IP addresses alone cannot identify a user).
(17 November 2011, 1520-1720)
tictoc (Timing over IP Connection and Transfer of Clock) WG
The tictoc working group is chartered to address next generation network time synchronization requirements. It is looking into enhancements for both the Network Time Protocol (NTP) and the IEEE 1588 Precise Time Protocol (PTP). This meeting will continue to address MPLS encapsulations, security requirements, and network management. Key topics for this meeting will include general security requirements for time synchronization protocols, the implications of carrying time synchronization information in IPSec tunnels, the status of the IEEE 1588 MIB development effort, and further efforts to resolve issues with the draft on MPLS encapsulation.
(17 November 2011, 1300-1500)
There is steadily increasing momentum to deploy IPv6 as the IPv4 address pool approaches depletion. While much work is ongoing to support interoperability in coexisting IPv4 and IPv6 network environments, there are also interesting developments in emerging IPv6 environments.
v6ops (IPv6 Operations) WG
RFC 6204 is an informational RFC that specifies to some extent basic requirements for home routing equipment implementing IPv6. There is quite a bit of interest in making a revision to this specification in light of early deployment experience. Some are also interested in adding additional requirements to support additional transition technologies. The revision has elicited more discussion than most anticipated and it is unclear what kind of progress can be made on this in the near term.
(16 November 2011, 0900-1130; 17 November 2011, 1500-1700)
Security and Stability
Securing the DNS and greater assurance in routing is critical for the ongoing expansion and evolution of the Internet in all areas of our societies and economies.
dane (DNS-based Authentication of Named Entities) WG
Dane WG is looking at the use of DNSSEC to facilitate the establishment of cryptographically secure communications for Internet applications. It is specifically chartered to specify mechanisms and techniques that allow Internet applications to establish cryptographically secured communications. This is accomplished by using information distributed through DNSSEC for discovering and authenticating public keys associating a service located at a domain name.
The agenda is not published yet, but there is certain expectation that the bulk of issues raised with the main document - draft-ietf-dane-protocol will be resolved and the document can move to the WG Last Call.
(14 November 2011, 0900-1130)
karp (Keying and Authentication for Routing Protocols) WG
The karp WG is focused on improving the state of authentication in all the Internet routing protocols. Many routing protocol deployments, if they use authentication at all, are using older (possibly deprecated) cryptographic algorithms and are missing some modern security mechanisms, like replay protection, algorithm agility, or key rollover. In addition, the issue of key management is a major stumbling block to deployment. The karp WG is working to address these topics in a number of IETF routing protocols. The foundational documents have stabilized, and this meeting will focus on analysis of operational models for key management and gap analysis and proposed approaches for various routing protocols.
(16 November 2011, 1300-1500)
kitten (Common Authentication Technology Next Generation) WG
The purpose of the kitten Working Group is to develop extensions/improvements to the GSS-API, shepherd specific GSS-API security mechanisms, and provide guidance for any new SASL related submissions. Two recently updated drafts: "A SASL and GSS-API Mechanism for OAuth" and "A SASL and GSS-API Mechanism for SAML" are of particular interest in the context of on line identity management and relate directly to efforts in the AbFab and Oauth working groups.
(15 November 2011, 1710-1810)
mile (Managed Incident Lightweight Exchange) WG
The recently chartered Mile working group will develop standards and extensions for the purpose of improving incident information sharing and handling capabilities based on the work developed in the IETF Extended INCident Handling (INCH) working group. The group will discuss adoption of existing drafts and a consensus call will be made on the list after IETF 82.
(16 November 2011, 1510-1610)
sidr (Secure Inter-Domain Routing) WG
The SIDR WG is focused on securing inter-domain routing. The approach being developed is 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.
Most of the work regarding the basic RPKI infrastructure is nearing completion and the discussion moves to the deployment infrastructure and protocols. But the bulk of work is happening in the area of BGPSEC - extensions to BGP that allow path validation.
(16 November 2011, 0800-1100)
weirds (WHOIS-based Extensible Internet Registration Data Service) BoF
The work aims at a replacement for WHOIS to be delivered as a RESTful service, with an eye to avoiding a number of the issues that have prevented IRIS deployment as a WHOIS replacement. The impetus for this work is the existence of three already-deployed experimental services along these lines, and the burgeoning number of IDN TLDs in the domain name system root zone. This paper provides useful background reading to understand this work:
(Draft) Charter: http://www.ietf.org/mail-archive/web/weirds/current/msg00231.html
(Draft) Agenda: http://www.ietf.org/mail-archive/web/weirds/current/msg00220.html
(16 November 2011, 0900-1130)
Trust and Identity
As public concerns increase about security of infrastructure, privacy, trust, and identity on the Internet, these themes recur in several working group discussions.
abfab (Application Bridging for Federated Access Beyond Web) WG
The abfab WG is chartered to develop federated solutions for non-web applications using EAP, AAA (Radius and Diameter), and SAML. It grew out of work done by the Moonshot project sponsored by JANET in the UK. For this meeting, the agenda will include review of the core architecture and use case documents along with discussions related to the Generic Security Service Application Program Interface (GSS-API) when using the EAP mechanism. In addition, there have been a number of individual submissions on topics including how to support multihop federations and user interface usability.
(18 November 2011, 1120-1220 and 1230-1330)
oauth (Open Authentication Protocol) WG
The Open Authentication Protocol is a mechanism that allows a user to give third-party web sites or applications access to protected resources without providing them access to their long term credentials or resources. The oauth WG was chartered to update and improve the security mechanisms in the original oauth protocol. This meeting will be focused on rechartering the working group now that the version 2.0 specifications are approaching completion. Possible rechartering topics include token revocation, dynamic client registration, user-managed access, xml encoding, simple web discovery, and JSON web token formats.
(17 November 2011; 1300-1500)
Other Items of Interest
In addition to formal working group (WG) and birds-of-a-feather (BoF) meetings, other developments around the IETF meeting may be of interest
jose WG (formerly WOES)
). Note, discussion on the possible definition of a token format has been determined to be out of scope and will be taken up in the oauth rechartering discussion.
(14 November 2011, 1300-1500)
multrans (Multicast Transition) BOF
This is the second BoF for this group. In the first BoF they talked
about the problems with multicast service in an IPv4-IPv6 transitional environment, but focus was diffused. This time the focus is on IPTV, and application-layer gateways.
(17 November 2011, 1740-1940)
Software Driven Networks (SDN) BoF
SDN infrastructure and components exist in most deployed networks today. Some of these components are being standardized by various organizations, as well some being already standardized by the IETF. However, no standards or open specifications currently exist to facilitate end-to-end operation of a software defined network, specifically one that provides open APIs for applications to control the network services and functions offered by device control planes or other "controlling" software. This BoF will explore whether there is clearly defined work to do here and whether this is IETF work.
Charter: to be discussed
(17 November 2011, 1740-1940)
A repute bar BoF was held in Quebec City (IETF 81) to consider formalizing some of the work coming out of discussions on the domainrep list relating to development and deployment of domain reputation evaluation and communication. There are a number of Internet Drafts already in circulation and a draft charter is currently under IESG review. REPUTE will develop mechanisms for reputation reporting by independent services. One mechanism will be for a basic assessment of trustworthiness. Another will provide a range of attribute/value data that is used as input to such an assessment. Each service determines the attributes it reports.
List Archive: https://www.ietf.org/mailman/listinfo/domainrep
(16 November 2011, 1510-1610)