ietf 72 host presentation and technical plenary 29 july 2008 dublin, ireland
TRANSCRIPT
IETF 72Host Presentation
andTechnical Plenary
29 July 2008
Dublin, Ireland
Agenda
• Welcome• Host Presentation• IRTF Chair’s report
Aaron Falk
• IAB Chair’s reportOlaf Kolkman
• Technical topic: IPv6 Deployment Forum
Moderated by Gregory Lebovitz
• Open microphone session
Host Presentation
Kevin O'CallaghanCountry Leader
Alcatel-Lucent Ireland.
Agenda
• Welcome• Host Presentation• IRTF Chair’s report
Aaron Falk
• IAB Chair’s reportOlaf Kolkman
• Technical topic: IPv6 Deployment Forum
Moderated by Gregory Lebovitz
• Open microphone session
Update on the Internet Research Task Force
Aaron Falk
IRTF Chair
IETF-72 – Dublin
IETF-71 -- Philadelphia, BC 8
Content Template
• Content Template
Internet Architecture BoardUpdateOlaf M. Kolkman
Dublin, Ireland
July 30, 2007
IETF 72, July 30, 2008, Dublin, Ireland
IAB
• IAB Charter: RFC2850http://www.iab.org/about/overview.html
• Documentshttp://www.iab.org/documents/selected-iab-documents.html
• Minuteshttp://www.iab.org/documents/iabmins/index.html
Backlog in minutes
• Correspondencehttp://www.iab.org/documents/correspondence/index.html
• Liaisons and more all via the IAB website
Document Activity (1)
Published:• What Makes For a Successful Protocol?
– RFC5218
About to be submitted to the RFC editor:• Design choices while expanding the
DNS– draft-iab-dns-choices-06– Needs one more editorial spin
Document Activity (2)Work in Progress:
• Principles of Internet Host Configuration– draft-iab-ip-config-04 – Expect a call for comments shortly
• Headers and Boillerplates– draft-iab-streams-headers-boilerplates-00– Relates to work on 3932-bis and the IRTF
stream definition
Architectural Activity
• Stockholm, April 25-26 (Hosts: Netnod and Arceo)Various topics:– The evolution of the IP model (lead: Dave
Thaler)• draft-thaler-ip-model-evolution-01.txt
– Peer to Peer Architecture (lead: Gonzalo Camarillo)
• Forthcoming: draft-camarillo-iab-p2p-archs-00
– IPv6 Technical Plenary (lead: Gregory Lebovitz)
Inter organizational 1Liaison Activity
• Internal IAB organization to structure and coordinate Liaison activities– Liaison shepherds
• Bert Wijnen stepped down as IEEE 802.1 liaison– Thanks for years of service!– Eric Gray has replaced Bert
• Class A liaison relation with ISO/TC46: John Klensin appointed as liaison
Inter Organizational 2The Joint Working Team on MPLS extensions
ITU-T Members
ITU-T T-MPLS Ad Hoc
Team
MPLS Interoperability
DesignTeam
Joint Working
Team(20)
IETF Members
ITU
IETF
The JWT was established to sort out how to proceed with MPLS for transport networks
Agreement on the recommendation
IETF to:– develop a transport profile for MPLS (MPLS-TP)– Taking into account ITU-T transport network
requirements
The ITU-T to:– Intergrate MPLS-TP in the transport network– Allign the current T-MPLS ITU-T rec. with MPLS-
TP– Terminate the work on T-MPLS
• For more details see: draft-bryant-mpls-tp-jwt-report-00.[txt|pdf]
Inter Organizational 3OECD
• In cooperation with ISOC
• Cosigned a memorandum on the Future of the Internet in a Global Economy– http://www.isoc.org/pubpolpillar/docs/oecd-
technical-community-memorandum.pdf
• Participation in the Technical Forum prior to the OECD Ministerial on the Future of the Internet Economy
IETF OrganizationalRFC Editor Model
• IAB: responsible for maintaining/defining the RFC Editor model
• IAOC: responsible for implementation of agreement between the IETF and the RFC editor
• RFC Editor contract up for bids in 2009• In order to guarantee continuity going
forward we needed a comprehensive model
RFC editor model
• Separates the RFC Editor function into 4 functional “production and process” roles– Independent Stream Approver– RFC Editor– Production House– Publisher
• Suggests methods for filling the positions and welcomes suggestions for possible other models
Where to learn more and provide input
Details on the IAB websitehttp://www.iab.org/documents/resources/RFC-Editor-Model.html
• Specific questions around:– Selection of the RFC Editor and Indep. Stream
approver; RFP or RFC4333 like process?
• Your informed views are welcome• Discussion takes place on the RFC interest
mailing list– Affects all streams– Conclusions to be drawn shortly after Dublin– Feedback to rfc-interest list– Decision by end of August
• Lars Eggert is succeeding Mark Townsley as IESG liaison to the IAB
• Logo: Designed by Dow Street.
• We have had no appeals
Worth Mentioning
IPv6 Deployment Forum
Moderation: Gregory Lebovitz
IPv6 DeploymentPanel
Follow Along with Us
• Jabber: [email protected]
• Presentations: https://datatracker.ietf.org/meeting/72/materials.html
Pls Read the Introduction
• Introduction & Background from the IAB– Done via email to save time for presenters and
Q&A
http://www.ietf.org/mail-archive/web/ietf/current/msg52686.html
IPv6 Transition Work Addressed this Week
• NAT-PT = transition mechanism defined a while back in RFC2766, deprecated in RFC4966.
• Use-cases that NAT-PT addressed (and some it didn’t) still need to be addressed; requirements persist.
• This week discussions in several places to cover these use-cases:– IPv6 Ops– Behave WG– Softwires (IPv6 in v4 L2TP tunnels)– Int Area– Ops Area– Even snuck into IPsecME
Panel Participants
• Mark Kosters – ARIN
• Alain Durand – Comcast
• Shin Miyakawa – NTTcom
• Lorenzo Colitti – Google
• Stuart Cheshire – Apple
• Gregory Lebovitz – Moderator
Ground Rules Keep the Pace
• 10 min per presenter– Hold all questions until Q&A time.– Yes, even clarifying questions
• 15 min of Moderator-led Q&A• 15-20 min Open Mic Q&A
– Questions, not pontifications– 30 seconds to ask– 1 question per person, as long as queues are full
Moderator’s Q&A
Q&A from the floor
Recall the Ground Rules
• Q & A from the Floor–15-20 min Open Mic Q&A– Questions > Comments– 30 seconds to ask– 1 question per person, as
long as queues are full