Re: [Sipping] I-D Action:draft-ietf-sipping-service-examples-15.txt

"Hutton, Andrew" <andrew.hutton@siemens.com> Tue, 15 July 2008 08:23 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C5EEA3A6B4C; Tue, 15 Jul 2008 01:23:46 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86C6828C2FA for <sipping@core3.amsl.com>; Tue, 15 Jul 2008 01:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_18=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lRyLnnIXSTgI for <sipping@core3.amsl.com>; Tue, 15 Jul 2008 01:23:44 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id A34A23A6AF5 for <sipping@ietf.org>; Tue, 15 Jul 2008 01:23:44 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0K4100814GO93V@siemenscomms.co.uk> for sipping@ietf.org; Tue, 15 Jul 2008 09:24:11 +0100 (BST)
Date: Tue, 15 Jul 2008 09:24:05 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens.com>
In-reply-to: <20080711183001.33A3128C1FC@core3.amsl.com>
To: sipping@ietf.org
Message-id: <719F9BBB3E7E71428A2D13F3D76C768FD9C9E5@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sipping] I-D Action:draft-ietf-sipping-service-examples-15.txt
Thread-Index: AcjjhIS2gNrQmk4oSb62mnrl8/y0tgCzhIbg
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <20080711183001.33A3128C1FC@core3.amsl.com>
Subject: Re: [Sipping] I-D Action:draft-ietf-sipping-service-examples-15.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

 
This new draft still includes the following text in section 2.1 (Call
Hold).

"However, a UA that places the other party on hold will generally also
stop sending media, resulting in no media exchange between the UAs.
Older UAs may set the connection address to 0.0.0.0 when initiating
hold.  However, this behavior has been deprecated in favor of using the
a=sendonly SDP attribute."

The problem with this statement it indicates that a UA that stops
sending media when placing a call on hold should use the a=sendonly SDP
attribute which is incorrect. If a UA does not wish to send or receive
media then it should use the a=inactive attribute. A UA can use
a=sendonly for call hold but not in the case when it stops sending
media. I would really like to see the draft updated to fix this and
state that a=inactive is the attribute to use when the UA stops sending
media.

Regards
Andy




-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Internet-Drafts@ietf.org
Sent: 11 July 2008 19:30
To: i-d-announce@ietf.org
Cc: sipping@ietf.org
Subject: [Sipping] I-D Action:draft-ietf-sipping-service-examples-15.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Session Initiation Proposal
Investigation Working Group of the IETF.


	Title           : Session Initiation Protocol Service Examples
	Author(s)       : A. Johnston, et al.
	Filename        : draft-ietf-sipping-service-examples-15.txt
	Pages           : 167
	Date            : 2008-07-11

This document gives examples of Session Initiation Protocol (SIP)
services.  This covers most features offered in so-called IP Centrex
offerings from local exchange carriers and PBX (Private Branch
Exchange) features.  Most of the services shown in this document are
implemented in the SIP User Agents, although some require the
assistance of a SIP Proxy.  Some require some extensions to SIP
including the REFER, SUBSCRIBE, and NOTIFY methods and the Replaces
and Join header fields.  These features are not intended to be an
exhaustive set, but rather show implementations of common features
likely to be implemented on SIP IP telephones in a business
environment.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples-
15.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP