From lion.jeanfc@gmail.com Sat Sep 1 06:53:18 2012 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 90D1311E8097 for ; Sat, 1 Sep 2012 06:53:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.913 X-Spam-Level: *** X-Spam-Status: No, score=3.913 tagged_above=-999 required=5 tests=[AWL=-4.722, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, HTML_MESSAGE=0.001, MANGLED_INCLDN=2.3, MANGLED_SIZE=2.3, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_GB2312=1.345] 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 ux15-ujSWZtL for ; Sat, 1 Sep 2012 06:53:17 -0700 (PDT) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 077F711E808D for ; Sat, 1 Sep 2012 06:53:17 -0700 (PDT) Received: by pbbrr4 with SMTP id rr4so5936438pbb.31 for ; Sat, 01 Sep 2012 06:53:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=j5bqM3h4DMuJ/lAArQUMiaZ0CUMnKicOG0xYGkd21GU=; b=jrIGGzkLnk0LqPFpi6po84XaXB1+lUBV455kahjyFIt2ZqbReOUW777yu+HIc2Kf5T sPWvrt7fQbVbKLo2jZplBgnKUbgpBnxung6GjvA8pCJMGNhkofl6y8YrDAjV1qFvJy5h AnOPQrx6J8ltJY53Hmrm7FSa5d9HgMQb61tnCJZK39G7OaLLsVwkPfxlWCK80QNAbVNc Wernb5XKrffWu4/GUwKCfdNYM4sH2I7lOu13LqNFX77p+MYqYUlsoavwbYrqRrsUIwlA ZfvBZXiiYWJ6sIb1O5kDdWbwfJ+jI7ZUJpl1qBGdteNfOEKs+ASWuDXZX939To3Ut6jQ 27Uw== MIME-Version: 1.0 Received: by 10.68.212.98 with SMTP id nj2mr24217592pbc.138.1346507595913; Sat, 01 Sep 2012 06:53:15 -0700 (PDT) Received: by 10.68.134.136 with HTTP; Sat, 1 Sep 2012 06:53:14 -0700 (PDT) Received: by 10.68.134.136 with HTTP; Sat, 1 Sep 2012 06:53:14 -0700 (PDT) Date: Sat, 1 Sep 2012 21:53:14 +0800 Message-ID: From: lion jean To: fmc@ietf.org, s@gmail.com, aaa@gmail.com, qa@gmail.com Content-Type: multipart/alternative; boundary=e89a8ff1c8b0f1199d04c8a43ab4 Subject: Re: [fmc] =?gb2312?b?Zm1jIERBUWlnZXNRQXQsIFZvbCA1LCBJc0VBV2FXc3VlIDU=?= =?gb2312?b?z9bU2qO/oa0sd2VxYGl3d2ZhYVFBWVFBWWFB?= 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: Sat, 01 Sep 2012 13:53:18 -0000 --e89a8ff1c8b0f1199d04c8a43ab4 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable =A3=BA=D8=BC =D4=DA 2012-8-27 =C9=CF=CE=E73:00=A3=AC =D0=B4=B5=C0= =A3=BA > If you have received this digest without all the individual message > attachments you will need to update your digest options in your list > subscription. To do so, go to > > https://www.ietf.org/mailman/listinfo/fmc > > Click the 'Unsubscribe or edit options' button, log in, and set "Get > MIME or Plain Text Digests?" to MIME. You can set this option > globally for all the list digests you receive at this point. > > > > Send fmc mailing list submissions to > fmc@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/fmc > or, via email, send a message with subject or body 'help' to > fmc-request@ietf.org > > You can reach the person managing the list at > fmc-owner@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of fmc digest..." > > Today's Topics: > > 1. Re: Minutes v2 of the side meeting on 7/30/12 (tso@zteusa.com) > 2. (no subject) > 3. (no subject) > > > ---------- =D2=D1=D7=AA=B7=A2=D3=CA=BC=FE ---------- > From: tso@zteusa.com > To: > Cc: sarikaya@ieee.org, fmc-bounces@ietf.org, fmc@ietf.org > Date: Sat, 25 Aug 2012 23:09:34 -0700 > Subject: 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" > 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. > > Sincerely thanks in advance. > Tricci > > > > > > Sent by: fmc-bounces@ietf.org > 08/24/2012 08:56 AM > > To > , > cc > > Subject > Re: [fmc] Minutes v2 of the side meeting on 7/30/12 > > > > > > > Dear all, > > ---------- =D2=D1=D7=AA=B7=A2=D3=CA=BC=FE ---------- > From: > To: > Cc: > Date: > Subject: > use cases to visualize the need to work on solutions for a fixed mobile= =3D20 > interworking scenario are the following: > > - common UE identification especially in the fixed network (in relation t= o > =3D > > NAT reversal and in case of handover) > - UE Mobility support in WiFi beyond CAPWAP radio resource management=3D2= 0 > (including also the handover issue from and to mobile network) > - access selection issues beyond work of MIF (detection) - including=3D20 > policies and considering actual link quality of connection on different= =3D20 > radio technologies (cellular and WiFi) which is also related to required= =3D20 > and agreed on service quality > > IMHO these might be the topics to detail and clarify until Atlanta=3D20 > meeting. > > Any other opinion or comment? > > Thanks and have a nice weekend > > Best regards > Dirk > > -----Urspr=3DFCngliche Nachricht----- > Von: fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] Im Auftrag von=3D= 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 >=3D20 > wrote: > > Folks, > > > > The minutes are attached. > > > > Many thanks to Pete McCann for taking these minutes! > > > > Regards, > > > > Behcet > > =3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D= 5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D > =3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D= 5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F > fmc mailing list > fmc@ietf.org > https://www.ietf.org/mailman/listinfo/fmc > > > > --=3D_alternative 0021E67888257A66_=3D > Content-Type: text/html; charset=3D"ISO-8859-1" > Content-Transfer-Encoding: quoted-printable > > Dear Dirk, >
>
Sincerely thanks for your kind > feedb=3D > ack. >   >
>
For the items 2 and 3 below, f= rom > 3G=3D > 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. >   >
>
Could you please share with us= a bit > more details, what are the "generic" considerations and > requireme=3D > 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. >
>
Sincerely thanks in advance. <= /font> >
Tricci >
>
>
>
> > >
<Dirk.von-= Hugo@tel > =3D > ekom.de> > >
Sent by: fmc-bounces@ietf.org > >

08/24/2012 08:56 AM >

> > > > >
>
To >
<sarikaya@ieee.org>, > <fmc@i=3D > etf.org> >
>
cc >
>
>
Subject
> 		Re: [fmc] Minutes v2 of the si= de > mee=3D > ting > on 7/30/12
>
> > >
>
>
>
>
>
Dear all,
> > > ---------- =D2=D1=D7=AA=B7=A2=D3=CA=BC=FE ---------- > From: > To: > Cc: > Date: > Subject: > use cases to visualize the need to work on solutions for a fixed mobile > 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 > (incl=3D > uding > also the handover issue from and to mobile network)
> - access selection issues beyond work of MIF (detection) - including > polici=3D > es > and considering actual link quality of connection on different radio > techno=3D > logies > (cellular and WiFi) which is also related to required and agreed on servi= ce > quality
>
> IMHO these might be the topics to detail and clarify until Atlanta > meeting.=3D >
>
> Any other opinion or comment?
>
> Thanks and have a nice weekend
>
> Best regards
> Dirk
>
> -----Urspr=3DFCngliche Nachricht-----
> Von: fmc-bounces@ietf.org [ fmc-bounces@ietf.o=3D > rg">mailto:fmc-bounces@ietf.org > size=3D3D2>] > Im Auftrag von 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 & > lt;sarikaya2012@gmail.com=3D > > > wrote:
> > Folks,
> >
> > The minutes are attached.
> >
> > Many thanks to Pete McCann for taking these minutes!
> >
> > Regards,
> >
> > Behcet
> > =3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D= 5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D > =3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D= 5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F
> fmc mailing list
> fmc@ietf.org
> s=3D > ize=3D3D2>https://www.ietf.org/mailman/listinfo/fmc =3D > size=3D3D2>
>
> >
> --=3D_alternative 0021E67888257A66_=3D-- > > > > _______________________________________________ > fmc mailing list > fmc@ietf.org > https://www.ietf.org/mailman/listinfo/fmc > > --e89a8ff1c8b0f1199d04c8a43ab4 Content-Type: text/html; charset=GB2312 Content-Transfer-Encoding: quoted-printable

=A3=BA=D8=BC

=D4=DA 2012-8-27 =C9=CF=CE=E73:00=A3=AC <fmc-request@ietf.org>=D0=B4=B5= =C0=A3=BA
If you have received this digest without all the individual message
attachments you will need to update your digest options in your list
subscription.  To do so, go to

htt= ps://www.ietf.org/mailman/listinfo/fmc

Click the 'Unsubscribe or edit options' button, log in, and set &qu= ot;Get
MIME or Plain Text Digests?" to MIME.  You can set this option globally for all the list digests you receive at this point.



Send fmc mailing list submissions to
        fmc@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://www.ietf.org/mailman/listinfo/fmc
or, via email, send a message with subject or body 'help' to
        fmc-req= uest@ietf.org

You can reach the person managing the list at
        fmc-owner= @ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of fmc digest..."

Today's Topics:

   1. Re: Minutes v2 of the side meeting on 7/30/12 (tso@zteusa.com)
   2. (no subject)
   3. (no subject)


---------- =D2=D1=D7=AA=B7=A2=D3=CA=BC=FE ----------
From: = tso@zteusa.com
To: <Dirk.von-Hugo@telekom.de>
C= c: sarikaya@ieee.org, fmc-bounces@ietf.org, fmc@ietf.org
Date: Sat, 25 Aug 2012 23:09:34 -0700
Subject: Re: [fmc] Minut= es 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 "gener= ic"
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 wo= rk
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,

---------- =D2=D1=D7=AA=B7=A2=D3=CA=BC=FE ----------
Fr= om: 
To: 
Cc: 
Date: 
Subject: 
use= cases to visualize the need to work on solutions for a fixed mobile=3D20 interworking scenario are the following:

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

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

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

Any other opinion or comment?

Thanks and have a nice weekend

Best regards
Dirk

-----Urspr=3DFCngliche Nachricht-----
Von: fmc-bounces@ietf.org [mail= to:fmc-bounces@ietf.org] Im Auf= trag von=3D20
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>=3D20
wrote:
> Folks,
>
> The minutes are attached.
>
> Many thanks to Pete McCann for taking these minutes!
>
> Regards,
>
> Behcet
=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F= =3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D
=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F= =3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F
fmc mailing list
fmc@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/fmc



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

<font size=3D3D2 face=3D3D"sans-serif">Dear Dirk, </font= >
<br>
<br><font size=3D3D2 face=3D3D"sans-serif">Sincerely = thanks for your kind feedb=3D
ack.
&nbsp;</font>
<br>
<br><font size=3D3D2 face=3D3D"sans-serif">For the it= ems 2 and 3 below, from 3G=3D
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;&l= t;/font>
<br>
<br><font size=3D3D2 face=3D3D"sans-serif">Could you = please share with us a bit
more details, what are the &quot;generic&quot; considerations and r= equireme=3D
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=3D3D2 face=3D3D"sans-serif">Sincerely = thanks in advance. </font>
<br><font size=3D3D2 face=3D3D"sans-serif">Tricci <= ;/font>
<br>
<br>
<br>
<br>
<table width=3D3D100%>
<tr valign=3D3Dtop>
<td width=3D3D35%><font size=3D3D1 face=3D3D"sans-serif"= ><b>&lt;Dirk.von-Hugo@tel=3D
ekom.de&gt;</b><= br> </font>
<br><font size=3D3D1 face=3D3D"sans-serif">Sent by: <= a href=3D"mailto:fmc-bounces@ietf.org">fmc-bounces@ietf.org</font>= ;
<p><font size=3D3D1 face=3D3D"sans-serif">08/24/2012 = 08:56 AM</font>
<td width=3D3D64%>
<table width=3D3D100%>
<tr valign=3D3Dtop>
<td>
<div align=3D3Dright><font size=3D3D1 face=3D3D"sans-serif&qu= ot;>To</font></div>
<td><font size=3D3D1 face=3D3D"sans-serif">&lt;sarikaya@ieee.org&gt;, &= ;lt;fmc@i=3D
etf.org&gt;</font&g= t;
<tr valign=3D3Dtop>
<td>
<div align=3D3Dright><font size=3D3D1 face=3D3D"sans-serif&qu= ot;>cc</font></div>
<td>
<tr valign=3D3Dtop>
<td>
<div align=3D3Dright><font size=3D3D1 face=3D3D"sans-serif&qu= ot;>Subject</font></div>
<td><font size=3D3D1 face=3D3D"sans-serif">Re: [fmc] = Minutes v2 of the side mee=3D
ting
on 7/30/12</font></table>
<br>
<table>
<tr valign=3D3Dtop>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=3D3D2>Dear all,<br>


---------- =D2=D1=D7=AA=B7=A2=D3=CA=BC=FE ----------
From: =
To: 
Cc: 
Date: 
Subject: 
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= =3D
uding
also the handover issue from and to mobile network)<br>
- access selection issues beyond work of MIF (detection) - including polici= =3D
es
and considering actual link quality of connection on different radio techno= =3D
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.= =3D
<br>
<br>
Any other opinion or comment?<br>
<br>
Thanks and have a nice weekend<br>
<br>
Best regards<br>
Dirk<br>
<br>
-----Urspr=3DFCngliche Nachricht-----<br>
Von: fmc-bounces@ietf.org [<= /font></tt><a href=3D3D"mailto:fmc-bounces@ietf.o=3D
rg"><tt><font size=3D3D2>mailto:fmc-bounces@ietf.org</font></tt></a>= <tt><font=3D
 size=3D3D2>]
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=3D
&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>
=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F= =3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D
=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F= =3D5F=3D5F=3D5F=3D5F=3D5F=3D5F=3D5F<br>
fmc mailing list<br>
fmc@ietf.org<br>
</font></tt><a href=3D3Dhttps://www.ietf.org/mailman/listinfo/fm= c><tt><font s=3D
ize=3D3D2>https://www.ietf.org/mailman/listinfo/fmc</font></= tt></a><tt><font =3D
size=3D3D2><br>
<br>
</font></tt>
<br>
--=3D_alternative 0021E67888257A66_=3D--



_______________________________________________
fmc mailing list
fmc@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/fmc

--e89a8ff1c8b0f1199d04c8a43ab4-- From Dirk.von-Hugo@telekom.de Wed Sep 12 05:42:21 2012 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 D3C4F21F85A2 for ; Wed, 12 Sep 2012 05:42:21 -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 DA+LAvnKfiOG for ; Wed, 12 Sep 2012 05:42:20 -0700 (PDT) Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by ietfa.amsl.com (Postfix) with ESMTP id 6A3EC21F84EB for ; Wed, 12 Sep 2012 05:42:19 -0700 (PDT) Received: from he111629.emea1.cds.t-internal.com ([10.134.93.21]) by tcmail71.telekom.de with ESMTP/TLS/AES128-SHA; 12 Sep 2012 14:42:17 +0200 Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE111629.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 12 Sep 2012 14:42:17 +0200 From: To: Date: Wed, 12 Sep 2012 14:42:16 +0200 Thread-Topic: AW: [fmc] Minutes v2 of the side meeting on 7/30/12 Thread-Index: Ac2Ey06NqUpOgimMQQmyBA/pk8n8kAMDNlwQ Message-ID: <05C81A773E48DD49B181B04BA21A342A27CC4EC78B@HE113484.emea1.cds.t-internal.com> References: <05C81A773E48DD49B181B04BA21A342A27C48EF434@HE113484.emea1.cds.t-internal.com> <05C81A773E48DD49B181B04BA21A342A27C48EFB3D@HE113484.emea1.cds.t-internal.com> In-Reply-To: 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_05C81A773E48DD49B181B04BA21A342A27CC4EC78BHE113484emea1_" MIME-Version: 1.0 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2012 12:42:22 -0000 --_000_05C81A773E48DD49B181B04BA21A342A27CC4EC78BHE113484emea1_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Tricci, sorry for some delay since your previous email and thanks again for pointin= g to the new interesting 3GPP Work Items WORM and NS (here in close co-oper= ation with WFA!). In general I think the recent creation of these new WIs once more confirms = the importance of the issue to discuss on and finally find generic solution= s for fixed mobile interworking scenarios as arise with ongoing sessions on= MIF terminals in a multi access network environment. IMHO from IETF perspective the additional work on UE Mobility support in Wi= Fi is to clarify whether partly 3GPP-referenced IP mobility protocols could= also be applied to all kinds of WiFi access scenarios (including residenti= al homes which might not be controlled via CAPWAP protocol or similar one c= ompatible to (P)MIP and extensions) and is based on BBFs requirement to all= ow for mobility with respect to an edge router which - in contrast to 3G no= des - does not provide intrinsical mobility anchor functionalities. - 3G WI= WORM on the other hand will focus on (3GPPs) ANDSF extensions (which curre= ntly does not provide mechanisms to indicate preferences with granularity a= t alternative radio accesses within network policies) and analyze mobility = scenarios with respect to minimizing user and service impact. I think that an IETF provided assessment of measures to grant such a seaml= ess service provision would fit very well into 3GPP interest. Regarding access selection as mentioned before we want to center more on ho= w to transport the WiFi link characteristics in a network layer representat= ion related to and required for QoS and network policies and user profiles,= respectively - thus this goes beyond Access Network Selection between 3G= and WFA on technology specific link layer information if I understand corr= ectly what 3G WI NS proposes to achieve. Of course here also the planned IntArea work would benefit from a close cou= pling to activities ongoing in 3GPP. Please correct me if I misunderstood something and any further comment is v= ery welcome! Thanks and best regards Dirk ________________________________ Von: tso@zteusa.com [mailto:tso@zteusa.com] Gesendet: Dienstag, 28. August 2012 05:15 An: von Hugo, Dirk Cc: fmc@ietf.org; sarikaya@ieee.org Betreff: Re: AW: [fmc] Minutes v2 of the side meeting on 7/30/12 Dear Dirk, Thank you very much for your kind responses. I am certainly looking forwa= rd for your feedback and your insight. Sincerely thanks again.... Cheers Tricci 08/27/2012 05:09 AM To cc , , Subject AW: [fm c] 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 "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 Sent by: fmc-bounces@ietf.org 08/24/2012 08:56 AM To , 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 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_05C81A773E48DD49B181B04BA21A342A27CC4EC78BHE113484emea1_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Dear Tricci,
sorry for some delay since your previous email a= nd=20 thanks again for pointing to the new interesting 3GPP Work Items WORM and N= S=20 (here in close co-operation with WFA!).
In general I think the recent creation of these = new WIs=20 once more confirms the importance of the issue to discuss on and finally fi= nd=20 generic solutions for fixed mobile interworking scenarios as arise with ong= oing=20 sessions on MIF terminals in a multi access network environment.=20
 
IMHO=20 from IETF perspective the additional work on UE Mobility support in WiFi is= to=20 clarify whether partly 3GPP-referenced IP mobility protocols could also be= =20 applied to all kinds of WiFi access scenarios (including residential homes = which=20 might not be controlled via CAPWAP protocol or similar one compatible to (P= )MIP=20 and extensions) and is based on BBFs requirement to allow for mobility with= =20 respect to an edge router which - in contrast to 3G nodes - does not=20 provide intrinsical mobility anchor functionalities. - 3G WI WORM= on=20 the other hand will focus on (3GPPs) ANDSF extensions (which currently <= SPAN=20 style=3D"FONT-FAMILY: Tele-GroteskHal; FONT-SIZE: 12pt; mso-ascii-font-fami= ly: Tele-GroteskHal; mso-hansi-font-family: Tele-GroteskHal"=20 lang=3DEN-US>does not provide mechanisms to indicate preferences with granu= larity=20 at alternative radio accesses within network policies) and analyze mobility scenarios with respect to minimizing user and service= =20 impact.
I think that an IETF provided assessment  of measure= s to=20 grant such a seamless service provision would fit very well into 3GPP=20 interest.
 
Regarding access selection as mentioned before we want to cent= er more=20 on how to transport the WiFi link characteristics in a network layer=20 representation related to and required for QoS and network policies and use= r=20 profiles, respectively  -  thus this goes beyond Access Netw= ork=20 Selection between 3G and WFA on technology specific link layer informa= tion=20 if I understand correctly what 3G WI NS proposes to=20 achieve. 
Of course here also the planned IntArea work would benefit fro= m a=20 close coupling to activities ongoing in=20 3GPP.
 
Please correct me if I misunderstood something and any further= =20 comment is very welcome!

Thanks and best regards
Dirk


Von: tso@zteusa.com [mailto:tso@zteusa.= com]=20
Gesendet: Dienstag, 28. August 2012 05:15
An: von Hugo= ,=20 Dirk
Cc: fmc@ietf.org; sarikaya@ieee.org
Betreff: Re: A= W:=20 [fmc] Minutes v2 of the side meeting on 7/30/12

Dear Dirk,

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

Sincerely thanks again....= =20 Cheers
Tricci 



 
 
<Dirk.von-Hugo@telekom.de>

08/27/2012 05:09 AM

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





Hi Tricci,
thank=20 you for pointing at the 3GPP related WIs. I think you refer to "Study on=20 Optimized Offloading to WLAN in 3GPP RAT mobility" (WLAN Optimized Offloadi= ng in=20 3GPP RAT Mobility, WORM) described in TD S2-121892 and "WID for WLAN Networ= k=20 Selection for 3GPP Terminals" (NS) described in TD SP-120259, right?=20
 
From a first glance it seems to me that WORM focusses on ANDSF= =20 extensions and within NS aspects of information exchange on available link= =20 quality and implications for current service provided are not in scope.=20
 
But we=20 will have a thorough look on the descriptions and come back with an answer= =20 including detailed ideas.
 
Thanks again!=20

Best regards
Dirk

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

Dear Dirk,

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

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

Sincerely thanks in advance.
Tricci


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

08/24/2012 08:56 AM=20


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







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

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

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

Any other opinio= n or=20 comment?

Thanks and have a nice weekend

Best=20 regards
Dirk

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

With Dave Allan's corrections.

On Mon, Jul 30, 2012 a= t=20 6:55 PM, Behcet Sarikaya <sarikaya2012@gmail.com> wrote:
>=20 Folks,
>
> The minutes are attached.
>
> Many thank= s to=20 Pete McCann for taking these minutes!
>
> Regards,
>
&= gt;=20 Behcet
_______________________________________________
fmc mailing=20 list
fmc@ietf.org
https://www.ietf.org/mailman/listinfo/fmc


--_000_05C81A773E48DD49B181B04BA21A342A27CC4EC78BHE113484emea1_-- From Roland.Schott@telekom.de Mon Sep 24 13:32:16 2012 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 0C1341F0C3A for ; Mon, 24 Sep 2012 13:32:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.248 X-Spam-Level: X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, 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 PufgYm-193Fa for ; Mon, 24 Sep 2012 13:32:15 -0700 (PDT) Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC171F042A for ; Mon, 24 Sep 2012 13:32:14 -0700 (PDT) Received: from he111631.emea1.cds.t-internal.com ([10.134.93.23]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 24 Sep 2012 22:32:13 +0200 Received: from HE111648.emea1.cds.t-internal.com ([10.134.93.17]) by HE111631.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 24 Sep 2012 22:32:12 +0200 From: To: Date: Mon, 24 Sep 2012 22:32:11 +0200 Thread-Topic: draft-schott-fmc-requirements-03 Thread-Index: Ac2ak6yyE6Iwz/6iQm6j1mOoXPbbQQ== Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D152DB80FC1@HE111648.emea1.cds.t-internal.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: multipart/alternative; boundary="_000_580BEA5E3B99744AB1F5BFF5E9A3C67D152DB80FC1HE111648emea1_" MIME-Version: 1.0 Subject: [fmc] draft-schott-fmc-requirements-03 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, 24 Sep 2012 20:32:16 -0000 --_000_580BEA5E3B99744AB1F5BFF5E9A3C67D152DB80FC1HE111648emea1_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, I have created a new version adding the section Link Characteristic Informa= tion. The streaming and access part can be integrated in this section. I am interested in the opinion of the list. The version is available on: http://www.ietf.org/internet-drafts/draft-schott-fmc-requirements-03.txt Regards Roland --_000_580BEA5E3B99744AB1F5BFF5E9A3C67D152DB80FC1HE111648emea1_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi all,
 
I have created a new version adding the section Link Characteristic Information.
 
The streaming and acc= ess part can be integrated in this section.
 
I am interested in th= e opinion of the list.
 
 
The version is available on:
 
 
 
Regards
 
Roland
 
 --_000_580BEA5E3B99744AB1F5BFF5E9A3C67D152DB80FC1HE111648emea1_-- From bingxuere@gmail.com Tue Sep 25 02:08:45 2012 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 9C46A21F88F8 for ; Tue, 25 Sep 2012 02:08:45 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AnUMi6HwSv3C for ; Tue, 25 Sep 2012 02:08:44 -0700 (PDT) Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9DBDC21F88D9 for ; Tue, 25 Sep 2012 02:08:44 -0700 (PDT) Received: by iec9 with SMTP id 9so14669161iec.31 for ; Tue, 25 Sep 2012 02:08:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=o19gZ15fp/WjY91zLXbx1KFQk/mABtdvZIRacvtnXiE=; b=gKHezbYpVcSpIbyIIO5dnzclTY93lH45+iBt8uFPy7kjfXbIEwpXYeUqTWgEwdtSqu oHuTSxnKjsvcFqMvzIevXR5tsWqLz6mS071MDiLaLDJhmfsad3pt8t64QduG6Gturzkw ueR/4jZDvK8k5mwbqe0vULmG0ocYPAxYmJulmAKF1ghFGDjq4Ni3tURivnviXd3GO9I+ fy5wCW7r+/IHB3FV3Vruc758vobXBHxlrUqqtTsFon0h8H1HO0vfBveeGwjEqnrnRamE 3zm6P03wcV/uhWBREsSMJ6EGG8XBmAa1Bb3mUQs/Xr3h26czbdnKBRADKbvHckH3ViYP xeLQ== Received: by 10.50.13.133 with SMTP id h5mr7602796igc.2.1348564124069; Tue, 25 Sep 2012 02:08:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.76.200 with HTTP; Tue, 25 Sep 2012 02:08:02 -0700 (PDT) In-Reply-To: <580BEA5E3B99744AB1F5BFF5E9A3C67D152DB80FC1@HE111648.emea1.cds.t-internal.com> References: <580BEA5E3B99744AB1F5BFF5E9A3C67D152DB80FC1@HE111648.emea1.cds.t-internal.com> From: Qiong Date: Tue, 25 Sep 2012 17:08:02 +0800 Message-ID: To: Roland.Schott@telekom.de Content-Type: multipart/alternative; boundary=f46d0447f21a926e8b04ca830d79 Cc: fmc@ietf.org Subject: Re: [fmc] draft-schott-fmc-requirements-03 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: Tue, 25 Sep 2012 09:08:45 -0000 --f46d0447f21a926e8b04ca830d79 Content-Type: text/plain; charset=UTF-8 Dear all, We are very interested to FMC work, we agree that several problems should be resolved in IETF, such as UE identified, and User group management, etc A draft about usecases is already submitted to the FMC list in last meeting. http://tools.ietf.org/html/draft-sun-fmc-use-case-00 I appreciate your comments and other usecases, I will update the draft later. Hope we will move forward :) Best wishes Qiong China Telecom On Tue, Sep 25, 2012 at 4:32 AM, wrote: > Hi all, > > I have created a new version adding the section Link Characteristic > Information. > > The streaming and access part can be integrated in this section. > > I am interested in the opinion of the list. > > > The version is available on: > > *http://www.ietf.org/internet-drafts/draft-schott-fmc-requirements-03.txt* > > > Regards > > Roland > > > _______________________________________________ > fmc mailing list > fmc@ietf.org > https://www.ietf.org/mailman/listinfo/fmc > > -- ============================================== Qiong Sun China Telecom Beijing Research Institude Open source code: lightweight 4over6: *http://sourceforge.net/projects/laft6/* PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/ * =============================================== --f46d0447f21a926e8b04ca830d79 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear all,

=C2=A0

We are very interested to FMC w= ork, we=20 agree that several problems should be resolved in IETF,

such as UE identified, and User= group=20 management, etc

=C2=A0

A draft about usecases is alrea= dy submitted=20 to the FMC list in last meeting.

http://tools.ietf.org/html/draft-sun-fmc-use-case-00

=C2=A0

I appreciate your comments and = other=20 usecases, I will update the draft later. Hope we will move forward :)


Best wishes<= /p>

Qiong


China Telecom



On Tue, Sep 25, 201= 2 at 4:32 AM, <Roland.Schott@telekom.de> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
Hi all,
=C2=A0
I have created a new version adding the section Link Characteristic Information.
=C2=A0
The streaming and acc= ess part can be integrated in this section.
=C2=A0
I am interested in th= e opinion of the list.
=C2=A0
=C2=A0
The version is available on:
=C2=A0
=C2=A0
=C2=A0
Regards
=C2=A0
Roland
=C2=A0

_______________________________________________
fmc mailing list
fmc@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/fmc




--
=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Qiong Sun
China Telecom= Beijing Research Institude


Open source code:
lightweight 4ov= er6: http://sourceforge.net/projects/laft6/
PCP-natcoord: http://sourceforge.net/projects/pcpportsetdemo/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

--f46d0447f21a926e8b04ca830d79-- From sarikaya2012@gmail.com Tue Sep 25 08:52:57 2012 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 00FE121F880E for ; Tue, 25 Sep 2012 08:52:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.376 X-Spam-Level: X-Spam-Status: No, score=-3.376 tagged_above=-999 required=5 tests=[AWL=0.223, BAYES_00=-2.599, 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 H+AwA6BjuvTU for ; Tue, 25 Sep 2012 08:52:56 -0700 (PDT) Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 789E021F885B for ; Tue, 25 Sep 2012 08:52:56 -0700 (PDT) Received: by iec9 with SMTP id 9so15815882iec.31 for ; Tue, 25 Sep 2012 08:52:56 -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:content-type; bh=rhqbyOsyLCa9Z/s11cd67PEq3oUxU2lFrI10CanM+SE=; b=XJUbe4QpeSszRKXEGcNinNXkJcS/xXCsm3lPuclyJYvEBRnyHsrCh4QU8vhqbYBuBb RoqcC5Kwm64yS709j4HP0SCIpWnaf++5uE4e1GG1BGih5zHqPWqjn4+4fai+fVutHhAk KIX5ZqiAQ9L+FymgBdEXHyQX+Me+8MOSsic+tVW1ZPDYF8HS5+FKZMk6LM1NCMwYPiLC QRG//ySCPPEgYPv0tSJH7giOeYQvJDd85LIJYcWYMVikLRjC+QO1goQcT3Lq4EQLqQaS UREXUFtPzE9NbVro7fB5r/VUoYsNygYOcBxQzKgjBoG7d+fZwa33/EsIjS//8DYDx6U+ VAdw== MIME-Version: 1.0 Received: by 10.50.95.231 with SMTP id dn7mr8705315igb.37.1348588376097; Tue, 25 Sep 2012 08:52:56 -0700 (PDT) Received: by 10.231.55.70 with HTTP; Tue, 25 Sep 2012 08:52:56 -0700 (PDT) Date: Tue, 25 Sep 2012 10:52:56 -0500 Message-ID: From: Behcet Sarikaya To: fmc@ietf.org Content-Type: multipart/mixed; boundary=e89a8f2354bf1b01f504ca88b3d5 Subject: [fmc] BoF Request & Charter Items Proposal 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, 25 Sep 2012 15:52:57 -0000 --e89a8f2354bf1b01f504ca88b3d5 Content-Type: text/plain; charset=ISO-8859-1 Hi all, We made a BoF request for IETF 85 in Atlanta, you can see the details at IETF's BoF Wiki page: http://trac.tools.ietf.org/bof/trac/wiki/WikiStart I am attaching our proposed charter items to this mail. Regards, Behcet --e89a8f2354bf1b01f504ca88b3d5 Content-Type: text/plain; charset=US-ASCII; name="fmcproposedcharteritems0912.txt" Content-Disposition: attachment; filename="fmcproposedcharteritems0912.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h7j6nqcq0 DQoNCkdPQUxTIEFORCBNSUxFU1RPTkVTDQoNCg0KDQpBcHJpbCAyMDEzIFJlcXVpcmVtZW50cyBm b3IgZml4ZWQgbW9iaWxlIGNvbnZlcmdlbmNlIGRvY3VtZW50IGFzIGluZm9ybWF0aW9uYWwgc3Rh bmRhcmQgdG8gSUVTRw0KDQpNYXkgMjAxMyBTb2x1dGlvbiBhbmFseXNpcyBhbmQgc2VsZWN0aW9u IGRvY3VtZW50IGZvciBVRSBpZGVudGlmaWNhdGlvbiBhcyBpbmZvcm1hdGlvbmFsIHN0YW5kYXJk IHRvIElFU0cNCg0KU2VwdGVtYmVyIDIwMTMgVUUgaWRlbnRpZmljYXRpb24gc29sdXRpb24gZG9j dW1lbnQgYXMgcHJvcG9zZWQgc3RhbmRhcmQgdG8gSUVTRw0KDQpEZWNlbWJlciAyMDEzIFVFIE1v YmlsaXR5IHNvbHV0aW9uIGRvY3VtZW50IGFzIHByb3Bvc2VkIHN0YW5kYXJkIHRvIElFU0cNCg0K RmVicnVhcnkgMjAxNCBUcmFuc3BvcnRhdGlvbiBvZiBVRSBXaS1GaSBMaW5rIENoYXJhY3Rlcmlz dGljcyBzb2x1dGlvbiBkb2N1bWVudCBhcyBwcm9wb3NlZCBzdGFuZGFyZCB0byBJRVNHDQoNClJl Y2hhcnRlciBvciBjbG9zZSB3b3JraW5nIGdyb3Vw --e89a8f2354bf1b01f504ca88b3d5-- From sarikaya2012@gmail.com Tue Sep 25 12:22:35 2012 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 0CA3921F889C for ; Tue, 25 Sep 2012 12:22:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.404 X-Spam-Level: X-Spam-Status: No, score=-3.404 tagged_above=-999 required=5 tests=[AWL=0.196, BAYES_00=-2.599, 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 yJyWcqCGTiwL for ; Tue, 25 Sep 2012 12:22:31 -0700 (PDT) Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 38BFE21F889E for ; Tue, 25 Sep 2012 12:22:31 -0700 (PDT) Received: by obqv19 with SMTP id v19so681489obq.31 for ; Tue, 25 Sep 2012 12:22:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ZuRt4GWfbetaLuHARvQXKhUS8xrftCgHNjPG4+KcrI8=; b=qXXlwcjNrNiqnabLWq5X52ezMZcRCmcH2hv7b1LPiTWhsh0MSpGO15MwEfDfdXuowh Uh90DVS2XFB5DC+6A+HVk9nw2yaNPZnAf0bzsh/zRHOBhsLo+Jpd92Pf73Wr7eYFXNCq bDvXxHe8TXvuPPkCkJqELC6RDJz8fKAB841JXf+jFlYaRjUWp1tvUadSffQm0M6sC9sl jOIzoyIHqAKowVCA1bY1ccFEnmavIORMDWfDWXpa27QrW6eUZX1W5U7PNtgJCsXbLmOm A3+ONxJjVFP504HZLFjnjfr8K43q6zqyiX5Ob8boPtXrzJka2jXvolhOfGGsnZuOK0h4 pTFQ== MIME-Version: 1.0 Received: by 10.60.29.202 with SMTP id m10mr13052774oeh.11.1348600946792; Tue, 25 Sep 2012 12:22:26 -0700 (PDT) Received: by 10.60.17.37 with HTTP; Tue, 25 Sep 2012 12:22:26 -0700 (PDT) In-Reply-To: <5061EFDC.5090209@concordia.ca> References: <5061EFDC.5090209@concordia.ca> Date: Tue, 25 Sep 2012 14:22:26 -0500 Message-ID: From: Behcet Sarikaya To: John William Atwood Content-Type: multipart/mixed; boundary=e89a8ff1c14460976d04ca8ba030 Cc: fmc@ietf.org Subject: Re: [fmc] BoF Request & Charter Items Proposal 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, 25 Sep 2012 19:22:35 -0000 --e89a8ff1c14460976d04ca8ba030 Content-Type: text/plain; charset=ISO-8859-1 Thanks Bill, I did the modifications suggested. Behcet On Tue, Sep 25, 2012 at 12:54 PM, John William Atwood wrote: > Behcet, > > The "informational" classification for an RFC carries with it the > implication that the document is _not_ defining a standard. Therefore, > I believe that the phrase "informational standard" in the charter items > is incorrect and misleading. > > I suggest that you use "informational document" in place of > "informational standard" in the two places where it occurs. > Alternatively, you could invert the order of "to IETF" and "as > informational" and write the following: > > April 2013 Requirements for fixed mobile convergence document to IESG as > informational > May 2013 Solution analysis and selection document for UE identification > to IESG as informational > . . . > > This option has the advantage that the word "document" is not repeated > in the bullet point. > > Bill > > > On 9/25/2012 11:52 AM, Behcet Sarikaya wrote: >> Hi all, >> >> We made a BoF request for IETF 85 in Atlanta, you can see the details >> at IETF's BoF Wiki page: >> >> http://trac.tools.ietf.org/bof/trac/wiki/WikiStart >> >> I am attaching our proposed charter items to this mail. >> >> Regards, >> >> Behcet >> >> >> _______________________________________________ >> fmc mailing list >> fmc@ietf.org >> https://www.ietf.org/mailman/listinfo/fmc > > -- > Dr. J.W. Atwood, Eng. tel: +1 (514) 848-2424 x3046 > Distinguished Professor Emeritus fax: +1 (514) 848-2830 > Department of Computer Science > and Software Engineering > Concordia University EV 3.185 email:william.atwood@concordia.ca > 1455 de Maisonneuve Blvd. West http://users.encs.concordia.ca/~bill > Montreal, Quebec Canada H3G 1M8 > --e89a8ff1c14460976d04ca8ba030 Content-Type: text/plain; charset=US-ASCII; name="fmcproposedcharteritems0912v2.txt" Content-Disposition: attachment; filename="fmcproposedcharteritems0912v2.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h7je5igj0 DQoNCkdPQUxTIEFORCBNSUxFU1RPTkVTDQoNCg0KDQpBcHJpbCAyMDEzIFJlcXVpcmVtZW50cyBm b3IgZml4ZWQgbW9iaWxlIGNvbnZlcmdlbmNlIGRvY3VtZW50IHRvIElFU0cgYXMgaW5mb3JtYXRp b25hbA0KDQpNYXkgMjAxMyBTb2x1dGlvbiBhbmFseXNpcyBhbmQgc2VsZWN0aW9uIGRvY3VtZW50 IGZvciBVRSBpZGVudGlmaWNhdGlvbiB0byBJRVNHIGZvciBwdWJsaWNhdGlvbiBhcyBpbmZvcm1h dGlvbmFsDQoNClNlcHRlbWJlciAyMDEzIFVFIGlkZW50aWZpY2F0aW9uIHNvbHV0aW9uIGRvY3Vt ZW50IHRvIElFU0cgZm9yIHB1YmxpY2F0aW9uIGFzIHByb3Bvc2VkIHN0YW5kYXJkIA0KDQpEZWNl bWJlciAyMDEzIFVFIE1vYmlsaXR5IHNvbHV0aW9uIGRvY3VtZW50IHRvIElFU0cgZm9yIHB1Ymxp Y2F0aW9uIGFzIHByb3Bvc2VkIHN0YW5kYXJkDQoNCkZlYnJ1YXJ5IDIwMTQgVHJhbnNwb3J0YXRp b24gb2YgVUUgV2ktRmkgTGluayBDaGFyYWN0ZXJpc3RpY3Mgc29sdXRpb24gZG9jdW1lbnQgdG8g SUVTRyBmb3IgcHVibGljYXRpb24gYXMgcHJvcG9zZWQgc3RhbmRhcmQNCg0KUmVjaGFydGVyIG9y IGNsb3NlIHdvcmtpbmcgZ3JvdXA= --e89a8ff1c14460976d04ca8ba030-- From sarikaya2012@gmail.com Fri Sep 28 12:28:29 2012 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 18A6521F84BF for ; Fri, 28 Sep 2012 12:28:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.457 X-Spam-Level: X-Spam-Status: No, score=-3.457 tagged_above=-999 required=5 tests=[AWL=0.142, BAYES_00=-2.599, 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 k5ZnMJl2ac+v for ; Fri, 28 Sep 2012 12:28:28 -0700 (PDT) Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8E31321F8498 for ; Fri, 28 Sep 2012 12:28:28 -0700 (PDT) Received: by iec9 with SMTP id 9so9351626iec.31 for ; Fri, 28 Sep 2012 12:28:26 -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=WoWYf122qlduuYMHDOjjM3bW7rYsWpZ5TSwQj2JE1jo=; b=PrUuarLLkSXEdLWI5H+MCZPTe0qYXaG8mPEhHnPkI/IaETUWrqi8k+ohXV+fOslZoV 2GkRZ4nm2D5K1Uktqmspi6PF+Y8taKIPVORanH60GKVlWesp3nRdN0lU8FTlV8a0VTq0 rtpu879O0V8LayHFqQ6gjuuZNJERRU4t6/3p652zVlPpEUOI1w6f7xJ1f/OX2p6lpyU8 UPK9PjIds9BfjSu+zI0EeFyOvRoS/xHPwZvb3CnZb2CICCdbsX/e+8ewgSsM1OV8cJ79 gnB7Jf58xfE0DleOExXX1PpRc08bXOTu+9jaWi/SpBg47Myb8aZ7ZqN89gr3A6oPSV77 yuEw== MIME-Version: 1.0 Received: by 10.50.53.170 with SMTP id c10mr2655417igp.45.1348860506005; Fri, 28 Sep 2012 12:28:26 -0700 (PDT) Received: by 10.231.55.70 with HTTP; Fri, 28 Sep 2012 12:28:25 -0700 (PDT) Date: Fri, 28 Sep 2012 14:28:25 -0500 Message-ID: From: Behcet Sarikaya To: fmc@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Dirk.von-Hugo@telekom.de Subject: [fmc] Use cases 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: Fri, 28 Sep 2012 19:28:29 -0000 Folks, Our BoF Request has been accepted. We are expecting to have a session for fmc BoF is to be scheduled in IETF 85. However, Brian, our Area Director asked, based on the feedback given to IETF that tt would be good to narrow the scope and focus on one or two well-defined issues. Ideally, these would be issues that, if solved, would provide building blocks for follow-on efforts. It would also be good if those issues fall within the same IETF area, i.e. Int Area. My suggestion is to drop one of the use cases and keep the other two. Which one or ones we should drop in our efforts to narrow the scope? Our use cases are (from the BoF page): UE Identification use case, UE Mobility use case, Transporting link characteristics use case. Please speak up. Regards, Behcet From bingxuere@gmail.com Fri Sep 28 18:27:22 2012 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 9DB1621F84FF for ; Fri, 28 Sep 2012 18:27:22 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 86CeaCN6ISki for ; Fri, 28 Sep 2012 18:27:21 -0700 (PDT) Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id C5FF821F8449 for ; Fri, 28 Sep 2012 18:27:21 -0700 (PDT) Received: by obqv19 with SMTP id v19so4218500obq.31 for ; Fri, 28 Sep 2012 18:27:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7o53fAsxJ/U7NGFj/TBcqm2GNydzdyNi5DTchHP/wLU=; b=B7dIIbs2cA0062VSSe32hgbH8IGtRroi7Ko3AhBAQq8jG6YzjVv42DzJLHnl19DXjU 5mmNZEyH/qmdZmcdU1vOTpqw6ErQv11xaMvExAuWcY+EicZPtl/Sft/K45nlHzyQAGJR 1B9qhyjA8ZO1BAzIPS0NP87lDZHnSviUGZSNeQGzDSU8QWkYY2u6z4EC2EDFZTV93qw7 xvulmAZTGPvRjEPgGrzXMJs1AG4kgMDMXb0WA7VwxRbqs4xfOjrM1lfw6IWOqkQcsZjn 6WYO3ULmz7f//vwb+zOoSuyHKucBar5znv1hp4ygkzeTthOzIBq20EMQuiZUfmUlbkWk kQFg== Received: by 10.60.7.104 with SMTP id i8mr7080548oea.31.1348882041318; Fri, 28 Sep 2012 18:27:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.87.104 with HTTP; Fri, 28 Sep 2012 18:26:41 -0700 (PDT) In-Reply-To: References: From: Qiong Date: Sat, 29 Sep 2012 09:26:41 +0800 Message-ID: To: sarikaya@ieee.org Content-Type: multipart/alternative; boundary=e89a8fb1ef14eaadc604cacd12ef Cc: fmc@ietf.org, Dirk.von-Hugo@telekom.de Subject: Re: [fmc] Use cases 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: Sat, 29 Sep 2012 01:27:22 -0000 --e89a8fb1ef14eaadc604cacd12ef Content-Type: text/plain; charset=UTF-8 Hi, Behcet, >From my point of view, the priority of these three use cases are (from high to low): 1) UE Identification use case, 2) UE Mobility use case, 3) Transporting link characteristics use case. If I have to drop one, I would chose the third one. Best wishes Qiong On Sat, Sep 29, 2012 at 3:28 AM, Behcet Sarikaya wrote: > Folks, > > Our BoF Request has been accepted. We are expecting to have a session > for fmc BoF is to be scheduled in IETF 85. > > However, Brian, our Area Director asked, based on the feedback given > to IETF that > tt would be good to narrow the scope and focus on one or two > well-defined issues. Ideally, these would be issues that, if solved, > would provide building blocks for follow-on efforts. It would also be > good if those issues fall within the same IETF area, i.e. Int Area. > > My suggestion is to drop one of the use cases and keep the other two. > Which one or ones we should drop in our efforts to narrow the scope? > > Our use cases are (from the BoF page): > > UE Identification use case, > > UE Mobility use case, > > Transporting link characteristics use case. > > Please speak up. > > Regards, > > Behcet > _______________________________________________ > fmc mailing list > fmc@ietf.org > https://www.ietf.org/mailman/listinfo/fmc > -- ============================================== Qiong Sun China Telecom Beijing Research Institude Open source code: lightweight 4over6: *http://sourceforge.net/projects/laft6/* PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/ * =============================================== --e89a8fb1ef14eaadc604cacd12ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Behcet,

From my point of view, the priority of these three use c= ases are (from high to low):
1) UE Identification use case,
2) UE Mobility use case,
3) Transporting link characteristics use case.

If I have to drop one= , I would chose the third one.

Best wishes
Qiong

On Sat, Sep 29, 2012 at 3:28 AM, Behcet Sarikaya <s= arikaya2012@gmail.com> wrote:
Folks,

Our BoF Request has been accepted. We are expecting to have a session
for fmc BoF is to be scheduled in IETF 85.

However, Brian, our Area Director asked, based on the feedback given
to IETF that
tt would be good to narrow the scope and focus on one or two
well-defined issues. =C2=A0Ideally, these would be issues that, if solved,<= br> would provide building blocks for follow-on efforts. =C2=A0It would also be=
good if those issues fall within the same IETF area, i.e. Int Area.

My suggestion is to drop one of the use cases and keep the other two.
Which one or ones we should drop in our efforts to narrow the scope?

Our use cases are (from the BoF page):

UE Identification use case,

UE Mobility use case,

Transporting link characteristics use case.

Please speak up.

Regards,

Behcet
_______________________________________________
fmc mailing list
fmc@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/fmc



--
=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Qiong Sun
China Telecom Be= ijing Research Institude


Open source code:
lightweight 4over6= : h= ttp://sourceforge.net/projects/laft6/
PCP-natcoord: http://sourceforge.net/projects/pcpportsetdemo/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

--e89a8fb1ef14eaadc604cacd12ef--