Upload
samuel-payne
View
214
Download
0
Tags:
Embed Size (px)
Citation preview
Agenda
• Welcome
• IRTF Chair’s report– Aaron Falk
• IAB Chair’s report– Olaf Kolkman
• Open microphone session
IRTF
• 14 Research Groups working on topics related to Internet protocols, applications, architecture and technology
• Some groups very tied to IETF work, others not so much
• Most groups are open, all maintain open mailing lists
• Not too structured:– Room for overlaps in scope, very hard problems, diverse
management styles– But also pre-standardization maturation
IRTF Status
• Seven Research Groups met at this IETF– SAMRG, DTNRG, EME/HIPRG, MOBOPTS,
ICCRG, RRG
• Published draft-irtf-rfcs-01 on the IRTF RFC review and publication process
• 1 IRTF RFC published since IETF-68– RFC4838 Delay-Tolerant Networking Architecture – ~10 drafts in-progress towards publication
Routing Research Group
• Meeting tomorrow.• Very active list (and on ram list)• Still producing new and modified proposals.• Converging on design goals.
Delay Tolerant Networking RG
• RFC 4838 (architecture document) published– 17 drafts in the tracker, 4 nearing RFC readiness
• Held an interim meeting in Dublin.– Much of the discussion was security-related.
• Met Tue morning this week: – Discussion focused on reliability and neighbor
discovery.
• Next planned meeting: IETF-71.
Mobility Optimizations RG
• Met this week
• Document on Layer 2 abstrations for mobility has completed IRSG review
• Working on: – Location Privacy and Mobility, – Multicast Mobility
End-Middles-End RG
• Held a joint meeting with HIP RG at IETF-69– EME complements HIP RG work for providing
name space and mechanism to relay policy requests
– EME can help HIP with NAT traversal– Potential future collaboration with HIP: larger scale
experiment
• Continuing to discuss Paul Francis’ NUTSS proposal
Host Identity Protocol RG
• Joint meeting with EMERG held on Tuesday:– to explore possible architectural synergy
• Three new drafts presented this meeting:– Two related to HIP as part of the P2PSIP
architecture– One regarding the applicability of shim6 REAP
protocol to HIP
Internet Congestion Control RG
• Two current drafts:– Survey of current congestion control RFCs
• Intention: provide CC designers with guide to related work
– Survey of open CC research issues• Charter item
• Starting to evaluate congestion control proposals for TSV area
• Met yesterday at IETF-69• Planning to meet in Manchester in conjunction with
PFLDnet 2008
Scalable, Adaptive Multicast RG
• Two active IDs: – SAM Framework, – Application-Layer Multicast (ALM) Router on PlanetLab
• ALM survey published as book chapter
• Met this week• Next meeting: planned for IETF 71 (Philadelphia)
Crypto-Forum Research Group
• Published a new message authentication code "VMAC: Message Authentication Code using Universal Hashing"
• List discussion on a variety of technical issues (AES-based KDFs, AEAD, SIV draft)
Internet Measurement RG
• Workshop on Application Classification and Identification (WACI) to be held October 3rd at BBN Technologies in Cambridge, MA.
Anti-Spam Research Group
• Working on DNS Black Lists:– Progress (slow) toward publishing the DNSBL
definitions draft– DNSBL Guidelines draft may follow
• Seeking interest in taxonomy of anti-spam strategies
• Occasional snake-oil salesmen show up and get little sympathy
Network Management RG
• Pretty quiet since Prague IETF • Some work on management trace analysis • Contemplating/planning workshops and future
meetings
Transport Modeling RG
• “Evaluation Metrics for Congestion Control” now in IRSG review
• A new document on "An NS2 TCP Evaluation Tool Suite” along with a web page with simulation scripts under discussion.
Peer-to-Peer Research Group
• Currently soliciting proposals for new work– Expected to feed into a charter update
• In need of new chairs
IAB(a reminder)
• 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
• Correspondencehttp://www.iab.org/documents/correspondence/index.html
• Liaisons and more all via the IAB website
Document Activity
Architectural documents
• RFC publications– RFC 4840: Multiple Encapsulation Methods
Considered Harmful– RFC 4903: Multi-Link Subnet Issues– RFC 4907: Architectural Implications of
Link Indications– RFC 4924: Reflections on Internet
Transparency
Document Activity (cont’d)
Workshop Reports• RFC Queue:
– draft-iab-iwout-report-03, “Report from the IAB workshop on Unwanted Traffic March 9-10, 2006”
– draft-iab-raws-report-02, “Report from the IAB Workshop on Routing and Addressing“
Non architectural documentspublished/announced/done– RFC 4844: The RFC Series and RFC Editor– RFC 4845: Process for Publication of IAB RFCs– RFC 4846: Independent Submissions to the RFC
Editor
Administration
• Appointed Ted Hardie as member of the ISOC Board of Trustees
• Liaison appointments– Loa Anderson: IAB liaison to the IESG– Danny Mc Pherson: IAB liaison to the
NomCom– ITU-MPLS: Stewart Bryant– ITU-NGN: Scott Brim is stepping down
Inter-Organizational
• ITU was looking for input on their role in Internet policy and standards development.– Provided input with respect to the IETF’s role in
this space– http://www.iab.org/documents/correspondence/2007-05-21-itu-resolution-102.html
• Informal gathering between IETF and ITU leadership on July 21st.– Goal: Get to know each other so that future
interaction collaboration is more effective and fruitful
Inter-Organizational(continued)
• IDN follow up– Proposals in ISO/TC46 that would impact
IDNS• Notified ISO/TC46 of the possible impact on
our work
• DNSSEC updates– RIPE NCC ready to sign e164.arpa– http://www.iab.org/documents/correspondence/2007-07-05-ripe-ncc-dnssec-e164.html
– http://www.iab.org/documents/correspondence/2007-07-24-iab-itu-dnssec-e164.html
RetreatOngoing business and possible future work
• Routing and Addressing– Actively following developments and building
common understanding of architectural issues
• IP fundamentals– What assumptions are made in stacks, how do
they relate to original design goals– IP and NAT and architectural questions
• Bridging Gaps– IETF & ISOC, IETF & IRTF, IETF & Other
organizations, IETF and other stakeholders