Re: [Ace] ACE Use Case document

--
Jong-Hyouk Lee, living somewhere between /dev/null and /dev/random
Protocol Engineering Lab., Sangmyung University

#email: jonghyouk@gmail.com
#webpage: https://sites.google.com/site/hurryon

On Aug 26, 2014, at 4:37 PM, Kumar, Sandeep <sandeep.kumar@philips.com> wrote:

> The call for adoption is only to make this a WG document so that folks can contribute to a single document. The document can only get broader with consensus if it is a WG document.

I do not think so. When an individual document has enough supports for adoption, the document can be a WG document. Not necessary, first adopted and then improved. In other words, I do not think that the current document is matured enough for calling the adoption.

> Do you think there are issues in the current use cases that should be removed?

As stated in the abstract, the use-cases document is intended to be a guideline for developing a comprehensive authentication and access control approach while deriving security requirements. However, what I concern from the current document is possibilities of lacking of deriving security requirements from the limited use-cases in the document. 

In addition, I would like to see the document’s improvement in its organisation and structure. For instance, it must help if the document contains a table showing comparisons of the use-cases listed in the document in terms of environment (network, protocol, etc) and security requirement.

J. 

> 
> Sandeep
> 
> -----Original Message-----
> From: Ace [mailto:ace-bounces@ietf.org] On Behalf Of Jong-Hyouk Lee
> Sent: Tuesday, August 26, 2014 9:12 AM
> To: Anthony Nadalin
> Cc: Hannes Tschofenig; Ace@ietf.org
> Subject: Re: [Ace] ACE Use Case document
> 
> Hi all
> 
> As like Anthony, I think that the use-cases document should be broader than the current one. The working group should try to get some more inputs from folks before trying to fire the call for adoption.
> 
> J.
> --
> Jong-Hyouk Lee, living somewhere between /dev/null and /dev/random Protocol Engineering Lab., Sangmyung University
> 
> #email: jonghyouk@gmail.com
> #webpage: https://sites.google.com/site/hurryon
> 
> On Aug 26, 2014, at 12:12 PM, Anthony Nadalin <tonynad@microsoft.com> wrote:
> 
>> My major issues and comments with the document is that it does not cover a lot of the use case that we see in the marketplace, the use case document can be broader than the scope of the WG (even though I don't see much in the charter that limits the scope).
>> 
>> -----Original Message-----
>> From: Ace [mailto:ace-bounces@ietf.org] On Behalf Of Hannes Tschofenig
>> Sent: Thursday, August 21, 2014 6:41 AM
>> To: Ace@ietf.org
>> Subject: [Ace] ACE Use Case document
>> 
>> Hi all,
>> 
>> we started a call for adoption of draft-seitz-ace-usecases as a starting point for the use case charter item in July and we were hoping to get a lot of feedback.
>> 
>> Unfortunately, it turned out that only very few responded, namely Robert, Michael, Peter, and Rene (whereby Rene voiced concerns).
>> 
>> Of course, you may have been on vacation and therefore unable to review the draft and to respond.
>> 
>> With the vacation period coming to an end we hope to receive additional feedback from other working group participants.
>> 
>> Ciao
>> Hannes & Kepeng
>> 
>> _______________________________________________
>> Ace mailing list
>> Ace@ietf.org
>> https://www.ietf.org/mailman/listinfo/ace
> 
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
> 
> ________________________________
> The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.