IETF Logo Mail Archive

RE: [Sip] FW: Submission: draft-ietf-sip-refer-01.txt

"Sriram Parameswar" <sriramp@nortelnetworks.com> Mon, 10 September 2001 21:24 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 RAA02233 for <sip-archive@odin.ietf.org>; Mon, 10 Sep 2001 17:24:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19315; Mon, 10 Sep 2001 17:05:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19284 for <sip@optimus.ietf.org>; Mon, 10 Sep 2001 17:05:20 -0400 (EDT)
Received: from zrc2s03g.us.nortel.com (zrc2s03g.nortelnetworks.com [47.103.122.66]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01615 for <sip@ietf.org>; Mon, 10 Sep 2001 17:03:49 -0400 (EDT)
Received: from smtprch1.nortel.com (erchg0j.us.nortel.com [47.113.64.103]) by zrc2s03g.us.nortel.com (8.9.3+Sun/8.9.1) with ESMTP id QAA02624 for <sip@ietf.org>; Mon, 10 Sep 2001 16:04:48 -0500 (CDT)
Received: from zrchb200.us.nortel.com by smtprch1.nortel.com; Mon, 10 Sep 2001 16:03:35 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) id <SK3LJN51>; Mon, 10 Sep 2001 16:03:34 -0500
Message-ID: <9A9367D1556AD21182C40000F80930AB04411DAB@crchy28b.us.nortel.com>
From: Sriram Parameswar <sriramp@nortelnetworks.com>
To: 'Robert Sparks' <rsparks@dynamicsoft.com>, "'sip@ietf.org'" <sip@ietf.org>
Subject: RE: [Sip] FW: Submission: draft-ietf-sip-refer-01.txt
Date: Mon, 10 Sep 2001 16:03:24 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C13A3C.079D4280"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org

Robert:

Quick question - in section 3.6.2.2 you say --> Each NOTIFY MUST contain a
body of type "message/sipfrag".

My question if (ignoring the obvious security problems) a UA wants it may
copy the entire SIP message into the NOTIFY and use "message/sip", this
seems to be disallowed or am I reading it wrong?

For the usage of RPI will you be adding more into this document either by
way of requirements or examples, or simply referring back to the privacy
document?

Thanks,

Sriram

__________________________________________
Sriram Parameswar              Phone: 972-685-8540
Interactive Multimedia Server (IMS) Fax: 972-685-3563
Nortel Networks, Richardson USA  Email: sriramp@nortelnetworks.com


-----Original Message-----
From: Robert Sparks [mailto:rsparks@dynamicsoft.com]
Sent: Tuesday, September 04, 2001 2:59 PM
To: 'sip@ietf.org'
Subject: [Sip] FW: Submission: draft-ietf-sip-refer-01.txt


I've submitted an update to the refer draft reflecting
the directions discussed at IETF 51.

Until it appears in the repository, the document is available at
http://www.nostrum.com/~rjsparks/draft-ietf-sip-refer-01.txt 

_______________________________________________
Sip mailing list  http://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

v2.23.0 | Report a Bug | By Email