Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler...

23
Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill April 6, 2004

Transcript of Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler...

Page 1: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4

INLS184Architectures and Issues in

Real Time Conferencing Protocols

Tyler Miller-Johnson

University of North Carolina at Chapel Hill

April 6, 2004

Page 2: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Exercise – Exploring Standards

• What is a standard ?

• What is the purpose of a standard ?

• Name 3 standards.

• What characteristics are desirable in a standards body ?

Page 3: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Exercise: What is a standard ?

• De facto• De jour• Proprietary• Agreed upon set of rules, set by authoritative

body• Set of rules to maintain consistency across an

industry• Accepted common system of procedures to

provide a uniform method of design and/or operation

Page 4: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Exercise: What is the purpose

of a standard ?• Avoid inefficiency

• Ensure interoperability

• Guide and ensure development

• Quality

Page 5: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Exercise: Examples of standards

• Traffic signs• Electricity• Food labels• IEEE 802.11b/g• Address an envelope• Phone conversation• RJ-45• TCP/IP• Metric system• IEEE 1394• ISO 9600• MARC for cataloging

Page 6: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Exercise: What characteristics are

desirable in a standards body ?

• Open• Non partial• Non proprietary• Simple• Respected• Rational• Knowledgeable• Uniform

• Quick• Thorough• Multiple

manufactures• Represent users of

the system• Widely accessible

Page 7: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Case Study:

Standardized Addressing Modes• URL Based Dialing

– Uses DNS to resolve address of call server– Uses endpoint registration to resolve endpoint address– Example h323:[email protected]

• ENUM– Uses DNS to translate a phone number into an URL– Phone numbers under municipal control– Example +1.(919) 843-7004 becomes:

• 4.0.0.7.3.4.8.9.1.9.1.e164.arpa• <h323:[email protected]>

• What are the social, GUI, market and technical consequences of this choice?

Page 8: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Comparing Standards Bodies

ITU / IETF

• International Telecommunications Union– Inter-governmental

organization under the umbrella of the United Nations (www.itu.int)

– Covers multiple topic and networks

– US Representation through US State Department

– Annual Cost• Associate: $7000• Sector: $40,000

• Internet Engineering Task Force– International community

of network designers, operators, vendors, and researchers chartered under ISOC (the Internet Society)

– Focused on Internet– No governmental

oversight– Annual Cost

• Individual: $0• ISOC Corporate:

variable with graduated benefits

Page 9: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4What Are Real Time Communications?

• Applications– Voice Over IP

• IP Telephony• Interactive Audio

Conferencing• Modem Over IP• Fax Over IP

– Video Conferencing– Instant Messaging– Presence

• Standards– H.323

• Voice• Video

– SIP• Voice• Presence• Instant Messaging• Video

– XMPP• Instant Messaging

Page 10: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4

Page 11: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4What Could You Do With This

Technology ?

Page 12: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Typical H.323 Stack

H.323

IP

UDP

RTP

RTCP

TCP/UDP TCP UDPUDP TCP

Audio

Codecs

G.711

G.723.1

G.729

..

Video

Codecs

H.261

H.263

H.264

..V.150 T.120

TCP/UDP

T.38

H.225.0

Call

Signaling

H.245H.225.0

RAS

Terminal Control and ManagementData

ApplicationsMedia Control

Multimedia Applications, User Interface

* source: Paul Jones, ITU-T H.323 Rapporteur SIP

Page 13: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Basic Architectural Elements

• Registration• Call Setup• Media Flow

• Smart endpoints– H.323, SIP

• Dumb endpoints– H.248, PSTN

Call ServerGateway MCU

AudioVideo

Page 14: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Firewall / NAT Issues

• NAT hides destination address• Communication out, but not in• Application Level Gateways

– Protocol Aware– Encryption breaks

Call ServerGateway MCU

Page 15: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4

Security

Knock, Knock.

Page 16: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4

Who’s There ?

Page 17: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Security Elements

• Authentication– Proving someone’s identity

• Authorization– What are they allowed to do?

• Privacy– Encryption of media– Encryption of call signaling

Page 18: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Regulatory Issues

• HIPPA requires privacy. CALEA requires wiretapping.• Service provider has no access to media• Media and call signaling may be encrypted• Service providers may become ubiquitous• Service providers may not fall under regulations (i.e. in another country)• “Help, I’ve fallen and I can’t get up !” – 911• How do we tax?

Call ServerGateway MCU

Page 19: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4Our Thinking Is All Wrong !

• Old– End users need access to central resources– End users are ‘clients’– IT must protect itself against end user abuse– Home domain is the world

• New– End users need access to each other– End users are servers and service providers– End users need to authenticate each other– The world is a large and complex place, but we

want to live there!

Page 20: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4E2M Security(user ID / password)

• Pros– Ensures nobody steals

service provider’s resources

– Ensures you pay your bill

• Cons– Doesn’t allow you to

access resources in other realms

– Doesn’t provide caller ID– Doesn’t recognize true

people to people nature of application

Call Server

Page 21: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4E2E Security

(X.509 certificates - PKI)

• Pros– Confirms your identity to

the called party– Works across realms

• Cons– Requires common

authentication across reams

– Other applications don’t use this approach

– Administrative cost to identity verification

Incoming Call From:

Dr. Thomas GrayRadiology

<OK> Duke University<OK> Internet2

Call Server

Page 22: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4How Does Federation Help ?

• E2E security features• Still implement your own authentication methods• Recognizes the world is a messy place

Call Server

Incoming Call From:

Dr. Thomas GrayRadiology

<OK> Duke University<OK> Internet2

Duke UNC

Internet2

Federation

Provider A Provider B

FCC

Federation

Page 23: Tyler Johnson - 2004 INLS184 Architectures and Issues in Real Time Conferencing Protocols Tyler Miller-Johnson University of North Carolina at Chapel Hill.

Tyle

r Jo

hnso

n -

2

00

4This Changes Everything

• Access to many service providers• Not necessarily required to pre-establish accounts• Call signaling and networks can be un-secured

Incoming Call From:Sarah McAllister

<OK> VISA 123456<OK> Provider A<OK> FCC

DukeHospital

UNCHospital

Federation

Provider A Provider B

FCC

Federation

MCUProvider

VoIPProvider

VoIPProvider

PTAFundraiser