Simple%20usage%20scenario%20for%20SIP

1
Simple usage scenario for SIP

• An alternative to present SIP CS usage (complex)
• Tool set for implementations includes NAT
  traversal, ID, encryption
• Applicable for CS and P2P SIP
• SIP for message routing only (10 refs infos)
• All applications reside in endpoints
• Eliminate all network services
• All extensions to support business models
• Ever new business models
• Is not scalable,
• Not for applicable for everyone
• Avoid complexity in SIP routing Unaware of apps
• Avoid any awareness of user data and the
  associated policies in network elements (use
  certified identity for apps)

2
Mandatory References

1. RFC 3261 SIP Session Initiation Protocol
2. RFC 3264 An Offer/Answer Model with SDP
3. RFC 3263 Locating SIP Servers
4. RFC 3840 Indicating User Agent Capabilities in
   SIP
5. RFC 3856 A Presence Event Package for SIP
6. RFC 3863 Presence Information Data Format
   (PIDF)
7. RFC 3428 SIP Extension for Instant Messaging
8. RFC 3994 Indication of Message Composition for
   Instant Messaging
9. RFC 3581 An Extension to SIP for Symmetric
   Response Routing
10. RFC xxxx Symmetric RTP and RTCP Considered
    Helpful

3
Informative References

• SIP applications in the endpoints
• A Call Control and Multi-party usage framework
  for SIP
• Guidelines for Implementing the Dialog Event
  Package in User Agents
• A New Forking Mechanism for SIP
• NAT Traversal
• Managing Client Initiated Connections in SIP
• RFC 3489bis Simple Traversal Under NAT (STUN)
• Interactive Connectivity Establishment (ICE)
• Obtaining Relay Addresses from Simple Traversal
  of UDP Through NAT (TURN)
• Best Current Practices for NAT Traversal for
  SIP
• Other Identity and media encryption
• Enhancements for Authenticated Identity
  Management in SIP
• RFC 4347 Datagram Transport Layer Security
  (DTLS)
• ZRTP Extensions to RTP for Diffie-Hellman Key
  Agreement for SRTP