Re: [decade] Review of draft-ietf-decade-reqs-08

[Songhaibin <[e-mail]>]

Hi Kostas and Akbar,

Thank you for the good comments and discussion.

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of
> Konstantinos Pentikousis
> Sent: Tuesday, September 04, 2012 12:43 AM
> To: Rahman, Akbar
> Cc: [e-mail]
> Subject: Re: [decade] Review of draft-ietf-decade-reqs-08
> 
> Hi Akbar,
> 
>   |Thanks, your comments and analysis are always very thought provoking!
> 
> Thank you for your kind words.
> 
> <snip>
> 
>   |In a DECADE system, efficient storage and data transfer of small data
>   |objects is required [5.3].
>   |
>   |[AKBAR] AND WE SHOULD ADD THE PHRASE "... AND DATA TRANSFER OF
> LARGE
>   |DATA OBJECTS IS ALSO INHERENTLY SUPPORTED."
> 
> Sure, I guess this goes into the text of [5.3] then.
> 
> 
>   |The data transport protocol can be negotiated but must be secure [7.1,
>   |7.3].
>   |
>   |
>   |[AKBAR] AND I WOULD ADD TWO MORE POINTS APPLICABLE TO THE NEXT
>   |PARAGRAPH:
>   |- ALL CONTROL FUNCTIONS ARE ACCOMPLISHED USING THE DECADE
> RESOURCE
>   |PROTOCOL (DRP)
> 
> I understand what you have in mind, but it will be a bit strange to put, let me call
> it, a "forward reference" to a protocol that does not exist. Just my $0.02.

As long as the explanation for DRP exists in the document, I do not think this is a problem.

-Haibin

> 
>   |Security is based on cryptographic methods which allow a DECADE
>   |provider to access system resources, distribute content to content
>   |consumers of its choosing, even when offline, using (if needed) fine-
>   |grained access control policies [6.2, 6.3, 6.4, 6.5, 6.6, 8.2, 8.3].
>   |Client data on a server are by default private [6.7]. It is the client
>   |that always discovers and initiates a connection to a server [6.8,
>   |6.9], not vice versa. Data objects can be written by a provider in one
>   |go or several rounds and can be read by multiple consumers
>   |simultaneously [7.2, 7.4]. Every provider is given the means to obtain
>   |resource usage stats and quotas [10.1]. Overall, attack mitigation is
>   |a MUST [9.5] and transport redirection SHOULD be supported [7.7]
>   |
>   |[AKBAR] IN THE EXPLANATION YOU SWITCH TERMS BETWEEN "PROVIDER"
> AND
>   |"CLIENT".  IT WOULD BE CLEARER I THINK IF YOU STUCK TO JUST "PROVIDER"
>   |AND "CONSUMER".
> 
> Well, I agree that a few terms in sec 2.* have some overlap and perhaps could be
> simplified a bit, but I tried to have the cheat sheet summary as close as possible
> to the definitions in Sec 2.* and the -reqs text. For example, in 6.7 (copy and
> paste):
> 
> REQUIREMENT(S): Unless read or write access is granted by a Provider, the
> default permission MUST be no access.
> RATIONALE: This requirement is to protect client privacy by default.
> 
> I guess that means s/client/provider in the rationale part, and the cheat sheet
> summary becomes "Provider data on a server are by default private [6.7]"
> 
> On the other hand, in the sentence "It is the client... [6.8, 6.9]", "client" (as per
> sec. 2.1) is the right term, not "provider".
> 
> Best regards,
> 
> Kostas