Re: CAP-12 - interm version 'E'

Harrie Hazewinkel wrote:

> 1)
> Why is the BEEP profile defined in this draft. Would it not be better
> to separate it?
> Maybe it is also useful advancement of the standard. 

There was  a decision to use BEEP.

In order for a protocol to use BEEP it requires that the protocol define
the BEEP profile. I do not think we can separate them.

>
> 2)
> Section 1.2, Related documents could be a bit extended in explaining
> the way this draft uses those other RFCs. Now they just specify what
> they are. 

Trying to explain without repeating or accidentally redefining text is
difficult. [GUIDE] ties them together.


> 3) The first definition of section 1.3 seems od to me. The definition
> is "BOOKED", but than it is actually a state which may have three
> values, "UNPROCESSED", "BOOKED", "DELETED". IMHO, on should define
> the definition state. 

An object has 3 states, one of which is booked. I'll update the text to be
more clear.

> 4)
> Calendar Store Identifier (CSID) is defined by
> 'A CSID consists of the host and port portions of a "Common Internet
> Scheme Syntax" part of a URL, as defined by [URL]'
> However, section 8.9 has in the example also the scheme (protocol) part. 

I'll update the text to say and the scheme is included as ....

>
>
> This looks to me a mixture with Calendar Identifier (CALID) that
> start with "cap:". With respect the the "cap:" part we are aware that
> then CAP is the only method to access a calendar. Not like 'ftp' and 
> 'http'
> that are different protocols but could access the same resource. 

I do not follow your point.

>
>
> 5) NIT
> The reference of the RFCs have a URL not of http://www.ietf.org/rfc/
> I am not fully sure what IETF policy is here. 

-- 

 Doug Royer                     |   http://INET-Consulting.com 
 -------------------------------|-----------------------------
 [email protected]                 | Office: (208)612-INET
 http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                |   Cell: (208)520-4044

                We Do Standards - You Need Standards