From Dirk.von-Hugo@telekom.de Mon Mar 4 08:59:33 2013 Return-Path: X-Original-To: fmc@ietfa.amsl.com Delivered-To: fmc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 752FF21F8BF8 for ; Mon, 4 Mar 2013 08:59:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ULEB-rNKxpYz for ; Mon, 4 Mar 2013 08:59:32 -0800 (PST) Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) by ietfa.amsl.com (Postfix) with ESMTP id E021E21F86C8 for ; Mon, 4 Mar 2013 08:59:31 -0800 (PST) Received: from he110890.emea1.cds.t-internal.com ([10.134.92.131]) by tcmail91.telekom.de with ESMTP/TLS/AES128-SHA; 04 Mar 2013 17:59:29 +0100 Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by he110890 ([10.134.92.131]) with mapi; Mon, 4 Mar 2013 17:59:29 +0100 From: To: , Date: Mon, 4 Mar 2013 17:59:28 +0100 Thread-Topic: New Version Notification for draft-pularikkal-opsawg-lawful-intercept-spwifi-00.txt Thread-Index: AQHODiY284CHMnBHT0i4Jwn8r08PTJiVyNyg Message-ID: <05C81A773E48DD49B181B04BA21A342A2BA2D5E0CC@HE113484.emea1.cds.t-internal.com> References: <20130218201547.25429.90513.idtracker@ietfa.amsl.com> <7FC7CEE8B5E132468B8AC6F812F6AE171B86BD@xmb-rcd-x13.cisco.com> In-Reply-To: <7FC7CEE8B5E132468B8AC6F812F6AE171B86BD@xmb-rcd-x13.cisco.com> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: sarikaya2012@gmail.com, sgundave@cisco.com Subject: Re: [fmc] New Version Notification for draft-pularikkal-opsawg-lawful-intercept-spwifi-00.txt X-BeenThere: fmc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Fixed Mobile Convergence List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2013 16:59:33 -0000 Dear Byju, all, Thanks for sharing your considerations with this list. I think that this draft also in a wider sense may add to the use cases for = the host identification issue we have considered so far as a typical fmc se= rver (here the Wireless Access Gateway, WAG) originated challenge, i.e. law= ful intercept to require a unique Target identifier to locate and address a= user across WiFi and other access networks. (BTW I suggest not to use 'Home Gateway' for LMA or similar subscriber anch= or point as it may be mixed up with 'Residential Gateway' at a users' home) Furthermore we had the IPv6 prefix sharing use case http://www.ietf.org/int= ernet-drafts/draft-sarikaya-fmc-prefix-sharing-usecase-01.txt for residenti= al gateways where some networks may be unable to assign different prefixes = to different visiting mobile hosts. Other - more general - fmc related issues arising from application servers = e.g. used both during fixed and mobile access to same service also underlin= e the need for unique host identification. A plurality of use cases are des= cribed in http://tools.ietf.org/html/draft-boucadair-intarea-host-identifie= r-scenarios-02. As Med mentions in that draft typical hurdles to service u= sage may occur to all hosts with same IP address which also applies to fmc = scenarios. Those problems cover e.g. unwanted sharing of o Blacklist for misbehaviour o Enforced policy (tayloring service offering) o Access denial due to failing service invoking o Missing correct correlation between internal address:port and external a= ddress:port required for policy issues Finally the Unified User Identification use case (here mainly related to NA= T/CGN) is described in http://www.ietf.org/internet-drafts/draft-sun-fmc-us= e-case-01.txt. I would invite you to discuss details on the host ID use cases and further = ideas how to proceed on this list. In any case there will be an FMC-related= BarBOF organised in Orlando ... Further details will be announced shortly = (although unfortunately I myself will be unable to attend the upcoming meet= ing ;-() Thanks! Best regards Dirk -----Urspr=FCngliche Nachricht----- Von: Byju Pularikkal (byjupg) [mailto:byjupg@cisco.com] Gesendet: Montag, 18. Februar 2013 23:21 An: fmc@ietf.org Cc: Sri Gundavelli (sgundave) Betreff: FW: New Version Notification for draft-pularikkal-opsawg-lawful-in= tercept-spwifi-00.txt Hello, Attached is a document on LI Architecture for SP WIFI. Comments appreciated Thanks & Regards Byju On 2/18/13 3:15 PM, "internet-drafts@ietf.org" wrote: > >A new version of I-D, >draft-pularikkal-opsawg-lawful-intercept-spwifi-00.txt >has been successfully submitted by Byju Pularikkal and posted to the >IETF repository. > >Filename: draft-pularikkal-opsawg-lawful-intercept-spwifi >Revision: 00 >Title: Lawful-Intercept Support for SP Wi-Fi Deployments >Creation date: 2013-02-18 >Group: Individual Submission >Number of pages: 20 >URL: >http://www.ietf.org/internet-drafts/draft-pularikkal-opsawg-lawful-interce >pt-spwifi-00.txt >Status: >http://datatracker.ietf.org/doc/draft-pularikkal-opsawg-lawful-intercept-s >pwifi >Htmlized: >http://tools.ietf.org/html/draft-pularikkal-opsawg-lawful-intercept-spwifi >-00 > > >Abstract: > Lawful Intercept stands for legally authorized capture & delivery of > subscriber communications data by a communications provider to a law > enforcement agency.This document describes Generic Lawful Intercept > Architecture Models & implementation considerations for Service > Provider Wi-Fi deployments. > > > > > >The IETF Secretariat > From sarikaya2012@gmail.com Sun Mar 10 17:44:54 2013 Return-Path: X-Original-To: fmc@ietfa.amsl.com Delivered-To: fmc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E470221F88BE for ; Sun, 10 Mar 2013 17:44:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YDD5pfLNYnNV for ; Sun, 10 Mar 2013 17:44:54 -0700 (PDT) Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) by ietfa.amsl.com (Postfix) with ESMTP id 1686721F88BF for ; Sun, 10 Mar 2013 17:44:53 -0700 (PDT) Received: by mail-lb0-f170.google.com with SMTP id ge1so2719873lbb.1 for ; Sun, 10 Mar 2013 17:44:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:date:message-id:subject:from:to:cc :content-type; bh=dpGFRNom3/MLMrdtfdTFFd1vcrwPjDYXIp0JAxRYGw4=; b=0hak35H9zVpEsyZBWdPjhB5gEMg9I7j/CchIfk8xx82qANoduafRy7aXn8XGyj8yi+ lJahDHN/FyY2WLgcKPP2HyQfHQNDme1TrrqTSwRw2cOsvRbB53j8KwR9FAV43DkmUEhe K+YZqi8uwJ9ZU/R+33XDN8wh3TzrvWYMPCETYZzpOJQSt9WfQv3H6naoDAPSTMLjxPmY YbY17lH0JwWrSYnRNFh8QzsNkIDiK6QntUc4UzQB+6HVHIA1ZsNrP+bs25JMu/zxh2pL 4tUGXZG6FGHlH04scBz+NRRis/VUaS/Nw/xtXsLu83wB6txmS0fVqyjSfvG62Uv2B9yb I8gg== MIME-Version: 1.0 X-Received: by 10.112.101.101 with SMTP id ff5mr3852996lbb.107.1362962692919; Sun, 10 Mar 2013 17:44:52 -0700 (PDT) Received: by 10.114.93.41 with HTTP; Sun, 10 Mar 2013 17:44:52 -0700 (PDT) Date: Sun, 10 Mar 2013 19:44:52 -0500 Message-ID: From: Behcet Sarikaya To: fmc@ietf.org Content-Type: multipart/alternative; boundary=14dae9d717fa275f5704d79b7b29 Cc: Brian Haberman , Pierrick Seite , Mohamed Boucadair , Dirk.von-Hugo@telekom.de Subject: [fmc] Bar BoF in Orlando on Monday X-BeenThere: fmc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Fixed Mobile Convergence List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 00:44:55 -0000 --14dae9d717fa275f5704d79b7b29 Content-Type: text/plain; charset=ISO-8859-1 Folks, as Dirk mentioned, we will have a meeting in Orlando on Monday March 11 at 6pm in Grand Sierra B room We hope to discuss: Address sharing issues draft, http://tools.ietf.org/html/draft-boucadair-intarea-host-identifier-scenarios-02 Those problems cover e.g. unwanted sharing of o Blacklist for misbehaviour o Enforced policy (tayloring service offering) o Access denial due to failing service invoking o Missing correct correlation between internal address:port and external address:port required for policy issues Prefix sharing issues draft, http://www.ietf.org/internet-drafts/draft-sarikaya-fmc-prefix-sharing-usecase-01.txt and more importantly, the next steps. See you. Behcet --14dae9d717fa275f5704d79b7b29 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Folks, as Dirk mentioned, we will have a meeting in Orlando

on Mond= ay March 11 at 6pm in Grand Sierra B room

We hope to discuss:
Add= ress sharing issues draft,
http://too= ls.ietf.org/html/draft-boucadair-intarea-host-identifier-scenarios-02
Those problems cover e.g. unwanted sharing of
o =A0Blacklist for misbehaviour
o =A0Enforced policy (tayloring service offering)
o =A0Access denial due to failing service invoking
o =A0Missing correct correlation between internal address:port and external= address:port required for policy issues
=A0

Prefix sharing issues draft,
http://www.ietf.org/internet-drafts/draft-sarikaya-fmc-prefi= x-sharing-usecase-01.txt

and more importantly, the next steps.


See you.

Behcet=
--14dae9d717fa275f5704d79b7b29-- From sarikaya2012@gmail.com Mon Mar 11 07:26:47 2013 Return-Path: X-Original-To: fmc@ietfa.amsl.com Delivered-To: fmc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B2FA21F8A3E for ; Mon, 11 Mar 2013 07:26:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tgs1xsa1tIaj for ; Mon, 11 Mar 2013 07:26:47 -0700 (PDT) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 7B70C21F87F5 for ; Mon, 11 Mar 2013 07:26:46 -0700 (PDT) Received: by mail-la0-f54.google.com with SMTP id gw10so3884380lab.41 for ; Mon, 11 Mar 2013 07:26:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:date:message-id:subject:from:to:cc :content-type; bh=SyH52Q9hF4Qg8sts1FkuTRAXqCnkraKy/944+4xlua8=; b=LXurVsvAcfYvlKGWnVvh1EU8BT6cyGb0CoU7n6Y9xSf3HNh4LYHouBgo+yAqqzlVDW z59krdC5s/6mfkF8h0lEe52K3Wca12HQhL5FOICT7F3yZSmo9ByOszaOIcgd7d2edFuX Q+3Ii0EdV/SOifSKf6OGSDKQBeXaBqFPuRoYJ4ifTny4pe2gDWMQ6Y0DNJzktzK5eEaZ ektvNYB47xHBynlt7LSDfp+Bk9hSizbdHrlLvxIFPNAaE8dUdrZ2gbaYJcIwOjfqOJql nKQ4M+6i/58BSQo6zxRcnn1/OxzUY5TpV/AFDmiLzoWIPgaRoMEaxu64OY/RWDnLkBga 8U7w== MIME-Version: 1.0 X-Received: by 10.112.41.165 with SMTP id g5mr4541403lbl.37.1363012005044; Mon, 11 Mar 2013 07:26:45 -0700 (PDT) Received: by 10.114.93.41 with HTTP; Mon, 11 Mar 2013 07:26:44 -0700 (PDT) Date: Mon, 11 Mar 2013 09:26:44 -0500 Message-ID: From: Behcet Sarikaya To: fmc@ietf.org Content-Type: multipart/alternative; boundary=e0cb4efe2d2e647ad004d7a6f6f9 Cc: Brian Haberman , Pierrick Seite , Mohamed Boucadair , QUEIROZ Jaqueline OLNC/OLN , Dirk.von-Hugo@telekom.de Subject: [fmc] TIME CHANGE Bar BoF in Orlando on Monday X-BeenThere: fmc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Fixed Mobile Convergence List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 14:26:47 -0000 --e0cb4efe2d2e647ad004d7a6f6f9 Content-Type: text/plain; charset=ISO-8859-1 Folks let's make it 5pm to enable people attending the plenary. So start at 5pm. The rest is the same. On Sun, Mar 10, 2013 at 7:44 PM, Behcet Sarikaya wrote: > Folks, as Dirk mentioned, we will have a meeting in Orlando > > on Monday March 11 at 6pm in Grand Sierra B room > > We hope to discuss: > Address sharing issues draft, > > http://tools.ietf.org/html/draft-boucadair-intarea-host-identifier-scenarios-02 > > Those problems cover e.g. unwanted sharing of > o Blacklist for misbehaviour > o Enforced policy (tayloring service offering) > o Access denial due to failing service invoking > o Missing correct correlation between internal address:port and external > address:port required for policy issues > > > Prefix sharing issues draft, > > http://www.ietf.org/internet-drafts/draft-sarikaya-fmc-prefix-sharing-usecase-01.txt > > and more importantly, the next steps. > > > See you. > > Behcet > --e0cb4efe2d2e647ad004d7a6f6f9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Folks let's make it 5pm to enable people attending the plenary.

= So start at 5pm. The rest is the same.



On Sun, Mar 10, 2013 at 7:44 PM, Behcet Sarikaya &l= t;sarikaya2012@= gmail.com> wrote:
Folks, as Dirk mentioned, we will have a mee= ting in Orlando

on Monday March 11 at 6pm in Grand Sierra B room
We hope to discuss:
Address sharing issues draft,
http://tools.ietf.org/html/draft-boucadair-intarea-host= -identifier-scenarios-02

Those problems cover e.g. unwanted sharing of
o =A0Blacklist for misbehaviour
o =A0Enforced policy (tayloring service offering)
o =A0Access denial due to failing service invoking
o =A0Missing correct correlation between internal address:port and external= address:port required for policy issues
=A0

Prefix sharing issues draft,
http://www.ietf.org/internet-drafts/draft-sarikaya-fmc-prefi= x-sharing-usecase-01.txt

and more importantly, the next steps.


See you.

Behcet

--e0cb4efe2d2e647ad004d7a6f6f9-- From sarikaya2012@gmail.com Tue Mar 12 07:17:08 2013 Return-Path: X-Original-To: fmc@ietfa.amsl.com Delivered-To: fmc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18E1021F8940 for ; Tue, 12 Mar 2013 07:17:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.08 X-Spam-Level: X-Spam-Status: No, score=-2.08 tagged_above=-999 required=5 tests=[AWL=0.519, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QUaZdyn+O1CX for ; Tue, 12 Mar 2013 07:17:07 -0700 (PDT) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id DC06D21F8570 for ; Tue, 12 Mar 2013 07:17:06 -0700 (PDT) Received: by mail-la0-f53.google.com with SMTP id fr10so5186117lab.40 for ; Tue, 12 Mar 2013 07:17:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:date:message-id:subject:from:to:cc :content-type; bh=OUJXD66H0CdSJeJ/0yosaCRLeYOgK/QlefHD8al28Es=; b=Y9jltUr0x29vOuvNdErxFaQ15bRBcCldGYGMyIJxYvRkgbPQ2dWpsO4JMnEeTCOGaJ mB8UfczwTnyng5rxWlLy/Xm2AbSJ15X40QUxxev0TaAK96v313/tAa3iyHrcUcQYmf9h fQc0yOXwuug0h2GdDnZpOClhfV6pOIW4ZI66xi9+YDMDQPReTxsxD3stj4ifEywKjz/M cszNE0EVoVN1ut/Cy1NsOvuIfttzj/1hynnNw6y3COk0kHA5kk0laYGn62laQawSyocg yCsv+gzCGXYsHIPQs+VQteeAtQgUz7btWZenuMfQxu202yZrYBVmWmoYUHiGhOQovXqo di0Q== MIME-Version: 1.0 X-Received: by 10.152.148.133 with SMTP id ts5mr14208337lab.2.1363097766057; Tue, 12 Mar 2013 07:16:06 -0700 (PDT) Received: by 10.114.93.41 with HTTP; Tue, 12 Mar 2013 07:16:05 -0700 (PDT) Date: Tue, 12 Mar 2013 09:16:05 -0500 Message-ID: From: Behcet Sarikaya To: fmc@ietf.org Content-Type: multipart/alternative; boundary=e89a8f2346bd23dcb904d7baeee1 Cc: Brian Haberman , Pierrick Seite , Mohamed Boucadair , QUEIROZ Jaqueline OLNC/OLN , Dirk.von-Hugo@telekom.de Subject: [fmc] Minutes of the Bar BoF in Orlando on Monday X-BeenThere: fmc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Fixed Mobile Convergence List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 14:17:08 -0000 --e89a8f2346bd23dcb904d7baeee1 Content-Type: text/plain; charset=ISO-8859-1 Yes, we did have the meeting yesterday. Not many people attended but the meeting was pretty productive. Issues discussed: Industry involvement. Pierrick mentioned that other SDOs like BBF can be involved in matters related to the address sharing, aka host id, possibly by the next meeting in early June. Rudiger also agreed to provide help from his side. The aim here is to get them ask IETF for some solution work. There was agreement to work on the address sharing/prefix sharing problem as the main issue. UE mobility which was identified in the last year's BoF and multiple device issue will be possibly included. We also discussed mailing list activity. The list members are encouraged to keep the list active with technical discussions. We need more mails on the list. One thing I would like to add is to call for solution related drafts. If we have such drafts they could be the basis for more technical discussions on the list. Regards, Behcet On Mon, Mar 11, 2013 at 9:26 AM, Behcet Sarikaya wrote: > Folks let's make it 5pm to enable people attending the plenary. > > So start at 5pm. The rest is the same. > > > > On Sun, Mar 10, 2013 at 7:44 PM, Behcet Sarikaya wrote: > >> Folks, as Dirk mentioned, we will have a meeting in Orlando >> >> on Monday March 11 at 6pm in Grand Sierra B room >> >> We hope to discuss: >> Address sharing issues draft, >> >> http://tools.ietf.org/html/draft-boucadair-intarea-host-identifier-scenarios-02 >> >> Those problems cover e.g. unwanted sharing of >> o Blacklist for misbehaviour >> o Enforced policy (tayloring service offering) >> o Access denial due to failing service invoking >> o Missing correct correlation between internal address:port and external >> address:port required for policy issues >> >> >> Prefix sharing issues draft, >> >> http://www.ietf.org/internet-drafts/draft-sarikaya-fmc-prefix-sharing-usecase-01.txt >> >> and more importantly, the next steps. >> >> >> See you. >> >> Behcet >> > > --e89a8f2346bd23dcb904d7baeee1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yes, we did have the meeting yesterday. Not many people attended but the me= eting was pretty productive.

Issues discussed:

Industry invol= vement. Pierrick mentioned that other SDOs like BBF can be involved in matt= ers related to the address sharing, aka host id, possibly by the next meeti= ng in early June. Rudiger also agreed to provide help from his side. The ai= m here is to get them ask IETF for some solution work.

There was agreement to work on the address sharing/prefix sharing probl= em as the main issue. UE mobility which was identified in the last year'= ;s BoF and multiple device issue will be possibly included.

We also = discussed mailing list activity. The list members are encouraged to keep th= e list active with technical discussions. We need more mails on the list. <= br>
One thing I would like to add is to call for solution related drafts. I= f we have such drafts they could be the basis for more technical discussion= s on the list.

Regards,

Behcet

On Mon, Mar 11, 2013 at 9:26 AM, Behcet Sarikaya <sarikaya2012@gmail.= com> wrote:
Folks let's make it 5pm to enable people attending the plenary.

= So start at 5pm. The rest is the same.



On Sun, Mar 10, 2013 at 7:44 PM, Behcet Sarikaya &l= t;sarikaya2012@= gmail.com> wrote:
Folks, as Dirk mentioned, we will have a mee= ting in Orlando

on Monday March 11 at 6pm in Grand Sierra B room
We hope to discuss:
Address sharing issues draft,
http://tools.ietf.org/html/draft-boucadair-intarea-host= -identifier-scenarios-02

Those problems cover e.g. unwanted sharing of
o =A0Blacklist for misbehaviour
o =A0Enforced policy (tayloring service offering)
o =A0Access denial due to failing service invoking
o =A0Missing correct correlation between internal address:port and external= address:port required for policy issues
=A0

Prefix sharing issues draft,
http://www.ietf.org/internet-drafts/draft-sarikaya-fmc-prefi= x-sharing-usecase-01.txt

and more importantly, the next steps.


See you.

Behcet


--e89a8f2346bd23dcb904d7baeee1-- From pierrick.seite@orange.com Wed Mar 13 07:40:18 2013 Return-Path: X-Original-To: fmc@ietfa.amsl.com Delivered-To: fmc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C1E621F8A41 for ; Wed, 13 Mar 2013 07:40:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.518 X-Spam-Level: X-Spam-Status: No, score=-1.518 tagged_above=-999 required=5 tests=[AWL=1.080, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0jdS42NaKDga for ; Wed, 13 Mar 2013 07:40:17 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 8C5C321F86C8 for ; Wed, 13 Mar 2013 07:40:16 -0700 (PDT) Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 0CFD03241F6; Wed, 13 Mar 2013 15:40:15 +0100 (CET) Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id DF6C7238055; Wed, 13 Mar 2013 15:40:14 +0100 (CET) Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Wed, 13 Mar 2013 15:40:14 +0100 From: To: "Dirk.von-Hugo@telekom.de" , "byjupg@cisco.com" , "fmc@ietf.org" Thread-Topic: [fmc] New Version Notification for draft-pularikkal-opsawg-lawful-intercept-spwifi-00.txt Thread-Index: AQHODiY284CHMnBHT0i4Jwn8r08PTJiVyNyggA37+hA= Date: Wed, 13 Mar 2013 14:40:14 +0000 Message-ID: <17725_1363185614_51408FCE_17725_1372_1_81C77F07008CA24F9783A98CFD706F710B1719@PEXCVZYM12.corporate.adroot.infra.ftgroup> References: <20130218201547.25429.90513.idtracker@ietfa.amsl.com> <7FC7CEE8B5E132468B8AC6F812F6AE171B86BD@xmb-rcd-x13.cisco.com> <05C81A773E48DD49B181B04BA21A342A2BA2D5E0CC@HE113484.emea1.cds.t-internal.com> In-Reply-To: <05C81A773E48DD49B181B04BA21A342A2BA2D5E0CC@HE113484.emea1.cds.t-internal.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.197.38.3] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.5.94520 Cc: "sgundave@cisco.com" , "sarikaya2012@gmail.com" Subject: Re: [fmc] New Version Notification for draft-pularikkal-opsawg-lawful-intercept-spwifi-00.txt X-BeenThere: fmc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Fixed Mobile Convergence List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 14:40:18 -0000 Hi Byju, Thanks for sharing this document and please apologize for my very late answ= er :-) I've read your document with the operator hat and outside the FMC sc= ope, as I think your work is more generic than FMC. Firstly, I'd say that t= his contribution well reflects current evolution of wifi architectures and = LI considerations are in line with operator practices. However, the goal of= the document is not clear to me. Architecture considerations are very inte= resting and relevant but what do you expect from the IETF? Do you way to go= for a best practices document or do you have protocol extensions in mind?= =20 Then, I've just clarifying questions. Why don't you consider architecture s= cenarios without WAC ? The document is limited to the case where the user session is not active wh= en LI is configured; what if the session is ongoing? In the scenario with inter-operator roaming, it's assumed that it's the WAG= will be responsible for sending the authorization request towards the roam= ing partner's AAA server. So, you implicitly assume AAA proxy in the WAG, r= ight? This assumption may not be always valid. So wouldn't it rather be the= AAA in the WiFi Operator's network responsible for contacting the roaming = partner's AAA server also for the authorization purposes? As already mentioned in the I-D, it seems that it may get quite complicated= in the case when WAG would be capable of SIPTO-like functionality. do you = plan to give more details on this topic? CU, Pierrick > -----Message d'origine----- > De=A0: fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] De la part de > Dirk.von-Hugo@telekom.de > Envoy=E9=A0: lundi 4 mars 2013 17:59 > =C0=A0: byjupg@cisco.com; fmc@ietf.org > Cc=A0: sarikaya2012@gmail.com; sgundave@cisco.com > Objet=A0: Re: [fmc] New Version Notification for draft-pularikkal-opsawg- > lawful-intercept-spwifi-00.txt >=20 > Dear Byju, all, >=20 > Thanks for sharing your considerations with this list. >=20 > I think that this draft also in a wider sense may add to the use cases > for the host identification issue we have considered so far as a > typical fmc server (here the Wireless Access Gateway, WAG) originated > challenge, i.e. lawful intercept to require a unique Target identifier > to locate and address a user across WiFi and other access networks. > (BTW I suggest not to use 'Home Gateway' for LMA or similar subscriber > anchor point as it may be mixed up with 'Residential Gateway' at a > users' home) >=20 > Furthermore we had the IPv6 prefix sharing use case > http://www.ietf.org/internet-drafts/draft-sarikaya-fmc-prefix-sharing- > usecase-01.txt for residential gateways where some networks may be > unable to assign different prefixes to different visiting mobile hosts. >=20 > Other - more general - fmc related issues arising from application > servers e.g. used both during fixed and mobile access to same service > also underline the need for unique host identification. A plurality of > use cases are described in http://tools.ietf.org/html/draft-boucadair- > intarea-host-identifier-scenarios-02. As Med mentions in that draft > typical hurdles to service usage may occur to all hosts with same IP > address which also applies to fmc scenarios. Those problems cover e.g. > unwanted sharing of o Blacklist for misbehaviour o Enforced policy > (tayloring service offering) o Access denial due to failing service > invoking o Missing correct correlation between internal address:port > and external address:port required for policy issues >=20 > Finally the Unified User Identification use case (here mainly related > to NAT/CGN) is described in http://www.ietf.org/internet-drafts/draft- > sun-fmc-use-case-01.txt. >=20 > I would invite you to discuss details on the host ID use cases and > further ideas how to proceed on this list. In any case there will be an > FMC-related BarBOF organised in Orlando ... Further details will be > announced shortly (although unfortunately I myself will be unable to > attend the upcoming meeting ;-() Thanks! >=20 > Best regards > Dirk >=20 > -----Urspr=FCngliche Nachricht----- > Von: Byju Pularikkal (byjupg) [mailto:byjupg@cisco.com] > Gesendet: Montag, 18. Februar 2013 23:21 > An: fmc@ietf.org > Cc: Sri Gundavelli (sgundave) > Betreff: FW: New Version Notification for draft-pularikkal-opsawg- > lawful-intercept-spwifi-00.txt >=20 > Hello, >=20 > Attached is a document on LI Architecture for SP WIFI. Comments > appreciated >=20 >=20 > Thanks & Regards >=20 > Byju >=20 >=20 >=20 >=20 > On 2/18/13 3:15 PM, "internet-drafts@ietf.org" drafts@ietf.org> > wrote: >=20 > > > >A new version of I-D, > >draft-pularikkal-opsawg-lawful-intercept-spwifi-00.txt > >has been successfully submitted by Byju Pularikkal and posted to the > >IETF repository. > > > >Filename: draft-pularikkal-opsawg-lawful-intercept-spwifi > >Revision: 00 > >Title: Lawful-Intercept Support for SP Wi-Fi Deployments > >Creation date: 2013-02-18 > >Group: Individual Submission > >Number of pages: 20 > >URL: > >http://www.ietf.org/internet-drafts/draft-pularikkal-opsawg-lawful- > inte > >rce > >pt-spwifi-00.txt > >Status: > >http://datatracker.ietf.org/doc/draft-pularikkal-opsawg-lawful- > intercep > >t-s > >pwifi > >Htmlized: > >http://tools.ietf.org/html/draft-pularikkal-opsawg-lawful-intercept- > spw > >ifi > >-00 > > > > > >Abstract: > > Lawful Intercept stands for legally authorized capture & delivery > of > > subscriber communications data by a communications provider to a > law > > enforcement agency.This document describes Generic Lawful Intercept > > Architecture Models & implementation considerations for Service > > Provider Wi-Fi deployments. > > > > > > > > > > > >The IETF Secretariat > > >=20 > _______________________________________________ > fmc mailing list > fmc@ietf.org > https://www.ietf.org/mailman/listinfo/fmc ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete al= tere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for message= s that have been modified, changed or falsified. Thank you.