From exim@www1.ietf.org Tue Dec 2 01:38:58 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22309 for ; Tue, 2 Dec 2003 01:38:58 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AR4BF-0004Gj-70 for seamoby-archive@odin.ietf.org; Tue, 02 Dec 2003 01:38:41 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB26cfSF016403 for seamoby-archive@odin.ietf.org; Tue, 2 Dec 2003 01:38:41 -0500 Received: from [218.5.192.219] (helo=vip.163.net) by optimus.ietf.org with esmtp (Exim 4.20) id 1AR4BD-0004GO-4g for seamoby-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 01:38:41 -0500 From: =?GB2312?B?0MLKvc2o0bY=?= Subject: =?GB2312?B?w+K30beit8WjrcrTxrW157uwv6rNqKOh?= To: seamoby-web-archive@optimus.ietf.org Content-Type: text/plain;charset="GB2312" Reply-To: xingshi_tx@vip.163.net Date: Tue, 2 Dec 2003 14:39:48 +0800 X-Priority: 3 X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Message-Id: 尊敬的seamoby-web-archive： 这是一封视频电话启用通知，如果对您没有用，请删掉本邮件，并对您说声对不起！祝您工作顺利。 您是否还在为您的高额的业务电话及各项通讯的费用增加而苦恼呢？您是否为了节约各项费用而绞尽脑汁呢？请您关注我们的产品，兴许，这对您及您的单位有很大益处。 国家科研机构，免费发放网络视频电话，欢迎您的使用！ 产品特点： 一人与多人同时视频讯的视频电话，没有摄像头可当语音电话使用，具有电子白板互相写、画贴图；IE协同浏览：同步浏览网页、同步点歌、点播电影、同步欣尝FLSAH； 文字对聊、发EMAIL、多个文件同时传输。 一切通讯没有防火墙问题。 集团单位申请，可轻松组建独立视频通讯网。 现在正式向： 集团单位用户开放申请； 向网络运营商提供服务器端并发放号群，供网络运营商向用户促销网络产品； 向摄像头厂商提供靓号，供厂商做产品促销。 向个人用户开放申请。 号码申请：http://www.qmeeting.org.cn/register.htm 软件下载：http://www.qmeeting.org.cn/qm.htm From exim@www1.ietf.org Tue Dec 2 16:21:00 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11774 for ; Tue, 2 Dec 2003 16:21:00 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARHwp-00019t-2w for seamoby-archive@odin.ietf.org; Tue, 02 Dec 2003 16:20:43 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2LKglk004443 for seamoby-archive@odin.ietf.org; Tue, 2 Dec 2003 16:20:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARHwk-00019a-0r for seamoby-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 16:20:38 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11736 for ; Tue, 2 Dec 2003 16:20:24 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARHwi-0001Cy-00 for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 16:20:36 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ARHwg-0001Ch-00 for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 16:20:34 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARHwA-000152-5u; Tue, 02 Dec 2003 16:20:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARHDf-0006VM-UY for seamoby@optimus.ietf.org; Tue, 02 Dec 2003 15:34:03 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08243; Tue, 2 Dec 2003 15:33:49 -0500 (EST) Message-Id: <200312022033.PAA08243@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: seamoby@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 02 Dec 2003 15:33:49 -0500 Subject: [Seamoby] I-D ACTION:draft-ietf-seamoby-mobility-terminology-05.txt Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting Working Group of the IETF. Title : Mobility Related Terminology Author(s) : J. Manner, M. Kojo Filename : draft-ietf-seamoby-mobility-terminology-05.txt Pages : 36 Date : 2003-12-2 There is a need for common definitions of terminology in the work to be done around IP mobility. This memo defines terms for mobility related terminology. It is intended as a living document for use by the Seamoby Working Group in Seamoby drafts and in WG discussions, but not limited in scope to the terms needed by the Seamoby Working Group. Other working groups dealing with mobility may take advantage of this terminology. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-seamoby-mobility-terminology-05.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-seamoby-mobility-terminology-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-seamoby-mobility-terminology-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-12-2153933.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-seamoby-mobility-terminology-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-seamoby-mobility-terminology-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-12-2153933.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Tue Dec 2 18:09:46 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21188 for ; Tue, 2 Dec 2003 18:09:44 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJe4-0007vu-NV for seamoby-archive@odin.ietf.org; Tue, 02 Dec 2003 18:09:29 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2N9S9p030488 for seamoby-archive@odin.ietf.org; Tue, 2 Dec 2003 18:09:28 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJe4-0007ve-HD for seamoby-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 18:09:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21097 for ; Tue, 2 Dec 2003 18:09:12 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARJe1-0004qZ-00 for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 18:09:25 -0500 Received: from manatick.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1ARJe0-0004pj-00 for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 18:09:24 -0500 Received: from [132.151.6.22] (helo=optimus.ietf.org) by manatick with esmtp (Exim 4.24) id 1ARJTz-00005p-HY for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 17:59:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJTx-00070i-3k; Tue, 02 Dec 2003 17:59:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJT0-000703-BJ for seamoby@optimus.ietf.org; Tue, 02 Dec 2003 17:58:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20254 for ; Tue, 2 Dec 2003 17:57:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARJSx-0004hX-00 for seamoby@ietf.org; Tue, 02 Dec 2003 17:57:59 -0500 Received: from motgate.mot.com ([129.188.136.100]) by ietf-mx with esmtp (Exim 4.12) id 1ARJSw-0004hU-00 for seamoby@ietf.org; Tue, 02 Dec 2003 17:57:58 -0500 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate.mot.com (Motorola/Motgate) with ESMTP id hB2Mvugd012453 for ; Tue, 2 Dec 2003 15:57:56 -0700 (MST) Received: from il27exm02.cig.mot.com (il27exm02.cig.mot.com [10.17.193.3]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id hB2MtnGS017780 for ; Tue, 2 Dec 2003 16:55:50 -0600 Received: by il27exm02.cig.mot.com with Internet Mail Service (5.5.2657.2) id ; Tue, 2 Dec 2003 16:57:05 -0600 Message-ID: From: Nakhjiri Madjid-MNAKHJI1 To: "'john.loughney@nokia.com'" , Lucian.Suciu@enst-bretagne.fr, seamoby@ietf.org Subject: RE: [Seamoby] CTP - a few comments on draft-ietf-seamoby-ctp-05.. . Date: Tue, 2 Dec 2003 16:57:04 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain; charset="iso-8859-1" Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , Hi John, I guess I haven't followed the discussion very closely, Is the replacement of R flag with A flag an open issue yet? How can the R flags for reliability be replaced with an acknowledge flag and expect that they do the same thing. Madjid -----Original Message----- From: seamoby-admin@ietf.org [mailto:seamoby-admin@ietf.org]On Behalf Of john.loughney@nokia.com Sent: Friday, November 21, 2003 2:57 AM To: Lucian.Suciu@enst-bretagne.fr; seamoby@ietf.org Subject: RE: [Seamoby] CTP - a few comments on draft-ietf-seamoby-ctp-05... Hi, Assigned issue 31: > Editorial: > > In section 2.5.2 Context Transfer Activate Acknowledge > (CTAA) Message: > > Reserved Reserved for future use. Must be set to > zero by the MN. > >>could be changed with>> > Must be set to zero by the sender of CTAA Message, > i.e. pAR or nAR. > > In 2.5.3 Context Transfer Data (CTD) Message: > > A reliability flag, 'R' > >>could be changed with>> > An acknowlwdgement flag 'A' > > ...indicates whether a reply is required by nAR. > >>could be changed with>> > ...indicates whether a reply is required by pAR. > > Reserved Reserved for future use. Must be set to > zero by the MN. > >>could be changed with>> > Must be set to zero by the pAR. > > Perhaps move here the description of 'Elapsed Time' > which exists > in section 3... > > In section 2.5.4 Context Transfer Data Reply (CTDR) Message > > Reserved Reserved for future use. Must be set to > zero by the MN. > >>could be changed with>> > Must be set to zero by the nAR. > > In 2.5.5 Context Transfer Cancel (CTC) Message > > Reserved Reserved for future use. Must be set to > zero by the MN. > >>could be changed with>> > Must be set to zero by the nAR. > > In 2.5.6 Context Transfer Request (CT Request) Message > > Reserved Reserved for future use. Must be set to > zero by the MN. > >>could be changed with>> > Must be set to zero by the nAR. _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Tue Dec 2 18:16:53 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22008 for ; Tue, 2 Dec 2003 18:16:53 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJkz-00087K-6D for seamoby-archive@odin.ietf.org; Tue, 02 Dec 2003 18:16:38 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2NGbAu031196 for seamoby-archive@odin.ietf.org; Tue, 2 Dec 2003 18:16:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJkz-000875-2a for seamoby-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 18:16:37 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21949 for ; Tue, 2 Dec 2003 18:16:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARJkw-0004xL-00 for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 18:16:34 -0500 Received: from manatick.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1ARJe3-0004pj-00 for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 18:09:27 -0500 Received: from [132.151.6.22] (helo=optimus.ietf.org) by manatick with esmtp (Exim 4.24) id 1ARJRA-0008Ra-TO for seamoby-web-archive@ietf.org; Tue, 02 Dec 2003 17:56:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJR3-0006lL-US; Tue, 02 Dec 2003 17:56:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARJQx-0006km-2V for seamoby@optimus.ietf.org; Tue, 02 Dec 2003 17:55:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20199 for ; Tue, 2 Dec 2003 17:55:39 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARJQt-0004gh-00 for seamoby@ietf.org; Tue, 02 Dec 2003 17:55:51 -0500 Received: from motgate.mot.com ([129.188.136.100]) by ietf-mx with esmtp (Exim 4.12) id 1ARJQi-0004ga-00 for seamoby@ietf.org; Tue, 02 Dec 2003 17:55:50 -0500 Received: from az33exr03.mot.com (pobox3.mot.com [10.64.251.242]) by motgate.mot.com (Motorola/Motgate) with ESMTP id hB2MtUgd010004 for ; Tue, 2 Dec 2003 15:55:33 -0700 (MST) Received: from il27exm02.cig.mot.com (il27exm02.cig.mot.com [10.17.193.3]) by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id hB2MqA58006953 for ; Tue, 2 Dec 2003 16:52:11 -0600 Received: by il27exm02.cig.mot.com with Internet Mail Service (5.5.2657.2) id ; Tue, 2 Dec 2003 16:52:11 -0600 Message-ID: From: Nakhjiri Madjid-MNAKHJI1 To: "'Seamoby CTP Issues'" , seamoby@ietf.org Subject: RE: [Seamoby] [issue30] How to handle bad MN's authorization Toke n? Date: Tue, 2 Dec 2003 16:52:10 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain; charset="UTF-8" Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , John, Are you soliciting opinions on these alternatives as well? Madjid -----Original Message----- From: seamoby-admin@ietf.org [mailto:seamoby-admin@ietf.org]On Behalf Of John Loughney SEAMOBY-Issues Sent: Friday, November 21, 2003 2:55 AM To: seamoby@ietf.org Subject: [Seamoby] [issue30] How to handle bad MN's authorization Token? New submission from John Loughney : In case nAR requests the transfer by a CTR message, the pAR must verify the MN's authorization token. If this token is unvalid, what do we do ? Possible solutions: - nothing ? the pAR does not answer to nAR. - pAR indicates the error to nAR: * In the CTD message. * In a error message which could carry error information. others ? ---------- category: Editorial document: draft-ietf-seamoby-ctp-05.txt messages: 39 nosy: jloughney priority: Should Fix status: No Discussion title: How to handle bad MN's authorization Token? _____________________________________________________________ Seamoby CTP Issues _____________________________________________________________ _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Wed Dec 3 16:38:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09258 for ; Wed, 3 Dec 2003 16:38:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARehC-0005hS-A9 for seamoby-archive@odin.ietf.org; Wed, 03 Dec 2003 16:38:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3Lc6Ic021906 for seamoby-archive@odin.ietf.org; Wed, 3 Dec 2003 16:38:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARehC-0005hF-3u for seamoby-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 16:38:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09206 for ; Wed, 3 Dec 2003 16:37:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AReh9-0001pa-00 for seamoby-web-archive@ietf.org; Wed, 03 Dec 2003 16:38:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AReh9-0001pX-00 for seamoby-web-archive@ietf.org; Wed, 03 Dec 2003 16:38:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AReh7-0005gW-9B; Wed, 03 Dec 2003 16:38:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARegf-0005aM-DU for seamoby@optimus.ietf.org; Wed, 03 Dec 2003 16:37:33 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09193 for ; Wed, 3 Dec 2003 16:37:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARegd-0001p4-00 for seamoby@ietf.org; Wed, 03 Dec 2003 16:37:31 -0500 Received: from motgate.mot.com ([129.188.136.100]) by ietf-mx with esmtp (Exim 4.12) id 1ARegc-0001p1-00 for seamoby@ietf.org; Wed, 03 Dec 2003 16:37:30 -0500 Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by motgate.mot.com (Motorola/Motgate) with ESMTP id hB3LbTgd000349 for ; Wed, 3 Dec 2003 14:37:29 -0700 (MST) Received: from il27exm02.cig.mot.com (il27exm02.cig.mot.com [10.17.193.3]) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id hB3LanYx017079 for ; Wed, 3 Dec 2003 15:36:55 -0600 Received: by il27exm02.cig.mot.com with Internet Mail Service (5.5.2657.2) id ; Wed, 3 Dec 2003 15:36:49 -0600 Message-ID: From: Singh Ajoy-ASINGH1 To: "'seamoby@ietf.org'" Subject: RE: [Seamoby] CARD and multiple ARs per AP? Date: Wed, 3 Dec 2003 15:36:49 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , Hello Jon, Sorry for late reply. Please see my inline reply. Regards, Ajoy -----Original Message----- From: Jon-Olov Vatn [mailto:vatn@it.kth.se] Sent: Tuesday, November 18, 2003 4:42 PM To: seamoby@ietf.org Subject: [Seamoby] CARD and multiple ARs per AP? Hi! I have a question regarding the CAR discovery protocol (CARD). When I read the draft (draft-ietf-seamoby-card-protocol-04.txt) my understanding was that it allows an AR to have multiple APs attached, but not an AP to be attached to multiple ARs. I this the case? (Or did I just not read it carefully enough?) AJOY-> This was not the intent. If this is the case, is this imposed structural limitation made of some specific reason, e.g., for simplicity, or was it just unintentional? (I hope you forgive me for having missed any prior discussion on this matter.) Background: ----------- I could think of two situations where one would like to have multiple ARs per AP: if a WISP has two ARs for redundancy, or if several WISPs are sharing an access infrastructure (my own interest concerns the latter. This would lead to a many-to-many relationship between APs and ARs and a L2 ID would no longer uniquely point to an AR. Perhaps I should explain what I mean with shared access infrastructures, since there are many ways to do it. If we consider 802.11 WLANs with 802.1X support, and a set of WISPs sharing an access infrastructure with briding APs (see the figure below) it is possible to use VLAN (or other tunneling techniques) between the APs and ARs to isolate the traffic for the different WISPs. The APs can map the traffic to/from the USER hosts to the WISP by adding/removing the appropriate VLAN tag. (For those interested I have written a paper which gives some more information about the architecture I anticipate): "A roaming architecture for IP based mobile telephony in WLAN environments", Stockholm Mobility Roundtable, 22-23 May 2003, Stockholm, Sweden. Available at http://www.it.kth.se/~vatn/research/roam-arch.pdf) WISP BACKBONE NETWORKS ^ ^ | | +--+--+ +--+--+ | | | | |WISP1| |WISP2| ... | AR1 | | AR2 | +--+--+ +--+--+ | | Tunnels between each AP ----+---+-------+--------+------- and AR, e.g., using | | VLAN tagging +--+--+ +--+--+ | | | | | AP1 | | AP2 | ... | | | | +--+--+ +--+--+ APs act as 802.1X authenticators | | Map traffic of each USER to the o o VLAN associated with its WISP. o o | | +--+--+ +--+--+ | | | | |USER1| |USER2| ......... | | | | +-----+ +-----+ Follow up question: ------------------- Perhaps you disagree to the whole idea of supporting the case with multiple ARs per AP. Nevertheless, I have a follow-up question and it concerns the usage of the "Context-ID" if one could have more than one AR per AP. The CARD draft uses the "Context-ID" field to map different sub-options to a specific AR. Together with the "MATCH Status-Code indication" the "Context-ID" can be used to avoid sending the CAR's address and capability information multiple times if two or more L2 IDs resolve to the same AR. To enable for multiple ARs per AP I would suggest to use two context fields instead of the single "Context-ID" field. By this one could avoid sending one copy of each "L2 ID" sub-option for each attached AR. One of the two contexts fields would be common to the all ARs on the shared network ("LAN-context ID") and one is specific to the individual ARs ("AR-context ID"). The Address sub-option would contain both context ID fields, while "L2 ID" suboption would only contain "LAN-context ID" and the "Capability Container" suboption would only contain an "AR-context ID". Would this be a good thing? The "LAN-context ID" could perhaps be based on a MAC-address of one of the attached ARs, using some election method similar to the "Root bridge election of the Spanning Tree algorithm" or the "Designated Router" election used by OSPF. AJOY-> We have simpler way to resolve this issue. We think it may be enough to include CAR IP address as one of the capabilities of the capability container sub-option. As long as the combination of the context-id and CAR IP is unique, MN will be able to correctly decode the CARD reply and extract capabilities associated with various CAR(s) serving single AP. Please let us know if you see any problem with approach. This approach does not require any change of existing message format. BW J-O ---------------------------------------------------------------------- Jon-Olov Vatn Email: vatn@it.kth.se Royal Institute of Technology Address: KTH-IMIT Dep. of Microelectronics and Isafjordsgatan 39 Information Technology S-164 40 Kista SWEDEN Telecommunication System Lab. Fax: +46 8 751 17 93 _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Dec 5 03:26:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25515 for ; Fri, 5 Dec 2003 03:26:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ASBHo-0001N5-9Z for seamoby-archive@odin.ietf.org; Fri, 05 Dec 2003 03:26:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB58Q4xZ005265 for seamoby-archive@odin.ietf.org; Fri, 5 Dec 2003 03:26:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ASBHn-0001Mq-LG for seamoby-web-archive@optimus.ietf.org; Fri, 05 Dec 2003 03:26:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25498 for ; Fri, 5 Dec 2003 03:25:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ASBHl-0004gu-00 for seamoby-web-archive@ietf.org; Fri, 05 Dec 2003 03:26:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ASBHk-0004gq-00 for seamoby-web-archive@ietf.org; Fri, 05 Dec 2003 03:26:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ASBHl-0001Lz-7Y; Fri, 05 Dec 2003 03:26:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ASBGx-0001L6-GP for seamoby@optimus.ietf.org; Fri, 05 Dec 2003 03:25:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25489 for ; Fri, 5 Dec 2003 03:24:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ASBGv-0004ga-00 for seamoby@ietf.org; Fri, 05 Dec 2003 03:25:09 -0500 Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx with esmtp (Exim 4.12) id 1ASBGu-0004gX-00 for seamoby@ietf.org; Fri, 05 Dec 2003 03:25:08 -0500 Message-ID: <035a01c3bb09$5902c780$1501a8c0@dclkempt40> From: "James Kempf" To: Cc: Date: Fri, 5 Dec 2003 00:25:27 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Seamoby] Conclusion of Last Call on draft-ietf-seamoby-card-protocol-05.txt Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Folks, WG Last Call has concluded on draft-ietf-seamoby-card-protocol-05.txt without any additional issues raised, so it looks like the WG is satisfied with the document and we are ready to proceed to the wider IETF for review and publication. Prior to doing that, I intend to give it one last critical read for editorial issues, in line with the recent thinking about requiring WG chairs to be more proactive about assuring document quality. After that, Pat and I will send it to Allison for AD Review, and then review and approval by the IESG when she is happy with it. Allision has generously offered to line up some outside reviewers from other areas to ensure that we have proper cross-area review. Thank you all for your year of hard effort on completing this document. jak _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Mon Dec 8 14:15:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25361 for ; Mon, 8 Dec 2003 14:15:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATQqZ-0000gU-Bk for seamoby-archive@odin.ietf.org; Mon, 08 Dec 2003 14:15:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8JF75m002624 for seamoby-archive@odin.ietf.org; Mon, 8 Dec 2003 14:15:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATQqZ-0000gF-8O for seamoby-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 14:15:07 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25353 for ; Mon, 8 Dec 2003 14:14:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATQqW-00035i-00 for seamoby-web-archive@ietf.org; Mon, 08 Dec 2003 14:15:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ATQqW-00035e-00 for seamoby-web-archive@ietf.org; Mon, 08 Dec 2003 14:15:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATQqV-0000fa-Kp; Mon, 08 Dec 2003 14:15:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATQqA-0000ez-9t for seamoby@optimus.ietf.org; Mon, 08 Dec 2003 14:14:45 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25341 for ; Mon, 8 Dec 2003 14:14:25 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATQq7-00035A-00 for seamoby@ietf.org; Mon, 08 Dec 2003 14:14:39 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1ATQq7-00034g-00 for seamoby@ietf.org; Mon, 08 Dec 2003 14:14:39 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id hB8JE1l30054; Mon, 8 Dec 2003 11:14:01 -0800 X-mProtect: <200312081914> Nokia Silicon Valley Messaging Protection Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpd603SUy; Mon, 08 Dec 2003 11:14:00 PST Message-ID: <3FD4CD6E.2075B826@iprg.nokia.com> Date: Mon, 08 Dec 2003 11:13:50 -0800 From: Rajeev Koodli Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Seamoby CTP Issues CC: seamoby@ietf.org Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token? References: <1069404882.47.0.767706199792.issue30@danforsberg.info> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit John Loughney SEAMOBY-Issues wrote: > New submission from John Loughney : > > In case nAR requests the transfer by a CTR message, the pAR must verify > the MN's authorization token. If this token is unvalid, what do we do ? > > Possible solutions: > > - nothing ? the pAR does not answer to nAR. > - pAR indicates the error to nAR: > * In the CTD message. > * In a error message which could carry error information. > pAR MUST respond to nAR with an appropriate error. nAR SHOULD convey the result to the MN. -Rajeev > > others ? > > ---------- > category: Editorial > document: draft-ietf-seamoby-ctp-05.txt > messages: 39 > nosy: jloughney > priority: Should Fix > status: No Discussion > title: How to handle bad MN's authorization Token? > _____________________________________________________________ > Seamoby CTP Issues > > _____________________________________________________________ > > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Tue Dec 9 04:01:19 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18724 for ; Tue, 9 Dec 2003 04:01:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATdjs-0003zo-9l for seamoby-archive@odin.ietf.org; Tue, 09 Dec 2003 04:01:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB9914EX015343 for seamoby-archive@odin.ietf.org; Tue, 9 Dec 2003 04:01:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATdjr-0003zH-Fu for seamoby-web-archive@optimus.ietf.org; Tue, 09 Dec 2003 04:01:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18695 for ; Tue, 9 Dec 2003 04:00:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATdjo-00045H-00 for seamoby-web-archive@ietf.org; Tue, 09 Dec 2003 04:01:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ATdjo-00045E-00 for seamoby-web-archive@ietf.org; Tue, 09 Dec 2003 04:01:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATdjp-0003xx-4j; Tue, 09 Dec 2003 04:01:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATdjH-0003wr-1H for seamoby@optimus.ietf.org; Tue, 09 Dec 2003 04:00:27 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18678 for ; Tue, 9 Dec 2003 04:00:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATdjE-00044j-00 for seamoby@ietf.org; Tue, 09 Dec 2003 04:00:24 -0500 Received: from herculanum.int-evry.fr ([157.159.11.15]) by ietf-mx with esmtp (Exim 4.12) id 1ATdjD-00044O-00 for seamoby@ietf.org; Tue, 09 Dec 2003 04:00:23 -0500 Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20]) by herculanum.int-evry.fr (Postfix) with ESMTP id E6129356F0; Tue, 9 Dec 2003 09:56:38 +0100 (CET) Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19]) by spartebis.int-evry.fr (Postfix) with SMTP id D34CE3F428; Tue, 9 Dec 2003 09:56:38 +0100 (CET) Received: from sparte.int-evry.fr ([157.159.10.11]) by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003120909560816548 ; Tue, 09 Dec 2003 09:56:09 +0100 Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78]) by sparte.int-evry.fr (Postfix) with ESMTP id 270CA3F428; Tue, 9 Dec 2003 09:56:38 +0100 (CET) Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1ATdeX-0000gv-Oh; Tue, 09 Dec 2003 09:55:33 +0100 Date: Tue, 9 Dec 2003 09:55:33 +0100 From: Julien Bournelle To: Rajeev Koodli Cc: Seamoby CTP Issues , seamoby@ietf.org Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token? Message-ID: <20031209085533.GA2605@ipv6-5.int-evry.fr> References: <1069404882.47.0.767706199792.issue30@danforsberg.info> <3FD4CD6E.2075B826@iprg.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FD4CD6E.2075B826@iprg.nokia.com> Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , Hi, On Mon, Dec 08, 2003 at 11:13:50AM -0800, Rajeev Koodli wrote: > John Loughney SEAMOBY-Issues wrote: > > > New submission from John Loughney : > > > > In case nAR requests the transfer by a CTR message, the pAR must verify > > the MN's authorization token. If this token is unvalid, what do we do ? > > > > Possible solutions: > > > > - nothing ? the pAR does not answer to nAR. > > - pAR indicates the error to nAR: > > * In the CTD message. > > * In a error message which could carry error information. > > > > pAR MUST respond to nAR with an appropriate error. > nAR SHOULD convey the result to the MN. I agree with that but how to carry this error ? In the CTD message or do we create a new message to carry error ? thanks, > > -Rajeev > > > > > > others ? > > > > ---------- > > category: Editorial > > document: draft-ietf-seamoby-ctp-05.txt > > messages: 39 > > nosy: jloughney > > priority: Should Fix > > status: No Discussion > > title: How to handle bad MN's authorization Token? > > _____________________________________________________________ > > Seamoby CTP Issues > > > > _____________________________________________________________ > > > > _______________________________________________ > > Seamoby mailing list > > Seamoby@ietf.org > > https://www1.ietf.org/mailman/listinfo/seamoby > > > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby > -- julien.bournelle@int-evry.fr _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Tue Dec 9 15:49:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16190 for ; Tue, 9 Dec 2003 15:49:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATon4-0000e8-GQ for seamoby-archive@odin.ietf.org; Tue, 09 Dec 2003 15:49:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB9Kn6fx002478 for seamoby-archive@odin.ietf.org; Tue, 9 Dec 2003 15:49:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATon3-0000ds-Mw for seamoby-web-archive@optimus.ietf.org; Tue, 09 Dec 2003 15:49:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16080 for ; Tue, 9 Dec 2003 15:48:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATon2-0000Me-00 for seamoby-web-archive@ietf.org; Tue, 09 Dec 2003 15:49:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ATon1-0000MZ-00 for seamoby-web-archive@ietf.org; Tue, 09 Dec 2003 15:49:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATomz-0000dX-E4; Tue, 09 Dec 2003 15:49:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATom0-0000a3-1m for seamoby@optimus.ietf.org; Tue, 09 Dec 2003 15:48:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15945 for ; Tue, 9 Dec 2003 15:47:44 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AToly-0000Ix-00 for seamoby@ietf.org; Tue, 09 Dec 2003 15:47:58 -0500 Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx with esmtp (Exim 4.12) id 1ATolx-0000Ib-00 for seamoby@ietf.org; Tue, 09 Dec 2003 15:47:58 -0500 Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by motgate8.mot.com (Motorola/Motgate3) with ESMTP id hB9KluP1001710 for ; Tue, 9 Dec 2003 13:47:56 -0700 (MST) Received: from il27exm02.cig.mot.com (il27exm02.cig.mot.com [10.17.193.3]) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id hB9KlKPx021910 for ; Tue, 9 Dec 2003 14:47:34 -0600 Received: by il27exm02.cig.mot.com with Internet Mail Service (5.5.2657.2) id ; Tue, 9 Dec 2003 14:47:20 -0600 Message-ID: From: Nakhjiri Madjid-MNAKHJI1 To: "'Rajeev Koodli'" , Seamoby CTP Issues Cc: seamoby@ietf.org Subject: RE: [Seamoby] [issue30] How to handle bad MN's authorization Toke n? Date: Tue, 9 Dec 2003 14:46:58 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , Rajeev, I don't recall whether there was a message authentication procedure between the pAR and nAR, if there is none, and the pAR can't verify the authorization token, then we may open the door to DoS attacks on the pAR. So responding to nAR may have bad consequences... If there is no message authentication between nAR and pAR, while you are expecting the MN to authenticate itself to pAR (to me this is half way solution), then the pAR should ignore the request. Madjid -----Original Message----- From: seamoby-admin@ietf.org [mailto:seamoby-admin@ietf.org]On Behalf Of Rajeev Koodli Sent: Monday, December 08, 2003 1:14 PM To: Seamoby CTP Issues Cc: seamoby@ietf.org Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token? John Loughney SEAMOBY-Issues wrote: > New submission from John Loughney : > > In case nAR requests the transfer by a CTR message, the pAR must verify > the MN's authorization token. If this token is unvalid, what do we do ? > > Possible solutions: > > - nothing ? the pAR does not answer to nAR. > - pAR indicates the error to nAR: > * In the CTD message. > * In a error message which could carry error information. > pAR MUST respond to nAR with an appropriate error. nAR SHOULD convey the result to the MN. -Rajeev > > others ? > > ---------- > category: Editorial > document: draft-ietf-seamoby-ctp-05.txt > messages: 39 > nosy: jloughney > priority: Should Fix > status: No Discussion > title: How to handle bad MN's authorization Token? > _____________________________________________________________ > Seamoby CTP Issues > > _____________________________________________________________ > > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Dec 12 19:04:29 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04337 for ; Fri, 12 Dec 2003 19:04:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxGN-0007uz-Qf for seamoby-archive@odin.ietf.org; Fri, 12 Dec 2003 19:04:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBD0437L030431 for seamoby-archive@odin.ietf.org; Fri, 12 Dec 2003 19:04:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxGN-0007uk-MR for seamoby-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 19:04:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04295 for ; Fri, 12 Dec 2003 19:03:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUxGK-0004q7-00 for seamoby-web-archive@ietf.org; Fri, 12 Dec 2003 19:04:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AUxGK-0004q3-00 for seamoby-web-archive@ietf.org; Fri, 12 Dec 2003 19:04:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxGL-0007uE-Bv; Fri, 12 Dec 2003 19:04:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxFW-0007s6-P7 for seamoby@optimus.ietf.org; Fri, 12 Dec 2003 19:03:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04256 for ; Fri, 12 Dec 2003 19:03:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUxFT-0004p6-00 for seamoby@ietf.org; Fri, 12 Dec 2003 19:03:07 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AUxFS-0004oe-00 for seamoby@ietf.org; Fri, 12 Dec 2003 19:03:06 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id hBD029r25099; Fri, 12 Dec 2003 16:02:09 -0800 X-mProtect: <200312130002> Nokia Silicon Valley Messaging Protection Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdwpAvAm; Fri, 12 Dec 2003 16:02:08 PST Message-ID: <3FDA56F5.8C43A449@iprg.nokia.com> Date: Fri, 12 Dec 2003 16:01:58 -0800 From: Rajeev Koodli Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Nakhjiri Madjid-MNAKHJI1 CC: Seamoby CTP Issues , seamoby@ietf.org Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, is your concern message tampering between pAR and nAR ? If so, that should apply to all contexts. I think we address that by saying the routers SHOULD have SAs. Regards, -Rajeev Nakhjiri Madjid-MNAKHJI1 wrote: > Rajeev, > > I don't recall whether there was a message authentication procedure between > the pAR and nAR, if there is none, and the pAR can't verify the authorization > token, then we may open the door to DoS attacks on the pAR. So responding to > nAR may have bad consequences... > If there is no message authentication between nAR and pAR, while you are expecting > the MN to authenticate itself to pAR (to me this is half way solution), then the > pAR should ignore the request. > > Madjid > > -----Original Message----- > From: seamoby-admin@ietf.org [mailto:seamoby-admin@ietf.org]On Behalf Of > Rajeev Koodli > Sent: Monday, December 08, 2003 1:14 PM > To: Seamoby CTP Issues > Cc: seamoby@ietf.org > Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization > Token? > > John Loughney SEAMOBY-Issues wrote: > > > New submission from John Loughney : > > > > In case nAR requests the transfer by a CTR message, the pAR must verify > > the MN's authorization token. If this token is unvalid, what do we do ? > > > > Possible solutions: > > > > - nothing ? the pAR does not answer to nAR. > > - pAR indicates the error to nAR: > > * In the CTD message. > > * In a error message which could carry error information. > > > > pAR MUST respond to nAR with an appropriate error. > nAR SHOULD convey the result to the MN. > > -Rajeev > > > > > others ? > > > > ---------- > > category: Editorial > > document: draft-ietf-seamoby-ctp-05.txt > > messages: 39 > > nosy: jloughney > > priority: Should Fix > > status: No Discussion > > title: How to handle bad MN's authorization Token? > > _____________________________________________________________ > > Seamoby CTP Issues > > > > _____________________________________________________________ > > > > _______________________________________________ > > Seamoby mailing list > > Seamoby@ietf.org > > https://www1.ietf.org/mailman/listinfo/seamoby > > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Dec 12 19:05:32 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04400 for ; Fri, 12 Dec 2003 19:05:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxHP-00084S-AC for seamoby-archive@odin.ietf.org; Fri, 12 Dec 2003 19:05:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBD056eJ030999 for seamoby-archive@odin.ietf.org; Fri, 12 Dec 2003 19:05:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxHO-000835-7G for seamoby-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 19:05:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04374 for ; Fri, 12 Dec 2003 19:05:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUxHK-0004tj-00 for seamoby-web-archive@ietf.org; Fri, 12 Dec 2003 19:05:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AUxHK-0004tg-00 for seamoby-web-archive@ietf.org; Fri, 12 Dec 2003 19:05:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxHM-00080E-L1; Fri, 12 Dec 2003 19:05:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUxGd-0007x0-LT for seamoby@optimus.ietf.org; Fri, 12 Dec 2003 19:04:19 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04307 for ; Fri, 12 Dec 2003 19:04:14 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUxGa-0004qf-00 for seamoby@ietf.org; Fri, 12 Dec 2003 19:04:16 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AUxGZ-0004pp-00 for seamoby@ietf.org; Fri, 12 Dec 2003 19:04:15 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id hBD03fE25949; Fri, 12 Dec 2003 16:03:41 -0800 X-mProtect: <200312130003> Nokia Silicon Valley Messaging Protection Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdHorgWy; Fri, 12 Dec 2003 16:03:39 PST Message-ID: <3FDA574E.C4D5907D@iprg.nokia.com> Date: Fri, 12 Dec 2003 16:03:26 -0800 From: Rajeev Koodli Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Julien Bournelle CC: Seamoby CTP Issues , seamoby@ietf.org Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token? References: <1069404882.47.0.767706199792.issue30@danforsberg.info> <3FD4CD6E.2075B826@iprg.nokia.com> <20031209085533.GA2605@ipv6-5.int-evry.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Julien Bournelle wrote: > > > > > > > pAR MUST respond to nAR with an appropriate error. > > nAR SHOULD convey the result to the MN. > > I agree with that but how to carry this error ? In the CTD message or do > we create a new message to carry error ? > This should be supplied in CTD. We don't need another message particularly for carrying the error. Regards, -Rajeev > > thanks, > > > > > -Rajeev > > > > > > > > > > others ? > > > > > > ---------- > > > category: Editorial > > > document: draft-ietf-seamoby-ctp-05.txt > > > messages: 39 > > > nosy: jloughney > > > priority: Should Fix > > > status: No Discussion > > > title: How to handle bad MN's authorization Token? > > > _____________________________________________________________ > > > Seamoby CTP Issues > > > > > > _____________________________________________________________ > > > > > > _______________________________________________ > > > Seamoby mailing list > > > Seamoby@ietf.org > > > https://www1.ietf.org/mailman/listinfo/seamoby > > > > > > _______________________________________________ > > Seamoby mailing list > > Seamoby@ietf.org > > https://www1.ietf.org/mailman/listinfo/seamoby > > > > -- > julien.bournelle@int-evry.fr _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Mon Dec 15 04:00:49 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00034 for ; Mon, 15 Dec 2003 04:00:49 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AVoaR-0001kz-3M for seamoby-archive@odin.ietf.org; Mon, 15 Dec 2003 04:00:19 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBF90H7d006716 for seamoby-archive@odin.ietf.org; Mon, 15 Dec 2003 04:00:17 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AVoaM-0001kC-OE for seamoby-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 04:00:14 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00031 for ; Mon, 15 Dec 2003 04:00:12 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AVoaK-0007h5-00 for seamoby-web-archive@ietf.org; Mon, 15 Dec 2003 04:00:12 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AVoaJ-0007gz-00 for seamoby-web-archive@ietf.org; Mon, 15 Dec 2003 04:00:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AVoaF-0001jN-3e; Mon, 15 Dec 2003 04:00:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AVoZb-0001i0-Np for seamoby@optimus.ietf.org; Mon, 15 Dec 2003 03:59:27 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00009 for ; Mon, 15 Dec 2003 03:59:25 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AVoZZ-0007gq-00 for seamoby@ietf.org; Mon, 15 Dec 2003 03:59:25 -0500 Received: from smtp2.libero.it ([193.70.192.52]) by ietf-mx with esmtp (Exim 4.12) id 1AVoZY-0007gQ-00 for seamoby@ietf.org; Mon, 15 Dec 2003 03:59:24 -0500 Received: from libero.it (193.70.192.97) by smtp2.libero.it (7.0.020-DD01) id 3F6F0DA000A60B8C for seamoby@ietf.org; Mon, 15 Dec 2003 09:59:39 +0100 Date: Mon, 15 Dec 2003 09:58:55 +0100 Message-Id: MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable From: "Ivano De Luca" To: "seamoby" X-XaM3-API-Version: 4.1 (B19) X-type: 0 X-SenderIP: 212.171.55.24 Content-Transfer-Encoding: quoted-printable Subject: [Seamoby] CARD servers discovery Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable I'm Ivano again. How are you ? I've a question for you again.... Le= t's suppose that a MN releaves 2 APs, connected with 2 AR connected with = 2 several CARD servers. (:-D) CARD1 CARD2 |= | || || |= | \\ // \\ = // CurrentAR AR2 || ||=0D = || || AP1 AP2 = \\ // \\ //=0D = \\ // MN How can= CARD1 know the IP address of CARD2 ? MN releaves AP2'MAC address from= its Current AR if CARD1 does not know CARD2'IP address ? Thanks for= the fastest answer ;-) Best Regards, Ivano from PBG4 =3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D Non =E8 bello Windows che =E8 bello, m= a =E8 bello MacOSX che piace _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Mon Dec 15 11:02:31 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14812 for ; Mon, 15 Dec 2003 11:02:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AVvAa-00017R-Fv for seamoby-archive@odin.ietf.org; Mon, 15 Dec 2003 11:02:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBFG24Bs004297 for seamoby-archive@odin.ietf.org; Mon, 15 Dec 2003 11:02:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AVvAa-00017E-07 for seamoby-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 11:02:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14795 for ; Mon, 15 Dec 2003 11:02:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AVvAX-0007VX-00 for seamoby-web-archive@ietf.org; Mon, 15 Dec 2003 11:02:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AVvAX-0007VU-00 for seamoby-web-archive@ietf.org; Mon, 15 Dec 2003 11:02:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AVvAX-00016a-RB; Mon, 15 Dec 2003 11:02:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AVv9k-00015y-Bv for seamoby@optimus.ietf.org; Mon, 15 Dec 2003 11:01:12 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14766 for ; Mon, 15 Dec 2003 11:01:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AVv9h-0007UL-00 for seamoby@ietf.org; Mon, 15 Dec 2003 11:01:09 -0500 Received: from [65.246.255.50] (helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AVv9h-0007UD-00 for seamoby@ietf.org; Mon, 15 Dec 2003 11:01:09 -0500 Received: from [138.15.108.3] (helo=mailer.nec-labs.com) by manatick with esmtp (Exim 4.24) id 1AVv9g-0008Ka-Lr for seamoby@ietf.org; Mon, 15 Dec 2003 11:01:08 -0500 Received: from peace ([138.15.107.202]) by mailer.nec-labs.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 15 Dec 2003 10:49:52 -0500 Message-ID: <005101c3c323$b7376b40$ca6b0f8a@peace> From: "Eunsoo Shim" To: "Ivano De Luca" , "seamoby" References: Subject: Re: [Seamoby] CARD servers discovery Date: Mon, 15 Dec 2003 10:54:25 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-OriginalArrivalTime: 15 Dec 2003 15:49:52.0879 (UTC) FILETIME=[14536FF0:01C3C323] Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA14767 Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi, Ivano, It is not so easy to read your message. Anyway I guess I understand your question. You are assuming two separate CARD servers. Please note that this is one = of the proposed approaches. There is another approach where there is no cent= ral server at all. In your scheme with the CARD servers, I think it is assumed that the two CARD servers don't share their information. So the current AR cannot know the IP address of AR2. This is a scalability issue. BTW, the current CARD draft does not specify how the CAR information is discovered or maintained in each AR. The current draft assumes that there= is correct CAR information already in each AR. Regards, Eunsoo ----- Original Message -----=20 From: "Ivano De Luca" To: "seamoby" Sent: Monday, December 15, 2003 3:58 AM Subject: [Seamoby] CARD servers discovery I'm Ivano again. How are you ? I've a question for you again.... Let's suppose that a MN releaves 2 APs, connected with 2 AR connected wit= h 2 several CARD servers. (:-D) CARD1 CARD2 || || || || \\ // \\ // CurrentAR AR2 || || || || AP1 AP2 \\ // \\ // \\ // MN How can CARD1 know the IP address of CARD2 ? MN releaves AP2'MAC address from its Current AR if CARD1 does not know CARD2'IP address ? Thanks for the fastest answer ;-) Best Regards, Ivano from PBG4 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Non =E8 bello Windows che =E8 bello, ma =E8 bello MacOSX che piace _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Mon Dec 15 16:23:32 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00655 for ; Mon, 15 Dec 2003 16:23:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AW0BD-0007vV-B5 for seamoby-archive@odin.ietf.org; Mon, 15 Dec 2003 16:23:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBFLN3mZ030465 for seamoby-archive@odin.ietf.org; Mon, 15 Dec 2003 16:23:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AW0BD-0007vI-7k for seamoby-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 16:23:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00634 for ; Mon, 15 Dec 2003 16:23:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AW0BB-0001HQ-00 for seamoby-web-archive@ietf.org; Mon, 15 Dec 2003 16:23:01 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AW0BA-0001HI-00 for seamoby-web-archive@ietf.org; Mon, 15 Dec 2003 16:23:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AW0BA-0001HC-00 for seamoby-web-archive@ietf.org; Mon, 15 Dec 2003 16:23:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AW0BA-0007uQ-Cl; Mon, 15 Dec 2003 16:23:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AW0Av-0007u1-OP for seamoby@optimus.ietf.org; Mon, 15 Dec 2003 16:22:46 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00621 for ; Mon, 15 Dec 2003 16:22:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AW0At-0001Gv-00 for seamoby@ietf.org; Mon, 15 Dec 2003 16:22:44 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AW0As-0001Go-00 for seamoby@ietf.org; Mon, 15 Dec 2003 16:22:43 -0500 Received: from motgate6.mot.com ([144.189.100.106]) by ietf-mx with esmtp (Exim 4.12) id 1AW0As-0001Gj-00 for seamoby@ietf.org; Mon, 15 Dec 2003 16:22:42 -0500 Received: from az33exr03.mot.com (pobox3.mot.com [10.64.251.242]) by motgate6.mot.com (Motorola/Motgate6) with ESMTP id hBFLM7EK027706 for ; Mon, 15 Dec 2003 14:22:07 -0700 (MST) Received: from il27exm02.cig.mot.com (il27exm02.cig.mot.com [10.17.193.3]) by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id hBFLHln1001077 for ; Mon, 15 Dec 2003 15:17:47 -0600 Received: by il27exm02.cig.mot.com with Internet Mail Service (5.5.2657.2) id ; Mon, 15 Dec 2003 15:17:51 -0600 Message-ID: From: Nakhjiri Madjid-MNAKHJI1 To: "'Rajeev Koodli'" , Nakhjiri Madjid-MNAKHJI1 Cc: Seamoby CTP Issues , seamoby@ietf.org Subject: RE: [Seamoby] [issue30] How to handle bad MN's authorization Toke n? Date: Mon, 15 Dec 2003 15:17:47 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.2) Content-Type: text/plain Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Hi Rajeev, No that was not my original concern (although that is a valid concern) the concern was somebody spoofing nAR, and hence the need for message authentication between pAR and nAR. Originally we didn't go as far as requiring message authentication for all messages between pAR and nAR (and yes the routers should have SAs, as the requirement stated, in case context delivery needs to be secure), but that was when we didn't have authentication token by the users. If you want the pAR to do something for every failed authentication token, then you are setting yourself for trouble (DoS attacks), especially since CT has to happen so quickly. Does the nAR has to keep any state? Madjid -----Original Message----- From: rajeev@darkstar.iprg.nokia.com [mailto:rajeev@darkstar.iprg.nokia.com]On Behalf Of Rajeev Koodli Sent: Friday, December 12, 2003 6:02 PM To: Nakhjiri Madjid-MNAKHJI1 Cc: Seamoby CTP Issues; seamoby@ietf.org Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token? Hi, is your concern message tampering between pAR and nAR ? If so, that should apply to all contexts. I think we address that by saying the routers SHOULD have SAs. Regards, -Rajeev Nakhjiri Madjid-MNAKHJI1 wrote: > Rajeev, > > I don't recall whether there was a message authentication procedure between > the pAR and nAR, if there is none, and the pAR can't verify the authorization > token, then we may open the door to DoS attacks on the pAR. So responding to > nAR may have bad consequences... > If there is no message authentication between nAR and pAR, while you are expecting > the MN to authenticate itself to pAR (to me this is half way solution), then the > pAR should ignore the request. > > Madjid > > -----Original Message----- > From: seamoby-admin@ietf.org [mailto:seamoby-admin@ietf.org]On Behalf Of > Rajeev Koodli > Sent: Monday, December 08, 2003 1:14 PM > To: Seamoby CTP Issues > Cc: seamoby@ietf.org > Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization > Token? > > John Loughney SEAMOBY-Issues wrote: > > > New submission from John Loughney : > > > > In case nAR requests the transfer by a CTR message, the pAR must verify > > the MN's authorization token. If this token is unvalid, what do we do ? > > > > Possible solutions: > > > > - nothing ? the pAR does not answer to nAR. > > - pAR indicates the error to nAR: > > * In the CTD message. > > * In a error message which could carry error information. > > > > pAR MUST respond to nAR with an appropriate error. > nAR SHOULD convey the result to the MN. > > -Rajeev > > > > > others ? > > > > ---------- > > category: Editorial > > document: draft-ietf-seamoby-ctp-05.txt > > messages: 39 > > nosy: jloughney > > priority: Should Fix > > status: No Discussion > > title: How to handle bad MN's authorization Token? > > _____________________________________________________________ > > Seamoby CTP Issues > > > > _____________________________________________________________ > > > > _______________________________________________ > > Seamoby mailing list > > Seamoby@ietf.org > > https://www1.ietf.org/mailman/listinfo/seamoby > > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Mon Dec 15 17:22:30 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03207 for ; Mon, 15 Dec 2003 17:22:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AW16J-0002Lo-BT for seamoby-archive@odin.ietf.org; Mon, 15 Dec 2003 17:22:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBFMM3Li009030 for seamoby-archive@odin.ietf.org; Mon, 15 Dec 2003 17:22:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AW16J-0002LZ-7t for seamoby-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 17:22:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03189 for ; Mon, 15 Dec 2003 17:21:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AW16G-0003fw-00 for seamoby-web-archive@ietf.org; Mon, 15 Dec 2003 17:22:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AW16F-0003fp-00 for seamoby-web-archive@ietf.org; Mon, 15 Dec 2003 17:22:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AW16F-0003fm-00 for seamoby-web-archive@ietf.org; Mon, 15 Dec 2003 17:21:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AW16G-0002Ku-CT; Mon, 15 Dec 2003 17:22:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AW160-0002Ka-IV for seamoby@optimus.ietf.org; Mon, 15 Dec 2003 17:21:44 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03183 for ; Mon, 15 Dec 2003 17:21:41 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AW15y-0003fO-00 for seamoby@ietf.org; Mon, 15 Dec 2003 17:21:42 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AW15x-0003fH-00 for seamoby@ietf.org; Mon, 15 Dec 2003 17:21:41 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AW15w-0003ec-00 for seamoby@ietf.org; Mon, 15 Dec 2003 17:21:40 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id hBFML2G17087; Mon, 15 Dec 2003 14:21:02 -0800 X-mProtect: <200312152221> Nokia Silicon Valley Messaging Protection Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdWrZfvF; Mon, 15 Dec 2003 14:21:01 PST Message-ID: <3FDE33C3.B14A89FC@iprg.nokia.com> Date: Mon, 15 Dec 2003 14:20:51 -0800 From: Rajeev Koodli Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Nakhjiri Madjid-MNAKHJI1 CC: Seamoby CTP Issues , seamoby@ietf.org Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Nakhjiri Madjid-MNAKHJI1 wrote: > Hi Rajeev, > > If you want the pAR to do something for every failed authentication > token, then you are setting yourself for trouble (DoS attacks), especially > since CT has to happen so quickly. Does the nAR has to keep any state? > each malicious MN can send one such bogus token. I think a DoS attack would probably need a bigger incentive. FYI: in Fast Handovers, a MN is allowed to send an FBU with a request to send an Ack. In Mobile IPv6, the 'A' bit in BU requests the HA to send a Binding Ack. I don't see this as a loophole to launch an attack. Am I missing something ? The CT Request from nAR to pAR is in response to CTAR which includes the MN's authorization token. The nAR has to match that with what pAR supplies. The size of the token is 4 bytes. If a malicious MN is wants launch a DoS attack on nAR's buffers, nAR can essentially stop being a router for that MN after the token verification fails (after couple of tens of milliseconds). I think the downside of not including the token opens up the possibility to steal some other MN's contexts, which we must avoid. -Rajeev > > Madjid > > -----Original Message----- > From: rajeev@darkstar.iprg.nokia.com > [mailto:rajeev@darkstar.iprg.nokia.com]On Behalf Of Rajeev Koodli > Sent: Friday, December 12, 2003 6:02 PM > To: Nakhjiri Madjid-MNAKHJI1 > Cc: Seamoby CTP Issues; seamoby@ietf.org > Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization > Token? > > Hi, > > is your concern message tampering between pAR and nAR ? > If so, that should apply to all contexts. I think we address that > by saying the routers SHOULD have SAs. > > Regards, > > -Rajeev > > Nakhjiri Madjid-MNAKHJI1 wrote: > > > Rajeev, > > > > I don't recall whether there was a message authentication procedure between > > the pAR and nAR, if there is none, and the pAR can't verify the authorization > > token, then we may open the door to DoS attacks on the pAR. So responding to > > nAR may have bad consequences... > > If there is no message authentication between nAR and pAR, while you are expecting > > the MN to authenticate itself to pAR (to me this is half way solution), then the > > pAR should ignore the request. > > > > Madjid > > > > -----Original Message----- > > From: seamoby-admin@ietf.org [mailto:seamoby-admin@ietf.org]On Behalf Of > > Rajeev Koodli > > Sent: Monday, December 08, 2003 1:14 PM > > To: Seamoby CTP Issues > > Cc: seamoby@ietf.org > > Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization > > Token? > > > > John Loughney SEAMOBY-Issues wrote: > > > > > New submission from John Loughney : > > > > > > In case nAR requests the transfer by a CTR message, the pAR must verify > > > the MN's authorization token. If this token is unvalid, what do we do ? > > > > > > Possible solutions: > > > > > > - nothing ? the pAR does not answer to nAR. > > > - pAR indicates the error to nAR: > > > * In the CTD message. > > > * In a error message which could carry error information. > > > > > > > pAR MUST respond to nAR with an appropriate error. > > nAR SHOULD convey the result to the MN. > > > > -Rajeev > > > > > > > > others ? > > > > > > ---------- > > > category: Editorial > > > document: draft-ietf-seamoby-ctp-05.txt > > > messages: 39 > > > nosy: jloughney > > > priority: Should Fix > > > status: No Discussion > > > title: How to handle bad MN's authorization Token? > > > _____________________________________________________________ > > > Seamoby CTP Issues > > > > > > _____________________________________________________________ > > > > > > _______________________________________________ > > > Seamoby mailing list > > > Seamoby@ietf.org > > > https://www1.ietf.org/mailman/listinfo/seamoby > > > > _______________________________________________ > > Seamoby mailing list > > Seamoby@ietf.org > > https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Tue Dec 16 06:02:31 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10690 for ; Tue, 16 Dec 2003 06:02:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWCxo-0004dp-Ki for seamoby-archive@odin.ietf.org; Tue, 16 Dec 2003 06:02:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGB24Bt017835 for seamoby-archive@odin.ietf.org; Tue, 16 Dec 2003 06:02:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWCxo-0004da-5L for seamoby-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 06:02:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10674 for ; Tue, 16 Dec 2003 06:02:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AWCxk-0004h1-00 for seamoby-web-archive@ietf.org; Tue, 16 Dec 2003 06:02:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AWCxj-0004gt-00 for seamoby-web-archive@ietf.org; Tue, 16 Dec 2003 06:01:59 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AWCxj-0004gq-00 for seamoby-web-archive@ietf.org; Tue, 16 Dec 2003 06:01:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWCxl-0004ct-ID; Tue, 16 Dec 2003 06:02:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWCxS-0004cc-HJ for seamoby@optimus.ietf.org; Tue, 16 Dec 2003 06:01:42 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10668 for ; Tue, 16 Dec 2003 06:01:38 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AWCxO-0004gb-00 for seamoby@ietf.org; Tue, 16 Dec 2003 06:01:38 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AWCxN-0004gU-00 for seamoby@ietf.org; Tue, 16 Dec 2003 06:01:38 -0500 Received: from herculanum.int-evry.fr ([157.159.11.15]) by ietf-mx with esmtp (Exim 4.12) id 1AWCxN-0004eq-00 for seamoby@ietf.org; Tue, 16 Dec 2003 06:01:37 -0500 Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20]) by herculanum.int-evry.fr (Postfix) with ESMTP id B7227340A3; Tue, 16 Dec 2003 12:01:08 +0100 (CET) Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19]) by spartebis.int-evry.fr (Postfix) with SMTP id 471CE3F45C; Tue, 16 Dec 2003 12:01:08 +0100 (CET) Received: from sparte.int-evry.fr ([157.159.10.11]) by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003121612002408200 ; Tue, 16 Dec 2003 12:00:24 +0100 Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78]) by sparte.int-evry.fr (Postfix) with ESMTP id 597313F428; Tue, 16 Dec 2003 12:01:07 +0100 (CET) Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1AWCvh-000897-Ve; Tue, 16 Dec 2003 11:59:53 +0100 Date: Tue, 16 Dec 2003 11:59:53 +0100 From: Julien Bournelle To: Rajeev Koodli Cc: Nakhjiri Madjid-MNAKHJI1 , Seamoby CTP Issues , seamoby@ietf.org Subject: Re: [Seamoby] [issue30] How to handle bad MN's authorization Token? Message-ID: <20031216105953.GO16373@ipv6-5.int-evry.fr> References: <3FDA56F5.8C43A449@iprg.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FDA56F5.8C43A449@iprg.nokia.com> Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Hi On Fri, Dec 12, 2003 at 04:01:58PM -0800, Rajeev Koodli wrote: > > Hi, > > is your concern message tampering between pAR and nAR ? > If so, that should apply to all contexts. I think we address that > by saying the routers SHOULD have SAs. I just wanted to note that the routers MUST have SAs. (ESP protection) regards, -- julien.bournelle@int-evry.fr _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Wed Dec 17 03:36:57 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29025 for ; Wed, 17 Dec 2003 03:36:56 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWXAR-0000nX-PG for seamoby-archive@odin.ietf.org; Wed, 17 Dec 2003 03:36:28 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBH8aRfG003068 for seamoby-archive@odin.ietf.org; Wed, 17 Dec 2003 03:36:27 -0500 Received: from [218.20.61.215] (helo=seamoby-web-archive) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWXAA-0000mY-93 for seamoby-web-archive@optimus.ietf.org; Wed, 17 Dec 2003 03:36:15 -0500 From: =?GB2312?B?uePW3crAvM3R9LniucvOytPQz965q8u+?= Subject: =?GB2312?B?u9jQxQ==?= 16:37:19:161 To: seamoby-web-archive@optimus.ietf.org Content-Type: text/html;charset="GB2312" Reply-To: cykun68@china.com Date: Wed, 17 Dec 2003 16:37:30 +0800 X-Priority: 1 X-Mailer: Microsoft Outlook Express 5.50.4133.2400 Message-Id:

               
世纪阳光财务沙龙
　
　研讨主题：预算管理中的难点问题
　
　2003年12月20日下午2:00-5:00 ● 广州 景星酒店


沙龙宗旨：
　　◎ 为企业财务管理人士创造同行之间的交流机会 　　◎ 探讨财务管理实践中的常见问题以及热点话题
　　◎ 通过借鉴先行者或者成功者的经验教训，得到启发和触动，从而探索自身企业问题的解决之道。

沙龙特点：
　　◎ 非盈利性质(只需100元/位)　　　　　 ◎ 以分享和交流形式为主
　　◎ 常年不定期举办　　　　　　　　　　 ◎ 分享嘉宾来自著名企业的实践精英
　　◎ 每期沙龙主题基于调研结果

本期嘉宾：
　　来自广州宝洁、深圳怡宝、丽珠医药公司、UT斯达康、新太科技、佳都国际集团的财务总监和高级财务经理们，将把自身企业沉淀多年的优秀预算管理精华及实际操作流程，经过提炼总结，在这里和盘托出，与大家分享。

★ 如果您希望在沙龙上发言，请提前预约!
　　　 您希望分享的主题是：（请写明在《报名申请表》的“补充要求或建议”栏目里，谢谢！)

研讨内容：（根据调研结果决定讨论重点，请选择您最感兴趣的选题，您可以在以下提示中选择，也可以另外注明；并把您最感兴趣的选题复制或填写在《报名申请表》的“补充要求或建议”栏目，谢谢！)
　　　□ 如何确立企业"利润责任中心"和"成本责任中心"？
　　　□ 如何将公司总目标分配到各个责任中心？
　　　□ 如何将你的预算从抽屉里的文件变成每个经理人心中追求的目标？
　　　□ 如何将投资集中于企业创收的部分，做到"有所为，有所不为"？
　　　□ 如何建立预算系统使一线经理的预算信息及财务总监的汇总分析同步？
　　　□ 如何使子公司、分公司预算与总公司同步？
　　　□ 如何把握预算的可行性？
　　　□ 如何将预算简明、清晰的传达给投资人、董事会、管理层及每个员工？
　　　□ 如何将管理费用及共同费用分摊到利润责任中心并说服他们接受？



　
现场赠送：
　　◎ 凡到场人员均赠送“第二届华南财务管理创新高峰论坛”vcd剪辑；
　　◎ 凡现场报读世纪阳光系列培训课程，均可获赠更多优惠。


主办单位：广州世纪阳光顾问有限公司

　联系电话：（020）38742252,38742253 赵小姐,吴小姐，程小姐
　传　　真：（020）38742580 　　　　　Email：training@21cnsun.com
　开户行:广州市商业银行华师大支行户名:广州世纪阳光顾问有限公司帐号321-8050022-16 

　　　　　　报 　名　 申　 请　 表　　　　
报读课程
单位名称
电话号码
详细地址
传真号码
企业性质
 国营  民营  集体 
外资  合资  上市公司
邮 编
付费方式
 会前银行划帐 会前上门交费 现场交费
安排住宿(费用自理): 是 否
姓 　名
性　别
职　　　　位
手 　　　机
E-mail
补充要求或建议
　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　SalesID:
　　　　　　　　

From exim@www1.ietf.org Mon Dec 22 12:23:33 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25914 for ; Mon, 22 Dec 2003 12:23:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYTlq-0001ax-JQ for seamoby-archive@odin.ietf.org; Mon, 22 Dec 2003 12:23:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBMHN628006125 for seamoby-archive@odin.ietf.org; Mon, 22 Dec 2003 12:23:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYTlq-0001ad-E4 for seamoby-web-archive@optimus.ietf.org; Mon, 22 Dec 2003 12:23:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25866 for ; Mon, 22 Dec 2003 12:22:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYTlm-0002u1-00 for seamoby-web-archive@ietf.org; Mon, 22 Dec 2003 12:23:02 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYTll-0002tt-00 for seamoby-web-archive@ietf.org; Mon, 22 Dec 2003 12:23:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AYTll-0002tq-00 for seamoby-web-archive@ietf.org; Mon, 22 Dec 2003 12:23:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYTll-0001YX-6l; Mon, 22 Dec 2003 12:23:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYTkx-0001YG-ET for seamoby@optimus.ietf.org; Mon, 22 Dec 2003 12:22:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25835 for ; Mon, 22 Dec 2003 12:22:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYTkv-0002tM-00 for seamoby@ietf.org; Mon, 22 Dec 2003 12:22:09 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYTkv-0002tF-00 for seamoby@ietf.org; Mon, 22 Dec 2003 12:22:09 -0500 Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx with esmtp (Exim 4.12) id 1AYTku-0002tC-00 for seamoby@ietf.org; Mon, 22 Dec 2003 12:22:08 -0500 Message-ID: <028301c3c8b0$2f514380$5b6015ac@dclkempt40> From: "James Kempf" To: Date: Mon, 22 Dec 2003 09:22:32 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Seamoby] Fw: ID Tracker State Update Notice: draft-ietf-seamoby-mobility-terminology Sender: seamoby-admin@ietf.org Errors-To: seamoby-admin@ietf.org X-BeenThere: seamoby@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,SUBJ_HAS_UNIQ_ID autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit ----- Original Message ----- From: "The IESG" To: ; Sent: Sunday, December 21, 2003 11:00 PM Subject: ID Tracker State Update Notice: draft-ietf-seamoby-mobility-terminology > 'State Changes to IESG Evaluation::AD Followup from IESG Evaluation::Revised ID Needed by Allison Mankin' > ID Tracker URL: https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=9277&rfc_flag=0 > > _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby