[Sipping] SIP Device Configuration and RESCAP
Richard Shockey <rich.shockey@neustar.com> Tue, 26 March 2002 13:37 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02117 for <sipping-archive@odin.ietf.org>; Tue, 26 Mar 2002 08:37:49 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id IAA16792 for sipping-archive@odin.ietf.org; Tue, 26 Mar 2002 08:37:50 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA10395; Tue, 26 Mar 2002 08:14:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA09962 for <sipping@optimus.ietf.org>; Mon, 25 Mar 2002 17:20:19 -0500 (EST)
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06108 for <sipping@ietf.org>; Mon, 25 Mar 2002 17:20:16 -0500 (EST)
Received: from dick.neustar.com (stih650b-s1p2.va.neustar.com [209.173.53.65]) by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g2PMJm828465 for <sipping@ietf.org>; Mon, 25 Mar 2002 17:19:48 -0500
Message-Id: <5.1.0.14.2.20020325161945.024bd480@popd.ix.netcom.com>
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 25 Mar 2002 17:23:05 -0500
To: sipping@ietf.org
From: Richard Shockey <rich.shockey@neustar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [Sipping] SIP Device Configuration and RESCAP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
I know this was a rather contentious issue at the 2nd SIPPING meeting but I'd like this group to at least be aware of some similar work that we have tried for years to move on in the IETF and I like to take this opportunity to add the pointers to the current RESCAP work. http://www.ietf.org/html.charters/rescap-charter.html A cursory overview of the RESCAP charter should identify similarities between the Petrie SIP Device Configuration draft and the general problem statement. RESCAP originally looked at the problem of identifying the capabilities of a POP3 or IMAP end points by an SMTP client. Unified Messaging and other technologies essentially have to "send and pray" that the end point recipient user agent was capable of processing the attachments. The desire was to avoid circumstances where one would send PPT files to a hand held cellphone etc...hense the need for a combination of technologies that could, discover a configuration file or capabilities "object" of the terminating email endpoint. Upon discovery of the end point capabilities, the message object could be re configured or rejected by the originating client as appropriate. Its rather easy to see how RESCAP concepts or a similar class of technologies could be applied to the originating endpoint, in this case a SIP Device. The data object (configuration file) could use a different form of semantic than capabilities ..but the two could share many attributes such as discovery and transport. I'm not suggesting this is the exact methodology SIPPING needs to look at, however the general problem statement is one that is well known in the IETF community. ############ A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Resource Capabilities Discovery Working Group of the IETF. Title : RESCAP Scenarios Author(s) : G. Klyne Filename : draft-ietf-rescap-scenarios-01.txt Pages : 18 Date : 11-Jan-02 This memo explores some scenarios for the resource capabaility discovery protocol (RESCAP). It is intended to provide some grounding in specific use-cases for decisions about RESCAP goals and design. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rescap-scenarios-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Resource Capabilities Discovery Working Group of the IETF. Title : The Binary Low-Overhead Block Presentation Protocol Author(s) : K. Moore Filename : draft-ietf-rescap-blob-01.txt Pages : 22 Date : 05-Mar-02 This memo describes the Binary Low-Overhead Block (BLOB) protocol for on-the-wire presentation of data in the context of higher-level protocols. BLOB is designed to encode and decode data with low overhead on most CPUs, to be reasonably space-efficient, and for its representation to be sufficiently precise that it is suitable as a canonical format for digital signatures A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rescap-blob-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Resource Capabilities Discovery Working Group of the IETF. Title : The Resource Catalog Author(s) : K. Moore Filename : draft-ietf-rescap-rc-01.txt Pages : 34 Date : 05-Mar-02 This memo describes version 3 of the Resource Catalog. The Resource Catalog (RC) is a service for storing and obtaining metadata that describes network-accessible resources. This service is primarily intended for use by clients prior to accessing, or attempting to access, a particular resource. The RC service may thus be used (for example) to inform a client as to which of a variety of features are supported by the resource, or which methods may be used to access the resource, or which of a small set of locations may be used to access the resource. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rescap-rc-01.txt >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 45980 Center Oak Plaza Bldg 8 Sterling, VA 20166 1120 Vermont Ave NW Suite 400 Washington DC 20005 Voice +1 571.434.5651 Cell : +1 314.503.0640, Fax: +1 815.333.1237 <mailto: rshockey@ix.netcom.com> or <mailto: rich.shockey@neustar.biz> <http://www.neustar.biz> <http://www.enum.org> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ Sipping mailing list https://www1.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] SIP Device Configuration and RESCAP Richard Shockey
- Re: [Sipping] SIP Device Configuration and RESCAP Henning Schulzrinne
- RE: [Sipping] SIP Device Configuration and RESCAP Blatherwick, Peter