From sunseawq@huawei.com Tue Mar 3 18:53:10 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 760573A6B57 for ; Tue, 3 Mar 2009 18:53:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.654 X-Spam-Level: X-Spam-Status: No, score=-0.654 tagged_above=-999 required=5 tests=[AWL=1.945, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7yBn5ii1YBtH for ; Tue, 3 Mar 2009 18:53:09 -0800 (PST) Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id D11D53A6AB7 for ; Tue, 3 Mar 2009 18:52:45 -0800 (PST) Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KFY0070KO0JDY@szxga01-in.huawei.com> for mip4@ietf.org; Wed, 04 Mar 2009 10:53:07 +0800 (CST) Received: from huawei.com ([172.24.1.33]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KFY002CPO0JZC@szxga01-in.huawei.com> for mip4@ietf.org; Wed, 04 Mar 2009 10:53:07 +0800 (CST) Received: from w53375a ([10.164.12.27]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KFY001ZCO0J1Q@szxml06-in.huawei.com> for mip4@ietf.org; Wed, 04 Mar 2009 10:53:07 +0800 (CST) Date: Wed, 04 Mar 2009 10:53:06 +0800 From: Qin Wu To: mip4@ietf.org Message-id: <02c501c99c74$58a50940$1b0ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <20090303104201.BFD1E3A6C34@core3.amsl.com> Cc: Hui Deng Subject: [Mip4] [mip4] New draft on MIP extension for ethernet service support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2009 02:53:10 -0000 Hi Folks We just submitted the draft http://tools.ietf.org/html/draft-wu-mip4-ether-00 Comments are welcome. BR Qin ----- Original Message ----- From: "IETF I-D Submission Tool" To: Cc: ; ; Sent: Tuesday, March 03, 2009 6:42 PM Subject: New Version Notification for draft-wu-mip4-ether-00 > > A new version of I-D, draft-wu-mip4-ether-00.txt has been successfuly submitted by Wenson Wu and posted to the IETF repository. > > Filename: draft-wu-mip4-ether > Revision: 00 > Title: MIP Extension for Ethernet Service Support > Creation_date: 2009-03-03 > WG ID: Independent Submission > Number_of_pages: 11 > > Abstract: > The IP Mobility Protocol [RFC3344] enables node to maintain IP > connectivity when node changes the location. However it is ideal to > support forwarding ethernet frame between mobile node and ethernet > service provider. This document describes ethernet extension mobility > option for mobile IPv4 that is intended to assist home agent to > tunnel ethernet frame on the home link to the FA in the foreign link > during datagram delivery process. > > > > The IETF Secretariat. > > From tsirtsis@googlemail.com Fri Mar 6 07:22:33 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CFA93A6BDA for ; Fri, 6 Mar 2009 07:22:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.865 X-Spam-Level: X-Spam-Status: No, score=-1.865 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMmUEL7Aks6Z for ; Fri, 6 Mar 2009 07:22:28 -0800 (PST) Received: from mail-fx0-f176.google.com (mail-fx0-f176.google.com [209.85.220.176]) by core3.amsl.com (Postfix) with ESMTP id 39C3F3A69DC for ; Fri, 6 Mar 2009 07:22:28 -0800 (PST) Received: by fxm24 with SMTP id 24so423962fxm.37 for ; Fri, 06 Mar 2009 07:22:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/cZZSqHkanx0iffjrz1HBY7ArnghHIqemwZiVrWtpmU=; b=LrUREEsMjnghzPXtYRP7YSEfeNqHanDw2yX9Bh5AXqjQr2otrMZLGm+F1h/WMLtqB8 NjGlA0Ukk048wh+lDIYwpPf7PKkWVYhkg1r4zRENEFAbDeS1RuIt+/TvVcjmFel8sAbC RFqL6oUb0x3mDaEkMqKUK2bIZOTsZ+IvEgcvY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=jIVBH5lC3vGlzS23yh5snoB1VPxzc7sAJcvlDsEPqritwkm9N7+waOJ7zQyQCjzkw5 thRMtljgxzqDB70IkIB5TpDcqSYz9q3g4F6da80/WRi32Mu9/B8m5Gbin0uw8WuZuLFu +EM8SnoeB+DI6CIP/5YWbRsdTWFgVCen6FpTw= MIME-Version: 1.0 Received: by 10.103.213.19 with SMTP id p19mr1123852muq.9.1236352978082; Fri, 06 Mar 2009 07:22:58 -0800 (PST) In-Reply-To: References: Date: Fri, 6 Mar 2009 15:22:58 +0000 Message-ID: From: George Tsirtsis To: McCann Peter-A001034 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Status update & Recharter effort X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Mar 2009 15:22:33 -0000 On Wed, Feb 11, 2009 at 5:04 PM, McCann Peter-A001034 wrote: ... > > > Several new work items have come to our attention over the past > few meeting cycles. =C2=A0Here is a partial list of potential work items > for mip4 going forward. =C2=A0Please comment on which you would like to > see and which you think should be excluded. > > > draft-deng-mip4-host-configuration-00.txt > draft-chakrabarti-mip4-mcbc-03.txt > =C2=A0These two items are related, because DHCP uses IP-layer broadcast > =C2=A0to deliver DHCPREQUEST messages. =C2=A0I'd like to propose that we = drop > =C2=A0the gen-ext draft and add these two. =C2=A0Comments? > > draft-gundavelli-mip4-multiple-tunnel-support-00.txt > =C2=A0We've had some good discussion already on the mailing list and this > =C2=A0seems like a potentially useful extension. =C2=A0Comments? > GT> If we take this up we should also consider http://tools.ietf.org/html/draft-tsirtsis-mip4-flowmove-01 which is expired but still relevant I think. From rfc-editor@rfc-editor.org Fri Mar 6 15:46:43 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 127EA28C10B; Fri, 6 Mar 2009 15:46:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.905 X-Spam-Level: X-Spam-Status: No, score=-16.905 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YHgZ2MIM89m0; Fri, 6 Mar 2009 15:46:42 -0800 (PST) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 4ECEF3A69C7; Fri, 6 Mar 2009 15:46:42 -0800 (PST) Received: by bosco.isi.edu (Postfix, from userid 70) id B380624259F; Fri, 6 Mar 2009 15:45:37 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20090306234537.B380624259F@bosco.isi.edu> Date: Fri, 6 Mar 2009 15:45:37 -0800 (PST) Cc: mip4@ietf.org, rfc-editor@rfc-editor.org Subject: [Mip4] RFC 5454 on Dual-Stack Mobile IPv4 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Mar 2009 23:46:43 -0000 A new Request for Comments is now available in online RFC libraries. RFC 5454 Title: Dual-Stack Mobile IPv4 Author: G. Tsirtsis, V. Park, H. Soliman Status: Standards Track Date: March 2009 Mailbox: tsirtsis@googlemail.com, vpark@qualcomm.com, hesham@elevatemobile.com Pages: 18 Characters: 38606 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip4-dsmipv4-10.txt URL: http://www.rfc-editor.org/rfc/rfc5454.txt This specification provides IPv6 extensions to the Mobile IPv4 protocol. The extensions allow a dual-stack node to use IPv4 and IPv6 home addresses as well as to move between IPv4 and dual stack network infrastructures. [STANDARDS TRACK] This document is a product of the Mobility for IPv4 Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From denghui02@gmail.com Mon Mar 9 07:15:09 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 312F03A6916 for ; Mon, 9 Mar 2009 07:15:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.018 X-Spam-Level: X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[AWL=0.581, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uTp61yMWdQ+B for ; Mon, 9 Mar 2009 07:15:08 -0700 (PDT) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170]) by core3.amsl.com (Postfix) with ESMTP id 1A8F73A67D2 for ; Mon, 9 Mar 2009 07:15:08 -0700 (PDT) Received: by wf-out-1314.google.com with SMTP id 27so1917469wfd.31 for ; Mon, 09 Mar 2009 07:15:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=rsN0lqJWO7otCazQKnIqE/qTIwCAS62SCXqV88RTYmg=; b=Icv2H6MbPHdPZxpsC+rISUrXzBSrWtxJK8H9LwQ+G1swylX5lkN+BdrsW+WEO6bBA6 X1uzqEeQmiNvg/COJRYfaxhx1OuKpl6i4PEJflzhr7fmizRcN8SCbtggYe29jV6ig9XN W6Dlq8rkQBicNDSUpZluKoptMEwf1nWhOiBFw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=nzTcePvBVjruTzCno+J0noHtZoCAIphI4AS7ilnNHAPe2+5qxgqxcidrnp+br1cRQr plnJHA6937emYz81lAf1BU4nY5ItaabeJWWsi88MT3kA6Q0CyaxELmBLeBXDme1hXxVh bvhTYni33FrUmYytEqK8BtbnzxFKjGtLsUyhI= MIME-Version: 1.0 Received: by 10.142.186.9 with SMTP id j9mr2574492wff.5.1236608142165; Mon, 09 Mar 2009 07:15:42 -0700 (PDT) In-Reply-To: References: <1d38a3350902142331v4651dd40r8a5b222a74a68a74@mail.gmail.com> Date: Mon, 9 Mar 2009 22:15:42 +0800 Message-ID: <1d38a3350903090715x477880e6k1b8b5034f3cfe969@mail.gmail.com> From: Hui Deng To: Ahmad Muhanna Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: mip4@ietf.org, McCann Peter-A001034 Subject: Re: [Mip4] Comments on: Generic Notification Message for Mobile IPv4 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 14:15:09 -0000 Hi, Ahmad, the word you raised is help, I also add one spcial clarification for FA. thank you also for reviewing HA section Best regards, -Hui The MN and HA MUST maintain the following information, the FA also need maintain both HA's and MN's direction the below information: - the IP source address of the Registration Request/Reply - the IP destination address of the Registration Request/Reply - the UDP source port of the Registration Request/Reply - the UDP destination port of the Registration Request/Reply The sending node always sends the GNM message following the same procedure for sending Registration Request as in section 3.3 of [RFC3344] and the receiving node follows the same procedure for Registration Reply as in section 3.4. of [RFC3344] when sending GNAM. 2009/2/16 Ahmad Muhanna : > Hi Hui, > looks good. I have one comment and a reply inline. > > Regards, > Ahmad > ________________________________ > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0++++++++++++++++ > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04.1. =A0Generic Notification Message > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0A generic notification message is sent= by a mobility > agent to inform > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0another mobility agent, or a MN, of MI= P-related > information such as > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0vendor specific extensions [RFC3115] a= nd generic > string > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0notification [RFC4917]. =A0These messa= ges must use the > same IP and UDP > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0headers as any previous Registration R= equest or Reply > message to the > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0same entity. =A0This would support NAT= traversal and > ensure same > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0security association used for GNM/GNAM= and RRQ/RRP. > The generic > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0notification message is defined as fol= lows: > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IP Fields: > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Source Address =A0 =A0 =A0 =A0 Sam= e as the last Registration > Reply/Request > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 message received. > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Destination Address =A0 =A0Same as= the last Registration > Reply/Request > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 message. > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0UDP Fields: > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Source Port =A0 =A0 =A0 =A0 =A0 = =A0Same as the last Registration > Reply/Request > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 message. > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Destination Port =A0 =A0 =A0 Same = as the last Registration > Reply/Request > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 message. > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0[Ahmad-1] > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Are these information saved in the mobile = node BCE? I > did not check > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0RFC3344 lately but just in case, if these = IP addresses > are not currently > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0save in the MN binding, then it needs to b= e added. > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0[Ahmad-end-1] > > =A0 =A0 =A0 =A0Your recollection is correct, those information are not sa= ved in > BCE, so I add > =A0 =A0 =A0 =A0one paragraph below > =A0 =A0 =A0 =A0 =A0 The MN, FA, and HA MUST maintain the following inform= ation: > =A0 =A0 =A0 =A0 =A0 =A0 =A0- the IP source address of the Registration Re= quest/Reply > =A0 =A0 =A0 =A0 =A0 =A0 =A0- the IP destination address of the Registrati= on > Request/Reply > =A0 =A0 =A0 =A0 =A0 =A0 =A0- the UDP source port of the Registration Requ= est/Reply > =A0 =A0 =A0 =A0 =A0 =A0 =A0- the UDP destination port of the Registration > Request/Reply > > [Ahmad-1] > This way looks ok but the text should be more specific to each node. In > other words, what the MN needs to keep, what the FA needs to keep, etc. > Especially the FA should be unique in here. IMO, the draft should not > leave this information vague in order to eliminate interoperability > issues. > > Actually, after thinking about this one more time, a much easier > approach should be something like the following: > > The sending node always sends the GNM message following the same > procedure for sending Registration Request as in section 3.3 of > [RFC3344] and the receiving node follows the same procedure for > Registration Reply as in section 3.4. of [RFC3344] when sending GNAM. > > IMO, this should work fine with messages sent to the FA and HA. With > respect to messages sent to the MN, it may be a little tricky. But a > mobile node which will support this draft, will comply with its > requirement. > > [Ahmad-end-1] > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Finally, I did not review the HA section. > > =A0 =A0 =A0 =A0If you have time, I would say thanks again if you could he= lp to > review HA section. > > [Ahmad] > Sure. I will try to do that and share with you my comments, if I have > any. > > > =A0 =A0 =A0 =A0Thanks for your detail review. > =A0 =A0 =A0 =A0Please feel free to let me know if you are fine with those > revisions. > > =A0 =A0 =A0 =A0Best regards, > > =A0 =A0 =A0 =A0-Hui > > > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Regards, > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Ahmad > > > > > From root@core3.amsl.com Mon Mar 9 07:30:01 2009 Return-Path: X-Original-To: mip4@ietf.org Delivered-To: mip4@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 8B1E63A6C16; Mon, 9 Mar 2009 07:30:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090309143001.8B1E63A6C16@core3.amsl.com> Date: Mon, 9 Mar 2009 07:30:01 -0700 (PDT) Cc: mip4@ietf.org Subject: [Mip4] I-D Action:draft-ietf-mip4-generic-notification-message-08.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 14:30:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobility for IPv4 Working Group of the IETF. Title : Generic Notification Message for Mobile IPv4 Author(s) : H. Deng, et al. Filename : draft-ietf-mip4-generic-notification-message-08.txt Pages : 34 Date : 2009-03-09 This document specifies protocol enhancements that allow Mobile IPv4 entities to send and receive explicit notification messages using a new Mobile IPv4 message type designed for this purpose. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-generic-notification-message-08.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ 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: Message/External-body; name="draft-ietf-mip4-generic-notification-message-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-03-09072901.I-D@ietf.org> --NextPart-- From pete.mccann@motorola.com Mon Mar 9 08:57:32 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A31F93A699C for ; Mon, 9 Mar 2009 08:57:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XuxZqOdc2u8j for ; Mon, 9 Mar 2009 08:57:32 -0700 (PDT) Received: from mail55.messagelabs.com (mail55.messagelabs.com [216.82.241.163]) by core3.amsl.com (Postfix) with ESMTP id B75B63A68C0 for ; Mon, 9 Mar 2009 08:57:31 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-3.tower-55.messagelabs.com!1236614280!9297936!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 8664 invoked from network); 9 Mar 2009 15:58:00 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-3.tower-55.messagelabs.com with AES256-SHA encrypted SMTP; 9 Mar 2009 15:58:00 -0000 Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate8.mot.com (8.14.3/8.14.3) with ESMTP id n29Fw0kT029797 for ; Mon, 9 Mar 2009 08:58:00 -0700 (MST) Received: from il06vts02.mot.com (il06vts02.mot.com [129.188.137.142]) by il06exr01.mot.com (8.13.5/Vontu) with SMTP id n29FvxVc022338 for ; Mon, 9 Mar 2009 10:57:59 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id n29FvxE2022333 for ; Mon, 9 Mar 2009 10:57:59 -0500 (CDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 9 Mar 2009 11:57:58 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Agenda topics for IETF 74 thread-index: Acmgz9D5SNEh3FBgQk+b9xOVZbN3wQ== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: Henrik Levkowetz Subject: [Mip4] Agenda topics for IETF 74 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 15:57:32 -0000 We will be meeting in San Francisco on Tuesday, March 24 2009, for 2 hours from 1300 to 1500. If anyone has agenda items they would like to discuss, please send e-mail ASAP to myself and=20 Henrik. -Pete From jeedward@yahoo.com Sun Mar 8 04:52:12 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2698428C10F for ; Sun, 8 Mar 2009 04:52:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.925 X-Spam-Level: X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[AWL=-0.723, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yHDirYH7b1W8 for ; Sun, 8 Mar 2009 04:52:11 -0700 (PDT) Received: from n55a.bullet.mail.sp1.yahoo.com (n55a.bullet.mail.sp1.yahoo.com [98.136.45.2]) by core3.amsl.com (Postfix) with SMTP id 36B4E3A6BE3 for ; Sun, 8 Mar 2009 04:52:11 -0700 (PDT) Received: from [216.252.122.216] by n55.bullet.mail.sp1.yahoo.com with NNFMP; 08 Mar 2009 11:52:44 -0000 Received: from [69.147.65.162] by t1.bullet.sp1.yahoo.com with NNFMP; 08 Mar 2009 11:52:44 -0000 Received: from [127.0.0.1] by omp407.mail.sp1.yahoo.com with NNFMP; 08 Mar 2009 11:52:44 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 58199.72495.bm@omp407.mail.sp1.yahoo.com Received: (qmail 99160 invoked by uid 60001); 8 Mar 2009 11:52:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1236513163; bh=BYfgUIvcDsH70f0nia4dzwiSQP1242LkUENeRE/Crhg=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=tqho1tKKvEugz8Sh3LMaAhEAXNvExz0xczpyOPBNbGo19GcbLZQ2b1M+S7clLRO5YuV9ttBgR9nXl8mBNo8gyvRX1S/Rvmx2pcXjIzgU75/7rFhcDM4HIIYwXuGeOceyd6mvvdg00JyxasU9fSNoZYuHVqJduEYYmZ3L2DEeVNs= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=aTJ3kjpkmJtkb2EzT/JLaRBbRBMh1HYsAHH3K6tcMYiL+ehV1dcY3Yc1G8ctu7IqprXQCt4pdcTSJscwqboyPsWJ3ozRoizrudoqrjapHyAiU/EzAILRa2T1sXubWAA2GCiI9J9hCDplTJ1ifefjcDDH6Wq6j1WLc7042xavnLg=; Message-ID: <867767.97780.qm@web45903.mail.sp1.yahoo.com> X-YMail-OSG: msaE9dIVM1mprEAkZUdInwpBseKDS5pnW4eOzfrfNbwBY37DVNTk3P45U0OdWBIvrSzg9zTg8RAJmYK3d4AWlUkLH_2wMM8TNr85ooHuWEF0jQlGVMAr578zpEqEYC.9qUE2Ww1n_3p2.ma0Fymi0qF1Ll3MBTBTbVRjfignzMeTeq30wSyYHvHoz4l16iNV9Yi9cKXfOHZEtbqG_HYC0c0NEt8H74vQCNeNYRl_fhLs_i2gRLQSg7Nv3lQIEDIrY2AXQX0.YmrC Received: from [67.233.182.106] by web45903.mail.sp1.yahoo.com via HTTP; Sun, 08 Mar 2009 04:52:43 PDT X-Mailer: YahooMailClassic/5.1.18 YahooMailWebService/0.7.289.1 Date: Sun, 8 Mar 2009 04:52:43 -0700 (PDT) From: John Edward To: jeedward@yahoo.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-644000141-1236513163=:97780" X-Mailman-Approved-At: Mon, 09 Mar 2009 14:02:01 -0700 Subject: [Mip4] Draft paper submission deadline extended (will not be extended further): HPCNCS-09 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2009 11:52:12 -0000 --0-644000141-1236513163=:97780 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Draft paper submission deadline extended (will not be extended further): HP= CNCS-09 =A0 *Apologies if you receive multiple copies of this email. Please forward to = interested people.* =A0 The deadline for draft paper submission at the 2009 International Conferenc= e on High Performance Computing, Networking and Communication Systems (HPCN= CS-09) (website: http://www.PromoteResearch.org ) is extended due to numero= us requests from the authors. The conference will be held during July 13-16= 2009 in Orlando, FL, USA. We invite draft paper submissions. The conferenc= e will take place at the same time and venue where several other internatio= nal conferences are taking place. The other conferences include: =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Artificial Intellig= ence and Pattern Recognition (AIPR-09)=20 =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Automation, Robotic= s and Control Systems (ARCS-09) =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Bioinformatics, Com= putational Biology, Genomics and Chemoinformatics (BCBGC-09)=20 =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Enterprise Informat= ion Systems and Web Technologies (EISWT-09) =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Information Securit= y and Privacy (ISP-09) =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Recent Advances in = Information Technology and Applications (RAITA-09) =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Software Engineerin= g Theory and Practice (SETP-09)=20 =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Theory and Applicat= ions of Computational Science (TACS-09) =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Theoretical and Mat= hematical Foundations of Computer Science (TMFCS-09) =A0 The website http://www.PromoteResearch.org contains more details. =A0 Sincerely John Edward Publicity committee =A0 =A0 =A0=0A=0A=0A --0-644000141-1236513163=:97780 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable

Draft paper submission deadline extend= ed (will not be extended further): HPCNCS-09

 

*Apologies if you receive multiple copies of this email. Please forwar= d to interested people.*

 

The deadline for draft paper submission at the 2009 International Conference on High Performance Computing, Networki= ng and Communication Systems (HPCNCS-09) (website: http://www.PromoteResearch.or= g ) is extended due to numerous requests= from the authors. The conference will be held during July 13-16 2009 in Or= lando, FL, USA. We invite draft paper submissions. The conference will take place at the same time and ven= ue where several other international conferences are taking place. The othe= r conferences include:

=B7         <= /FONT>

=B7         =B7         =B7         =B7         =B7         =B7         =B7         =B7          

The website http://www.PromoteResearch.org<= SPAN style=3D"mso-bookmark: OLE_LINK4"> contains more details.

 

Sincerely

John Edward

Publicity committee

 

 

 


=0A=0A = --0-644000141-1236513163=:97780-- From sunseawq@huawei.com Mon Mar 9 18:06:22 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B63FC28C11C for ; Mon, 9 Mar 2009 18:06:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.246 X-Spam-Level: X-Spam-Status: No, score=-0.246 tagged_above=-999 required=5 tests=[AWL=0.249, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9d5d7KwWt4z for ; Mon, 9 Mar 2009 18:06:22 -0700 (PDT) Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 9F2143A6CC8 for ; Mon, 9 Mar 2009 18:06:18 -0700 (PDT) Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KG900EKON360Q@szxga02-in.huawei.com> for mip4@ietf.org; Tue, 10 Mar 2009 09:06:42 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KG9001NRN36OM@szxga02-in.huawei.com> for mip4@ietf.org; Tue, 10 Mar 2009 09:06:42 +0800 (CST) Received: from w53375a ([10.164.12.27]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KG90063TN35I7@szxml04-in.huawei.com> for mip4@ietf.org; Tue, 10 Mar 2009 09:06:42 +0800 (CST) Date: Tue, 10 Mar 2009 09:06:44 +0800 From: Qin Wu To: McCann Peter-A001034 , mip4@ietf.org Message-id: <009601c9a11c$7b11a540$1b0ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: Cc: Henrik Levkowetz Subject: Re: [Mip4] Agenda topics for IETF 74 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2009 01:06:22 -0000 Hi Peter and Henrik: May I ask a slot to discuss: MIP extension for ethernet service support The URL for the Internet draft is: http://tools.ietf.org/html/draft-wu-mip4-ether-00 Thanks! -Qin ----- Original Message ----- From: "McCann Peter-A001034" To: Cc: "Henrik Levkowetz" Sent: Monday, March 09, 2009 11:57 PM Subject: [Mip4] Agenda topics for IETF 74 > We will be meeting in San Francisco on Tuesday, March 24 2009, > for 2 hours from 1300 to 1500. If anyone has agenda items they > would like to discuss, please send e-mail ASAP to myself and > Henrik. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ From denghui02@gmail.com Mon Mar 9 20:40:27 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4276C3A6C8A for ; Mon, 9 Mar 2009 20:40:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.034 X-Spam-Level: X-Spam-Status: No, score=-2.034 tagged_above=-999 required=5 tests=[AWL=0.565, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ou41mpqn8sMx for ; Mon, 9 Mar 2009 20:40:26 -0700 (PDT) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by core3.amsl.com (Postfix) with ESMTP id 627FE3A6C83 for ; Mon, 9 Mar 2009 20:40:26 -0700 (PDT) Received: by wf-out-1314.google.com with SMTP id 27so2276503wfd.31 for ; Mon, 09 Mar 2009 20:41:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=c/IsSHiEO9Z4aGv0jGj3K8iFyE6F5wRxZS2HPr5c+DU=; b=FkxRNdJn8MM7A5tP1srws4iYV9Jo01Omx17ZXN2DIRl6C7AxN9nGErjvAILfLXfW5p ampvDAMemihi28oO06Wz+TWIy7zSdIX+SJxQhYiUqAgZXyzKn9JeDZvTtdE9X8WSQ9Ct oGz+p3VMdUlbC6TDvzINFJp7hV3A+fQVeBoxo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xz6XeyLIQoHmytAwQDsdckjR/Tzs4qW6YG9uclbuhATBxzv7GjiZMOE1nLYJSEy6UV c5rqSYlG+clHqodNcFe8haCNfE/71je0a+NbB/8knZoE7Os4olNx3JsFIVifsn+mxvfQ xwEDWu76WOAjxH9rKnRxuEniCoOhY23LREk6s= MIME-Version: 1.0 Received: by 10.142.51.4 with SMTP id y4mr2852873wfy.303.1236656461039; Mon, 09 Mar 2009 20:41:01 -0700 (PDT) In-Reply-To: References: Date: Tue, 10 Mar 2009 11:41:01 +0800 Message-ID: <1d38a3350903092041q3853a1d1v13a84e08b63c2cac@mail.gmail.com> From: Hui Deng To: McCann Peter-A001034 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Agenda topics for IETF 74 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2009 03:40:27 -0000 Hi, Peter and Henrik, Peny has helped to update the draft to describe HA not supporting DHCP rela= y. http://tools.ietf.org/html/draft-deng-mip4-host-configuration-01 If possible, could you help to allocate a time slot for presentation, Many thanks -Hui 2009/3/9 McCann Peter-A001034 : > We will be meeting in San Francisco on Tuesday, March 24 2009, > for 2 hours from 1300 to 1500. =A0If anyone has agenda items they > would like to discuss, please send e-mail ASAP to myself and > Henrik. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > =A0 =A0Web interface: https://www.ietf.org/mailman/listinfo/mip4 > =A0 =A0 Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From tsirtsis@googlemail.com Tue Mar 10 03:57:40 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B14D328C155 for ; Tue, 10 Mar 2009 03:57:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.887 X-Spam-Level: X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YnexvYxu01tY for ; Tue, 10 Mar 2009 03:57:39 -0700 (PDT) Received: from mail-bw0-f178.google.com (mail-bw0-f178.google.com [209.85.218.178]) by core3.amsl.com (Postfix) with ESMTP id 8307D28C14B for ; Tue, 10 Mar 2009 03:57:39 -0700 (PDT) Received: by bwz26 with SMTP id 26so1524390bwz.37 for ; Tue, 10 Mar 2009 03:58:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=flmBWR0KyIwDpZ7Xi6B/EUytc1ZVQX/qYh9eFT3pCwQ=; b=IpTrPTlzhFGrM3UnCcz+WC+EsdvP7Y3qne3o8UrhDDviU8LpEZGm38aY++QYBZoW2i ZaXbUlTeW2YfSC9kljsVRxzyNlNwnIV1FpQoTxNwdbcGaSRpKby4yGqYrVnqH2By0dmK 5utvJCpL4CAETCnt1HP/rw163lPmzxBpdyxuE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=RpgIcoWBRMMtXhfjrpAekoXV76O5zBP83FHp4tRkoYU3F1e7q5IW1XJItg/cmYnYgj rfOgFjI1xZZ5ZPAil+TaIhVj6PQ2JRNQPqY2EB8l0FjVaZW5n8PUcHq9LpX2Ocw3nZLC xDZkigXqMQfshVDvph/rBkqg3EZ/N1ID2QTqk= MIME-Version: 1.0 Received: by 10.103.160.3 with SMTP id m3mr3189976muo.25.1236682693607; Tue, 10 Mar 2009 03:58:13 -0700 (PDT) In-Reply-To: References: Date: Tue, 10 Mar 2009 10:58:13 +0000 Message-ID: From: George Tsirtsis To: McCann Peter-A001034 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Agenda topics for IETF 74 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2009 10:57:40 -0000 I think it would be useful to discuss MIPv4 versions of MCoA and Flow Movement described in the following drafts: http://tools.ietf.org/html/draft-gundavelli-mip4-multiple-tunnel-support-00 http://tools.ietf.org/html/draft-tsirtsis-mip4-flowmove-01 Maybe a 10-15min slot to gauge interest and discuss how to proceed e.g., follow the MEXT way of having 3 different drafts for this or do a single draft based possibly on the above two. Thanks George On Mon, Mar 9, 2009 at 3:57 PM, McCann Peter-A001034 wrote: > We will be meeting in San Francisco on Tuesday, March 24 2009, > for 2 hours from 1300 to 1500. =C2=A0If anyone has agenda items they > would like to discuss, please send e-mail ASAP to myself and > Henrik. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > =C2=A0 =C2=A0Web interface: https://www.ietf.org/mailman/listinfo/mip4 > =C2=A0 =C2=A0 Charter page: http://www.ietf.org/html.charters/mip4-charte= r.html > Supplemental site: http://www.mip4.org/ > From antti.makela@teliasonera.com Tue Mar 10 04:14:36 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA67A3A6D08 for ; Tue, 10 Mar 2009 04:14:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.555 X-Spam-Level: X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[AWL=0.744, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2BGp5zqOj3Fl for ; Tue, 10 Mar 2009 04:14:29 -0700 (PDT) Received: from smtp.tele.fi (smtp.tele.fi [192.89.123.25]) by core3.amsl.com (Postfix) with ESMTP id 6563C3A6CB6 for ; Tue, 10 Mar 2009 04:14:29 -0700 (PDT) X-Originating-Ip: [192.194.74.130] Received: from lohi.mit.sonera.com (lohi.mit.sonera.com [192.194.74.130]) by smtp.tele.fi (Postfix) with ESMTP id 74A00BA55; Tue, 10 Mar 2009 13:14:19 +0200 (EET) Received: from lohi.mit.sonera.com (localhost [127.0.0.1]) by lohi.mit.sonera.com (Postfix) with ESMTP id EABD08DC30; Tue, 10 Mar 2009 13:14:13 +0200 (EET) Received: from suutari.mit.sonera.com (suutari.mit.sonera.com [194.142.21.7]) by lohi.mit.sonera.com (Postfix) with ESMTP id D32DA8DC2F; Tue, 10 Mar 2009 13:14:13 +0200 (EET) Received: from suutari.mit.sonera.com (suutari.mit.sonera.com [194.142.21.7]) by suutari.mit.sonera.com (Postfix) with ESMTP id AAFA1C2E2A; Tue, 10 Mar 2009 13:14:13 +0200 (EET) Date: Tue, 10 Mar 2009 13:14:13 +0200 (EET) From: =?ISO-8859-1?Q?Antti_M=E4kel=E4?= X-X-Sender: makelan2@suutari.mit.sonera.com To: McCann Peter-A001034 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1899886827-509914101-1236683589=:19351" Content-ID: X-Virus-Scanned: ClamAV using ClamSMTP Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Agenda topics for IETF 74 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2009 11:14:36 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1899886827-509914101-1236683589=:19351 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: Depends on how much reminding the WG needs on individual drafts for the recharter discussion. I'm assuming there is going to be rather long discussion about potential drafts (and humming when appropriate :)). I won't be present at Frisco (will participate via Jabber). If necessary, I can prepare some slides about current state and plans for -04 (or ietf-00) of http://tools.ietf.org/html/draft-makela-mip4-nemo-haaro-03 - Jouni can present them. On Mon, 9 Mar 2009, McCann Peter-A001034 wrote: > > We will be meeting in San Francisco on Tuesday, March 24 2009, > for 2 hours from 1300 to 1500. If anyone has agenda items they > would like to discuss, please send e-mail ASAP to myself and > Henrik. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > -- - Antti Mäkelä | Senior Network Architect | +358 2040 21613 - - TeliaSonera Corporation - ---1899886827-509914101-1236683589=:19351-- From pete.mccann@motorola.com Thu Mar 12 07:58:30 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83F173A6A4A for ; Thu, 12 Mar 2009 07:58:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.571 X-Spam-Level: X-Spam-Status: No, score=-6.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xcTQP6BUa3Pm for ; Thu, 12 Mar 2009 07:58:29 -0700 (PDT) Received: from mail153.messagelabs.com (mail153.messagelabs.com [216.82.253.51]) by core3.amsl.com (Postfix) with ESMTP id B3D4D3A6826 for ; Thu, 12 Mar 2009 07:58:29 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-5.tower-153.messagelabs.com!1236869945!10180337!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [136.182.1.13] Received: (qmail 2651 invoked from network); 12 Mar 2009 14:59:06 -0000 Received: from motgate3.mot.com (HELO motgate3.mot.com) (136.182.1.13) by server-5.tower-153.messagelabs.com with AES256-SHA encrypted SMTP; 12 Mar 2009 14:59:06 -0000 Received: from il27exr02.cig.mot.com (il27exr02.mot.com [10.17.196.71]) by motgate3.mot.com (8.14.3/8.14.3) with ESMTP id n2CEx5o9016106 for ; Thu, 12 Mar 2009 07:59:05 -0700 (MST) Received: from az10vts04.mot.com (il27vts04.cig.mot.com [10.17.196.88]) by il27exr02.cig.mot.com (8.13.1/Vontu) with SMTP id n2CEx5Ze012408 for ; Thu, 12 Mar 2009 09:59:05 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il27exr02.cig.mot.com (8.13.1/8.13.0) with ESMTP id n2CEx46J012404 for ; Thu, 12 Mar 2009 09:59:05 -0500 (CDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 12 Mar 2009 10:59:03 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Draft Agenda Posted thread-index: AcmjIxWRkb8S2Z/AQcOIMouDtBwUqw== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: Henrik Levkowetz Subject: [Mip4] Draft Agenda Posted X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2009 14:58:30 -0000 A draft agenda for our meeting in San Francisco is available here: http://www.ietf.org/proceedings/09mar/agenda/mip4.txt Please, agenda bash now. -Pete From web-usrn@ISI.EDU Sun Mar 15 11:27:25 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1ADE028C0E5 for ; Sun, 15 Mar 2009 11:27:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.249 X-Spam-Level: X-Spam-Status: No, score=-17.249 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fR0yfAUIBflr for ; Sun, 15 Mar 2009 11:27:24 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 1E03128C0CE for ; Sun, 15 Mar 2009 11:27:24 -0700 (PDT) Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2FIRWOB013128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 15 Mar 2009 11:27:32 -0700 (PDT) Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n2FIRUD5013127; Sun, 15 Mar 2009 11:27:30 -0700 (PDT) Date: Sun, 15 Mar 2009 11:27:30 -0700 (PDT) Message-Id: <200903151827.n2FIRUD5013127@boreas.isi.edu> To: tsirtsis@googlemail.com, vpark@qualcomm.com, hesham@elevatemobile.com, rdroms@cisco.com, jari.arkko@piuha.net, townsley@cisco.com, henrik@levkowetz.com, pete.mccann@motorola.com From: RFC Errata System X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: web-usrn@boreas.isi.edu X-Mailman-Approved-At: Sun, 15 Mar 2009 11:35:33 -0700 Cc: ah@TR-Sys.de, mip4@ietf.org, rfc-editor@rfc-editor.org Subject: [Mip4] [Technical Errata Reported] RFC5454 (1718) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Mar 2009 18:27:25 -0000 The following errata report has been submitted for RFC5454, "Dual-Stack Mobile IPv4". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5454&eid=1718 -------------------------------------- Type: Technical Reported by: Alfred Hoenes Section: 2.1, pg.5 Original Text ------------- Prefix Length A sixteen-byte field containing the Mobile IPv6 Network Prefix; all insignificant (low-order) bits (beyond the Prefix Length) MUST be set to 0 by the originator of the option and ignored by the receiver. Mobile IPv6 Network Prefix A sixteen-byte field containing the Mobile IPv6 Network Prefix Corrected Text -------------- Prefix Length | Indicates the prefix length of the prefix included in the Mobile | IPv6 Network Prefix field. A value of 255 indicates that a link- | local address is included in the Mobile IPv6 Network Prefix field. Mobile IPv6 Network Prefix | A sixteen-byte field containing the Mobile IPv6 Network Prefix; | all insignificant (low-order) bits (beyond the Prefix Length) MUST | be set to 0 by the originator of the option and ignored by the | receiver. Notes ----- The replacement text apparently has been placed into the wrong field explanation. The text presented for "Prefix Length" is the text that should be specified for "Mobile IPv6 Network Prefix"; the correct text for "Prefix Length" (as shown above) is borrowed from Section 2.2. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5454 (draft-ietf-mip4-dsmipv4-10) -------------------------------------- Title : Dual-Stack Mobile IPv4 Publication Date : March 2009 Author(s) : G. Tsirtsis, V. Park, H. Soliman Category : PROPOSED STANDARD Source : Mobility for IPv4 Area : Internet Stream : IETF Verifying Party : IESG From web-usrn@ISI.EDU Sun Mar 15 11:33:47 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 22F3F3A6359 for ; Sun, 15 Mar 2009 11:33:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.253 X-Spam-Level: X-Spam-Status: No, score=-17.253 tagged_above=-999 required=5 tests=[AWL=0.346, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZKqxdZ9m55l for ; Sun, 15 Mar 2009 11:33:46 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 2BEC73A67D7 for ; Sun, 15 Mar 2009 11:33:46 -0700 (PDT) Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2FIW6PC014842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 15 Mar 2009 11:32:07 -0700 (PDT) Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n2FIW67D014841; Sun, 15 Mar 2009 11:32:06 -0700 (PDT) Date: Sun, 15 Mar 2009 11:32:06 -0700 (PDT) Message-Id: <200903151832.n2FIW67D014841@boreas.isi.edu> To: tsirtsis@googlemail.com, vpark@qualcomm.com, hesham@elevatemobile.com, rdroms@cisco.com, jari.arkko@piuha.net, townsley@cisco.com, henrik@levkowetz.com, pete.mccann@motorola.com From: RFC Errata System X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: web-usrn@boreas.isi.edu X-Mailman-Approved-At: Sun, 15 Mar 2009 11:35:45 -0700 Cc: ah@TR-Sys.de, mip4@ietf.org, rfc-editor@rfc-editor.org Subject: [Mip4] [Editorial Errata Reported] RFC5454 (1719) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Mar 2009 18:33:47 -0000 The following errata report has been submitted for RFC5454, "Dual-Stack Mobile IPv4". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5454&eid=1719 -------------------------------------- Type: Editorial Reported by: Alfred Hoenes Section: 2.2, pg.7 Original Text ------------- The following values are defined for use as a Code value in the above extension: | 0 registration accepted, IPv6 to be tunneled to HoA | 1 registration accepted, IPv6 to be tunneled to CoA 8 registration rejected, reason unspecified 9 registration rejected, administratively prohibited Corrected Text -------------- The following values are defined for use as a Code value in the above extension: | 0 registration accepted, IPv6 will be tunneled to HoA | 1 registration accepted, IPv6 will be tunneled to CoA 8 registration rejected, reason unspecified 9 registration rejected, administratively prohibited Notes ----- Rationale: The extension described in this section is sent from the Home Agent to the Mobile Node and reflects the decisions made by the Home Agent. "to be tunnelled" could be misunderstood; the text should better be stated as a confirmation; hence s/to/will/. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5454 (draft-ietf-mip4-dsmipv4-10) -------------------------------------- Title : Dual-Stack Mobile IPv4 Publication Date : March 2009 Author(s) : G. Tsirtsis, V. Park, H. Soliman Category : PROPOSED STANDARD Source : Mobility for IPv4 Area : Internet Stream : IETF Verifying Party : IESG From web-usrn@ISI.EDU Sun Mar 15 11:40:15 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CC3C3A6A7E for ; Sun, 15 Mar 2009 11:40:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.256 X-Spam-Level: X-Spam-Status: No, score=-17.256 tagged_above=-999 required=5 tests=[AWL=0.343, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id crZKsbKmTCXc for ; Sun, 15 Mar 2009 11:40:09 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 97FC028C0FF for ; Sun, 15 Mar 2009 11:40:09 -0700 (PDT) Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2FIeWuP017483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 15 Mar 2009 11:40:33 -0700 (PDT) Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n2FIeW70017482; Sun, 15 Mar 2009 11:40:32 -0700 (PDT) Date: Sun, 15 Mar 2009 11:40:32 -0700 (PDT) Message-Id: <200903151840.n2FIeW70017482@boreas.isi.edu> To: tsirtsis@googlemail.com, vpark@qualcomm.com, hesham@elevatemobile.com, rdroms@cisco.com, jari.arkko@piuha.net, townsley@cisco.com, henrik@levkowetz.com, pete.mccann@motorola.com From: RFC Errata System X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: web-usrn@boreas.isi.edu X-Mailman-Approved-At: Mon, 16 Mar 2009 10:08:53 -0700 Cc: ah@TR-Sys.de, mip4@ietf.org, rfc-editor@rfc-editor.org Subject: [Mip4] [Editorial Errata Reported] RFC5454 (1720) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Mar 2009 18:40:15 -0000 The following errata report has been submitted for RFC5454, "Dual-Stack Mobile IPv4". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5454&eid=1720 -------------------------------------- Type: Editorial Reported by: Alfred Hoenes Section: 3.6,pp.13/14 Original Text ------------- When IPv6 runs over an IPv4 tunnel, the IPv6 tunnel endpoints can treat the IPv4 tunnel as a single hop link as defined in [RFC4213]. The two tunnel endpoints, e.g., mobile node and home agent, MUST configure link-local IPv6 addresses as defined in Section 3.7 of [RFC4213], while they MUST also adhere to the neighbor discovery requirements of the same specification, Section 3.8, and the hop | limit requirements of Section 3.3. Corrected Text -------------- When IPv6 runs over an IPv4 tunnel, the IPv6 tunnel endpoints can treat the IPv4 tunnel as a single hop link as defined in [RFC4213]. The two tunnel endpoints, e.g., mobile node and home agent, MUST configure link-local IPv6 addresses as defined in Section 3.7 of [RFC4213], while they MUST also adhere to the neighbor discovery requirements of the same specification, Section 3.8, and the hop | limit requirements of Section 3.3 in [RFC4213]. Notes ----- Rationale: The text should also make clear to which document (this RFC or RFC 4213) the last section number given refers. Pointing to RFC 4213 twice (but not in the final case) could be misunderstood, in particular due to the presence of the comma in front of the "and" in a two-item list. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5454 (draft-ietf-mip4-dsmipv4-10) -------------------------------------- Title : Dual-Stack Mobile IPv4 Publication Date : March 2009 Author(s) : G. Tsirtsis, V. Park, H. Soliman Category : PROPOSED STANDARD Source : Mobility for IPv4 Area : Internet Stream : IETF Verifying Party : IESG From tsirtsis@googlemail.com Mon Mar 16 05:53:14 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8ECC3A67ED for ; Mon, 16 Mar 2009 05:53:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.889 X-Spam-Level: X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OUZlJj0Fxc25 for ; Mon, 16 Mar 2009 05:53:13 -0700 (PDT) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.187]) by core3.amsl.com (Postfix) with ESMTP id 6D3563A677D for ; Mon, 16 Mar 2009 05:53:13 -0700 (PDT) Received: by fk-out-0910.google.com with SMTP id f33so1428671fkf.5 for ; Mon, 16 Mar 2009 05:53:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=oW277uSrKxy4iXibK57IJNXhuO8+mI01QDhsWAkuatk=; b=dWZHeF+aK6lKH7uDdwfKHV7SpoMaITd1p9gvh/PvZQLmY0nG0VGigPlxASvVf644Cl JTdWuU9LouEkkbJQ1j8zoMaEgwi3EkRLmDOlWzN5U1O/JBJzC2LJxCTA5uOhMlrHxXtn xtQ7y04qhZke+oUf+9A7VYpEEjh7Ua0u71XYs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=jav2n54ZTIZNTif2bRGc66qSV8f14WNyzvfPZByim5sYXc3OBDwQ8XexKcLFkGgqcj sFgTdCWUmdGq5jIyzKaTD2LsSkHMogvmXVuYNrIyn77sWvMVARv16dwKLuTrE6tU+FVk cQLVe3PERpnd49izBvYMM0BmKYzRd1UAIHCC8= MIME-Version: 1.0 Received: by 10.223.126.145 with SMTP id c17mr3146734fas.16.1237208034620; Mon, 16 Mar 2009 05:53:54 -0700 (PDT) In-Reply-To: <200903151827.n2FIRUD5013127@boreas.isi.edu> References: <200903151827.n2FIRUD5013127@boreas.isi.edu> Date: Mon, 16 Mar 2009 08:53:54 -0400 Message-ID: From: George Tsirtsis To: RFC Errata System Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Mon, 16 Mar 2009 10:08:53 -0700 Cc: ah@tr-sys.de, hesham@elevatemobile.com, pete.mccann@motorola.com, rdroms@cisco.com, mip4@ietf.org, jari.arkko@piuha.net, vpark@qualcomm.com, townsley@cisco.com, henrik@levkowetz.com Subject: Re: [Mip4] [Technical Errata Reported] RFC5454 (1718) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2009 12:53:14 -0000 I verify that this is indeed an error and I agree with the proposed fix. George On Sun, Mar 15, 2009 at 2:27 PM, RFC Errata System wrote: > > The following errata report has been submitted for RFC5454, > "Dual-Stack Mobile IPv4". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=3D5454&eid=3D1718 > > -------------------------------------- > Type: Technical > Reported by: Alfred Hoenes > > Section: 2.1, pg.5 > > Original Text > ------------- > =C2=A0 Prefix Length > > =C2=A0 =C2=A0 =C2=A0A sixteen-byte field containing the Mobile IPv6 Netwo= rk Prefix; > =C2=A0 =C2=A0 =C2=A0all insignificant (low-order) bits (beyond the Prefix= Length) MUST > =C2=A0 =C2=A0 =C2=A0be set to 0 by the originator of the option and ignor= ed by the > =C2=A0 =C2=A0 =C2=A0receiver. > > =C2=A0 Mobile IPv6 Network Prefix > > =C2=A0 =C2=A0 =C2=A0A sixteen-byte field containing the Mobile IPv6 Netwo= rk Prefix > > > Corrected Text > -------------- > =C2=A0 Prefix Length > > | =C2=A0 =C2=A0 Indicates the prefix length of the prefix included in the= Mobile > | =C2=A0 =C2=A0 IPv6 Network Prefix field. =C2=A0A value of 255 indicates= that a link- > | =C2=A0 =C2=A0 local address is included in the Mobile IPv6 Network Pref= ix field. > > =C2=A0 Mobile IPv6 Network Prefix > > | =C2=A0 =C2=A0 A sixteen-byte field containing the Mobile IPv6 Network P= refix; > | =C2=A0 =C2=A0 all insignificant (low-order) bits (beyond the Prefix Len= gth) MUST > | =C2=A0 =C2=A0 be set to 0 by the originator of the option and ignored b= y the > | =C2=A0 =C2=A0 receiver. > > Notes > ----- > The replacement text apparently has been placed into the wrong > field explanation. > The text presented for "Prefix Length" is the text that should > be specified for "Mobile IPv6 Network Prefix"; the correct text > for "Prefix Length" (as shown above) is borrowed from Section 2.2. > > Instructions: > ------------- > This errata is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC5454 (draft-ietf-mip4-dsmipv4-10) > -------------------------------------- > Title =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Dual-Stack Mobil= e IPv4 > Publication Date =C2=A0 =C2=A0: March 2009 > Author(s) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : G. Tsirtsis, V. Park, H. S= oliman > Category =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: PROPOSED STANDARD > Source =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Mobility for IPv= 4 > Area =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Internet > Stream =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: IETF > Verifying Party =C2=A0 =C2=A0 : IESG > From tsirtsis@googlemail.com Mon Mar 16 05:55:10 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 388163A6B14 for ; Mon, 16 Mar 2009 05:55:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.894 X-Spam-Level: X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sz8fa97t5s3D for ; Mon, 16 Mar 2009 05:55:09 -0700 (PDT) Received: from mail-bw0-f175.google.com (mail-bw0-f175.google.com [209.85.218.175]) by core3.amsl.com (Postfix) with ESMTP id 02BD33A677D for ; Mon, 16 Mar 2009 05:55:08 -0700 (PDT) Received: by bwz23 with SMTP id 23so939494bwz.37 for ; Mon, 16 Mar 2009 05:55:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=sCgVG3/A8aZH6zYgoax2TtD7O9oT8PacUKzl35BRgPo=; b=d+EjJgCbSd3ap066zxm8FR1r7BoR0kjUa3XQMXMMXvr5HI+fHO8vxh+AnXiEBR2UZV 2bTZFFfpOTDYzCLk7SFrJgONXMMcb6IEB7fgrJs24xUtRCMdbhxVzgAyVANQ+IPCBY0P VvytwPGt06LbVp9C42xe98UFFdgOJDs7wmqT8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=BlQ4uA6hOppHw41tuTT2uL7iaC/EK4v+8vpjE+niNnWZ5kBYu6UbrvX8bDuTf/LzyF 8tSWKfRQnxWsV/2MgzPoNirnr23P84bZk7aawH3lMI7a5O6onRaqpcTRLTryOVw0M8Sp q/MaMF4t7HoU6lWSxg7bzrRWBYy/ljg4AgjOM= MIME-Version: 1.0 Received: by 10.223.107.9 with SMTP id z9mr3145288fao.1.1237208149680; Mon, 16 Mar 2009 05:55:49 -0700 (PDT) In-Reply-To: <200903151832.n2FIW67D014841@boreas.isi.edu> References: <200903151832.n2FIW67D014841@boreas.isi.edu> Date: Mon, 16 Mar 2009 08:55:49 -0400 Message-ID: From: George Tsirtsis To: RFC Errata System Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Mon, 16 Mar 2009 10:08:53 -0700 Cc: ah@tr-sys.de, hesham@elevatemobile.com, pete.mccann@motorola.com, rdroms@cisco.com, mip4@ietf.org, jari.arkko@piuha.net, vpark@qualcomm.com, townsley@cisco.com, henrik@levkowetz.com Subject: Re: [Mip4] [Editorial Errata Reported] RFC5454 (1719) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2009 12:55:10 -0000 Personally I do not see a problem here but I am not against the proposed changed if others think the change makes the text clearer. George On Sun, Mar 15, 2009 at 2:32 PM, RFC Errata System wrote: > > The following errata report has been submitted for RFC5454, > "Dual-Stack Mobile IPv4". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=3D5454&eid=3D1719 > > -------------------------------------- > Type: Editorial > Reported by: Alfred Hoenes > > Section: 2.2, pg.7 > > Original Text > ------------- > =C2=A0 The following values are defined for use as a Code value in the ab= ove > =C2=A0 extension: > > | =C2=A0 =C2=A0 0 registration accepted, IPv6 to be tunneled to HoA > > | =C2=A0 =C2=A0 1 registration accepted, IPv6 to be tunneled to CoA > > =C2=A0 =C2=A0 =C2=A08 registration rejected, reason unspecified > > =C2=A0 =C2=A0 =C2=A09 registration rejected, administratively prohibited > > > Corrected Text > -------------- > =C2=A0 The following values are defined for use as a Code value in the ab= ove > =C2=A0 extension: > > | =C2=A0 =C2=A0 0 registration accepted, IPv6 will be tunneled to HoA > > | =C2=A0 =C2=A0 1 registration accepted, IPv6 will be tunneled to CoA > > =C2=A0 =C2=A0 =C2=A08 registration rejected, reason unspecified > > =C2=A0 =C2=A0 =C2=A09 registration rejected, administratively prohibited > > > Notes > ----- > Rationale: The extension described in this section is sent > from the Home Agent to the Mobile Node and reflects the decisions > made by the Home Agent. "to be tunnelled" could be misunderstood; > the text should better be stated as a confirmation; hence s/to/will/. > > Instructions: > ------------- > This errata is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC5454 (draft-ietf-mip4-dsmipv4-10) > -------------------------------------- > Title =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Dual-Stack Mobil= e IPv4 > Publication Date =C2=A0 =C2=A0: March 2009 > Author(s) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : G. Tsirtsis, V. Park, H. S= oliman > Category =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: PROPOSED STANDARD > Source =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Mobility for IPv= 4 > Area =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Internet > Stream =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: IETF > Verifying Party =C2=A0 =C2=A0 : IESG > From maselli@di.uniroma1.it Tue Mar 17 02:48:49 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC11A3A67DA; Tue, 17 Mar 2009 02:48:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.972 X-Spam-Level: X-Spam-Status: No, score=-1.972 tagged_above=-999 required=5 tests=[AWL=-2.377, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, SORTED_RECIPS=1.125] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qqtBsnYtEVEK; Tue, 17 Mar 2009 02:48:48 -0700 (PDT) Received: from mail2.di.uniroma1.it (mail2.di.uniroma1.it [151.100.17.20]) by core3.amsl.com (Postfix) with ESMTP id 34C843A697D; Tue, 17 Mar 2009 02:48:47 -0700 (PDT) Received: from [151.100.17.90] (maselli.di.uniroma1.it [151.100.17.90]) by mail2.di.uniroma1.it (Postfix) with ESMTP id 8BBD02E053; Tue, 17 Mar 2009 10:51:24 +0100 (CET) Message-ID: <49BF7226.5000400@di.uniroma1.it> Date: Tue, 17 Mar 2009 10:49:26 +0100 From: Gaia Maselli User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: it, it-it, en-us, en MIME-Version: 1.0 To: announce@ubicomp.lancs.ac.uk, cost290@cs.tut.fi, end2end-interest@postel.org, mip4@ietf.org, mycolleagues@grid.lrg.ufsc.br, p2prg@ietf.org, smac-users@mailman.isi.edu, tccc@lists.cs.columbia.edu, tcos-announce@tcos.org, ukubinet-announce@doc.ic.ac.uk Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 17 Mar 2009 07:12:12 -0700 Subject: [Mip4] IEEE SECON 2009: Call for Posters and Demo X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: maselli@di.uniroma1.it List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2009 09:48:50 -0000 (Apologies for cross posting.) === IEEE SECON 2009 Call for Posters and Demo http://www.ieee-secon.com/2009/ - Abstract submission due on: 4/20/2009 - Acceptance notification: May, 4, 2009 - Early registration due on: May 9, 2009 - Final abstract due on: May 9, 2009 IEEE SECON 2009 will include poster/demonstration sessions that shall provide a forum to present and discuss: works in progress, industry demonstrations of new applications and techniques, practical implementations, industrial and commercial developments, research testbeds and demonstrations, recent research/implementation results, upcoming research challenges, future directions, and novel approaches in the fields of sensor, mesh and ad hoc communications and networks. One of the key goals of this conference is to foster collaboration between industry and academia. Hence, participation of researchers/developers from industry and posters/demonstrations reporting joint work between industry and academia are especially encouraged. Submissions should be in the form of a proposal describing the main contributions of the poster/demo and the merits of the proposed ideas. If available, preliminary results can also be included. Proposals will be evaluated mainly based on their potential to stimulate interesting discussions, exchange of ideas and promote collaborations. Submissions should not be more than three pages (preferably IEEE conference format, 2-column) in length. Demonstration submissions should include the space requirements and/or any other equipment-specific requirements. The documents must contain the authors' names, affiliations, and contact information and the designated corresponding author. Accepted authors of posters/demos will have a space in the poster/demo session room to display their posters or exhibit their demos and describe their work in discussions with interested attendees. Moreover, the abstact of the accepted posters/demos will appear in IEEE Xplore. IEEE Communications Society policy states that all accepted IEEE SECON 2009 posters/demos require at least a one day registration. For authors co-authoring multiple posters/demos, a one day registration is valid for up to three presentations. In addition, there needs to be at least one person per poster/demo registered for one day by May 9, 2009 in order for the abstract to appear in IEEE Xplore. Please submit the proposal via EDAS at http://edas.info/7621. Any questions can be addressed to the Poster/Demo Co-Chairs, Antonio Capone (antonio.capone@polimi.it ) and Suman Banerjee (suman@cs.wisc.edu ). Antonio Capone and Suman Banerjee IEEE SECON 2009 Poster/Demo Co-Chairs From pete.mccann@motorola.com Mon Mar 23 08:17:50 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AEA83A6A7F for ; Mon, 23 Mar 2009 08:17:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yj+mIerQNgit for ; Mon, 23 Mar 2009 08:17:49 -0700 (PDT) Received: from mail153.messagelabs.com (mail153.messagelabs.com [216.82.253.51]) by core3.amsl.com (Postfix) with ESMTP id 72C813A6803 for ; Mon, 23 Mar 2009 08:17:49 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-13.tower-153.messagelabs.com!1237821514!10807523!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 10469 invoked from network); 23 Mar 2009 15:18:35 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-13.tower-153.messagelabs.com with AES256-SHA encrypted SMTP; 23 Mar 2009 15:18:35 -0000 Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.14.3/8.14.3) with ESMTP id n2NFIYg3000693 for ; Mon, 23 Mar 2009 08:18:34 -0700 (MST) Received: from il06vts03.mot.com (il06vts03.mot.com [129.188.137.143]) by il06exr04.mot.com (8.13.1/Vontu) with SMTP id n2NFIY2H029182 for ; Mon, 23 Mar 2009 10:18:34 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id n2NFIXmi029177 for ; Mon, 23 Mar 2009 10:18:34 -0500 (CDT) x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 23 Mar 2009 11:18:32 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Presentations Thread-Index: AcmryqDTMATaVqL2Q8u5Dy4mwPI9cw== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: henrik@levkowetz.com Subject: [Mip4] Presentations X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2009 15:17:50 -0000 To all those giving presentations tomorrow: please send in your presentation slides TODAY to me and Henrik. We prefer slides in PDF format so that they are accessible to the broadest possible audience. Thank you, -Pete From alexandru.petrescu@gmail.com Tue Mar 24 15:28:35 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 409493A6B45 for ; Tue, 24 Mar 2009 15:28:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.333 X-Spam-Level: X-Spam-Status: No, score=-1.333 tagged_above=-999 required=5 tests=[AWL=-0.573, BAYES_05=-1.11, HELO_EQ_FR=0.35] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hg0dvuEpuvfe for ; Tue, 24 Mar 2009 15:28:34 -0700 (PDT) Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id C865B3A6836 for ; Tue, 24 Mar 2009 15:28:32 -0700 (PDT) Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id EF3AAE080ED; Tue, 24 Mar 2009 23:29:18 +0100 (CET) Received: from [127.0.0.1] (bur91-3-82-239-213-32.fbx.proxad.net [82.239.213.32]) by smtp6-g21.free.fr (Postfix) with ESMTP id B6102E0801C; Tue, 24 Mar 2009 23:29:14 +0100 (CET) Message-ID: <49C95EB9.8000408@gmail.com> Date: Tue, 24 Mar 2009 23:29:13 +0100 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Alexandru Petrescu References: <499403FE.90807@gmail.com> In-Reply-To: <499403FE.90807@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 090323-0, 23/03/2009), Outbound message X-Antivirus-Status: Clean Cc: =?ISO-8859-1?Q?Antti_M=E4kel=E4?= , mip4@ietf.org, McCann Peter-A001034 , Henrik Levkowetz Subject: Re: [Mip4] Status update & Recharter effort X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2009 22:28:35 -0000 Alexandru Petrescu a écrit : > Antti Mäkelä a écrit : >> On Wed, 11 Feb 2009, McCann Peter-A001034 wrote: >> >>> draft-makela-mip4-nemo-haaro-03.txt This was presented at IETF-70 >>> and it looks like there have been a couple of revisions since. >>> Is there interest in working on it? Other comments? >> >> As the primary author :) I'll comment that I have been preparing >> for and will most likely (barring force majeure issues) start >> working towards my doctoral dissertation in the summer as soon as >> certain arrangements have been made. My topic will be covering the >> virtual operator model outlined in the first section of the draft. >> The work will be conducted as part of Finnish Future Internet >> project (http://futureinternet.fi/). Anyway, at least *I* will >> continue to have interest in developing this further - so I'm not >> just going to toss it to the WG and leave it at -00..as part of the >> work, there will be actual implementation coming up. >> >> Whether the draft is of interest to the IETF is of course another >> matter, but I do remember hearing some encouraging comments from >> the audience in Vancouver that this thing might actually have a >> business case :) > > This is certainly a draft worth following up closely, I can provide > comments on the mailing list as new versions come up. (sorry I wasn't in the mip4 jabber room). This nemo-haaro should be further pursued. I could come back later with further support but here goes the easiest. I some times deal with IPv4 moving networks in vehicles, very often connecting to a cell operator network. That network is very dumb in terms of IP mobility, although very high bandwidth. The type of services I'm considering offering to users involve continuous sessions. _If_ the operator offered this, and via short paths (not through HAs) then I'd have much less work to do deploying home agents, designing endpoint-based RO, etc. That's why I do support all initiative which may some day lead to a cell operator offering IP mobility, and RO, and for moving networks at the same time. But of course it should be identified, or reminded, what kind of RO is haaro, and how much applicability does it have to real deployments. Alex > Alex > >> >> >> ------------------------------------------------------------------------ >> >> >> >> -- Mip4 mailing list: Mip4@ietf.org Web interface: >> https://www.ietf.org/mailman/listinfo/mip4 Charter page: >> http://www.ietf.org/html.charters/mip4-charter.html Supplemental >> site: http://www.mip4.org/ > > > -- Mip4 mailing list: Mip4@ietf.org Web interface: > https://www.ietf.org/mailman/listinfo/mip4 Charter page: > http://www.ietf.org/html.charters/mip4-charter.html Supplemental > site: http://www.mip4.org/ > From antti.makela@teliasonera.com Wed Mar 25 00:51:29 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59EF93A67FE for ; Wed, 25 Mar 2009 00:51:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.927 X-Spam-Level: X-Spam-Status: No, score=-2.927 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itAaaHQeB8gA for ; Wed, 25 Mar 2009 00:51:28 -0700 (PDT) Received: from smtp.tele.fi (smtp.tele.fi [192.89.123.25]) by core3.amsl.com (Postfix) with ESMTP id 35E713A6965 for ; Wed, 25 Mar 2009 00:51:27 -0700 (PDT) X-Originating-Ip: [192.194.74.130] Received: from lohi.mit.sonera.com (lohi.mit.sonera.com [192.194.74.130]) by smtp.tele.fi (Postfix) with ESMTP id 04974912; Wed, 25 Mar 2009 09:52:04 +0200 (EET) Received: from lohi.mit.sonera.com (localhost [127.0.0.1]) by lohi.mit.sonera.com (Postfix) with ESMTP id C1B7E8DC27; Wed, 25 Mar 2009 09:51:59 +0200 (EET) Received: from suutari.mit.sonera.com (suutari.mit.sonera.com [194.142.21.7]) by lohi.mit.sonera.com (Postfix) with ESMTP id AA4588D7B7; Wed, 25 Mar 2009 09:51:59 +0200 (EET) Received: from suutari.mit.sonera.com (suutari.mit.sonera.com [194.142.21.7]) by suutari.mit.sonera.com (Postfix) with ESMTP id 87630C2E2A; Wed, 25 Mar 2009 09:51:59 +0200 (EET) Date: Wed, 25 Mar 2009 09:51:59 +0200 (EET) From: =?ISO-8859-1?Q?Antti_M=E4kel=E4?= X-X-Sender: makelan2@suutari.mit.sonera.com To: Alexandru Petrescu In-Reply-To: <49C95EB9.8000408@gmail.com> Message-ID: References: <499403FE.90807@gmail.com> <49C95EB9.8000408@gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1899886827-2069118430-1237967519=:2339" X-Virus-Scanned: ClamAV using ClamSMTP Cc: mip4@ietf.org, McCann Peter-A001034 , Henrik Levkowetz Subject: Re: [Mip4] Status update & Recharter effort X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Mar 2009 07:51:29 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1899886827-2069118430-1237967519=:2339 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Tue, 24 Mar 2009, Alexandru Petrescu wrote: > This nemo-haaro should be further pursued. I could come back later with > further support but here goes the easiest. > > I some times deal with IPv4 moving networks in vehicles, very often > connecting to a cell operator network. That network is very dumb in > terms of IP mobility, although very high bandwidth. The type of > services I'm considering offering to users involve continuous sessions. > _If_ the operator offered this, and via short paths (not through HAs) > then I'd have much less work to do deploying home agents, designing > endpoint-based RO, etc. > > That's why I do support all initiative which may some day lead to a cell > operator offering IP mobility, and RO, and for moving networks at the same > time. Hi, Thanks for support :) During the session (recharter discussion portion) there were some questions about on what's the use-case as it was still a bit unclear. Now, the use-case is right there in the first section of the draft for the explicit purpose of informing reader of that http://tools.ietf.org/html/draft-makela-mip4-nemo-haaro-03#page-4 However, I'll reiterate the points in the draft here, what were my original drivers for writing the draft. Unlike Alexandru, I originally didn't consider mobile networks in "traditional" sense at all (e.g. cell phone networks). And hoping this might garner enough interest that the WG could still consider taking this in... My original use case was simply this: You have a - Small company (not too much money to invest in infrastructure) with several sites or - Medium sized or large company with perhaps a HQ and several small branch/sales offices that need reliable connectivity. Anyway: You wish to have reliable, private connectivity between each site. Options: - You can get a dedicated line for each site from your friendly ISP (T1, Frame Relay, ATM, MPLS, you know). Pro: Reliable, guaranteed SLAs. Con: Costs a LOT. $$$$ issue. - You can get a consumer-grade ADSL/Cable/etc from a consumer-grade ISP for peanuts a month and run VPN on top of that. Pro: Cheap. Con: No guarantee of service, can go down at any time. Now, following this train of thought: What if you could bundle several of these cheap connections together, running a VPN on top, so that there would be a switchover if a single connection goes down? Consumer-grade DSL might be flaky but hey, if you have 3 consumer-grade connections from separate providers, they probably won't ALL be down at once. Most of the time. Problem: You really cannot run multihoming on top of consumer-grade connections. Try getting an AS number and BGP peering working over such a link... not going to happen. Without routing protocol, well, since IP addresses of *any* endpoint can change dynamically, you'd need some central point constantly reconfiguring the VPNs, at least if you are running full mesh. Enter Mobile IP, and replace the gateway routers at customer sites with Mobile Routers connecting to a central Home Agent. We've already done this (way back in '07) in lab with Cisco Mobile Routers (Non-nemo proprietary, no route optimization). In case of last-mile link failure, the switchover is immediate - you lose a few packets. If the failure happens further upstream, you need to wait for RFC 3519 keepalive to expire. However, even when running e.g. streaming application, you can just snap your fingers and the traffic comes in on the new connection. Problem sort of solved. New Problem: Once there's plenty of load, Home Agent becomes point of congestion since ALL traffic goes via the HA (star topology). Enter Route Optimization. Someone still needs to run that HA and provide it as a service. Enter "Virtual Operator ('ISP')". The HA is hosted at traditional High-Availability network. One HA can probably serve multiple customers. Business case: The local DSL/Cable/insert consumer connection providers who run bit-pipes can keep on selling bit-pipes. Each customer needs a few. Virtual Operator provides an overlay service that provides reliable site-to-site connectivity with cheap (consumer grade DSL cost times X) pricing. Bulk of the real load happens at the access operators networks. Home Agent handles mostly control traffic and few initial traffic flows before RO can kick in. Note that when I'm talking about customers, I mean corporations or similar entities (The ISP's customers). I'm not even mentioning *users*. What the draft provides: Means for Mobile Routers to discover other Mobile Routers (Since HA knows all MRs, it might as well relay that information to them), so they can establish direct MIP tunnels. Using this with a wireless network is obviously possibility. Cable/DSL are just the most traditional examples. In fact, the more technologies you can mash together the more independent the connections become (DSL from multiple operators probably goes through same wiring closet). So...if the above description manages to convice anyone that this might be a good idea to work on within the WG, would be nice :) -- - Antti Mäkelä | Senior Network Architect | +358 2040 21613 - - TeliaSonera Corporation - ---1899886827-2069118430-1237967519=:2339-- From alexandru.petrescu@gmail.com Wed Mar 25 08:43:56 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A41D33A683A for ; Wed, 25 Mar 2009 08:43:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.029 X-Spam-Level: X-Spam-Status: No, score=-2.029 tagged_above=-999 required=5 tests=[AWL=-0.080, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WOjF+PCvtFDh for ; Wed, 25 Mar 2009 08:43:55 -0700 (PDT) Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.1]) by core3.amsl.com (Postfix) with ESMTP id EA1443A6774 for ; Wed, 25 Mar 2009 08:43:52 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.0) with ESMTP id n2PFgpI8025974 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 25 Mar 2009 16:42:51 +0100 Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.2/8.14.2) with ESMTP id n2PFkxDf029721; Wed, 25 Mar 2009 16:46:59 +0100 (envelope-from alexandru.petrescu@gmail.com) Received: from [127.0.0.1] ([132.166.133.173]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id n2PFigpB030476; Wed, 25 Mar 2009 16:44:43 +0100 Message-ID: <49CA516A.6010501@gmail.com> Date: Wed, 25 Mar 2009 16:44:42 +0100 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Antti_M=E4kel=E4?= References: <499403FE.90807@gmail.com> <49C95EB9.8000408@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: mip4@ietf.org, McCann Peter-A001034 , Henrik Levkowetz Subject: Re: [Mip4] Status update & Recharter effort X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Mar 2009 15:43:56 -0000 Antti Mäkelä a écrit : > On Tue, 24 Mar 2009, Alexandru Petrescu wrote: > >> This nemo-haaro should be further pursued. I could come back later >> with further support but here goes the easiest. >> >> I some times deal with IPv4 moving networks in vehicles, very often >> connecting to a cell operator network. That network is very dumb >> in terms of IP mobility, although very high bandwidth. The type of >> services I'm considering offering to users involve continuous >> sessions. _If_ the operator offered this, and via short paths (not >> through HAs) then I'd have much less work to do deploying home >> agents, designing endpoint-based RO, etc. >> >> That's why I do support all initiative which may some day lead to a >> cell operator offering IP mobility, and RO, and for moving >> networks at the same time. > > Hi, > > Thanks for support :) > > During the session (recharter discussion portion) there were some > questions about on what's the use-case as it was still a bit unclear. > Now, the use-case is right there in the first section of the draft > for the explicit purpose of informing reader of that > > http://tools.ietf.org/html/draft-makela-mip4-nemo-haaro-03#page-4 That section's use-case - multi-homed fixed sites - is not relevant for the vehicular mobile router experimentations I'm considering. > However, I'll reiterate the points in the draft here, what were my > original drivers for writing the draft. Unlike Alexandru, I > originally didn't consider mobile networks in "traditional" sense at > all (e.g. cell phone networks). And hoping this might garner enough > interest that the WG could still consider taking this in... > > My original use case was simply this: > > You have a - Small company (not too much money to invest in > infrastructure) with several sites or - Medium sized or large company > with perhaps a HQ and several small branch/sales offices that need > reliable connectivity. > > Anyway: You wish to have reliable, private connectivity between each > site. > > Options: > > - You can get a dedicated line for each site from your friendly ISP > (T1, Frame Relay, ATM, MPLS, you know). Pro: Reliable, guaranteed > SLAs. Con: Costs a LOT. $$$$ issue. - You can get a consumer-grade > ADSL/Cable/etc from a consumer-grade ISP for peanuts a month and run > VPN on top of that. Pro: Cheap. Con: No guarantee of service, can go > down at any time. > > Now, following this train of thought: What if you could bundle > several of these cheap connections together, running a VPN on top, so > that there would be a switchover if a single connection goes down? > Consumer-grade DSL might be flaky but hey, if you have 3 > consumer-grade connections from separate providers, they probably > won't ALL be down at once. Most of the time. > > Problem: You really cannot run multihoming on top of consumer-grade > connections. Try getting an AS number and BGP peering working over > such a link... not going to happen. Without routing protocol, well, > since IP addresses of *any* endpoint can change dynamically, you'd > need some central point constantly reconfiguring the VPNs, at least > if you are running full mesh. > > Enter Mobile IP, and replace the gateway routers at customer sites > with Mobile Routers connecting to a central Home Agent. > > We've already done this (way back in '07) in lab with Cisco Mobile > Routers (Non-nemo proprietary, no route optimization). In case of > last-mile link failure, the switchover is immediate - you lose a few > packets. If the failure happens further upstream, you need to wait > for RFC 3519 keepalive to expire. However, even when running e.g. > streaming application, you can just snap your fingers and the traffic > comes in on the new connection. Problem sort of solved. > > New Problem: Once there's plenty of load, Home Agent becomes point of > congestion since ALL traffic goes via the HA (star topology). > > Enter Route Optimization. Someone still needs to run that HA and > provide it as a service. Enter "Virtual Operator ('ISP')". The HA is > hosted at traditional High-Availability network. One HA can probably > serve multiple customers. > > Business case: The local DSL/Cable/insert consumer connection > providers who run bit-pipes can keep on selling bit-pipes. Each > customer needs a few. Virtual Operator provides an overlay service > that provides reliable site-to-site connectivity with cheap (consumer > grade DSL cost times X) pricing. Bulk of the real load happens at > the access operators networks. Home Agent handles mostly control > traffic and few initial traffic flows before RO can kick in. > > Note that when I'm talking about customers, I mean corporations or > similar entities (The ISP's customers). I'm not even mentioning > *users*. > > What the draft provides: Means for Mobile Routers to discover other > Mobile Routers (Since HA knows all MRs, it might as well relay that > information to them), so they can establish direct MIP tunnels. > > Using this with a wireless network is obviously possibility. > Cable/DSL are just the most traditional examples. In fact, the more > technologies you can mash together the more independent the > connections become (DSL from multiple operators probably goes through > same wiring closet). > > So...if the above description manages to convice anyone that this > might be a good idea to work on within the WG, would be nice :) The motivation of using Mobile IP with sites where BGP would be used traditionally but couldn't because no AS number for a little ADSL consumer - makes some sense to me. This could be discussed further. For me it's difficult to advertise the use of Mobile IP protocol for sites which aren't moving. Maybe one day, when a definition of 'mobility' encompassing something else than a device handing over from one base station to another becomes more accepted. And, at the same time, it may happen that an RO scheme designed for MIP for fixed sites may be re-used for MIP for mobile devices - (like the DHCP method designed earlier for workstations is largely used for PDAs today.) Another motivation for MIP4 RO could be the easiness of using a Mobile Router in a moving entity, running both MIP4 and MIP6, and RO for MIP6 and RO for MIP4 - without having to implement a complex DSMIPv6 or DSMIPv4 RO. Alex From pete.mccann@motorola.com Fri Mar 27 10:04:02 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF85B3A6CA8 for ; Fri, 27 Mar 2009 10:04:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Py49qNzzWNTt for ; Fri, 27 Mar 2009 10:04:02 -0700 (PDT) Received: from mail55.messagelabs.com (mail55.messagelabs.com [216.82.241.163]) by core3.amsl.com (Postfix) with ESMTP id D06743A69C3 for ; Fri, 27 Mar 2009 10:04:01 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-2.tower-55.messagelabs.com!1238173495!38918093!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 2083 invoked from network); 27 Mar 2009 17:04:55 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-2.tower-55.messagelabs.com with AES256-SHA encrypted SMTP; 27 Mar 2009 17:04:55 -0000 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate8.mot.com (8.14.3/8.14.3) with ESMTP id n2RH4tPK002896 for ; Fri, 27 Mar 2009 10:04:55 -0700 (MST) Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141]) by il06exr02.mot.com (8.13.1/Vontu) with SMTP id n2RH4s4j024936 for ; Fri, 27 Mar 2009 12:04:54 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id n2RH4sop024932 for ; Fri, 27 Mar 2009 12:04:54 -0500 (CDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 27 Mar 2009 13:04:53 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Minutes uploaded Thread-Index: Acmu/iWyRDiuBoK4Qfev2BBR8TrAmA== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Subject: [Mip4] Minutes uploaded X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2009 17:04:03 -0000 The minutes have been uploaded and are available here: http://www.ietf.org/proceedings/09mar/minutes/mip4.txt Please review and send any corrections to the mip4 mailing list ASAP. Many thanks to George Tsirtsis for taking the notes. -Pete From sunseawq@huawei.com Fri Mar 27 10:59:23 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 570243A6CA6 for ; Fri, 27 Mar 2009 10:59:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shVNq6UC-+Ul for ; Fri, 27 Mar 2009 10:59:22 -0700 (PDT) Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 373B63A6A3C for ; Fri, 27 Mar 2009 10:59:22 -0700 (PDT) Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KH60055ZFCGBU@usaga01-in.huawei.com> for mip4@ietf.org; Fri, 27 Mar 2009 11:00:16 -0700 (PDT) Received: from jys8064005 (dhcp-16c8.meeting.ietf.org [130.129.22.200]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KH6006AQFCFJA@usaga01-in.huawei.com> for mip4@ietf.org; Fri, 27 Mar 2009 11:00:16 -0700 (PDT) Date: Fri, 27 Mar 2009 11:00:25 -0700 From: Qin Wu To: McCann Peter-A001034 , mip4@ietf.org Message-id: <037101c9af05$e7eebd50$b7468182@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: Cc: rahman@redback.com Subject: Re: [Mip4] Minutes uploaded X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2009 17:59:23 -0000 Hi,Pete: May I point out some nits as regarding the draft-wu-mip4-ether-00: Firstly, the people who comments on my draft "MIP extension for ethernet service support" is not someone but Shan Rahman from Redbak. Secondly, as regarding how it works in the PMIP scenarios, I have replied to Shah at that time and he has already understood. My answer at that time is the binding between the MN MAC address and FA CoA should be established in the Foreign Agent and the home agent. MAC address of MN should be carried over basic MIP4 message. Also I can't understand what the last question is? it said Each MAG has its own MAC address, You know what we talk about is MIP4 scenario in which the MAG does not exists. Thanks a lot! Regards! -Qin ----- Original Message ----- From: "McCann Peter-A001034" To: Sent: Friday, March 27, 2009 10:04 AM Subject: [Mip4] Minutes uploaded > The minutes have been uploaded and are available here: > > http://www.ietf.org/proceedings/09mar/minutes/mip4.txt > > Please review and send any corrections to the mip4 mailing > list ASAP. > > Many thanks to George Tsirtsis for taking the notes. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From sunseawq@huawei.com Fri Mar 27 15:42:30 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECD043A68F4 for ; Fri, 27 Mar 2009 15:42:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_72=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id um91T3HqwsK4 for ; Fri, 27 Mar 2009 15:42:29 -0700 (PDT) Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 6F9F83A6934 for ; Fri, 27 Mar 2009 15:42:29 -0700 (PDT) Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KH600AW6SGBDP@usaga01-in.huawei.com> for mip4@ietf.org; Fri, 27 Mar 2009 15:43:24 -0700 (PDT) Received: from jys8064005 (dhcp-16c8.meeting.ietf.org [130.129.22.200]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KH600E6USGACZ@usaga01-in.huawei.com> for mip4@ietf.org; Fri, 27 Mar 2009 15:43:23 -0700 (PDT) Date: Fri, 27 Mar 2009 15:43:31 -0700 From: Qin Wu To: McCann Peter-A001034 , George Tsirtsis Message-id: <060e01c9af2d$74e62a00$b7468182@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <037101c9af05$e7eebd50$b7468182@china.huawei.com> <050a01c9af27$12c11980$b7468182@china.huawei.com> Cc: mip4@ietf.org Subject: Re: [Mip4] Minutes uploaded X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2009 22:42:31 -0000 Hi,George and Peter I appreciate your understanding. Thanks! For the last three comments as regarding my draft, if my memory is correct, are described as follows: someone> I come from wimax background but I do not see a use case for this. You can probably do this with VSE if you really needed to do it. Howe it works for PMIP? Qin> It works for FA CoA mode and PMIP. The basic idea is to setup binding between the MN's MAC address and FA CoA in the FA and HA perspectively and carry ethernet packet over GRE tunnel between the FA and HA, deliver the specific ethernet Frame from the FA to the MN based on the binding between the MN's MAC address and FA CoA. someone>it seems not work for PMIP because MAGs have different MAC addresses <> Qin> The ethernet packet is not sent to the MAG but the Mobile node served by the MAG, So you needn't care about MAG's MAC address.<> Regards! -Qin ----- Original Message ----- From: "McCann Peter-A001034" To: "George Tsirtsis" ; "Qin Wu" Cc: Sent: Friday, March 27, 2009 3:24 PM Subject: RE: [Mip4] Minutes uploaded Indeed, please send comments and corrections to the mailing list and I will make appropriate changes. The minutes are not yet final. Sorry if that wasn't clear from my original message. -Pete George Tsirtsis wrote: > I can not recall but if that's the case I am sorry about that. > > This is why usually we have two minute takers. I wrote down what I > could and it is perfectly possible to have misheard, or > misinterpreted what I heard, or even missed something completely. In > any case you can point to the exact place of the minutes you want to > be changed and if no one has any objections, the minutes will be > changed as you request. > > At least this is my understanding of how minutes work in the IETF. > > George > > On Fri, Mar 27, 2009 at 2:57 PM, Qin Wu wrote: >> Hi, George: >> Thank for your clarification. >> What I am difficult to understand is: >> what someone said in the minutes is not what Rahman ask, also what I >> answered as regarding someone's question has not been reflected in >> the minutes. >> >> Regards! >> -Qin >> ----- Original Message ----- >> From: "George Tsirtsis" >> To: "Qin Wu" >> Cc: "McCann Peter-A001034" ; >> >> Sent: Friday, March 27, 2009 11:27 AM >> Subject: Re: [Mip4] Minutes uploaded >> >> >> Hi Qin, >> >> Sorry for calling Shah "Someone" but at the time I did not know his >> name...later on in the meeting I found out and started using his >> first >> name. This is the time of thing that one can catch with two minute >> takers instead of just one. >> >> BTW, the term "someone" is pretty common in minutes when the minute >> taker does not know the name of the speaker. >> >> Best Regards >> George >> >> On Fri, Mar 27, 2009 at 11:00 AM, Qin Wu wrote: >>> Hi,Pete: >>> May I point out some nits as regarding the draft-wu-mip4-ether-00: >>> Firstly, the people who comments on my draft "MIP extension for >>> ethernet service support" is not someone but Shan Rahman from >>> Redbak. >>> Secondly, as regarding how it works in the PMIP scenarios, I have >>> replied to Shah at that time and he has already understood. My >>> answer at that time is the binding between the MN MAC address and >>> FA CoA should be established in the Foreign Agent and the home >>> agent. MAC address of MN should be carried over basic MIP4 message. >>> Also I can't understand what the last question is? it said Each MAG >>> has its own MAC address, You know what we talk about is MIP4 >>> scenario in which the MAG does not exists. >>> Thanks a lot! >>> >>> Regards! >>> -Qin >>> ----- Original Message ----- >>> From: "McCann Peter-A001034" >>> To: >>> Sent: Friday, March 27, 2009 10:04 AM >>> Subject: [Mip4] Minutes uploaded >>> >>> >>>> The minutes have been uploaded and are available here: >>>> >>>> http://www.ietf.org/proceedings/09mar/minutes/mip4.txt >>>> >>>> Please review and send any corrections to the mip4 mailing list >>>> ASAP. >>>> >>>> Many thanks to George Tsirtsis for taking the notes. >>>> >>>> -Pete >>>> -- >>>> Mip4 mailing list: Mip4@ietf.org >>>> Web interface: https://www.ietf.org/mailman/listinfo/mip4 >>>> Charter page: http://www.ietf.org/html.charters/mip4-charter.html >>>> Supplemental site: http://www.mip4.org/ >>>> >>> -- >>> Mip4 mailing list: Mip4@ietf.org >>> Web interface: https://www.ietf.org/mailman/listinfo/mip4 >>> Charter page: http://www.ietf.org/html.charters/mip4-charter.html >>> Supplemental site: http://www.mip4.org/