Re: [Sipping] I-D Action:draft-ietf-sipping-service-examples-15.txt
Paul Kyzivat <pkyzivat@cisco.com> Tue, 15 July 2008 15:55 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 3C9E928C12F; Tue, 15 Jul 2008 08:55:17 -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 CA72528C123 for <sipping@core3.amsl.com>; Tue, 15 Jul 2008 08:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.278
X-Spam-Level:
X-Spam-Status: No, score=-6.278 tagged_above=-999 required=5 tests=[AWL=-0.279, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_MED=-4]
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 qn0LGCTtN2Cj for <sipping@core3.amsl.com>; Tue, 15 Jul 2008 08:55:15 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 9003E28C12F for <sipping@ietf.org>; Tue, 15 Jul 2008 08:55:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.30,367,1212364800"; d="scan'208";a="14377567"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 15 Jul 2008 15:55:43 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m6FFtgnZ004260; Tue, 15 Jul 2008 11:55:42 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m6FFtgW6017273; Tue, 15 Jul 2008 15:55:42 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 15 Jul 2008 11:55:42 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 15 Jul 2008 11:55:42 -0400
Message-ID: <487CC8B3.1010508@cisco.com>
Date: Tue, 15 Jul 2008 11:56:35 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Alan Johnston <alan@sipstation.com>
References: <20080711183001.33A3128C1FC@core3.amsl.com> <719F9BBB3E7E71428A2D13F3D76C768FD9C9E5@GBNTHT12009MSX.gb002.siemens.net> <487CC4D8.5080404@cisco.com> <487CC5E4.7080205@sipstation.com>
In-Reply-To: <487CC5E4.7080205@sipstation.com>
X-OriginalArrivalTime: 15 Jul 2008 15:55:42.0500 (UTC) FILETIME=[3C38DE40:01C8E693]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4238; t=1216137343; x=1217001343; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sipping]=20I-D=20Action=3Adraft-ietf-s ipping-service-examples-15.txt |Sender:=20 |To:=20Alan=20Johnston=20<alan@sipstation.com>; bh=9Iv3hW4hjU0ETMYqokdU80oYa3o9pgdvKyMLXo5U7eI=; b=L1L2TxMiN3lbu6jLR27KgudEEdNBiAsKfS4YnLJ47rKWPeLROhJqOl9JPv GSGB8L41bPNTsUEUIxoXIxlBPGy/zF5a2vd6DxOtNlwAospvE/3FVl201TZn eHyvKhNIcC;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: sipping@ietf.org, "Hutton, Andrew" <andrew.hutton@siemens.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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
sounds good! Thanks, Paul Alan Johnston wrote: > I can fix in Author's 48 hours as this should be the last version before > protocol action. > > Thanks, > Alan > > Paul Kyzivat wrote: >> I agree with Andy here. A lot of people seem to think that you must >> use sendonly for hold - that inactive is inappropriate. But that is >> silly. Of course if you really want to you can negotiate sendonly and >> then not send anything. But IMO that shouldn't be held out as best >> practice. Doing so encourages people to build UAs that don't work when >> offered a=inactive. >> >> Thanks, >> Paul >> >> Hutton, Andrew wrote: >>> >>> 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 >>> >> _______________________________________________ >> 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 >> >> > > _______________________________________________ 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
- [Sipping] I-D Action:draft-ietf-sipping-service-e… Internet-Drafts
- Re: [Sipping] I-D Action:draft-ietf-sipping-servi… Hutton, Andrew
- Re: [Sipping] I-D Action:draft-ietf-sipping-servi… Paul Kyzivat
- Re: [Sipping] I-D Action:draft-ietf-sipping-servi… Alan Johnston
- Re: [Sipping] I-D Action:draft-ietf-sipping-servi… Paul Kyzivat