IETF an overviewand a few work items...

Olaf M. Kolkmanolaf@NLnetLabs.nl

Contains material from Lars Eggers, Scott Bradner, and others

On the IETF

The Internet Engineering Task Force isa loosely self-organized group of peoplewho contribute to the engineering andevolution of Internet technologies.It is the principal body engaged in thedevelopment of new Internet standardspecifications. RFC4677

IETF

• The IETF is an open, international community

• Network designers, operators, vendors and researchers

• Goal: evolution of the Internet architecture and smooth operation of the Internet

• Open to any interested individual “people, not companies”

• Produces Internet standards (and other documents)

In other words

IETF Trust

IETF Universe

RFC Editor

IASAIAD IAOC IESG

Area Area Area Area Area Areaworkinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

workinggroup

IETF Secretariat

INT

RTG

TSV

OPS

RAI

About Packets

About creating the paths for the packets

About managing the networks

About the use of the paths to provide the end-to-end experience

AboutReal Time Applications

APS About Application Protocols used on the Internet

SECAbout Security Protocols (cross area)

IESGApplications

AreaP. Saint-AndreA. Melnikov

TransportArea

L. EggertD. Harrington

SecurityArea

S. TurnerT. Polk

RoutingArea

S. BryantA. Farrell

O&MArea

R. BonicaD. Romascanu

RAIArea

G.GamarilloR. Sparks

InternetArea

J. ArkkoR. Droms

GENERALAREA

R. Housley

altocalsify

coredecade

eaihttpbis

httpstatehybi

irimarf

morgoauth

sievevcarddav

vwrap

yam

behavedccp

fecframeippm

ledbatmptcp

nfsv4hybi

nsispcn

ppsprmt

stormtcpm

tsvwg

dkimemu

hokeyipsecme

ismskeyprov

httpstatekitten

krbltans

msecnea

pkixsasl

smime

syslog

tls

bfdccamp

forcesidr

isiskarp

l2vpnl3vpn

manetmpls

ospfpce

pimpwe3

roll

rtgwg

sidrvrrp

adslmibbmwg

dimednsop

growipfix

mbonednetconf

netmodopsawg

opsecpmol

radext

avtbliss

codecdispatch

drinksecrit

enumgeopriv

martinimediactrl

mmusicp2psip

simplesipcore

siprec

speechsc

speermintxconxmpp

v6ops

16ng6lowpan

6manancp

autoconfcsi

dhcdnsext

hipipdvb

l2tpextlisp

mextmif

mip4

mipshop

multimobnetlmm

ntppppext

savi

shim6tictoc

trill

• 1K-2K people at 3 meetings/year

• from ca. 40-50 different countries

• Many, many more on mailing lists

• ~120 Working Groups (WGs)

• ~2 WGsG chairs each

• 8 Areas with 15 Area Directors (ADs)

• More than 5500 RFCs published

• Internet Standards and informational documents

• More than 50000 Internet Draft revisions submitted

US617

JP105

CN102

FR47

CA40

DE39

UK32

FI29

Others181

IETF77 Anaheim March 2010

1192 people173 newcomersIETF 74 was 1157 people

48 countries IETF 74 was 49 countries

IETF 74 was held in San Francisco

People

On RFCs and Internet Drafts

Documents...Internet Draft (I-D)

Active working documents

Not finalized! Not stable!

Anyone can submitdraft-yourname-...

Only some IDs are WG documents!

draft-ietf-wgname-...

Request For Comment (RFC)

Archival publicationsNever change once published

Not all RFCs are standards!Standards track:

Proposed StandardDraft StandardFull Standard

Other types:InformationalExperimentalBest-Current-Practice (BCP)

In fact:Not all RFCs are IETF documents

On the individual Areas

Internet (INT)

• Focus on layer-3architecture and protocols

• IPv4 and IPv6

• VPNs and MPLS

• DNS and DHCP

• Mobility & multihoming

• Network access control

InternetArea

J. ArkkoR. Droms

16ng6lowpan

6manancp

autoconfcsi

dhcdnsext

hipipdvb

l2tpextlisp

mextmif

mip4

mipshop

multimobnetlmm

ntppppext

savi

shim6tictoc

trill

LISP

• Set out to document an experimental architecture for a Locator-Identity split.

• IP addresses currently serve two purposes: splitting may have benefits

• LISP is only one approach (also see the routing research group)

• Incremental deployment, no changes to end hosts

• Running code: a lot can be learned even when this might not be the final solution

InternetArea

J. ArkkoR. Droms

16ng6lowpan

6manancp

autoconfcsi

dhcdnsext

hipipdvb

l2tpextlisp

mextmif

mip4

mipshop

multimobnetlmm

ntppppext

savi

shim6tictoc

trill

DNSEXT• DNSSEC and TSIG/TKEY algorithm maintenance

• Mechanisms that complement, or are alternatives to, TSIG and SIG(0)

• Hardening DNS protocol and providing guidance to implementers

• Advancing existing DNS-related Proposed Standard RFCs to Draft/Full

• Standard

• Obsoleting DNS-related RFCs

• Maintaining a Wiki containing a guide to DNS protocol RFCs

• Improving DNS zone synchronization mechanisms

• Examining transport protocols, possibly adding new ones.

• Mechanisms to alias DNS trees or parts thereof

InternetArea

J. ArkkoR. Droms

16ng6lowpan

6manancp

autoconfcsi

dhcdnsext

hipipdvb

l2tpextlisp

mextmif

mip4

mipshop

multimobnetlmm

ntppppext

savi

shim6tictoc

trill

Transport (TSV)

• Focus on layer-4 transport protocols and services

• TCP, UDP, SCTP, DCCP

• Congestion control

• Multicast, signaling

• NAT regularization

• IP storage and NFS

TransportArea

L. EggertD. Harrington

behavedccp

fecframeippm

ledbatmptcp

nfsv4hybi

nsispcn

ppsprmt

stormtcpm

tsvwg

BEHAVE

• Working group focused on Network Address Translator traversal

• IPv6 network to IPv4 Internet

• IPv6 Internet to IPv4 Network

• IPv4 network to IPv6 Internet

• IPv4 Internet to IPv6 Network

• Coexistence and Transition, not for long term

Behave

Security (SEC)

• Focus on security protocols and services for integrity, authentication, non-repudiation, confidentialityand access control

• IPsec, TLS

• Kerberos, SASL

• S/MIME

SecurityArea

S. TurnerT. Polk

dkimemu

hokeyipsecme

ismskeyprov

httpstatekitten

krbltans

msecnea

pkixsasl

smime

syslog

tls

FEDAUTH BOF(tentative)

• Moonshot project

• Proposed charter:http://www.project-moonshot.org/bof/charter

SecurityArea

S. TurnerT. Polk

dkimemu

hokeyipsecme

ismskeyprov

httpstatekitten

krbltans

msecnea

pkixsasl

smime

syslog

tls

Routing (RTG)

• Focus on layer-3 routing protocols

• Forwarding for unicast, multicast and MPLS

• Routing and signaling protocols (OSPF, IS-IS, BGP), MPLS

• Routing security

RoutingArea

S. BryantA. Farrell

bfdccamp

forcesidr

isiskarp

l2vpnl3vpn

manetmpls

ospfpce

pimpwe3

roll

rtgwg

sidrvrrp

SIDR

• Architecture base on a PKI representing address and AS hierarchy

• Route Origination Authorizations

• Attestation that a certain address prefixes can be originated by an AS

• RIRs will be maintaining CAs for the address space they maintain

• http://tools.ietf.org/html/draft-ietf-sidr-arch

RoutingArea

S. BryantA. Farrell

bfdccamp

forcesidr

isiskarp

l2vpnl3vpn

manetmpls

ospfpce

pimpwe3

roll

rtgwg

sidrvrrp

Operations & Management (OPS)

• Focus on network management and operation

• AAA, DNS, IPv6 & routing operations

• Management (SNMP, NetConf, CAPWAP)

O&MArea

R. BonicaD. Romascanu

adslmibbmwg

dimednsop

growipfix

mbonednetconf

netmodopsawg

opsecpmol

radext

v6ops

Real-Time Applications and Infrastructure (RAI)

• Focus on delay-sensitive applications + services

• Voice & video over IP

• Instant messaging and presence

• SIP and RTP

• IP telephony & services

RAIArea

G.GamarilloR. Sparks

avtbliss

codecdispatch

drinksecrit

enumgeopriv

martinimediactrl

mmusicp2psip

simplesipcore

siprec

speechsc

speermintxconxmpp

Dispatch• WG that helps to identify where work can

be done within the RAI area

draft-avasarala-dispatch-comm-barring-notificationdraft-avasarala-dispatch-comm-div-notificationdraft-camarillo-dispatch-preconsdraft-dawes-dispatch-mediasec-parameterdraft-drage-dispatch-sub-datadraft-gautam-dispatch-quick-answerdraft-haluska-dispatch-charge-number-neededdraft-haluska-dispatch-csi-neededdraft-haluska-dispatch-isup-olidraft-hutton-dispatch-session-recording-archdraft-jesske-dispatch-reason-in-responsesdraft-jesske-dispatch-req-reason-in-responsesdraft-johnston-dispatch-sip-cc-uuidraft-kaplan-dispatch-session-iddraft-lawrence-dispatch-sipforum-provider-alias

draft-li-dispatch-cbusdraft-liess-dispatch-alert-info-urnsdraft-loreto-dispatch-disaggregated-mediadraft-malas-dispatch-sip-egress-routedraft-patel-dispatch-cpc-oli-parameterdraft-rehor-dispatch-session-recording-reqdraft-rosenberg-dispatch-vipr-overviewdraft-rosenberg-dispatch-vipr-pvpdraft-rosenberg-dispatch-vipr-reload-usagedraft-rosenberg-dispatch-vipr-sip-antispamdraft-rosenberg-dispatch-vipr-vapdraft-yusef-dispatch-ach-rest-apidraft-zhipeng-dispatch-dynamic-adaptation

CODEC

• Set out to develop an Internet Wideband Audio Codec

• New work for the IETF

• New Community

• Cross Area: Collaborate with various WGs in the Transport Area and RAI

• Collaboration with ITU-T specified in the Charter

RAIArea

G.GamarilloR. Sparks

avtbliss

codecdispatch

drinksecrit

enumgeopriv

martinimediactrl

mmusicp2psip

simplesipcore

siprec

speechsc

speermintxconxmpp

Application (APP)

• Focus on applications and application-layer protocols

• Current work items:

• Email, calendaring, web

• Directories, registries

• Internationalization

ApplicationsArea

P. Saint-AndreA. Melnikov

altocalsify

coredecade

eaihttpbis

httpstatehybi

irimarf

morgoauth

sievevcarddav

vwrap

yam

Internationalized Resource Identifiers (IRI)

• Internationalization is one of the focus points within the current IAB

• Encoding of Identifiers in protocols, specifically where domain names are used, is troublesome e.g. from security perspectives

• http://tools.ietf.org/html/draft-iab-idn-encoding

ApplicationsArea

P. Saint-AndreA. Melnikov

altocalsify

coredecade

eaihttpbis

httpstatehybi

irimarf

morgoauth

sievevcarddav

vwrap

yam

Topics

• There are a number of cross-area topics

• Two examples:

• IPv6 Transition

• ‘Internet of Things’

IPv6 work in the IETF

• Behave: Deals defines translation mechanisms to connect IPv4 to IPv6 networks

• Softwires: Provides tunneling mechanisms to connect islands of address families (see RFC4925)

• 6man: Fixes ‘bugs’ in the IPv6 specification

• v6ops: Operational guidance and more

• SAVI: improvement of validation of sources of IP traffic on a link (v4 and v6)

• CSI: Reviewing secure neighbor discovery (SEND)

‘Internet of Things’

• ROLL: Routing Over Low power and Lossy networks

• Leddbat: Low Extra Delay Background Transport

• Smart Power Directorate

• http://www.ietf.org/iesg/directorate/smart-power.html

Some Links

• http://www.ietf.org/

• http://tools.ietf.org/

• http://www.ietf.org/tao.html

• http://tools.ietf.org/html/<partial-draft-name>

Next: IETF 78Maastricht, NLJuly 25-30, 2010

?