Re: [Sip] Some Comments: WGLC of draft-ietf-sip-hitchhikers-guide-03
Jonathan Rosenberg <jdrosen@cisco.com> Wed, 14 November 2007 23:22 UTC
Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsRYc-0007jD-GF; Wed, 14 Nov 2007 18:22:06 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IsRYY-0007bm-Ha for sip-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 18:22:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsRYX-0007aa-Tr for sip@ietf.org; Wed, 14 Nov 2007 18:22:02 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IsRYU-0004mj-5o for sip@ietf.org; Wed, 14 Nov 2007 18:22:01 -0500
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 14 Nov 2007 15:21:57 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lAENLvOf030259; Wed, 14 Nov 2007 15:21:57 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lAENLhEG023915; Wed, 14 Nov 2007 23:21:57 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Nov 2007 15:21:47 -0800
Received: from [10.32.241.148] ([10.32.241.148]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Nov 2007 15:21:46 -0800
Message-ID: <473B8329.2040705@cisco.com>
Date: Wed, 14 Nov 2007 18:22:17 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mary Barnes <mary.barnes@nortel.com>
Subject: Re: [Sip] Some Comments: WGLC of draft-ietf-sip-hitchhikers-guide-03
References: <F66D7286825402429571678A16C2F5EE10EE68@zrc2hxm1.corp.nortel.com> <1ECE0EB50388174790F9694F77522CCF12BCA8CD@zrc2hxm0.corp.nortel.com> <F66D7286825402429571678A16C2F5EE10EE6D@zrc2hxm1.corp.nortel.com>
In-Reply-To: <F66D7286825402429571678A16C2F5EE10EE6D@zrc2hxm1.corp.nortel.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Nov 2007 23:21:46.0435 (UTC) FILETIME=[1FFA4130:01C82715]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3554; t=1195082517; x=1195946517; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com> |Subject:=20Re=3A=20[Sip]=20Some=20Comments=3A=20WGLC=20of=20draft-ietf-s ip-hitchhikers-guide-03 |Sender:=20; bh=t6O1lS7r5RrhDo9fblk3JZIG0GenZV2QDtOnFUKSq50=; b=L1Go1kBTQZadrOydejCDm+39P1/MOFosIxiDcELccLTOXWH5F1gwm8W0ISEd8Q8oiXSpK3Qz hMRoFkiPRZ6DIZiY1cP6lmk3WVxTOISglCL5CPM4L7ptzw/uBq1OH7vKn5u6kYQdO6OpoykO/f spMRUpEI7QkMOqPo130jWLkQw=;
Authentication-Results: sj-dkim-1; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>, "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org
OK, I took this wording. RFC 4588 got added also per other comments, and appears in the service URI section. -Jonathan R. Mary Barnes wrote: > I like the suggested rewording for RFC 4244 and agree that RFC 4458 > would fit well in the Service URI section. > > Mary. > > -----Original Message----- > From: Audet, Francois (SC100:3055) > Sent: Wednesday, October 24, 2007 6:35 PM > To: Barnes, Mary (RICH2:AR00); Jonathan Rosenberg > Cc: sip@ietf.org; DRAGE, Keith (Keith) > Subject: RE: [Sip] Some Comments: WGLC of > draft-ietf-sip-hitchhikers-guide-03 > > Mary has a good point, but I think an even simpler solution is the > following: > > NEW: > > RFC 4244, An Extension to SIP for Request History Information (S): > RFC 4244 [37] defines the History-Info header field, which > indicates information on how and why a call came to be routed to > a > particular destination. > > As for RFC 4458, I think it belongs int the "SIP Service URIs" section > and maybe the PSTN interop one (it's really a form of RFC 3087 service > URI for PSTN interop). > >> -----Original Message----- >> From: Barnes, Mary (RICH2:AR00) >> Sent: Wednesday, October 24, 2007 08:20 >> To: Jonathan Rosenberg >> Cc: sip@ietf.org; DRAGE, Keith (Keith) >> Subject: [Sip] Some Comments: WGLC of >> draft-ietf-sip-hitchhikers-guide-03 >> >> >> Following Keith's recommendation for us to at least review the entries > >> for the RFCs that we authored, I have some feedback on the entry for >> RFC >> 4244 (History-Info) and a few other comments. >> >> RFC 4244 comments (Section 5): >> ------------------------------ >> The statement about the primary application being voicemail is a >> mis-characterization and is based on the fact that we had so, so many >> long, long discussions on the use of History-Info for voicemail. RFC >> 4244 is written to provide a very general mechanism and is applicable >> to a variety of applications. My concern is that mis-characterization >> may result in folks trying to define something new when the capability > >> already exists with History-Info (e.g., 3GPP p-served-user p-header). >> So, I suggest something like the following change: >> >> OLD: >> RFC 4244, An Extension to SIP for Request History Information (S): >> RFC 4244 [37] defines the History-Info header field, which >> indicates information on how a call came to be routed to a >> particular destination. Its primary application was in support >> of >> voicemail services. >> >> NEW: >> RFC 4244, An Extension to SIP for Request History Information (S): >> RFC 4244 [37] defines the History-Info header field, which >> indicates information on how and why a call came to be routed to > >> a >> particular destination. One application was in support of >> voicemail services, with details of such provided in RFC 4458. >> Other example applications include Automatic Call Distribution >> and Call Transfer scenarios. >> >> And, this of course, adds a reference to RFC 4458. I don't have a >> strong opinion as to whether detail on that RFC shouldn't be included >> elsewhere >> in this document. > -- Jonathan D. Rosenberg, Ph.D. 499 Thornall St. Cisco Fellow Edison, NJ 08837 Cisco, Voice Technology Group jdrosen@cisco.com http://www.jdrosen.net PHONE: (408) 902-3084 http://www.cisco.com _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- RE: [Sip] Some Comments: WGLC of draft-ietf-sip-h… Mary Barnes
- RE: [Sip] Some Comments: WGLC of draft-ietf-sip-h… Francois Audet
- [Sip] Some Comments: WGLC of draft-ietf-sip-hitch… Mary Barnes
- Re: [Sip] Some Comments: WGLC of draft-ietf-sip-h… Jonathan Rosenberg