[Rest] More comments (RE: intiial rough draft)

[Simo.Veikkolainen at nokia.com]

Hi Theo,

I went through the draft in a bit more detail and found some things to comment. We are already past the submission deadline but I'm sure there will be a subsequent version.

7.1: OPEN-ISSUE: These need precedence for the case of multiple matches;
   Which take priority? (the above seems to make sense to me)

(1) (all) needs to be executed at first. (2) (busy) is when one contact returns 603, or all of them return 486. CF No Answer is the timer expiration before 200 OK or busy or unreachable event. (3) unreachable is any other error from all contacts, except 488 with SDP or 3xx, which need to be returned transparantly to caller.

7.1.2: OPEN-ISSUE: does this apply to 3xx?

No, it does not, 3xx should be carried back to the caller, since it contains a new contact address. The same goes for 488 when it contains supported codecs, these should be carried to the caller.

7.1.3:  This class applies when bindings are available, but each returned a
   486 or 600 response code.

603 should stop forking even when returned from a single contact.  Otherwise the end user would need to press the red button from all devices to stop them ringing, which may not be very convinient :)

7.2 timeout is missing from the parameters (it is described in 7.2.3)


An additional feature we might want to have is querying all settings at once. We would need to define a resource for this, which could be queried by sending a GET to that resource.

Simo

>-----Original Message-----
>From: rest-bounces at bliss-ietf.org 
>[mailto:rest-bounces at bliss-ietf.org] On Behalf Of ext Theo 
>Zourzouvillys
>Sent: 02 March, 2009 20:44
>To: rest at bliss-ietf.org
>Subject: [Rest] intiial rough draft
>
>So turned out my weekend was more exciting than i thought it 
>was goign to be, and have only just managed to get around to 
>it.  Good thing deadline isn''t until weds now :-)
>
>Please take a look at ...
>
>  
><http://dev.voip.co.uk/~theo/ietf/draft-zourzouvillys-bliss-ach
-http-api-00.txt>
>
>... and get some discussion going on it.
>
>I hope there is enough text (and typos) in there to get people 
>to understand what i'm trying to document - although if anyone 
>has any other ideas i'm all up for them instead!
>
>I'll wait for some feedback (and questions, which i'll answer) 
>before fleshing it up and actually making it more spec-like :)
>
>I'm in meetings most the day tomorrow but will be able to 
>spend more time on it in the evening (GMT).
>
> ~ Theo
>
>_______________________________________________
>Rest mailing list
>Rest at bliss-ietf.org
>http://bliss-ietf.org/mailman/listinfo/rest_bliss-ietf.org
>