From mipshop-mih-dt-bounces@ietf.org Wed Jan 10 16:27:22 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H4kyg-0002sU-KM; Wed, 10 Jan 2007 16:27:22 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H4kyf-0002sP-W9 for mipshop-mih-dt@ietf.org; Wed, 10 Jan 2007 16:27:22 -0500 Received: from rsys002x.roke.co.uk ([193.118.201.109]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4kyd-0002ZI-AK for mipshop-mih-dt@ietf.org; Wed, 10 Jan 2007 16:27:21 -0500 Received: from rsys005a.comm.ad.roke.co.uk (rsys005a [193.118.193.85]) by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id l0ALQvC1009575 for ; Wed, 10 Jan 2007 21:26:57 GMT Received: from ehlaptop ([193.118.192.66]) by rsys005a.comm.ad.roke.co.uk with Microsoft SMTPSVC(6.0.3790.1830); Wed, 10 Jan 2007 21:26:57 +0000 From: "Robert Hancock" To: Date: Wed, 10 Jan 2007 21:26:58 -0000 Message-ID: <01aa01c734fe$0f7f3180$0100000a@comm.ad.roke.co.uk> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Thread-Index: Acc0/g9C7G5rTrWRQf61E6+qhuENtQ== X-OriginalArrivalTime: 10 Jan 2007 21:26:57.0330 (UTC) FILETIME=[0E854120:01C734FE] X-MailScanner-roke-co-uk: Found to be clean X-MailScanner-roke-co-uk-SpamCheck: X-MailScanner-From: robert.hancock@roke.co.uk X-Spam-Score: 1.8 (+) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Subject: [MIPSHOP-MIH-DT] this is a test message X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0847084354==" Errors-To: mipshop-mih-dt-bounces@ietf.org This is a multi-part message in MIME format. --===============0847084354== Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AB_01C734FE.0F7F3180" This is a multi-part message in MIME format. ------=_NextPart_000_01AB_01C734FE.0F7F3180 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit please ignore this one. if this works, i'll send a real message! robert h. ------=_NextPart_000_01AB_01C734FE.0F7F3180 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable this is a test message

please ignore this one. if this works, = i'll send a real message!

robert h.

------=_NextPart_000_01AB_01C734FE.0F7F3180-- --===============0847084354== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt --===============0847084354==-- From mipshop-mih-dt-bounces@ietf.org Tue Jan 23 05:34:51 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9IzL-0005AA-88; Tue, 23 Jan 2007 05:34:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9IzK-0005A5-Cu for mipshop-mih-dt@ietf.org; Tue, 23 Jan 2007 05:34:50 -0500 Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9IzI-0004a6-QN for mipshop-mih-dt@ietf.org; Tue, 23 Jan 2007 05:34:50 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCB00566H4E40@szxga01-in.huawei.com> for mipshop-mih-dt@ietf.org; Tue, 23 Jan 2007 18:29:03 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCB00MMVH4E4J@szxga01-in.huawei.com> for mipshop-mih-dt@ietf.org; Tue, 23 Jan 2007 18:29:02 +0800 (CST) Received: from x49105 ([10.111.12.66]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JCB000GKH4A41@szxml03-in.huawei.com> for mipshop-mih-dt@ietf.org; Tue, 23 Jan 2007 18:29:02 +0800 (CST) Date: Tue, 23 Jan 2007 18:28:58 +0800 From: Sam Xia Subject: RE: [MIPSHOP-MIH-DT] this is a test message In-reply-to: <01aa01c734fe$0f7f3180$0100000a@comm.ad.roke.co.uk> To: 'Robert Hancock' Message-id: <000001c73ed9$4b429ab0$420c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook 11 Thread-index: Acc0/g9C7G5rTrWRQf61E6+qhuENtQJ2yVdw X-Spam-Score: 0.0 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0977131960==" Errors-To: mipshop-mih-dt-bounces@ietf.org This is a multi-part message in MIME format. --===============0977131960== Content-type: multipart/alternative; boundary="Boundary_(ID_h+i/FNJFdbRSr7k45YZicQ)" This is a multi-part message in MIME format. --Boundary_(ID_h+i/FNJFdbRSr7k45YZicQ) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Hi, Robert, What is your planning of MIH designing? Best Regards, Sam Xia _____ From: Robert Hancock [mailto:robert.hancock@roke.co.uk] Sent: Thursday, January 11, 2007 5:27 AM To: mipshop-mih-dt@ietf.org Subject: [MIPSHOP-MIH-DT] this is a test message please ignore this one. if this works, i'll send a real message! robert h. --Boundary_(ID_h+i/FNJFdbRSr7k45YZicQ) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT this is a test message
Hi, Robert,
 What is your planning of MIH designing?
 

 Best Regards, Sam Xia

 

From: Robert Hancock [mailto:robert.hancock@roke.co.uk]
Sent: Thursday, January 11, 2007 5:27 AM
To: mipshop-mih-dt@ietf.org
Subject: [MIPSHOP-MIH-DT] this is a test message

please ignore this one. if this works, i'll send a real message!

robert h.

--Boundary_(ID_h+i/FNJFdbRSr7k45YZicQ)-- --===============0977131960== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt --===============0977131960==-- From mipshop-mih-dt-bounces@ietf.org Tue Jan 23 11:54:54 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Ov8-0000In-Lt; Tue, 23 Jan 2007 11:54:54 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Ov7-0000Ig-Gh for mipshop-mih-dt@ietf.org; Tue, 23 Jan 2007 11:54:53 -0500 Received: from host2.marvell.com ([65.219.4.2] helo=maili.marvell.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9Ov5-0008QX-KQ for mipshop-mih-dt@ietf.org; Tue, 23 Jan 2007 11:54:53 -0500 Received: from MSI-MTA.marvell.com (msi-mta.marvell.com [10.68.76.91]) by maili.marvell.com (Postfix) with ESMTP id 491CF1D26C; Tue, 23 Jan 2007 08:54:51 -0800 (PST) Received: from SC-EXCH01.marvell.com ([10.68.76.80]) by MSI-MTA.marvell.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 23 Jan 2007 08:54:50 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [MIPSHOP-MIH-DT] this is a test message Date: Tue, 23 Jan 2007 08:54:48 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MIPSHOP-MIH-DT] this is a test message Thread-Index: Acc0/g9C7G5rTrWRQf61E6+qhuENtQJ2yVdwAA13hNA= From: "Stefano Faccin" To: "Sam Xia" , "Robert Hancock" X-OriginalArrivalTime: 23 Jan 2007 16:54:50.0914 (UTC) FILETIME=[3296A020:01C73F0F] X-Spam-Score: 0.0 (/) X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798 Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0300312746==" Errors-To: mipshop-mih-dt-bounces@ietf.org This is a multi-part message in MIME format. --===============0300312746== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C73F0F.327B0E80" This is a multi-part message in MIME format. ------_=_NextPart_001_01C73F0F.327B0E80 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Guys, I haven't seen any activity yet. Robert, what's the status? We're way behind with the plan we decided at the last meeting. If you cannot lead the team, please let me know NOW. Stefano =20 ________________________________ From: Sam Xia [mailto:xiazhongqi@huawei.com]=20 Sent: Tuesday, January 23, 2007 2:29 AM To: 'Robert Hancock' Cc: mipshop-mih-dt@ietf.org Subject: RE: [MIPSHOP-MIH-DT] this is a test message =20 Hi, Robert, What is your planning of MIH designing? =20 Best Regards, Sam Xia=20 =20 =20 =09 ________________________________ From: Robert Hancock [mailto:robert.hancock@roke.co.uk]=20 Sent: Thursday, January 11, 2007 5:27 AM To: mipshop-mih-dt@ietf.org Subject: [MIPSHOP-MIH-DT] this is a test message please ignore this one. if this works, i'll send a real message! robert h.=20 ------_=_NextPart_001_01C73F0F.327B0E80 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable this is a test message

Guys,

I haven’t seen any activity = yet. Robert, what’s the status? We’re way behind with the plan we decided at the last meeting. If you cannot lead the team, please let me = know NOW.

Stefano

=

 

From: Sam = Xia [mailto:xiazhongqi@huawei.com]
Sent: Tuesday, January = 23, 2007 2:29 AM
To: 'Robert Hancock'
Cc: = mipshop-mih-dt@ietf.org
Subject: RE: = [MIPSHOP-MIH-DT] this is a test message

 

Hi, = Robert,

 What is your planning of MIH = designing?

 

 Best Regards, Sam Xia

 

 

From: Robert Hancock [mailto:robert.hancock@roke.co.uk]
Sent: Thursday, January = 11, 2007 5:27 AM
To: = mipshop-mih-dt@ietf.org
Subject: [MIPSHOP-MIH-DT] = this is a test message

please ignore this one. if this works, i'll send a real message! =

robert h.

------_=_NextPart_001_01C73F0F.327B0E80-- --===============0300312746== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt --===============0300312746==-- From mipshop-mih-dt-bounces@ietf.org Wed Jan 24 09:55:35 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9jXD-0006RS-8j; Wed, 24 Jan 2007 09:55:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9jXB-0006R2-Ap for mipshop-mih-dt@ietf.org; Wed, 24 Jan 2007 09:55:33 -0500 Received: from rsys002x.roke.co.uk ([193.118.201.109]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9jX9-0001oh-3z for mipshop-mih-dt@ietf.org; Wed, 24 Jan 2007 09:55:33 -0500 Received: from rsys005a.comm.ad.roke.co.uk (rsys005a [193.118.193.85]) by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id l0OEt4ox020751 for ; Wed, 24 Jan 2007 14:55:04 GMT Received: from ehlaptop ([193.118.192.66]) by rsys005a.comm.ad.roke.co.uk with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jan 2007 14:54:59 +0000 From: "Robert Hancock" To: Date: Wed, 24 Jan 2007 15:54:47 +0100 Message-ID: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Thread-Index: Acc0/g9C7G5rTrWRQf61E6+qhuENtQJ2yVdwAA13hNAALThggA== In-Reply-To: X-OriginalArrivalTime: 24 Jan 2007 14:55:00.0974 (UTC) FILETIME=[9F7698E0:01C73FC7] X-MailScanner-roke-co-uk: Found to be clean X-MailScanner-roke-co-uk-SpamCheck: X-MailScanner-From: robert.hancock@roke.co.uk X-Spam-Score: 0.0 (/) X-Scan-Signature: 562cdc9baa87554b29d950396a30cf75 Subject: [MIPSHOP-MIH-DT] admin stuff X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1488222218==" Errors-To: mipshop-mih-dt-bounces@ietf.org This is a multi-part message in MIME format. --===============1488222218== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0480_01C73FD0.00ABB930" This is a multi-part message in MIME format. ------=_NextPart_000_0480_01C73FD0.00ABB930 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit hi guys, sorry for my silence. i'm not entirely well at the moment but will see what i can do. the rest of this mail is about admin: the current subscriber list is * heejin.jang@samsung.com * john.loughney@nokia.com * JuanCarlos.Zuniga@interdigital.com * robert.hancock@roke.co.uk * Srinivas.Sreemanthula@nokia.com * stefano.m.faccin@marvell.com * subir@research.telcordia.com * telemaco.melia@netlab.nec.de * vijay.devarapalli@azairenet.com * xiazhongqi@huawei.com it would be helpful if those people (who haven't already replied to the test message...) can confirm to me that they can receive this mail so I know I got all the addresses right. the list is subscriber only post. if you need to post from multiple addresses, please subscribe using the usual mailman procedures. subscriptions have to be approved (by me). please note that the design team work, and this mailing list, are (so far as I know) IETF activities in the sense of RFC 3978/4748. In other words, the standard provisions of the 'Note Well' notice apply. finally, please note that the mailing list archive is currently public. my preference would be that the archive is openly available for the long term as a record of the work of the DT, and at the moment I don't see a reason to close it for the short term. Please bear that in mind in posting. If people have different preferences, please speak up and we can all discuss it. cheers, robert h. _____ From: Stefano Faccin [mailto:stefano.m.faccin@marvell.com] Sent: 23 January 2007 17:55 To: Sam Xia; Robert Hancock Cc: mipshop-mih-dt@ietf.org Subject: RE: [MIPSHOP-MIH-DT] this is a test message Guys, I haven't seen any activity yet. Robert, what's the status? We're way behind with the plan we decided at the last meeting. If you cannot lead the team, please let me know NOW. Stefano _____ From: Sam Xia [mailto:xiazhongqi@huawei.com] Sent: Tuesday, January 23, 2007 2:29 AM To: 'Robert Hancock' Cc: mipshop-mih-dt@ietf.org Subject: RE: [MIPSHOP-MIH-DT] this is a test message Hi, Robert, What is your planning of MIH designing? Best Regards, Sam Xia _____ From: Robert Hancock [mailto:robert.hancock@roke.co.uk] Sent: Thursday, January 11, 2007 5:27 AM To: mipshop-mih-dt@ietf.org Subject: [MIPSHOP-MIH-DT] this is a test message please ignore this one. if this works, i'll send a real message! robert h. ------=_NextPart_000_0480_01C73FD0.00ABB930 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable this is a test = message
hi guys,
 
sorry for my silence. i'm not entirely well at = the moment=20 but will see what i can do.
 
the rest of this mail is about = admin:
 
the current subscriber list = is
  • heejin.jang@samsung.com
  • john.loughney@nokia.com
  • JuanCarlos.Zuniga@interdigital.com
  • robert.hancock@roke.co.uk
  • Srinivas.Sreemanthula@nokia.com
  • stefano.m.faccin@marvell.com
  • subir@research.telcordia.com
  • telemaco.melia@netlab.nec.de
  • vijay.devarapalli@azairenet.com
  • xiazhongqi@huawei.com
it would be helpful if those people (who = haven't already=20 replied to the test message...) can confirm to me that they can receive = this=20 mail so I know I got all the addresses right.
 
the list is subscriber only post. if you need = to post from=20 multiple addresses, please subscribe using the usual mailman procedures. = subscriptions have to be approved (by me).
 
please note that the design team work, and this = mailing=20 list, are (so far as I know) IETF activities in the sense of RFC = 3978/4748. In=20 other words, the standard provisions of the 'Note Well' notice=20 apply.
 
finally, please note that the mailing list = archive is=20 currently public. my preference would be that the archive is openly = available=20 for the long term as a record of the work of the DT, and at the moment I = don't=20 see a reason to close it for the short term. Please bear that in mind in = posting. If people have different preferences, please speak up and we = can all=20 discuss it.
 
cheers,
 
robert h.
 

From: Stefano Faccin=20 [mailto:stefano.m.faccin@marvell.com]
Sent: 23 January 2007 = 17:55
To: Sam Xia; Robert Hancock
Cc:=20 mipshop-mih-dt@ietf.org
Subject: RE: [MIPSHOP-MIH-DT] this = is a test=20 message

Guys,

I = haven’t seen any=20 activity yet. Robert, what’s the status? We’re way behind = with the plan we=20 decided at the last meeting. If you cannot lead the team, please let = me know=20 NOW.

Stefano

 

From: Sam Xia=20 [mailto:xiazhongqi@huawei.com]
Sent: Tuesday, January 23, 2007 = 2:29=20 AM
To: 'Robert=20 Hancock'
Cc:=20 mipshop-mih-dt@ietf.org
Subject: RE: [MIPSHOP-MIH-DT] = this is a=20 test message

 

Hi,=20 Robert,

 What is = your=20 planning of MIH designing?

 

 Best=20 Regards, Sam Xia

 

 

From:=20 Robert Hancock [mailto:robert.hancock@roke.co.uk]
Sent: Thursday, January 11, = 2007 5:27=20 AM
To:=20 mipshop-mih-dt@ietf.org
Subject: [MIPSHOP-MIH-DT] = this is a=20 test message

please=20 ignore this one. if this works, i'll send a real = message!=20

robert = h.=20

------=_NextPart_000_0480_01C73FD0.00ABB930-- --===============1488222218== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt --===============1488222218==-- From mipshop-mih-dt-bounces@ietf.org Wed Jan 24 10:11:38 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9jmk-0006kd-Jd; Wed, 24 Jan 2007 10:11:38 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9jmj-0006kY-9f for mipshop-mih-dt@ietf.org; Wed, 24 Jan 2007 10:11:37 -0500 Received: from smtp0.netlab.nec.de ([195.37.70.40]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H9jmh-0005Ow-7O for mipshop-mih-dt@ietf.org; Wed, 24 Jan 2007 10:11:37 -0500 Received: from localhost (atlas1.office [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 11FEB2004BF8; Wed, 24 Jan 2007 16:12:10 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office) Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77d0FhQu7jhL; Wed, 24 Jan 2007 16:12:09 +0100 (CET) Received: from mx1.office (mx1.office [10.1.1.23]) by smtp0.netlab.nec.de (Postfix) with ESMTP id DA90C20001AF; Wed, 24 Jan 2007 16:12:09 +0100 (CET) Received: from [127.0.0.1] ([10.1.1.217]) by mx1.office over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jan 2007 16:11:30 +0100 Message-ID: <45B77721.1040406@netlab.nec.de> Date: Wed, 24 Jan 2007 16:11:29 +0100 From: Telemaco Melia User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Robert Hancock Subject: Re: [MIPSHOP-MIH-DT] admin stuff References: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> In-Reply-To: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> X-OriginalArrivalTime: 24 Jan 2007 15:11:30.0087 (UTC) FILETIME=[ED054370:01C73FC9] X-Spam-Score: 0.0 (/) X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6 Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0315782645==" Errors-To: mipshop-mih-dt-bounces@ietf.org This is a multi-part message in MIME format. --===============0315782645== Content-Type: multipart/alternative; boundary="------------070801060807000902090206" This is a multi-part message in MIME format. --------------070801060807000902090206 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Ack. regards, telemaco Robert Hancock wrote: > hi guys, > > sorry for my silence. i'm not entirely well at the moment but will see > what i can do. > > the rest of this mail is about admin: > > the current subscriber list is > > * > heejin.jang@samsung.com > * > john.loughney@nokia.com > * > JuanCarlos.Zuniga@interdigital.com > * > robert.hancock@roke.co.uk > * > Srinivas.Sreemanthula@nokia.com > * > stefano.m.faccin@marvell.com > * > subir@research.telcordia.com > * > telemaco.melia@netlab.nec.de > * > vijay.devarapalli@azairenet.com > * > xiazhongqi@huawei.com > > it would be helpful if those people (who haven't already replied to > the test message...) can confirm to me that they can receive this mail > so I know I got all the addresses right. > > the list is subscriber only post. if you need to post from multiple > addresses, please subscribe using the usual mailman procedures. > subscriptions have to be approved (by me). > > please note that the design team work, and this mailing list, are (so > far as I know) IETF activities in the sense of RFC 3978/4748. In other > words, the standard provisions of the 'Note Well' notice apply. > > finally, please note that the mailing list archive is currently > public. my preference would be that the archive is openly available > for the long term as a record of the work of the DT, and at the moment > I don't see a reason to close it for the short term. Please bear that > in mind in posting. If people have different preferences, please speak > up and we can all discuss it. > > cheers, > > robert h. > > > ------------------------------------------------------------------------ > *From:* Stefano Faccin [mailto:stefano.m.faccin@marvell.com] > *Sent:* 23 January 2007 17:55 > *To:* Sam Xia; Robert Hancock > *Cc:* mipshop-mih-dt@ietf.org > *Subject:* RE: [MIPSHOP-MIH-DT] this is a test message > > Guys, > > I haven't seen any activity yet. Robert, what's the status? We're > way behind with the plan we decided at the last meeting. If you > cannot lead the team, please let me know NOW. > > Stefano > > > > ------------------------------------------------------------------------ > > *From:* Sam Xia [mailto:xiazhongqi@huawei.com] > *Sent:* Tuesday, January 23, 2007 2:29 AM > *To:* 'Robert Hancock' > *Cc:* mipshop-mih-dt@ietf.org > *Subject:* RE: [MIPSHOP-MIH-DT] this is a test message > > > > Hi, Robert, > > What is your planning of MIH designing? > > > > Best Regards, Sam Xia > > > > > > ------------------------------------------------------------------------ > > *From:* Robert Hancock [mailto:robert.hancock@roke.co.uk] > *Sent:* Thursday, January 11, 2007 5:27 AM > *To:* mipshop-mih-dt@ietf.org > *Subject:* [MIPSHOP-MIH-DT] this is a test message > > please ignore this one. if this works, i'll send a real message! > > robert h. > > ------------------------------------------------------------------------ > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > --------------070801060807000902090206 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Ack.

regards,
telemaco

Robert Hancock wrote:
this is a test message
hi guys,
 
sorry for my silence. i'm not entirely well at the moment but will see what i can do.
 
the rest of this mail is about admin:
 
the current subscriber list is
it would be helpful if those people (who haven't already replied to the test message...) can confirm to me that they can receive this mail so I know I got all the addresses right.
 
the list is subscriber only post. if you need to post from multiple addresses, please subscribe using the usual mailman procedures. subscriptions have to be approved (by me).
 
please note that the design team work, and this mailing list, are (so far as I know) IETF activities in the sense of RFC 3978/4748. In other words, the standard provisions of the 'Note Well' notice apply.
 
finally, please note that the mailing list archive is currently public. my preference would be that the archive is openly available for the long term as a record of the work of the DT, and at the moment I don't see a reason to close it for the short term. Please bear that in mind in posting. If people have different preferences, please speak up and we can all discuss it.
 
cheers,
 
robert h.
 

From: Stefano Faccin [mailto:stefano.m.faccin@marvell.com]
Sent: 23 January 2007 17:55
To: Sam Xia; Robert Hancock
Cc: mipshop-mih-dt@ietf.org
Subject: RE: [MIPSHOP-MIH-DT] this is a test message

Guys,

I haven’t seen any activity yet. Robert, what’s the status? We’re way behind with the plan we decided at the last meeting. If you cannot lead the team, please let me know NOW.

Stefano

 

From: Sam Xia [mailto:xiazhongqi@huawei.com]
Sent: Tuesday, January 23, 2007 2:29 AM
To: 'Robert Hancock'
Cc: mipshop-mih-dt@ietf.org
Subject: RE: [MIPSHOP-MIH-DT] this is a test message

 

Hi, Robert,

 What is your planning of MIH designing?

 

 Best Regards, Sam Xia

 

 

From: Robert Hancock [mailto:robert.hancock@roke.co.uk]
Sent: Thursday, January 11, 2007 5:27 AM
To: mipshop-mih-dt@ietf.org
Subject: [MIPSHOP-MIH-DT] this is a test message

please ignore this one. if this works, i'll send a real message!

robert h. 


_______________________________________________
MIPSHOP-MIH-DT mailing list
MIPSHOP-MIH-DT@ietf.org
https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt


--------------070801060807000902090206-- --===============0315782645== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt --===============0315782645==-- From mipshop-mih-dt-bounces@ietf.org Wed Jan 24 10:35:42 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9kA2-0004zl-DA; Wed, 24 Jan 2007 10:35:42 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9kA1-0004zf-91 for mipshop-mih-dt@ietf.org; Wed, 24 Jan 2007 10:35:41 -0500 Received: from rsys002x.roke.co.uk ([193.118.201.109]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9k9y-0000sG-Qb for mipshop-mih-dt@ietf.org; Wed, 24 Jan 2007 10:35:41 -0500 Received: from rsys005a.comm.ad.roke.co.uk (rsys005a [193.118.193.85]) by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id l0OFZWe1031201 for ; Wed, 24 Jan 2007 15:35:32 GMT Received: from ehlaptop ([193.118.192.66]) by rsys005a.comm.ad.roke.co.uk with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jan 2007 15:35:31 +0000 From: "Robert Hancock" To: Date: Wed, 24 Jan 2007 16:35:31 +0100 Message-ID: <04ad01c73fcd$48aef6a0$0100c90a@comm.ad.roke.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Thread-Index: Acc0/g9C7G5rTrWRQf61E6+qhuENtQJ2yVdwAA13hNAALThggAAA92Aw In-Reply-To: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> X-OriginalArrivalTime: 24 Jan 2007 15:35:32.0411 (UTC) FILETIME=[48B670B0:01C73FCD] X-MailScanner-roke-co-uk: Found to be clean X-MailScanner-roke-co-uk-SpamCheck: X-MailScanner-From: robert.hancock@roke.co.uk X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Subject: [MIPSHOP-MIH-DT] technical stuff - how to begin the work X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org Hi, We now have the question how to begin the work on a solution. One thing i want to avoid is starting off with a 'who likes what solution' discussion. My perception is that once we all have a common view on the problem, choosing a solution will actually be the simpler part of the problem. >From that point of view, I'd rather have a higher level discussion about the issues which a solution has to take account of. For that, we previously wrote the design considerations draft (still at http://tools.ietf.org/wg/mipshop/draft-hepworth-mipshop-mih-design-considera tions-01.txt) which I humbly claim at least provides a set of headings for the things that we have to worry about. Please note: - I'm not claiming that people have to agree that the analysis in that draft is correct. That is what we are discussing. I am claiming that the list of issues is pretty good. - I'm not even claiming that we have to construct an update to this draft or follow its structure; but it would be nice to capture the conclusions of our discussions in some way. Please can people say what they think about this approach. We can split up the small problems (1 each or so) and argue out any issues on this list. I think there are a few bigger issues for which we could form smaller groups to look at things. They are either harder, or require closer work with the details of the .21 standard: - one is discovery. here, there just seem to be too many different options, and we have to think about the tradeoff between allowing/supporting many and being able to enforce a universal one - another is security. we need to have a view on what security services the MIH transport actually needs (who authenticates who, what identity infrastructures that authentication might be based on) - another is the transport/application service interface. .21 is going through various versions of this, which it would be ideal to align with what we actually propose. What would be nice now is if people can say what they think about this as an approach for the work; and, if they approve of the approach, what parts of the analysis they would feel happy to take the lead on or take part in. cheers, robert h. _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt From mipshop-mih-dt-bounces@ietf.org Wed Jan 24 19:36:47 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9sbf-0001bM-Ss; Wed, 24 Jan 2007 19:36:47 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9sbf-0001aX-20 for mipshop-mih-dt@ietf.org; Wed, 24 Jan 2007 19:36:47 -0500 Received: from mail2.azairenet.com ([66.92.223.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9sbd-0001xW-PB for mipshop-mih-dt@ietf.org; Wed, 24 Jan 2007 19:36:47 -0500 Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jan 2007 16:36:44 -0800 Message-ID: <45B7FB98.9050102@azairenet.com> Date: Wed, 24 Jan 2007 16:36:40 -0800 From: Vijay Devarapalli User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Robert Hancock Subject: Re: [MIPSHOP-MIH-DT] admin stuff References: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> In-Reply-To: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 Jan 2007 00:36:44.0671 (UTC) FILETIME=[E3B018F0:01C74018] X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org Robert Hancock wrote: > finally, please note that the mailing list archive is currently public. > my preference would be that the archive is openly available for the long > term as a record of the work of the DT, and at the moment I don't see a > reason to close it for the short term. Please bear that in mind in > posting. If people have different preferences, please speak up and we > can all discuss it. It would be better to keep the archives private until a stable document or at least the first version of the solution document is available. After that the archives can be made available to the MIPSHOP WG. Vijay _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt From mipshop-mih-dt-bounces@ietf.org Thu Jan 25 10:31:37 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HA6Zc-00084S-Rk; Thu, 25 Jan 2007 10:31:37 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HA6Zc-00083B-6I for mipshop-mih-dt@ietf.org; Thu, 25 Jan 2007 10:31:36 -0500 Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HA6ZW-00068h-BM for mipshop-mih-dt@ietf.org; Thu, 25 Jan 2007 10:31:36 -0500 Received: from mailee.research.telcordia.com (mailee [192.4.16.29]) by thumper.research.telcordia.com (8.13.6/8.13.5) with ESMTP id l0PFVTeI024180; Thu, 25 Jan 2007 10:31:29 -0500 (EST) Received: from [192.4.8.227] (ar8-227 [192.4.8.227]) by mailee.research.telcordia.com (8.9.3/8.9.3) with ESMTP id KAA00492; Thu, 25 Jan 2007 10:31:29 -0500 (EST) Message-ID: <45B8CD50.5040706@research.telcordia.com> Date: Thu, 25 Jan 2007 10:31:28 -0500 From: Subir Das User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Robert Hancock Subject: Re: [MIPSHOP-MIH-DT] admin stuff References: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> In-Reply-To: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by thumper.research.telcordia.com id l0PFVTeI024180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org Robert, My email-id is correct. Thanks, -Subir Robert Hancock wrote: > hi guys, > sorry for my silence. i'm not entirely well at the moment but will see=20 > what i can do. > the rest of this mail is about admin: > the current subscriber list is > > * > heejin.jang@samsung.com > * > john.loughney@nokia.com > * > JuanCarlos.Zuniga@interdigital.com > * > robert.hancock@roke.co.uk > * > Srinivas.Sreemanthula@nokia.com > * > stefano.m.faccin@marvell.com > * > subir@research.telcordia.com > * > telemaco.melia@netlab.nec.de > * > vijay.devarapalli@azairenet.com > * > xiazhongqi@huawei.com > > it would be helpful if those people (who haven't already replied to=20 > the test message...) can confirm to me that they can receive this mail=20 > so I know I got all the addresses right. > the list is subscriber only post. if you need to post from multiple=20 > addresses, please subscribe using the usual mailman procedures.=20 > subscriptions have to be approved (by me). > please note that the design team work, and this mailing list, are (so=20 > far as I know) IETF activities in the sense of RFC 3978/4748. In other=20 > words, the standard provisions of the 'Note Well' notice apply. > finally, please note that the mailing list archive is currently=20 > public. my preference would be that the archive is openly available=20 > for the long term as a record of the work of the DT, and at the moment=20 > I don't see a reason to close it for the short term. Please bear that=20 > in mind in posting. If people have different preferences, please speak=20 > up and we can all discuss it. > cheers, > robert h. > > -------------------------------------------------------------------= ----- > *From:* Stefano Faccin [mailto:stefano.m.faccin@marvell.com] > *Sent:* 23 January 2007 17:55 > *To:* Sam Xia; Robert Hancock > *Cc:* mipshop-mih-dt@ietf.org > *Subject:* RE: [MIPSHOP-MIH-DT] this is a test message > > Guys, > > I haven=92t seen any activity yet. Robert, what=92s the status? We=92= re > way behind with the plan we decided at the last meeting. If you > cannot lead the team, please let me know NOW. > > Stefano > > -------------------------------------------------------------------= ----- > > *From:* Sam Xia [mailto:xiazhongqi@huawei.com] > *Sent:* Tuesday, January 23, 2007 2:29 AM > *To:* 'Robert Hancock' > *Cc:* mipshop-mih-dt@ietf.org > *Subject:* RE: [MIPSHOP-MIH-DT] this is a test message > > Hi, Robert, > > What is your planning of MIH designing? > > Best Regards, Sam Xia > > ---------------------------------------------------------------= --------- > > *From:* Robert Hancock [mailto:robert.hancock@roke.co.uk] > *Sent:* Thursday, January 11, 2007 5:27 AM > *To:* mipshop-mih-dt@ietf.org > *Subject:* [MIPSHOP-MIH-DT] this is a test message > > please ignore this one. if this works, i'll send a real message= ! > > robert h. > > -----------------------------------------------------------------------= - > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > =20 _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt From mipshop-mih-dt-bounces@ietf.org Fri Jan 26 03:24:39 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAMNz-0000B3-Ou; Fri, 26 Jan 2007 03:24:39 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAMNy-0000AA-0A for mipshop-mih-dt@ietf.org; Fri, 26 Jan 2007 03:24:38 -0500 Received: from szxga02-in.huawei.com ([61.144.161.54]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAMMx-00073F-UC for mipshop-mih-dt@ietf.org; Fri, 26 Jan 2007 03:23:42 -0500 Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCG00F6FV4F1L@szxga02-in.huawei.com> for mipshop-mih-dt@ietf.org; Fri, 26 Jan 2007 16:19:28 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JCG000Z2V4FHU@szxga02-in.huawei.com> for mipshop-mih-dt@ietf.org; Fri, 26 Jan 2007 16:19:27 +0800 (CST) Received: from x49105 ([10.111.12.66]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JCG00E9BV4BVW@szxml03-in.huawei.com> for mipshop-mih-dt@ietf.org; Fri, 26 Jan 2007 16:19:27 +0800 (CST) Date: Fri, 26 Jan 2007 16:19:24 +0800 From: Sam Xia Subject: RE: [MIPSHOP-MIH-DT] technical stuff - how to begin the work In-reply-to: <04ad01c73fcd$48aef6a0$0100c90a@comm.ad.roke.co.uk> To: 'Robert Hancock' , mipshop-mih-dt@ietf.org Message-id: <000001c74122$b05dcfa0$420c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: Acc0/g9C7G5rTrWRQf61E6+qhuENtQJ2yVdwAA13hNAALThggAAA92AwAFaf9nA= X-Spam-Score: 0.0 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Cc: X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org Hi, all See the inline. Best Regards, Sam Xia > -----Original Message----- > From: Robert Hancock [mailto:robert.hancock@roke.co.uk] > Sent: Wednesday, January 24, 2007 11:36 PM > To: mipshop-mih-dt@ietf.org > Subject: [MIPSHOP-MIH-DT] technical stuff - how to begin the work > > Hi, > > We now have the question how to begin the work on a solution. > > One thing i want to avoid is starting off with a 'who likes > what solution' > discussion. My perception is that once we all have a common > view on the problem, choosing a solution will actually be the > simpler part of the problem. > > >From that point of view, I'd rather have a higher level discussion > >about the > issues which a solution has to take account of. For that, we > previously wrote the design considerations draft (still at > http://tools.ietf.org/wg/mipshop/draft-hepworth-mipshop-mih-de > sign-considera > tions-01.txt) which I humbly claim at least provides a set of > headings for the things that we have to worry about. Please note: > - I'm not claiming that people have to agree that the > analysis in that draft is correct. That is what we are > discussing. I am claiming that the list of issues is pretty good. > - I'm not even claiming that we have to construct an update > to this draft or follow its structure; but it would be nice > to capture the conclusions of our discussions in some way. > > Please can people say what they think about this approach. We > can split up the small problems (1 each or so) and argue out > any issues on this list. > > I think there are a few bigger issues for which we could form > smaller groups to look at things. They are either harder, or > require closer work with the details of the .21 standard: > - one is discovery. here, there just seem to be too many > different options, and we have to think about the tradeoff > between allowing/supporting many and being able to enforce a > universal one > - another is security. we need to have a view on what > security services the MIH transport actually needs (who > authenticates who, what identity infrastructures that > authentication might be based on) > - another is the transport/application service interface. .21 > is going through various versions of this, which it would be > ideal to align with what we actually propose. I agree with robert that we could form smaller groupds to look at these issue. It is easy to discuss them in this method. > > What would be nice now is if people can say what they think > about this as an approach for the work; and, if they approve > of the approach, what parts of the analysis they would feel > happy to take the lead on or take part in. > > cheers, > > robert h. > > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt From mipshop-mih-dt-bounces@ietf.org Sat Jan 27 11:52:06 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAqmc-0002PW-Bo; Sat, 27 Jan 2007 11:52:06 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HAqmb-0002PR-Dh for mipshop-mih-dt@ietf.org; Sat, 27 Jan 2007 11:52:05 -0500 Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HAqmY-0005D3-31 for mipshop-mih-dt@ietf.org; Sat, 27 Jan 2007 11:52:05 -0500 Received: from mailee.research.telcordia.com (mailee [192.4.16.29]) by thumper.research.telcordia.com (8.13.6/8.13.5) with ESMTP id l0RGpssD021602; Sat, 27 Jan 2007 11:51:54 -0500 (EST) Received: from [128.96.59.126] (vpntnlB126 [128.96.59.126]) by mailee.research.telcordia.com (8.9.3/8.9.3) with ESMTP id LAA09922; Sat, 27 Jan 2007 11:51:54 -0500 (EST) Message-ID: <45BB8327.608@research.telcordia.com> Date: Sat, 27 Jan 2007 11:51:51 -0500 From: Subir Das User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Robert Hancock Subject: Re: [MIPSHOP-MIH-DT] technical stuff - how to begin the work References: <04ad01c73fcd$48aef6a0$0100c90a@comm.ad.roke.co.uk> In-Reply-To: <04ad01c73fcd$48aef6a0$0100c90a@comm.ad.roke.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org The draft may be a good start for discussions since it is already available. Regarding issues, I think it would be better if we discuss them together. It may be a good idea to discuss these points in a telecon and exchange the views. regards, -Subir Robert Hancock wrote: > Hi, > > We now have the question how to begin the work on a solution. > > One thing i want to avoid is starting off with a 'who likes what solution' > discussion. My perception is that once we all have a common view on the > problem, choosing a solution will actually be the simpler part of the > problem. > > >From that point of view, I'd rather have a higher level discussion about the > issues which a solution has to take account of. For that, we previously > wrote the design considerations draft (still at > http://tools.ietf.org/wg/mipshop/draft-hepworth-mipshop-mih-design-considera > tions-01.txt) which I humbly claim at least provides a set of headings for > the things that we have to worry about. Please note: > - I'm not claiming that people have to agree that the analysis in that draft > is correct. That is what we are discussing. I am claiming that the list of > issues is pretty good. > - I'm not even claiming that we have to construct an update to this draft or > follow its structure; but it would be nice to capture the conclusions of our > discussions in some way. > > Please can people say what they think about this approach. We can split up > the small problems (1 each or so) and argue out any issues on this list. > > I think there are a few bigger issues for which we could form smaller groups > to look at things. They are either harder, or require closer work with the > details of the .21 standard: > - one is discovery. here, there just seem to be too many different options, > and we have to think about the tradeoff between allowing/supporting many and > being able to enforce a universal one > - another is security. we need to have a view on what security services the > MIH transport actually needs (who authenticates who, what identity > infrastructures that authentication might be based on) > - another is the transport/application service interface. .21 is going > through various versions of this, which it would be ideal to align with what > we actually propose. > > What would be nice now is if people can say what they think about this as an > approach for the work; and, if they approve of the approach, what parts of > the analysis they would feel happy to take the lead on or take part in. > > cheers, > > robert h. > > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt From mipshop-mih-dt-bounces@ietf.org Sun Jan 28 23:33:37 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBOD3-0006fl-Da; Sun, 28 Jan 2007 23:33:37 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBOD1-0006fY-Ei for mipshop-mih-dt@ietf.org; Sun, 28 Jan 2007 23:33:35 -0500 Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBOD0-00061y-2u for mipshop-mih-dt@ietf.org; Sun, 28 Jan 2007 23:33:35 -0500 Received: from ep_ms5_bk (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0JCM00FUI4MNCR@mailout2.samsung.com> for mipshop-mih-dt@ietf.org; Mon, 29 Jan 2007 13:32:47 +0900 (KST) Received: from ep_spt01 (ms5.samsung.com [203.254.225.113]) by ms5.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0JCM000LO4MNQU@ms5.samsung.com> for mipshop-mih-dt@ietf.org; Mon, 29 Jan 2007 13:32:47 +0900 (KST) Content-return: prohibited Date: Mon, 29 Jan 2007 04:32:47 +0000 (GMT) From: Heejin Jang Subject: Re: [MIPSHOP-MIH-DT] admin stuff To: Robert Hancock Message-id: <0JCM000LP4MNQU@ms5.samsung.com> MIME-version: 1.0 MIME-version: 1.0 X-Priority: 3 Msgkey: 20070129043246934@heejin.jang X-MTR: 20070129043246934@heejin.jang X-EPLocale: ko_KR.windows-1252 X-EPWebmail-Msg-Type: personal X-EPWebmail-Reply-Demand: 0 X-EPApproval-Locale: X-Generator: NamoMIME 6.0.0.8 X-Spam-Score: 3.3 (+++) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Cc: "mipshop-mih-dt@ietf.org" X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: heejin.jang@samsung.com List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0665715577==" Errors-To: mipshop-mih-dt-bounces@ietf.org --===============0665715577== Content-return: prohibited Content-type: text/html; charset=windows-1252 Content-transfer-encoding: base64 PEhUTUw+PEhFQUQ+CjxNRVRBIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9J3RleHQv aHRtbDsgY2hhcnNldD13aW5kb3dzLTEyNTInPgo8dGl0bGU+U2Ftc3VuZyBFbnRlcnByaXNlIFBv cnRhbCBteVNpbmdsZTwvdGl0bGU+CjxzdHlsZT4gUCwgdGQsIGxpIHtmb250LWZhbWlseTpBcmlh bCwgYXJpYWw7IGZvbnQtc2l6ZTo5cHQ7IG1hcmdpbi10b3A6NXB4O21hcmdpbi1ib3R0b206NXB4 O30gYm9keXtmb250LWZhbWlseTpBcmlhbCwgYXJpYWw7IGZvbnQtc2l6ZTo5cHQ7fTwvc3R5bGU+ CjwvSEVBRD48Qk9EWT5IaSwgUm9iZXJ0LiANCjxwPkkgZ290IHRoZSZuYnNwO2VtYWlsIHN1Y2Nl ZnVsbHkuPC9wPg0KPHA+Jm5ic3A7PC9wPg0KPHA+UmVnYXJkcywgPC9wPg0KPHA+SGVlamluLjwv cD4NCjxwPiZuYnNwOzwvcD4NCjxwPiZuYnNwOzwvcD48cD4mbmJzcDs8L3A+PC9CT0RZPjwvSFRN TD4= --===============0665715577== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt --===============0665715577==-- From mipshop-mih-dt-bounces@ietf.org Mon Jan 29 11:22:56 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBZHU-0004uL-PF; Mon, 29 Jan 2007 11:22:56 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBZHS-0004u1-U0 for mipshop-mih-dt@ietf.org; Mon, 29 Jan 2007 11:22:54 -0500 Received: from idcexmail.interdigital.com ([12.32.197.135] helo=sahara.InterDigital.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBZHR-0001ZL-9F for mipshop-mih-dt@ietf.org; Mon, 29 Jan 2007 11:22:54 -0500 Received: from interdigital.com ([10.0.128.11]) by sahara.InterDigital.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Jan 2007 11:22:51 -0500 Received: from SAM.InterDigital.com ([10.30.2.12]) by interdigital.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Jan 2007 11:22:52 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: RE: [MIPSHOP-MIH-DT] admin stuff MIME-Version: 1.0 Date: Mon, 29 Jan 2007 11:22:46 -0500 Message-ID: In-Reply-To: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MIPSHOP-MIH-DT] admin stuff Thread-Index: Acc0/g9C7G5rTrWRQf61E6+qhuENtQJ2yVdwAA13hNAALThggAD/aIqw From: "Zuniga, Juan Carlos" To: "Robert Hancock" X-OriginalArrivalTime: 29 Jan 2007 16:22:52.0160 (UTC) FILETIME=[B9668000:01C743C1] X-Spam-Score: 0.0 (/) X-Scan-Signature: f90f4746216faf1f6cbda6dd26dbc608 Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1596424400==" Errors-To: mipshop-mih-dt-bounces@ietf.org This is a multi-part message in MIME format. --===============1596424400== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C743C1.B90287B6" This is a multi-part message in MIME format. ------_=_NextPart_001_01C743C1.B90287B6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Robert, =20 I got the email fine. =20 Cheers, =20 Juan Carlos =20 ________________________________ From: Robert Hancock [mailto:robert.hancock@roke.co.uk]=20 Sent: January 24, 2007 9:55 AM To: mipshop-mih-dt@ietf.org Subject: [MIPSHOP-MIH-DT] admin stuff =20 hi guys, =20 sorry for my silence. i'm not entirely well at the moment but will see what i can do. =20 the rest of this mail is about admin: =20 the current subscriber list is * heejin.jang@samsung.com=20 * john.loughney@nokia.com * JuanCarlos.Zuniga@interdigital.com * robert.hancock@roke.co.uk * Srinivas.Sreemanthula@nokia.com * stefano.m.faccin@marvell.com * subir@research.telcordia.com * telemaco.melia@netlab.nec.de * vijay.devarapalli@azairenet.com * xiazhongqi@huawei.com it would be helpful if those people (who haven't already replied to the test message...) can confirm to me that they can receive this mail so I know I got all the addresses right.=20 =20 the list is subscriber only post. if you need to post from multiple addresses, please subscribe using the usual mailman procedures. subscriptions have to be approved (by me). =20 please note that the design team work, and this mailing list, are (so far as I know) IETF activities in the sense of RFC 3978/4748. In other words, the standard provisions of the 'Note Well' notice apply. =20 finally, please note that the mailing list archive is currently public. my preference would be that the archive is openly available for the long term as a record of the work of the DT, and at the moment I don't see a reason to close it for the short term. Please bear that in mind in posting. If people have different preferences, please speak up and we can all discuss it. =20 cheers, =20 robert h. =20 =20 =09 ________________________________ From: Stefano Faccin [mailto:stefano.m.faccin@marvell.com]=20 Sent: 23 January 2007 17:55 To: Sam Xia; Robert Hancock Cc: mipshop-mih-dt@ietf.org Subject: RE: [MIPSHOP-MIH-DT] this is a test message Guys, I haven't seen any activity yet. Robert, what's the status? We're way behind with the plan we decided at the last meeting. If you cannot lead the team, please let me know NOW. Stefano =20 =09 ________________________________ From: Sam Xia [mailto:xiazhongqi@huawei.com]=20 Sent: Tuesday, January 23, 2007 2:29 AM To: 'Robert Hancock' Cc: mipshop-mih-dt@ietf.org Subject: RE: [MIPSHOP-MIH-DT] this is a test message =20 Hi, Robert, What is your planning of MIH designing? =20 Best Regards, Sam Xia=20 =20 =20 =09 ________________________________ From: Robert Hancock [mailto:robert.hancock@roke.co.uk]=20 Sent: Thursday, January 11, 2007 5:27 AM To: mipshop-mih-dt@ietf.org Subject: [MIPSHOP-MIH-DT] this is a test message please ignore this one. if this works, i'll send a real message!=20 robert h.=20 ------_=_NextPart_001_01C743C1.B90287B6 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable this is a test message

Hi = Robert,

 

I got the email = fine.

 

Cheers,

=

 

Juan = Carlos

 

From: = Robert Hancock [mailto:robert.hancock@roke.co.uk]
Sent: January 24, 2007 = 9:55 AM
To: = mipshop-mih-dt@ietf.org
Subject: [MIPSHOP-MIH-DT] = admin stuff

 

hi = guys,

 

sorry for my silence. i'm not = entirely well at the moment but will see what i can = do.

 

the rest of this mail is about = admin:

 

the current subscriber list = is

  • heejin.jang@samsung.com =
  • john.loughney@nokia.com=
  • JuanCarlos.Zuniga@interdigit= al.com
  • robert.hancock@roke.co.uk
  • Srinivas.Sreemanthula@nokia.= com
  • stefano.m.faccin@marvell.com=
  • subir@research.telcordia.com=
  • telemaco.melia@netlab.nec.de=
  • vijay.devarapalli@azairenet.= com
  • xiazhongqi@huawei.com

it would be helpful if those people = (who haven't already replied to the test message...) can confirm to me that = they can receive this mail so I know I got all the addresses right. =

 

the list is subscriber only post. = if you need to post from multiple addresses, please subscribe using the usual = mailman procedures. subscriptions have to be approved (by = me).

 

please note that the design team = work, and this mailing list, are (so far as I know) IETF activities in the sense = of RFC 3978/4748. In other words, the standard provisions of the 'Note Well' = notice apply.

 

finally, please note that the = mailing list archive is currently public. my preference would be that the archive is = openly available for the long term as a record of the work of the DT, and at = the moment I don't see a reason to close it for the short term. Please bear = that in mind in posting. If people have different preferences, please speak up = and we can all discuss it.

 

cheers,

=

 

robert = h.

 

 

From: Stefano Faccin [mailto:stefano.m.faccin@marvell.com]
Sent: 23 January 2007 = 17:55
To: Sam Xia; Robert = Hancock
Cc: = mipshop-mih-dt@ietf.org
Subject: RE: = [MIPSHOP-MIH-DT] this is a test message

Guys,

I haven’t seen any activity = yet. Robert, what’s the status? We’re way behind with the plan we decided at the last meeting. If you cannot lead the team, please let me = know NOW.

Stefano

=

 

From: Sam = Xia [mailto:xiazhongqi@huawei.com]
Sent: Tuesday, January = 23, 2007 2:29 AM
To: 'Robert Hancock'
Cc: = mipshop-mih-dt@ietf.org
Subject: RE: = [MIPSHOP-MIH-DT] this is a test message

 

Hi, = Robert,

 What is your planning of MIH = designing?

 

 Best Regards, Sam Xia

 

 

From: Robert Hancock [mailto:robert.hancock@roke.co.uk]
Sent: Thursday, January = 11, 2007 5:27 AM
To: = mipshop-mih-dt@ietf.org
Subject: [MIPSHOP-MIH-DT] = this is a test message

please ignore this one. if this works, i'll send a real message! =

robert h.

------_=_NextPart_001_01C743C1.B90287B6-- --===============1596424400== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt --===============1596424400==-- From mipshop-mih-dt-bounces@ietf.org Mon Jan 29 19:10:55 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBgaN-0004pZ-7o; Mon, 29 Jan 2007 19:10:55 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBgaM-0004pU-4Z for mipshop-mih-dt@ietf.org; Mon, 29 Jan 2007 19:10:54 -0500 Received: from smtp0.netlab.nec.de ([195.37.70.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBgaK-0002lD-Kj for mipshop-mih-dt@ietf.org; Mon, 29 Jan 2007 19:10:54 -0500 Received: from localhost (atlas1.office [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 33D5D2000293; Tue, 30 Jan 2007 01:11:30 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office) Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zZ61Uy0N+0oL; Tue, 30 Jan 2007 01:11:30 +0100 (CET) Received: from mx1.office (mx1.office [10.1.1.23]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 1E5AE20001AF; Tue, 30 Jan 2007 01:11:30 +0100 (CET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Date: Tue, 30 Jan 2007 01:10:49 +0100 Message-ID: <113091BD57179D4491C19DA7E10CD696503DAA@mx1.office> In-Reply-To: <04ad01c73fcd$48aef6a0$0100c90a@comm.ad.roke.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Thread-Index: Acc0/g9C7G5rTrWRQf61E6+qhuENtQJ2yVdwAA13hNAALThggAAA92AwAQ66dRA= From: "Telemaco Melia" To: "Robert Hancock" , X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Cc: X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org Hi all, I support Robert's suggestion about splitting the work.=20 What about an AC next week (e.g. Monday, Wednesday)? Comments? Cheers, Telemaco =20 -----Original Message----- From: Robert Hancock [mailto:robert.hancock@roke.co.uk]=20 Sent: Wednesday, January 24, 2007 4:36 PM To: mipshop-mih-dt@ietf.org Subject: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Hi, We now have the question how to begin the work on a solution. One thing i want to avoid is starting off with a 'who likes what = solution' discussion. My perception is that once we all have a common view on the = problem, choosing a solution will actually be the simpler part of the = problem. >From that point of view, I'd rather have a higher level discussion=20 >about the issues which a solution has to take account of. For that, we previously = wrote the design considerations draft (still at = http://tools.ietf.org/wg/mipshop/draft-hepworth-mipshop-mih-design-consid= era tions-01.txt) which I humbly claim at least provides a set of headings = for the things that we have to worry about. Please note: - I'm not claiming that people have to agree that the analysis in that = draft is correct. That is what we are discussing. I am claiming that the = list of issues is pretty good. - I'm not even claiming that we have to construct an update to this = draft or follow its structure; but it would be nice to capture the = conclusions of our discussions in some way. Please can people say what they think about this approach. We can split = up the small problems (1 each or so) and argue out any issues on this = list.=20 I think there are a few bigger issues for which we could form smaller = groups to look at things. They are either harder, or require closer work = with the details of the .21 standard: - one is discovery. here, there just seem to be too many different = options, and we have to think about the tradeoff between = allowing/supporting many and being able to enforce a universal one - another is security. we need to have a view on what security services = the MIH transport actually needs (who authenticates who, what identity = infrastructures that authentication might be based on) - another is the transport/application service interface. .21 is going = through various versions of this, which it would be ideal to align with = what we actually propose. What would be nice now is if people can say what they think about this = as an approach for the work; and, if they approve of the approach, what = parts of the analysis they would feel happy to take the lead on or take = part in. cheers, robert h. _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt From mipshop-mih-dt-bounces@ietf.org Tue Jan 30 00:26:53 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBlW9-0004nE-SI; Tue, 30 Jan 2007 00:26:53 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBlW7-0004n8-VI for mipshop-mih-dt@ietf.org; Tue, 30 Jan 2007 00:26:51 -0500 Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBlW6-0005My-1i for mipshop-mih-dt@ietf.org; Tue, 30 Jan 2007 00:26:51 -0500 Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l0U5Nvvh031073; Tue, 30 Jan 2007 07:23:59 +0200 Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Jan 2007 07:26:30 +0200 Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Jan 2007 23:26:28 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [MIPSHOP-MIH-DT] admin stuff Date: Mon, 29 Jan 2007 23:26:26 -0600 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MIPSHOP-MIH-DT] admin stuff Thread-Index: Acc0/g9C7G5rTrWRQf61E6+qhuENtQJ2yVdwAA13hNAALThggAD/aIqwABtkD+A= References: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> From: To: , X-OriginalArrivalTime: 30 Jan 2007 05:26:28.0083 (UTC) FILETIME=[31130430:01C7442F] X-eXpurgate-Category: 1/0 X-eXpurgate-ID: 149371::070130072401-788A3BB0-5D475BE1/0-0/0-0 X-Nokia-AV: Clean X-Spam-Score: 0.2 (/) X-Scan-Signature: a89bc6ca33b14646e47592488f7eaef6 Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1032212660==" Errors-To: mipshop-mih-dt-bounces@ietf.org This is a multi-part message in MIME format. --===============1032212660== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7442F.308F2BE4" This is a multi-part message in MIME format. ------_=_NextPart_001_01C7442F.308F2BE4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Robert, My email is working too. =20 Regards, Srini ________________________________ From: ext Zuniga, Juan Carlos [mailto:JuanCarlos.Zuniga@InterDigital.com]=20 Sent: Monday, January 29, 2007 10:23 AM To: Robert Hancock Cc: mipshop-mih-dt@ietf.org Subject: RE: [MIPSHOP-MIH-DT] admin stuff Hi Robert, =20 I got the email fine. =20 Cheers, =20 Juan Carlos =20 ________________________________ From: Robert Hancock [mailto:robert.hancock@roke.co.uk]=20 Sent: January 24, 2007 9:55 AM To: mipshop-mih-dt@ietf.org Subject: [MIPSHOP-MIH-DT] admin stuff =20 hi guys, =20 sorry for my silence. i'm not entirely well at the moment but will see what i can do. =20 the rest of this mail is about admin: =20 the current subscriber list is * heejin.jang@samsung.com=20 * john.loughney@nokia.com=20 * JuanCarlos.Zuniga@interdigital.com=20 * robert.hancock@roke.co.uk=20 * Srinivas.Sreemanthula@nokia.com=20 * stefano.m.faccin@marvell.com=20 * subir@research.telcordia.com=20 * telemaco.melia@netlab.nec.de=20 * vijay.devarapalli@azairenet.com=20 * xiazhongqi@huawei.com=20 it would be helpful if those people (who haven't already replied to the test message...) can confirm to me that they can receive this mail so I know I got all the addresses right.=20 =20 the list is subscriber only post. if you need to post from multiple addresses, please subscribe using the usual mailman procedures. subscriptions have to be approved (by me). =20 please note that the design team work, and this mailing list, are (so far as I know) IETF activities in the sense of RFC 3978/4748. In other words, the standard provisions of the 'Note Well' notice apply. =20 finally, please note that the mailing list archive is currently public. my preference would be that the archive is openly available for the long term as a record of the work of the DT, and at the moment I don't see a reason to close it for the short term. Please bear that in mind in posting. If people have different preferences, please speak up and we can all discuss it. =20 cheers, =20 robert h. =20 =20 =09 ________________________________ From: Stefano Faccin [mailto:stefano.m.faccin@marvell.com]=20 Sent: 23 January 2007 17:55 To: Sam Xia; Robert Hancock Cc: mipshop-mih-dt@ietf.org Subject: RE: [MIPSHOP-MIH-DT] this is a test message Guys, I haven't seen any activity yet. Robert, what's the status? We're way behind with the plan we decided at the last meeting. If you cannot lead the team, please let me know NOW. Stefano =20 =09 ________________________________ From: Sam Xia [mailto:xiazhongqi@huawei.com]=20 Sent: Tuesday, January 23, 2007 2:29 AM To: 'Robert Hancock' Cc: mipshop-mih-dt@ietf.org Subject: RE: [MIPSHOP-MIH-DT] this is a test message =20 Hi, Robert, What is your planning of MIH designing? =20 Best Regards, Sam Xia=20 =20 =20 =09 ________________________________ From: Robert Hancock [mailto:robert.hancock@roke.co.uk]=20 Sent: Thursday, January 11, 2007 5:27 AM To: mipshop-mih-dt@ietf.org Subject: [MIPSHOP-MIH-DT] this is a test message please ignore this one. if this works, i'll send a real message!=20 robert h.=20 ------_=_NextPart_001_01C7442F.308F2BE4 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable this is a test = message
Hello Robert,
My email is working too.
 
Regards,
Srini

From: ext Zuniga, Juan Carlos=20 [mailto:JuanCarlos.Zuniga@InterDigital.com]
Sent: Monday, = January 29,=20 2007 10:23 AM
To: Robert Hancock
Cc:=20 mipshop-mih-dt@ietf.org
Subject: RE: [MIPSHOP-MIH-DT] admin=20 stuff

Hi=20 Robert,

 

I got the = email=20 fine.

 

Cheers,

 

Juan=20 Carlos

 

From: Robert=20 Hancock [mailto:robert.hancock@roke.co.uk]
Sent: January 24, 2007 9:55 = AM
To: = mipshop-mih-dt@ietf.org
Subject: [MIPSHOP-MIH-DT] admin=20 stuff

 

hi=20 guys,

 

sorry for my = silence.=20 i'm not entirely well at the moment but will see what i can=20 do.

 

the rest of = this mail=20 is about admin:

 

the current = subscriber=20 list is

  • heejin.jang@samsung.com=20
  • john.loughney@nokia.com=20
  • JuanCarlos.Zuniga@interdigital.com=20
  • robert.hancock@roke.co.uk=20
  • Srinivas.Sreemanthula@nokia.com=20
  • stefano.m.faccin@marvell.com=20
  • subir@research.telcordia.com=20
  • telemaco.melia@netlab.nec.de=20
  • vijay.devarapalli@azairenet.com=20
  • xiazhongqi@huawei.com=20

it would be = helpful if=20 those people (who haven't already replied to the test message...) can = confirm to=20 me that they can receive this mail so I know I got all the addresses = right.=20

 

the list is = subscriber=20 only post. if you need to post from multiple addresses, please subscribe = using=20 the usual mailman procedures. subscriptions have to be approved (by=20 me).

 

please note = that the=20 design team work, and this mailing list, are (so far as I know) IETF = activities=20 in the sense of RFC 3978/4748. In other words, the standard provisions = of the=20 'Note Well' notice apply.

 

finally, = please note=20 that the mailing list archive is currently public. my preference would = be that=20 the archive is openly available for the long term as a record of the = work of the=20 DT, and at the moment I don't see a reason to close it for the short = term.=20 Please bear that in mind in posting. If people have different = preferences,=20 please speak up and we can all discuss it.

 

cheers,

 

robert=20 h.

 

 

From: Stefano=20 Faccin [mailto:stefano.m.faccin@marvell.com]
Sent: 23 January 2007 = 17:55
To: Sam Xia; Robert = Hancock
Cc: = mipshop-mih-dt@ietf.org
Subject: RE: [MIPSHOP-MIH-DT] = this is a=20 test message

Guys,

I = haven’t seen any=20 activity yet. Robert, what’s the status? We’re way behind = with the plan we=20 decided at the last meeting. If you cannot lead the team, please let = me know=20 NOW.

Stefano

 

From: Sam Xia=20 [mailto:xiazhongqi@huawei.com]
Sent: Tuesday, January 23, 2007 = 2:29=20 AM
To: 'Robert=20 Hancock'
Cc:=20 mipshop-mih-dt@ietf.org
Subject: RE: [MIPSHOP-MIH-DT] = this is a=20 test message

 

Hi,=20 Robert,

 What is = your=20 planning of MIH designing?

 

 Best=20 Regards, Sam Xia

 

 

From:=20 Robert Hancock [mailto:robert.hancock@roke.co.uk]
Sent: Thursday, January 11, = 2007 5:27=20 AM
To:=20 mipshop-mih-dt@ietf.org
Subject: [MIPSHOP-MIH-DT] = this is a=20 test message

please=20 ignore this one. if this works, i'll send a real = message!=20

robert = h.=20

------_=_NextPart_001_01C7442F.308F2BE4-- --===============1032212660== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt --===============1032212660==-- From mipshop-mih-dt-bounces@ietf.org Tue Jan 30 00:34:21 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBldN-0000SQ-S2; Tue, 30 Jan 2007 00:34:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBldM-0000SK-IY for mipshop-mih-dt@ietf.org; Tue, 30 Jan 2007 00:34:20 -0500 Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBldL-00076g-2d for mipshop-mih-dt@ietf.org; Tue, 30 Jan 2007 00:34:20 -0500 Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l0U5VGlL024200; Tue, 30 Jan 2007 07:31:29 +0200 Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Jan 2007 07:33:38 +0200 Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Jan 2007 23:33:22 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Date: Mon, 29 Jan 2007 23:33:22 -0600 Message-ID: In-Reply-To: <04ad01c73fcd$48aef6a0$0100c90a@comm.ad.roke.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Thread-Index: Acc0/g9C7G5rTrWRQf61E6+qhuENtQJ2yVdwAA13hNAALThggAAA92AwARnsa1A= References: <047f01c73fc7$9ee75130$0100c90a@comm.ad.roke.co.uk> <04ad01c73fcd$48aef6a0$0100c90a@comm.ad.roke.co.uk> From: To: , X-OriginalArrivalTime: 30 Jan 2007 05:33:22.0768 (UTC) FILETIME=[283EED00:01C74430] X-Nokia-AV: Clean X-Spam-Score: 0.2 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Cc: X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org Hello all, I don't really have strong opinions on whether we split up or not. Eventually, there is only one solution with all features. While smaller groups can look more carefully on details and provide feedback on the design choices to the main group for the overall solution. The first step is to identify the areas. The design considerations, I agree is a good starting point. Regards, Srini -----Original Message----- From: ext Robert Hancock [mailto:robert.hancock@roke.co.uk]=20 Sent: Wednesday, January 24, 2007 9:36 AM To: mipshop-mih-dt@ietf.org Subject: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Hi, We now have the question how to begin the work on a solution. One thing i want to avoid is starting off with a 'who likes what solution' discussion. My perception is that once we all have a common view on the problem, choosing a solution will actually be the simpler part of the problem. >From that point of view, I'd rather have a higher level discussion=20 >about the issues which a solution has to take account of. For that, we previously wrote the design considerations draft (still at http://tools.ietf.org/wg/mipshop/draft-hepworth-mipshop-mih-design-consi dera tions-01.txt) which I humbly claim at least provides a set of headings for the things that we have to worry about. Please note: - I'm not claiming that people have to agree that the analysis in that draft is correct. That is what we are discussing. I am claiming that the list of issues is pretty good. - I'm not even claiming that we have to construct an update to this draft or follow its structure; but it would be nice to capture the conclusions of our discussions in some way. Please can people say what they think about this approach. We can split up the small problems (1 each or so) and argue out any issues on this list.=20 I think there are a few bigger issues for which we could form smaller groups to look at things. They are either harder, or require closer work with the details of the .21 standard: - one is discovery. here, there just seem to be too many different options, and we have to think about the tradeoff between allowing/supporting many and being able to enforce a universal one - another is security. we need to have a view on what security services the MIH transport actually needs (who authenticates who, what identity infrastructures that authentication might be based on) - another is the transport/application service interface. .21 is going through various versions of this, which it would be ideal to align with what we actually propose. What would be nice now is if people can say what they think about this as an approach for the work; and, if they approve of the approach, what parts of the analysis they would feel happy to take the lead on or take part in. cheers, robert h. _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt From mipshop-mih-dt-bounces@ietf.org Tue Jan 30 17:12:53 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC1Dh-0003AT-4V; Tue, 30 Jan 2007 17:12:53 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HC1De-00039s-JU for mipshop-mih-dt@ietf.org; Tue, 30 Jan 2007 17:12:50 -0500 Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HC1CR-00047K-4L for mipshop-mih-dt@ietf.org; Tue, 30 Jan 2007 17:11:37 -0500 Received: from mailee.research.telcordia.com (mailee [192.4.16.29]) by thumper.research.telcordia.com (8.13.6/8.13.5) with ESMTP id l0UMBY6f022658; Tue, 30 Jan 2007 17:11:34 -0500 (EST) Received: from [128.96.59.126] (vpntnlB126 [128.96.59.126]) by mailee.research.telcordia.com (8.9.3/8.9.3) with ESMTP id RAA03309; Tue, 30 Jan 2007 17:11:33 -0500 (EST) Message-ID: <45BFC292.3090300@research.telcordia.com> Date: Tue, 30 Jan 2007 17:11:30 -0500 From: Subir Das User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Telemaco Melia Subject: Re: [MIPSHOP-MIH-DT] technical stuff - how to begin the work References: <113091BD57179D4491C19DA7E10CD696503DAA@mx1.office> In-Reply-To: <113091BD57179D4491C19DA7E10CD696503DAA@mx1.office> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org I am fine with any time in the morning, EST (US) rest of this week. Thanks, -Subir Telemaco Melia wrote: > Hi all, > > I support Robert's suggestion about splitting the work. > What about an AC next week (e.g. Monday, Wednesday)? > Comments? > > Cheers, > Telemaco > > > -----Original Message----- > From: Robert Hancock [mailto:robert.hancock@roke.co.uk] > Sent: Wednesday, January 24, 2007 4:36 PM > To: mipshop-mih-dt@ietf.org > Subject: [MIPSHOP-MIH-DT] technical stuff - how to begin the work > > Hi, > > We now have the question how to begin the work on a solution. > > One thing i want to avoid is starting off with a 'who likes what solution' > discussion. My perception is that once we all have a common view on the problem, choosing a solution will actually be the simpler part of the problem. > > >From that point of view, I'd rather have a higher level discussion > >> about the >> > issues which a solution has to take account of. For that, we previously wrote the design considerations draft (still at http://tools.ietf.org/wg/mipshop/draft-hepworth-mipshop-mih-design-considera > tions-01.txt) which I humbly claim at least provides a set of headings for the things that we have to worry about. Please note: > - I'm not claiming that people have to agree that the analysis in that draft is correct. That is what we are discussing. I am claiming that the list of issues is pretty good. > - I'm not even claiming that we have to construct an update to this draft or follow its structure; but it would be nice to capture the conclusions of our discussions in some way. > > Please can people say what they think about this approach. We can split up the small problems (1 each or so) and argue out any issues on this list. > > I think there are a few bigger issues for which we could form smaller groups to look at things. They are either harder, or require closer work with the details of the .21 standard: > - one is discovery. here, there just seem to be too many different options, and we have to think about the tradeoff between allowing/supporting many and being able to enforce a universal one > - another is security. we need to have a view on what security services the MIH transport actually needs (who authenticates who, what identity infrastructures that authentication might be based on) > - another is the transport/application service interface. .21 is going through various versions of this, which it would be ideal to align with what we actually propose. > > What would be nice now is if people can say what they think about this as an approach for the work; and, if they approve of the approach, what parts of the analysis they would feel happy to take the lead on or take part in. > > cheers, > > robert h. > > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt From mipshop-mih-dt-bounces@ietf.org Wed Jan 31 10:18:06 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCHDq-0005q3-90; Wed, 31 Jan 2007 10:18:06 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCHDo-0005kZ-Hd for mipshop-mih-dt@ietf.org; Wed, 31 Jan 2007 10:18:04 -0500 Received: from idcexmail.interdigital.com ([12.32.197.135] helo=sahara.InterDigital.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCHDl-0006UF-Tu for mipshop-mih-dt@ietf.org; Wed, 31 Jan 2007 10:18:04 -0500 Received: from interdigital.com ([10.0.128.11]) by sahara.InterDigital.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Jan 2007 10:18:01 -0500 Received: from SAM.InterDigital.com ([10.30.2.12]) by interdigital.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Jan 2007 10:14:53 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Date: Wed, 31 Jan 2007 10:14:51 -0500 Message-ID: In-Reply-To: <45BFC292.3090300@research.telcordia.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Thread-Index: AcdEu88ggjV9qAEMQA6yoHMnrZCJJQAAEIlA From: "Zuniga, Juan Carlos" To: "Subir Das" , "Telemaco Melia" X-OriginalArrivalTime: 31 Jan 2007 15:14:53.0133 (UTC) FILETIME=[8EEFDFD0:01C7454A] X-Spam-Score: 0.0 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org I'm also fine with the rest of this week, or Monday next week. Regards, Juan Carlos -----Original Message----- From: Subir Das [mailto:subir@research.telcordia.com]=20 Sent: January 30, 2007 5:12 PM To: Telemaco Melia Cc: mipshop-mih-dt@ietf.org Subject: Re: [MIPSHOP-MIH-DT] technical stuff - how to begin the work I am fine with any time in the morning, EST (US) rest of this week. Thanks, -Subir Telemaco Melia wrote: > Hi all, > > I support Robert's suggestion about splitting the work.=20 > What about an AC next week (e.g. Monday, Wednesday)? > Comments? > > Cheers, > Telemaco > =20 > > -----Original Message----- > From: Robert Hancock [mailto:robert.hancock@roke.co.uk]=20 > Sent: Wednesday, January 24, 2007 4:36 PM > To: mipshop-mih-dt@ietf.org > Subject: [MIPSHOP-MIH-DT] technical stuff - how to begin the work > > Hi, > > We now have the question how to begin the work on a solution. > > One thing i want to avoid is starting off with a 'who likes what solution' > discussion. My perception is that once we all have a common view on the problem, choosing a solution will actually be the simpler part of the problem. > > >From that point of view, I'd rather have a higher level discussion=20 > =20 >> about the >> =20 > issues which a solution has to take account of. For that, we previously wrote the design considerations draft (still at http://tools.ietf.org/wg/mipshop/draft-hepworth-mipshop-mih-design-consi dera > tions-01.txt) which I humbly claim at least provides a set of headings for the things that we have to worry about. Please note: > - I'm not claiming that people have to agree that the analysis in that draft is correct. That is what we are discussing. I am claiming that the list of issues is pretty good. > - I'm not even claiming that we have to construct an update to this draft or follow its structure; but it would be nice to capture the conclusions of our discussions in some way. > > Please can people say what they think about this approach. We can split up the small problems (1 each or so) and argue out any issues on this list.=20 > > I think there are a few bigger issues for which we could form smaller groups to look at things. They are either harder, or require closer work with the details of the .21 standard: > - one is discovery. here, there just seem to be too many different options, and we have to think about the tradeoff between allowing/supporting many and being able to enforce a universal one > - another is security. we need to have a view on what security services the MIH transport actually needs (who authenticates who, what identity infrastructures that authentication might be based on) > - another is the transport/application service interface. .21 is going through various versions of this, which it would be ideal to align with what we actually propose. > > What would be nice now is if people can say what they think about this as an approach for the work; and, if they approve of the approach, what parts of the analysis they would feel happy to take the lead on or take part in. > > cheers, > > robert h. > > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > =20 _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt From mipshop-mih-dt-bounces@ietf.org Wed Jan 31 12:25:02 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCJCg-0006Rp-86; Wed, 31 Jan 2007 12:25:02 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCJCe-0006KZ-TD for mipshop-mih-dt@ietf.org; Wed, 31 Jan 2007 12:25:00 -0500 Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCJCN-0005TI-SB for mipshop-mih-dt@ietf.org; Wed, 31 Jan 2007 12:24:45 -0500 Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l0VHMcQB005933; Wed, 31 Jan 2007 19:22:42 +0200 Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Jan 2007 19:24:24 +0200 Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Jan 2007 11:24:18 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Date: Wed, 31 Jan 2007 11:24:17 -0600 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Thread-Index: AcdEu88ggjV9qAEMQA6yoHMnrZCJJQAAEIlAACgi3hA= References: <45BFC292.3090300@research.telcordia.com> From: To: , , X-OriginalArrivalTime: 31 Jan 2007 17:24:18.0469 (UTC) FILETIME=[A3701D50:01C7455C] X-eXpurgate-Category: 1/0 X-eXpurgate-ID: 149371::070131192243-171CBBB0-75798FCF/0-0/0-1 X-Nokia-AV: Clean X-Spam-Score: 0.2 (/) X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org Me too. Regards, Srini=20 -----Original Message----- From: ext Zuniga, Juan Carlos [mailto:JuanCarlos.Zuniga@InterDigital.com]=20 Sent: Wednesday, January 31, 2007 9:15 AM To: Subir Das; Telemaco Melia Cc: mipshop-mih-dt@ietf.org Subject: RE: [MIPSHOP-MIH-DT] technical stuff - how to begin the work I'm also fine with the rest of this week, or Monday next week. Regards, Juan Carlos -----Original Message----- From: Subir Das [mailto:subir@research.telcordia.com] Sent: January 30, 2007 5:12 PM To: Telemaco Melia Cc: mipshop-mih-dt@ietf.org Subject: Re: [MIPSHOP-MIH-DT] technical stuff - how to begin the work I am fine with any time in the morning, EST (US) rest of this week. Thanks, -Subir Telemaco Melia wrote: > Hi all, > > I support Robert's suggestion about splitting the work.=20 > What about an AC next week (e.g. Monday, Wednesday)? > Comments? > > Cheers, > Telemaco > =20 > > -----Original Message----- > From: Robert Hancock [mailto:robert.hancock@roke.co.uk] > Sent: Wednesday, January 24, 2007 4:36 PM > To: mipshop-mih-dt@ietf.org > Subject: [MIPSHOP-MIH-DT] technical stuff - how to begin the work > > Hi, > > We now have the question how to begin the work on a solution. > > One thing i want to avoid is starting off with a 'who likes what solution' > discussion. My perception is that once we all have a common view on the problem, choosing a solution will actually be the simpler part of the problem. > > >From that point of view, I'd rather have a higher level discussion > =20 >> about the >> =20 > issues which a solution has to take account of. For that, we previously wrote the design considerations draft (still at http://tools.ietf.org/wg/mipshop/draft-hepworth-mipshop-mih-design-consi dera > tions-01.txt) which I humbly claim at least provides a set of headings for the things that we have to worry about. Please note: > - I'm not claiming that people have to agree that the analysis in that draft is correct. That is what we are discussing. I am claiming that the list of issues is pretty good. > - I'm not even claiming that we have to construct an update to this draft or follow its structure; but it would be nice to capture the conclusions of our discussions in some way. > > Please can people say what they think about this approach. We can split up the small problems (1 each or so) and argue out any issues on this list.=20 > > I think there are a few bigger issues for which we could form smaller groups to look at things. They are either harder, or require closer work with the details of the .21 standard: > - one is discovery. here, there just seem to be too many different options, and we have to think about the tradeoff between allowing/supporting many and being able to enforce a universal one > - another is security. we need to have a view on what security services the MIH transport actually needs (who authenticates who, what identity infrastructures that authentication might be based on) > - another is the transport/application service interface. .21 is going through various versions of this, which it would be ideal to align with what we actually propose. > > What would be nice now is if people can say what they think about this as an approach for the work; and, if they approve of the approach, what parts of the analysis they would feel happy to take the lead on or take part in. > > cheers, > > robert h. > > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > =20 _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt From mipshop-mih-dt-bounces@ietf.org Wed Jan 31 13:17:45 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCK1h-0003yt-3I; Wed, 31 Jan 2007 13:17:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCK1f-0003yR-SF for mipshop-mih-dt@ietf.org; Wed, 31 Jan 2007 13:17:43 -0500 Received: from rsys002x.roke.co.uk ([193.118.201.109]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCK1Z-0005jj-Ep for mipshop-mih-dt@ietf.org; Wed, 31 Jan 2007 13:17:43 -0500 Received: from rsys005a.comm.ad.roke.co.uk (rsys005a [193.118.193.85]) by rsys002x.roke.co.uk (8.13.1/8.13.1) with ESMTP id l0VIFIxd004862; Wed, 31 Jan 2007 18:15:59 GMT Received: from ehlaptop ([193.118.192.66]) by rsys005a.comm.ad.roke.co.uk with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Jan 2007 18:15:58 +0000 From: "Robert Hancock" To: , , , Subject: RE: [MIPSHOP-MIH-DT] technical stuff - how to begin the work Date: Wed, 31 Jan 2007 18:16:00 -0000 Message-ID: <011f01c74563$dd464fc0$0100c90a@comm.ad.roke.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Thread-Index: AcdEu88ggjV9qAEMQA6yoHMnrZCJJQAAEIlAACgi3hAAAFhVEA== X-OriginalArrivalTime: 31 Jan 2007 18:15:58.0302 (UTC) FILETIME=[DB1517E0:01C74563] X-MailScanner-roke-co-uk: Found to be clean X-MailScanner-roke-co-uk-SpamCheck: X-MailScanner-From: robert.hancock@roke.co.uk X-Spam-Score: 0.0 (/) X-Scan-Signature: 0770535483960d190d4a0d020e7060bd Cc: mipshop-mih-dt@ietf.org X-BeenThere: mipshop-mih-dt@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: MIPSHOP Media Independent Handover Design Team List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mipshop-mih-dt-bounces@ietf.org hi all, while i appreciate the attraction of a phone conference (at least for some), please bear in mind that AFAIK we have people in the DT from US, Europe and Far East. So fair scheduling is pretty tricky. For that reason, I would really like people to comment on the technical aspects of the original email (as well as the organisation of how to discuss them). r. > -----Original Message----- > From: Srinivas.Sreemanthula@nokia.com > [mailto:Srinivas.Sreemanthula@nokia.com] > Sent: 31 January 2007 17:24 > To: JuanCarlos.Zuniga@InterDigital.com; > subir@research.telcordia.com; Telemaco.Melia@netlab.nec.de > Cc: mipshop-mih-dt@ietf.org > Subject: RE: [MIPSHOP-MIH-DT] technical stuff - how to begin the work > > Me too. > > Regards, > Srini > > -----Original Message----- > From: ext Zuniga, Juan Carlos > [mailto:JuanCarlos.Zuniga@InterDigital.com] > Sent: Wednesday, January 31, 2007 9:15 AM > To: Subir Das; Telemaco Melia > Cc: mipshop-mih-dt@ietf.org > Subject: RE: [MIPSHOP-MIH-DT] technical stuff - how to begin the work > > I'm also fine with the rest of this week, or Monday next week. > > Regards, > > Juan Carlos > > > -----Original Message----- > From: Subir Das [mailto:subir@research.telcordia.com] > Sent: January 30, 2007 5:12 PM > To: Telemaco Melia > Cc: mipshop-mih-dt@ietf.org > Subject: Re: [MIPSHOP-MIH-DT] technical stuff - how to begin the work > > I am fine with any time in the morning, EST (US) rest of this week. > > Thanks, > -Subir > > Telemaco Melia wrote: > > Hi all, > > > > I support Robert's suggestion about splitting the work. > > What about an AC next week (e.g. Monday, Wednesday)? > > Comments? > > > > Cheers, > > Telemaco > > > > > > -----Original Message----- > > From: Robert Hancock [mailto:robert.hancock@roke.co.uk] > > Sent: Wednesday, January 24, 2007 4:36 PM > > To: mipshop-mih-dt@ietf.org > > Subject: [MIPSHOP-MIH-DT] technical stuff - how to begin the work > > > > Hi, > > > > We now have the question how to begin the work on a solution. > > > > One thing i want to avoid is starting off with a 'who likes what > solution' > > discussion. My perception is that once we all have a common view on > the problem, choosing a solution will actually be the simpler > part of the problem. > > > > >From that point of view, I'd rather have a higher level discussion > > > >> about the > >> > > issues which a solution has to take account of. For that, we > previously wrote the design considerations draft (still at > http://tools.ietf.org/wg/mipshop/draft-hepworth-mipshop-mih-de > sign-consi > dera > > tions-01.txt) which I humbly claim at least provides a set > of headings > for the things that we have to worry about. Please note: > > - I'm not claiming that people have to agree that the > analysis in that > draft is correct. That is what we are discussing. I am > claiming that the list of issues is pretty good. > > - I'm not even claiming that we have to construct an update to this > draft or follow its structure; but it would be nice to > capture the conclusions of our discussions in some way. > > > > Please can people say what they think about this approach. We can > split up the small problems (1 each or so) and argue out any > issues on this list. > > > > I think there are a few bigger issues for which we could > form smaller > groups to look at things. They are either harder, or require > closer work with the details of the .21 standard: > > - one is discovery. here, there just seem to be too many different > options, and we have to think about the tradeoff between > allowing/supporting many and being able to enforce a universal one > > - another is security. we need to have a view on what security > services the MIH transport actually needs (who authenticates > who, what identity infrastructures that authentication might > be based on) > > - another is the transport/application service interface. > .21 is going > through various versions of this, which it would be ideal to > align with what we actually propose. > > > > What would be nice now is if people can say what they think > about this > as an approach for the work; and, if they approve of the > approach, what parts of the analysis they would feel happy to > take the lead on or take part in. > > > > cheers, > > > > robert h. > > > > > > _______________________________________________ > > MIPSHOP-MIH-DT mailing list > > MIPSHOP-MIH-DT@ietf.org > > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > > > > _______________________________________________ > > MIPSHOP-MIH-DT mailing list > > MIPSHOP-MIH-DT@ietf.org > > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > > > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > > _______________________________________________ > MIPSHOP-MIH-DT mailing list > MIPSHOP-MIH-DT@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt > _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt