Re: [hiaps] Hiaps use cases

Xueli <xueli@huawei.com> Tue, 25 February 2014 01:27 UTC

Return-Path: <xueli@huawei.com>
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 D85651A0360 for <hiaps@ietfa.amsl.com>; Mon, 24 Feb 2014 17:27:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.747
X-Spam-Level:
X-Spam-Status: No, score=-4.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 Ft-NJ7l4HTJt for <hiaps@ietfa.amsl.com>; Mon, 24 Feb 2014 17:27:07 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F14C11A0359 for <hiaps@ietf.org>; Mon, 24 Feb 2014 17:27:05 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBL90906; Tue, 25 Feb 2014 01:27:04 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 25 Feb 2014 01:26:58 +0000
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 25 Feb 2014 01:27:03 +0000
Received: from NKGEML504-MBX.china.huawei.com ([169.254.7.47]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Tue, 25 Feb 2014 09:27:00 +0800
From: Xueli <xueli@huawei.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, "hiaps@ietf.org" <hiaps@ietf.org>
Thread-Topic: Hiaps use cases
Thread-Index: AQHPMYGH0dIviH6Pv0SXd5EgffVi0JrFJYMA
Date: Tue, 25 Feb 2014 01:26:59 +0000
Message-ID: <01FE63842C181246BBE4CF183BD159B448F7DF5F@nkgeml504-mbx.china.huawei.com>
References: <CAC8QAcd1bVyoz=u9+C2P3pbB2YOJE0TXV44uUJcCouC61anQMg@mail.gmail.com> <CAC8QAcfLvt8fTgFhj4AD=fasFZ_LTkM03HsqtnHrEe-nG8eT7Q@mail.gmail.com>
In-Reply-To: <CAC8QAcfLvt8fTgFhj4AD=fasFZ_LTkM03HsqtnHrEe-nG8eT7Q@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.97.86]
Content-Type: multipart/alternative; boundary="_000_01FE63842C181246BBE4CF183BD159B448F7DF5Fnkgeml504mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/hiaps/uLcPYh5zEs9FVBqkJOII3JMGB5M
Cc: Mohamed Boucadair <mohamed.boucadair@orange.com>, "brandon.williams@akamai.com" <brandon.williams@akamai.com>, Dan Wing <dwing@cisco.com>, "Dirk.von-Hugo@telekom.de" <Dirk.von-Hugo@telekom.de>
Subject: Re: [hiaps] Hiaps use cases
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: Tue, 25 Feb 2014 01:27:10 -0000

Hi all

This draft lists several scenarios which encounters the issues of  the host unique identification.

Two more new use cases are added from version 03.


In Use case 10: operators expect that the traffic subject to the packet inspection is
   routed via the Traffic Detection Function (TDF) function as

   requirement specified in 3GPP [TS29.212].  This assumption only holds if it is possible to
   identify individual UEs behind NA(P)T.


In use case 11: A UE is connected to the RG, routed back to the mobile network.  The
   mobile operator's PCRF needs to maintain the interconnect with the
   Broadband Policy Control Function (BPCF) in the BBF network for Policy control.
  The hosts (i.e. UEs) attaching to fixed broadband network with a NA(P)T deployed should be identified.
In IPv6 network, prefix sharing issues should be resolved.

The use cases in this draft covers the all the hiaps issues right now.
I hope this clarification is useful.

Best Regards
Li Xue
From: Behcet Sarikaya [mailto:sarikaya2012@gmail.com]
Sent: Tuesday, February 25, 2014 12:57 AM
To: hiaps@ietf.org
Cc: Mohamed Boucadair; Dirk.von-Hugo@telekom.de; Xueli; Dan Wing; brandon.williams@akamai.com
Subject: Re: Hiaps use cases

Folks,
We had brought up this issue way back in December. Now we observe that a new version of the host identifier scenarios draft has been submitted, at:

http://tools.ietf.org/id/draft-boucadair-intarea-host-identifier-scenarios-04.txt
This new document as 11 cases:

3.1.  Use Case 1: CGN . . . . . . . . . . . . . . . . . . . . .   4

     3.2.  Use Case 2: A+P . . . . . . . . . . . . . . . . . . . . .   4

     3.3.  Use Case 3: Application Proxies . . . . . . . . . . . . .   5

     3.4.  Use Case 4: Open Wi-Fi or Provider Wi-Fi  . . . . . . . .   5

     3.5.  Use Case 5: Policy and Charging Control Architecture  . .   7

     3.6.  Use Case 6: Cellular Networks . . . . . . . . . . . . . .   8

     3.7.  Use Case 7: Femtocells  . . . . . . . . . . . . . . . . .   8

     3.8.  Use Case 8: Overlay Network . . . . . . . . . . . . . . .  10

     3.9.  Use Case 9: Emergency Calls . . . . . . . . . . . . . . .  11

     3.10. Use Case 10: Traffic Detection Function . . . . . . . . .  12

     3.11. Use Case 11: Fixed and Mobile Network Convergence . . . .  13
It seems like use case 11 is about prefix sharing use case for which a detailed document will be submitted soon. This means that with Rev 04 of host id scenarios draft all of hiaps issues are covered.
I hope the authors can confirm.
Regards,
Dirk & Behcet

On Mon, Dec 2, 2013 at 10:32 AM, Behcet Sarikaya <sarikaya2012@gmail.com<mailto:sarikaya2012@gmail.com>> wrote:
I started a new tread on the use case issue that Med brought up.
Based on what Med said in his previous mail:

>IMHO before having solution-oriented discussion, let's see first if people
>understand well the problem space and the set of use cases identified
>so far.
for this we currently have:
http://tools.ietf.org/id/draft-boucadair-intarea-host-identifier-scenarios-03.txt
and
http://tools.ietf.org/id/draft-sarikaya-aps-prefix-sharing-usecase-00.txt
We are expecting a new draft on this and I know we already have some people working on it.
Regards,
Behcet