[Secauth] avoid confusion..

Hosnieh Rafiee <hosnieh.rafiee@huawei.com> Tue, 09 December 2014 11:39 UTC

From: Hosnieh Rafiee <hosnieh.rafiee@huawei.com>
To: "secauth@ietf.org" <secauth@ietf.org>
Thread-Topic: avoid confusion..
Thread-Index: AdATpMwHq/NjCd3xR72PlNdRdhX5ow==
Date: Tue, 09 Dec 2014 11:39:35 +0000
Message-ID: <814D0BFB77D95844A01CA29B44CBF8A7B2355D@lhreml513-mbx>
Accept-Language: zh-CN, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/ohpcA0CgH6U3ODcXmuvIWk_Fj_E
Subject: [Secauth] avoid confusion..
Precedence: list

All,

Based on offlist discussion, I think we need to clarify the direction of our discussion in order to avoid confusion.

1- We are still discussing on the secauth scope to agree on it.
2- There is no solution proposal yet at this time so feel free to propose solution.
3- Discussing about infrastructure is not about solution. I think there is already some standards in current infrastructure (non-virtualized) and some groups working on them. So, I would like our focus to be on virtualized environment and virtualized components so that secauth scope clearly defined in such environment and the relationship of end user, intermediate companies, ISPs, vendors where the existing standards might not work well or need some extensions. 
4- We need to update secauth use case document. Feel free to propose other use cases. This will be also the discussion in telco. I will try to think about more use cases.
< https://tools.ietf.org/html/draft-rafiee-secauth-usecase-02 >
5- last but not least, IMO, identifying the place of each players in this infrastructure help to clarify the scope of secauth. 

Any Thoughts?
Best,
Hosnieh

[Secauth] avoid confusion.. Hosnieh Rafiee