[SIPForum-discussion] Request for Comments - Preliminary FeatureSet Document

[kaushik at ncoretech.com]

Hi,

My thoughts.

Dilemma is - how to universally define what is "mandatory"
and what is "recommended". For e.g. there can be an implementation
of UA that does not support TCP (for call signaling), RFC 3262,
RFC 3263 but is sufficient because some of these aspects are taken
care of by another piece in the puzzle.

I was thinking that, may be, we should first define usage scenarios
and then create a profile for each.

Secondly, w.r.t. defining what is "mandatory" we should keep it
absolutely minimal (so long as there is usage scenario where smaller
set of features are sufficient).

Regards,
Kaushik


Quoting larry schessel <lschesse at gmail.com>:

> All,
>
> I'm resending the attached document since I haven't seen any comments
> to the feature set categories (Section 6). While the categories are
> high level, I do think it is important that we finalize these
> categories before proceeding to define specific requirements within
> the categories. I am also including below the last feature categories
> and requirements details developed by Markus Isomaki of Nokia - if
> people would rather provide comments to that more detailed list.
>
> Please send comments to the above distribution. Specifically, we
> should be commenting on whether this is the correct feature list to
> define phone requirements.
>
> As further reminder - the next SIP Phone TG meeting will be next
> Tuesday, May 15, at 1:00PM EST (NY). The bridge is 1-218-486-1300, PIN
> 920441. I'll send out another meeting reminder on Monday.
>
> Regards,
>
> Larry Schessel
> SIP Forum Marketing Chairman
>
> *** Input from Markus Isomaki follows ***
> Mandatory features
> - RFC 2327: Session Description Protocol.
> - RFC 3261: SIP: Session Initiation Protocol. UA MUST support both SIP
> over UDP and SIP over TCP.
> - RFC 3262: Reliability of Provisional Responses.
> - RFC 3263: Locating SIP Servers.
> - RFC 3264: An Offer/Answer Model with the Session Description Protocol
> (SDP).
>
> Recommended features
> - RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification.
> - RFC 3311: The Session Initiation Protocol (SIP) UPDATE Method.
> - RFC 3515: The Session Initiation Protocol (SIP) REFER Method.
> - RFC 3966: The tel URI for Telephone Numbers.
>
> Advanced features
> - RFC 3312: Integration of Resource Management and Session Initiation
> Protocol (SIP). QoS precondition.
> - RFC 3327: Session Initiation Protocol (SIP) Extension Header Field
> for Registaring Non-Adjacent Contacts.
> - RFC 3608: Session Initiation Protocol (SIP) Extension Header Field
> for Service Route Discovery During Registration.
> - draft-ietf-sip-gruu: Obtaining and Using Globally Routable User
> Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP).
>
> Security
> --------
>
> With the mandatory features the User Agent is able to use SIP over TLS
> and HTTP digest authentication with a proxy/registrar. The recommended
> features provided additional stronger end-to-end identity and message
> integrity/confidentiality.
>
> Mandatory features
> - RFC 3261: SIP: Session Initiation Protocol. SIP over TLS, HTTP-digest.
> - RFC 3325: Private Extension to the Session Initiation Protocol (SIP)
> for Asserted Identity witin Trusted Networks.
> - draft-ietf-sip-outbound: Managing Client Initiated Connections in
> the Session Initiation Protocol (SIP)
>   -> Normative dependency on draft-ietf-sip-gruu: Obtaining and Using
> Globally Routable User Agent (UA) URIs (GRUU) in the Session
> Initiation Protocol (SIP).
>
> Recommended features
> - draft-ietf-sip-identity: Enhancements for Authenticated Identity
> Management in the Session Initiation Protocol (SIP).
> - RFC 3261: SIP: Session Initiation Protocol. S/MIME.
> - RFC 3892: The Session Initiation Protocol (SIP) Referred-By
> Mechanism. With the S/MIME protected token.
>   -> Normative dependency on RFC 3420: Internet Media Type message/sipfrag.
> - RFC 3893: Session Initiation Protocol (SIP) Authenticated Identity
> Body (AIB) Format.
>
> Advanced features
> - RFC 3310: HTTP Digest Authentication Using Authentication and Key
> Agreement (AKA).
> - RFC 3329: Security Mechanism Agreement for the Session Intiation
> Protocol (SIP).
>
> Real-time Media and Voice
> -------------------------
>
> This set contains features that form the baseline for real-time media
> services (e.g. audio and video) and allow the User Agents to make
> basic point-to-point voice calls. Recommended features add more voice
> media capabilities, for instance for better voice quality.
>
> Mandatory features
> - RFC 3550: RTP: A Transport Protocol for Real-Time Applications.
> - RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control
> - Voice codecs: G.711, iLBC?
>
> Recommended features
> - Voice codecs: G.729, G.723, AMR
> - Wide-band voice codecs?
>
> Telephony
> ---------
>
> This set contains the building blocks for the most important telephony
> services, including proper interworking with the PSTN and the
> execution of "supplementary" services, such as call transfer.
>
> Mandatory features
> - RFC 2833: RTP Payload for DTMF Digits, Telephony Tones and Telephony
> Signals.
> - RFC 3891: The Session Initiation Protocol (SIP) "Replaces" Header.
> - RFC 3892: The Session Initiation Protocol (SIP) Referred-By
> Mechanism. Without the S/MIME protected token.
> - RFC 3960: Early Media and Ringing Tone Generation in the Session
> Initiation Protocol S(SIP).
> - RFC 3966: The tel URI for Telephone Numbers.
>
> Recommended features
> - RFC 3087: Control of Serice Context Using SIP Request-URI
> - RFC 3842: A Message Summary and Message Waiting Indication Event
> Package for the Session Initiation Protocol (SIP)
> - draft-ietf-sip-gruu: Obtaining and Using Globally Routable User
> Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP).
> - draft-ietf-sipping-cc-transfer: Session Initiation Protocol Call
> Control - Transfer.
>
> NAT Traversal
> -------------
>
> The mandatory features allow the User Agent to traverse non-symmetric
> NATs and work well with Session Border Controllers. The recommended
> features provide traversal for symmetric NATs without SBCs and
> optimizations for end-to-end media.
>
> Mandatory features
> - UA MUST be able and by default use the same local UDP ports for
> transmitting and receiving RTP and RTCP. Reference can be found at
> draft-wing-behave-symmetric-rtprtcp: Common Local Transmit and Receive
> Ports (Symmetric RTP).
> - RFC 3489: STUN - Simple Traversal of User Datagram Protocol (UDP)
> Through Network Address Translators (NAT).
> - RFC 3581: An Extension to Session Initiation Protocol (SIP) for
> Symmetric Response Routing.
> - RFC 3605: Real Time Control Protocol (RTCP) Attribute in Session
> Description Protocol (SDP).
> - draft-ietf-sip-outbound: Managing Client Initiated Connections in
> the Session Initiation Protocol (SIP)
>
> Recommended features
> - draft-ietf-mmusic-ice: Interactive Connectivity Establishment (ICE):
> A Methodoloty for Network Address Translator (NAT) Traversal for
> Offer/Answer Protocols
> - draft-rosenberg-midcom-turn: Traversal Using Relay NAT (TURN)
>
> Advanced features
> - draft-rosenberg-mmusic-ice-tcp: TCP Alternatives for Interactive
> Connectivity Establishment (ICE)
>
> Configuration
> -------------
>
> Basic User Agent configuration.
>
> Mandatory features
> - draft-ietf-sipping-config-framework: A Framework for Session
> Initiation Protocol User Agent Profile Delivery
>
> Instant Messaging
> -----------------
>
> Messaging services. Mandatory features allow basic page-mode
> (one-shot) and session-mode (chat) messaging between User Agents.
>
> Mandatory features
> - RFC 3428: Session Initiation Protocol Extension for Instant Messaging.
> - draft-ietf-simple-message-sessions: The Message Session Relay Protocol.
>
> Recommended features
> - RFC 3994: Indication of Message Composition for IM.
> - draft-ietf-simple-msrp-relays: Relay Extensions for the Message
> Session Relay Protocol (MSRP).
> - draft-ietf-sipping-uri-list-message: Multi-Recipient MESSAGE
> Requests in the Session Initiation Protocol (SIP).
>
> Presence
> --------
>
> The mandatory set allows the User Agent to publish its own presence
> and subscribe to the presence of other users - with reasonable
> richness. The recommended features add functionality such as
> authorization and optimized list subscriptions. They also include more
> presence attributes for the UA to use and understand.
>
> Mandatory features
> - RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification.
> - RFC 3903: Session Initiation Protocol (SIP) Extension for Event
> State Publication
> - RFC 3856: A Presence Event Package for the Session Initiation Protocol
> (SIP).
> - RFC 3863: Presence Information Data Format (PIDF).
> - draft-ietf-simple-presence-data-model: A Data Model for Presence
> - draft-ietf-simple-rpid: Rich Presence Extensions to the Presence
> Information Data Format
>
> Recommended features
> - RFC 3857: A Watcher Information Event Template-Package for the
> Session Initiation Protocol (SIP).
> - RFC 3858: An Extensible Markup Language (XML) Based Format for
> Watcher Information.
> - draft-ietf-simple-cipid: CIPID: Contact Information in Presence
> Information Data Format
> - draft-ietf-simple-future: Timed Presence Extensions to the Presence
> Information Data Format to Indicate Past and Future Time Intervals
> - draft-ietf-simple-prescaps-ext: User Agent Capability Extension to
> Presence Information Data Format (PIDF).
> - draft-ietf-simple-event-list: A Session Initiation Protocol (SIP)
> Event Notification Extension for Resource Lists.
> - draft-ietf-simple-xcap-list-usage: Extensible Markup Language (XML)
> Formats for Representing Resource Lists.
> - draft-ietf-simple-presence-rules: Presence Authorization Rules.
>   -> Normative dependency on draft-ietf-geopriv-common-policy: A
> Document Format for Expressing Privacy Preferences.
> - draft-ietf-simple-xcap: The Extensible Markup Language (XML)
> Configuration Access Protocol (XCAP).
> - draft-ietf-simple-xcap-pidf-manipulation: An Extensible Markup
> Language (XML) Configuration Access Protocol (XCAP) Usage for
> Manipulating Presence Document Contents
>
> Advanced features
> - draft-ietf-simple-partial-notify: Session Initiation Protocol (SIP)
> Extensions for Partial Notification of Presence Information.
> - draft-ietf-simple-partial-publish: Publication of Partial Presence
> Information.
> - draft-ietf-simple-partial-pidf-format: Presence Information Data
> Format (PIDF) Extension for Partial Presence.
> - draft-ietf-simple-xml-patch-ops: An Extensible Markup Language (XML)
> Patch Operations Framework Utilizing XML Path Language (XPath)
> Selectors.
> - draft-ietf-simple-event-filter-funct: Functional Description of
> Event Notification Filtering.
> - draft-ietf-simple-filter-format: An Extensible Markup Language (XML)
> Based Format for Event Notification Filtering.
>
> Video
> -----
>
> TBD. Feature set for basic video service.
>
> Conferencing
> ------------
>
> Mandatory features
> - draft-ietf-sipping-cc-conferencing: Session Initiation Protocol Call
> Control - Conferencing for User Agents.
>
> Recommended features
> - draft-ietf-sipping-conference-package: A Session Initiation Protocol
> (SIP) Event Package for Conference State.
>
> Advanced features
> - draft-ietf-sipping-uri-list-conferencing: Conference Establishment
> Using Request-Contained Lists in the Session Initiation Protocol.
> - Floor control
>
> Wireless
> --------
>
> TBD. Will contain features that are important for User Agents that
> want to work well in low bitrate wireless access networks. These
> include e.g. Signaling Compression, QoS preconditions, and Presence
> optimizations.
>
> "IMS"
> -----
>
> TBD. Will contain features that are mandatory or recommended for User
> Agents that aim to be used in 3GPP IP Multimedia Subsystem (IMS) based
> deployments.
>