VoCCN: Voice over Content-Centric Networks Van Jacobson, Diana - - PowerPoint PPT Presentation

▶
voccn voice over content centric networks
SMART_READER_LITE
LIVE PREVIEW

VoCCN: Voice over Content-Centric Networks Van Jacobson, Diana - - PowerPoint PPT Presentation

Feb 18, 2024 805 likes •922 views

VoCCN: Voice over Content-Centric Networks Van Jacobson, Diana Smetters, Nick Briggs, Michael Plass, Paul Stewart, Jim Thornton, Rebecca Braynard Palo Alto Research Center (PARC) ReArch 09 1 December 2009 Rome, Italy Everybody knows that

slide-1
SLIDE 1

VoCCN: Voice over Content-Centric Networks

Van Jacobson, Diana Smetters, Nick Briggs, Michael Plass, Paul Stewart, Jim Thornton, Rebecca Braynard

Palo Alto Research Center (PARC)

ReArch ’09 1 December 2009 Rome, Italy

slide-2
SLIDE 2

2

Everybody knows that ...

  • Content-based networking is great for

content dissemination ...

  • ... but can’t handle conversational
  • r real-time traffic.

‘Everybody’ is half right.

slide-3
SLIDE 3

Content networking is more general than IP

It does anything that IP can. To demonstrate this we implemented VoCCN, a VoIP-functional-equivalent based on CCN. (The way we map the IP conversation model isn’t CCN-specific and should work for other Pub/Sub systems.)

3

slide-4
SLIDE 4

VoCCN – why bother?

  • VoIP works badly for multi-point,

multi-interface and mobility.

  • VoIP security is poor.
  • VoIP setup is complex.

4

IP

M

S

M

S a.com SIP proxy b.com SIP proxy Alice Bob INVITE sip:bob@b.com

IP

INVITE sips:bob@b.com

INVITE sip:bob@b.com STUN/UPnP ENUM + NAPTR + SRV STUN/UPnP
slide-5
SLIDE 5

IP builds conversations using two patterns:

  • Service to instance
  • Uni- to bi-directional

5

SIP client SIP service SIP instance

A B

B-IP A-IP SIP port 12345 data B-IP A-IP SIP port 12345 data

These are just ‘name’ manipulations that should map to any (topic-based) pub-sub system with hierarchical or algorithmic names.

B-IP:SIP/ B-IP:SIP/A-IP:12345 A-IP:12345/B-IP:SIP

slide-6
SLIDE 6

VoCCN has only a few moving parts

  • Resulting system is simple, secure and scalable.
  • Robust support for mobility and multi-point.
  • Supports secure, stateless, VoIP inter-operation.

6

Alice Bob

IP C IP C

C C C C

? b.com/sip/bob/invite/EpkB(sk)/Esk(invite)

REG: b.com/sip/bob

slide-7
SLIDE 7

7

0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 10 20 30 40 50 60 70 80 90 100 CDF: Proportion of Packets Packet Interarrival Time (ms) Packet Interarrival Times Stock LinPhone CCN LinPhone (encrypted) 10 20 30 40 50 60 70 20 40 60 80 100 120 140 160 180 Rate (pkts/sec) Time (sec) from Start of Call Link A traffic Link B traffic

link A disconnected link B disconnected link A disconnected

Performance

slide-8
SLIDE 8

8

  • Our (open-source, GPL’d) CCN stack is

available at www.ccnx.org.

  • The VoCCN linphone code should be there

by the end of this week.

Availability

Questions?

slide-9
SLIDE 9

9

slide-10
SLIDE 10

Message exchanges

10

Name:!!!!!!!!!!!!!!!!!!!!!!!!!/domain/bob/call-id/rtp/seq-no Signature Info: <metadata>, <signature> Content: SRTP packet (encrypted audio)

Caller (Alice) Callee (Bob)

<registers a desire to see interests asking for content beginning with /domain/sip/bob/invite>

/domain/sip/bob/invite/EpkB(sk)/Esk(SIP INVITE message)

"#$%&'#%$!(&)*! +,-#&!(&)*!

Name:!!!!!!!!/domain/sip/bob/invite/EpkB(sk)/Esk(SIP INVITE message) Signature Info: <metadata>, <signature> Content: Esk(SIP response message) Interest:! Data:! /domain/bob/call-id/rtp/seq-no Interest:! Data:! Name:!!!!!!!!!!!!!!!!!!!!!!!!!/domain/alice/call-id/rtp/seq-no Signature Info: <metadata>, <signature> Content: SRTP packet (encrypted audio) /domain/alice/call-id/rtp/seq-no Interest:! Data:!