From nobody Tue Jun 10 02:06:28 2014 Return-Path: X-Original-To: secauth@ietfa.amsl.com Delivered-To: secauth@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8F41A01EB for ; Tue, 10 Jun 2014 02:06:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.851 X-Spam-Level: X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fz678FblPEXZ for ; Tue, 10 Jun 2014 02:06:27 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 721A81A02FE for ; Tue, 10 Jun 2014 02:06:26 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BIG47291; Tue, 10 Jun 2014 09:06:24 +0000 (GMT) Received: from SZXEMA401-HUB.china.huawei.com (10.82.72.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 10 Jun 2014 10:06:24 +0100 Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.3]) by SZXEMA401-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0158.001; Tue, 10 Jun 2014 17:06:20 +0800 From: "Liushucheng (Will)" To: "secauth@ietf.org" Thread-Topic: A page for secuth? Thread-Index: Ac+Eiz442u4ebV/VSy+JOVAO1un6YA== Date: Tue, 10 Jun 2014 09:06:19 +0000 Message-ID: Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.66.78.79] Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB5FEF7794SZXEMA509MBSchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/8U8M3R3lMvGahiNadn0GDN45Tt0 Subject: [Secauth] A page for secuth? X-BeenThere: secauth@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Omni-purpose Network-layer based Secure Authentication non-working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2014 09:06:28 -0000 --_000_C9B5F12337F6F841B35C404CF0554ACB5FEF7794SZXEMA509MBSchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, I just joint this list and read through your emails. Regarding Hosnieh said= "One problem I can see here is that since some of the discussion was in separate messages, it was not easy to follow the cases. " Yes, it will be = difficult for a freshman to catch up here. One good example is what TAPS and ACTN did. They set up a web page which m= ake everything much easier. https://sites.google.com/site/actnbof/ https://sites.google.com/site/transportprotocolservices/charter-proposal Just FYI. Regards, Shucheng LIU (Will) ---------------------------------------------------------------------------= -------- Shucheng LIU (Will), Ph.D. Researcher & Standard Representative Huawei Technologies Co.,Ltd liushucheng@huawei.com http://www.linkedin.com/in/shucheng ---------------------------------------------------------------------------= -------- --_000_C9B5F12337F6F841B35C404CF0554ACB5FEF7794SZXEMA509MBSchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Folks,

 

I just joint this list and read through your emails. Regarding Hosnieh=
 said “One problem I can see here is that since some of the discussio=
n was in

separate messages, it was not easy to follow the cas= es. “  Yes, it will be difficult for a freshman to catch up here= .

 

One good example is what TAPS and ACTN did. They set= up a web page  which make everything much easier.

h= ttps://sites.google.com/site/actnbof/

https://sites.google.com/site/transportpro= tocolservices/charter-proposal

Just FYI.

 

Regards,

Shucheng LIU (Will)

----------------------------------------------------= -------------------------------

Shucheng LIU (Will), Ph.D.

Researcher & Standard Representative

Huawei Technologies Co.,Ltd

liushucheng@huawei.com

<= span style=3D"color:blue">http://www.linkedin.com/in/shucheng

----------------------------------------------------= -------------------------------

 

--_000_C9B5F12337F6F841B35C404CF0554ACB5FEF7794SZXEMA509MBSchi_-- From nobody Tue Jun 10 02:24:52 2014 Return-Path: X-Original-To: secauth@ietfa.amsl.com Delivered-To: secauth@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34A7C1A035B for ; Tue, 10 Jun 2014 02:24:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dNEWNMk30uv1 for ; Tue, 10 Jun 2014 02:24:49 -0700 (PDT) Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B96001A001B for ; Tue, 10 Jun 2014 02:24:48 -0700 (PDT) Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 638C856608D9; Tue, 10 Jun 2014 09:24:46 +0000 (UTC) X-Virus-Scanned: amavisd-new at rozanak.com Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0-Vm-Yx-d5RN; Tue, 10 Jun 2014 11:24:12 +0200 (CEST) Received: from kopoli (g225184206.adsl.alicedsl.de [92.225.184.206]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id BD3A456608D8; Tue, 10 Jun 2014 11:24:11 +0200 (CEST) From: "Hosnieh Rafiee" To: References: In-Reply-To: Date: Tue, 10 Jun 2014 11:24:08 +0200 Message-ID: <000f01cf848d$bc05ddf0$341199d0$@rozanak.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01CF849E.7F920950" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHlMdhT0e8HO+r6H2Wlay0weXqvw5s+to7g Content-Language: en-us Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/KoKbSHVdi4fDq71cN0BDbAan23Q Cc: "'Liushucheng \(Will\)'" Subject: Re: [Secauth] A page for secuth? X-BeenThere: secauth@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Omni-purpose Network-layer based Secure Authentication non-working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2014 09:24:51 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0010_01CF849E.7F920950 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit You're right. Thanks for your suggestion. I will create a page today and post all the summery including the two documents I prepared as a use cases and requirements. Thanks again, Best, Hosnieh P.S. Sorry folks, I was quite busy with changing my work place and I really appreciate helps to progress this work faster. From: Secauth [mailto:secauth-bounces@ietf.org] On Behalf Of Liushucheng (Will) Sent: Tuesday, June 10, 2014 11:06 AM To: secauth@ietf.org Subject: [Secauth] A page for secuth? Folks, I just joint this list and read through your emails. Regarding Hosnieh said "One problem I can see here is that since some of the discussion was in separate messages, it was not easy to follow the cases. " Yes, it will be difficult for a freshman to catch up here. One good example is what TAPS and ACTN did. They set up a web page which make everything much easier. https://sites.google.com/site/actnbof/ https://sites.google.com/site/transportprotocolservices/charter-proposal Just FYI. Regards, Shucheng LIU (Will) ---------------------------------------------------------------------------- ------- Shucheng LIU (Will), Ph.D. Researcher & Standard Representative Huawei Technologies Co.,Ltd liushucheng@huawei.com http://www.linkedin.com/in/shucheng ---------------------------------------------------------------------------- ------- ------=_NextPart_000_0010_01CF849E.7F920950 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

You’re right. =

Thanks for your suggestion. =

I will = create a page today and post all the summery including the two documents = I prepared as a use cases and requirements.

 

Thanks = again,

Best,

Hosnieh

P.S. = Sorry folks, I was quite busy with changing my work place and I really = appreciate helps to progress this work faster.

 

 

From:= = Secauth [mailto:secauth-bounces@ietf.org] On Behalf Of = Liushucheng (Will)
Sent: Tuesday, June 10, 2014 11:06 = AM
To: secauth@ietf.org
Subject: [Secauth] A page = for secuth?

 

Folks,

 

I just joint this list and =
read through your emails. Regarding Hosnieh said “One problem I =
can see here is that since some of the discussion was =
in

separate messages, it was not = easy to follow the cases. “  Yes, it will be difficult for a = freshman to catch up here.

 

One good = example is what TAPS and ACTN did. They set up a web page  which = make everything much easier.

https://sites.google.com/= site/actnbof/

https://sites.google.com/site/transportprotocolservices/charter-= proposal

Just = FYI.

 

Regards,

Shucheng = LIU (Will)

-------------------------------------------------------= ----------------------------

Shucheng LIU (Will), Ph.D.

Researcher & Standard Representative =

Huawei Technologies = Co.,Ltd

liushucheng@huawei.com

http://www.linkedin.com/in/s= hucheng

-------------------------------------------------------= ----------------------------

 

------=_NextPart_000_0010_01CF849E.7F920950-- From nobody Tue Jun 10 16:25:12 2014 Return-Path: X-Original-To: secauth@ietfa.amsl.com Delivered-To: secauth@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14AF51A00FD for ; Tue, 10 Jun 2014 16:25:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1_uUpTNcy7P3 for ; Tue, 10 Jun 2014 16:25:10 -0700 (PDT) Received: from mail.rozanak.com (mail.rozanak.com [IPv6:2a01:238:42ad:1500:aa19:4238:e48f:61cf]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE91F1A00A5 for ; Tue, 10 Jun 2014 16:25:09 -0700 (PDT) Received: from localhost (unknown [127.0.0.1]) by mail.rozanak.com (Postfix) with ESMTP id 149D656608D9 for ; Tue, 10 Jun 2014 23:25:08 +0000 (UTC) X-Virus-Scanned: amavisd-new at rozanak.com Received: from mail.rozanak.com ([127.0.0.1]) by localhost (mail.iknowlaws.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Siietj0fOsfd for ; Wed, 11 Jun 2014 01:24:36 +0200 (CEST) Received: from kopoli (g225041086.adsl.alicedsl.de [92.225.41.86]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.rozanak.com (Postfix) with ESMTPSA id B37D256608D8 for ; Wed, 11 Jun 2014 01:24:36 +0200 (CEST) From: "Hosnieh Rafiee" To: Date: Wed, 11 Jun 2014 01:24:33 +0200 Message-ID: <00a901cf8503$2368f1b0$6a3ad510$@rozanak.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac+FAyL/6e4yvYWpTzmr+28ZyWaIRA== Content-Language: en-us Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/VUHUbmXJUlHFzQsQVE0xoj-vnas Subject: [Secauth] All messages X-BeenThere: secauth@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Omni-purpose Network-layer based Secure Authentication non-working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2014 23:25:11 -0000 Folks, As Will suggested, I have created a page and copied all messages there. Maybe it is easier to follow and read them. Thanks, Best, Hosnieh P.S. It is quite late and I cannot keep myself up to submit the two documents I promised... will do it tomorrow (or today ... my time :| ) From nobody Tue Jun 10 18:18:54 2014 Return-Path: X-Original-To: secauth@ietfa.amsl.com Delivered-To: secauth@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBFFF1A0261 for ; Tue, 10 Jun 2014 18:18:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.852 X-Spam-Level: X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e1PT2oU4JjYf for ; Tue, 10 Jun 2014 18:18:52 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 025AC1A0264 for ; Tue, 10 Jun 2014 18:18:50 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BFH08327; Wed, 11 Jun 2014 01:18:49 +0000 (GMT) Received: from SZXEMA406-HUB.china.huawei.com (10.82.72.38) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 11 Jun 2014 02:18:49 +0100 Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.3]) by SZXEMA406-HUB.china.huawei.com ([10.82.72.38]) with mapi id 14.03.0158.001; Wed, 11 Jun 2014 09:18:42 +0800 From: "Liushucheng (Will)" To: Hosnieh Rafiee , "secauth@ietf.org" Thread-Topic: [Secauth] All messages Thread-Index: Ac+FAyL/6e4yvYWpTzmr+28ZyWaIRAAD+PyQ Date: Wed, 11 Jun 2014 01:18:41 +0000 Message-ID: References: <00a901cf8503$2368f1b0$6a3ad510$@rozanak.com> In-Reply-To: <00a901cf8503$2368f1b0$6a3ad510$@rozanak.com> Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.66.78.79] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/r5Wx2lBUXdG3-gTCd53yKS6whB4 Subject: Re: [Secauth] All messages X-BeenThere: secauth@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Omni-purpose Network-layer based Secure Authentication non-working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 01:18:53 -0000 Cool. Great work! Regards, Will (Shucheng LIU) > -----Original Message----- > From: Secauth [mailto:secauth-bounces@ietf.org] On Behalf Of Hosnieh > Rafiee > Sent: Wednesday, June 11, 2014 7:25 AM > To: secauth@ietf.org > Subject: [Secauth] All messages >=20 > Folks, >=20 > As Will suggested, I have created a page and copied all messages there. > Maybe it is easier to follow and read them. > >=20 > Thanks, > Best, > Hosnieh > P.S. It is quite late and I cannot keep myself up to submit the two > documents I promised... will do it tomorrow (or today ... my time :| ) >=20 >=20 > _______________________________________________ > Secauth mailing list > Secauth@ietf.org > https://www.ietf.org/mailman/listinfo/secauth From nobody Thu Jun 26 09:58:53 2014 Return-Path: X-Original-To: secauth@ietfa.amsl.com Delivered-To: secauth@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B06E1B2C92 for ; Thu, 26 Jun 2014 09:58:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.851 X-Spam-Level: X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mt3O9L-wwFDB for ; Thu, 26 Jun 2014 09:58:48 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F9BD1B2C5E for ; Thu, 26 Jun 2014 09:44:40 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJH55600; Thu, 26 Jun 2014 16:44:39 +0000 (GMT) Received: from LHREML513-MBB.china.huawei.com ([fe80::b810:863:a57e:3ff]) by lhreml402-hub.china.huawei.com ([10.201.5.241]) with mapi id 14.03.0158.001; Thu, 26 Jun 2014 17:44:33 +0100 From: Hosnieh Rafiee To: "Secauth@ietf.org" Thread-Topic: First draft of requirements and use cases Thread-Index: Ac+RXegNFh/w/ZUHQvy1AbftARnVBg== Date: Thu, 26 Jun 2014 16:44:33 +0000 Message-ID: <814D0BFB77D95844A01CA29B44CBF8A7A09750@lhreml513-mbb.china.huawei.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.221.82.100] Content-Type: multipart/alternative; boundary="_000_814D0BFB77D95844A01CA29B44CBF8A7A09750lhreml513mbbchina_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/fBAokkYFTxP8uT17RPMX57a8bAY Subject: [Secauth] First draft of requirements and use cases X-BeenThere: secauth@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Omni-purpose Network-layer based Secure Authentication non-working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2014 16:58:51 -0000 --_000_814D0BFB77D95844A01CA29B44CBF8A7A09750lhreml513mbbchina_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, This is the first draft of requirement and use case scenarios for secauth (= that might be good to consider it as a protocol and have its implementation= as an API) http://editor.rozanak.com/show.aspx?u=3DAZ6AA4BFD809BB71B2544CTAM I have= n't yet uploaded it on IETF website because I would like to complete it mor= e. I am also looking for volunteer co-authors to improve this document. This i= s really a raw version and it needs more efforts. My idea is that to have s= omething good for the next IETF. So, I welcome any types of comments either= editorial or in case the requirement is not clear yet. I need to add some more info to some sections and probably when you read th= is document tomorrow you will find more text on place I wrote TBD. Thank you! Looking forward to see your comments and contributions. Best, Hosnieh P.S. Sorry again for the delay (busy with relocation and...). I also had li= mited access to internet. --_000_814D0BFB77D95844A01CA29B44CBF8A7A09750lhreml513mbbchina_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

This is the first draft of requirement and use case = scenarios for secauth (that might be good to consider it as a protocol and = have its implementation as an API)

http://editor.rozanak.com/show.aspx?u=3DAZ6AA4BFD= 809BB71B2544CTAM    I haven’t yet uploaded it on I= ETF website because I would like to complete it more.

 

I am also looking for volunteer co-authors to improv= e this document. This is really a raw version and it needs more efforts. My= idea is that to have something good for the next IETF. So, I welcome any t= ypes of comments either editorial or in case the requirement is not clear yet.

I need to add some more info to some sections and pr= obably when you read this document tomorrow you will find more text on plac= e I wrote TBD.

 

Thank you! Looking forward to see your comments and = contributions.

Best,

Hosnieh

P.S. Sorry again for the delay (busy with relocation= and…). I also had limited access to internet.

--_000_814D0BFB77D95844A01CA29B44CBF8A7A09750lhreml513mbbchina_-- From nobody Thu Jun 26 10:02:28 2014 Return-Path: X-Original-To: secauth@ietfa.amsl.com Delivered-To: secauth@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75E701B29A9 for ; Thu, 26 Jun 2014 10:02:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.851 X-Spam-Level: X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rhq7Rjf8kO6 for ; Thu, 26 Jun 2014 10:02:25 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54AAA1B2932 for ; Thu, 26 Jun 2014 09:53:49 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJH56101; Thu, 26 Jun 2014 16:53:47 +0000 (GMT) Received: from LHREML513-MBB.china.huawei.com ([fe80::b810:863:a57e:3ff]) by lhreml401-hub.china.huawei.com ([10.201.5.240]) with mapi id 14.03.0158.001; Thu, 26 Jun 2014 17:53:44 +0100 From: Hosnieh Rafiee To: "secauth@ietf.org" Thread-Topic: First draft of requirements and use cases Thread-Index: Ac+RXegNFh/w/ZUHQvy1AbftARnVBgAAS/yw Date: Thu, 26 Jun 2014 16:53:44 +0000 Message-ID: <814D0BFB77D95844A01CA29B44CBF8A7A09769@lhreml513-mbb.china.huawei.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.221.82.100] Content-Type: multipart/alternative; boundary="_000_814D0BFB77D95844A01CA29B44CBF8A7A09769lhreml513mbbchina_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/BLrq6RHgu9S-Hnsrb-iMPCuEG90 Subject: [Secauth] First draft of requirements and use cases X-BeenThere: secauth@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Omni-purpose Network-layer based Secure Authentication non-working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jun 2014 17:02:27 -0000 --_000_814D0BFB77D95844A01CA29B44CBF8A7A09769lhreml513mbbchina_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, This is the first draft of requirement and use case scenarios for secauth (= that might be good to consider it as a protocol and have its implementation= as an API) http://editor.rozanak.com/show.aspx?u=3DAZ6AA4BFD809BB71B2544CTAM I have= n't yet uploaded it on IETF website because I would like to complete it mor= e. I am also looking for volunteer co-authors to improve this document. This i= s really a raw version and it needs more efforts. My idea is that to have s= omething good for the next IETF. So, I welcome any types of comments either= editorial or in case the requirement is not clear yet. I need to add some more info to some sections and probably when you read th= is document tomorrow you will find more text on place I wrote TBD. Thank you! Looking forward to see your comments and contributions. Best, Hosnieh P.S. Sorry again for the delay (busy with relocation and...). I also had li= mited access to internet. --_000_814D0BFB77D95844A01CA29B44CBF8A7A09769lhreml513mbbchina_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

This is the first draft of requirement and use case = scenarios for secauth (that might be good to consider it as a protocol and = have its implementation as an API)

http://editor.rozanak.com/show.aspx?u=3DAZ6AA4BFD= 809BB71B2544CTAM    I haven’t yet uploaded it on I= ETF website because I would like to complete it more.

 

I am also looking for volunteer co-authors to improv= e this document. This is really a raw version and it needs more efforts. My= idea is that to have something good for the next IETF. So, I welcome any t= ypes of comments either editorial or in case the requirement is not clear yet.

I need to add some more info to some sections and pr= obably when you read this document tomorrow you will find more text on plac= e I wrote TBD.

 

Thank you! Looking forward to see your comments and = contributions.

Best,

Hosnieh

P.S. Sorry again for the delay (busy with relocation= and…). I also had limited access to internet.

--_000_814D0BFB77D95844A01CA29B44CBF8A7A09769lhreml513mbbchina_--