Organizations

a portal for promoting internet and telecom
standardization knowledge

IETF topics > SIP
  RFC index search site map about tech-invite home
# IETF   # 3GPP   # ETSI
# Alliances, Fora, & other SDOs
Standardization work
# IETF WGs: RFCs & Drafts  
# IAB # IRTF
# 3GPP series   # ETSI committees
IETF topics
# SIP   # Security  
# Presence, IM & XCAP
# Conferencing   # Media Control  
# EAP   # Mobility Management  
3GPP topics
# Network Architecture   # GPRS  
# IMS   # Security Architecture  
# AKA   # GAA/GBA   # LI  
# GAN   # MBMS   # I-WLAN   # EPS  
# PCC   # Charging  
# HSS & Subscriber Data   # GUP  
# LCS   # Presence   # PoC  
# SIP-I   # ISC   # ICS  
ETSI topics
# TISPAN NGN  
Other topics
# M2M   # RFID   # NFC  
# Network Simulation
#public access
#private access (full or partial)
# public access so far, but very likely private access with next version
# SIP RFC3261's Example  
# SIP Protocol Structure  
# SIP Dialogs & Routing  
# SIP Service Examples  
# SIP Authentication Service  
# ABNF Grammars (SIP, SDP...)  

SIP Authentification Service as per RFC 4474

RFC 4474 defines a mechanism for securely identifying originators of SIP requests, especially in an interdomain context. The authentication service authenticates Alice and validates that she is authorized to assert the identity that is populated in the From header field. It then computes a hash over some particular headers, including the From header field and the bodies in the message. This hash is signed with the private key for the domain and inserted in a new header field in the SIP message, the 'Identity' header.

The proxy, as the holder of the private key of its domain, is asserting that the originator of this request has been authenticated and that she is authorized to claim the identity (the SIP address-of-record) that appears in the From header field. The proxy also inserts a companion header field, Identity-Info, that tells Bob how to acquire its certificate, if he doesn't already have it.

When Bob's domain receives the request, it verifies the signature provided in the Identity header, and thus can validate that the domain indicated by the host portion of the AoR in the From header field authenticated the user, and permitted the user to assert that From header field value.
Authentication Service for Non-REGISTER SIP Requests
Top   1) Alice: TLS Connection 2) Alice: REGISTER (1) 3) Alice: REGISTER (2) 4) Alice: INVITE (1)
Prev Next 5) Alice: INVITE (2) 6) P-atlanta: Build "Identity" 7) P-biloxi: Check "Identity"

Authentication Service for Non-REGISTER SIP Requests
Top   1) Alice: TLS Connection 2) Alice: REGISTER (1) 3) Alice: REGISTER (2) 4) Alice: INVITE (1)
Prev Next 5) Alice: INVITE (2) 6) P-atlanta: Build "Identity" 7) P-biloxi: Check "Identity"

Authentication Service for Non-REGISTER SIP Requests
Top   1) Alice: TLS Connection 2) Alice: REGISTER (1) 3) Alice: REGISTER (2) 4) Alice: INVITE (1)
Prev Next 5) Alice: INVITE (2) 6) P-atlanta: Build "Identity" 7) P-biloxi: Check "Identity"

Authentication Service for Non-REGISTER SIP Requests
Top   1) Alice: TLS Connection 2) Alice: REGISTER (1) 3) Alice: REGISTER (2) 4) Alice: INVITE (1)
Prev Next 5) Alice: INVITE (2) 6) P-atlanta: Build "Identity" 7) P-biloxi: Check "Identity"

Authentication Service for Non-REGISTER SIP Requests
Top   1) Alice: TLS Connection 2) Alice: REGISTER (1) 3) Alice: REGISTER (2) 4) Alice: INVITE (1)
Prev Next 5) Alice: INVITE (2) 6) P-atlanta: Build "Identity" 7) P-biloxi: Check "Identity"

Authentication Service for Non-REGISTER SIP Requests
Top   1) Alice: TLS Connection 2) Alice: REGISTER (1) 3) Alice: REGISTER (2) 4) Alice: INVITE (1)
Prev Next 5) Alice: INVITE (2) 6) P-atlanta: Build "Identity" 7) P-biloxi: Check "Identity"

Authentication Service for Non-REGISTER SIP Requests
Top   1) Alice: TLS Connection 2) Alice: REGISTER (1) 3) Alice: REGISTER (2) 4) Alice: INVITE (1)
Prev Next 5) Alice: INVITE (2) 6) P-atlanta: Build "Identity" 7) P-biloxi: Check "Identity"

Last update: January 25, 2010 
© 2005-2010 Joël Repiquet, All Rights Reserved.