Submission Information: The Call for Proposals is now CLOSED

Proposals: The focus areas for talks at this Joint Techs are Software Defined Networking, Integration of Services Across Multiple Networks, and Convergence. Other areas of continued interest include Security, Performance/Measurement, and IPv6. Preference will be given to submissions that demonstrate relevance to campus networking concerns. Please feel free to submit proposals on those topics, as they will be duly considered. We are holding a few spaces for proposals on other relevant topics, so please do not let the primary focus areas limit your submission.

Primary Focus Areas	Co-Chairs
Software Defined Networking (SDN)	Matt Davy (IU) & Inder Monga (ESnet)
Integration of Services Across Multiple Networks	Eric Boyd (Internet2) & Evangelos Chaniotakas (ESnet)
Convergence	Jeffry Handal (LSU) & Scott Bradley (BNL)
Areas of Continued Interest
Performance/Measurement	Jason Zurawski (Internet2)
Security	Joe St Sauver (Internet2 & University of Oregon)
IPv6	Michael Lambert (PSC) & Michael Sinatra (ESnet)

Primary Focus Areas

Software Defined Networking

The SDN paradigm is revolutionizing how networks -- and the constituent network software, hardware and services -- are being designed and built. This topic area is a primary focus for the meeting; the co-chairs are working to identify individuals and projects that are using OpenFlow and other SDN tools in interesting and useful ways but welcome proposals from the community. This full-day event will consist of a series of presentations with multiple demos, small group discussions, and aims to answer questions that network engineers/operators face on campus while deploying and helping researchers use this new technology. Topics of especial interest include deployment/uses on campus networks, data centers, disruptive applications of SDN, and end-to-end SDN/Wide Area Networks.

Integration of Services Across Multiple Networks

In our current network culture, individual networks are very comfortable talking or sharing data with each other but each NOC/Engineering group is responsible for their individual network. In the past year, the community has tried to build up coordinated services that span multiple networks, but each effort has taken far longer and resulted in less than one might hope. Inspired by community work on LHCONE, DICE services, DYNES, and IRNC, this topic area focuses on example case areas, what went right, what went wrong, and what is realistic. It will cover both use cases (e.g. an overview of LHCONE development) and topic areas (e.g. what's needed to have a multi-domain diagnostic service). It could include focus on service areas such as performance monitoring, dynamic circuits, video, etc.

Convergence

After many years of hype over the coming of convergence technologies, the real merging of traditional voice, data, and video teleconferencing technologies has arrived.  Within a few short years, handheld PDA’s and the iPad have become ubiquitous, Voice over IP telephony has become the industry standard for new telephony deployments, and video teleconferencing technologies have migrated from stand-alone facilities to the desktop.  Adoption and deployment of converged technologies requires a fundamental shift in thinking as to how previously disparate data networking, voice telephony and video teleconferencing are to be designed, deployed and maintained.  In addition to addressing “what’s out there” in terms of future R&D, presentations given as part of this focal area will emphasize and share pragmatic lessons learned from organizations that have evolved their system and support models in support of new, converged technology services.

Areas of Continued Interest

Performance/Measurement

User expectations for data transfer performance across the wide area are still seldom met. Users are left wondering what went wrong and how to improve performance. This problem is intrinsically complex because the user's data transfer path is likely to involve multiple layers of the network stack and to cross multiple network domains that are administratively independent. However, network monitoring and performance diagnosis tools, and monitoring frameworks, have emerged to alleviate the problems in addressing this complexity. In addition, the Large Hadron Collider at CERN will start in November with unprecedented data volumes -- its transfers will be a significant field validation for existing network performance tools.

The network performance and monitoring focus area at Summer 2010 Joint Techs will examine the advances and opportunities in network performance monitoring, diagnosis, and tuning. We seek presentations that discuss such experiences; suggested topics include (but are certainly not limited to):

• Performance Measurement
• Multi-domain end-to-end network measurement projects and tools, both IP-based, and circuit-based. For projects and tools that consider circuit-based services, how is end-to-end (e.g., workstation to server) performance considered?
• Measurement and monitoring tools and use cases
• Best practices in application, network and device performance tuning and diagnosis
• Effective network operational metrics to show how well network performs.
• Advanced and complex network metrics monitoring, such as topology monitoring for dynamic network circuits.
• Emerging Tools
• perfSONAR developments and directions; monitoring frameworks and layered architectures
• Network Monitoring Centers
• Secure access / use concerns (adopting OpenID, etc.)
• User Experience
• End-user experiences
• Application community experiences
• Campus experiences
• Monitoring LHC data transfers after LHC starts in November
• NOC engineer experiences (deploying & using to solve problems)

Security

The Security Focus area is interested in network security and/or system security talks including (but not limited to) talks on:

• Routing security (RPKI and BGP route hijacking analysis/mitigation, attacks against the routing infrastructure control plane, etc.)
• Layer-2 ethernet security (ARP/ND spoofing and related threats)
• IPSec deployment experiences
• Scalable deployment of multifactor/multichannel authentication (including lessons learned from large scale deployments of crypto tokens, personal certs, biometrics, etc.)
• New security issues arising from commercial deployment of large-scale NAT (aka "carrier grade NAT"), particularly with respect to successful backtracking abnd mitigation of observed security incidents
• The unique challenges of network security at 10Gps and higher speeds
• Security consideration related to US UCAN and broadband stimulus-relateed activities
• Physical security of advanced networking facilities
• New and particularly promising open source network security tools the community should know about
• Reports on security related work by Internet2-related entities in leading third party organizations such as the IETF, IEEE, NANOG, ICANN, ARIN/RIPE/APNIC/LACNIC/AFRINIC, ACM, IEEE, APWG, MAAWG, etc.

IPv6: The Coming Crisis in Routing and Addressing

Several significant addressing and routing limitations in both hardware and software are converging into a "perfect storm" that could have a major impact on the stability of the Internet. These include:

• Exhaustion of IPv4 address space and its impact on the size of the forwarding table.
• Growth of the default-free FIB has moved beyond the capacity of many popular routers.
• "Churn" resulting from the acceleration of the growth in prefixes advertised in BGP is reaching the point where processors in popular routers can no longer converge forwarding tables between updates.
• The deployment of global network resources (storage and computing) has been forced into NAT and application gateways, even in North America.
• IPv6-enabled networks don't help until users can run IPv6-only stacks.]
• Those deploying IPv6 for wide-area services have encountered problems involving both loss of ‘reach-ability’ in some cases, and even faster growth of the hardware resources needed.

This focus area will look at the nature and scope of the problem and at possible approaches to dealing with it. These may involve hardware and software changes including significant changes in how global routing is done.