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

advertisement
IETF - Areas of Work
Patrik Fältström
Area Director, Applications Area
Document IPW-8
©Patrik Fältström 2000
What are we doing?

Work is done in Working Groups
– Specified by charters
– Specification + Work Items
– Work items according to timeline

©Patrik Fältström 2000
Internet-Drafts do not specify what
the IETF is doing, among them are
though working documents for the
working groups
Areas in the IETF








©Patrik Fältström 2000
Applications
General
Internet
Operations and Management
Routing
Security
Transport
User Services
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
©Patrik Fältström 2000
IESG Liasons











©Patrik Fältström 2000
IAB
SC2
SC6
SC21
SC29
ATM Forum
ITU
Unicode
OECD
W3C
WIPO
Keith Moore
Harald Alvestrand
Allison Mankin
Harald Alvestrand
Harald Alvestrand
Andy Malis
Scott Bradner
Patrik Faltstrom
Donald Eastlake
Keith Moore
Patrik Faltstrom
Specifically for ITU

FAX over Internet
– SG8

Media Gateway Control
– SG16

PSTN and Internet Internetworking
– SG11
©Patrik Fältström 2000
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...

©Patrik Fältström 2000
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

©Patrik Fältström 2000
IESG then makes a decision
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

©Patrik Fältström 2000
Documents should only be created
in one of the organizations, and
referenced from the other
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
©Patrik Fältström 2000
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"

©Patrik Fältström 2000
Layering issues must be resolved!
Layers in the IETF?

Telephone call
– Addressing, routing, QoS

Transport mechanism
– Connection oriented ("a call")

ITU?
IETF?
IP layer
– Addressing, routing

Link layer, UMTS, GPRS
– Addressing, routing, QoS
©Patrik Fältström 2000
ITU?
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
©Patrik Fältström 2000
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


©Patrik Fältström 2000
Decide before starting discussing
Or, is the NNR discussion a meta
discussion by itself?
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>
©Patrik Fältström 2000
Download