Re: O/A model

Isn't there a mechanism whereby both UAs get back to an agreed 
state? How can the negotiation process continue properly 
otherwise?

regards,
Salva

On 10 Apr 2002, at 0:43, Jonathan Rosenberg wrote:

> THe spec does not detail error handling for the infinite different ways
> in which they might occur. The choice is at the discretion of the
> implementation.
> 
> -Jonathan R.
> 
> Salva Rey Calatayud wrote:
> > 
> > Hi,
> > 
> >         how should a UA act when let's say the other endpoint doesn't
> > behave compliantly to the O/A exchange model. For instance, we
> > send an offer, and none of the associated messages that could
> > contain an answer does (an UPDATE with a 200OK without
> > answer, INVITE with offer and none of the provisional response nor
> > final 200OK contain an answer )
> > 
> > thanks,
> > Salva
> > 

SIP O/A model

Isn't there a mechanism whereby both UAs get back to an agreed 
state? How can the negotiation process continue properly 
otherwise?

regards,
Salva

On 10 Apr 2002, at 0:43, Jonathan Rosenberg wrote:

> THe spec does not detail error handling for the infinite different 
ways
> in which they might occur. The choice is at the discretion of the
> implementation.
> 
> -Jonathan R.
> 
> Salva Rey Calatayud wrote:
> > 
> > Hi,
> > 
> >         how should a UA act when let's say the other endpoint 
doesn't
> > behave compliantly to the O/A exchange model. For instance, 
we
> > send an offer, and none of the associated messages that could
> > contain an answer does (an UPDATE with a 200OK without
> > answer, INVITE with offer and none of the provisional response 
nor
> > final 200OK contain an answer )
> > 

manyfolks

Hi Gonzalo,

	This is Salva Rey, from Siemens CT in Munich. How are you 
doing?

	I wanted to comment you a couple of things about manyfolks.

	For what I see in manyfolks it seems that two aspects are 
being defined jointly:

	1. QoS capability exchange signalling and interaction with the 
offer/answer model(through methods and headers)	

	2. QoS requirements (in SDP fields)

	Point #1 will be always managed by the UA, but maybe #2 is 
let to the application...

	this has never been mentioned, but are we aware of this?
	will manyfolks provide any support for QoS capability exchange 
signalling in case that the format for media stream descriptor is 
other than sdp, let's say here sdpng or xml?

	my concern is that maybe these two aspects are woven too 
tightly, and later on manyfolks cannot be used if a format different 
to sdp is used.

regards,
Salva

dialog identifiers