
From pierrick.seite@orange.com  Wed Aug  1 01:59:10 2012
Return-Path: <pierrick.seite@orange.com>
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 ACF6B21F870F for <fmc@ietfa.amsl.com>; Wed,  1 Aug 2012 01:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Level: 
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.019,  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 Rdij+hnSFCuE for <fmc@ietfa.amsl.com>; Wed,  1 Aug 2012 01:59:09 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 638E021F870A for <fmc@ietf.org>; Wed,  1 Aug 2012 01:59:09 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id BB901324689; Wed,  1 Aug 2012 10:59:08 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id A085B35C06C; Wed,  1 Aug 2012 10:59:08 +0200 (CEST)
Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0298.004; Wed, 1 Aug 2012 10:59:08 +0200
From: <pierrick.seite@orange.com>
To: "'sarikaya@ieee.org'" <sarikaya@ieee.org>, "fmc@ietf.org" <fmc@ietf.org>,  'Hui Deng' <denghui02@gmail.com>
Thread-Topic: [fmc] Minutes v2 of the side meeting on 7/30/12
Thread-Index: AQHNb2ArA2OUujURJkyCW1UZi+1y0pdEpE4g
Date: Wed, 1 Aug 2012 08:59:08 +0000
Message-ID: <3484_1343811548_5018EFDC_3484_5616_1_81C77F07008CA24F9783A98CFD706F7102EF1A@PEXCVZYM12.corporate.adroot.infra.ftgroup>
References: <CAC8QAccGfoHL7SC+5t3KDqhmtizhda8kDz4xf9M+taoLQRbJ=Q@mail.gmail.com>
In-Reply-To: <CAC8QAccGfoHL7SC+5t3KDqhmtizhda8kDz4xf9M+taoLQRbJ=Q@mail.gmail.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.6]
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: 2012.8.1.71520
Subject: Re: [fmc] Minutes v2 of the side meeting on 7/30/12
X-BeenThere: fmc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Fixed Mobile Convergence <fmc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fmc>, <mailto:fmc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fmc>
List-Post: <mailto:fmc@ietf.org>
List-Help: <mailto:fmc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fmc>, <mailto:fmc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 08:59:10 -0000

Hi,=20

I'm surprised to see that I was supposed to own the access selection use-ca=
se since, I repeat myself, I do not see the need for specific work here. Le=
t me clarify. Access selection is clearly a key feature for multiple access=
es systems but this topic is already covered in different SDOs (3GPP/ANDSF,=
 OMA-DM/OpenCM API), including IETF within MIF. So, IMHO, it cannot be a mo=
tivation for new WG.=20

Pierrick

> -----Message d'origine-----
> De=A0: fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] De la part de
> Behcet Sarikaya
> Envoy=E9=A0: mardi 31 juillet 2012 23:05
> =C0=A0: fmc@ietf.org
> Objet=A0: [fmc] Minutes v2 of the side meeting on 7/30/12
>=20
> With Dave Allan's corrections.
>=20
> On Mon, Jul 30, 2012 at 6:55 PM, Behcet Sarikaya
> <sarikaya2012@gmail.com> wrote:
> > Folks,
> >
> > The minutes are attached.
> >
> > Many thanks to Pete McCann for taking these minutes!
> >
> > Regards,
> >
> > Behcet

___________________________________________________________________________=
______________________________________________

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.


From Dirk.von-Hugo@telekom.de  Wed Aug  1 08:05:58 2012
Return-Path: <Dirk.von-Hugo@telekom.de>
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 ADDCE11E8100 for <fmc@ietfa.amsl.com>; Wed,  1 Aug 2012 08:05:58 -0700 (PDT)
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=[AWL=0.000,  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 6g4O06CZYCLl for <fmc@ietfa.amsl.com>; Wed,  1 Aug 2012 08:05:58 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id BE89011E810E for <fmc@ietf.org>; Wed,  1 Aug 2012 08:05:57 -0700 (PDT)
Received: from he113470.emea1.cds.t-internal.com ([10.134.93.128]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 01 Aug 2012 17:05:55 +0200
Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE113470.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 1 Aug 2012 17:05:55 +0200
From: <Dirk.von-Hugo@telekom.de>
To: <pierrick.seite@orange.com>, <sarikaya@ieee.org>, <fmc@ietf.org>, <denghui02@gmail.com>
Date: Wed, 1 Aug 2012 17:05:54 +0200
Thread-Topic: [fmc] Minutes v2 of the side meeting on 7/30/12
Thread-Index: AQHNb2ArA2OUujURJkyCW1UZi+1y0pdEpE4ggABD4sA=
Message-ID: <05C81A773E48DD49B181B04BA21A342A27C42B128A@HE113484.emea1.cds.t-internal.com>
References: <CAC8QAccGfoHL7SC+5t3KDqhmtizhda8kDz4xf9M+taoLQRbJ=Q@mail.gmail.com> <3484_1343811548_5018EFDC_3484_5616_1_81C77F07008CA24F9783A98CFD706F7102EF1A@PEXCVZYM12.corporate.adroot.infra.ftgroup>
In-Reply-To: <3484_1343811548_5018EFDC_3484_5616_1_81C77F07008CA24F9783A98CFD706F7102EF1A@PEXCVZYM12.corporate.adroot.infra.ftgroup>
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
Subject: Re: [fmc] Minutes v2 of the side meeting on 7/30/12
X-BeenThere: fmc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Fixed Mobile Convergence <fmc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fmc>, <mailto:fmc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fmc>
List-Post: <mailto:fmc@ietf.org>
List-Help: <mailto:fmc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fmc>, <mailto:fmc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 15:05:58 -0000

Hi Pierrick,
I agree that access selection is a topic in scope of several organizations,=
 but 3GPP and OMA is no show stopper IMO since evenso there is not much pra=
ctice to be observed. However I agree (and I think this was also mentioned =
in the bar-BOF) that the work done within MIF has to be carefully analysed =
to decide whether there is still an open gap or not. And honestly, in case =
of an identified gap MIF would be the first address to address this ...

Best regards
Dirk

-----Urspr=FCngliche Nachricht-----
Von: fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] Im Auftrag von pier=
rick.seite@orange.com
Gesendet: Mittwoch, 1. August 2012 10:59
An: 'sarikaya@ieee.org'; fmc@ietf.org; 'Hui Deng'
Betreff: Re: [fmc] Minutes v2 of the side meeting on 7/30/12

Hi,

I'm surprised to see that I was supposed to own the access selection use-ca=
se since, I repeat myself, I do not see the need for specific work here. Le=
t me clarify. Access selection is clearly a key feature for multiple access=
es systems but this topic is already covered in different SDOs (3GPP/ANDSF,=
 OMA-DM/OpenCM API), including IETF within MIF. So, IMHO, it cannot be a mo=
tivation for new WG.

Pierrick

> -----Message d'origine-----
> De : fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] De la part de
> Behcet Sarikaya
> Envoy=E9 : mardi 31 juillet 2012 23:05
> =C0 : fmc@ietf.org
> Objet : [fmc] Minutes v2 of the side meeting on 7/30/12
>
> With Dave Allan's corrections.
>
> On Mon, Jul 30, 2012 at 6:55 PM, Behcet Sarikaya
> <sarikaya2012@gmail.com> wrote:
> > Folks,
> >
> > The minutes are attached.
> >
> > Many thanks to Pete McCann for taking these minutes!
> >
> > Regards,
> >
> > Behcet

___________________________________________________________________________=
______________________________________________

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.

_______________________________________________
fmc mailing list
fmc@ietf.org
https://www.ietf.org/mailman/listinfo/fmc

From pierrick.seite@orange.com  Thu Aug  2 01:12:25 2012
Return-Path: <pierrick.seite@orange.com>
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 B6F2921F8D37 for <fmc@ietfa.amsl.com>; Thu,  2 Aug 2012 01:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.017,  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 1F+wN2BbxM+2 for <fmc@ietfa.amsl.com>; Thu,  2 Aug 2012 01:12:24 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id E81EF21F8DFC for <fmc@ietf.org>; Thu,  2 Aug 2012 01:12:23 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id D40FC18C485; Thu,  2 Aug 2012 10:12:21 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id B1A6435C05A; Thu,  2 Aug 2012 10:12:21 +0200 (CEST)
Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0298.004; Thu, 2 Aug 2012 10:12:21 +0200
From: <pierrick.seite@orange.com>
To: "'Dirk.von-Hugo@telekom.de'" <Dirk.von-Hugo@telekom.de>, "sarikaya@ieee.org" <sarikaya@ieee.org>, "fmc@ietf.org" <fmc@ietf.org>,  "denghui02@gmail.com" <denghui02@gmail.com>
Thread-Topic: [fmc] Minutes v2 of the side meeting on 7/30/12
Thread-Index: AQHNb2ArA2OUujURJkyCW1UZi+1y0pdEpE4ggABD4sCAAUXEEA==
Date: Thu, 2 Aug 2012 08:12:21 +0000
Message-ID: <20149_1343895141_501A3665_20149_10684_1_81C77F07008CA24F9783A98CFD706F7102F7DB@PEXCVZYM12.corporate.adroot.infra.ftgroup>
References: <CAC8QAccGfoHL7SC+5t3KDqhmtizhda8kDz4xf9M+taoLQRbJ=Q@mail.gmail.com> <3484_1343811548_5018EFDC_3484_5616_1_81C77F07008CA24F9783A98CFD706F7102EF1A@PEXCVZYM12.corporate.adroot.infra.ftgroup> <05C81A773E48DD49B181B04BA21A342A27C42B128A@HE113484.emea1.cds.t-internal.com>
In-Reply-To: <05C81A773E48DD49B181B04BA21A342A27C42B128A@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.2]
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: 2012.8.2.74519
Subject: Re: [fmc] Minutes v2 of the side meeting on 7/30/12
X-BeenThere: fmc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Fixed Mobile Convergence <fmc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fmc>, <mailto:fmc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fmc>
List-Post: <mailto:fmc@ietf.org>
List-Help: <mailto:fmc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fmc>, <mailto:fmc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 08:12:26 -0000

Hi Dirk,

Thanks for the clarification; we are in agreement.

BR,
Pierrick

> -----Message d'origine-----
> De=A0: Dirk.von-Hugo@telekom.de [mailto:Dirk.von-Hugo@telekom.de]
> Envoy=E9=A0: mercredi 1 ao=FBt 2012 17:06
> =C0=A0: SEITE Pierrick RD-RESA; sarikaya@ieee.org; fmc@ietf.org;
> denghui02@gmail.com
> Objet=A0: AW: [fmc] Minutes v2 of the side meeting on 7/30/12
>=20
> Hi Pierrick,
> I agree that access selection is a topic in scope of several
> organizations, but 3GPP and OMA is no show stopper IMO since evenso
> there is not much practice to be observed. However I agree (and I think
> this was also mentioned in the bar-BOF) that the work done within MIF
> has to be carefully analysed to decide whether there is still an open
> gap or not. And honestly, in case of an identified gap MIF would be the
> first address to address this ...
>=20
> Best regards
> Dirk
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] Im Auftrag von
> pierrick.seite@orange.com
> Gesendet: Mittwoch, 1. August 2012 10:59
> An: 'sarikaya@ieee.org'; fmc@ietf.org; 'Hui Deng'
> Betreff: Re: [fmc] Minutes v2 of the side meeting on 7/30/12
>=20
> Hi,
>=20
> I'm surprised to see that I was supposed to own the access selection
> use-case since, I repeat myself, I do not see the need for specific
> work here. Let me clarify. Access selection is clearly a key feature
> for multiple accesses systems but this topic is already covered in
> different SDOs (3GPP/ANDSF, OMA-DM/OpenCM API), including IETF within
> MIF. So, IMHO, it cannot be a motivation for new WG.
>=20
> Pierrick
>=20
> > -----Message d'origine-----
> > De : fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] De la part de
> > Behcet Sarikaya Envoy=E9 : mardi 31 juillet 2012 23:05 =C0 : fmc@ietf.o=
rg
> > Objet : [fmc] Minutes v2 of the side meeting on 7/30/12
> >
> > With Dave Allan's corrections.
> >
> > On Mon, Jul 30, 2012 at 6:55 PM, Behcet Sarikaya
> > <sarikaya2012@gmail.com> wrote:
> > > Folks,
> > >
> > > The minutes are attached.
> > >
> > > Many thanks to Pete McCann for taking these minutes!
> > >
> > > Regards,
> > >
> > > Behcet
>=20
> _______________________________________________________________________
> __________________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles 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 electroniques etant susceptibles
> d'alteration, France Telecom - Orange decline toute responsabilite si
> ce message a ete altere, deforme ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or privileged
> information 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
> delete this message and its attachments.
> As emails may be altered, France Telecom - Orange is not liable for
> messages that have been modified, changed or falsified.
> Thank you.
>=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.


From sarikaya2012@gmail.com  Mon Aug 13 12:02:44 2012
Return-Path: <sarikaya2012@gmail.com>
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 87C3621F86B2 for <fmc@ietfa.amsl.com>; Mon, 13 Aug 2012 12:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.558
X-Spam-Level: 
X-Spam-Status: No, score=-3.558 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599, 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 8B0Bf7H2dexg for <fmc@ietfa.amsl.com>; Mon, 13 Aug 2012 12:02:44 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 07BD121F85F7 for <fmc@ietf.org>; Mon, 13 Aug 2012 12:02:43 -0700 (PDT)
Received: by yenm5 with SMTP id m5so3901506yen.31 for <fmc@ietf.org>; Mon, 13 Aug 2012 12:02:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type; bh=kF2VZbiZLJtGW+dUnkqiwKXwzeOkORvcA2J4k8Bl7NI=; b=WYYukStqye5btchN7FuoNMPPwuFnziravUS8Ewgd6oof4Xx5tTmJvtJslWIMRp/AF7 l/0HqY52dbiiD2qiiHD25FYW3GOmEOWpG/59xhw7qh8uZ0P7nCwDAOcMuItPTnV9KfhU LUJ2lHbZJYmR2uk96/kSlq/k6hKXiMuFok9j7KBtFsb2KxQ/qC2z4iyBME/LYIHdpdr6 NJu83/XcO7JdwmC/FbuDvzyw9eQXhezrihKxLQOfDlR+0Els17vsZ4Za56wINuuyizEA mHSU+ZALPbgkLQC69oICTUa7KsiK+B+yLmBfUrxW4w+hyWzw0v5oo4VqYPsT+C4bK7Dp 5rIg==
MIME-Version: 1.0
Received: by 10.50.34.131 with SMTP id z3mr6991027igi.45.1344884563175; Mon, 13 Aug 2012 12:02:43 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Mon, 13 Aug 2012 12:02:43 -0700 (PDT)
Date: Mon, 13 Aug 2012 14:02:43 -0500
Message-ID: <CAC8QAcdNDe8K+gi0Vka0wbxTwYAhVfxL4d9PJNpAyEBmfz-8kA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: pierrick.seite@orange.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: "denghui02@gmail.com" <denghui02@gmail.com>, "fmc@ietf.org" <fmc@ietf.org>, "Dirk.von-Hugo@telekom.de" <Dirk.von-Hugo@telekom.de>
Subject: [fmc] access selection
X-BeenThere: fmc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Fixed Mobile Convergence <fmc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fmc>, <mailto:fmc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fmc>
List-Post: <mailto:fmc@ietf.org>
List-Help: <mailto:fmc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fmc>, <mailto:fmc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 19:02:44 -0000

Hi Pierrick,

Please see inline.


Regards,


Behcet


>>
>> I'm surprised to see that I was supposed to own the access selection
>> use-case since, I repeat myself, I do not see the need for specific
>> work here. Let me clarify. Access selection is clearly a key feature
>> for multiple accesses systems but this topic is already covered in
>> different SDOs (3GPP/ANDSF, OMA-DM/OpenCM API), including IETF within
>> MIF.

I think that the discussions we had on mif list made it clear that mif
API is not being designed as a solution to the access network
selection. Mif API will tell the application how many networks it can
connect to on each interface.

So access selection is not being covered by IETF.
What do you think on revising the access selection use case?

From Dirk.von-Hugo@telekom.de  Fri Aug 24 08:56:14 2012
Return-Path: <Dirk.von-Hugo@telekom.de>
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 8D0D521F86AA for <fmc@ietfa.amsl.com>; Fri, 24 Aug 2012 08:56:14 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X0Z8TCAoHXbS for <fmc@ietfa.amsl.com>; Fri, 24 Aug 2012 08:56:13 -0700 (PDT)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by ietfa.amsl.com (Postfix) with ESMTP id 62A1321F86A2 for <fmc@ietf.org>; Fri, 24 Aug 2012 08:56:13 -0700 (PDT)
Received: from he113472.emea1.cds.t-internal.com ([10.134.93.130]) by tcmail71.telekom.de with ESMTP/TLS/AES128-SHA; 24 Aug 2012 17:56:11 +0200
Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE113472.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 24 Aug 2012 17:56:11 +0200
From: <Dirk.von-Hugo@telekom.de>
To: <sarikaya@ieee.org>, <fmc@ietf.org>
Date: Fri, 24 Aug 2012 17:56:09 +0200
Thread-Topic: [fmc] Minutes v2 of the side meeting on 7/30/12
Thread-Index: Ac1vYCvXx+A7ee4yRySmgk4S/29XMQSrYxSw
Message-ID: <05C81A773E48DD49B181B04BA21A342A27C48EF434@HE113484.emea1.cds.t-internal.com>
References: <CAC8QAccGfoHL7SC+5t3KDqhmtizhda8kDz4xf9M+taoLQRbJ=Q@mail.gmail.com>
In-Reply-To: <CAC8QAccGfoHL7SC+5t3KDqhmtizhda8kDz4xf9M+taoLQRbJ=Q@mail.gmail.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
Subject: Re: [fmc] Minutes v2 of the side meeting on 7/30/12
X-BeenThere: fmc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Fixed Mobile Convergence <fmc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fmc>, <mailto:fmc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fmc>
List-Post: <mailto:fmc@ietf.org>
List-Help: <mailto:fmc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fmc>, <mailto:fmc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 15:56:14 -0000

Dear all,
>From the minutes the conclusion of the meeting for me is that the major use=
 cases to visualize the need to work on solutions for a fixed mobile interw=
orking scenario are the following:

- common UE identification especially in the fixed network (in relation to =
NAT reversal and in case of handover)
- UE Mobility support in WiFi beyond CAPWAP radio resource management (incl=
uding also the handover issue from and to mobile network)
- access selection issues beyond work of MIF (detection) - including polici=
es and considering actual link quality of connection on different radio tec=
hnologies (cellular and WiFi) which is also related to required and agreed =
on service quality

IMHO these might be the topics to detail and clarify until Atlanta meeting.

Any other opinion or comment?

Thanks and have a nice weekend

Best regards
Dirk

-----Urspr=FCngliche Nachricht-----
Von: fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] Im Auftrag von Behc=
et Sarikaya
Gesendet: Dienstag, 31. Juli 2012 23:05
An: fmc@ietf.org
Betreff: [fmc] Minutes v2 of the side meeting on 7/30/12

With Dave Allan's corrections.

On Mon, Jul 30, 2012 at 6:55 PM, Behcet Sarikaya <sarikaya2012@gmail.com> w=
rote:
> Folks,
>
> The minutes are attached.
>
> Many thanks to Pete McCann for taking these minutes!
>
> Regards,
>
> Behcet

From tso@zteusa.com  Sat Aug 25 23:10:24 2012
Return-Path: <tso@zteusa.com>
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 1685C21F84F7; Sat, 25 Aug 2012 23:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.367
X-Spam-Level: *
X-Spam-Status: No, score=1.367 tagged_above=-999 required=5 tests=[AWL=1.129,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_BAD_ID=2.837]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mtp9nmlPzT3l; Sat, 25 Aug 2012 23:10:23 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 9199921F84A1; Sat, 25 Aug 2012 23:10:19 -0700 (PDT)
Received: from [10.30.3.21] by mx5.zte.com.cn with surfront esmtp id 232552816692506(version=TLSv1/SSLv3 cipher=SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA bits=128 verify=NO);  Sun, 26 Aug 2012 14:03:59 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id q7Q6A7oE060193; Sun, 26 Aug 2012 14:10:07 +0800 (GMT-8) (envelope-from tso@zteusa.com)
In-Reply-To: <05C81A773E48DD49B181B04BA21A342A27C48EF434@HE113484.emea1.cds.t-internal.com>
References: <CAC8QAccGfoHL7SC+5t3KDqhmtizhda8kDz4xf9M+taoLQRbJ=Q@mail.gmail.com> <05C81A773E48DD49B181B04BA21A342A27C48EF434@HE113484.emea1.cds.t-internal.com>
To: <Dirk.von-Hugo@telekom.de>
MIME-Version: 1.0
X-KeepSent: 0D2F190D:2B331677-88257A66:00215E9A; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.1 September 28, 2009
Message-ID: <OF0D2F190D.2B331677-ON88257A66.00215E9A-88257A66.0021E67A@zte.com.cn>
From: tso@zteusa.com
Date: Sat, 25 Aug 2012 23:09:34 -0700
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-08-26 14:09:57, Serialize complete at 2012-08-26 14:09:57
Content-Type: multipart/alternative; boundary="=_alternative 0021E67888257A66_="
X-MAIL: mse02.zte.com.cn q7Q6A7oE060193
Cc: sarikaya@ieee.org, fmc-bounces@ietf.org, fmc@ietf.org
Subject: Re: [fmc] Minutes v2 of the side meeting on 7/30/12
X-BeenThere: fmc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Fixed Mobile Convergence <fmc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fmc>, <mailto:fmc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fmc>
List-Post: <mailto:fmc@ietf.org>
List-Help: <mailto:fmc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fmc>, <mailto:fmc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Aug 2012 06:10:24 -0000

This is a multipart message in MIME format.
--=_alternative 0021E67888257A66_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear Dirk,=20

Sincerely thanks for your kind feedback.=20

For the items 2 and 3 below, from 3GPP perspectives, there are two=20
separate working items (FS-WORM and WLAN-NSD) which have been started in=20
Rel-12 to address these two issues.=20

Could you please share with us a bit more details, what are the "generic"=20
considerations and requirements from IETF perspective, that are beyond=20
3GPP and WFA for the items 2 and 3 below which need IETF's effort to work=20
on the solutions.=20

Sincerely thanks in advance.=20
Tricci=20




<Dirk.von-Hugo@telekom.de>=20
Sent by: fmc-bounces@ietf.org
08/24/2012 08:56 AM

To
<sarikaya@ieee.org>, <fmc@ietf.org>
cc

Subject
Re: [fmc] Minutes v2 of the side meeting on 7/30/12






Dear all,
>From the minutes the conclusion of the meeting for me is that the major=20
use cases to visualize the need to work on solutions for a fixed mobile=20
interworking scenario are the following:

- common UE identification especially in the fixed network (in relation to =

NAT reversal and in case of handover)
- UE Mobility support in WiFi beyond CAPWAP radio resource management=20
(including also the handover issue from and to mobile network)
- access selection issues beyond work of MIF (detection) - including=20
policies and considering actual link quality of connection on different=20
radio technologies (cellular and WiFi) which is also related to required=20
and agreed on service quality

IMHO these might be the topics to detail and clarify until Atlanta=20
meeting.

Any other opinion or comment?

Thanks and have a nice weekend

Best regards
Dirk

-----Urspr=FCngliche Nachricht-----
Von: fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] Im Auftrag von=20
Behcet Sarikaya
Gesendet: Dienstag, 31. Juli 2012 23:05
An: fmc@ietf.org
Betreff: [fmc] Minutes v2 of the side meeting on 7/30/12

With Dave Allan's corrections.

On Mon, Jul 30, 2012 at 6:55 PM, Behcet Sarikaya <sarikaya2012@gmail.com>=20
wrote:
> Folks,
>
> The minutes are attached.
>
> Many thanks to Pete McCann for taking these minutes!
>
> Regards,
>
> Behcet
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
fmc mailing list
fmc@ietf.org
https://www.ietf.org/mailman/listinfo/fmc



--=_alternative 0021E67888257A66_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<font size=3D2 face=3D"sans-serif">Dear Dirk, </font>
<br>
<br><font size=3D2 face=3D"sans-serif">Sincerely thanks for your kind feedb=
ack.
&nbsp;</font>
<br>
<br><font size=3D2 face=3D"sans-serif">For the items 2 and 3 below, from 3G=
PP
perspectives, there are two separate working items (FS-WORM and WLAN-NSD)
which have been started in Rel-12 to address these two issues. &nbsp;</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Could you please share with us a bit
more details, what are the &quot;generic&quot; considerations and requireme=
nts
from IETF perspective, that are beyond 3GPP and WFA for the items 2 and
3 below which need IETF's effort to work on the solutions. </font>
<br>
<br><font size=3D2 face=3D"sans-serif">Sincerely thanks in advance. </font>
<br><font size=3D2 face=3D"sans-serif">Tricci </font>
<br>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td width=3D35%><font size=3D1 face=3D"sans-serif"><b>&lt;Dirk.von-Hugo@tel=
ekom.de&gt;</b>
</font>
<br><font size=3D1 face=3D"sans-serif">Sent by: fmc-bounces@ietf.org</font>
<p><font size=3D1 face=3D"sans-serif">08/24/2012 08:56 AM</font>
<td width=3D64%>
<table width=3D100%>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">To</font></div>
<td><font size=3D1 face=3D"sans-serif">&lt;sarikaya@ieee.org&gt;, &lt;fmc@i=
etf.org&gt;</font>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">cc</font></div>
<td>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">Subject</font></div>
<td><font size=3D1 face=3D"sans-serif">Re: [fmc] Minutes v2 of the side mee=
ting
on 7/30/12</font></table>
<br>
<table>
<tr valign=3Dtop>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=3D2>Dear all,<br>
>From the minutes the conclusion of the meeting for me is that the major
use cases to visualize the need to work on solutions for a fixed mobile
interworking scenario are the following:<br>
<br>
- common UE identification especially in the fixed network (in relation
to NAT reversal and in case of handover)<br>
- UE Mobility support in WiFi beyond CAPWAP radio resource management (incl=
uding
also the handover issue from and to mobile network)<br>
- access selection issues beyond work of MIF (detection) - including polici=
es
and considering actual link quality of connection on different radio techno=
logies
(cellular and WiFi) which is also related to required and agreed on service
quality<br>
<br>
IMHO these might be the topics to detail and clarify until Atlanta meeting.=
<br>
<br>
Any other opinion or comment?<br>
<br>
Thanks and have a nice weekend<br>
<br>
Best regards<br>
Dirk<br>
<br>
-----Urspr=FCngliche Nachricht-----<br>
Von: fmc-bounces@ietf.org [</font></tt><a href=3D"mailto:fmc-bounces@ietf.o=
rg"><tt><font size=3D2>mailto:fmc-bounces@ietf.org</font></tt></a><tt><font=
 size=3D2>]
Im Auftrag von Behcet Sarikaya<br>
Gesendet: Dienstag, 31. Juli 2012 23:05<br>
An: fmc@ietf.org<br>
Betreff: [fmc] Minutes v2 of the side meeting on 7/30/12<br>
<br>
With Dave Allan's corrections.<br>
<br>
On Mon, Jul 30, 2012 at 6:55 PM, Behcet Sarikaya &lt;sarikaya2012@gmail.com=
&gt;
wrote:<br>
&gt; Folks,<br>
&gt;<br>
&gt; The minutes are attached.<br>
&gt;<br>
&gt; Many thanks to Pete McCann for taking these minutes!<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Behcet<br>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
fmc mailing list<br>
fmc@ietf.org<br>
</font></tt><a href=3Dhttps://www.ietf.org/mailman/listinfo/fmc><tt><font s=
ize=3D2>https://www.ietf.org/mailman/listinfo/fmc</font></tt></a><tt><font =
size=3D2><br>
<br>
</font></tt>
<br>
--=_alternative 0021E67888257A66_=--


From Dirk.von-Hugo@telekom.de  Mon Aug 27 05:09:16 2012
Return-Path: <Dirk.von-Hugo@telekom.de>
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 B816621F8619; Mon, 27 Aug 2012 05:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.948
X-Spam-Level: 
X-Spam-Status: No, score=-0.948 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, MANGLED_LOAN=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BtqSgdyrGdlC; Mon, 27 Aug 2012 05:09:16 -0700 (PDT)
Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by ietfa.amsl.com (Postfix) with ESMTP id 3CDEB21F8600; Mon, 27 Aug 2012 05:09:14 -0700 (PDT)
Received: from he111628.emea1.cds.t-internal.com ([10.134.93.20]) by tcmail81.telekom.de with ESMTP/TLS/AES128-SHA; 27 Aug 2012 14:09:11 +0200
Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE111628.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 27 Aug 2012 14:09:11 +0200
From: <Dirk.von-Hugo@telekom.de>
To: <tso@zteusa.com>
Date: Mon, 27 Aug 2012 14:09:08 +0200
Thread-Topic: [fmc] Minutes v2 of the side meeting on 7/30/12 
Thread-Index: Ac2DUXdzfhiwVx0yQ7yNzx+6lJNd2AA9+AEg
Message-ID: <05C81A773E48DD49B181B04BA21A342A27C48EFB3D@HE113484.emea1.cds.t-internal.com>
References: <CAC8QAccGfoHL7SC+5t3KDqhmtizhda8kDz4xf9M+taoLQRbJ=Q@mail.gmail.com> <05C81A773E48DD49B181B04BA21A342A27C48EF434@HE113484.emea1.cds.t-internal.com> <OF0D2F190D.2B331677-ON88257A66.00215E9A-88257A66.0021E67A@zte.com.cn>
In-Reply-To: <OF0D2F190D.2B331677-ON88257A66.00215E9A-88257A66.0021E67A@zte.com.cn>
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: multipart/alternative; boundary="_000_05C81A773E48DD49B181B04BA21A342A27C48EFB3DHE113484emea1_"
MIME-Version: 1.0
Cc: sarikaya@ieee.org, fmc-bounces@ietf.org, fmc@ietf.org
Subject: Re: [fmc] Minutes v2 of the side meeting on 7/30/12
X-BeenThere: fmc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Fixed Mobile Convergence <fmc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fmc>, <mailto:fmc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fmc>
List-Post: <mailto:fmc@ietf.org>
List-Help: <mailto:fmc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fmc>, <mailto:fmc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Aug 2012 12:09:16 -0000

--_000_05C81A773E48DD49B181B04BA21A342A27C48EFB3DHE113484emea1_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Tricci,
thank you for pointing at the 3GPP related WIs. I think you refer to "Study=
 on Optimized Offloading to WLAN in 3GPP RAT mobility" (WLAN Optimized Offl=
oading in 3GPP RAT Mobility, WORM) described in TD S2-121892 and "WID for W=
LAN Network Selection for 3GPP Terminals" (NS) described in TD SP-120259, r=
ight?

>From a first glance it seems to me that WORM focusses on ANDSF extensions a=
nd within NS aspects of information exchange on available link quality and =
implications for current service provided are not in scope.

But we will have a thorough look on the descriptions and come back with an =
answer including detailed ideas.

Thanks again!

Best regards
Dirk
________________________________
Von: tso@zteusa.com [mailto:tso@zteusa.com]
Gesendet: Sonntag, 26. August 2012 08:10
An: von Hugo, Dirk
Cc: fmc@ietf.org; fmc-bounces@ietf.org; sarikaya@ieee.org
Betreff: Re: [fmc] Minutes v2 of the side meeting on 7/30/12


Dear Dirk,

Sincerely thanks for your kind feedback.

For the items 2 and 3 below, from 3GPP perspectives, there are two separate=
 working items (FS-WORM and WLAN-NSD) which have been started in Rel-12 to =
address these two issues.

Could you please share with us a bit more details, what are the "generic" c=
onsiderations and requirements from IETF perspective, that are beyond 3GPP =
and WFA for the items 2 and 3 below which need IETF's effort to work on the=
 solutions.

Sincerely thanks in advance.
Tricci



<Dirk.von-Hugo@telekom.de>
Sent by: fmc-bounces@ietf.org

08/24/2012 08:56 AM

To
<sarikaya@ieee.org>, <fmc@ietf.org>
cc
Subject
Re: [fmc] Minutes v2 of the side meeting on 7/30/12





Dear all,
>From the minutes the conclusion of the meeting for me is that the major use=
 cases to visualize the need to work on solutions for a fixed mobile interw=
orking scenario are the following:

- common UE identification especially in the fixed network (in relation to =
NAT reversal and in case of handover)
- UE Mobility support in WiFi beyond CAPWAP radio resource management (incl=
uding also the handover issue from and to mobile network)
- access selection issues beyond work of MIF (detection) - including polici=
es and considering actual link quality of connection on different radio tec=
hnologies (cellular and WiFi) which is also related to required and agreed =
on service quality

IMHO these might be the topics to detail and clarify until Atlanta meeting.

Any other opinion or comment?

Thanks and have a nice weekend

Best regards
Dirk

-----Urspr=FCngliche Nachricht-----
Von: fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] Im Auftrag von Behc=
et Sarikaya
Gesendet: Dienstag, 31. Juli 2012 23:05
An: fmc@ietf.org
Betreff: [fmc] Minutes v2 of the side meeting on 7/30/12

With Dave Allan's corrections.

On Mon, Jul 30, 2012 at 6:55 PM, Behcet Sarikaya <sarikaya2012@gmail.com> w=
rote:
> Folks,
>
> The minutes are attached.
>
> Many thanks to Pete McCann for taking these minutes!
>
> Regards,
>
> Behcet
_______________________________________________
fmc mailing list
fmc@ietf.org
https://www.ietf.org/mailman/listinfo/fmc



--_000_05C81A773E48DD49B181B04BA21A342A27C48EFB3DHE113484emea1_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19258"></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D949394411-27082012><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Hi Tricci,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D949394411-27082012><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>thank you for pointing at the 3GPP related WIs. I thi=
nk you=20
refer to&nbsp;"Study on Optimized Offloading to WLAN in 3GPP RAT mobility" =
(WLAN=20
Optimized Offloading&nbsp;in 3GPP RAT Mobility, WORM)&nbsp;described in TD=
=20
S2-121892 and "WID for WLAN Network Selection for 3GPP Terminals" (NS) desc=
ribed=20
in TD SP-120259, right? </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D949394411-27082012></SPAN>&nbsp;<=
/DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D949394411-27082012></SPAN><SPAN=20
class=3D949394411-27082012><FONT color=3D#0000ff size=3D2 face=3DArial>From=
 a first=20
glance it seems to me that WORM focusses on ANDSF extensions and within NS=
=20
aspects of information exchange on available&nbsp;link quality&nbsp;and=20
implications for current service provided are not in scope.</FONT></SPAN></=
DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D949394411-27082012><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D949394411-27082012><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>But we will have a thorough look on the descriptions =
and come=20
back with an answer including detailed&nbsp;ideas.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D949394411-27082012><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D949394411-27082012><FONT color=3D=
#0000ff=20
size=3D2 face=3DArial>Thanks again!</FONT></SPAN></DIV><!-- Converted from =
text/rtf format -->
<P><SPAN lang=3Den-gb><FONT size=3D2 face=3DArial>Best regards</FONT></SPAN=
> <BR><SPAN=20
lang=3Den-gb><FONT size=3D2 face=3DArial>Dirk </FONT></SPAN>
<HR tabIndex=3D-1>
<FONT size=3D2 face=3DTahoma><B>Von:</B> tso@zteusa.com [mailto:tso@zteusa.=
com]=20
<BR><B>Gesendet:</B> Sonntag, 26. August 2012 08:10<BR><B>An:</B> von Hugo,=
=20
Dirk<BR><B>Cc:</B> fmc@ietf.org; fmc-bounces@ietf.org;=20
sarikaya@ieee.org<BR><B>Betreff:</B> Re: [fmc] Minutes v2 of the side meeti=
ng on=20
7/30/12<BR></FONT><BR></P>
<DIV></DIV><FONT size=3D2 face=3Dsans-serif>Dear Dirk, </FONT><BR><BR><FONT=
 size=3D2=20
face=3Dsans-serif>Sincerely thanks for your kind feedback. &nbsp;</FONT>=20
<BR><BR><FONT size=3D2 face=3Dsans-serif>For the items 2 and 3 below, from =
3GPP=20
perspectives, there are two separate working items (FS-WORM and WLAN-NSD) w=
hich=20
have been started in Rel-12 to address these two issues. &nbsp;</FONT>=20
<BR><BR><FONT size=3D2 face=3Dsans-serif>Could you please share with us a b=
it more=20
details, what are the "generic" considerations and requirements from IETF=20
perspective, that are beyond 3GPP and WFA for the items 2 and 3 below which=
 need=20
IETF's effort to work on the solutions. </FONT><BR><BR><FONT size=3D2=20
face=3Dsans-serif>Sincerely thanks in advance. </FONT><BR><FONT size=3D2=20
face=3Dsans-serif>Tricci </FONT><BR><BR><BR><BR>
<TABLE width=3D"100%">
  <TBODY>
  <TR vAlign=3Dtop>
    <TD width=3D"35%"><FONT size=3D1=20
      face=3Dsans-serif><B>&lt;Dirk.von-Hugo@telekom.de&gt;</B> </FONT><BR>=
<FONT=20
      size=3D1 face=3Dsans-serif>Sent by: fmc-bounces@ietf.org</FONT>=20
      <P><FONT size=3D1 face=3Dsans-serif>08/24/2012 08:56 AM</FONT> </P>
    <TD width=3D"64%">
      <TABLE width=3D"100%">
        <TBODY>
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT size=3D1 face=3Dsans-serif>To</FONT></=
DIV>
          <TD><FONT size=3D1 face=3Dsans-serif>&lt;sarikaya@ieee.org&gt;,=20
            &lt;fmc@ietf.org&gt;</FONT>=20
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT size=3D1 face=3Dsans-serif>cc</FONT></=
DIV>
          <TD>
        <TR vAlign=3Dtop>
          <TD>
            <DIV align=3Dright><FONT size=3D1 face=3Dsans-serif>Subject</FO=
NT></DIV>
          <TD><FONT size=3D1 face=3Dsans-serif>Re: [fmc] Minutes v2 of the =
side=20
            meeting on 7/30/12</FONT></TR></TBODY></TABLE><BR>
      <TABLE>
        <TBODY>
        <TR vAlign=3Dtop>
          <TD>
          <TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><TT=
><FONT=20
size=3D2>Dear all,<BR>From the minutes the conclusion of the meeting for me=
 is=20
that the major use cases to visualize the need to work on solutions for a f=
ixed=20
mobile interworking scenario are the following:<BR><BR>- common UE=20
identification especially in the fixed network (in relation to NAT reversal=
 and=20
in case of handover)<BR>- UE Mobility support in WiFi beyond CAPWAP radio=20
resource management (including also the handover issue from and to mobile=20
network)<BR>- access selection issues beyond work of MIF (detection) - incl=
uding=20
policies and considering actual link quality of connection on different rad=
io=20
technologies (cellular and WiFi) which is also related to required and agre=
ed on=20
service quality<BR><BR>IMHO these might be the topics to detail and clarify=
=20
until Atlanta meeting.<BR><BR>Any other opinion or comment?<BR><BR>Thanks a=
nd=20
have a nice weekend<BR><BR>Best regards<BR>Dirk<BR><BR>-----Urspr=FCngliche=
=20
Nachricht-----<BR>Von: fmc-bounces@ietf.org [</FONT></TT><A=20
href=3D"mailto:fmc-bounces@ietf.org"><TT><FONT=20
size=3D2>mailto:fmc-bounces@ietf.org</FONT></TT></A><TT><FONT size=3D2>] Im=
 Auftrag=20
von Behcet Sarikaya<BR>Gesendet: Dienstag, 31. Juli 2012 23:05<BR>An:=20
fmc@ietf.org<BR>Betreff: [fmc] Minutes v2 of the side meeting on=20
7/30/12<BR><BR>With Dave Allan's corrections.<BR><BR>On Mon, Jul 30, 2012 a=
t=20
6:55 PM, Behcet Sarikaya &lt;sarikaya2012@gmail.com&gt; wrote:<BR>&gt;=20
Folks,<BR>&gt;<BR>&gt; The minutes are attached.<BR>&gt;<BR>&gt; Many thank=
s to=20
Pete McCann for taking these minutes!<BR>&gt;<BR>&gt; Regards,<BR>&gt;<BR>&=
gt;=20
Behcet<BR>_______________________________________________<BR>fmc mailing=20
list<BR>fmc@ietf.org<BR></FONT></TT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/fmc"><TT><FONT=20
size=3D2>https://www.ietf.org/mailman/listinfo/fmc</FONT></TT></A><TT><FONT=
=20
size=3D2><BR><BR></FONT></TT><BR></BODY></HTML>

--_000_05C81A773E48DD49B181B04BA21A342A27C48EFB3DHE113484emea1_--

From tso@zteusa.com  Mon Aug 27 20:15:02 2012
Return-Path: <tso@zteusa.com>
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 576F921E803D for <fmc@ietfa.amsl.com>; Mon, 27 Aug 2012 20:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.292
X-Spam-Level: **
X-Spam-Status: No, score=2.292 tagged_above=-999 required=5 tests=[AWL=-0.247,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LOAN=2.3, RCVD_BAD_ID=2.837]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NdhyCGkdCX87 for <fmc@ietfa.amsl.com>; Mon, 27 Aug 2012 20:15:01 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 4342021F848B for <fmc@ietf.org>; Mon, 27 Aug 2012 20:15:00 -0700 (PDT)
Received: from [10.30.3.21] by mx5.zte.com.cn with surfront esmtp id 232552293413252(version=TLSv1/SSLv3 cipher=SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA bits=128 verify=NO);  Tue, 28 Aug 2012 11:08:32 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id q7S3Ejvj090618; Tue, 28 Aug 2012 11:14:45 +0800 (GMT-8) (envelope-from tso@zteusa.com)
In-Reply-To: <05C81A773E48DD49B181B04BA21A342A27C48EFB3D@HE113484.emea1.cds.t-internal.com>
References: <CAC8QAccGfoHL7SC+5t3KDqhmtizhda8kDz4xf9M+taoLQRbJ=Q@mail.gmail.com> <05C81A773E48DD49B181B04BA21A342A27C48EF434@HE113484.emea1.cds.t-internal.com> <OF0D2F190D.2B331677-ON88257A66.00215E9A-88257A66.0021E67A@zte.com.cn> <05C81A773E48DD49B181B04BA21A342A27C48EFB3D@HE113484.emea1.cds.t-internal.com>
To: <Dirk.von-Hugo@telekom.de>
MIME-Version: 1.0
X-KeepSent: BBB0A18D:842BEAC7-88257A68:001176F6; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.1 September 28, 2009
Message-ID: <OFBBB0A18D.842BEAC7-ON88257A68.001176F6-88257A68.0011BC1B@zte.com.cn>
From: tso@zteusa.com
Date: Tue, 28 Aug 2012 11:14:41 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-08-28 11:14:44, Serialize complete at 2012-08-28 11:14:44
Content-Type: multipart/alternative; boundary="=_alternative 0011BC1888257A68_="
X-MAIL: mse02.zte.com.cn q7S3Ejvj090618
Cc: sarikaya@ieee.org, fmc@ietf.org
Subject: Re: [fmc] Minutes v2 of the side meeting on 7/30/12
X-BeenThere: fmc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Fixed Mobile Convergence <fmc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fmc>, <mailto:fmc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fmc>
List-Post: <mailto:fmc@ietf.org>
List-Help: <mailto:fmc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fmc>, <mailto:fmc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Aug 2012 03:15:02 -0000

This is a multipart message in MIME format.
--=_alternative 0011BC1888257A68_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear Dirk,=20

Thank you very much for your kind responses.   I am certainly looking=20
forward for your feedback and your insight.=20

Sincerely thanks again.... Cheers
Tricci=20




<Dirk.von-Hugo@telekom.de>=20
08/27/2012 05:09 AM

To
<tso@zteusa.com>
cc
<fmc@ietf.org>, <fmc-bounces@ietf.org>, <sarikaya@ieee.org>
Subject
AW: [fmc] Minutes v2 of the side meeting on 7/30/12






Hi Tricci,
thank you for pointing at the 3GPP related WIs. I think you refer to=20
"Study on Optimized Offloading to WLAN in 3GPP RAT mobility" (WLAN=20
Optimized Offloading in 3GPP RAT Mobility, WORM) described in TD S2-121892 =

and "WID for WLAN Network Selection for 3GPP Terminals" (NS) described in=20
TD SP-120259, right?=20
=20
>From a first glance it seems to me that WORM focusses on ANDSF extensions=20
and within NS aspects of information exchange on available link quality=20
and implications for current service provided are not in scope.
=20
But we will have a thorough look on the descriptions and come back with an =

answer including detailed ideas.
=20
Thanks again!
Best regards=20
Dirk Von: tso@zteusa.com [mailto:tso@zteusa.com]=20
Gesendet: Sonntag, 26. August 2012 08:10
An: von Hugo, Dirk
Cc: fmc@ietf.org; fmc-bounces@ietf.org; sarikaya@ieee.org
Betreff: Re: [fmc] Minutes v2 of the side meeting on 7/30/12

Dear Dirk,=20

Sincerely thanks for your kind feedback.  =20

For the items 2 and 3 below, from 3GPP perspectives, there are two=20
separate working items (FS-WORM and WLAN-NSD) which have been started in=20
Rel-12 to address these two issues.  =20

Could you please share with us a bit more details, what are the "generic"=20
considerations and requirements from IETF perspective, that are beyond=20
3GPP and WFA for the items 2 and 3 below which need IETF's effort to work=20
on the solutions.=20

Sincerely thanks in advance.=20
Tricci=20



<Dirk.von-Hugo@telekom.de>=20
Sent by: fmc-bounces@ietf.org=20
08/24/2012 08:56 AM=20


To
<sarikaya@ieee.org>, <fmc@ietf.org>=20
cc

Subject
Re: [fmc] Minutes v2 of the side meeting on 7/30/12








Dear all,
>From the minutes the conclusion of the meeting for me is that the major=20
use cases to visualize the need to work on solutions for a fixed mobile=20
interworking scenario are the following:

- common UE identification especially in the fixed network (in relation to =

NAT reversal and in case of handover)
- UE Mobility support in WiFi beyond CAPWAP radio resource management=20
(including also the handover issue from and to mobile network)
- access selection issues beyond work of MIF (detection) - including=20
policies and considering actual link quality of connection on different=20
radio technologies (cellular and WiFi) which is also related to required=20
and agreed on service quality

IMHO these might be the topics to detail and clarify until Atlanta=20
meeting.

Any other opinion or comment?

Thanks and have a nice weekend

Best regards
Dirk

-----Urspr=FCngliche Nachricht-----
Von: fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] Im Auftrag von=20
Behcet Sarikaya
Gesendet: Dienstag, 31. Juli 2012 23:05
An: fmc@ietf.org
Betreff: [fmc] Minutes v2 of the side meeting on 7/30/12

With Dave Allan's corrections.

On Mon, Jul 30, 2012 at 6:55 PM, Behcet Sarikaya <sarikaya2012@gmail.com>=20
wrote:
> Folks,
>
> The minutes are attached.
>
> Many thanks to Pete McCann for taking these minutes!
>
> Regards,
>
> Behcet
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
fmc mailing list
fmc@ietf.org
https://www.ietf.org/mailman/listinfo/fmc



--=_alternative 0011BC1888257A68_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<font size=3D2 face=3D"sans-serif">Dear Dirk, </font>
<br>
<br><font size=3D2 face=3D"sans-serif">Thank you very much for your kind re=
sponses.
&nbsp; I am certainly looking forward for your feedback and your insight.
</font>
<br>
<br><font size=3D2 face=3D"sans-serif">Sincerely thanks again.... Cheers</f=
ont>
<br><font size=3D2 face=3D"sans-serif">Tricci </font>
<br>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td width=3D35%><font size=3D1 face=3D"sans-serif"><b>&lt;Dirk.von-Hugo@tel=
ekom.de&gt;</b>
</font>
<p><font size=3D1 face=3D"sans-serif">08/27/2012 05:09 AM</font>
<td width=3D64%>
<table width=3D100%>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">To</font></div>
<td><font size=3D1 face=3D"sans-serif">&lt;tso@zteusa.com&gt;</font>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">cc</font></div>
<td><font size=3D1 face=3D"sans-serif">&lt;fmc@ietf.org&gt;, &lt;fmc-bounce=
s@ietf.org&gt;,
&lt;sarikaya@ieee.org&gt;</font>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">Subject</font></div>
<td><font size=3D1 face=3D"sans-serif">AW: [fmc] Minutes v2 of the side mee=
ting
on 7/30/12</font></table>
<br>
<table>
<tr valign=3Dtop>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3D2 color=3Dblue face=3D"Arial">Hi Tricci,</font>
<br><font size=3D2 color=3Dblue face=3D"Arial">thank you for pointing at the
3GPP related WIs. I think you refer to &quot;Study on Optimized Offloading
to WLAN in 3GPP RAT mobility&quot; (WLAN Optimized Offloading in 3GPP RAT
Mobility, WORM) described in TD S2-121892 and &quot;WID for WLAN Network
Selection for 3GPP Terminals&quot; (NS) described in TD SP-120259, right?
</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D2 color=3Dblue face=3D"Arial">From a first glance it seems=
 to
me that WORM focusses on ANDSF extensions and within NS aspects of informat=
ion
exchange on available link quality and implications for current service
provided are not in scope.</font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D2 color=3Dblue face=3D"Arial">But we will have a thorough =
look
on the descriptions and come back with an answer including detailed ideas.<=
/font>
<br><font size=3D3>&nbsp;</font>
<br><font size=3D2 color=3Dblue face=3D"Arial">Thanks again!</font>
<p><font size=3D2 face=3D"Arial">Best regards</font><font size=3D3> </font>=
<font size=3D2 face=3D"Arial"><br>
Dirk </font>
<hr><font size=3D2 face=3D"Tahoma"><b>Von:</b> tso@zteusa.com [</font><a hr=
ef=3Dmailto:tso@zteusa.com><font size=3D2 face=3D"Tahoma">mailto:tso@zteusa=
.com</font></a><font size=3D2 face=3D"Tahoma">]
<b><br>
Gesendet:</b> Sonntag, 26. August 2012 08:10<b><br>
An:</b> von Hugo, Dirk<b><br>
Cc:</b> fmc@ietf.org; fmc-bounces@ietf.org; sarikaya@ieee.org<b><br>
Betreff:</b> Re: [fmc] Minutes v2 of the side meeting on 7/30/12</font><fon=
t size=3D3><br>
</font>
<p><font size=3D2 face=3D"sans-serif">Dear Dirk, </font><font size=3D3><br>
</font><font size=3D2 face=3D"sans-serif"><br>
Sincerely thanks for your kind feedback. &nbsp;</font><font size=3D3> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
For the items 2 and 3 below, from 3GPP perspectives, there are two separate
working items (FS-WORM and WLAN-NSD) which have been started in Rel-12
to address these two issues. &nbsp;</font><font size=3D3> <br>
</font><font size=3D2 face=3D"sans-serif"><br>
Could you please share with us a bit more details, what are the &quot;gener=
ic&quot;
considerations and requirements from IETF perspective, that are beyond
3GPP and WFA for the items 2 and 3 below which need IETF's effort to work
on the solutions. </font><font size=3D3><br>
</font><font size=3D2 face=3D"sans-serif"><br>
Sincerely thanks in advance. <br>
Tricci </font><font size=3D3><br>
<br>
<br>
</font>
<table width=3D100%>
<tr valign=3Dtop>
<td width=3D35%><font size=3D1 face=3D"sans-serif"><b>&lt;Dirk.von-Hugo@tel=
ekom.de&gt;</b>
<br>
Sent by: fmc-bounces@ietf.org</font><font size=3D3> </font>
<p><font size=3D1 face=3D"sans-serif">08/24/2012 08:56 AM</font><font size=
=3D3>
</font>
<td width=3D64%>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td width=3D12%>
<div align=3Dright><font size=3D1 face=3D"sans-serif">To</font></div>
<td width=3D87%><font size=3D1 face=3D"sans-serif">&lt;sarikaya@ieee.org&gt=
;,
&lt;fmc@ietf.org&gt;</font><font size=3D3> </font>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">cc</font></div>
<td>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">Subject</font></div>
<td><font size=3D1 face=3D"sans-serif">Re: [fmc] Minutes v2 of the side mee=
ting
on 7/30/12</font></table>
<br>
<br>
<table>
<tr valign=3Dtop>
<td>
<td></table>
<br></table>
<br><font size=3D3><br>
<br>
</font><tt><font size=3D2><br>
Dear all,<br>
>From the minutes the conclusion of the meeting for me is that the major
use cases to visualize the need to work on solutions for a fixed mobile
interworking scenario are the following:<br>
<br>
- common UE identification especially in the fixed network (in relation
to NAT reversal and in case of handover)<br>
- UE Mobility support in WiFi beyond CAPWAP radio resource management (incl=
uding
also the handover issue from and to mobile network)<br>
- access selection issues beyond work of MIF (detection) - including polici=
es
and considering actual link quality of connection on different radio techno=
logies
(cellular and WiFi) which is also related to required and agreed on service
quality<br>
<br>
IMHO these might be the topics to detail and clarify until Atlanta meeting.=
<br>
<br>
Any other opinion or comment?<br>
<br>
Thanks and have a nice weekend<br>
<br>
Best regards<br>
Dirk<br>
<br>
-----Urspr=FCngliche Nachricht-----<br>
Von: fmc-bounces@ietf.org [</font></tt><a href=3D"mailto:fmc-bounces@ietf.o=
rg"><tt><font size=3D2 color=3Dblue><u>mailto:fmc-bounces@ietf.org</u></fon=
t></tt></a><tt><font size=3D2>]
Im Auftrag von Behcet Sarikaya<br>
Gesendet: Dienstag, 31. Juli 2012 23:05<br>
An: fmc@ietf.org<br>
Betreff: [fmc] Minutes v2 of the side meeting on 7/30/12<br>
<br>
With Dave Allan's corrections.<br>
<br>
On Mon, Jul 30, 2012 at 6:55 PM, Behcet Sarikaya &lt;sarikaya2012@gmail.com=
&gt;
wrote:<br>
&gt; Folks,<br>
&gt;<br>
&gt; The minutes are attached.<br>
&gt;<br>
&gt; Many thanks to Pete McCann for taking these minutes!<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Behcet<br>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
fmc mailing list<br>
fmc@ietf.org</font></tt><font size=3D3 color=3Dblue><u><br>
</u></font><a href=3Dhttps://www.ietf.org/mailman/listinfo/fmc><tt><font si=
ze=3D2 color=3Dblue><u>https://www.ietf.org/mailman/listinfo/fmc</u></font>=
</tt></a><tt><font size=3D2><br>
</font></tt><font size=3D3><br>
</font>
<br>
--=_alternative 0011BC1888257A68_=--


From Dirk.von-Hugo@telekom.de  Wed Aug 29 03:40:07 2012
Return-Path: <Dirk.von-Hugo@telekom.de>
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 ED10021F8617 for <fmc@ietfa.amsl.com>; Wed, 29 Aug 2012 03:40:06 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jUUR9dr2fTbu for <fmc@ietfa.amsl.com>; Wed, 29 Aug 2012 03:40:06 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id D4E8F21F8622 for <fmc@ietf.org>; Wed, 29 Aug 2012 03:40:05 -0700 (PDT)
Received: from he111628.emea1.cds.t-internal.com ([10.134.93.20]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 29 Aug 2012 12:40:03 +0200
Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE111628.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 29 Aug 2012 12:40:03 +0200
From: <Dirk.von-Hugo@telekom.de>
To: <fmc@ietf.org>
Date: Wed, 29 Aug 2012 12:40:00 +0200
Thread-Topic: New Version Notification for draft-xue-fmc-ps-01.txt
Thread-Index: Ac2FvqDqw+XuK3wfTA6Srn7u3XvU9gAExSyg
Message-ID: <05C81A773E48DD49B181B04BA21A342A27C49991B5@HE113484.emea1.cds.t-internal.com>
References: <20120829081638.19273.62823.idtracker@ietfa.amsl.com>
In-Reply-To: <20120829081638.19273.62823.idtracker@ietfa.amsl.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: sarikaya@ieee.org, xueli@huawei.com
Subject: Re: [fmc] New Version Notification for draft-xue-fmc-ps-01.txt
X-BeenThere: fmc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Fixed Mobile Convergence <fmc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fmc>, <mailto:fmc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fmc>
List-Post: <mailto:fmc@ietf.org>
List-Help: <mailto:fmc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fmc>, <mailto:fmc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Aug 2012 10:40:07 -0000

Dear all,
An updated version of the PS draft is available.
We like to attract your interest esp. for the use cases described as
- UE identification in fixed broadband network
- UE mobility across fixed networks
- UE wireless link characteristics related to QoS
We hope to focus thus on the major FMC aspects to be discussed and solved w=
ithin INT area.

Thanks!
Best regards
Dirk

-----Urspr=FCngliche Nachricht-----
Von: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
Gesendet: Mittwoch, 29. August 2012 10:17
An: sarikaya@ieee.org
Cc: von Hugo, Dirk; xueli@huawei.com
Betreff: New Version Notification for draft-xue-fmc-ps-01.txt


A new version of I-D, draft-xue-fmc-ps-01.txt
has been successfully submitted by Behcet Sarikaya and posted to the
IETF repository.

Filename:        draft-xue-fmc-ps
Revision:        01
Title:           Problem Statement for Fixed Mobile Convergence
Creation date:   2012-08-29
WG ID:           Individual Submission
Number of pages: 16
URL:             http://www.ietf.org/internet-drafts/draft-xue-fmc-ps-01.tx=
t
Status:          http://datatracker.ietf.org/doc/draft-xue-fmc-ps
Htmlized:        http://tools.ietf.org/html/draft-xue-fmc-ps-01
Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-xue-fmc-ps-01

Abstract:
   The purpose of this document is to analyze the issues that have
   arisen so far and to propose several use cases for the Fixed Mobile
   Convergence.  This document gives a brief overview of the assumed
   Fixed Mobile Convergence architecture and related works and then
   introduces several Intarea type of use cases based on the partnership
   in Fixed Mobile Convergence architecture, such as User Equipment
   identification, mobility consideration, such as mobility status
   reporting in Wi-Fi network and transporting Wi-Fi link
   characteristics type of considerations.




The IETF Secretariat

