Identity header example (from RFC 4474)

INVITE sip:bob@biloxi.example.org SIP/2.0
Via: SIP/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bKnashds8 To: Bob <sip:bob@biloxi.example.org>
From: Alice <sip:alice@atlanta.example.com>;tag=1928301774 Call-ID: a84b4c76e66710
CSeq: 314159 INVITE
Max-Forwards: 70
Date: Thu, 21 Feb 2002 13:02:03 GMT
Contact: <sip:alice@pc33.atlanta.example.com>
Identity: "ZYNBbHC00VMZr2kZt6VmCvPonWJMGvQTBDqghoWeLxJfzB2a1pxAr3VgrB0SsSAa ifsRdiOPoQZYOy2wrVghuhcsMbHWUSFxI6p6q5TOQXHMmz6uEo3svJsSH49thyGn
FVcnyaZ++yRlBYYQTLqWzJ+KVhPKbfU/pryhVn9Yc6U="
Identity-Info: <https://atlanta.example.com/atlanta.cer>;alg=rsa-sha1
Content-Type: application/sdp Content-Length: 147
v=0
o=UserA 2890844526 2890844526 IN IP4 pc33.atlanta.example.com s=Session SDP
c=IN IP4 pc33.atlanta.example.com
t=0 0
m=audio 49172 RTP/AVP 0 a=rtpmap:0 PCMU/8000

Slide Notes

Peterson and C. Jennings, Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP), IETF, Network Working Group, RFC 4474, August 2006 http://tools.ietf.org/html/rfc4474 Links to an external site.

Transcript

[slide360] And basically the idea is that now I can have an identity here, which is an encrypted message, and I say the IdentityInfo and I give the information about the server where you can go to verify that identity. And I also say in this case that it's using RSA for the encryption and SHA-1 for the authenticity protection of that particular message. So someone now, knowing that, could go and check, am I really who I claim to be?