[Sipping] RE: [Sip] Requirements on Reason information. New I-D
"Eric Burger" <eburger@snowshore.com> Tue, 19 March 2002 15:54 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 KAA24957 for <sipping-archive@odin.ietf.org>; Tue, 19 Mar 2002 10:54:57 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA24986 for sipping-archive@odin.ietf.org; Tue, 19 Mar 2002 10:54:59 -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 KAA24125; Tue, 19 Mar 2002 10:37:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24065 for <sipping@ns.ietf.org>; Tue, 19 Mar 2002 10:37:15 -0500 (EST)
Received: from noc-e.ietf53.cw.net (noc-e.ietf53.cw.net [166.63.177.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24583; Tue, 19 Mar 2002 10:37:12 -0500 (EST)
Received: from eburger (eburger.ietf53.cw.net [166.63.183.156]) by noc-e.ietf53.cw.net (Postfix) with SMTP id 937CB6A919; Tue, 19 Mar 2002 09:37:14 -0600 (CST)
Reply-To: eburger@snowshore.com
From: Eric Burger <eburger@snowshore.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: SIP List <sip@ietf.org>, Sipping <sipping@ietf.org>
Date: Tue, 19 Mar 2002 10:36:55 -0500
Message-ID: <EEEDJPFPPHPFKDDLLMOKOEFADMAA.eburger@snowshore.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <3C96F057.6AE2D67@lmf.ericsson.se>
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sipping] RE: [Sip] Requirements on Reason information. New I-D
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
Content-Transfer-Encoding: 7bit
This is why we have SIPPING: the REASON header would be a sensible way of solving the issues raised by Gonzalo in his draft. In addition, it would, with some modifications, also solve the issues raised in draft-watson-sipping-req-history-00.txt. I would propose that the requirements raised in draft-camarillo-sipping-reason-00.txt get folded into a revision of draft-watson-sipping-req-history. Correct me if I'm wrong, but I don't think draft-schulzrinne-sip-reason-01.txt, as it stands today, addresses the history part of the SIPPING requirements. The draft is silent on this point, but it looks like the SIP entity generating the message with the Reason header inserts it only for *its* operation. That is, it explains why that particular entity failed. Said differently, it looks to me that there will be only one Reason header in a SIP message. If we can carry and identify the source of the Reason headers, like we do for Via or SMTP does for Received-By, then this header can satisfy both camarillo-sipping-reason's and watson-sipping-req-history's requirements. -----Original Message----- From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Gonzalo Camarillo Sent: Tuesday, March 19, 2002 3:01 AM To: sip; Brian Rosenberg (EUS); Dean Willis; Joerg Ott; rohan@cisco.com Cc: Henning Schulzrinne; oran@cisco.com Subject: [Sip] Requirements on Reason information. New I-D Chairmen, I presented the Reason header field draft today in the SIP WG meeting: http://search.ietf.org/internet-drafts/draft-schulzrinne-sip-reason-01.txt Some folks considered that the requirements for this work were not clear enough, so I was asked by the chairmen to write a set of requirements. We agreed that there was no need to wait for the next IETF meeting in order to progress such a requirements draft. Discussions in the mailing list were encouraged. I have put together an I-D with those requirements. http://standards.ericsson.net/gonzalo/draft-camarillo-sipping-reason-00.txt I would like to know if these requirements are what you expected or if, on the other hand, you wanted something else... I intend to submit this draft, including the comments I may receive, on Monday. Thanks, Gonzalo -- Gonzalo Camarillo Phone : +1 212 939 71 71 Columbia University Mobile: +358 40 702 35 35 472 Computer Science Building Fax : +358 9 299 30 52 1214 Amsterdam Ave., Mail Code 0401 http://www.hut.fi/~gonzalo New York, NY 10027 USA Gonzalo.Camarillo@ericsson.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 _______________________________________________ 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] RE: [Sip] Requirements on Reason inform… Eric Burger
- Re: [Sipping] RE: [Sip] Requirements on Reason in… Paul Kyzivat
- [Sipping] Re: [Sip] Requirements on Reason inform… Gonzalo Camarillo