From exim@www1.ietf.org Mon Nov 3 00:01:03 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06842 for ; Mon, 3 Nov 2003 00:01:03 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGWpY-0003y9-8a for seamoby-archive@odin.ietf.org; Mon, 03 Nov 2003 00:00:44 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA350iI8015251 for seamoby-archive@odin.ietf.org; Mon, 3 Nov 2003 00:00:44 -0500 Received: from [219.234.29.195] (helo=02) by optimus.ietf.org with smtp (Exim 4.20) id 1AGWpX-0003xW-8O for seamoby-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 00:00:44 -0500 From: "赠送" To: Subject: 11月20日前免费注册参加最新的网上赚钱网 Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Date: Mon, 3 Nov 2003 12:59:39 +0800 X-Priority: 3 X-Mailer: JiXing mailer V1.75 Design By JohnnieHuang Message-Id: 朋友，你好，11月20日前注册"一诺网信息"网站,我为你免费激活，快快行动吧： http://yn888.8126.net/888/soho/index.asp?user=admin05 平常参加得50元 所有11月20日前注册的会员我全部会为你免费开通！ 请站长抓紧时间尽快发展您的下级！11月20日以后只要你下级发展一个付费的您就有10块的奖金！！！！ 这个消息请不要透露给没有注册的人！ 现在我全部为你免费打开！ 欢迎光临 03-11-3 12:59:04 ============================邮件内容与以下文字无关============================= 优联网络 http://www.chinamysql.com 专业提供各类虚拟主机，不满意可获退款。 强势套餐：100M主机送顶级域名，送10个10M企业油箱，加送20个二级域名，仅需318元/年！ 三龙证券投资 http://3long.sayba.com 为您提供专业理财服务。现在购买只需588元，赠送价值超过1800元的礼品！ 说吧网上商城 http://shop.sayba.com 全是厂商直销的新品或折上折的商品，是您网络购物的好去处！ 使用极星邮件群发，无须通过邮件服务器，直达对方邮箱，速度绝对一流！ 软件下载网址：http://www.lovexin.com，更多的超酷软件等你来下载哦！ From exim@www1.ietf.org Mon Nov 3 04:29:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24952 for ; Mon, 3 Nov 2003 04:29:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGb1H-0000he-Ka for seamoby-archive@odin.ietf.org; Mon, 03 Nov 2003 04:29:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA39T7fO002692 for seamoby-archive@odin.ietf.org; Mon, 3 Nov 2003 04:29:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGb1G-0000hG-Uf for seamoby-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 04:29: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 EAA24872 for ; Mon, 3 Nov 2003 04:28:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGb1D-0002YL-00 for seamoby-web-archive@ietf.org; Mon, 03 Nov 2003 04:29:03 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AGb1D-0002YF-00 for seamoby-web-archive@ietf.org; Mon, 03 Nov 2003 04:29:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGb1C-0000fI-5K; Mon, 03 Nov 2003 04:29:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGb0E-0000Qp-L8 for seamoby@optimus.ietf.org; Mon, 03 Nov 2003 04:28:02 -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 EAA24800 for ; Mon, 3 Nov 2003 04:27:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGb0B-0002Wh-00 for seamoby@ietf.org; Mon, 03 Nov 2003 04:27:59 -0500 Received: from smtp5.clb.oleane.net ([213.56.31.25]) by ietf-mx with esmtp (Exim 4.12) id 1AGb0A-0002WJ-00 for seamoby@ietf.org; Mon, 03 Nov 2003 04:27:58 -0500 Received: from oleane ([194.250.212.114]) by smtp5.clb.oleane.net with SMTP id hA39RRpR015878 for ; Mon, 3 Nov 2003 10:27:28 +0100 Message-ID: <014c01c3a1ed$306bd440$0601a8c0@www.oleane.com> From: "Peter Lewis" To: Date: Mon, 3 Nov 2003 10:30:58 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0149_01C3A1F5.91ED18C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Subject: [Seamoby] UWB Summit 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: , C'est un message de format MIME en plusieurs parties. ------=_NextPart_000_0149_01C3A1F5.91ED18C0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Which proposal will be selected as the IEEE 802.15.3a standard? A = consortium has just proposed to offer a RANDZ access to its patents. The = industry is now waiting for the reply from the supporters of the other = proposal.=20 This battle between technology heavyweights underlines the growing = importance of a technology expected to generate $1.39 billion in revenue = by 2007. All questions and answers will be delivered during the UWB Summit to be = held in Paris next 2-5 December. All details at: http://www.upperside.fr/newmobtech/uwb03cfp.htm ------=_NextPart_000_0149_01C3A1F5.91ED18C0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Which proposal will be selected as = the=20 IEEE 802.15.3a standard? A consortium has just proposed = to=20 offer a RANDZ access to its patents. The industry is now waiting for the = reply=20 from the supporters of the other proposal.
This battle between technology = heavyweights=20 underlines the growing importance of a technology expected to generate = $1.39=20 billion in revenue by 2007.
All questions and answers will be = delivered=20 during the UWB Summit to be held in Paris next 2-5=20 December.
All details at:
http://www.upper= side.fr/newmobtech/uwb03cfp.htm
------=_NextPart_000_0149_01C3A1F5.91ED18C0-- _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Mon Nov 3 07:08:14 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28692 for ; Mon, 3 Nov 2003 07:08:13 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGdUy-0000op-Cp for seamoby-archive@odin.ietf.org; Mon, 03 Nov 2003 07:07:56 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3C7uqB003143 for seamoby-archive@odin.ietf.org; Mon, 3 Nov 2003 07:07:56 -0500 Received: from [219.234.29.195] (helo=02) by optimus.ietf.org with smtp (Exim 4.20) id 1AGdUv-0000aV-QC for seamoby-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 07:07:56 -0500 From: "赠送" To: Subject: 11月20日前免费注册参加最新的网上赚钱网 Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Date: Mon, 3 Nov 2003 20:06:47 +0800 X-Priority: 3 X-Mailer: JiXing mailer V1.75 Design By JohnnieHuang Message-Id: 朋友，你好，11月20日前注册"一诺网信息"网站,我为你免费激活，快快行动吧： http://www.8126.net/888/soho/index.asp?user=admin05 平常参加得50元 所有11月20日前注册的会员我全部会为你免费开通！ 请站长抓紧时间尽快发展您的下级！11月20日以后只要你下级发展一个付费的您就有10块的奖金！！！！ 这个消息请不要透露给没有注册的人！ 现在我全部为你免费打开！ 欢迎光临 03-11-3 20:06:07 ============================邮件内容与以下文字无关============================= 优联网络 http://www.chinamysql.com 专业提供各类虚拟主机，不满意可获退款。 强势套餐：100M主机送顶级域名，送10个10M企业油箱，加送20个二级域名，仅需318元/年！ 三龙证券投资 http://3long.sayba.com 为您提供专业理财服务。现在购买只需588元，赠送价值超过1800元的礼品！ 说吧网上商城 http://shop.sayba.com 全是厂商直销的新品或折上折的商品，是您网络购物的好去处！ 使用极星邮件群发，无须通过邮件服务器，直达对方邮箱，速度绝对一流！ 软件下载网址：http://www.lovexin.com，更多的超酷软件等你来下载哦！ From exim@www1.ietf.org Tue Nov 4 13:18:20 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26055 for ; Tue, 4 Nov 2003 13:18: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 1AH5kh-0008OL-Hg for seamoby-archive@odin.ietf.org; Tue, 04 Nov 2003 13:18:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA4II3s1032241 for seamoby-archive@odin.ietf.org; Tue, 4 Nov 2003 13:18:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH5kg-0008Nw-W3 for seamoby-web-archive@optimus.ietf.org; Tue, 04 Nov 2003 13:18: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 NAA26016 for ; Tue, 4 Nov 2003 13:17:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AH5ke-00027z-00 for seamoby-web-archive@ietf.org; Tue, 04 Nov 2003 13:18:00 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AH5ke-00027m-00 for seamoby-web-archive@ietf.org; Tue, 04 Nov 2003 13:18:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH5ke-0008Mi-NX; Tue, 04 Nov 2003 13:18:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH5kU-0008MH-13 for seamoby@optimus.ietf.org; Tue, 04 Nov 2003 13:17:50 -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 NAA25991 for ; Tue, 4 Nov 2003 13:17:36 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AH5kS-000275-00 for seamoby@ietf.org; Tue, 04 Nov 2003 13:17:48 -0500 Received: from tokyo.netlab.nec.de ([195.37.70.2] helo=tokyo.ccrle.nec.de) by ietf-mx with esmtp (Exim 4.12) id 1AH5kR-00026V-00 for seamoby@ietf.org; Tue, 04 Nov 2003 13:17:47 -0500 Received: from venus.office (venus.office [10.1.1.11]) by tokyo.ccrle.nec.de (8.12.10/8.12.9) with ESMTP id hA4IH4p7060027 for ; Tue, 4 Nov 2003 19:17:04 +0100 (CET) Received: from ccrle.nec.de (liebsch.office [10.1.1.153]) by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 956ADBFEB2 for ; Tue, 4 Nov 2003 18:40:28 +0100 (CET) Message-ID: <3FA7ED1F.6040209@ccrle.nec.de> Date: Tue, 04 Nov 2003 19:17:03 +0100 From: Marco Liebsch Organization: NEC Europe Ltd. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Seamoby Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.35 Content-Transfer-Encoding: 7bit Subject: [Seamoby] CARD: Proposal on remaining issues 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 Based on today's telephone conference and discussion about remaining technical issues, we found and agreed on the following solutions taken as a proposal to the WG. Please find the summarized proposal below. If you have any concerns or comments, please indicate. Issue: "Handling of sequence numbers" The proposal is to use the same sequence numbers for resent CARD Request messages, increase the sequence number for new requests. Assumed a solicited CARD Reply is lost on its way back to the requesting MN, a MN's current AR must send the same CARD Reply again in case it receives a CARD Request carrying the same sequence number as the previous request. Issue: "Timeout and retransmission of signaling messages" The following values have been agreed on for the proposal: MN_AR_CARD_TIMEOUT: 1 sec. MN_AR_CARD_RETRIES: 5 AR_AR_CARD_TIMEOUT: 300 ms AR_AR_CARD_RETRIES: 2 Furthermore: Change CARD_RETRANSMISSION_INTERVAL (current draft) to CARD_REQUEST_RATE and set the value to 1 request/sec. Drop CARD_MAX_RETRIES (as specified in the current draft). Issue: "Storing Sequence numbers in AR's CAR tables" Add a paragraph in section "Conceptual data structures", which indicates, that MNs and ARs must maintain entries for sequence numbers of latest received unsolicited CARD Reply messages. Furthermore, MNs and ARs, in case of receiving both solicited and unsolicited CARD Reply messages, should always consider the latest/newest info received as valid info. Issue: "Preferences and Requirements sub-option" Keep both sub-options and use the recently proposed rule to fill preferred capabilities' attributes into the Preferences sub-option. Issue: "Request IANA for L2 type IDs" Change example types to be included with the CARD spec to IEEE802.11a, IEEE802.11b, IEEE802.11g. Other technologies' types should be requested in the future outside the scope of the CARD spec, but controlled by IANA and dedicated experts. Issue: "Address length in L2-ID sub-options" Here, two opinions exist: Either, use the L2-type to specify the length of the subsequent L2-ID, or add a further length field to the sub-option, which indicates the real length of the subsequent L2-ID (more flexible, but will have 2 length fields in the sub-option; one for the entire option including padding bytes, another one for the L2-ID only). Comments? marco _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Tue Nov 4 14:15:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28807 for ; Tue, 4 Nov 2003 14:15:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH6dt-000515-Ox for seamoby-archive@odin.ietf.org; Tue, 04 Nov 2003 14:15:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA4JF5iJ019275 for seamoby-archive@odin.ietf.org; Tue, 4 Nov 2003 14:15:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH6dt-00050o-E8 for seamoby-web-archive@optimus.ietf.org; Tue, 04 Nov 2003 14:15: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 OAA28787 for ; Tue, 4 Nov 2003 14:14:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AH6dq-00038Q-00 for seamoby-web-archive@ietf.org; Tue, 04 Nov 2003 14:15:02 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AH6dq-00038N-00 for seamoby-web-archive@ietf.org; Tue, 04 Nov 2003 14:15:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH6dr-000505-Q6; Tue, 04 Nov 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 1AH6dI-0004yN-KC for seamoby@optimus.ietf.org; Tue, 04 Nov 2003 14:14: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 OAA28747 for ; Tue, 4 Nov 2003 14:14:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AH6dG-00037P-00 for seamoby@ietf.org; Tue, 04 Nov 2003 14:14:26 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AH6dF-00036N-00 for seamoby@ietf.org; Tue, 04 Nov 2003 14:14:25 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id hA4JDeM02559; Tue, 4 Nov 2003 11:13:40 -0800 X-mProtect: <200311041913> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.30.3, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdL0GEoh; Tue, 04 Nov 2003 11:13:37 PST Message-ID: <3FA7FB1F.1090601@iprg.nokia.com> Date: Tue, 04 Nov 2003 11:16:47 -0800 From: Vijay Devarapalli User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marco Liebsch CC: Seamoby Subject: Re: [Seamoby] CARD: Proposal on remaining issues References: <3FA7ED1F.6040209@ccrle.nec.de> In-Reply-To: <3FA7ED1F.6040209@ccrle.nec.de> Content-Type: text/plain; charset=us-ascii; format=flowed 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 Marco Liebsch wrote: > > Issue: "Timeout and retransmission of signaling messages" > The following values have been agreed on for the proposal: > > MN_AR_CARD_TIMEOUT: 1 sec. > MN_AR_CARD_RETRIES: 5 > AR_AR_CARD_TIMEOUT: 300 ms > AR_AR_CARD_RETRIES: 2 > > Furthermore: > Change CARD_RETRANSMISSION_INTERVAL (current draft) to > CARD_REQUEST_RATE and set the value to 1 request/sec. sorry, I missed the conference call, but why not make it 2 requests/sec? shouldnt break anything. from an earlier mail > the mobile node sends a request. within another > 200 ms, something changes (like the MN discovering a new AP with > a stronger signal). the mobile node now needs to send out > another CARD request for the new AP. the time gap between the two > requests would be just 200 seconds. waiting for a second before > you can enquire about this new AP is too long. Vijay _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Wed Nov 5 13:35:54 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16291 for ; Wed, 5 Nov 2003 13:35:54 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHSVE-0002iN-JW for seamoby-archive@odin.ietf.org; Wed, 05 Nov 2003 13:35:36 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA5IZaj0010431 for seamoby-archive@odin.ietf.org; Wed, 5 Nov 2003 13:35:36 -0500 Received: from [61.235.68.66] (helo=sss492.com) by optimus.ietf.org with smtp (Exim 4.20) id 1AHSVC-0002i3-Lh for seamoby-web-archive@optimus.ietf.org; Wed, 05 Nov 2003 13:35:35 -0500 From: =?gb2312?q?=D3=F2=C3=FB=BF=D5=BC=E4=CC=D8=BC=DB_?= Reply-To: sddd@ddd.com Subject: =?gb2312?q?=D3=F2=C3=FB=A1=A2=BF=D5=BC=E4=B6=BC=BD=B5=BC=DB=C1=CB=A3=AC=BB=B9=B2=BB=B8=CF=BF=EC=D7=F6=D2=BB=B8=F6=CD=F8=D5=BE?= Date: Thu, 06 Nov 2003 02:35:49 +0800 MIME-Version: 1.0 Content-Type: multipart/related; boundary="c4a768d2-db55-4b01-8184-c83ac434b39a" Message-Id: This is a multi-part message in MIME format --c4a768d2-db55-4b01-8184-c83ac434b39a Content-Type: text/html; charset=gb2312 Content-Transfer-Encoding: quoted-printable

=D0=E9=C4=E2=BF=D5=BC=E4=B4=F3=D3=C5=BB=DD=A3=AC= 199=D4=AA=BF=C9=D2=D4=BD=A8=D2=BB=B8=F6=CD=F8=D5=BE=A3=AC=B8=CF=BF=EC=B5=BDwww.0755sz.com=C9=EA=C7=EB=B0=C9=A3=AC=BB= =B9=D3=D0=BA=DC=B6=E0=BF=EE=C8=CE=C4=E3=D1=A1=D4=F1=A1=A3=CF=EA=C7=E9=C7=EB=B5= =E70755 26368636 EMAIL=A3=BAusa123678@yahoo.com.cn =BB=F2usa123678@hotmail.com

=D0=CD=BA=C5 =BF=D5=BC=E4=B4=F3=D0=A1 =D3=CA=CF=E4 =C1=AC=BD=D3 =BC=DB=B8=F1 =B1=B8=D7=A2
P199W0306D 200M =CB=CD10M 50 199=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
P= 199W0306R 50M =CB=CD10M 150 199=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
P199W0306C 150M =CB=CD10M 150 199=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
SPI99W0307C =BF=D5=BC=E4+=D3=CA= =CF=E4=B9=B260M=A3=A8=BF=C9=D2=D4=B7=D6=B8=EE 50 199=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
P299W0306D 200M =CB=CD100M 50 299=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
P299W0306R 50M =CB=CD50M 150 299=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
P299W0306C 150M =CB=CD50M 100 299=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
SP299W0307C =BF=D5=BC=E4+=D3=CA= =CF=E4=B9=B2150M=A3=A8=BF=C9=D2=D4=B7=D6=B8=EE 100 299=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
SB299W0307H =BF=D5=BC=E4+=D3=CA= =CF=E4=B9=B2150M=A3=A8=BF=C9=D2=D4=B7=D6=B8=EE 80 299=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
P399W0306D 400M 100M 50 399=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
P399W0306R 100M 50M 150 399=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
P399W0306C 250M 100M 100 399=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
SP399W0307C =BF=D5=BC=E4+=D3=CA= =CF=E4=B9=B2250M=A3=A8=BF=C9=D2=D4=B7=D6=B8=EE 100 399=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
SB399W0307H =BF=D5=BC=E4+=D3=CA= =CF=E4=B9=B2220M=A3=A8=BF=C9=D2=D4=B7=D6=B8=EE 80 399=D4=AA =CB=CD=B9=FA=BC=CA=D3=F2=C3=FB=D2= =BB=B8=F6
--c4a768d2-db55-4b01-8184-c83ac434b39a-- From exim@www1.ietf.org Thu Nov 6 17:22:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04937 for ; Thu, 6 Nov 2003 17:22: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 1AHsVw-0001CC-3q for seamoby-archive@odin.ietf.org; Thu, 06 Nov 2003 17:22:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6MM4HH004592 for seamoby-archive@odin.ietf.org; Thu, 6 Nov 2003 17:22:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHsVv-0001Bz-To for seamoby-web-archive@optimus.ietf.org; Thu, 06 Nov 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 RAA04911 for ; Thu, 6 Nov 2003 17:21:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHsVt-0001tz-00 for seamoby-web-archive@ietf.org; Thu, 06 Nov 2003 17:22:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AHsVt-0001ts-00 for seamoby-web-archive@ietf.org; Thu, 06 Nov 2003 17:22:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHsVt-0001BK-JP; Thu, 06 Nov 2003 17:22:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHsVk-0001B2-3m for seamoby@optimus.ietf.org; Thu, 06 Nov 2003 17:21:52 -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 RAA04902 for ; Thu, 6 Nov 2003 17:21:38 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHsVh-0001tj-00 for seamoby@ietf.org; Thu, 06 Nov 2003 17:21:49 -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 1AHsVh-0001tg-00 for seamoby@ietf.org; Thu, 06 Nov 2003 17:21:49 -0500 Message-ID: <034401c3a4b4$6b6c8b10$9f6015ac@dclkempt40> From: "James Kempf" To: Date: Thu, 6 Nov 2003 14:22:09 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Seamoby] WG Last Call on draft-ietf-seamoby-ctp-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 Since draft-ietf-seamoby-ctp-05.txt seems to have made it into the drafts directory, WG Last Call for the CTP draft starts now and ends on Nov. 27 (and extra week to accommodate the IETF meeting). Please read the draft and send any final comments. The plan is for this draft to be the final one before submitting to the IESG for publication as Experimental, unless there are major comments during this last call period. jak _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Nov 7 04:47:28 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07955 for ; Fri, 7 Nov 2003 04:47:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AI3Cv-000448-3L for seamoby-archive@odin.ietf.org; Fri, 07 Nov 2003 04:47:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA79l7Mm015606 for seamoby-archive@odin.ietf.org; Fri, 7 Nov 2003 04:47:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AI3Ct-00043X-0a for seamoby-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 04:47: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 EAA07939 for ; Fri, 7 Nov 2003 04:46:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AI3Cp-0002Bf-00 for seamoby-web-archive@ietf.org; Fri, 07 Nov 2003 04:47:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AI3Cp-0002BU-00 for seamoby-web-archive@ietf.org; Fri, 07 Nov 2003 04:47:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AI3Cq-00042H-8Z; Fri, 07 Nov 2003 04:47:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AI3Cd-00041V-Rl for seamoby@optimus.ietf.org; Fri, 07 Nov 2003 04:46:51 -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 EAA07924 for ; Fri, 7 Nov 2003 04:46:40 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AI3Ca-0002B5-00 for seamoby@ietf.org; Fri, 07 Nov 2003 04:46:48 -0500 Received: from smtp2.clb.oleane.net ([213.56.31.18]) by ietf-mx with esmtp (Exim 4.12) id 1AI3CZ-0002Au-00 for seamoby@ietf.org; Fri, 07 Nov 2003 04:46:47 -0500 Received: from oleane ([194.250.212.114]) by smtp2.clb.oleane.net with SMTP id hA79kHfo016962 for ; Fri, 7 Nov 2003 10:46:17 +0100 Message-ID: <02bc01c3a514$835ac9c0$0601a8c0@www.oleane.com> From: "Peter Lewis" To: Date: Fri, 7 Nov 2003 10:50:01 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_02B9_01C3A51C.E4BA7C80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Subject: [Seamoby] WiMAX Summit 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: , C'est un message de format MIME en plusieurs parties. ------=_NextPart_000_02B9_01C3A51C.E4BA7C80 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Are WiMAX and WiFi complementary (local vs. metropolitan area = networking)?=20 When and how will WiMAX evolve towards mobility?=20 Can WiMAX be considered as a migration path to 4G?=20 How is addressed the interoperability challenge?=20 These questions, among others, will be addressed during the WiMAX = Summit, to be held in Paris on May 25 to 28, 2004.=20 A call for papers has been launched on-line at: http://www.upperside.fr/wimax04/wimax04intro.htm ------=_NextPart_000_02B9_01C3A51C.E4BA7C80 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Are WiMAX and WiFi complementary (local vs. = metropolitan=20 area networking)?
When and how will WiMAX evolve towards = mobility?=20
Can WiMAX be considered as a migration path to 4G?
How is = addressed the=20 interoperability challenge?

These questions, among others, will = be=20 addressed during the WiMAX = Summit, to=20 be held in Paris on May 25 to 28, 2004. =

A=20 call for papers has been launched on-line at:
http://www.uppe= rside.fr/wimax04/wimax04intro.htm
------=_NextPart_000_02B9_01C3A51C.E4BA7C80-- _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Nov 7 12:37:16 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26091 for ; Fri, 7 Nov 2003 12:37:15 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIAXZ-0002ql-1R for seamoby-archive@odin.ietf.org; Fri, 07 Nov 2003 12:36:58 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7HavuW010949 for seamoby-archive@odin.ietf.org; Fri, 7 Nov 2003 12:36:57 -0500 Received: from [218.58.166.253] (helo=163.com) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIAXW-0002p0-Bj for seamoby-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 12:36:56 -0500 From: "san mao " Subject: =?GB2312?B?xOO6wyDF89PR?= To: seamoby-web-archive@optimus.ietf.org Content-Type: text/plain;charset="GB2312" Reply-To: shandong@www1.ietf.org Date: Sat, 8 Nov 2003 01:38:08 +0800 X-Priority: 3 X-Mailer: Foxmail 4.1 [cn] Message-Id: 想知道一个月怎样赚十万吗？一个赚钱的成倍增长系统。 看电影，赚钱两不误 请访问: http://asdis001.126.com QQ:44895573 有详细内容(中文版): 相信你也能做到。 进入上面网站(复制,粘贴到地址到地址栏或直接点击） 如果你有兴趣看完,你就会知道它是一套不看人脸色的赚钱系统,是一套把命运掌握在自 已手中的赚钱系统。 我要告诉你的是这套系统 的优越性在于 “所付即所得,只要你付出,你每天都能收到钱。 你付出一份,能得到十万份的回报。 　　　　如果想加入,那么就请详细看看网站下方的会员规则和发展理念，那里有详细资料。 　 成功只青睐于有胆识的人! From exim@www1.ietf.org Sun Nov 9 08:40:38 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28233 for ; Sun, 9 Nov 2003 08:40:37 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AIpng-0002mX-Ac for seamoby-archive@odin.ietf.org; Sun, 09 Nov 2003 08:40:20 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA9DeKUd010687 for seamoby-archive@odin.ietf.org; Sun, 9 Nov 2003 08:40:20 -0500 Received: from [219.234.29.195] (helo=02) by optimus.ietf.org with smtp (Exim 4.20) id 1AIpnd-0002ku-Hw for seamoby-web-archive@optimus.ietf.org; Sun, 09 Nov 2003 08:40:20 -0500 From: "赠送" To: Subject: 11月20日前免费注册参加最新的网上赚钱网 Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Date: Sun, 9 Nov 2003 21:38:37 +0800 X-Priority: 3 X-Mailer: JiXing mailer V1.75 Design By JohnnieHuang Message-Id: 朋友，你好，11月20日前注册"一诺网信息"网站,我为你免费激活，快快行动吧： http://yn888.8126.net/888/soho/index.asp?user=hao 平常参加得50元 所有11月20日前注册的会员我全部会为你免费开通！ 请站长抓紧时间尽快发展您的下级！11月20日以后只要你下级发展一个付费的您就有10块的奖金！！！！ 这个消息请不要透露给没有注册的人！ 现在我全部为你免费打开！ 欢迎光临 03-11-9 21:38:02 ============================邮件内容与以下文字无关============================= 优联网络 http://www.chinamysql.com 专业提供各类虚拟主机，不满意可获退款。 强势套餐：100M主机送顶级域名，送10个10M企业油箱，加送20个二级域名，仅需318元/年！ 三龙证券投资 http://3long.sayba.com 为您提供专业理财服务。现在购买只需588元，赠送价值超过1800元的礼品！ 说吧网上商城 http://shop.sayba.com 全是厂商直销的新品或折上折的商品，是您网络购物的好去处！ 使用极星邮件群发，无须通过邮件服务器，直达对方邮箱，速度绝对一流！ 软件下载网址：http://www.lovexin.com，更多的超酷软件等你来下载哦！ From exim@www1.ietf.org Mon Nov 10 12:26:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01844 for ; Mon, 10 Nov 2003 12:26: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 1AJFnk-0003Td-1Q for seamoby-archive@odin.ietf.org; Mon, 10 Nov 2003 12:26:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAHQ8Mi013364 for seamoby-archive@odin.ietf.org; Mon, 10 Nov 2003 12:26:08 -0500 Received: from [218.5.192.246] (helo=yahoo.com) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJFnh-0003Sm-PU for seamoby-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 12:26:07 -0500 From: =?GB2312?B?0MLKvc34wue157uw?= Subject: =?GB2312?B?w+K30beit8WjrcrTxrW157uwv6rNqA==?= To: seamoby-web-archive@optimus.ietf.org Content-Type: text/plain;charset="GB2312" Reply-To: newsphotoe0o@yahoo.com Date: Tue, 11 Nov 2003 01:29:33 +0800 X-Priority: 3 X-Mailer: Microsoft Outlook Express 5.00.2919.6700 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 Wed Nov 12 11:46:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26712 for ; Wed, 12 Nov 2003 11:46:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJy84-0007PQ-9F for seamoby-archive@odin.ietf.org; Wed, 12 Nov 2003 11:46:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hACGk4BD028474 for seamoby-archive@odin.ietf.org; Wed, 12 Nov 2003 11:46:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJy84-0007PB-5y for seamoby-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 11:46: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 LAA26668 for ; Wed, 12 Nov 2003 11:45:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJy82-00022T-00 for seamoby-web-archive@ietf.org; Wed, 12 Nov 2003 11:46:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AJy82-00022P-00 for seamoby-web-archive@ietf.org; Wed, 12 Nov 2003 11:46:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJy81-0007OI-75; Wed, 12 Nov 2003 11:46:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJy7k-0007LY-Dy for seamoby@optimus.ietf.org; Wed, 12 Nov 2003 11:45: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 LAA26646 for ; Wed, 12 Nov 2003 11:45:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJy7j-00021A-00 for seamoby@ietf.org; Wed, 12 Nov 2003 11:45:43 -0500 Received: from herculanum.int-evry.fr ([157.159.11.15]) by ietf-mx with esmtp (Exim 4.12) id 1AJy7i-0001yP-00 for seamoby@ietf.org; Wed, 12 Nov 2003 11:45:42 -0500 Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20]) by herculanum.int-evry.fr (Postfix) with ESMTP id E1F3234C0A for ; Wed, 12 Nov 2003 17:38:05 +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 2D3D33F427 for ; Wed, 12 Nov 2003 17:37:46 +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 M2003111217374515952 for ; Wed, 12 Nov 2003 17:37:45 +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 AF8B63F4AC for ; Wed, 12 Nov 2003 17:36:49 +0100 (CET) Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1AJxxz-000FvQ-63 for ; Wed, 12 Nov 2003 17:35:39 +0100 Date: Wed, 12 Nov 2003 17:35:39 +0100 From: Julien Bournelle To: seamoby@ietf.org Message-ID: <20031112163539.GN55178@ipv6-5.int-evry.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Seamoby] CTP - How to handle bad MN's authorization Token ? 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 all, 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 ? -- julien.bournelle@int-evry.fr _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Thu Nov 13 04:10:34 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17707 for ; Thu, 13 Nov 2003 04:10:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKDUU-0004IN-Jd for seamoby-archive@odin.ietf.org; Thu, 13 Nov 2003 04:10:15 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAD9AEAa016506 for seamoby-archive@odin.ietf.org; Thu, 13 Nov 2003 04:10:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKDUS-0004I9-Fx for seamoby-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 04:10: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 EAA17669 for ; Thu, 13 Nov 2003 04:10:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKDUP-0001KH-00 for seamoby-web-archive@ietf.org; Thu, 13 Nov 2003 04:10:09 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKDUP-0001KE-00 for seamoby-web-archive@ietf.org; Thu, 13 Nov 2003 04:10:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKDUJ-0004HK-L6; Thu, 13 Nov 2003 04:10:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKDTo-0004DM-2I for seamoby@optimus.ietf.org; Thu, 13 Nov 2003 04:09:32 -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 EAA17642 for ; Thu, 13 Nov 2003 04:09:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKDTl-0001JO-00 for seamoby@ietf.org; Thu, 13 Nov 2003 04:09:29 -0500 Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx with esmtp (Exim 4.12) id 1AKDTk-0001J5-00 for seamoby@ietf.org; Thu, 13 Nov 2003 04:09:28 -0500 Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16]) by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id hAD98s421135 for ; Thu, 13 Nov 2003 10:08:54 +0100 Received: from enst-bretagne.fr (dhcp75 [193.52.74.175]) by courrier.rennes.enst-bretagne.fr (8.11.6p2/8.11.6) with ESMTP id hAD98sM17080 for ; Thu, 13 Nov 2003 10:08:54 +0100 (MET) Message-ID: <3FB349CE.5090403@enst-bretagne.fr> Date: Thu, 13 Nov 2003 10:07:26 +0100 From: Lucian Suciu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: fr-fr, fr MIME-Version: 1.0 To: seamoby@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr Content-Transfer-Encoding: 7bit Subject: [Seamoby] CTP - a few comments on draft-ietf-seamoby-ctp-05... 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 All, I put below a few comments on draft-ietf-seamoby-ctp-05, both editorial and technical. 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. Technical: Can we steal two bits from 'Researved' "area" and use them for a 'V' flag within the Context Transfer Activate Acknowledge (CTAA) Message? The same thing for Context Transfer Cancel (CTC) Message... Is the 'A' flag within CTD Message linked in some way to 'A' flag within CTAR Message? E.g., if the MN has set the 'A' to '1' in CTAR, then the pAR should (or must) also set the 'A' to '1' within the CTD Message? However, the definition for 'A' flag is the same in both messages... (i.e., "the MN requests an acknowledgement"??). Furthermore, does an 'A' flag within the CT Request Message sound totally inappropriate for the time being (i.e., it might be in relation to the 'A' flag received by the nAR within CTAR Message)? Thank you. Have a good day, Lucian Suciu _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Thu Nov 13 11:18:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05519 for ; Thu, 13 Nov 2003 11:18:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKKAW-0000Es-56 for seamoby-archive@odin.ietf.org; Thu, 13 Nov 2003 11:18:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hADGI402000914 for seamoby-archive@odin.ietf.org; Thu, 13 Nov 2003 11:18:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKKAW-0000Ef-0i for seamoby-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 11:18: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 LAA05511 for ; Thu, 13 Nov 2003 11:17:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKKAV-00005k-00 for seamoby-web-archive@ietf.org; Thu, 13 Nov 2003 11:18:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKKAU-00005h-00 for seamoby-web-archive@ietf.org; Thu, 13 Nov 2003 11:18:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKKAT-0000EL-Ps; Thu, 13 Nov 2003 11:18:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKKAQ-0000Dl-J6 for seamoby@optimus.ietf.org; Thu, 13 Nov 2003 11:17:58 -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 LAA05492 for ; Thu, 13 Nov 2003 11:17:46 -0500 (EST) From: john.loughney@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKKAP-00005T-00 for seamoby@ietf.org; Thu, 13 Nov 2003 11:17:57 -0500 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1AKKAO-00005Q-00 for seamoby@ietf.org; Thu, 13 Nov 2003 11:17:57 -0500 Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hADGHu603009 for ; Thu, 13 Nov 2003 18:17:56 +0200 (EET) Received: from esebh004.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Thu, 13 Nov 2003 18:17:55 +0200 Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Thu, 13 Nov 2003 18:17:55 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Seamoby] CTP - How to handle bad MN's authorization Token ? Date: Thu, 13 Nov 2003 18:17:55 +0200 Message-ID: Thread-Topic: [Seamoby] CTP - How to handle bad MN's authorization Token ? Thread-Index: AcOpPIPaqDoCffNJTSSXf42o0CcxaAAxQlWw To: , X-OriginalArrivalTime: 13 Nov 2003 16:17:55.0445 (UTC) FILETIME=[B1FEA250:01C3AA01] Content-Transfer-Encoding: quoted-printable 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 Julien, thanks for the questions - I'm going to ask Charlie or Rajeev to try to answer this, as they have been playing with implementations of this and I'd like to know what solution is reasonable. John > -----Original Message----- > From: seamoby-admin@ietf.org=20 > [mailto:seamoby-admin@ietf.org]On Behalf Of > ext Julien Bournelle > Sent: 12 November, 2003 18:36 > To: seamoby@ietf.org > Subject: [Seamoby] CTP - How to handle bad MN's authorization Token ? >=20 >=20 > hi all, >=20 > In case nAR requests the transfer by a CTR message, the pAR=20 > must verify > the MN's authorization token. If this token is unvalid, what=20 > do we do ? >=20 > Possible solutions: >=20 > - 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. >=20 > others ? >=20 > --=20 > julien.bournelle@int-evry.fr >=20 > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby >=20 _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Thu Nov 13 14:14:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13516 for ; Thu, 13 Nov 2003 14:14: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 1AKMup-0005J4-A7 for seamoby-archive@odin.ietf.org; Thu, 13 Nov 2003 14:14:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hADJE3HX020392 for seamoby-archive@odin.ietf.org; Thu, 13 Nov 2003 14:14:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKMup-0005Io-29 for seamoby-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 14:14: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 OAA13478 for ; Thu, 13 Nov 2003 14:13:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKMum-000378-00 for seamoby-web-archive@ietf.org; Thu, 13 Nov 2003 14:14:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKMum-000374-00 for seamoby-web-archive@ietf.org; Thu, 13 Nov 2003 14:14:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKMun-0005ID-6W; Thu, 13 Nov 2003 14:14:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKMu7-0005Dy-7J for seamoby@optimus.ietf.org; Thu, 13 Nov 2003 14:13: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 OAA13388 for ; Thu, 13 Nov 2003 14:13:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKMu4-00036P-00 for seamoby@ietf.org; Thu, 13 Nov 2003 14:13:16 -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 1AKMu3-00036H-00 for seamoby@ietf.org; Thu, 13 Nov 2003 14:13:15 -0500 Message-ID: <036701c3aa1a$3cf4e5a0$85818182@dclkempt40> From: "James Kempf" To: Date: Thu, 13 Nov 2003 11:13:29 -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: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit ----- Original Message ----- From: "The IESG" To: ; Sent: Thursday, November 13, 2003 9:13 AM Subject: ID Tracker State Update Notice: draft-ietf-seamoby-mobility-terminology > 'State Changes to IESG Evaluation from AD Evaluation 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 From exim@www1.ietf.org Fri Nov 14 10:21:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15276 for ; Fri, 14 Nov 2003 10:21: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 1AKfkv-0005tr-EJ for seamoby-archive@odin.ietf.org; Fri, 14 Nov 2003 10:21:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEFL5iP022678 for seamoby-archive@odin.ietf.org; Fri, 14 Nov 2003 10:21:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfkv-0005th-B1 for seamoby-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 10:21: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 KAA15245 for ; Fri, 14 Nov 2003 10:20:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKfkt-0006th-00 for seamoby-web-archive@ietf.org; Fri, 14 Nov 2003 10:21:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AKfks-0006te-00 for seamoby-web-archive@ietf.org; Fri, 14 Nov 2003 10:21:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfkr-0005sq-79; Fri, 14 Nov 2003 10:21:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AKfk5-0005rl-BZ for seamoby@optimus.ietf.org; Fri, 14 Nov 2003 10:20: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 KAA15177 for ; Fri, 14 Nov 2003 10:19:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKfk3-0006s0-00 for seamoby@ietf.org; Fri, 14 Nov 2003 10:20:11 -0500 Received: from tokyo.netlab.nec.de ([195.37.70.2] helo=tokyo.ccrle.nec.de) by ietf-mx with esmtp (Exim 4.12) id 1AKfk2-0006rd-00 for seamoby@ietf.org; Fri, 14 Nov 2003 10:20:10 -0500 Received: from tokyo.ccrle.nec.de (localhost [127.0.0.1]) by tokyo.ccrle.nec.de (8.12.10/8.12.9) with ESMTP id hAEFJZCx019151 for ; Fri, 14 Nov 2003 16:19:35 +0100 (CET) Received: (from defang@localhost) by tokyo.ccrle.nec.de (8.12.10/8.12.8/Submit) id hAEFJWmD019147 for ; Fri, 14 Nov 2003 16:19:32 +0100 (CET) X-Authentication-Warning: tokyo.ccrle.nec.de: defang set sender to using -f Received: from venus.office (venus.office [10.1.1.11]) by pluto.office (8.12.9/8.12.9+MIMEDefang) with ESMTP id hAEFJVCx019146; Fri, 14 Nov 2003 16:19:32 +0100 (CET) Received: from ccrle.nec.de (liebsch.office [10.1.1.153]) by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 14A3DA5F2E; Fri, 14 Nov 2003 16:19:31 +0100 (CET) Message-ID: <3FB4F282.4040705@ccrle.nec.de> Date: Fri, 14 Nov 2003 16:19:30 +0100 From: Marco Liebsch Organization: NEC Europe Ltd. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vijay Devarapalli Cc: Seamoby Subject: Re: [Seamoby] CARD: Proposal on remaining issues References: <3FA7ED1F.6040209@ccrle.nec.de> <3FA7FB1F.1090601@iprg.nokia.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.35 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 If there are no objections with regard to allowing 2 requests per second, we can take this over. Any comments? marco Vijay Devarapalli wrote: > Marco Liebsch wrote: > >> >> Issue: "Timeout and retransmission of signaling messages" >> The following values have been agreed on for the proposal: >> >> MN_AR_CARD_TIMEOUT: 1 sec. >> MN_AR_CARD_RETRIES: 5 >> AR_AR_CARD_TIMEOUT: 300 ms >> AR_AR_CARD_RETRIES: 2 >> >> Furthermore: >> Change CARD_RETRANSMISSION_INTERVAL (current draft) to >> CARD_REQUEST_RATE and set the value to 1 request/sec. > > > sorry, I missed the conference call, but why not make it > 2 requests/sec? shouldnt break anything. > > from an earlier mail > >> the mobile node sends a request. within another >> 200 ms, something changes (like the MN discovering a new AP with >> a stronger signal). the mobile node now needs to send out >> another CARD request for the new AP. the time gap between the two >> requests would be just 200 seconds. waiting for a second before >> you can enquire about this new AP is too long. > > > Vijay > _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Tue Nov 18 04:24:29 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11447 for ; Tue, 18 Nov 2003 04:24:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AM25h-0003lm-Vy for seamoby-archive@odin.ietf.org; Tue, 18 Nov 2003 04:24:10 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAI9O9R5014491 for seamoby-archive@odin.ietf.org; Tue, 18 Nov 2003 04:24:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AM25g-0003lK-9z for seamoby-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 04:24:08 -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 EAA11410 for ; Tue, 18 Nov 2003 04:23:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AM25c-00017j-00 for seamoby-web-archive@ietf.org; Tue, 18 Nov 2003 04:24:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AM25c-00017f-00 for seamoby-web-archive@ietf.org; Tue, 18 Nov 2003 04:24:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AM25b-0003kb-Sj; Tue, 18 Nov 2003 04:24:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AM24z-0003jW-1A for seamoby@optimus.ietf.org; Tue, 18 Nov 2003 04:23:25 -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 EAA11385 for ; Tue, 18 Nov 2003 04:23:12 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AM24w-000178-00 for seamoby@ietf.org; Tue, 18 Nov 2003 04:23:22 -0500 Received: from smtp6.clb.oleane.net ([213.56.31.26]) by ietf-mx with esmtp (Exim 4.12) id 1AM24v-00016Z-00 for seamoby@ietf.org; Tue, 18 Nov 2003 04:23:21 -0500 Received: from oleane ([194.250.212.114]) by smtp6.clb.oleane.net with SMTP id hAI9Mp6f001232 for ; Tue, 18 Nov 2003 10:22:51 +0100 Message-ID: <014f01c3adb6$2525e740$0601a8c0@www.oleane.com> From: "Peter Lewis" To: Date: Tue, 18 Nov 2003 10:27:10 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_014C_01C3ADBE.868D3B20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Subject: [Seamoby] 2004 WiFi Voice Conference 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: , C'est un message de format MIME en plusieurs parties. ------=_NextPart_000_014C_01C3ADBE.868D3B20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The 2004 WiFi Voice Conference will stand in Paris on May 25 to 28, = 2004.=20 The call for papers dead line has been extended until December 15, 2003. = Get more details at: http://www.upperside.fr/wifivoice04/wifivoice04intro.htm We also remind you that registration is still open to the New Mobile = Technologies Forum (UWB, IPCN and IPv6 Mobile sessions) at: http://www.upperside.fr/newmobtech/newmobtech03intro.htm ------=_NextPart_000_014C_01C3ADBE.868D3B20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
The 2004 WiFi Voice=20 Conference will stand in Paris on May 25 to=20 28, 2004. 
The call for papers dead line has been = extended until=20 December 15, 2003.
Get more details at:
http://= www.upperside.fr/wifivoice04/wifivoice04intro.htm
 
We also remind you that registration is still open to the New Mobile Technologies Forum (UWB, IPCN and IPv6 = Mobile=20 sessions) at:
http://= www.upperside.fr/newmobtech/newmobtech03intro.htm
<= /DIV>
 
------=_NextPart_000_014C_01C3ADBE.868D3B20-- _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Tue Nov 18 17:42:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22457 for ; Tue, 18 Nov 2003 17:42:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMEXv-0006S7-KM for seamoby-archive@odin.ietf.org; Tue, 18 Nov 2003 17:42:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAIMg74l024802 for seamoby-archive@odin.ietf.org; Tue, 18 Nov 2003 17:42:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMEXv-0006Rx-Gr for seamoby-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 17:42: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 RAA22443 for ; Tue, 18 Nov 2003 17:41:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMEXs-0001En-00 for seamoby-web-archive@ietf.org; Tue, 18 Nov 2003 17:42:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMEXs-0001Eg-00 for seamoby-web-archive@ietf.org; Tue, 18 Nov 2003 17:42:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMEXo-0006RH-Uw; Tue, 18 Nov 2003 17:42:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMEXe-0006Qp-QN for seamoby@optimus.ietf.org; Tue, 18 Nov 2003 17:41:50 -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 RAA22382 for ; Tue, 18 Nov 2003 17:41:37 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMEXc-0001E5-00 for seamoby@ietf.org; Tue, 18 Nov 2003 17:41:48 -0500 Received: from mail2.it.kth.se ([130.237.212.132]) by ietf-mx with esmtp (Exim 4.12) id 1AMEXb-0001Du-00 for seamoby@ietf.org; Tue, 18 Nov 2003 17:41:47 -0500 Received: from it.kth.se (ripper.it.kth.se [130.237.212.25]) by mail2.it.kth.se (8.11.6p2/8.11.6) with ESMTP id hAIMfdk07837 for ; Tue, 18 Nov 2003 23:41:40 +0100 (MET) Message-Id: <200311182241.hAIMfdk07837@mail2.it.kth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: seamoby@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Tue, 18 Nov 2003 23:42:29 +0100 From: Jon-Olov Vatn Content-Transfer-Encoding: quoted-printable Subject: [Seamoby] CARD and multiple ARs per AP? 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! 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?) 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. 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 From exim@www1.ietf.org Thu Nov 20 13:32:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17592 for ; Thu, 20 Nov 2003 13:32: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 1AMtb4-0007hH-SI for seamoby-archive@odin.ietf.org; Thu, 20 Nov 2003 13:32:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKIW6oY029581 for seamoby-archive@odin.ietf.org; Thu, 20 Nov 2003 13:32:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMtb4-0007h2-Oh for seamoby-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 13:32: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 NAA17566 for ; Thu, 20 Nov 2003 13:31:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMtb2-000036-00 for seamoby-web-archive@ietf.org; Thu, 20 Nov 2003 13:32:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMtb2-000032-00 for seamoby-web-archive@ietf.org; Thu, 20 Nov 2003 13:32:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMtb0-0007g7-7X; Thu, 20 Nov 2003 13:32:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMtap-0007fk-IQ for seamoby@optimus.ietf.org; Thu, 20 Nov 2003 13:31:51 -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 NAA17547 for ; Thu, 20 Nov 2003 13:31:38 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMtan-00002Y-00 for seamoby@ietf.org; Thu, 20 Nov 2003 13:31:49 -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 1AMtam-00002V-00 for seamoby@ietf.org; Thu, 20 Nov 2003 13:31:48 -0500 Message-ID: <0e3001c3af94$9bc9f370$956015ac@dclkempt40> From: "James Kempf" To: Date: Thu, 20 Nov 2003 10:32:09 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Seamoby] WG 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, Marco and Ajoy have released a new version of the CARD draft including all the comments from the Review Board and WG members during the previous last call. Pat and I would like people to take a final look and send comments, prior to Dec. 5 if they find anything that should be changed. The draft is at: http://www.ccrle.nec.de/I-D/draft-ietf-seamoby-card-protocol-05.txt Please don't reopen any issues that have already been decided. The issues list is at: https://roundup.machshav.com/seamoby/index Thanx. jak _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Thu Nov 20 18:27:53 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07677 for ; Thu, 20 Nov 2003 18:27: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 1AMyD3-0005Gx-Hm for seamoby-archive@odin.ietf.org; Thu, 20 Nov 2003 18:27:37 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKNRb9W020263 for seamoby-archive@odin.ietf.org; Thu, 20 Nov 2003 18:27:37 -0500 Received: from [218.242.166.14] (helo=plasticsurgery.com) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMyCz-0005Gh-Nw for seamoby-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 18:27:34 -0500 From: "plasticsurgery@plasticsurgery.com" Subject: =?GB2312?B?yc+6o7Ok1ffSvdS61fvQzs3iv8bW7M/+uqOyqcq/zfjJz9XvytI=?= To: seamoby-web-archive@optimus.ietf.org Content-Type: text/html;charset="GB2312" Reply-To: plasticsurgery@plasticsurgery.com Date: Fri, 21 Nov 2003 07:27:33 +0800 X-Priority: 4 X-Mailer: FoxMail 4.0 beta 2 [cn] Message-Id: 上海长征医院－整形美容中心－医生个人简介

网络诊室
有问必答
　
热点新闻
·上海第二军医大学附属长征医院介绍
·长征医院整形外科开展治疗范围
·长征医院整形外科介绍
·女性性器官整形，不必遮遮掩掩
·长征医院光子嫩肤美容效果良好
·再造修复阴茎阴道 中国整复列世界先进
·聚能震波吸脂技术；塑造美好体型的理想选择
·小耳畸形的福音：人工耳，假作真！
·一期阴茎再造术及阴茎粗长术
·长征医院整形外科摘除一巨型血管瘤
当前位置：首页>>专家门诊>>朱晓海(医生)的个人简介


　　朱晓海 [男，37岁]，博士，1990-7-1毕业于第二军医大学研究生院。留学英国UCL大学整形外科中心。
　　现工作于上海长征医院整形外科 ，主治医师、讲师。擅长脂肪抽吸，阴道、阴茎再造，小耳畸形整复，重睑术，隆鼻术，眼袋整形术，隆乳术，乳房缩小术，面部畸形整复，脂肪充填术，秃发修复，面形改变术、颧骨过高、下颌角肥大，皮瓣转移，显微外科，除皱术，处女膜修补等等。世界首创女变男变性手术一次性完成。每周二上午门诊。联系电话：02163220619
欢迎来到我的诊室！ email: zhuxiaohai@ hotmail.com 欢迎MSNmessenger联络 其余时间msn messenger联系 联系电话：021-63220619 门诊时间： 每周二上午门诊

基本信息：
 朱晓海， 整形外科 〔科〕医生。
现居住于 上海 ，电子邮件zhuxiaohai@hotmail.com。
于1990-7-1毕业于第二军医大学研究生院、留学英国，专业是脂肪抽吸，阴道、阴茎再造，小耳畸形整复，重睑术，隆鼻术，眼袋整形术，隆乳术，乳房缩小术，面部畸形整复，脂肪充填术，秃发修复，面形改变术、颧骨过高、下颌角肥大，皮瓣转移，显微外科，除皱术等。世界首创女变男变性手术一次性完成。每周二上午门诊。02163220619，最高学历是博士。
联系信息：
 详细住址是上海市南京西路500号，邮编：200003。
家庭电话：MSN Messenger。
单位电话：02163220619。
手机号码：13311773250。
Call号码：MSN Messenger。
其他电话：QQ:99421204。
目前在上海长征医院工作，主治医师、讲师，任主治医师、讲师。
个人介绍：
 朱晓海，男，1966年生，主治医师，讲师。1984年考入第二军医大学医学系六年制本科，1990毕业后即考取临床医学研究生，师从著名整形外科专家、中国变性之父何清濂教授，历经六年，于1996年研究生毕业，获得临床医学博士学位。2001年获得世界卫生组织奖学金，赴英国伦敦大学整形外科中心进行深造。回国后继续在临床开展工作，曾经完成首例女变男变性手术一期完成，手术包括乳房切除、子宫附件切除、阴道剥离、尿道前徙、阴茎再造，尿道吻接，阴蒂移位等，历经13小时，取得了圆满成功。主要擅长：脂肪抽吸，阴道再造，阴茎再造，先天性小耳畸形的耳廓再造，重睑术，隆鼻术，眼袋整形术，隆乳术，乳房缩小术，面部畸形人工材料充填术，脂肪充填术，秃发修复，颧骨过高、下颌角肥大修整术，皮瓣转移，显微外科，除皱术等。服务宗旨：全心全意为人民服务。MSN Messenger号为zhuxiaohai@hotmail.com
　
　
　
© 2001-2003 版权所有.上海第二军医大学附属长征医院整形激光美容中心
 　
住院 部 地址：
 上海市黄浦区凤阳路415号长征医院住院部18楼整形外科
门诊中心地址：
 上海市南京西路500号（南京西路和成都路南北高架 交界处）
门诊咨询电话：
 021-63220619- -○021-63610109－73383－－
E -mail ：
 czzxwk@etang.com
　
[ManageMent]
 　
From exim@www1.ietf.org Thu Nov 20 18:36:20 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07979 for ; Thu, 20 Nov 2003 18:36: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 1AMyLE-0006Ng-Oe for seamoby-archive@odin.ietf.org; Thu, 20 Nov 2003 18:36:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKNa4G7024522 for seamoby-archive@odin.ietf.org; Thu, 20 Nov 2003 18:36:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMyLE-0006NR-Kh for seamoby-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 18:36: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 SAA07954 for ; Thu, 20 Nov 2003 18:35:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMyLB-0006mK-00 for seamoby-web-archive@ietf.org; Thu, 20 Nov 2003 18:36:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMyLA-0006mD-00 for seamoby-web-archive@ietf.org; Thu, 20 Nov 2003 18:36:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMyLC-0006MS-Mh; Thu, 20 Nov 2003 18:36:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMyKC-0006Ks-C9 for seamoby@optimus.ietf.org; Thu, 20 Nov 2003 18:35:00 -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 SAA07909 for ; Thu, 20 Nov 2003 18:34:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMyK9-0006lM-00 for seamoby@ietf.org; Thu, 20 Nov 2003 18:34:57 -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 1AMyK8-0006lA-00 for seamoby@ietf.org; Thu, 20 Nov 2003 18:34:56 -0500 Message-ID: <0fc601c3afbe$f4e91970$956015ac@dclkempt40> From: "James Kempf" To: Date: Thu, 20 Nov 2003 15:35:18 -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: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit ID Tracker State Update Notice: draft-ietf-seamoby-mobility-terminology > 'State Changes to IESG Evaluation::Revised ID Needed from IESG Evaluation by Amy Vezza' > 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 From exim@www1.ietf.org Thu Nov 20 20:31:23 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12941 for ; Thu, 20 Nov 2003 20:31:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN08X-0004MD-MG for seamoby-archive@odin.ietf.org; Thu, 20 Nov 2003 20:31:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAL1V5C5016750 for seamoby-archive@odin.ietf.org; Thu, 20 Nov 2003 20:31:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN08X-0004M5-H4 for seamoby-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 20:31: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 UAA12815 for ; Thu, 20 Nov 2003 20:30:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN08V-00011r-00 for seamoby-web-archive@ietf.org; Thu, 20 Nov 2003 20:31:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AN08U-00011o-00 for seamoby-web-archive@ietf.org; Thu, 20 Nov 2003 20:31:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN08T-0004L3-Dj; Thu, 20 Nov 2003 20:31:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN07y-0004Ka-PG for seamoby@optimus.ietf.org; Thu, 20 Nov 2003 20:30:30 -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 UAA12791 for ; Thu, 20 Nov 2003 20:30:17 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN07w-000115-00 for seamoby@ietf.org; Thu, 20 Nov 2003 20:30:28 -0500 Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1AN07w-000112-00 for seamoby@ietf.org; Thu, 20 Nov 2003 20:30:28 -0500 Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.24; FreeBSD 4.9) id 1AN07u-000OLB-Sd; Fri, 21 Nov 2003 01:30:27 +0000 To: kempf@docomolabs-usa.com, seamoby@ietf.org Cc: pcalhoun@airespace.com Reply-To: mankin@psg.com Date: Thu, 20 Nov 2003 17:30:26 -0800 From: Allison Mankin Message-Id: Subject: [Seamoby] IESG Review: draft-ietf-seamoby-mobility-terminology (Re: ID Tracker State Update Notice) 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, Folks, Jim sent the state change, but caught the tracker before I got to enter any notes about today's telechat (TSV had a lot of documents). Here forthwith the report on the issues that came up on the document today. Now Jim can follow up on each point with the editors (if there are any ADish questions, don't hesitate to ask), and shepherd the document through a quick, limited new rev. One review to come before the revision, so wait for that before submitting revision - see 3. Is the next to last point in 4 below, the Ops-Dir review (source route including loose source routes) any problem? I think it should not be. Other than that item in 4, and 2, the points below do not challenge content. 1. Mostly the document is viewed as useful. It was noticed that both nemo and mipshop WGs are using it and view it as valuable. 2. Section 4.9 (user mobility etc.) is viewed as weak and* not needed for the mission the document. Because it touches on WGs such the geopriv (mentioning location tracking) and would be hard to get right even with much involvement by Apps WGs, the suggestion is for this section to be dropped. I think this is a very good suggestion. 3. Thomas Narten thought that a very focused single additional review by Henrik Levkowetz (co-Chair of the MIP4 WG) would dot the i's of inter-WG checking - Thomas thought there might be a few considerations seen from the Mobile IPv4 point of view that might come out of this review, but he asked Henrik for this review to be done expeditiously. Communicating with Henrik directly on this is correct, both to ask for it (Jim, it's expected before 10 days) and to interact on it. One last point: as discussed in the plenary, we could do better than to have such cross-checking review happen as late as IESG review - discussions started on this! But by the direct communication of Jim/editors with Henrik, let's keep it short in time. 4. A review from the Operations Directorate found the following small issues: - appendix B says it should list all the terms ("index"), but doesn't. [Note from AD: you could leave out Appendix B] - s/Author's Addresses/Authors' Addresses/ - to align better with the previous definition rephrase: In a vertical handover the mobile node's network interface to the access network changes. to: A handover in which the mobile node's network interface to the access network changes. (similar elsewhere as well..) ... - there is inconsistancy of capitalizing in sections 4.2, 4.5, 4.6, 4.9; the definitions should start with capital letters, like the rest of the spec. Clearly a result of merging definitions from someone else without properly integrating them? - section 4.6 starts by referring to Mobile Nodes, but the definitions at places describe Mobile Hosts. Suggest replacing the latter with MN's. Should probably grep -i for "host" or "MH" and check if these are valid..? - s/authentication/authenticate/ in sect 6, "Security context" Content: Source Route A source route from node A to node B is an ordered list of IP addresses, starting with the IP address of node A and ending with the IP address of the node B. Between A and B, the source route includes an ordered list of all the intermediate hops between A and B, as well as the interface index of the interface through which the packet should be transmitted to reach the next hop. ==> this is a stricter definition of Source Route than is usual. Normally SR includes ("Loose SR") the possibility to omit intermediate hops. Consider clarifying. ... "IP access address" is also a funny term, I probably wouldn't use it, but I have no more serious problems with it: IP access address An IP address (often dynamically allocated) which a node uses to designate its current point of attachment to the local network. The IP access address is typically to be distinguished from the mobile node's home address; in fact, while visiting a foreign network the former may be considered unsuitable for use as an end-point address by any but the most short-lived applications. Instead, the IP access address is typically used as the care-of address of the node. [Note from AD: OPS AD and I agree there is no action to take on this point, just FYI]. ------- End of Forwarded Message _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Nov 21 01:28:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19425 for ; Fri, 21 Nov 2003 01:28:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN4lw-00056y-0y for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 01:28:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAL6S343019642 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 01:28:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN4lv-00056j-Qn for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 01:28: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 BAA19403 for ; Fri, 21 Nov 2003 01:27:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN4ls-0004Vh-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 01:28:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AN4ls-0004Ve-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 01:28:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN4lt-000565-EM; Fri, 21 Nov 2003 01:28:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN4lG-00055j-6B for seamoby@optimus.ietf.org; Fri, 21 Nov 2003 01:27:22 -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 BAA19399 for ; Fri, 21 Nov 2003 01:27:09 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN4lD-0004VW-00 for seamoby@ietf.org; Fri, 21 Nov 2003 01:27:19 -0500 Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]) by ietf-mx with esmtp (Exim 4.12) id 1AN4lC-0004VI-00 for seamoby@ietf.org; Fri, 21 Nov 2003 01:27:18 -0500 Received: from huez (unknown [203.178.138.13]) by shonan.sfc.wide.ad.jp (Postfix) with ESMTP id 5CB0A5D14B; Fri, 21 Nov 2003 15:26:47 +0900 (JST) Date: Fri, 21 Nov 2003 15:24:12 +0900 From: Thierry Ernst To: mankin@psg.com Cc: kempf@docomolabs-usa.com, seamoby@ietf.org, pcalhoun@airespace.com Subject: Re: [Seamoby] IESG Review: draft-ietf-seamoby-mobility-terminology (Re: ID Tracker State Update Notice) Message-Id: <20031121152412.772557d1.ernst@sfc.wide.ad.jp> In-Reply-To: References: Organization: Keio University X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart_Fri__21_Nov_2003_15:24:12_+0900_082a3e68" 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: , This is a multi-part message in MIME format. --Multipart_Fri__21_Nov_2003_15:24:12_+0900_082a3e68 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, A few more minor comments, if it's not too late: - I would add "HoA" next to the term "Home Address" as this is done in Care-of Address (CoA). - a question concerning the term "link" was left unanswered. I attach the mail. I also had interest into clarifying. - a definition about what a subnet is may be useful since the term is used in many places in the document. - Mobile Node (MN) An IP node capable of changing its point of attachment to the network. A Mobile Node may or may not have forwarding functionality. -> I would add "MR" and "MH" in it: An IP node capable of changing its point of attachment to the network. A Mobile Node may either be a Mobile Host (no forwarding functionality) or a Mobile Router (forwarding functionality). or mention something about forwarding functionality in defs of MH and MR. - Mobile Host (MH) ".... A Mobile host..." -> capitalize Host. - Mobile Router (MR) In the middle paragraph, I would recommend to move the sentence about "ingress interface" and the one about "egress interfaces" as standalones definitions. Those 2 terms are extensively used in NEMO WG. The last paragraph shall be kept under the definition of MR. - Network mobility -> I would add something similar to first sentence of "host mobility" refers to the function of allowing an entire network to change its point of attachment to the network, and thus its reachability in the topology, without interrupting IP packet delivery to/from that mobile network. And, as long as we are using the term "function" into the definition of either "host mobility" or "network mobility", it would make sense to add the word "support" to both terms: -> replace "Host Mobility" with "Host Mobility Support" and "Network Mobility" with "Network Mobility Support". E.g: I don't have any support function on my laptop, so by doing host mobility I cannot maintain sessions. It's the fact that I do have "host mobility support" abilities that my sessions do not break. Thierry. --Multipart_Fri__21_Nov_2003_15:24:12_+0900_082a3e68 Content-Type: text/plain; name="link-definition.txt" Content-Disposition: attachment; filename="link-definition.txt" Content-Transfer-Encoding: 7bit Return-Path: Received: from shonan.sfc.wide.ad.jp ([unix socket]) by shonan.sfc.wide.ad.jp (Cyrus v2.0.17); Thu, 04 Sep 2003 20:30:50 +0900 X-Sieve: cmu-sieve 2.0 Return-Path: Received: from optimus.ietf.org (ietf-ops.ietf.org [132.151.6.20]) by shonan.sfc.wide.ad.jp (Postfix) with ESMTP id CA5D75D09D; Thu, 4 Sep 2003 20:30:49 +0900 (JST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19usJO-0002bd-3C; Thu, 04 Sep 2003 07:30:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19usIU-0002ai-RH for seamoby@optimus.ietf.org; Thu, 04 Sep 2003 07:29:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13020 for ; Thu, 4 Sep 2003 07:29:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19usIU-0002p6-00 for seamoby@ietf.org; Thu, 04 Sep 2003 07:29:06 -0400 Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx with smtp (Exim 4.12) id 19usIT-0002p2-00 for seamoby@ietf.org; Thu, 04 Sep 2003 07:29:05 -0400 Received: (qmail 30950 invoked for bounce); 4 Sep 2003 11:39:10 -0000 Received: from unknown (HELO clarinet.u-strasbg.fr) (montavont@unknown) by unknown with RC4-MD5 encrypted SMTP; 4 Sep 2003 11:39:10 -0000 Message-ID: <3F573E0C.5060103@clarinet.u-strasbg.fr> Date: Thu, 04 Sep 2003 22:28:44 +0900 From: Nicolas Montavont User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030727 Thunderbird/0.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: seamoby@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Seamoby] Question on link definition 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, I have a question about the definition of "link" in draft-ietf-seamoby-mobility-terminology-04.txt It is said: "A communication facility or physical medium that can sustain data communications between multiple network nodes, such as an Ethernet (simple or bridged). A link is the layer immediately below IP." As I undestand, the definition of link is not directly related to an IPv6 link. For example, consider the following example: One ethernet link where a router advertises a single IPv6 prefix, and an 802.11b access point connected to this ethernet link as illustrated here: AR ____ |__________________ | | AP Fixed node MN2 MN1 In this situation, is it right to say that : - there are 2 links and - there is one IPv6 link ? Thanks Regards, Nicolas _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby --Multipart_Fri__21_Nov_2003_15:24:12_+0900_082a3e68-- _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Nov 21 03:56:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05845 for ; Fri, 21 Nov 2003 03:56:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN75D-0007MA-0D for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 03:56:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAL8u6JA028278 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 03:56:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN75C-0007Lz-81 for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 03:56: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 DAA05827 for ; Fri, 21 Nov 2003 03:55:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN759-0006TD-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 03:56:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AN758-0006TA-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 03:56:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN759-0007Kq-G2; Fri, 21 Nov 2003 03:56:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN74C-0007Fs-ME for seamoby@optimus.ietf.org; Fri, 21 Nov 2003 03:55: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 DAA05772 for ; Fri, 21 Nov 2003 03:54:51 -0500 (EST) From: john.loughney@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN749-0006SI-00 for seamoby@ietf.org; Fri, 21 Nov 2003 03:55:01 -0500 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1AN748-0006SF-00 for seamoby@ietf.org; Fri, 21 Nov 2003 03:55:00 -0500 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAL8t1616032 for ; Fri, 21 Nov 2003 10:55:01 +0200 (EET) Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Fri, 21 Nov 2003 10:55:00 +0200 Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 21 Nov 2003 10:54:59 +0200 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Seamoby] CTP - How to handle bad MN's authorization Token ? X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Fri, 21 Nov 2003 10:54:59 +0200 Message-ID: Thread-Topic: [Seamoby] CTP - How to handle bad MN's authorization Token ? Thread-Index: AcOpPIPaqDoCffNJTSSXf42o0CcxaAG0JhJA To: Cc: X-OriginalArrivalTime: 21 Nov 2003 08:54:59.0884 (UTC) FILETIME=[2507D6C0:01C3B00D] Content-Transfer-Encoding: quoted-printable 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 Assigned issue 30. > -----Original Message----- > From: seamoby-admin@ietf.org=20 > [mailto:seamoby-admin@ietf.org]On Behalf Of > ext Julien Bournelle > Sent: 12 November, 2003 18:36 > To: seamoby@ietf.org > Subject: [Seamoby] CTP - How to handle bad MN's authorization Token ? >=20 >=20 > hi all, >=20 > In case nAR requests the transfer by a CTR message, the pAR=20 > must verify > the MN's authorization token. If this token is unvalid, what=20 > do we do ? >=20 > Possible solutions: >=20 > - 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. >=20 > others ? >=20 > --=20 > julien.bournelle@int-evry.fr >=20 > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby >=20 _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Nov 21 03:57:25 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05908 for ; Fri, 21 Nov 2003 03:57: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 1AN76A-0007a0-DR for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 03:57:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAL8v6Fa029103 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 03:57:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN768-0007WV-H6 for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 03:57: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 DAA05886 for ; Fri, 21 Nov 2003 03:56:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN765-0006UV-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 03:57:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AN765-0006US-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 03:57:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN767-0007VH-7p; Fri, 21 Nov 2003 03:57:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN75x-0007Up-DY for seamoby@optimus.ietf.org; Fri, 21 Nov 2003 03:56:53 -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 DAA05873 for ; Fri, 21 Nov 2003 03:56:40 -0500 (EST) From: john.loughney@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN75u-0006UA-00 for seamoby@ietf.org; Fri, 21 Nov 2003 03:56:50 -0500 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1AN75u-0006U7-00 for seamoby@ietf.org; Fri, 21 Nov 2003 03:56:50 -0500 Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAL8uo618225 for ; Fri, 21 Nov 2003 10:56:50 +0200 (EET) Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Fri, 21 Nov 2003 10:56:48 +0200 Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 21 Nov 2003 10:56:50 +0200 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Subject: RE: [Seamoby] CTP - a few comments on draft-ietf-seamoby-ctp-05... Date: Fri, 21 Nov 2003 10:56:50 +0200 Message-ID: Thread-Topic: [Seamoby] CTP - a few comments on draft-ietf-seamoby-ctp-05... Thread-Index: AcOpxs8GPuOvrbVMQKqQa+uVweRBzgGRo3Jg To: , X-OriginalArrivalTime: 21 Nov 2003 08:56:50.0470 (UTC) FILETIME=[66F1EC60:01C3B00D] Content-Transfer-Encoding: quoted-printable 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, Assigned issue 31:=20 > Editorial: >=20 > In section 2.5.2 Context Transfer Activate Acknowledge=20 > (CTAA) Message: >=20 > Reserved Reserved for future use. Must be set to=20 > zero by the MN. > >>could be changed with>> > Must be set to zero by the sender of CTAA Message,=20 > i.e. pAR or nAR. >=20 > In 2.5.3 Context Transfer Data (CTD) Message: >=20 > A reliability flag, 'R' > >>could be changed with>> > An acknowlwdgement flag 'A' >=20 > ...indicates whether a reply is required by nAR. > >>could be changed with>> > ...indicates whether a reply is required by pAR. >=20 > Reserved Reserved for future use. Must be set to=20 > zero by the MN. > >>could be changed with>> > Must be set to zero by the pAR. >=20 > Perhaps move here the description of 'Elapsed Time'=20 > which exists=20 > in section 3... >=20 > In section 2.5.4 Context Transfer Data Reply (CTDR) Message >=20 > Reserved Reserved for future use. Must be set to=20 > zero by the MN. > >>could be changed with>> > Must be set to zero by the nAR. >=20 > In 2.5.5 Context Transfer Cancel (CTC) Message >=20 > Reserved Reserved for future use. Must be set to=20 > zero by the MN. > >>could be changed with>> > Must be set to zero by the nAR. >=20 > In 2.5.6 Context Transfer Request (CT Request) Message >=20 > Reserved Reserved for future use. Must be set to=20 > 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 From exim@www1.ietf.org Fri Nov 21 04:01:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06085 for ; Fri, 21 Nov 2003 04:01: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 1AN7A2-0007x2-NR for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 04:01:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAL916lv030557 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 04:01:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN7A2-0007wm-94 for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 04:01: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 EAA06055 for ; Fri, 21 Nov 2003 04:00:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN79z-0006YB-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 04:01:03 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AN79z-0006Y8-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 04:01:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN7A0-0007vx-TG; Fri, 21 Nov 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 1AN79v-0007vG-OT for seamoby@optimus.ietf.org; Fri, 21 Nov 2003 04:00:59 -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 EAA06052 for ; Fri, 21 Nov 2003 04:00:47 -0500 (EST) From: john.loughney@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN79t-0006Y5-00 for seamoby@ietf.org; Fri, 21 Nov 2003 04:00:57 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AN79s-0006Y2-00 for seamoby@ietf.org; Fri, 21 Nov 2003 04:00:56 -0500 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAL90uA22510 for ; Fri, 21 Nov 2003 11:00:56 +0200 (EET) Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Fri, 21 Nov 2003 11:00:53 +0200 Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Fri, 21 Nov 2003 11:00:54 +0200 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Subject: RE: [Seamoby] CTP - a few comments on draft-ietf-seamoby-ctp-05... Date: Fri, 21 Nov 2003 11:00:53 +0200 Message-ID: Thread-Topic: [Seamoby] CTP - a few comments on draft-ietf-seamoby-ctp-05... Thread-Index: AcOpxs8GPuOvrbVMQKqQa+uVweRBzgGRujDQ To: , X-OriginalArrivalTime: 21 Nov 2003 09:00:54.0809 (UTC) FILETIME=[F8951890:01C3B00D] Content-Transfer-Encoding: quoted-printable 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 Lucian, Before assigning an issue, I have some questions. > Can we steal two bits from 'Researved' "area" and use them for a = 'V'=20 > flag within the Context Transfer Activate Acknowledge (CTAA) = Message? > The same thing for Context Transfer Cancel (CTC) Message... Can you give me any more reason & text you think is appropriate? =20 > Is the 'A' flag within CTD Message linked in some way to 'A' flag = within=20 CTAR Message? E.g., if the MN has set the 'A' to '1' in CTAR, then = the pAR should=20 > (or must) also set the 'A' to '1' within the CTD Message? > However, the definition for 'A' flag is the same in both = messages...=20 > (i.e., "the MN requests an acknowledgement"??). No linkage is meant. =20 > Furthermore, does an 'A' flag within the CT Request Message sound=20 > totally inappropriate for the time being > (i.e., it might be in relation to the 'A' flag received by the nAR = > within CTAR Message)? Sorry, I don't get your meaning here. John _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Nov 21 04:46:22 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07330 for ; Fri, 21 Nov 2003 04:46:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN7rY-0002jC-Ox for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 04:46:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAL9k4LG010487 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 04:46:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN7rY-0002it-5f for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 04:46: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 EAA07290 for ; Fri, 21 Nov 2003 04:45:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN7rU-00078Z-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 04:46:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AN7rU-00078W-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 04:46:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN7rW-0002iM-DA; Fri, 21 Nov 2003 04:46:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN7qa-0002dU-QI for seamoby@optimus.ietf.org; Fri, 21 Nov 2003 04:45: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 EAA07267 for ; Fri, 21 Nov 2003 04:44:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN7qX-00077b-00 for seamoby@ietf.org; Fri, 21 Nov 2003 04:45:01 -0500 Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx with esmtp (Exim 4.12) id 1AN7qW-00077J-00 for seamoby@ietf.org; Fri, 21 Nov 2003 04:45:01 -0500 Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16]) by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id hAL9iQ414094; Fri, 21 Nov 2003 10:44:26 +0100 Received: from enst-bretagne.fr (dhcp75 [193.52.74.175]) by courrier.rennes.enst-bretagne.fr (8.11.6p2/8.11.6) with ESMTP id hAL9iQM00118; Fri, 21 Nov 2003 10:44:26 +0100 (MET) Message-ID: <3BFB7704.5060003@enst-bretagne.fr> Date: Wed, 21 Nov 2001 10:42:28 +0100 From: Lucian Suciu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: fr-fr, fr MIME-Version: 1.0 To: john.loughney@nokia.com CC: seamoby@ietf.org Subject: Re: [Seamoby] CTP - a few comments on draft-ietf-seamoby-ctp-05... References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr 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, >Lucian, > >Before assigning an issue, I have some questions. > > > >> Can we steal two bits from 'Researved' "area" and use them for a 'V' >> flag within the Context Transfer Activate Acknowledge (CTAA) Message? >> The same thing for Context Transfer Cancel (CTC) Message... >> >> > >Can you give me any more reason & text you think is appropriate? > If an AR acknowledges a CTAR Message in which we set the 'V' flag to '10' (both IPv6 and IPv4), how can the MN decide if there is a IPv4 address or a IPv6 address within the CTAA Message? >> Is the 'A' flag within CTD Message linked in some way to 'A' flag within >> >> > CTAR Message? E.g., if the MN has set the 'A' to '1' in CTAR, then the pAR should > > >> (or must) also set the 'A' to '1' within the CTD Message? >> However, the definition for 'A' flag is the same in both messages... >> (i.e., "the MN requests an acknowledgement"??). >> >> > >No linkage is meant. > OK. >> Furthermore, does an 'A' flag within the CT Request Message sound >> totally inappropriate for the time being >> (i.e., it might be in relation to the 'A' flag received by the nAR >> within CTAR Message)? >> >> > >Sorry, I don't get your meaning here. > > If no linkage is meant, there is no meaning here :) So, we should forget this comment... Lucian _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Nov 21 08:40:26 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13149 for ; Fri, 21 Nov 2003 08:40:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW4-0006rE-IX for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 08:40:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hALDe7BY026283 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 08:40:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW1-0006p4-Fp for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 08:40: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 IAA13133 for ; Fri, 21 Nov 2003 08:39:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ANBW0-0002He-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 08:40:04 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ANBVz-0002Hb-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 08:40:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBVz-0006oX-Uq; Fri, 21 Nov 2003 08:40:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMvOb-0007fa-1N for seamoby@optimus.ietf.org; Thu, 20 Nov 2003 15:27:21 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23752; Thu, 20 Nov 2003 15:27:08 -0500 (EST) Message-Id: <200311202027.PAA23752@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: Thu, 20 Nov 2003 15:27:07 -0500 Subject: [Seamoby] I-D ACTION: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: , --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 : Candidate Access Router Discovery Author(s) : M. Liebsch Filename : draft-ietf-seamoby-card-protocol-05.txt Pages : 47 Date : 2003-11-20 To enable seamless IP-layer handover of a mobile node (MN) from one access router (AR) to another, the MN is required to discover the identities of candidate ARs (CARs) for handover, along with their capabilities, prior to the initiation of the IP-layer handover. The act of discovery of CARs has two aspects to it: Identifying the IP addresses of the CARs and finding the capabilities of those CARs. This process is called 'candidate access router discovery' (CARD). At the time of IP-layer handover, that CAR, whose capabilities is a good match to the preferences of the MN, may be chosen as the target AR for handover. The protocol described in this document allows a mobile node to perform CARD. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-seamoby-card-protocol-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-card-protocol-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-card-protocol-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-11-20154044.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-seamoby-card-protocol-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-seamoby-card-protocol-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-11-20154044.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Nov 21 08:40:27 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13151 for ; Fri, 21 Nov 2003 08:40:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW4-0006rC-D5 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 08:40:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hALDe7na026304 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 08:40:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW3-0006pq-1l for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 08:40: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 IAA13136 for ; Fri, 21 Nov 2003 08:39:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ANBW1-0002Hl-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 08:40:05 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ANBW1-0002Hi-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 08:40:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW0-0006ox-Tn; Fri, 21 Nov 2003 08:40:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMzBi-0000o3-GC for seamoby@optimus.ietf.org; Thu, 20 Nov 2003 19:30:18 -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 TAA10795 for ; Thu, 20 Nov 2003 19:30:04 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMzBg-00004u-00 for seamoby@ietf.org; Thu, 20 Nov 2003 19:30:16 -0500 Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1AMzBg-00004l-00 for seamoby@ietf.org; Thu, 20 Nov 2003 19:30:16 -0500 Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.24; FreeBSD 4.9) id 1AMzBf-000LAb-4G; Fri, 21 Nov 2003 00:30:15 +0000 To: "James Kempf" cc: seamoby@ietf.org Subject: Re: [Seamoby] Fw: ID Tracker State Update Notice: draft-ietf-seamoby-mobility-terminology In-Reply-To: Message from "James Kempf" of "Thu, 20 Nov 2003 15:35:18 PST." <0fc601c3afbe$f4e91970$956015ac@dclkempt40> Date: Thu, 20 Nov 2003 16:30:15 -0800 From: Allison Mankin Message-Id: 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, Folks, Jim sent the state change, but caught the tracker before I got to enter any notes about today's telechat (TSV had a lot of documents). Here forthwith the report on the issues that came up on the document today. Now Jim can follow up on each point with the editors (if there are any ADish questions, don't hesitate to ask), and shepherd the document through a quick, limited new rev. One review to come before the revision, so wait for that - see 3. Is the next to last point in the 4. Ops-Dir review (about source route including loose source routes) any issue? I think it should not be. Other than that item in 4, and 2, the points below do not challenge content. 1. Mostly the document is viewed as useful. It was noticed that both nemo and mipshop WGs are using it and view it as valuable. 2. Section 4.9 (user mobility etc.) is viewed as weak and* not needed for the mission the document. Because it touches on WGs such the geopriv (mentioning location tracking) and would be hard to get right even with much involvement by Apps WGs, the suggestion is for this section to be dropped. I think this is a very good suggestion. 3. Thomas Narten thought that a very focused single additional review by Henrik Levkowetz (co-Chair of the MIP4 WG) would dot the i's of inter-WG checking - Thomas thought there might be a few considerations seen from the Mobile IPv4 point of view that might come out of this review, but he asked Henrik for this review to be done expeditiously. Communicating with Henrik directly on this is correct, both to ask for it (Jim, it's expected before 10 days) and to interact on it. One last point: as discussed in the plenary, we could do better than to have such cross-checking review happen as late as IESG review - discussions started on this! But by the direct communication of Jim/editors with Henrik, let's keep it short in time. 4. A review from the Operations Directorate found the following small issues: - appendix B says it should list all the terms ("index"), but doesn't. [Note from me: you could leave out Appendix B] - s/Author's Addresses/Authors' Addresses/ - to align better with the previous definition rephrase: In a vertical handover the mobile node's network interface to the access network changes. to: A handover in which the mobile node's network interface to the access network changes. (similar elsewhere as well..) ... - there is inconsistancy of capitalizing in sections 4.2, 4.5, 4.6, 4.9; the definitions should start with capital letters, like the rest of the spec. Clearly a result of merging definitions from someone else without properly integrating them? - section 4.6 starts by referring to Mobile Nodes, but the definitions at places describe Mobile Hosts. Suggest replacing the latter with MN's. Should probably grep -i for "host" or "MH" and check if these are valid..? - s/authentication/authenticate/ in sect 6, "Security context" Content: Source Route A source route from node A to node B is an ordered list of IP addresses, starting with the IP address of node A and ending with the IP address of the node B. Between A and B, the source route includes an ordered list of all the intermediate hops between A and B, as well as the interface index of the interface through which the packet should be transmitted to reach the next hop. ==> this is a stricter definition of Source Route than is usual. Normally SR includes ("Loose SR") the possibility to omit intermediate hops. Consider clarifying. ... "IP access address" is also a funny term, I probably wouldn't use it, but I have no more serious problems with it: IP access address An IP address (often dynamically allocated) which a node uses to designate its current point of attachment to the local network. The IP access address is typically to be distinguished from the mobile node's home address; in fact, while visiting a foreign network the former may be considered unsuitable for use as an end-point address by any but the most short-lived applications. Instead, the IP access address is typically used as the care-of address of the node. _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Nov 21 08:40:29 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13179 for ; Fri, 21 Nov 2003 08:40: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 1ANBW5-0006sG-VH for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 08:40:10 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hALDe955026390 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 08:40:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW4-0006rF-QB for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 08:40:08 -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 IAA13139 for ; Fri, 21 Nov 2003 08:39:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ANBW3-0002Hr-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 08:40:07 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ANBW3-0002Ho-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 08:40:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW3-0006qK-I7; Fri, 21 Nov 2003 08:40:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN74T-0007I2-N6 for seamoby@optimus.ietf.org; Fri, 21 Nov 2003 03:55:21 -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 DAA05804 for ; Fri, 21 Nov 2003 03:55:09 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN74Q-0006Sa-00 for seamoby@ietf.org; Fri, 21 Nov 2003 03:55:18 -0500 Received: from media7.org ([194.100.13.106] helo=cafe-seed.net) by ietf-mx with smtp (Exim 4.12) id 1AN74Q-0006Ry-00 for seamoby@ietf.org; Fri, 21 Nov 2003 03:55:18 -0500 Received: (qmail 15118 invoked from network); 21 Nov 2003 08:54:42 -0000 Received: from unknown (HELO helsinki) (127.0.0.1) by localhost with SMTP; 21 Nov 2003 08:54:42 -0000 Content-Type: text/plain; charset=utf-8 To: seamoby@ietf.org From: John Loughney SEAMOBY-Issues Reply-To: Seamoby CTP Issues Date: Fri, 21 Nov 2003 08:54:42 +0000 MIME-Version: 1.0 Message-Id: <1069404882.47.0.767706199792.issue30@danforsberg.info> X-Roundup-Name: Seamoby CTP Issues X-Roundup-Loop: hello Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Subject: [Seamoby] [issue30] How to handle bad MN's authorization Token? 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 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 From exim@www1.ietf.org Fri Nov 21 08:40:30 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13189 for ; Fri, 21 Nov 2003 08:40: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 1ANBW8-0006sy-18 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 08:40:12 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hALDeBrT026445 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 08:40:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW6-0006sJ-E9 for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 08:40:10 -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 IAA13144 for ; Fri, 21 Nov 2003 08:39:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ANBW5-0002Hx-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 08:40:09 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ANBW4-0002Hu-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 08:40:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANBW4-0006rH-Sp; Fri, 21 Nov 2003 08:40:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN769-0007Yt-IN for seamoby@optimus.ietf.org; Fri, 21 Nov 2003 03:57: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 DAA05881 for ; Fri, 21 Nov 2003 03:56:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN764-0006UM-00 for seamoby@ietf.org; Fri, 21 Nov 2003 03:57:00 -0500 Received: from media7.org ([194.100.13.106] helo=cafe-seed.net) by ietf-mx with smtp (Exim 4.12) id 1AN764-0006Ti-00 for seamoby@ietf.org; Fri, 21 Nov 2003 03:57:00 -0500 Received: (qmail 15135 invoked from network); 21 Nov 2003 08:56:31 -0000 Received: from unknown (HELO helsinki) (127.0.0.1) by localhost with SMTP; 21 Nov 2003 08:56:31 -0000 Content-Type: text/plain; charset=utf-8 To: seamoby@ietf.org From: John Loughney SEAMOBY-Issues Reply-To: Seamoby CTP Issues Date: Fri, 21 Nov 2003 08:56:30 +0000 MIME-Version: 1.0 Message-Id: <1069404990.99.0.344916405293.issue31@danforsberg.info> X-Roundup-Name: Seamoby CTP Issues X-Roundup-Loop: hello Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Subject: [Seamoby] [issue31] editorial comments 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 New submission from John Loughney : Editorial: In section 2.5.2 Context Transfer Activate Acknowledge (CTAA)=20 Message: Reserved Reserved for future use. Must be set to zero by the=20 MN. >>could be changed with>> Must be set to zero by the sender of CTAA Message, i.e. pAR or=20 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=20 MN. >>could be changed with>> Must be set to zero by the pAR. Perhaps move here the description of 'Elapsed Time' which exists=20 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=20 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=20 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=20 MN. >>could be changed with>> Must be set to zero by the nAR. ---------- category: Editorial document: draft-ietf-seamoby-ctp-05.txt messages: 40 nosy: jloughney priority: Should Fix status: Text Proposed title: editorial comments _____________________________________________________________ Seamoby CTP Issues _____________________________________________________________ _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Fri Nov 21 13:28:21 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25603 for ; Fri, 21 Nov 2003 13:28: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 1ANG0h-0002GF-SE for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 13:28:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hALIS3OF008685 for seamoby-archive@odin.ietf.org; Fri, 21 Nov 2003 13:28:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANG0h-0002G0-Od for seamoby-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 13:28: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 NAA25553 for ; Fri, 21 Nov 2003 13:27:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ANG0f-0006aD-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 13:28:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ANG0f-0006aA-00 for seamoby-web-archive@ietf.org; Fri, 21 Nov 2003 13:28:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANG0g-0002F1-4S; Fri, 21 Nov 2003 13:28:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ANG0c-0002D7-Qw for seamoby@optimus.ietf.org; Fri, 21 Nov 2003 13:27:58 -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 NAA25546 for ; Fri, 21 Nov 2003 13:27:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ANG0a-0006Zu-00 for seamoby@ietf.org; Fri, 21 Nov 2003 13:27:56 -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 1ANG0a-0006Zq-00 for seamoby@ietf.org; Fri, 21 Nov 2003 13:27:56 -0500 Message-ID: <010f01c3b05d$3bd5f2b0$956015ac@dclkempt40> From: "James Kempf" To: "Allison Mankin" Cc: References: Subject: Re: [Seamoby] Fw: ID Tracker State Update Notice: draft-ietf-seamoby-mobility-terminology Date: Fri, 21 Nov 2003 10:28:17 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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 Allison, Thanx for posting the IESG review. I will forward the IESG comments to Jukka (who should actually have seen them since he's on the list but just to make sure) for incorporation into the document. Also, Jukka and I will co-ordinate asking Henrick to do a review for us. We will ask for a 10 day turnaround as suggested. I believe Thierry Ernst had a few comments from the NEMO perspective that Jukka also needs to consider. jak ----- Original Message ----- From: "Allison Mankin" To: "James Kempf" Cc: Sent: Thursday, November 20, 2003 4:30 PM Subject: Re: [Seamoby] Fw: ID Tracker State Update Notice: draft-ietf-seamoby-mobility-terminology > Hi, Folks, > > Jim sent the state change, but caught the tracker before I got to enter any > notes about today's telechat (TSV had a lot of documents). Here forthwith the > report on the issues that came up on the document today. Now Jim can follow up > on each point with the editors (if there are any ADish questions, don't hesitate to > ask), and shepherd the document through a quick, limited new rev. One review to come > before the revision, so wait for that - see 3. > > Is the next to last point in the 4. Ops-Dir review (about source route including > loose source routes) any issue? I think it should not be. Other than that > item in 4, and 2, the points below do not challenge content. > > 1. Mostly the document is viewed as useful. It was noticed > that both nemo and mipshop WGs are using it and view it as valuable. > > 2. Section 4.9 (user mobility etc.) is viewed as weak and* not needed > for the mission the document. Because it touches on WGs such the geopriv > (mentioning location tracking) and would be hard to get right even with > much involvement by Apps WGs, the suggestion is for this section to be > dropped. I think this is a very good suggestion. > > 3. Thomas Narten thought that a very focused single additional review > by Henrik Levkowetz (co-Chair of the MIP4 WG) would dot the i's of > inter-WG checking - Thomas thought there might be a few considerations > seen from the Mobile IPv4 point of view that might come out of this > review, but he asked Henrik for this review to be done expeditiously. > Communicating with Henrik directly on this is correct, both to ask > for it (Jim, it's expected before 10 days) and to interact on it. > One last point: as discussed in the plenary, we could do better > than to have such cross-checking review happen as late as IESG > review - discussions started on this! But by the direct > communication of Jim/editors with Henrik, let's keep it short in time. > > 4. A review from the Operations Directorate found the following small issues: > > - appendix B says it should list all the terms ("index"), but doesn't. > > [Note from me: you could leave out Appendix B] > > - s/Author's Addresses/Authors' Addresses/ > - to align better with the previous definition rephrase: > > In a vertical handover the mobile node's network interface to the > access network changes. > > to: > > A handover in which the mobile node's network interface to the > access network changes. > > (similar elsewhere as well..) > ... > > - there is inconsistancy of capitalizing in sections 4.2, 4.5, 4.6, > 4.9; the definitions should start with capital letters, like the rest > of the spec. Clearly a result of merging definitions from someone > else without properly integrating them? > > - section 4.6 starts by referring to Mobile Nodes, but the definitions > at places describe Mobile Hosts. Suggest replacing the latter with > MN's. Should probably grep -i for "host" or "MH" and check if these > are valid..? > > - s/authentication/authenticate/ in sect 6, "Security context" > > > Content: > > Source Route > A source route from node A to node B is an ordered list of IP > addresses, starting with the IP address of node A and ending with > the IP address of the node B. Between A and B, the source route > includes an ordered list of all the intermediate hops between A > and B, as well as the interface index of the interface through > which the packet should be transmitted to reach the next hop. > > ==> this is a stricter definition of Source Route than is usual. > Normally SR includes ("Loose SR") the possibility to omit intermediate > hops. Consider clarifying. > > ... > > "IP access address" is also a funny term, I probably wouldn't use it, > but I have no more serious problems with it: > > IP access address > An IP address (often dynamically allocated) which a node uses to > designate its current point of attachment to the local network. > The IP access address is typically to be distinguished from the > mobile node's home address; in fact, while visiting a foreign > network the former may be considered unsuitable for use as an > end-point address by any but the most short-lived applications. > Instead, the IP access address is typically used as the care-of > address of the node. > > > > _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Tue Nov 25 17:43:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14951 for ; Tue, 25 Nov 2003 17:43:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOltf-0007r6-GD for seamoby-archive@odin.ietf.org; Tue, 25 Nov 2003 17:43:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPMh3xc030192 for seamoby-archive@odin.ietf.org; Tue, 25 Nov 2003 17:43:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOltf-0007qt-7k for seamoby-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 17:43: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 RAA14940 for ; Tue, 25 Nov 2003 17:42:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOltc-000113-00 for seamoby-web-archive@ietf.org; Tue, 25 Nov 2003 17:43:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOltc-00010z-00 for seamoby-web-archive@ietf.org; Tue, 25 Nov 2003 17:43:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOltd-0007qA-8g; Tue, 25 Nov 2003 17:43:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOltO-0007pf-JO for seamoby@optimus.ietf.org; Tue, 25 Nov 2003 17:42: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 RAA14932 for ; Tue, 25 Nov 2003 17:42:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOltL-00010b-00 for seamoby@ietf.org; Tue, 25 Nov 2003 17:42:43 -0500 Received: from mail2.it.kth.se ([130.237.212.132]) by ietf-mx with esmtp (Exim 4.12) id 1AOltL-00010X-00 for seamoby@ietf.org; Tue, 25 Nov 2003 17:42:43 -0500 Received: from it.kth.se (ripper.it.kth.se [130.237.212.25]) by mail2.it.kth.se (8.11.6p2/8.11.6) with ESMTP id hAPMggk26805 for ; Tue, 25 Nov 2003 23:42:42 +0100 (MET) Message-Id: <200311252242.hAPMggk26805@mail2.it.kth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: seamoby@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Tue, 25 Nov 2003 23:43:34 +0100 From: Jon-Olov Vatn Content-Transfer-Encoding: quoted-printable Subject: [Seamoby] Using CARD to find CARs with roaming agreement with my ISP? 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! Would it be feasible to use CARD to find out whether a CAR is likely to give me Internet access (in advance of a handoff)? The case I am interested in is when a customer is about to perform a handoff and would like to know the set of CARs that are either run by his/her ISP or by an ISP with a roaming agreement with his/her ISP. I was reading the draft "Issues in candidate access router discovery for seamless IP-level handoffs", = (draft-ietf-seamoby-cardiscovery-issues-04.txt) but this case was not mentioned in list with sample scenarios for CARD motivation. BW J-O _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby From exim@www1.ietf.org Tue Nov 25 18:39:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18251 for ; Tue, 25 Nov 2003 18:39:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOmlr-0002Xw-Og for seamoby-archive@odin.ietf.org; Tue, 25 Nov 2003 18:39:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPNd3FA009775 for seamoby-archive@odin.ietf.org; Tue, 25 Nov 2003 18:39:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOmlr-0002Xa-Gp for seamoby-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 18:39: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 SAA18223 for ; Tue, 25 Nov 2003 18:38:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOmlo-0002G4-00 for seamoby-web-archive@ietf.org; Tue, 25 Nov 2003 18:39:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOmlo-0002G1-00 for seamoby-web-archive@ietf.org; Tue, 25 Nov 2003 18:39:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOmlp-0002Wk-DL; Tue, 25 Nov 2003 18:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOmlA-0002Ug-OQ for seamoby@optimus.ietf.org; Tue, 25 Nov 2003 18:38:20 -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 SAA18165 for ; Tue, 25 Nov 2003 18:38:04 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOml7-0002EX-00 for seamoby@ietf.org; Tue, 25 Nov 2003 18:38:17 -0500 Received: from mailer.ccrl.nj.nec.com ([138.15.108.3] helo=mailer.nec-labs.com) by ietf-mx with esmtp (Exim 4.12) id 1AOml6-0002E5-00 for seamoby@ietf.org; Tue, 25 Nov 2003 18:38:16 -0500 Received: from peace ([138.15.107.202]) by mailer.nec-labs.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 25 Nov 2003 18:38:04 -0500 Message-ID: <000901c3b3ad$d261e150$ca6b0f8a@peace> From: "Eunsoo Shim" To: , "Jon-Olov Vatn" References: <200311252242.hAPMggk26805@mail2.it.kth.se> Subject: Re: [Seamoby] Using CARD to find CARs with roaming agreement with my ISP? Date: Tue, 25 Nov 2003 18:42:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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: 25 Nov 2003 23:38:04.0259 (UTC) FILETIME=[2BD4DB30:01C3B3AD] 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 I think it is certainly possible. Account requirements or ownership can be attributes of the CARs. Regards, Eunsoo ----- Original Message ----- From: "Jon-Olov Vatn" To: Sent: Tuesday, November 25, 2003 5:43 PM Subject: [Seamoby] Using CARD to find CARs with roaming agreement with my ISP? Hi! Would it be feasible to use CARD to find out whether a CAR is likely to give me Internet access (in advance of a handoff)? The case I am interested in is when a customer is about to perform a handoff and would like to know the set of CARs that are either run by his/her ISP or by an ISP with a roaming agreement with his/her ISP. I was reading the draft "Issues in candidate access router discovery for seamless IP-level handoffs", (draft-ietf-seamoby-cardiscovery-issues-04.txt) but this case was not mentioned in list with sample scenarios for CARD motivation. BW J-O _______________________________________________ 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 Nov 26 04:48:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29905 for ; Wed, 26 Nov 2003 04:48: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 1AOwHG-0007Xm-DG for seamoby-archive@odin.ietf.org; Wed, 26 Nov 2003 04:48:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQ9m64i028997 for seamoby-archive@odin.ietf.org; Wed, 26 Nov 2003 04:48:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOwHG-0007Xc-0C for seamoby-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 04:48: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 EAA29886 for ; Wed, 26 Nov 2003 04:47:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOwHC-0002ZG-00 for seamoby-web-archive@ietf.org; Wed, 26 Nov 2003 04:48:02 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOwHC-0002ZD-00 for seamoby-web-archive@ietf.org; Wed, 26 Nov 2003 04:48:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOwHB-0007Wx-EO; Wed, 26 Nov 2003 04:48:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOwGz-0007Wf-HN for seamoby@optimus.ietf.org; Wed, 26 Nov 2003 04:47:49 -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 EAA29868 for ; Wed, 26 Nov 2003 04:47:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOwGw-0002Yu-00 for seamoby@ietf.org; Wed, 26 Nov 2003 04:47:46 -0500 Received: from mail2.it.kth.se ([130.237.212.132]) by ietf-mx with esmtp (Exim 4.12) id 1AOwGv-0002Yr-00 for seamoby@ietf.org; Wed, 26 Nov 2003 04:47:45 -0500 Received: from it.kth.se (ripper.it.kth.se [130.237.212.25]) by mail2.it.kth.se (8.11.6p2/8.11.6) with ESMTP id hAQ9lik03442; Wed, 26 Nov 2003 10:47:44 +0100 (MET) Message-Id: <200311260947.hAQ9lik03442@mail2.it.kth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: seamoby@ietf.org, "Mani, Mahalingam (Mahalingam)" From: Jon-Olov Vatn Cc: vatn@it.kth.se, lwapp@frascone.com X-url: http://www.it.kth.se/~vatn/ Subject: Re: [Seamoby] CARD and multiple ARs per AP? In-reply-to: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Wed, 26 Nov 2003 10:48:37 +0100 Content-Transfer-Encoding: quoted-printable 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 19 November 2003 "Mani, Mahalingam (Mahalingam)" wrote: > This discussion in SEAMOBY overlaps CAPWAP interest: > = > This many-many mapping variant of AP->AR is of additional interest to > CAPWAP which is about to get into the thick of varied AP->AR (it's > termed AC) architecture discussions - hopefully soon. > = > Is it in the interests of WiSPs to share a common AP infrastructure to > facilitate uniform roaming while having agreements to route appropriate= > user traffic to relevant ACs? It does appear to make sense in dense > deployments of 11b/11g. I can also imagine situations where the L2 infrastructure is owned by a third party, such as an appartment building association, and made available to multiple ISPs so that the individual customers do not have to sign-up with the same ISP. (This case is similar to the case with wired broadband access; the only difference would be that we now have WLAN APs attached to the shared L2 infrastructure). My wish would be that CARD would support architectures that make it easier for customers to change ISPs. Limiting the architecure to one AR per AP seems to prohibit some of the possibilities to establish such access networks. /J-O > = > It seems like yet another case in point for policy enforcement in the A= P > dataplane with policy decisions delivered by ACs from mgmt. plane. > = > -mani > > -----Original Message----- > > From: seamoby-admin@ietf.org [mailto:seamoby-admin@ietf.org] On Behal= f > Of > > Jon-Olov Vatn > > Sent: Tuesday, November 18, 2003 2: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?) > > = > > 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 an= d > > 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 acces= s > > infrastructure with briding APs (see the figure below) it is possible= > > to use VLAN (or other tunneling techniques) between the APs and ARs t= o > > 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 on= e > > 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 contai= n > > 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 o= f > > 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. > > = > > 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 Wed Nov 26 05:49:24 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01735 for ; Wed, 26 Nov 2003 05: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 1AOxEH-0002BY-8F for seamoby-archive@odin.ietf.org; Wed, 26 Nov 2003 05:49:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQAn5n1008399 for seamoby-archive@odin.ietf.org; Wed, 26 Nov 2003 05:49:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOxEG-0002Ay-SF for seamoby-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 05:49: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 FAA01709 for ; Wed, 26 Nov 2003 05:48:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOxED-0003Rg-00 for seamoby-web-archive@ietf.org; Wed, 26 Nov 2003 05:49:01 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOxEC-0003Rd-00 for seamoby-web-archive@ietf.org; Wed, 26 Nov 2003 05:49:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOxEE-0002A9-DN; Wed, 26 Nov 2003 05:49:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOxDv-00029O-Rv for seamoby@optimus.ietf.org; Wed, 26 Nov 2003 05:48:43 -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 FAA01701 for ; Wed, 26 Nov 2003 05:48:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOxDs-0003RS-00 for seamoby@ietf.org; Wed, 26 Nov 2003 05:48:40 -0500 Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi) by ietf-mx with esmtp (Exim 4.12) id 1AOxDr-0003RP-00 for seamoby@ietf.org; Wed, 26 Nov 2003 05:48:39 -0500 Received: from mannersaari.cs.Helsinki.FI (mannersaari.cs.helsinki.fi [::ffff:128.214.11.173]) (IDENT: jmanner, TLS: TLSv1/SSLv3,168bits,DES-CBC3-SHA) by mail.cs.helsinki.fi with esmtp; Wed, 26 Nov 2003 12:48:40 +0200 Date: Wed, 26 Nov 2003 12:48:39 +0200 (EET) From: Jukka MJ Manner To: Seamoby Working Group In-Reply-To: <0fc601c3afbe$f4e91970$956015ac@dclkempt40> Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Seamoby] Final edits for the terminology draft 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 all, I am doing the final edits to the terminology draft, and I would need answers to the following questions raised by the IESG and Thierry Ernst in a separate email. Jukka 1) What would be the definition of a subnet? Thierry thought one should be added. 2) The definition of source route? Source Route A source route from node A to node B is an ordered list of IP addresses, starting with the IP address of node A and ending with the IP address of the node B. Between A and B, the source route includes an ordered list of all the intermediate hops between A and B, as well as the interface index of the interface through which the packet should be transmitted to reach the next hop. Allison: This is a stricter definition of Source Route than is usual. Normally SR includes ("Loose SR") the possibility to omit intermediate hops. Consider clarifying. [JM]: Suggestion to remove "all the", and add at the end "The list of intermediate hops might not include all visited nodes, some hops might be omitted for a reason or another." 3) Is the definition of "link" sufficient? Does it need to be very detailed? There was this email quite some time ago: Hi, I have a question about the definition of "link" in draft-ietf-seamoby-mobility-terminology-04.txt It is said: "A communication facility or physical medium that can sustain data communications between multiple network nodes, such as an Ethernet (simple or bridged). A link is the layer immediately below IP." As I undestand, the definition of link is not directly related to an IPv6 link. For example, consider the following example: One ethernet link where a router advertises a single IPv6 prefix, and an 802.11b access point connected to this ethernet link as illustrated here: AR ____ |__________________ | | AP Fixed node MN2 MN1 In this situation, is it right to say that : - there are 2 links and - there is one IPv6 link ? Thanks Regards, Nicolas [JM]: (don't know how the figure was meant to be formatted...) Isn't an 802.11b AP just a wireless bridge between the AR/FN and MN1, and, thus, not its own link? Still, you could say there are two links and one "IPv6 link", for example. Comments? 4) Do we need an index of terms (Appendix B)? _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby