a sip load control event package draft-shen-sipping-load-control-event-package-00.txt
DESCRIPTION
A SIP Load Control Event Package draft-shen-sipping-load-control-event-package-00.txt. Charles Shen, Henning Schulzrinne, Arata Koike IETF 72, Dublin Ireland July 28. Motivation: Throttle only Selected Calls When Possible. Legitimate short-term load spike - PowerPoint PPT PresentationTRANSCRIPT
A SIP Load Control Event Package
draft-shen-sipping-load-control-event-package-00.txtCharles Shen, Henning Schulzrinne, Arata Koike
IETF 72, Dublin Ireland July 28
23/4/20 Slide 2
Motivation: Throttle only Selected Calls When Possible
Legitimate short-term load spike Viewer-voting TV shows or ticket giveaways Special holidays such as New Year's Day and Mother's Day
Natural disaster areas such as those affected by earthquakes
Malicious attack caused overload Denial-of-Service attacks
Only calls causing overload should be throttled
23/4/20 Slide 3
Motivation: Current Feedback-based Control Proposal Insufficient
Feedback-based overload control is reactive affects signaling messages already issued ineffective for edge-server overload, e.g., ticket giveaway
Hotline user:
+1-212-555-1234
Service Provider for the overloaded customer
Upstream Service Provider II
PSPS
Upstream Service Provider I
Upstream Service Provider III
PS PS
PS
PS
PS
PS
Overload caused by
+1-212-555-1234
Feedback to throttle traffic may
undesirably affect other users
Most of the calls to
+1-212-555-1234
will fail but still injected
Most of the calls to
+1-212-555-1234
will fail but still injected
23/4/20 Slide 4
Requirements for Filter-based Load Control
Complements feedback-based mechanisms Prevents calls as close to the user agent client as possible Efficient and scalable filter distribution mechanism Re-uses existing SIP protocol mechanisms when possible Distribute filter in advance when overload situation is
predictable Flexible filter identity
caller/callee, single/groups, SIP/tel URLs
Extensibility for future needs
23/4/20 Slide 5
Solution
Define Load-Control Event Package for SIP based on SIP-Specific Event Notification [RFC3265]
Define Load-Control XML document for SIP extended Common-Policy: A Document Format for Expressing Privacy
Preferences [RFC4745]
SIP entities subscribe to load-control package from SIP signaling peers
Load-control event notifications distributed as widely as possible Enforce filter policies as specified
23/4/20 Slide 6
Example: Filter Hotline 212-555-1234 from 9am-12pm, 2008-7-28
User: +1-212-555-1234
Service Provider for the overloaded customer
Upstream Service Provider II
PSPS
Upstream Service Provider I
Upstream Service Provider III
PS PS
PS
PS
PS
PS
Filter SpecIDENTITY: To: +1-212-555-1234
TIME: 9am-12pm 2008-7-28ACTION: accept: rate=100
Filter SpecIDENTITY: To: +1-212-555-1234
TIME: 9am-12pm 2008-7-28ACTION: accept: rate=60
Filter SpecIDENTITY: To: +1-212-555-1234
TIME: 9am-12pm 2008-7-28ACTION: accept: rate=40
Filter SpecIDENTITY: To: +1-212-555-1234
TIME: 9am-12pm 2008-7-28ACTION: accept: rate=20
Filter SpecIDENTITY: To: +1-212-555-1234
TIME: 9am-12pm 2008-7-28ACTION: accept: rate=30
23/4/20 Slide 7
Open issues
Problem statement? Combination of events and filter? Security mechanisms?