[prev in list] [next in list] [prev in thread] [next in thread]
List: ietf-saag
Subject: [saag] ACE meeting summary for IETF 90
From: Likepeng <likepeng () huawei ! com>
Date: 2014-07-24 11:38:21
Message-ID: 34966E97BE8AD64EAE9D3D6E4DEE36F25817AFEA () SZXEMA501-MBS ! china ! huawei ! com
[Download RAW message or body]
ACE (Authentication and Authorization for Constrained Environments)
Chairs: Kepeng Li, Hannes Tschofenig
Time: Wednesday morning, 9:00 ~ 11:30
Physical attendees: ~70
1. ACE Introduction (Chairs, 10 mins):
This was the first WG F2F meeting. Kepeng introduced briefly about ACE work=
. Hannes gave some brief summaries about Stockholm informal meeting.
2. Design Directions
2.1: Problem Description (Ludwig Seitz, 30 mins)
Most of the discussions were about different models: Pull model, Push model=
, Agent model, Push & Confirm model.
Different models can apply to different use cases.
We need to analyze the use cases to see which model(s) to choose.
2.2: Use Cases & Design Patterns (Ludwig Seitz, 30 mins)
There was discussion that there may be multiple authorization servers, and =
we need to consider the case to change authorization servers.
There was discussion that client joining network process should be out of s=
cope.
Hannes mentioned we have already called for adoption for use case draft. Th=
ree volunteers were identified to review the draft and provide feedback in =
the mailing list.
2.3: Design Considerations (Corinna Schmitt, 30 mins)
It was discussed that we should not be scared about asymmetric key, and als=
o we don't force on asymmetric key.
It was also discussed that we should not narrow down to either one of the t=
wo mechanisms (symmetric key vs. asymmetric key), different environments re=
quire different mechanisms.
We need to get more data to make decision about symmetric key and/or asymme=
tric key.
2.4: Cross-domain Support (Carsten Bormann, 30 mins)
It was discussed that we should consider legacy devices, and consider proxy=
support.
3. Summary and Next Steps (Chairs, 10 mins)
Hannes mentioned about possible interim meeting(s): conference calls or F2F=
meeting.
Hannes also mentioned that it will be good to use implementation experience=
to collect data to help our designs.
Kind Regards
Kepeng
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
text-align:justify;
text-justify:inter-ideograph;
font-size:10.5pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"\7EAF\6587\672C Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.Char
{mso-style-name:"\7EAF\6587\672C Char";
mso-style-priority:99;
mso-style-link:\7EAF\6587\672C;
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="ZH-CN" link="blue" vlink="purple" style="text-justify-trim:punctuation">
<div class="WordSection1">
<p class="MsoPlainText"><span lang="EN-US">ACE (Authentication and Authorization for \
Constrained Environments)<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">Chairs: Kepeng Li, Hannes Tschofenig<o:p></o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US">Time: Wednesday morning, 9:00 ~ \
11:30<o:p></o:p></span></p> <p class="MsoPlainText"><span lang="EN-US">Physical \
attendees: ~70<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">1. ACE Introduction (Chairs, 10 mins): <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">This was the first WG F2F meeting. Kepeng \
introduced briefly about ACE work. Hannes gave some brief summaries about Stockholm \
informal meeting.<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">2. Design Directions<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">2.1: Problem Description (Ludwig Seitz, 30 mins)<o:p></o:p></span></p> \
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US">Most of the discussions were about different \
models: Pull model, Push model, Agent model, Push & Confirm \
model.<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">Different models can apply to different use cases.<o:p></o:p></span></p> \
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US">We need to analyze the use cases to see which \
model(s) to choose.<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">2.2: Use Cases & Design Patterns (Ludwig Seitz, 30 \
mins)<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">There was discussion that there may be multiple authorization servers, \
and we need to consider the case to change authorization \
servers.<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">There was discussion that client joining network process should be out \
of scope.<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">Hannes mentioned we have already called for adoption for use case draft. \
Three volunteers were identified to review the draft and provide feedback in the \
mailing list.<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">2.3: Design Considerations (Corinna Schmitt, 30 \
mins)<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">It was discussed that we should not be scared about asymmetric key, and \
also we don't force on asymmetric key.<o:p></o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US">It was also discussed that we should not \
narrow down to either one of the two mechanisms (symmetric key vs. asymmetric key), \
different environments require different mechanisms.<o:p></o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US">We need to get more data to make decision \
about symmetric key and/or asymmetric key.<o:p></o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US">2.4: Cross-domain Support (Carsten Bormann, \
30 mins)<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">It was discussed that we should consider legacy devices, and consider \
proxy support.<o:p></o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoPlainText"><span \
lang="EN-US">3. Summary and Next Steps (Chairs, 10 mins)<o:p></o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US">Hannes mentioned about possible interim \
meeting(s): conference calls or F2F meeting.<o:p></o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p> <p \
class="MsoPlainText"><span lang="EN-US">Hannes also mentioned that it will be good to \
use implementation experience to collect data to help our \
designs.<o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US">Kind Regards<o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US">Kepeng<o:p></o:p></span></p> </div>
</body>
</html>
_______________________________________________
saag mailing list
saag@ietf.org
https://www.ietf.org/mailman/listinfo/saag
--===============8210213971379519594==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic