SIP: Session Initiation Protocol

Rosenberg, Jonathan; Schulzrinne, Henning; Camarillo, Gonzalo; Johnston, Alan; Peterson, Jon; Sparks, Robert; Handley, Mark; Schooler, Eve M.

doi:10.17487/rfc3261

Cited by 2,752 publications

(2,842 citation statements)

References 26 publications

Supporting

Mentioning

2,781

Contrasting

Unclassified

Order By: Relevance

“…It is also responsible for modifying and terminating these sessions. The details of this protocol are specified in RFC 3261 [1]. …”

Section: Overviewmentioning

confidence: 99%

“…UA UA Target Domain Origin Domain The SIP request takes the following form, as defined in [1]. The "To:" header conveys information about the desired target user in the target domain.…”

Section: Step 1: Invite (Initiating An Inter-domain Session)mentioning

confidence: 99%

“…In step 1, the calling party's User Agent sends an INVITE to the target user The SIP request takes the following form (as described in [1] "Confidentiality and message integrity MUST be maintained in step 1." [7] Step 2: 428 Artifact/Assertion Required:…”

Section: Step 1: Invite (Initiating An Inter-domain Session)mentioning

confidence: 99%

“…The SIP response MUST conform to [1]. The target domain PEP SHOULD provide some form of helpful error message in the case where the originating user is not authorized to initiate a session with the target user.…”

Section: Step 1: Invite (Initiating An Inter-domain Session)mentioning

confidence: 99%

“…The current security mechanisms defined in the SIP specification, RFC 3261 [1], provide authentication, integrity and confidentiality. Authorization, however, hasn't been explicitly provided.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Session Initiation Protocol (SIP)

Burke

2007

Speech Processing for IP Networks

View full text Add to dashboard Cite

Anand Chavali (M.S., Telecommunications) Implementing Role-based Authorization capabilities in the Session Initiation Protocol (SIP) Thesis directed by Professor Douglas SickerThis thesis presents an approach to providing role-based authorization capabilities for the Session Initiation Protocol (SIP). SIP defines various methods for performing authentication. Authorization, however, is not defined explicitly and is generally based on identity. This does not scale well in multi-domain scenarios. In order to facilitate a greater level of granularity and scalability for authorization in SIP, new mechanisms need to be defined. This thesis describes the implementation of role-based authorization capabilities as part of a federation.Federation, or federated management, is an approach where domains share the responsibility of controlling access to their respective resources to users in similarly diverse domains. It is particularly suited to a multi-domain environment and is extremely scalable. Role-based authorization is a paradigm wherein authorization decisions are based on 'role(s)' asserted or assumed by a user rather than the identity of that user. Roles assigned to a user depend on the function performed by that user in the particular organization.

show abstract

“…It is also responsible for modifying and terminating these sessions. The details of this protocol are specified in RFC 3261 [1]. …”

Section: Overviewmentioning

confidence: 99%

“…UA UA Target Domain Origin Domain The SIP request takes the following form, as defined in [1]. The "To:" header conveys information about the desired target user in the target domain.…”

Section: Step 1: Invite (Initiating An Inter-domain Session)mentioning

confidence: 99%

Section: Step 1: Invite (Initiating An Inter-domain Session)mentioning

confidence: 99%

Section: Step 1: Invite (Initiating An Inter-domain Session)mentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations