Re: [hiaps] Hiaps use cases

Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 24 February 2014 16:57 UTC

Return-Path: <sarikaya2012@gmail.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 8BD731A01F4 for <hiaps@ietfa.amsl.com>; Mon, 24 Feb 2014 08:57:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.951
X-Spam-Level:
X-Spam-Status: No, score=0.951 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 30gKIM3VSAA5 for <hiaps@ietfa.amsl.com>; Mon, 24 Feb 2014 08:57:27 -0800 (PST)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 9C8551A01FC for <hiaps@ietf.org>; Mon, 24 Feb 2014 08:57:20 -0800 (PST)
Received: by mail-la0-f43.google.com with SMTP id pv20so6067393lab.16 for <hiaps@ietf.org>; Mon, 24 Feb 2014 08:57:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=9h7SxqJ1xYeanjhoxI5119L980uFcd7TP96GMcmC7Ac=; b=NEpTpJlvVDFGZiK5pXZ1QkNChN5hzGeLnCwIrYMxVz9EHBgN6+segJypsbO9raR3hk egngOkn0YawEsD1G2whQPZR4EUZsh+6jBX11ENq2nBoEZU4a3g2kaaB7JLkxlrNc3GB4 kAEpWBHcVQTo1hCHdIQTlilwYjmZ0lljearroc6I6l1jpgqYGzWxrtI2/CZYNFZC1Z9Q ADOh4okrJIMuKj7BAWp3/bZbBXbuOBqkz8Y/sdbc3vy9IIvz9hsnk2QOR8Wrb7f9jPw6 xSud9fchUKEZNlcrDTkxmdAaEEe5pC3Bp//asnJgVgeS9QBybxdldA79pO9v/7qtr+R6 bICg==
MIME-Version: 1.0
X-Received: by 10.152.2.131 with SMTP id 3mr2731837lau.20.1393261039325; Mon, 24 Feb 2014 08:57:19 -0800 (PST)
Received: by 10.114.176.234 with HTTP; Mon, 24 Feb 2014 08:57:19 -0800 (PST)
In-Reply-To: <CAC8QAcd1bVyoz=u9+C2P3pbB2YOJE0TXV44uUJcCouC61anQMg@mail.gmail.com>
References: <CAC8QAcd1bVyoz=u9+C2P3pbB2YOJE0TXV44uUJcCouC61anQMg@mail.gmail.com>
Date: Mon, 24 Feb 2014 10:57:19 -0600
Message-ID: <CAC8QAcfLvt8fTgFhj4AD=fasFZ_LTkM03HsqtnHrEe-nG8eT7Q@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: hiaps@ietf.org
Content-Type: multipart/alternative; boundary=089e013c674c54174404f329dda7
Archived-At: http://mailarchive.ietf.org/arch/msg/hiaps/MzSE9wlOhm82A7_1T6NLdi46Vw8
Cc: Xueli <xueli@huawei.com>, Mohamed Boucadair <mohamed.boucadair@orange.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
Reply-To: sarikaya@ieee.org
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: Mon, 24 Feb 2014 16:57:28 -0000

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>wrote;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
>