RE: [Simple] RE: [Sip] draft-ietf-sip-events-04; Questions

Adam Roach <adam@dynamicsoft.com> Thu, 28 February 2002 17:02 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 MAA04393 for <sip-archive@odin.ietf.org>; Thu, 28 Feb 2002 12:02:15 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA14302 for sip-archive@odin.ietf.org; Thu, 28 Feb 2002 12:02:19 -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 LAA11003; Thu, 28 Feb 2002 11:33:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA10973 for <sip@optimus.ietf.org>; Thu, 28 Feb 2002 11:32:56 -0500 (EST)
Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02172 for <sip@ietf.org>; Thu, 28 Feb 2002 11:32:50 -0500 (EST)
Received: from DYN-VA-EXCH-001.dynamicsoft.com (dyn-va-exch-001 [63.114.208.70]) by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g1SGU9Zq029508; Thu, 28 Feb 2002 11:30:10 -0500 (EST)
Received: by DYN-VA-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2650.21) id <14NNGK5V>; Thu, 28 Feb 2002 11:32:15 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F36300B6@DYN-TX-EXCH-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Chiou, Mark'" <MChiou@santera.com>, sip@ietf.org
Cc: simple@mailman.dynamicsoft.com
Subject: RE: [Simple] RE: [Sip] draft-ietf-sip-events-04; Questions
Date: Thu, 28 Feb 2002 11:32:14 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
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

> -----Original Message-----
> From: Chiou, Mark [mailto:MChiou@Santera.com]
> 
> 1. Why the Contact header is mandatory for SUBSCRIBER and 
> NOTIFY? If the Contact is not applicable to these methods, 
> then "-" should be applied to R, 1xx, 2xx, 3xx, and 485.

Contact headers form an important part of the route. This
behavior mirrors that of the bis draft.

> 2. I don't think 3xx is applicable to these two methods, such 
> that contact 3xx should have "-" instead of "o".

3xx responses are applicable to all methods, and there's nothing
that an extension can do about it. Redirect servers will always
redirect unknown methods.

I could also argue that 3xx responses can be quite useful
for SUBSCRIBE, with some fairly compelling examples, but
the above fact makes it a rather moot point.

/a

_______________________________________________
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