/
1 STUN Handling 1 STUN Handling

1 STUN Handling - PowerPoint Presentation

alexa-scheidler
alexa-scheidler . @alexa-scheidler
Follow
375 views
Uploaded On 2016-07-21

1 STUN Handling - PPT Presentation

in B2BUAs draftramstraw b2bua stun STRAW Meeting IETF 90 Toronto July 25th 2014 Presenter Lorenzo Miniero Authors Ram Mohan R Tiru Reddy Gonzalo Salgueiro Problem Statement ID: 414026

b2buas ice media b2bua ice b2buas b2bua media sdp candidate stun received path termination pass candidates part incoming list

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "1 STUN Handling" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

1

STUN Handling in B2BUAs(draft-ram-straw-b2bua-stun)

STRAW Meeting, IETF 90, TorontoJuly 25th, 2014

Presenter:

Lorenzo

Miniero

Authors: Ram Mohan R,

Tiru

Reddy, Gonzalo

Salgueiro

Slide2

Problem Statement

OverviewICE Termination with B2BUAsICE Passthrough with B2BUAs

Next Steps

2

AgendaSlide3

This draft describes the behavior B2BUA should follow for STUN packets received as part of ICE processing

3

Problem StatementSlide4

Endpoints likely to use ICE

for:NAT, Firewall traversalAddress Selection (when it has multiple addresses, dual-stack, etc.)

Verify media path exists prior to connecting the call (avoids ghost rings, etc.)

B2BUAs

acting on media path likely to receive STUN packets as part of ICE processing.

RFC 5245 does not clearly describe the behavior B2BUAs should

follow

4

OverviewSlide5

B2BUAs acting on media plane can be classified

as (per RFC 7092):Media relay [only modifies transport (e.g. UDP/IP) header]

Media-aware relay [inspects

and/or modifies RTP/RTCP

headers]

Media termination

[e.g

.

Transcoder

]

B2BUAs

MUST support ICE or at a minimum support ICE LITE

functionality.

B2BUAs MUST use the mechanism described in Section 5.1.2 of [RFC5764] to demultiplex STUN packets that arrive on RTP/RTCP port.

5

Overview (cont’d..)Slide6

B2BUAs can handle STUN messages received as part of ICE processing in two

ways:ICE termination – B2BUAs can always terminate ICE on each leg and thus have two ICE contexts. Reason for termination may be due to the need for B2BUA to be in the media path (e.g. Transcoding, address hiding, interworking etc.)

ICE pass-through – In case a B2BUA does not have a need to be in media path, it can

passthrough

STUN messages received as part of ICE.

6

Overview (cont’d..)Slide7

ICE Termination

with B2BUAsB2BUAs (both full and ICE lite) terminating ICE must do the following:The B2BUA MUST NOT propagate the candidate list received in the incoming SDP to the outbound SDP. Should re-write the c/m-lines and

advertise its candidate list. The B2BUA MUST generate a new username, password values for ice- ufrag and ice-

pwd

attributes when it sends out the SDP and MUST NOT propagate the

ufrag

, password values it

received from either endpoints

B2BUA

terminates the ICE messages on each leg and does not propagate

them.

7Slide8

ICE Pass

-through with B2BUAsB2BUAs (both full and ICE lite) that wishes to pass-through ICE does the following:When a B2BUA receives an incoming SDP with ICE semantics it copies the received candidate list, adds its own candidate list in the outgoing SDP. The B2BUA also copies the ufrag/password values it received in the incoming SDP to the outgoing SDP and then sends

it out.The B2BUAs candidates will have lower-priority than the candidates provided by the endpoint; this way endpoint and remote

peer candidate

pairs are tested first before trying candidate pairs with B2BUA candidates

.

The B2BUA may optionally change m/c lines in the incoming SDP to

its

own IP

add/

port before

forwarding.

8Slide9

ICE Pass

-through with B2BUAs (cont’d)After offer/answer is complete, the endpoints will have both the B2BUA's and remote peer candidates. It will then use ICE procedures described in [RFC5245] to nominate a candidate pair for sending and receiving media streams.

With this approach the B2BUA will be in media path only if the ICE checks between all the candidate pairs formed from the both the endpoints fails.

9Slide10

Next Steps

Additional reviews neededAdoption as WG item

10