1. BINDing URIs to SIP AORs
Henning Schulzrinne
Columbia University
19 October 2019

2. Summary Information and actions associated with AOR:
scripts and call processing logic
conference control (floor control, conference management) via non-SIP protocols
upload presence
user provisioning
binding: SIP AOR  set of URIs
different degrees of indirection:
data URI
mid/cid URI
http, acap, ldap, ... URIs
19 October 2019

3. Binding vs. content indirection
Same: non-SIP URI references external data
content indirection: replace data carried in SIP body
binding: associate data with AOR
19 October 2019

4. Binding header field
Binding header field updates binding for particular purpose
Binding: <
;disposition=configuration ;expires=0 ;q=0.1
Binding: <tftp://store.example.com>
;disposition=boot ;expires=36000
Binding: ;disposition=conference ;expires=0
May be returned in by REGISTER, OPTIONS
19 October 2019

5. BIND method
REGISTER not appropriate to maintain bindings  multiple failure reasons, refresh intervals
Almost like REGISTER, but:
address to SIP URI  use methods parameter to direct to particular entity
handle both AOR and per-SIP URI bindings
;expires=0  Delete all bindings for one disposition or individual URI
event package for updates
19 October 2019

6. Open issues Is this useful in general?
For the applications envisioned?
Alternative: generalized PUBLISH
Details:
Status code "Maximum number of bindings exceeded"?
Tagged bindings for replacement?
19 October 2019