[Ace] Fwd: New Version Notification for draft-ietf-ace-usecases-00.txt

[Ludwig Seitz <[e-mail]>]

Hello all,

I have just re-submitted draft-seitz-ace-usecases as 
draft-ietf-ace-usecases, as by the WG chair's instructions.

Currently the only change is one line added in the acknowledgments. 
However as was stressed in the ACE session at IETF 91, this doesn't mean 
we consider the document to be finished.

I encourage everyone to review the document and suggest changes and 
improvements, so that we can move forward with it quickly.

Perhaps the WG chairs can give the IETF newbies among us a short 
overview of how the document update procedure is going to be handled 
from now on?

Regards,

Ludwig


-------- Forwarded Message --------
Subject: New Version Notification for draft-ietf-ace-usecases-00.txt
Date: Thu, 04 Dec 2014 05:56:11 -0800
From: [e-mail]
To: Mehdi Mani <[e-mail]>, Sandeep Kumar 
<[e-mail]>, Goeran Selander 
<[e-mail]>, Sandeep S. Kumar 
<[e-mail]>, Ludwig Seitz <[e-mail]>, Goran 
Selander <[e-mail]>, Stefanie Gerdes 
<[e-mail]>, Stefanie Gerdes <[e-mail]>, Ludwig Seitz 
<[e-mail]>, Mehdi Mani <[e-mail]>


A new version of I-D, draft-ietf-ace-usecases-00.txt
has been successfully submitted by Ludwig Seitz and posted to the
IETF repository.

Name:		draft-ietf-ace-usecases
Revision:	00
Title:		ACE use cases
Document date:	2014-12-02
Group:		ace
Pages:		24
URL: 
http://www.ietf.org/internet-drafts/draft-ietf-ace-usecases-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-ace-usecases/
Htmlized:       http://tools.ietf.org/html/draft-ietf-ace-usecases-00


Abstract:
    Constrained devices are nodes with limited processing power, storage
    space and transmission capacities.  These devices in many cases do
    not provide user interfaces and are often intended to interact
    without human intervention.

    This document comprises a collection of representative use cases for
    the application of authentication and authorization in constrained
    environments.  These use cases aim at identifying authorization
    problems that arise during the lifecylce of a constrained device and
    are intended to provide a guideline for developing a comprehensive
    authentication and access control solution for this class of
    scenarios.

    Where specific details are relevant, it is assumed that the devices
    use the Constrained Application Protocol (CoAP) as communication
    protocol, however most conclusions apply generally.

 



Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat