1 / 15

IETF - Areas of Work

IETF - Areas of Work. Patrik Fältström Area Director, Applications Area. What are we doing?. Work is done in Working Groups Specified by charters Specification + Work Items Work items according to timeline

kelsey-lamb
Télécharger la présentation

IETF - Areas of Work

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF - Areas of Work Patrik Fältström Area Director, Applications Area Document IPW-8

  2. What are we doing? • Work is done in Working Groups • Specified by charters • Specification + Work Items • Work items according to timeline • Internet-Drafts do not specify what the IETF is doing, among them are though working documents for the working groups

  3. Areas in the IETF • Applications • General • Internet • Operations and Management • Routing • Security • Transport • User Services

  4. Specifics • IETF works with a layered modular model, with IP in the middle • IP on top of something • Something on top of IP • Communication between layers • Reuse of existing solutions

  5. IESG Liasons • IAB Keith Moore • SC2 Harald Alvestrand • SC6 Allison Mankin • SC21 Harald Alvestrand • SC29 Harald Alvestrand • ATM Forum Andy Malis • ITU Scott Bradner • Unicode Patrik Faltstrom • OECD Donald Eastlake • W3C Keith Moore • WIPO Patrik Faltstrom

  6. Specifically for ITU • FAX over Internet • SG8 • Media Gateway Control • SG16 • PSTN and Internet Internetworking • SG11

  7. Other contacts • Telephone Number Mapping • SG2 • Service in the PSTN/IN Requesting Internet Service • SG11 • Signaling Transport • Multiparty Multimedia Session Control • Audio/Video Transport • IP Telephony • Session Initiation Protocol • Internetworking Over NBMA • Electronic Data Interchange-Internet Integration …and maybe some more...

  8. New work in the IETF • Anyone can propose a WG • Normally they first get a BOF • IESG decide if it looks ok • Question goes to "new-work" list and IETF as a whole • Input is requested - also from ITU • Overlapping, not clear enough charter, impossible milestones, forgotten issues, just plain stupid • IESG then makes a decision

  9. When wg exists • Liason can be appointed • Contact point for information to/from other organization • Liasons appointed in pairs • Org A assigns Foo as liason to B • Org B assigns Bar as liason to A • Documents should only be created in one of the organizations, and referenced from the other

  10. Not carved in stone • Exactly how liasons and wg work has changed from wg to wg • It depends on how the wg work, and what the wg do • We are still trying to find the way of cooperation which creates minimal friction • We eq IETF and ITU

  11. New areas • "Parallel" technologies like WAP • Is this because "glue" between layers in the IETF is not good enough? • New carriers of IP • UMTS, GPRS • Addressing, IP and lower layers • Routing of IP, and "application" • Layering issues must be resolved!

  12. Layers in the IETF? • Telephone call • Addressing, routing, QoS • Transport mechanism • Connection oriented ("a call") • IP layer • Addressing, routing • Link layer, UMTS, GPRS • Addressing, routing, QoS ITU? IETF? ITU?

  13. No borders! • We need to cooperate • Several things are • Clearly IETF • Clearly ITU • Note that addressing was mentioned in many layers • E.164 number, IP address, wireless end node identifier • How do we create correct glues? • QoS is one such issue • How do we reuse technologies? • FaxIP is email of TIFF image

  14. What is NNR? • Depends on what layer one talk about • One do easily create "layering violation" • Mix up link address with IP address with name for example • Decide before starting discussing • Or, is the NNR discussion a meta discussion by itself?

  15. Contact points • Don't hesitate contacting IESG, or rather, relevant Area Directors • http://www.ietf.org • Contacts from ITU should be coordinated, if possible Patrik Fältström <paf@swip.net>

More Related