Re: [Sip] draft-ietf-sip-rfc2543bis-09 and the offer/answer model
Jonathan Rosenberg <jdrosen@dynamicsoft.com> Tue, 18 June 2002 22:15 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 SAA06602 for <sip-archive@odin.ietf.org>; Tue, 18 Jun 2002 18:15:59 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id SAA19518 for sip-archive@odin.ietf.org; Tue, 18 Jun 2002 18:16:39 -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 RAA17988; Tue, 18 Jun 2002 17:58:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA17959 for <sip@optimus.ietf.org>; Tue, 18 Jun 2002 17:58:18 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06303 for <sip@ietf.org>; Tue, 18 Jun 2002 17:57:37 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.125]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g5ILvhYH016863; Tue, 18 Jun 2002 17:57:43 -0400 (EDT)
Message-ID: <3D0FACD3.6050702@dynamicsoft.com>
Date: Tue, 18 Jun 2002 17:57:39 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: frank.derks@philips.com
CC: sip@ietf.org
Subject: Re: [Sip] draft-ietf-sip-rfc2543bis-09 and the offer/answer model
References: <OFDD77E0C2.2DFDFE3E-ONC1256BD4.00266186@diamond.philips.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit
frank.derks@philips.com wrote: > The latest version of the SIP draft contains the following text: > > "The offer/answer model defines restrictions on when offers and answers > can be made. This results in restrictions on where the offers and > answers can appear in SIP messages. In this specification, offers and > answers can only appear in INVITE requests and responses, and ACK. The > usage of offers and answers is further restricted." > > The first sentence states that the offer/answer model defines when > offers > and answers can be made. From draft-ietf-mmusic-sdp-offer-answer-02, it > does not really become clear that this is the case. Which restrictions > are being referred to? Its referring to this paragraph: At any time, either agent MAY generate a new offer that updates the session. However, it MUST NOT generate a new offer if it has received an offer which it has not yet answered or rejected. Furthermore, it MUST NOT generate a new offer if it has generated a prior offer for which it has not yet received an answer or a rejection. If an agent receives an offer after having sent one, but before receiving an answer to it, this is considered a "glare" condition. -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PH: (973) 952-5000 http://www.dynamicsoft.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
- [Sip] draft-ietf-sip-rfc2543bis-09 and the offer/… frank.derks
- Re: [Sip] draft-ietf-sip-rfc2543bis-09 and the of… Jonathan Rosenberg