[SIPForum-discussion] [SIPForum-techwg] Request for Comments - Preliminary Feature Set Document

Tue May 15 13:51:07 UTC 2007

Hi all, 

Sorry for the delay.  I do have some basic comments, for discussion on the 
call today. 

The general categorization looks basically fine overall, though I'm sure 
we could (and will) dicker over details. 

My main comment is the content is (so far) basically just a list of RFCs, 
with no support for why that particular list needs to be supported.  The 
sections are called "features" (in Markus' listing), but do not really 
list what the features are, just the RFCs.  For example, if REFER is 
required, why, what user operations does it support?  I think, for each 
section, we need to outline specifically what features are expected to be 
supported, may even need to roughly define the features (*gasp*).   Then, 
what RFCs (perhaps even specific sections) are needed to do so.  If there 
are multiple ways pointed by the RFCs, then pick *one*. as the 
recommended. 

Another concern is there are other supporting pieces needed to provide a 
quality product.  For example: 
- basic IP networking (eg. Diffserv, including recommended DSCPs)
- IEEE stuff, eg 802.1D/p, 802.1Q, LLDP/LLDP-MED ...
- Acoustic performance, loss plans and such (can point to TIA specs for 
these) 
I Can gather some refs for these bits if we agree it is needed. 

A small organization thing:  I suggest "Core" be subdivided, roughly as 
follows: 
   6.1 Core functions (basis for all other feature sets
      6.1.1 Core SIP (current sec 6.1)
      6.1.2 Core Networking (some of the stuff listed above)
      6.1.3 Core security (current sec 6.2)
      6.1.4 Core NAT traversal current sec 6.12 ... assuming we would want 
to say all MUST do NATs)

We will also need a section on emergency services support. 

Hope this helps, and talk to y'all in a few...

Peter Blatherwick

"larry schessel" <lschesse at gmail.com>
Sent by: techwg-bounces at sipforum.org
11.05.07 10:38

        To:     techwg at sipforum.org, discussion at sipforum.org, "Dutkiewicz, 
Marek" <marek.dutkiewicz at polycom.com>, "Wesley. Hacker" 
<wesley at broadsoft.com>
        cc: 
        Subject:        [SIPForum-techwg] Request for Comments - 
Preliminary Feature Set Document

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.

<sf-draft-twg-SIP_Phone_Interop_01.doc>

_______________________________________________
techwg mailing list
Send mail to: techwg at sipforum.org
Unsubscribe or edit options at:  
http://sipforum.org/mailman/listinfo/techwg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20070515/cb45bba1/attachment-0002.html>