IETF Logo Mail Archive

Re: [hiaps] Draft Charter Revised

<Dirk.von-Hugo@telekom.de> Wed, 15 January 2014 18:19 UTC

Return-Path: <Dirk.von-Hugo@telekom.de>
X-Original-To: hiaps@ietfa.amsl.com
Delivered-To: hiaps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E790E1AE13A for <hiaps@ietfa.amsl.com>; Wed, 15 Jan 2014 10:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538] 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 3IOF8oUbSlcn for <hiaps@ietfa.amsl.com>; Wed, 15 Jan 2014 10:19:42 -0800 (PST)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [80.149.113.247]) by ietfa.amsl.com (Postfix) with ESMTP id 3017E1AE128 for <hiaps@ietf.org>; Wed, 15 Jan 2014 10:19:41 -0800 (PST)
Received: from he113443.emea1.cds.t-internal.com ([10.134.93.103]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 15 Jan 2014 19:19:28 +0100
Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE113443.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 15 Jan 2014 19:19:28 +0100
From: <Dirk.von-Hugo@telekom.de>
To: <mohamed.boucadair@orange.com>, <sarikaya@ieee.org>, <hiaps@ietf.org>
Date: Wed, 15 Jan 2014 19:19:26 +0100
Thread-Topic: Draft Charter Revised
Thread-Index: Ac8Mrj0WrGsgBgYOTaCmSukOEkaZNwFUtGnAAAbLeJA=
Message-ID: <05C81A773E48DD49B181B04BA21A342A2DA6006FC2@HE113484.emea1.cds.t-internal.com>
References: <CAC8QAcdTNOPdhPfZrgg2SLerDs8b=DSHyVmXi7baLTdO6ZjwHw@mail.gmail.com> <94C682931C08B048B7A8645303FDC9F36F45EC4344@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36F45EC4344@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, de-DE
Content-Type: multipart/alternative; boundary="_000_05C81A773E48DD49B181B04BA21A342A2DA6006FC2HE113484emea1_"
MIME-Version: 1.0
Subject: Re: [hiaps] Draft Charter Revised
X-BeenThere: hiaps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Host Identification, Address and Prefix Sharing in Wi-Fi Access \(hiaps\)" <hiaps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hiaps>, <mailto:hiaps-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hiaps/>
List-Post: <mailto:hiaps@ietf.org>
List-Help: <mailto:hiaps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hiaps>, <mailto:hiaps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 18:19:46 -0000

Hi Med and all,
Thanks for the question. I agree that emergency call is just one of multiple use cases where host identification is an issue and currently no viable solution is agreed on.
On the other hand we have to realize and keep in mind that (not only nowadays) the privacy issues for location and identity are a major concern towards everyone. It seems that for most of the use cases thus a satisfying solution will be hard to find - the narrowed down scenario with limited actors to which the identity is uncovered (emergency and call service providers) might allow to manage the issue here.
We have chosen WiFi as typical and widespread environment providing guest access where - as opposite to cellular service - the identity may be not accessible to any intermediate connectivity provider.
Surely after successful solution of this case one can try to extend it to others ...

Hope this helps to understand. Any further comments and opinions welcome!
Best regards
Dirk
From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
Sent: Mittwoch, 15. Januar 2014 15:53
To: sarikaya@ieee.org; hiaps@ietf.org
Cc: von Hugo, Dirk
Subject: RE: Draft Charter Revised

Hi Behcet, all,

I just read the proposed charter text. I don't understand why the scope is limited to the emergency case. IMHO, the emergency case is only a use case among others. I don't understand either why "Wi-Fi" access is mentioned in the title of the proposed bof.

Cheers,
Med

De : Behcet Sarikaya [mailto:sarikaya2012@gmail.com]
Envoyé : mercredi 8 janvier 2014 21:14
À : hiaps@ietf.org
Cc : Dirk.von-Hugo@telekom.de
Objet : Draft Charter Revised

Hi all,
Based on the comments received so far and based on our contacts with ETSI, we have revised the charter. Please check the current version at:

http://trac.tools.ietf.org/bof/trac/
Please direct all comments and support to the list.
Kind regards,
Behcet

v2.8.7 | Report a Bug | By Email