[Rest] intiial rough draft

[Theo Zourzouvillys]

On Tue, Mar 3, 2009 at 7:44 AM, Sanjay Sinha (sanjsinh)
<sanjsinh at cisco.com> wrote:
> I had one question about usage of term HTTP API throughout this
> document. Is that because we are trying to find a middle ground between
> REST and XCAP. I was thinking that the draft will mention that it uses
> REST methodology for configuring (enabling/disabling/querying)  ACH
> features mentioned in it. I know REST implementations are based on HTTP,
> but non-mention of REST looks stands out.

Christian's update to an extent has fixed this, although i'll also
update the introduction and abstract to reflect this.


> Sec. 6.0: Configuration Scope  - You have mentioned that setting applies
> to AOR and not individual bindings. If I have a desk phone and a
> cellphone both related to my AOR and they register with their own
> Contact addresses to the registrar. If I fwd my desk phone to cell
> phone, so because of AOR binding, the cell phone also gets fwded to
> itself. Is that a valid understanding of the AOR binding scope mentioned
> here.

Yes it is, and imo a "known issue".  However, fixing this in the -00
or -01 will open up a can of worms we don't have time to deal with
before cut-off, and is certainly something worth more discussion.

> Call Waiting was also in the use case email Shida sent and it is not
> there in this initial version.
>
> Call Forwarding All is same as Call Forwarding Unconditional, correct. I
> think it should be worth mentioning it.

done!

would people prefer i changed the path node 'all' to 'unconditional' ?


> Some nits:
>
> 7.2.1 Should read: "This setting, which must be a valid URI, is the
> target of the new SIP request"
> 7.2.3: Typo: seconds
>

fixed!

 ~ tHeo