From mip4-bounces@ietf.org Mon Oct 01 11:26:47 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IcNAQ-0004Sb-Pd; Mon, 01 Oct 2007 11:26:42 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IcNAP-0004SR-JK for mip4-confirm+ok@megatron.ietf.org; Mon, 01 Oct 2007 11:26:41 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IcNAP-0004SB-9E for Mip4@ietf.org; Mon, 01 Oct 2007 11:26:41 -0400 Received: from hydrogen.cen.brad.ac.uk ([143.53.238.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IcNAJ-0003pB-OY for Mip4@ietf.org; Mon, 01 Oct 2007 11:26:41 -0400 Received: from radon.cen.brad.ac.uk (radon.cen.brad.ac.uk [143.53.238.18]) by hydrogen.cen.brad.ac.uk (8.13.6/8.13.4) with ESMTP id l91FPWtb014455 for ; Mon, 1 Oct 2007 16:26:17 +0100 (BST) Received: from d212 (d212.inf.brad.ac.uk [143.53.29.36]) by radon.cen.brad.ac.uk (8.13.6/8.13.4) with SMTP id l91FNkKD016969 for ; Mon, 1 Oct 2007 16:23:47 +0100 (BST) Message-Id: <200710011523.l91FNkKD016969@radon.cen.brad.ac.uk> Date: Mon, 1 Oct 2007 16:23:47 +0100 From: "X.Jin" To: "Mip4" X-mailer: Foxmail 5.0 [en] Mime-Version: 1.0 X-Spam-Score: 2.8 (++) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f Cc: Subject: [Mip4] CFP -- PMEO-UCNS'08 to be held with IPDPS'08 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0012022176==" Errors-To: mip4-bounces@ietf.org --===============0012022176== Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 W1BsZWFzZSBhY2NlcHQgb3VyIGFwb2xvZ2llcyBpZiB5b3UgcmVjZWl2ZSBtdWx0aXBsZSBjb3Bp ZXMgb2YgdGhpcyBlbWFpbHNdDQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKg0KDQooU2VsZWN0ZWQgaGlnaC1xdWFsaXR5IHBhcGVy cyBmcm9tIHRoZSBQTUVPLVVDTlMnMDggd29ya3Nob3Agd2lsbCANCmFwcGVhciBpbiBhIFNwZWNp YWwgSXNzdWUgb2YgdGhlIGpvdXJuYWwgLSBJbnRlcm5hdGlvbmFsIEpvdXJuYWwgb2YgUGFyYWxs ZWwsIA0KRW1lcmdlbnQsIGFuZCBEaXN0cmlidXRlZCBTeXN0ZW1zIChJSlBFRFMpLCBUYXlsb3Ig JiBGcmFuY2lzIC0gDQpodHRwOi8vd3d3LnRhbmRmLmNvLnVrL2pvdXJuYWxzL3RpdGxlcy8xNzQ0 NTc2MC5hc3ApDQoNCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqDQoNCkNBTEwgRk9SIFBBUEVSUw0KDQoNCjd0aCBJbnRlcm5hdGlv bmFsIFdvcmtzaG9wIG9uIFBlcmZvcm1hbmNlIE1vZGVsaW5nLCBFdmFsdWF0aW9uLCBhbmQgDQpP cHRpbWl6YXRpb24gb2YgVWJpcXVpdG91cyBDb21wdXRpbmcgYW5kIE5ldHdvcmtlZCBTeXN0ZW1z IA0KKFBNRU8tVUNOU6GvMDgpDQoNClRvIGJlIGhlbGQgaW4gY29uanVuY3Rpb24gd2l0aCBJUERQ UycwOCAoU3VwcG9ydGVkIGJ5IElFRUUgQ29tcHV0ZXIgDQpTb2NpZXR5IGluIGNvb3BlcmF0aW9u IHdpdGggQUNNIFNJR0FSQ0gpLCAxNCAtMTggQXByaWwsIDIwMDgsIE1pYW1pLCANCkZsb3JpZGEs IFVTQQ0KDQpodHRwOi8vd3d3LmluZi5icmFkLmFjLnVrL35nbWluL1BNRU8tMDguaHRtbA0KaHR0 cDovL3d3dy5pcGRwcy5vcmcvaXBkcHMyMDA4LzIwMDhfd29ya3Nob3BzLmh0bWwNCg0KDQpTQ09Q RToNCg0KVGhlIHBlcmZvcm1hbmNlIG1vZGVsaW5nLCBldmFsdWF0aW9uLCBhbmQgb3B0aW1pemF0 aW9uIG9mIHViaXF1aXRvdXMgDQpjb21wdXRpbmcgYW5kIG5ldHdvcmtlZCBzeXN0ZW1zIGhhdmUg YmVlbiBhbiBpbXBvcnRhbnQgcmVzZWFyY2ggDQp0b3BpYyBvdmVyIHRoZSBwYXN0IHllYXJzIGFu ZCBwb3NlcyBjaGFsbGVuZ2luZyBwcm9ibGVtcyB0aGF0IHJlcXVpcmUgDQpuZXcgdG9vbHMgYW5k IG1ldGhvZHMgdG8ga2VlcCB1cCB3aXRoIHRoZSByYXBpZCBldm9sdXRpb24gYW5kIA0KaW5jcmVh c2luZyBjb21wbGV4aXR5IG9mIHN1Y2ggc3lzdGVtcy4gDQoNClRoaXMgd29ya3Nob3Agd2lsbCBi cmluZyB0b2dldGhlciBzY2llbnRpc3RzLCBlbmdpbmVlcnMsIHByYWN0aXRpb25lcnMsIGFuZCAN CmNvbXB1dGVyIHVzZXJzIHRvIHNoYXJlIGFuZCBleGNoYW5nZSB0aGVpciBleHBlcmllbmNlcywg ZGlzY3VzcyBjaGFsbGVuZ2VzLCANCmFuZCByZXBvcnQgc3RhdGUtb2YtdGhlLWFydCBhbmQgaW4t cHJvZ3Jlc3MgcmVzZWFyY2ggb24gYWxsIGFzcGVjdHMgb2YgDQpwZXJmb3JtYW5jZSBtb2RlbGlu ZywgZXZhbHVhdGlvbiwgYW5kIG9wdGltaXphdGlvbiBvZiB1YmlxdWl0b3VzIGNvbXB1dGluZyAN CmFuZCBuZXR3b3JrZWQgc3lzdGVtcy4gVGhlIHRvcGljcyBvZiBpbnRlcmVzdCBpbmNsdWRlLCBi dXQgYXJlIG5vdCBsaW1pdGVkIHRvOiANCg0KICAgIC0tIFByZWRpY3RpdmUgcGVyZm9ybWFuY2Ug bW9kZWxzIG9mIHViaXF1aXRvdXMgY29tcHV0aW5nIHN5c3RlbXMgDQogICAgLS0gUHJlZGljdGl2 ZSBwZXJmb3JtYW5jZSBtb2RlbHMgb2Ygd2lyZWQgYW5kIHdpcmVsZXNzIG5ldHdvcmtzDQogICAg LS0gUGVyZm9ybWFuY2UgbWVhc3VyZW1lbnQgYW5kIG1vbml0b3JpbmcgdG9vbHMgDQogICAgLS0g VHJhY2luZyBhbmQgdHJhY2UgYW5hbHlzaXMNCiAgICAtLSBTaW11bGF0aW9uDQogICAgLS0gQW5h bHl0aWNhbCBtb2RlbGluZw0KICAgIC0tIFNvZnR3YXJlIHRvb2xzIGZvciBzeXN0ZW0gcGVyZm9y bWFuY2UgYW5kIGV2YWx1YXRpb24NCiAgICAtLSBBdXRvbWF0aWMgcGVyZm9ybWFuY2UgYW5hbHlz aXMgDQogICAgLS0gUGVyZm9ybWFuY2UgY29tcGFyaXNvbg0KICAgIC0tIFBlcmZvcm1hbmNlIG9m IG1lbW9yeSBhbmQgSS9PIGludGVyY29ubmVjdA0KICAgIC0tIFBlcmZvcm1hbmNlIG9mIGNvbW11 bmljYXRpb24gbmV0d29ya3MgDQogICAgLS0gUGVyZm9ybWFuY2Ugb2YgbW9iaWxlIGRpc3RyaWJ1 dGVkIHN5c3RlbXMNCiAgICAtLSBQZXJmb3JtYW5jZSBhbmFseXNpcyBhbmQgZXZhbHVhdGlvbiBv ZiB1YmlxdWl0b3VzIGNvbXB1dGluZyBhbmQgDQogICAgICAgbmV0d29ya2VkIGFwcGxpY2F0aW9u cw0KICAgIC0tIEltcHJvdmVtZW50IGluIHN5c3RlbSBwZXJmb3JtYW5jZSB0aHJvdWdoIG9wdGlt aXphdGlvbiBhbmQgdHVuaW5nDQogICAgLS0gQ2FzZSBzdHVkaWVzIHNob3dpbmcgdGhlIHJvbGUg b2YgZXZhbHVhdGlvbiBpbiB0aGUgZGVzaWduIG9mIHN5c3RlbXMNCg0KDQpXT1JLU0hPUCBDTy1D SEFJUlM6DQoNCiAgICAgR2V5b25nIE1pbg0KICAgICBEZXBhcnRtZW50IG9mIENvbXB1dGluZw0K ICAgICBVbml2ZXJzaXR5IG9mIEJyYWRmb3JkDQogICAgIEJyYWRmb3JkLCBCRDcgMURQLCBVLksu IA0KICAgICBFLW1haWw6IGcubWluQGJyYWQuYWMudWsNCg0KICAgICBNb2hhbWVkIE91bGQtS2hh b3VhIA0KICAgICBEZXBhcnRtZW50IG9mIENvbXB1dGluZyBTY2llbmNlDQogICAgIFVuaXZlcnNp dHkgb2YgR2xhc2dvdyAgDQogICAgIEdsYXNnb3csIEcxMiA4UlosIFUuSy4NCiAgICAgRS1tYWls OiBtb2hhbWVkQGRjcy5nbGEuYWMudWsgICANCg0KDQpQUk9HUkFNIENIQUlSOg0KDQogICAgIEFo bWVkIFkuIEFsLUR1YmFpIA0KICAgICBTY2hvb2wgb2YgQ29tcHV0aW5nDQogICAgIE5hcGllciBV bml2ZXJzaXR5DQogICAgIEVkaW5idXJnaCwgRUgxMCA1RFQsIFUuSy4NCiAgICAgRS1tYWlsOiBB LkFsLUR1YmFpQG5hcGllci5hYy51aw0KDQoNClBVQkxJQ0lUWSBDTy1DSEFJUlM6DQoNCiAgICAg WGlhb2xvbmcgSmluDQogICAgIERlcGFydG1lbnQgb2YgQ29tcHV0aW5nDQogICAgIFVuaXZlcnNp dHkgb2YgQnJhZGZvcmQNCiAgICAgQnJhZGZvcmQsIEJENyAxRFAsIFUuSy4NCiAgICAgRS1tYWls OiB4LmppbkBicmFkLmFjLnVrDQoNCiAgICAgTWlyZWxhIFNlY2hpIE1vcmV0dGkgQW5ub25pIE5v dGFyZSANCiAgICAgQmFyZGRhbCBVbml2ZXJzaXR5DQogICAgIEZsb3JpYW5vcG9saXMsIFNDIEJy YXppbCANCiAgICAgRW1haWw6IG1pcmVsYUBiYXJkZGFsLmJyDQoNCg0KUFJPR1JBTSBDT01NSVRU RUU6DQogDQogICAgIEsuIEFsLUJlZ2FpbiwgVW5pdi4gb2YgR2xhbW9yZ2FuIChVSykNCiAgICAg SS4gUm9tZGhhbmksIE5hcGllciBVbml2ZXJzaXR5IChVSykNCiAgICAgSC4gUi4gQXJhYm5pYSwg VW5pdi4gb2YgR2VvcmdpYSAoVVNBKQ0KICAgICBELiBLLiBBcnZpbmQsIEVkaW5idXJnaCBVbml2 ZXJzaXR5IChVSykNCiAgICAgSS4gQXdhbiwgVW5pdi4gb2YgQnJhZGZvcmQgKFVLKQ0KICAgICBB LiBCb3VrZXJjaGUsIFVuaXYuIG9mIE5vcnRoIFRleGFzIChVU0EpDQogICAgIEouIEJyYWRsZXks IEltcGVyaWFsIENvbGxlZ2UgTG9uZG9uIChVSykNCiAgICAgUC4gQ29ja3Nob3R0LCBVbml2LiBv ZiBHbGFzZ293IChVSykNCiAgICAgTS4gQ29sYWphbm5pLCBVbml2LiBvZiBNb2RlbmEgKEl0YWx5 KQ0KICAgICBLLiBEYXksIFN1bHRhbiBRYWJvb3MgVW5pdi4gKE9tYW4pDQogICAgIEsuIERqZW1h bWUsIFVuaXYuIG9mIExlZWRzIChVSykNCiAgICAgVC4gRWwtR2hhemF3aSwgR2VvcmdlIFdhc2hp bmd0b24gVW5pdmVyc2l0eSAoVVNBKQ0KICAgICBSLiBGYXRvb2hpLCBTYW4gSm9zZSBTdGF0ZSBV bml2ZXJzaXR5IChVU0EpDQogICAgIE0uIEd1ZXJvdWksIFVuaXZlcnNpdHkgb2YgQ2VyZ3ktUG9u dG9pc2UgKEZyYW5jZSkgIA0KICAgICBTLiBIZWxhbCwgVW5pdmVyc2l0eSBvZiBGbG9yaWRhIChV U0EpDQogICAgIEguIEhhc3NhbmVpbiwgUXVlZW4ncyBVbml2ZXJzaXR5IChDYW5hZGEpDQogICAg IFMuIEphcnZpcywgVW5pdi4gb2YgV2Fyd2ljayAoVUspDQogICAgIEguIEthcmF0emEsIFVuaXYu IG9mIFRoZXNzYWxvbmlraSAoR3JlZWNlKQ0KICAgICBBLiBLYXRhbmd1ciwgVGV4YXMgQSZNIFVu aXYuIChVU0EpDQogICAgIEEuIEtob25zYXJpLCBJUE0gKElyYW4pDQogICAgIFcuIEtub3R0ZW5i ZWx0LCBJbXBlcmlhbCBDb2xsZWdlIExvbmRvbiAoVUspDQogICAgIEsuIExpLCBTdGF0ZSBVbml2 LiBvZiBOZXcgWW9yayBhdCBOZXcgUGFsdHogKFVTQSkNCiAgICAgSC4gTGl1LCBIdWF6aG9uZyBV bml2LiBvZiBTY2llbmNlIGFuZCBUZWNobm9sb2d5IChDaGluYSkgDQogICAgIFMuIExvdWNpZiwg TW9uY3RvbiBVbml2ZXJzaXR5LCAoQ2FuYWRhKQ0KICAgICBMLk0uIE1hY2tlbnppZSwgVW5pdi4g b2YgR2xhc2dvdyAoVUspDQogICAgIFkuIFBhbiwgR2VvcmdpYSBTdGF0ZSBVbml2LiAoVVNBKQ0K ICAgICBELiBLLiBQcmFkaGFuLCBVbml2LiBvZiBCcmlzdG9sIChVSykNCiAgICAgSC4gU2FyYmF6 aS1BemFkLCBTaGFyaWYgVW5pdi4gJiBJUE0gKElyYW4pDQogICAgIEEuIFNoYWhyYWJpLCBHbGFz Z293IENhbGVkb25pYW4gVW5pdi4gKFVLKQ0KICAgICBFLiBTb25nLCBIdWF6aG9uZyBVbml2LiBv ZiBTY2llbmNlIGFuZCBUZWNobm9sb2d5IChDaGluYSkgDQogICAgIE4uIFRob21hcywgVW5pdi4g b2YgTmV3Y2FzdGxlIChVSykNCiAgICAgQS4gVG91emVuZSwgU3VsdGFuIFFhYm9vcyBVbml2LiAo T21hbikgDQogICAgIE0uIFdvb2R3YXJkLCBVbml2LiBvZiBCcmFkZm9yZCAoVUspDQogICAgIEou IFd1LCBGbG9yaWRhIEF0bGFudGljIFVuaXYuIChVU0EpICANCiAgICAgTC4gWGlhbywgTWljaGln YW4gU3RhdGUgVW5pdi4gKFVTQSkNCiAgICAgVC4gWGllLCBTYW4gRGllZ28gU3RhdGUgVW5pdmVy c2l0eSAoVVNBKQ0KICAgICBMLiBULiBZYW5nLCBTdCBGcmFuY2lzIFhhdmllciBVbml2LiAoQ2Fu YWRhKQ0KICAgICBXLiBWYW5kZXJiYXV3aGVkZSwgVW5pdmVyc2l0eSBvZiBHbGFzZ293IChVSykN CiAgICAgVy4gQnVjaGFuYW4sIE5hcGllciBVbml2ZXJzaXR5IChVSykNCiAgICAgQS4gWm9tYXlh LCBVbml2LiBvZiBTeWRuZXkgKEF1c3RyYWxpYSkNCiAgICAgICAgICAgICAgICAgICAgICAgDQoN ClBBUEVSIFNVQk1JU1NJT046DQoNCkF1dGhvcnMgYXJlIGludml0ZWQgdG8gc3VibWl0IG1hbnVz Y3JpcHRzIHJlcG9ydGluZyBvcmlnaW5hbCB1bnB1Ymxpc2hlZCANCnJlc2VhcmNoIGFuZCByZWNl bnQgZGV2ZWxvcG1lbnRzIGluIHRoZSB0b3BpY3MgcmVsYXRlZCB0byB0aGUgd29ya3Nob3AuIA0K VGhlIGxlbmd0aCBvZiB0aGUgcGFwZXJzIHNob3VsZCBub3QgZXhjZWVkIDggcGFnZXMgKElFRUUg Q29tcHV0ZXIgDQpTb2NpZXR5IFByb2NlZWRpbmdzIE1hbnVzY3JpcHRzIHN0eWxlOiB0d28gY29s dW1ucywgc2luZ2xlLXNwYWNlZCksIA0KaW5jbHVkaW5nIGZpZ3VyZXMgYW5kIHJlZmVyZW5jZXMs IHVzaW5nIDEwIGZvbnRzLCBhbmQgbnVtYmVyIGVhY2ggcGFnZS4gDQpQYXBlcnMgc2hvdWxkIGJl IHN1Ym1pdHRlZCBlbGVjdHJvbmljYWxseSBpbiBQREYgZm9ybWF0IChvciBwb3N0c2NyaXB0KSBi eSANCnNlbmRpbmcgaXQgYXMgYW4gZS1tYWlsIGF0dGFjaG1lbnQgdG8gQS5BbC1EdWJhaUBuYXBp ZXIuYWMudWsuIEFsbCBwYXBlcnMgDQp3aWxsIGJlIHBlZXIgcmV2aWV3ZWQgYW5kIHRoZSBjb21t ZW50cyB3aWxsIGJlIHByb3ZpZGVkIHRvIHRoZSBhdXRob3JzLiANClRoZSBhY2NlcHRlZCBwYXBl cnMgd2lsbCBiZSBwdWJsaXNoZWQgdG9nZXRoZXIgd2l0aCB0aG9zZSBvZiBvdGhlciBJUERQUycw OCANCndvcmtzaG9wcyBieSB0aGUgSUVFRSBDb21wdXRlciBTb2NpZXR5IFByZXNzLg0KDQoNCklN UE9SVEFOVCBEQVRFUzoNCg0KU3VibWlzc2lvbiBEZWFkbGluZTogT2N0b2JlciAyMSwgMjAwNw0K QXV0aG9yIE5vdGlmaWNhdGlvbjogRGVjZW1iZXIgMTEsIDIwMDcNCkZpbmFsIE1hbnVzY3JpcHQg RHVlOiBKYW51YXJ5IDI4LCAyMDA4DQoNCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQoNCg== --===============0012022176== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --===============0012022176==-- From mip4-bounces@ietf.org Tue Oct 02 13:10:48 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IclFz-0005Xn-Fl; Tue, 02 Oct 2007 13:10:03 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IclFy-0005X1-9F for mip4-confirm+ok@megatron.ietf.org; Tue, 02 Oct 2007 13:10:02 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IclFx-0005Wd-Ow for mip4@ietf.org; Tue, 02 Oct 2007 13:10:01 -0400 Received: from mail119.messagelabs.com ([216.82.241.179]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IclFx-0001r6-Cw for mip4@ietf.org; Tue, 02 Oct 2007 13:10:01 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-11.tower-119.messagelabs.com!1191345000!26012789!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 11210 invoked from network); 2 Oct 2007 17:10:00 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-11.tower-119.messagelabs.com with SMTP; 2 Oct 2007 17:10:00 -0000 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l92H9xwK010805 for ; Tue, 2 Oct 2007 10:09:59 -0700 (MST) Received: from il06vts02.mot.com (il06vts02.mot.com [129.188.137.142]) by il06exr02.mot.com (8.13.1/Vontu) with SMTP id l92H9x0R025082 for ; Tue, 2 Oct 2007 12:09:59 -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 l92H9wQT025069 for ; Tue, 2 Oct 2007 12:09: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 Subject: RE: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Date: Tue, 2 Oct 2007 13:09:57 -0400 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Thread-Index: Acf66c9woFfD8IV2STKswhXPshuUBwKLMfJg References: From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Reminder: this WGLC ends tomorrow, October 3rd. Please send statements of support / non-support for this draft to the list. If we do not see sufficient consensus in the WG the draft=20 will not be advanced. So far we have only gotten 1 comment in support of the draft. -Pete McCann Peter-A001034 wrote: > This message announces a 2-week working group last call on: >=20 > "Network Mobility (NEMO) Extensions for Mobile IPv4" > draft-ietf-mip4-nemo-v4-base-02.txt >=20 > The last call will end at 24:00 UTC on Wednesday, October 3rd 2007. >=20 > This document describes a protocol for supporting Mobile Networks > between a Mobile Router and a Home Agent by extending the Mobile IPv4 > protocol. A Mobile Router is responsible for the mobility of one or > more network segments or subnets moving together. The Mobile Router > hides its mobility from the nodes on the mobile network. The nodes > on the Mobile Network may be fixed in relationship to the Mobile > Router and may not have any mobility function. =20 >=20 > Extensions to Mobile IPv4 are introduced to support Mobile Networks. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-02.txt >=20 > Please respond to this working group last call: >=20 > * If you have no comments on the draft, and support its advancement, > simply respond with a line containing something like >=20 > "I support the advancement of this document to the IESG with a > request for publication as a Proposed Standard RFC." >=20 > If you have comments, please use a line similar to the one above, > and supplement this with your comments. >=20 >=20 > * If you *don't* support its advancement, respond with a line > containing something like the following, supplemented by your > comments - >=20 > "I don't support the advancement of this document to the IESG with > a request for publication as a Proposed Standard RFC, for the > following reasons:" > ... >=20 > Please direct all replies to the Mobile IPv4 mailing list, > mip4@ietf.org.=20 >=20 > -Pete & Henrik -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Tue Oct 02 20:05:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Icrk8-0002UO-Jg; Tue, 02 Oct 2007 20:05:36 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1Icrk8-0002UJ-5E for mip4-confirm+ok@megatron.ietf.org; Tue, 02 Oct 2007 20:05:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Icrk7-0002TH-Qh for mip4@ietf.org; Tue, 02 Oct 2007 20:05:35 -0400 Received: from wr-out-0506.google.com ([64.233.184.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Icrk1-0001JH-Ko for mip4@ietf.org; Tue, 02 Oct 2007 20:05:35 -0400 Received: by wr-out-0506.google.com with SMTP id 70so2215570wra for ; Tue, 02 Oct 2007 17:05:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=CMR66MGEuYiJGF/L/ZeiryKAAlATiwFuYzwLNyxo4wI=; b=hX0nAD+Eh4zEeqECcgTzDskRENw0ZMi/TnRbD0+e0pl4ZQXQv5FDsBKOgzoawMA1DqDbsuaqDdO7fr812cWNZghY0OLpZnx0HSEF8lxmjLhNA3NMWxxUAy3Q4cm6CWOthxCgb7DzPT7jcDdcctRMHAg18XmV5bm0+MoeI8mjHB0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sG1aUsvHc6etwMRExgsGgnPh/DQfeQ1BvrVCQaIL+0s4A/gZSVO0jr2A4HtyFT26ZyKwiTpquBCJTUOSWv7YcfKtqeC9sDwwv/nWjRjZzBcTlxkdf8Xr4g1YAjFx12dydjShDA+lGp6ek2meA9JFwdTVr7FGt5yoxvJRFxzSP6Y= Received: by 10.142.157.15 with SMTP id f15mr760088wfe.1191369918644; Tue, 02 Oct 2007 17:05:18 -0700 (PDT) Received: by 10.143.166.2 with HTTP; Tue, 2 Oct 2007 17:05:18 -0700 (PDT) Message-ID: <1d38a3350710021705y102537f2pdcb6b3e6bfabc4f3@mail.gmail.com> Date: Wed, 3 Oct 2007 08:05:18 +0800 From: "Hui Deng" To: mip4@ietf.org Subject: Re: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org I support the advancement of this document to the IESG with a request for publication as a Proposed Standard RFC." -Hui > > McCann Peter-A001034 wrote: > > This message announces a 2-week working group last call on: > > > > "Network Mobility (NEMO) Extensions for Mobile IPv4" > > draft-ietf-mip4-nemo-v4-base-02.txt > > > > The last call will end at 24:00 UTC on Wednesday, October 3rd 2007. > > > > This document describes a protocol for supporting Mobile Networks > > between a Mobile Router and a Home Agent by extending the Mobile IPv4 > > protocol. A Mobile Router is responsible for the mobility of one or > > more network segments or subnets moving together. The Mobile Router > > hides its mobility from the nodes on the mobile network. The nodes > > on the Mobile Network may be fixed in relationship to the Mobile > > Router and may not have any mobility function. > > > > Extensions to Mobile IPv4 are introduced to support Mobile Networks. > > > > A URL for this Internet-Draft is: > > > http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-02.txt > > > > Please respond to this working group last call: > > > > * If you have no comments on the draft, and support its advancement, > > simply respond with a line containing something like > > > > "I support the advancement of this document to the IESG with a > > request for publication as a Proposed Standard RFC." > > > > If you have comments, please use a line similar to the one above, > > and supplement this with your comments. > > > > > > * If you *don't* support its advancement, respond with a line > > containing something like the following, supplemented by your > > comments - > > > > "I don't support the advancement of this document to the IESG with > > a request for publication as a Proposed Standard RFC, for the > > following reasons:" > > ... > > > > Please direct all replies to the Mobile IPv4 mailing list, > > mip4@ietf.org. > > > > -Pete & Henrik > > > > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www1.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://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 03 02:45:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Icxz9-0006wD-7f; Wed, 03 Oct 2007 02:45:31 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1Icxz7-0006tI-Vq for mip4-confirm+ok@megatron.ietf.org; Wed, 03 Oct 2007 02:45:29 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Icxz2-0006HI-FZ for mip4@ietf.org; Wed, 03 Oct 2007 02:45:24 -0400 Received: from ind-iport-1.cisco.com ([64.104.129.195]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Icxz1-0005iQ-RG for mip4@ietf.org; Wed, 03 Oct 2007 02:45:24 -0400 X-IronPort-AV: E=Sophos;i="4.21,223,1188757800"; d="scan'208";a="89652928" Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by ind-iport-1.cisco.com with ESMTP; 04 Oct 2007 01:10:28 +0530 Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l936jLE3020811; Wed, 3 Oct 2007 14:45:21 +0800 Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l936jD7p002622; Wed, 3 Oct 2007 06:45:19 GMT Received: from xmb-hkg-416.apac.cisco.com ([64.104.123.88]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 3 Oct 2007 14:45:06 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Date: Wed, 3 Oct 2007 14:44:13 +0800 Message-ID: <35912544FC930E49BF20EF16C3EF276502AECE0D@xmb-hkg-416.apac.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Thread-Index: Acf66c9woFfD8IV2STKswhXPshuUBwKLMfJgABxrooA= References: From: "Yoshi Tsuda (yotsuda)" To: "McCann Peter-A001034" X-OriginalArrivalTime: 03 Oct 2007 06:45:06.0115 (UTC) FILETIME=[EEDC1130:01C80588] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15460.000 X-TM-AS-Result: No--30.932300-8.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2978; t=1191393921; x=1192257921; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=yotsuda@cisco.com; z=From:=20=22Yoshi=20Tsuda=20(yotsuda)=22=20 |Subject:=20RE=3A=20[Mip4]=20WGLC=20for=20draft-ietf-mip4-nemo-v4-base-02 .txt=20 |Sender:=20; bh=EF1TAQMvJNOQGEUjL1si763dVy2xxI2SC3ciuVja11Y=; b=Tw9ORunD62C5Lf6gOA22SqbWVn2ld8yN+u2j8+JeQvP7JwjuHIIoau38nQ/BIh7swcwpM7ik FM0t3be/mZPK+VBTyqrENO773iqEZotBdXKkcGRZxNygEyVSG+a4kgw3hQsLDg4G7m1rgaTfkc ifp057YJ2LrWry5yT1ww9OLS8=; Authentication-Results: hkg-dkim-1; header.From=yotsuda@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi WG chair, "I support the advancement of this document to the IESG with a request for publication as a Proposed Standard RFC." Thanks. -Yoshi > -----Original Message----- > From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]=20 > Sent: Tuesday, October 02, 2007 10:10 AM > To: mip4@ietf.org > Subject: RE: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt=20 >=20 > Reminder: this WGLC ends tomorrow, October 3rd. Please send=20 > statements of support / non-support for this draft to the list. >=20 > If we do not see sufficient consensus in the WG the draft=20 > will not be advanced. So far we have only gotten 1 comment=20 > in support of the draft. >=20 > -Pete >=20 > McCann Peter-A001034 wrote: > > This message announces a 2-week working group last call on: > >=20 > > "Network Mobility (NEMO) Extensions for Mobile IPv4" > > draft-ietf-mip4-nemo-v4-base-02.txt > >=20 > > The last call will end at 24:00 UTC on Wednesday, October 3rd 2007. > >=20 > > This document describes a protocol for supporting Mobile Networks=20 > > between a Mobile Router and a Home Agent by extending the=20 > Mobile IPv4=20 > > protocol. A Mobile Router is responsible for the mobility=20 > of one or=20 > > more network segments or subnets moving together. The=20 > Mobile Router=20 > > hides its mobility from the nodes on the mobile network. =20 > The nodes on=20 > > the Mobile Network may be fixed in relationship to the Mobile > > Router and may not have any mobility function. =20 > >=20 > > Extensions to Mobile IPv4 are introduced to support Mobile Networks. > >=20 > > A URL for this Internet-Draft is: > > > http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-ba > se-02.txt > >=20 > > Please respond to this working group last call: > >=20 > > * If you have no comments on the draft, and support its advancement, > > simply respond with a line containing something like > >=20 > > "I support the advancement of this document to the IESG with a > > request for publication as a Proposed Standard RFC." > >=20 > > If you have comments, please use a line similar to the one above, > > and supplement this with your comments. > >=20 > >=20 > > * If you *don't* support its advancement, respond with a line > > containing something like the following, supplemented by your > > comments - > >=20 > > "I don't support the advancement of this document to=20 > the IESG with > > a request for publication as a Proposed Standard RFC, for the > > following reasons:" > > ... > >=20 > > Please direct all replies to the Mobile IPv4 mailing list,=20 > > mip4@ietf.org. > >=20 > > -Pete & Henrik >=20 >=20 >=20 > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www1.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ >=20 -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 03 04:32:41 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iczef-0005Ac-3K; Wed, 03 Oct 2007 04:32:29 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1Iczed-000547-EV for mip4-confirm+ok@megatron.ietf.org; Wed, 03 Oct 2007 04:32:27 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iczec-0004AN-FY for mip4@ietf.org; Wed, 03 Oct 2007 04:32:27 -0400 Received: from sehan001bb.han.telia.se ([131.115.18.152]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IczeR-0000Ig-Os for mip4@ietf.org; Wed, 03 Oct 2007 04:32:16 -0400 Received: from SEHAN021MB.tcad.telia.se ([131.115.18.160]) by sehan001bb.han.telia.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 3 Oct 2007 10:32:11 +0200 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Date: Wed, 3 Oct 2007 10:32:10 +0200 Message-ID: <59D7431DE2527D4CB0F1EFEDA5683ED30222D2D6@SEHAN021MB.tcad.telia.se> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Thread-Index: Acf66c9woFfD8IV2STKswhXPshuUBwKLMfJgACBE3xA= References: From: To: , X-OriginalArrivalTime: 03 Oct 2007 08:32:11.0778 (UTC) FILETIME=[E4DA6E20:01C80597] X-Spam-Score: 0.0 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org I support advancing this draft. Cheers, Jouni > -----Original Message----- > From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]=20 > Sent: Tuesday, October 02, 2007 8:10 PM > To: mip4@ietf.org > Subject: RE: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt=20 >=20 >=20 > Reminder: this WGLC ends tomorrow, October 3rd. Please send=20 > statements of support / non-support for this draft to the list. >=20 > If we do not see sufficient consensus in the WG the draft=20 > will not be advanced. So far we have only gotten 1 comment=20 > in support of the draft. >=20 > -Pete >=20 > McCann Peter-A001034 wrote: > > This message announces a 2-week working group last call on: > >=20 > > "Network Mobility (NEMO) Extensions for Mobile IPv4" > > draft-ietf-mip4-nemo-v4-base-02.txt > >=20 > > The last call will end at 24:00 UTC on Wednesday, October 3rd 2007. > >=20 > > This document describes a protocol for supporting Mobile Networks=20 > > between a Mobile Router and a Home Agent by extending the=20 > Mobile IPv4=20 > > protocol. A Mobile Router is responsible for the mobility=20 > of one or=20 > > more network segments or subnets moving together. The=20 > Mobile Router=20 > > hides its mobility from the nodes on the mobile network. =20 > The nodes on=20 > > the Mobile Network may be fixed in relationship to the Mobile > > Router and may not have any mobility function. =20 > >=20 > > Extensions to Mobile IPv4 are introduced to support Mobile Networks. > >=20 > > A URL for this Internet-Draft is: > > > http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-ba > se-02.txt > >=20 > > Please respond to this working group last call: > >=20 > > * If you have no comments on the draft, and support its advancement, > > simply respond with a line containing something like > >=20 > > "I support the advancement of this document to the IESG with a > > request for publication as a Proposed Standard RFC." > >=20 > > If you have comments, please use a line similar to the one above, > > and supplement this with your comments. > >=20 > >=20 > > * If you *don't* support its advancement, respond with a line > > containing something like the following, supplemented by your > > comments - > >=20 > > "I don't support the advancement of this document to=20 > the IESG with > > a request for publication as a Proposed Standard RFC, for the > > following reasons:" > > ... > >=20 > > Please direct all replies to the Mobile IPv4 mailing list,=20 > > mip4@ietf.org. > >=20 > > -Pete & Henrik >=20 >=20 >=20 > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www1.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ >=20 -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 04 08:41:35 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdQ15-0007te-Q4; Thu, 04 Oct 2007 08:41:23 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IdQ14-0007h0-81 for mip4-confirm+ok@megatron.ietf.org; Thu, 04 Oct 2007 08:41:22 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdQ13-0007gs-Sh for mip4@ietf.org; Thu, 04 Oct 2007 08:41:21 -0400 Received: from 213.80.52.78.dataphone.se ([213.80.52.78] helo=mailgw.local.ipunplugged.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IdQ0x-0006lU-HV for mip4@ietf.org; Thu, 04 Oct 2007 08:41:21 -0400 Received: from [127.0.0.1] (echo.local.ipunplugged.com [192.168.4.74]) by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with ESMTP id l94CewTZ019211 for ; Thu, 4 Oct 2007 14:40:59 +0200 Message-ID: <4704DF54.8020605@ipunplugged.com> Date: Thu, 04 Oct 2007 14:40:52 +0200 From: =?ISO-8859-1?Q?Hans_Sj=F6strand?= User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: mip4@ietf.org Subject: Re: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on mailgw.local.ipunplugged.com X-Virus-Status: Clean X-Spam-Score: 1.7 (+) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org I support the advancement of this document to the IESG with a request for publication as a Proposed Standard RFC when the following comment is addressed. - The issue about foreign agent care of mode must be clarified. As it is now, it's ambiguous whether foreign agent care of mode is supported with the mechanisms in this document. Further, if it is supported, if it's mandatory double tunneling or something like draft-ietf-mip4-nemov4-fa that applies. Sorry for being late best regards /// Hasse On 2007-09-19 20:20, McCann Peter-A001034 wrote: > This message announces a 2-week working group last call on: > > "Network Mobility (NEMO) Extensions for Mobile IPv4" > draft-ietf-mip4-nemo-v4-base-02.txt > > The last call will end at 24:00 UTC on Wednesday, October 3rd 2007. > > This document describes a protocol for supporting Mobile Networks > between a Mobile Router and a Home Agent by extending the Mobile IPv4 > protocol. A Mobile Router is responsible for the mobility of one or > more network segments or subnets moving together. The Mobile Router > hides its mobility from the nodes on the mobile network. The nodes > on the Mobile Network may be fixed in relationship to the Mobile > Router and may not have any mobility function. > > Extensions to Mobile IPv4 are introduced to support Mobile Networks. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-02.txt > > Please respond to this working group last call: > > * If you have no comments on the draft, and support its advancement, > simply respond with a line containing something like > > "I support the advancement of this document to the IESG with a > request for publication as a Proposed Standard RFC." > > If you have comments, please use a line similar to the one above, > and supplement this with your comments. > > > * If you *don't* support its advancement, respond with a line > containing something like the following, supplemented by your > comments - > > "I don't support the advancement of this document to the IESG with > a request for publication as a Proposed Standard RFC, for the > following reasons:" > ... > > Please direct all replies to the Mobile IPv4 mailing list, > mip4@ietf.org. > > -Pete & Henrik > > > -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 04 10:15:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdRTm-0002O1-JD; Thu, 04 Oct 2007 10:15:06 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IdRTl-0002IJ-AW for mip4-confirm+ok@megatron.ietf.org; Thu, 04 Oct 2007 10:15:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdRTl-00026C-0O for mip4@ietf.org; Thu, 04 Oct 2007 10:15:05 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IdRTc-0002Fg-QH for mip4@ietf.org; Thu, 04 Oct 2007 10:15:03 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-9.tower-128.messagelabs.com!1191507278!17745579!1 X-StarScan-Version: 5.5.12.14.2; banners=.,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 17575 invoked from network); 4 Oct 2007 14:14:38 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-9.tower-128.messagelabs.com with SMTP; 4 Oct 2007 14:14:38 -0000 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l94EEbjc017092; Thu, 4 Oct 2007 07:14:37 -0700 (MST) Received: from il06vts03.mot.com (il06vts03.mot.com [129.188.137.143]) by il06exr02.mot.com (8.13.1/Vontu) with SMTP id l94EEbYm009900; Thu, 4 Oct 2007 09:14:37 -0500 (CDT) Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id l94EEZQE009879; Thu, 4 Oct 2007 09:14:36 -0500 (CDT) Message-ID: <4704F54B.4050908@gmail.com> Date: Thu, 04 Oct 2007 16:14:35 +0200 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Hans_Sj=F6strand?= Subject: Re: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt References: <4704DF54.8020605@ipunplugged.com> In-Reply-To: <4704DF54.8020605@ipunplugged.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 000778-2, 03/10/2007), Outbound message X-Antivirus-Status: Clean X-CFilter-Loop: Reflected X-Spam-Score: -4.0 (----) X-Scan-Signature: b22590c27682ace61775ee7b453b40d3 Cc: Christophe Janneteau , mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hans Sjöstrand wrote: > I support the advancement of this document to the IESG with a request > for publication as a Proposed Standard RFC when the following > comment is addressed. - The issue about foreign agent care of mode > must be clarified. As it is now, it's ambiguous whether foreign agent > care of mode is supported with the mechanisms in this document. > Further, if it is supported, if it's mandatory double tunneling or > something like draft-ietf-mip4-nemov4-fa that applies. Sorry for > being late Hasse, ChristopheJ, thanks for the follow-up. How about this introductory text: > This document describes protocol extensions to Mobile IPv4 as per > [RFC3344] and its update [2], to enable support for Mobile Networks. > This draft addresses mainly the co-located Care-of Address mode. > Foreign Agent Care-of Address mode (with 'legacy' Foreign Agents, RFC > 3344) are supported but without optimization, double encapsulation > being used. For an optimization of this mode, the gentle reader is > directed to [1]. Instead of: > This document describes protocol extensions to Mobile IPv4 > ([RFC3344]) to enable support for Mobile Networks. This draft > addresses only co-located Care-of Address mode (not Foreign Agent > Care-of Address mode, for which the gentle reader is directed to > [1]). And this (check last 3 lines): > This document specifies an additional tunnel between Mobile Router's > Home Address and the Home Agent. This tunnel is encapsulated within > the normal tunnel between the Care-of Address (CoA) and Home Agent. > In Foreign Agent CoA mode, the tunnel between the Mobile Router and > Home Agent is needed to allow the Foreign Agent to direct the > decapsulated packet to the proper visiting Mobile Router. However, > in Collocated CoA mode, the additional tunnel is not essential and > could be eliminated because the Mobile Router is the recipient of the > encapsulated packets for the Mobile Network. Instead of (check last 3 lines): > This document specifies an additional tunnel between Mobile Router's > Home Address and the Home Agent. This tunnel is encapsulated within > the normal tunnel between the Care-of Address (CoA) and Home Agent. > In Foreign Agent CoA mode, the tunnel between the Mobile Router and > Home Agent is needed to allow the Foreign Agent to direct the > decapsulated packet to the proper visiting Mobile Router. However, > in Collocated CoA mode, the additional tunnel is not essential and > can be eliminated because the Mobile Router is the recipient of the > encapsulated packets for the Mobile Network. Finally, if the following paragraph disturbs then I can remove it altogether: > For optimization, the Home Agent SHOULD only encapsulate the packet > with the tunnel header (source IP address set to Home Agent and > destination IP address set to CoA) for Collocated CoA mode. Is there any other text occurence that disturbs? Alex > > best regards /// Hasse > > > On 2007-09-19 20:20, McCann Peter-A001034 wrote: >> This message announces a 2-week working group last call on: >> >> "Network Mobility (NEMO) Extensions for Mobile IPv4" >> draft-ietf-mip4-nemo-v4-base-02.txt >> >> The last call will end at 24:00 UTC on Wednesday, October 3rd 2007. >> >> >> This document describes a protocol for supporting Mobile Networks >> between a Mobile Router and a Home Agent by extending the Mobile >> IPv4 protocol. A Mobile Router is responsible for the mobility of >> one or more network segments or subnets moving together. The >> Mobile Router hides its mobility from the nodes on the mobile >> network. The nodes on the Mobile Network may be fixed in >> relationship to the Mobile Router and may not have any mobility >> function. >> >> Extensions to Mobile IPv4 are introduced to support Mobile >> Networks. >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-02.txt >> >> >> Please respond to this working group last call: >> >> * If you have no comments on the draft, and support its >> advancement, simply respond with a line containing something like >> >> "I support the advancement of this document to the IESG with a >> request for publication as a Proposed Standard RFC." >> >> If you have comments, please use a line similar to the one above, >> and supplement this with your comments. >> >> >> * If you *don't* support its advancement, respond with a line >> containing something like the following, supplemented by your >> comments - >> >> "I don't support the advancement of this document to the IESG with >> a request for publication as a Proposed Standard RFC, for the >> following reasons:" ... >> >> Please direct all replies to the Mobile IPv4 mailing list, >> mip4@ietf.org. >> >> -Pete & Henrik >> >> >> > > > > ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 04 11:19:50 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdSUE-0007Sv-If; Thu, 04 Oct 2007 11:19:38 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IdSUD-0007QC-1t for mip4-confirm+ok@megatron.ietf.org; Thu, 04 Oct 2007 11:19:37 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdSUC-0007Pg-MN for mip4@ietf.org; Thu, 04 Oct 2007 11:19:36 -0400 Received: from mail119.messagelabs.com ([216.82.241.179]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IdSUC-0002xl-38 for mip4@ietf.org; Thu, 04 Oct 2007 11:19:36 -0400 X-VirusChecked: Checked X-Env-Sender: Christophe.Janneteau@motorola.com X-Msg-Ref: server-4.tower-119.messagelabs.com!1191511175!28300800!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 8653 invoked from network); 4 Oct 2007 15:19:35 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-4.tower-119.messagelabs.com with SMTP; 4 Oct 2007 15:19:35 -0000 Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l94FJYUq009323 for ; Thu, 4 Oct 2007 08:19:34 -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 l94FJYZK017589 for ; Thu, 4 Oct 2007 10:19:34 -0500 (CDT) Received: from zuk35exm62.ds.mot.com (zuk35exm62.ea.mot.com [10.178.1.41]) by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l94FJWKT017566 for ; Thu, 4 Oct 2007 10:19:33 -0500 (CDT) Received: from [10.161.201.129] ([10.161.201.129]) by zuk35exm62.ds.mot.com with Microsoft SMTPSVC(6.0.3790.2709); Thu, 4 Oct 2007 16:19:32 +0100 Message-ID: <47050483.30605@motorola.com> Date: Thu, 04 Oct 2007 17:19:31 +0200 From: Christophe Janneteau User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Alexandru Petrescu Subject: Re: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt References: <4704DF54.8020605@ipunplugged.com> <4704F54B.4050908@gmail.com> In-Reply-To: <4704F54B.4050908@gmail.com> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Oct 2007 15:19:32.0341 (UTC) FILETIME=[F6FA2250:01C80699] X-CFilter-Loop: Reflected X-Spam-Score: 0.0 (/) X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 Cc: =?ISO-8859-1?Q?Hans_Sj=F6strand?= , mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Alex, Please see my comments inline. Alexandru Petrescu wrote: [snip] > How about this introductory text: >> This document describes protocol extensions to Mobile IPv4 as per >> [RFC3344] and its update [2], to enable support for Mobile Networks. >> This draft addresses mainly the co-located Care-of Address mode. >> Foreign Agent Care-of Address mode (with 'legacy' Foreign Agents, RFC >> 3344) are supported but without optimization, double encapsulation >> being used. For an optimization of this mode, the gentle reader is >> directed to [1]. > > Instead of: >> This document describes protocol extensions to Mobile IPv4 ([RFC3344]) >> to enable support for Mobile Networks. This draft addresses only >> co-located Care-of Address mode (not Foreign Agent Care-of Address >> mode, for which the gentle reader is directed to [1]). I agree. I guess this addresses quite well the issue I raised. > And this (check last 3 lines): >> This document specifies an additional tunnel between Mobile Router's >> Home Address and the Home Agent. This tunnel is encapsulated within >> the normal tunnel between the Care-of Address (CoA) and Home Agent. >> In Foreign Agent CoA mode, the tunnel between the Mobile Router and >> Home Agent is needed to allow the Foreign Agent to direct the >> decapsulated packet to the proper visiting Mobile Router. However, >> in Collocated CoA mode, the additional tunnel is not essential and >> could be eliminated because the Mobile Router is the recipient of the >> encapsulated packets for the Mobile Network. > > Instead of (check last 3 lines): >> This document specifies an additional tunnel between Mobile Router's >> Home Address and the Home Agent. This tunnel is encapsulated within >> the normal tunnel between the Care-of Address (CoA) and Home Agent. In >> Foreign Agent CoA mode, the tunnel between the Mobile Router and Home >> Agent is needed to allow the Foreign Agent to direct the decapsulated >> packet to the proper visiting Mobile Router. However, in Collocated >> CoA mode, the additional tunnel is not essential and can be eliminated >> because the Mobile Router is the recipient of the encapsulated packets >> for the Mobile Network. OK. > Finally, if the following paragraph disturbs then I can remove it > altogether: >> For optimization, the Home Agent SHOULD only encapsulate the packet >> with the tunnel header (source IP address set to Home Agent and >> destination IP address set to CoA) for Collocated CoA mode. I am fine with this text and keeping it inside the draft. Thanks Christophe > Is there any other text occurence that disturbs? > > Alex > > >> >> best regards /// Hasse >> >> >> On 2007-09-19 20:20, McCann Peter-A001034 wrote: >>> This message announces a 2-week working group last call on: >>> >>> "Network Mobility (NEMO) Extensions for Mobile IPv4" >>> draft-ietf-mip4-nemo-v4-base-02.txt >>> >>> The last call will end at 24:00 UTC on Wednesday, October 3rd 2007. >>> >>> >>> This document describes a protocol for supporting Mobile Networks >>> between a Mobile Router and a Home Agent by extending the Mobile >>> IPv4 protocol. A Mobile Router is responsible for the mobility of >>> one or more network segments or subnets moving together. The >>> Mobile Router hides its mobility from the nodes on the mobile >>> network. The nodes on the Mobile Network may be fixed in >>> relationship to the Mobile Router and may not have any mobility >>> function. >>> >>> Extensions to Mobile IPv4 are introduced to support Mobile >>> Networks. >>> >>> A URL for this Internet-Draft is: >>> http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-02.txt >>> >>> >>> Please respond to this working group last call: >>> >>> * If you have no comments on the draft, and support its >>> advancement, simply respond with a line containing something like >>> >>> "I support the advancement of this document to the IESG with a >>> request for publication as a Proposed Standard RFC." >>> >>> If you have comments, please use a line similar to the one above, and >>> supplement this with your comments. >>> >>> >>> * If you *don't* support its advancement, respond with a line >>> containing something like the following, supplemented by your comments - >>> >>> "I don't support the advancement of this document to the IESG with a >>> request for publication as a Proposed Standard RFC, for the following >>> reasons:" ... >>> >>> Please direct all replies to the Mobile IPv4 mailing list, >>> mip4@ietf.org. >>> >>> -Pete & Henrik >>> >>> >>> >> >> >> >> > -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 04 11:41:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdSpi-00075K-Rs; Thu, 04 Oct 2007 11:41:50 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IdSpi-00073i-6q for mip4-confirm+ok@megatron.ietf.org; Thu, 04 Oct 2007 11:41:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdSph-0006vV-RH for mip4@ietf.org; Thu, 04 Oct 2007 11:41:49 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IdSpZ-0005XX-J7 for mip4@ietf.org; Thu, 04 Oct 2007 11:41:47 -0400 Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l94FfJx0029817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 4 Oct 2007 08:41:19 -0700 Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com [172.30.36.176]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l94FfIu5018455; Thu, 4 Oct 2007 08:41:18 -0700 (PDT) Received: from NAEX16.na.qualcomm.com ([10.47.6.158]) by SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 4 Oct 2007 08:41:17 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Date: Thu, 4 Oct 2007 08:40:47 -0700 Message-ID: <2309978910A6A6478C2C7585692B0AF4ACD0B4@NAEX16.na.qualcomm.com> In-Reply-To: <47050483.30605@motorola.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Thread-Index: AcgGmndC43apoF4lQj6cn+z2c6ilCQAAhkSw References: <4704DF54.8020605@ipunplugged.com> <4704F54B.4050908@gmail.com> <47050483.30605@motorola.com> From: "Tsirtsis, George" To: "Christophe Janneteau" , "Alexandru Petrescu" X-OriginalArrivalTime: 04 Oct 2007 15:41:17.0767 (UTC) FILETIME=[01125570:01C8069D] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: =?iso-8859-1?Q?Hans_Sj=F6strand?= , mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Alex, sorry I have still not managed to review the document but in any = case I did in the past and I do not remember any outstanding issues, so = the WG should not wait for my review. I wanted to make one comment = below, however,... -----Original Message----- From: Christophe Janneteau [mailto:Christophe.Janneteau@motorola.com]=20 Sent: Thursday, October 04, 2007 4:20 PM To: Alexandru Petrescu Cc: Hans Sj=F6strand; mip4@ietf.org Subject: Re: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Hi Alex, Please see my comments inline. Alexandru Petrescu wrote: [snip] > How about this introductory text: >> This document describes protocol extensions to Mobile IPv4 as per >> [RFC3344] and its update [2], to enable support for Mobile Networks. >> This draft addresses mainly the co-located Care-of Address mode. >> Foreign Agent Care-of Address mode (with 'legacy' Foreign Agents, RFC >> 3344) are supported but without optimization, double encapsulation >> being used. For an optimization of this mode, the gentle reader is >> directed to [1]. >=20 > Instead of: >> This document describes protocol extensions to Mobile IPv4 = ([RFC3344]) >> to enable support for Mobile Networks. This draft addresses only >> co-located Care-of Address mode (not Foreign Agent Care-of Address >> mode, for which the gentle reader is directed to [1]). I agree. I guess this addresses quite well the issue I raised. GT> Yes this is clearer, but can the reference to an Internet-draft = survive the conversion of this doc to an RFC? -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 04 16:50:10 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdXdu-0007er-KW; Thu, 04 Oct 2007 16:49:58 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IdXdt-0007cw-NE for mip4-confirm+ok@megatron.ietf.org; Thu, 04 Oct 2007 16:49:57 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdXdt-0007Vl-CU for mip4@ietf.org; Thu, 04 Oct 2007 16:49:57 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IdXdl-0006BV-9a for mip4@ietf.org; Thu, 04 Oct 2007 16:49:49 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-10.tower-128.messagelabs.com!1191530988!14077644!1 X-StarScan-Version: 5.5.12.14.2; banners=.,-,- X-Originating-IP: [144.189.100.102] Received: (qmail 12106 invoked from network); 4 Oct 2007 20:49:48 -0000 Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102) by server-10.tower-128.messagelabs.com with SMTP; 4 Oct 2007 20:49:48 -0000 Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232]) by motgate4.mot.com (8.12.11/Motorola) with ESMTP id l94KncUP003364; Thu, 4 Oct 2007 13:49:38 -0700 (MST) Received: from az10vts02.mot.com (az10vts02.mot.com [10.64.251.243]) by az33exr02.mot.com (8.13.1/Vontu) with SMTP id l94Knbtq026154; Thu, 4 Oct 2007 15:49:38 -0500 (CDT) Received: from [127.0.0.1] ([10.129.40.209]) by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id l94KnV39026089; Thu, 4 Oct 2007 15:49:33 -0500 (CDT) Message-ID: <470551DA.30305@gmail.com> Date: Thu, 04 Oct 2007 22:49:30 +0200 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: "Tsirtsis, George" Subject: Re: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt References: <4704DF54.8020605@ipunplugged.com> <4704F54B.4050908@gmail.com> <47050483.30605@motorola.com> <2309978910A6A6478C2C7585692B0AF4ACD0B4@NAEX16.na.qualcomm.com> In-Reply-To: <2309978910A6A6478C2C7585692B0AF4ACD0B4@NAEX16.na.qualcomm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 000778-3, 04/10/2007), Outbound message X-Antivirus-Status: Clean X-CFilter-Loop: Reflected X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Cc: Christophe Janneteau , =?ISO-8859-1?Q?Hans_Sj=F6strand?= , mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Tsirtsis, George wrote: > Alex, sorry I have still not managed to review the document but in > any case I did in the past and I do not remember any outstanding > issues, so the WG should not wait for my review. So you > "I support the advancement of this document to the IESG with a > request for publication as a Proposed Standard RFC." ? > I wanted to make one comment below, however,... > > -----Original Message----- From: Christophe Janneteau > [mailto:Christophe.Janneteau@motorola.com] Sent: Thursday, October > 04, 2007 4:20 PM To: Alexandru Petrescu Cc: Hans Sjöstrand; > mip4@ietf.org Subject: Re: [Mip4] WGLC for > draft-ietf-mip4-nemo-v4-base-02.txt > > Hi Alex, > > Please see my comments inline. > > Alexandru Petrescu wrote: [snip] >> How about this introductory text: >>> This document describes protocol extensions to Mobile IPv4 as per >>> [RFC3344] and its update [2], to enable support for Mobile >>> Networks. This draft addresses mainly the co-located Care-of >>> Address mode. Foreign Agent Care-of Address mode (with 'legacy' >>> Foreign Agents, RFC 3344) are supported but without optimization, >>> double encapsulation being used. For an optimization of this >>> mode, the gentle reader is directed to [1]. >> Instead of: >>> This document describes protocol extensions to Mobile IPv4 >>> ([RFC3344]) to enable support for Mobile Networks. This draft >>> addresses only co-located Care-of Address mode (not Foreign Agent >>> Care-of Address mode, for which the gentle reader is directed to >>> [1]). > > I agree. I guess this addresses quite well the issue I raised. > > > GT> Yes this is clearer, but can the reference to an Internet-draft > survive the conversion of this doc to an RFC? Usually no, I don't remember having seen an RFC with references to drafts, or not common. During later editing steps we could either remove that "for which the gentle reader is directed to [1]" or replace it with something else; let's watch that space. Alex ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 04 17:15:47 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdY2h-0005ex-Jc; Thu, 04 Oct 2007 17:15:35 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IdY2c-0005Yv-0e for mip4-confirm+ok@megatron.ietf.org; Thu, 04 Oct 2007 17:15:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdY2b-0005X6-JS; Thu, 04 Oct 2007 17:15:29 -0400 Received: from ns1.neustar.com ([156.154.16.138]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IdY2a-0000zf-BL; Thu, 04 Oct 2007 17:15:29 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 33D8126EAB; Thu, 4 Oct 2007 21:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IdY2A-0006EC-3J; Thu, 04 Oct 2007 17:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 04 Oct 2007 17:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-dsmipv4-05.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org --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 : Dual Stack Mobile IPv4 Author(s) : G. Tsirtsis, et al. Filename : draft-ietf-mip4-dsmipv4-05.txt Pages : 27 Date : 2007-10-4 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-dsmipv4-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mip4-dsmipv4-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-dsmipv4-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-4164803.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-dsmipv4-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-dsmipv4-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-4164803.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --NextPart-- From mip4-bounces@ietf.org Fri Oct 05 12:17:29 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Idppy-00029x-BR; Fri, 05 Oct 2007 12:15:38 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1Idppt-00029F-P2 for mip4-confirm+ok@megatron.ietf.org; Fri, 05 Oct 2007 12:15:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Idppt-00028E-E5; Fri, 05 Oct 2007 12:15:33 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Idpps-0002SD-A3; Fri, 05 Oct 2007 12:15:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 459A1329D3; Fri, 5 Oct 2007 16:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IdppO-0004yD-6D; Fri, 05 Oct 2007 12:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 05 Oct 2007 12:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-02.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org --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 : Network Mobility (NEMO) Extensions for Mobile IPv4 Author(s) : K. Leung, et al. Filename : draft-ietf-mip4-nemo-v4-base-02.txt Pages : 19 Date : 2007-9-12 This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the mobile network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mip4-nemo-v4-base-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-5115014.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-nemo-v4-base-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-5115014.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --NextPart-- From mip4-bounces@ietf.org Fri Oct 05 13:15:40 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Idqm1-000472-Cj; Fri, 05 Oct 2007 13:15:37 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1Idqlx-000411-GD for mip4-confirm+ok@megatron.ietf.org; Fri, 05 Oct 2007 13:15:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Idqlx-00040t-6G; Fri, 05 Oct 2007 13:15:33 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Idqlw-0004nR-2K; Fri, 05 Oct 2007 13:15:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 0A5D5329DC; Fri, 5 Oct 2007 17:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IdqlR-0007MY-Ua; Fri, 05 Oct 2007 13:15:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 05 Oct 2007 13:15:01 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-03.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org --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 : Network Mobility (NEMO) Extensions for Mobile IPv4 Author(s) : K. Leung, et al. Filename : draft-ietf-mip4-nemo-v4-base-03.txt Pages : 19 Date : 2007-10-5 This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the mobile network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mip4-nemo-v4-base-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-5121413.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-nemo-v4-base-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-5121413.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --NextPart-- From mip4-bounces@ietf.org Fri Oct 05 14:47:58 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdsDJ-0000Pu-Db; Fri, 05 Oct 2007 14:47:53 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IdsDI-0000MM-6l for mip4-confirm+ok@megatron.ietf.org; Fri, 05 Oct 2007 14:47:52 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdsDH-0000E9-H6 for mip4@ietf.org; Fri, 05 Oct 2007 14:47:51 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IdsDB-0008SS-KU for mip4@ietf.org; Fri, 05 Oct 2007 14:47:51 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-8.tower-128.messagelabs.com!1191610044!17262672!1 X-StarScan-Version: 5.5.12.14.2; banners=.,-,- X-Originating-IP: [144.189.100.102] Received: (qmail 17488 invoked from network); 5 Oct 2007 18:47:24 -0000 Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102) by server-8.tower-128.messagelabs.com with SMTP; 5 Oct 2007 18:47:24 -0000 Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate4.mot.com (8.12.11/Motorola) with ESMTP id l95IlOHW017009 for ; Fri, 5 Oct 2007 11:47:24 -0700 (MST) Received: from az10vts02.mot.com (az10vts02.mot.com [10.64.251.243]) by az33exr04.mot.com (8.13.1/Vontu) with SMTP id l95IlNHB000435 for ; Fri, 5 Oct 2007 13:47:24 -0500 (CDT) Received: from [127.0.0.1] ([10.129.42.92]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id l95IlLqq000427 for ; Fri, 5 Oct 2007 13:47:22 -0500 (CDT) Message-ID: <470686B8.3020401@gmail.com> Date: Fri, 05 Oct 2007 20:47:20 +0200 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 CC: mip4@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 000778-4, 05/10/2007), Outbound message X-Antivirus-Status: Clean X-CFilter-Loop: Reflected X-Spam-Score: -2.4 (--) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Subject: [Mip4] Re: I-D ACTION:draft-ietf-mip4-nemo-v4-base-03.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Folks, don't worry, I've submitted today the 4th version of NEMOv4 for MIP4 WG. I think it will be announced next week sometime. It contains the latest modifications we've discussed. Alex Internet-Drafts@ietf.org wrote: > 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 : Network Mobility (NEMO) Extensions for Mobile IPv4 > Author(s) : K. Leung, et al. > Filename : draft-ietf-mip4-nemo-v4-base-03.txt > Pages : 19 > Date : 2007-10-5 > > This document describes a protocol for supporting Mobile Networks > between a Mobile Router and a Home Agent by extending the Mobile IPv4 > protocol. A Mobile Router is responsible for the mobility of one or > more network segments or subnets moving together. The Mobile Router > hides its mobility from the nodes on the mobile network. The nodes > on the Mobile Network may be fixed in relationship to the Mobile > Router and may not have any mobility function. > > Extensions to Mobile IPv4 are introduced to support Mobile Networks. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-03.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@ietf.org with the word unsubscribe in the body of > the message. > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > Internet-Drafts are also available by anonymous FTP. Login with the > username "anonymous" and a password of your e-mail address. After > logging in, type "cd internet-drafts" and then > "get draft-ietf-mip4-nemo-v4-base-03.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-03.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > > ------------------------------------------------------------------------ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Mon Oct 15 00:02:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IhH9z-0005Ys-Ew; Mon, 15 Oct 2007 00:02:31 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IhH9x-0005XC-Jr for mip4-confirm+ok@megatron.ietf.org; Mon, 15 Oct 2007 00:02:29 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IhH9w-0005WD-KM for mip4@ietf.org; Mon, 15 Oct 2007 00:02:28 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IhH9u-0003UW-4K for mip4@ietf.org; Mon, 15 Oct 2007 00:02:26 -0400 Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l9F42NZU001716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 14 Oct 2007 21:02:23 -0700 Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com [172.30.36.176]) by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l9F42Mns023547; Sun, 14 Oct 2007 21:02:22 -0700 (PDT) Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 14 Oct 2007 21:02:22 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Date: Sun, 14 Oct 2007 21:02:20 -0700 Message-ID: In-Reply-To: <470551DA.30305@gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] WGLC for draft-ietf-mip4-nemo-v4-base-02.txt Thread-Index: AcgGyPTmDbPUZ6oNQqKtB01JttWSlwIFwEGQ References: <4704DF54.8020605@ipunplugged.com><4704F54B.4050908@gmail.com> <47050483.30605@motorola.com><2309978910A6A6478C2C7585692B0AF4ACD0B4@NAEX16.na.qualcomm.com> <470551DA.30305@gmail.com> From: "Narayanan, Vidya" To: "Alexandru Petrescu" , "Tsirtsis, George" X-OriginalArrivalTime: 15 Oct 2007 04:02:22.0038 (UTC) FILETIME=[2FF92760:01C80EE0] X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Cc: Christophe Janneteau , =?iso-8859-1?Q?Hans_Sj=F6strand?= , mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org > >=20 > > GT> Yes this is clearer, but can the reference to an Internet-draft > > survive the conversion of this doc to an RFC? >=20 > Usually no, I don't remember having seen an RFC with references to > drafts, or not common. During later editing steps we could either=20 > remove that "for which the gentle reader is directed to [1]"=20 > or replace=20 > it with something else; let's watch that space. >=20 Since this is only an informative reference, using a draft as a = reference is fine and should have no impact on getting published as an = RFC. So, I don't think we need to revise the text.=20 Regards, Vidya -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Mon Oct 15 11:15:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IhRes-0001MX-PN; Mon, 15 Oct 2007 11:15:06 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IhRep-0001M4-4P for mip4-confirm+ok@megatron.ietf.org; Mon, 15 Oct 2007 11:15:03 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IhReo-0001Lu-4I; Mon, 15 Oct 2007 11:15:02 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IhRen-0000ld-Nz; Mon, 15 Oct 2007 11:15:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id A48842AC63; Mon, 15 Oct 2007 15:15:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IhRen-0002Ud-EH; Mon, 15 Oct 2007 11:15:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 15 Oct 2007 11:15:01 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-04.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org --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 : Network Mobility (NEMO) Extensions for Mobile IPv4 Author(s) : K. Leung, et al. Filename : draft-ietf-mip4-nemo-v4-base-04.txt Pages : 18 Date : 2007-10-15 This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the mobile network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mip4-nemo-v4-base-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-15105555.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-nemo-v4-base-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-15105555.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --NextPart-- From mip4-bounces@ietf.org Sun Oct 21 09:51:43 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IjbDJ-0003AA-MJ; Sun, 21 Oct 2007 09:51:33 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IjbDG-00037I-Mt for mip4-confirm+ok@megatron.ietf.org; Sun, 21 Oct 2007 09:51:31 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IjbDF-0002wX-LK for Mip4@ietf.org; Sun, 21 Oct 2007 09:51:29 -0400 Received: from hydrogen.cen.brad.ac.uk ([143.53.238.3]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IjbD4-0006N5-9H for Mip4@ietf.org; Sun, 21 Oct 2007 09:51:19 -0400 Received: from radon.cen.brad.ac.uk (radon.cen.brad.ac.uk [143.53.238.18]) by hydrogen.cen.brad.ac.uk (8.13.6/8.13.4) with ESMTP id l9LDpEQ8004465 for ; Sun, 21 Oct 2007 14:51:16 +0100 (BST) Received: from d212 (d212.inf.brad.ac.uk [143.53.29.36]) by radon.cen.brad.ac.uk (8.13.6/8.13.4) with SMTP id l9LDnTUr010876 for ; Sun, 21 Oct 2007 14:49:29 +0100 (BST) Message-Id: <200710211349.l9LDnTUr010876@radon.cen.brad.ac.uk> Date: Sun, 21 Oct 2007 14:49:29 +0100 From: "X.Jin" To: "Mip4" X-mailer: Foxmail 5.0 [en] Mime-Version: 1.0 X-Spam-Score: 2.8 (++) X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e Cc: Subject: [Mip4] CFP - PMEO-UCNS'08 to be held with IPDPS'08 (Deadline EXTENDED TO 28 OCTOBER 2007) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0665132388==" Errors-To: mip4-bounces@ietf.org --===============0665132388== Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 W1BsZWFzZSBhY2NlcHQgb3VyIGFwb2xvZ2llcyBpZiB5b3UgcmVjZWl2ZSBtdWx0aXBsZSBjb3Bp ZXMgb2YgdGhpcyBlbWFpbHNdDQoNCioqKiogU3VibWlzc2lvbiBEZWFkbGluZSBFWFRFTkRFRCBU TyAyOCBPQ1RPQkVSIDIwMDcgKioqKioNCg0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCg0KKFNlbGVjdGVkIGhpZ2gtcXVhbGl0 eSBwYXBlcnMgZnJvbSB0aGUgUE1FTy1VQ05TJzA4IHdvcmtzaG9wIHdpbGwgDQphcHBlYXIgaW4g YSBTcGVjaWFsIElzc3VlIG9mIHRoZSBqb3VybmFsIC0gSW50ZXJuYXRpb25hbCBKb3VybmFsIG9m IFBhcmFsbGVsLCANCkVtZXJnZW50LCBhbmQgRGlzdHJpYnV0ZWQgU3lzdGVtcyAoSUpQRURTKSwg VGF5bG9yICYgRnJhbmNpcyAtIA0KaHR0cDovL3d3dy50YW5kZi5jby51ay9qb3VybmFscy90aXRs ZXMvMTc0NDU3NjAuYXNwKQ0KDQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKg0KDQpDQUxMIEZPUiBQQVBFUlMNCg0KDQo3dGggSW50 ZXJuYXRpb25hbCBXb3Jrc2hvcCBvbiBQZXJmb3JtYW5jZSBNb2RlbGluZywgRXZhbHVhdGlvbiwg YW5kIA0KT3B0aW1pemF0aW9uIG9mIFViaXF1aXRvdXMgQ29tcHV0aW5nIGFuZCBOZXR3b3JrZWQg U3lzdGVtcyANCihQTUVPLVVDTlOhrzA4KQ0KDQpUbyBiZSBoZWxkIGluIGNvbmp1bmN0aW9uIHdp dGggSVBEUFMnMDggKFN1cHBvcnRlZCBieSBJRUVFIENvbXB1dGVyIA0KU29jaWV0eSBpbiBjb29w ZXJhdGlvbiB3aXRoIEFDTSBTSUdBUkNIKSwgMTQgLTE4IEFwcmlsLCAyMDA4LCBNaWFtaSwgDQpG bG9yaWRhLCBVU0ENCg0KaHR0cDovL3d3dy5pbmYuYnJhZC5hYy51ay9+Z21pbi9QTUVPLTA4Lmh0 bWwNCmh0dHA6Ly93d3cuaXBkcHMub3JnL2lwZHBzMjAwOC8yMDA4X3dvcmtzaG9wcy5odG1sDQoN Cg0KU0NPUEU6DQoNClRoZSBwZXJmb3JtYW5jZSBtb2RlbGluZywgZXZhbHVhdGlvbiwgYW5kIG9w dGltaXphdGlvbiBvZiB1YmlxdWl0b3VzIA0KY29tcHV0aW5nIGFuZCBuZXR3b3JrZWQgc3lzdGVt cyBoYXZlIGJlZW4gYW4gaW1wb3J0YW50IHJlc2VhcmNoIA0KdG9waWMgb3ZlciB0aGUgcGFzdCB5 ZWFycyBhbmQgcG9zZXMgY2hhbGxlbmdpbmcgcHJvYmxlbXMgdGhhdCByZXF1aXJlIA0KbmV3IHRv b2xzIGFuZCBtZXRob2RzIHRvIGtlZXAgdXAgd2l0aCB0aGUgcmFwaWQgZXZvbHV0aW9uIGFuZCAN CmluY3JlYXNpbmcgY29tcGxleGl0eSBvZiBzdWNoIHN5c3RlbXMuIA0KDQpUaGlzIHdvcmtzaG9w IHdpbGwgYnJpbmcgdG9nZXRoZXIgc2NpZW50aXN0cywgZW5naW5lZXJzLCBwcmFjdGl0aW9uZXJz LCBhbmQgDQpjb21wdXRlciB1c2VycyB0byBzaGFyZSBhbmQgZXhjaGFuZ2UgdGhlaXIgZXhwZXJp ZW5jZXMsIGRpc2N1c3MgY2hhbGxlbmdlcywgDQphbmQgcmVwb3J0IHN0YXRlLW9mLXRoZS1hcnQg YW5kIGluLXByb2dyZXNzIHJlc2VhcmNoIG9uIGFsbCBhc3BlY3RzIG9mIA0KcGVyZm9ybWFuY2Ug bW9kZWxpbmcsIGV2YWx1YXRpb24sIGFuZCBvcHRpbWl6YXRpb24gb2YgdWJpcXVpdG91cyBjb21w dXRpbmcgDQphbmQgbmV0d29ya2VkIHN5c3RlbXMuIFRoZSB0b3BpY3Mgb2YgaW50ZXJlc3QgaW5j bHVkZSwgYnV0IGFyZSBub3QgbGltaXRlZCB0bzogDQoNCiAgICAtLSBQcmVkaWN0aXZlIHBlcmZv cm1hbmNlIG1vZGVscyBvZiB1YmlxdWl0b3VzIGNvbXB1dGluZyBzeXN0ZW1zIA0KICAgIC0tIFBy ZWRpY3RpdmUgcGVyZm9ybWFuY2UgbW9kZWxzIG9mIHdpcmVkIGFuZCB3aXJlbGVzcyBuZXR3b3Jr cw0KICAgIC0tIFBlcmZvcm1hbmNlIG1lYXN1cmVtZW50IGFuZCBtb25pdG9yaW5nIHRvb2xzIA0K ICAgIC0tIFRyYWNpbmcgYW5kIHRyYWNlIGFuYWx5c2lzDQogICAgLS0gU2ltdWxhdGlvbg0KICAg IC0tIEFuYWx5dGljYWwgbW9kZWxpbmcNCiAgICAtLSBTb2Z0d2FyZSB0b29scyBmb3Igc3lzdGVt IHBlcmZvcm1hbmNlIGFuZCBldmFsdWF0aW9uDQogICAgLS0gQXV0b21hdGljIHBlcmZvcm1hbmNl IGFuYWx5c2lzIA0KICAgIC0tIFBlcmZvcm1hbmNlIGNvbXBhcmlzb24NCiAgICAtLSBQZXJmb3Jt YW5jZSBvZiBtZW1vcnkgYW5kIEkvTyBpbnRlcmNvbm5lY3QNCiAgICAtLSBQZXJmb3JtYW5jZSBv ZiBjb21tdW5pY2F0aW9uIG5ldHdvcmtzIA0KICAgIC0tIFBlcmZvcm1hbmNlIG9mIG1vYmlsZSBk aXN0cmlidXRlZCBzeXN0ZW1zDQogICAgLS0gUGVyZm9ybWFuY2UgYW5hbHlzaXMgYW5kIGV2YWx1 YXRpb24gb2YgdWJpcXVpdG91cyBjb21wdXRpbmcgYW5kIA0KICAgICAgIG5ldHdvcmtlZCBhcHBs aWNhdGlvbnMNCiAgICAtLSBJbXByb3ZlbWVudCBpbiBzeXN0ZW0gcGVyZm9ybWFuY2UgdGhyb3Vn aCBvcHRpbWl6YXRpb24gYW5kIHR1bmluZw0KICAgIC0tIENhc2Ugc3R1ZGllcyBzaG93aW5nIHRo ZSByb2xlIG9mIGV2YWx1YXRpb24gaW4gdGhlIGRlc2lnbiBvZiBzeXN0ZW1zDQoNCg0KV09SS1NI T1AgQ08tQ0hBSVJTOg0KDQogICAgIEdleW9uZyBNaW4NCiAgICAgRGVwYXJ0bWVudCBvZiBDb21w dXRpbmcNCiAgICAgVW5pdmVyc2l0eSBvZiBCcmFkZm9yZA0KICAgICBCcmFkZm9yZCwgQkQ3IDFE UCwgVS5LLiANCiAgICAgRS1tYWlsOiBnLm1pbkBicmFkLmFjLnVrDQoNCiAgICAgTW9oYW1lZCBP dWxkLUtoYW91YSANCiAgICAgRGVwYXJ0bWVudCBvZiBDb21wdXRpbmcgU2NpZW5jZQ0KICAgICBV bml2ZXJzaXR5IG9mIEdsYXNnb3cgIA0KICAgICBHbGFzZ293LCBHMTIgOFJaLCBVLksuDQogICAg IEUtbWFpbDogbW9oYW1lZEBkY3MuZ2xhLmFjLnVrICAgDQoNCg0KUFJPR1JBTSBDSEFJUjoNCg0K ICAgICBBaG1lZCBZLiBBbC1EdWJhaSANCiAgICAgU2Nob29sIG9mIENvbXB1dGluZw0KICAgICBO YXBpZXIgVW5pdmVyc2l0eQ0KICAgICBFZGluYnVyZ2gsIEVIMTAgNURULCBVLksuDQogICAgIEUt bWFpbDogQS5BbC1EdWJhaUBuYXBpZXIuYWMudWsNCg0KDQpQVUJMSUNJVFkgQ08tQ0hBSVJTOg0K DQogICAgIFhpYW9sb25nIEppbg0KICAgICBEZXBhcnRtZW50IG9mIENvbXB1dGluZw0KICAgICBV bml2ZXJzaXR5IG9mIEJyYWRmb3JkDQogICAgIEJyYWRmb3JkLCBCRDcgMURQLCBVLksuDQogICAg IEUtbWFpbDogeC5qaW5AYnJhZC5hYy51aw0KDQogICAgIE1pcmVsYSBTZWNoaSBNb3JldHRpIEFu bm9uaSBOb3RhcmUgDQogICAgIEJhcmRkYWwgVW5pdmVyc2l0eQ0KICAgICBGbG9yaWFub3BvbGlz LCBTQyBCcmF6aWwgDQogICAgIEVtYWlsOiBtaXJlbGFAYmFyZGRhbC5icg0KDQoNClBST0dSQU0g Q09NTUlUVEVFOg0KIA0KICAgICBLLiBBbC1CZWdhaW4sIFVuaXYuIG9mIEdsYW1vcmdhbiAoVUsp DQogICAgIEkuIFJvbWRoYW5pLCBOYXBpZXIgVW5pdmVyc2l0eSAoVUspDQogICAgIEguIFIuIEFy YWJuaWEsIFVuaXYuIG9mIEdlb3JnaWEgKFVTQSkNCiAgICAgRC4gSy4gQXJ2aW5kLCBFZGluYnVy Z2ggVW5pdmVyc2l0eSAoVUspDQogICAgIEkuIEF3YW4sIFVuaXYuIG9mIEJyYWRmb3JkIChVSykN CiAgICAgQS4gQm91a2VyY2hlLCBVbml2LiBvZiBOb3J0aCBUZXhhcyAoVVNBKQ0KICAgICBKLiBC cmFkbGV5LCBJbXBlcmlhbCBDb2xsZWdlIExvbmRvbiAoVUspDQogICAgIFAuIENvY2tzaG90dCwg VW5pdi4gb2YgR2xhc2dvdyAoVUspDQogICAgIE0uIENvbGFqYW5uaSwgVW5pdi4gb2YgTW9kZW5h IChJdGFseSkNCiAgICAgSy4gRGF5LCBTdWx0YW4gUWFib29zIFVuaXYuIChPbWFuKQ0KICAgICBL LiBEamVtYW1lLCBVbml2LiBvZiBMZWVkcyAoVUspDQogICAgIFQuIEVsLUdoYXphd2ksIEdlb3Jn ZSBXYXNoaW5ndG9uIFVuaXZlcnNpdHkgKFVTQSkNCiAgICAgUi4gRmF0b29oaSwgU2FuIEpvc2Ug U3RhdGUgVW5pdmVyc2l0eSAoVVNBKQ0KICAgICBNLiBHdWVyb3VpLCBVbml2ZXJzaXR5IG9mIENl cmd5LVBvbnRvaXNlIChGcmFuY2UpICANCiAgICAgUy4gSGVsYWwsIFVuaXZlcnNpdHkgb2YgRmxv cmlkYSAoVVNBKQ0KICAgICBILiBIYXNzYW5laW4sIFF1ZWVuJ3MgVW5pdmVyc2l0eSAoQ2FuYWRh KQ0KICAgICBTLiBKYXJ2aXMsIFVuaXYuIG9mIFdhcndpY2sgKFVLKQ0KICAgICBILiBLYXJhdHph LCBVbml2LiBvZiBUaGVzc2Fsb25pa2kgKEdyZWVjZSkNCiAgICAgQS4gS2F0YW5ndXIsIFRleGFz IEEmTSBVbml2LiAoVVNBKQ0KICAgICBBLiBLaG9uc2FyaSwgSVBNIChJcmFuKQ0KICAgICBXLiBL bm90dGVuYmVsdCwgSW1wZXJpYWwgQ29sbGVnZSBMb25kb24gKFVLKQ0KICAgICBLLiBMaSwgU3Rh dGUgVW5pdi4gb2YgTmV3IFlvcmsgYXQgTmV3IFBhbHR6IChVU0EpDQogICAgIEguIExpdSwgSHVh emhvbmcgVW5pdi4gb2YgU2NpZW5jZSBhbmQgVGVjaG5vbG9neSAoQ2hpbmEpIA0KICAgICBTLiBM b3VjaWYsIE1vbmN0b24gVW5pdmVyc2l0eSwgKENhbmFkYSkNCiAgICAgTC5NLiBNYWNrZW56aWUs IFVuaXYuIG9mIEdsYXNnb3cgKFVLKQ0KICAgICBZLiBQYW4sIEdlb3JnaWEgU3RhdGUgVW5pdi4g KFVTQSkNCiAgICAgRC4gSy4gUHJhZGhhbiwgVW5pdi4gb2YgQnJpc3RvbCAoVUspDQogICAgIEgu IFNhcmJhemktQXphZCwgU2hhcmlmIFVuaXYuICYgSVBNIChJcmFuKQ0KICAgICBBLiBTaGFocmFi aSwgR2xhc2dvdyBDYWxlZG9uaWFuIFVuaXYuIChVSykNCiAgICAgRS4gU29uZywgSHVhemhvbmcg VW5pdi4gb2YgU2NpZW5jZSBhbmQgVGVjaG5vbG9neSAoQ2hpbmEpIA0KICAgICBOLiBUaG9tYXMs IFVuaXYuIG9mIE5ld2Nhc3RsZSAoVUspDQogICAgIEEuIFRvdXplbmUsIFN1bHRhbiBRYWJvb3Mg VW5pdi4gKE9tYW4pIA0KICAgICBNLiBXb29kd2FyZCwgVW5pdi4gb2YgQnJhZGZvcmQgKFVLKQ0K ICAgICBKLiBXdSwgRmxvcmlkYSBBdGxhbnRpYyBVbml2LiAoVVNBKSAgDQogICAgIEwuIFhpYW8s IE1pY2hpZ2FuIFN0YXRlIFVuaXYuIChVU0EpDQogICAgIFQuIFhpZSwgU2FuIERpZWdvIFN0YXRl IFVuaXZlcnNpdHkgKFVTQSkNCiAgICAgTC4gVC4gWWFuZywgU3QgRnJhbmNpcyBYYXZpZXIgVW5p di4gKENhbmFkYSkNCiAgICAgVy4gVmFuZGVyYmF1d2hlZGUsIFVuaXZlcnNpdHkgb2YgR2xhc2dv dyAoVUspDQogICAgIFcuIEJ1Y2hhbmFuLCBOYXBpZXIgVW5pdmVyc2l0eSAoVUspDQogICAgIEEu IFpvbWF5YSwgVW5pdi4gb2YgU3lkbmV5IChBdXN0cmFsaWEpDQogICAgICAgICAgICAgICAgICAg ICAgIA0KDQpQQVBFUiBTVUJNSVNTSU9OOg0KDQpBdXRob3JzIGFyZSBpbnZpdGVkIHRvIHN1Ym1p dCBtYW51c2NyaXB0cyByZXBvcnRpbmcgb3JpZ2luYWwgdW5wdWJsaXNoZWQgDQpyZXNlYXJjaCBh bmQgcmVjZW50IGRldmVsb3BtZW50cyBpbiB0aGUgdG9waWNzIHJlbGF0ZWQgdG8gdGhlIHdvcmtz aG9wLiANClRoZSBsZW5ndGggb2YgdGhlIHBhcGVycyBzaG91bGQgbm90IGV4Y2VlZCA4IHBhZ2Vz IChJRUVFIENvbXB1dGVyIA0KU29jaWV0eSBQcm9jZWVkaW5ncyBNYW51c2NyaXB0cyBzdHlsZTog dHdvIGNvbHVtbnMsIHNpbmdsZS1zcGFjZWQpLCANCmluY2x1ZGluZyBmaWd1cmVzIGFuZCByZWZl cmVuY2VzLCB1c2luZyAxMCBmb250cywgYW5kIG51bWJlciBlYWNoIHBhZ2UuIA0KUGFwZXJzIHNo b3VsZCBiZSBzdWJtaXR0ZWQgZWxlY3Ryb25pY2FsbHkgaW4gUERGIGZvcm1hdCAob3IgcG9zdHNj cmlwdCkgYnkgDQpzZW5kaW5nIGl0IGFzIGFuIGUtbWFpbCBhdHRhY2htZW50IHRvIEEuQWwtRHVi YWlAbmFwaWVyLmFjLnVrLiBBbGwgcGFwZXJzIA0Kd2lsbCBiZSBwZWVyIHJldmlld2VkIGFuZCB0 aGUgY29tbWVudHMgd2lsbCBiZSBwcm92aWRlZCB0byB0aGUgYXV0aG9ycy4gDQpUaGUgYWNjZXB0 ZWQgcGFwZXJzIHdpbGwgYmUgcHVibGlzaGVkIHRvZ2V0aGVyIHdpdGggdGhvc2Ugb2Ygb3RoZXIg SVBEUFMnMDggDQp3b3Jrc2hvcHMgYnkgdGhlIElFRUUgQ29tcHV0ZXIgU29jaWV0eSBQcmVzcy4N Cg0KDQpJTVBPUlRBTlQgREFURVM6DQoNClN1Ym1pc3Npb24gRGVhZGxpbmU6IE9jdG9iZXIgMjEs IDIwMDcgKEV4dGVuZGVkIHVudGlsIDI4IE9jdG9iZXIgMjAwNykNCkF1dGhvciBOb3RpZmljYXRp b246IERlY2VtYmVyIDExLCAyMDA3DQpGaW5hbCBNYW51c2NyaXB0IER1ZTogSmFudWFyeSAyOCwg MjAwOA0KDQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKg0K --===============0665132388== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --===============0665132388==-- From mip4-bounces@ietf.org Thu Oct 25 20:14:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlCp9-0008GL-Bd; Thu, 25 Oct 2007 20:13:15 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IlCp8-0008G9-0a for mip4-confirm+ok@megatron.ietf.org; Thu, 25 Oct 2007 20:13:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IlCp7-0008Fs-MA; Thu, 25 Oct 2007 20:13:13 -0400 Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IlCp1-00034S-Ce; Thu, 25 Oct 2007 20:13:13 -0400 Received: by bosco.isi.edu (Postfix, from userid 70) id 41AA7E8E5F; Thu, 25 Oct 2007 17:07:01 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20071026000701.41AA7E8E5F@bosco.isi.edu> Date: Thu, 25 Oct 2007 17:07:01 -0700 (PDT) X-Spam-Score: -15.0 (---------------) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Cc: mip4@ietf.org, rfc-editor@rfc-editor.org Subject: [Mip4] RFC 5030 on Mobile IPv4 RADIUS Requirements X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5030 Title: Mobile IPv4 RADIUS Requirements Author: M. Nakhjiri, Ed., K. Chowdhury, A. Lior, K. Leung Status: Informational Date: October 2007 Mailbox: madjid.nakhjiri@motorola.com, kchowdhury@starentnetworks.com, avi@bridgewatersystems.com, kleung@cisco.com Pages: 9 Characters: 20319 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip4-radius-requirements-04.txt URL: http://www.rfc-editor.org/rfc/rfc5030.txt This document provides an applicability statement as well as a scope definition for specifying Remote Authentication Dial-In User Service (RADIUS) extensions to support Mobile IPv4. The goal is to allow specification of RADIUS attributes to assist the Mobile IPv4 signaling procedures. This memo provides information for the Internet community. This document is a product of the Mobility for IPv4 Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Mon Oct 29 10:30:49 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImVdS-0004MO-St; Mon, 29 Oct 2007 10:30:34 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1ImVdR-0004Jq-DA for mip4-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 10:30:33 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImVdR-0004Jh-2A; Mon, 29 Oct 2007 10:30:33 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImVdQ-0002pf-LS; Mon, 29 Oct 2007 10:30:32 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 503C4175D8; Mon, 29 Oct 2007 14:30:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1ImVcv-000711-Rf; Mon, 29 Oct 2007 10:30:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 29 Oct 2007 10:30:01 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: mip4@ietf.org Subject: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-05.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org --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 : Network Mobility (NEMO) Extensions for Mobile IPv4 Author(s) : K. Leung, et al. Filename : draft-ietf-mip4-nemo-v4-base-05.txt Pages : 18 Date : 2007-10-29 This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the mobile network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mip4-nemo-v4-base-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-29102821.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-nemo-v4-base-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-29102821.I-D\@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --NextPart-- From mip4-bounces@ietf.org Mon Oct 29 10:41:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImVo5-0003FQ-Og; Mon, 29 Oct 2007 10:41:33 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1ImVbW-0002kW-P7 for mip4-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 10:28:34 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImVbW-0002kK-Fb for mip4@ietf.org; Mon, 29 Oct 2007 10:28:34 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ImVbW-0001Za-A4 for mip4@ietf.org; Mon, 29 Oct 2007 10:28:34 -0400 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns1.neustar.com (Postfix) with ESMTP id 2DF6726EEC; Mon, 29 Oct 2007 14:28:24 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1ImVbM-0006Bx-2r; Mon, 29 Oct 2007 10:28:24 -0400 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: alexandru.petrescu@motorola.com From: IETF I-D Submission Tool Message-Id: Date: Mon, 29 Oct 2007 10:28:24 -0400 X-Spam-Score: -1.4 (-) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 X-Mailman-Approved-At: Mon, 29 Oct 2007 10:41:32 -0400 Cc: gdommety@cisco.com, kleung@cisco.com, mip4@ietf.org, vidyan@qualcomm.com, Alexandru.Petrescu@motorola.com Subject: [Mip4] New Version Notification for draft-ietf-mip4-nemo-v4-base-05 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org A new version of I-D, draft-ietf-mip4-nemo-v4-base-05.txt has been successfuly submitted by Alexandru Petrescu and posted to the IETF repository. Filename: draft-ietf-mip4-nemo-v4-base Revision: 05 Title: Network Mobility (NEMO) Extensions for Mobile IPv4 Creation_date: 2007-10-29 WG ID: mip4 Number_of_pages: 18 Abstract: This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the mobile network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks. The IETF Secretariat. -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 31 13:47:26 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InHf4-0003tE-OA; Wed, 31 Oct 2007 13:47:26 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1InHf3-0003r2-M9 for mip4-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 13:47:25 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InHf3-0003qo-C8 for mip4@ietf.org; Wed, 31 Oct 2007 13:47:25 -0400 Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1InHex-0001mh-6Y for mip4@ietf.org; Wed, 31 Oct 2007 13:47:25 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-12.tower-119.messagelabs.com!1193852819!31657445!1 X-StarScan-Version: 5.5.12.14.2; banners=.,-,- X-Originating-IP: [144.189.100.103] Received: (qmail 24802 invoked from network); 31 Oct 2007 17:46:59 -0000 Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103) by server-12.tower-119.messagelabs.com with SMTP; 31 Oct 2007 17:46:59 -0000 Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate3.mot.com (8.12.11/Motorola) with ESMTP id l9VHkr7w007171 for ; Wed, 31 Oct 2007 10:46:58 -0700 (MST) Received: from az10vts02.mot.com (az10vts02.mot.com [10.64.251.243]) by az33exr04.mot.com (8.13.1/Vontu) with SMTP id l9VHkrT6006467 for ; Wed, 31 Oct 2007 12:46:53 -0500 (CDT) Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id l9VHkpXJ006400 for ; Wed, 31 Oct 2007 12:46:52 -0500 (CDT) Message-ID: <4728BF85.5030908@gmail.com> Date: Wed, 31 Oct 2007 18:46:45 +0100 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Mobile IPv4 Mailing List Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 071031-0, 31/10/2007), Outbound message X-Antivirus-Status: Clean X-CFilter-Loop: Reflected X-Spam-Score: -4.0 (----) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Subject: [Mip4] Status of draft-ietf-mip4-nemov4-fa X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi, while idnitting ('idnits') draft-ietf-mip4-nemo-v4-base the way it refers draft-ietf-mip4-nemov4-fa: " -- Unexpected draft version: The latest known version of draft-ietf-mip4-nemov4-fa is -00, but you're referring to -01" I think I've seen the NEMOv4 FA version 01 submitted, but is it still available or has it expired? Alex ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 31 13:48:26 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InHfy-0005S9-R7; Wed, 31 Oct 2007 13:48:22 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1InHfx-0005RB-De for mip4-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 13:48:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InHfx-0005R3-44 for mip4@ietf.org; Wed, 31 Oct 2007 13:48:21 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1InHfw-0001rX-19 for mip4@ietf.org; Wed, 31 Oct 2007 13:48:21 -0400 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns0.neustar.com (Postfix) with ESMTP id D9DB53291E; Wed, 31 Oct 2007 17:48:19 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1InHfv-0005Zb-OV; Wed, 31 Oct 2007 13:48:19 -0400 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: alexandru.petrescu@motorola.com From: IETF I-D Submission Tool Message-Id: Date: Wed, 31 Oct 2007 13:48:19 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Cc: gdommety@cisco.com, kleung@cisco.com, mip4@ietf.org, vidyan@qualcomm.com, Alexandru.Petrescu@motorola.com Subject: [Mip4] New Version Notification for draft-ietf-mip4-nemo-v4-base-06 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org A new version of I-D, draft-ietf-mip4-nemo-v4-base-06.txt has been successfuly submitted by Alexandru Petrescu and posted to the IETF repository. Filename: draft-ietf-mip4-nemo-v4-base Revision: 06 Title: Network Mobility (NEMO) Extensions for Mobile IPv4 Creation_date: 2007-10-31 WG ID: mip4 Number_of_pages: 19 Abstract: This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the mobile network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks. The IETF Secretariat. -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 31 13:50:40 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InHi8-0007Do-Bq; Wed, 31 Oct 2007 13:50:36 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1InHi6-0007DS-Ly for mip4-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 13:50:34 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InHi6-0007DI-At; Wed, 31 Oct 2007 13:50:34 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InHi5-0007ps-Ua; Wed, 31 Oct 2007 13:50:34 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 5EF682ACD7; Wed, 31 Oct 2007 17:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1InHha-0007E1-55; Wed, 31 Oct 2007 13:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 31 Oct 2007 13:50:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: mip4@ietf.org Subject: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-06.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org --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 : Network Mobility (NEMO) Extensions for Mobile IPv4 Author(s) : K. Leung, et al. Filename : draft-ietf-mip4-nemo-v4-base-06.txt Pages : 19 Date : 2007-10-31 This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the mobile network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-06.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mip4-nemo-v4-base-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-10-31134817.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-nemo-v4-base-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-10-31134817.I-D\@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --NextPart-- From mip4-bounces@ietf.org Wed Oct 31 13:56:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InHng-0003Xj-1A; Wed, 31 Oct 2007 13:56:20 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1InHne-0003Xe-Nc for mip4-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 13:56:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InHne-0003XW-E2 for mip4@ietf.org; Wed, 31 Oct 2007 13:56:18 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1InHnY-0002ED-4c for mip4@ietf.org; Wed, 31 Oct 2007 13:56:18 -0400 Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l9VHtsia016886 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 31 Oct 2007 10:55:55 -0700 Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com [172.30.36.176]) by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l9VHtsZn013329; Wed, 31 Oct 2007 10:55:54 -0700 (PDT) Received: from NAEX16.na.qualcomm.com ([10.47.6.158]) by SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 31 Oct 2007 10:55:54 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] Status of draft-ietf-mip4-nemov4-fa Date: Wed, 31 Oct 2007 10:55:50 -0700 Message-ID: <2309978910A6A6478C2C7585692B0AF4C821F8@NAEX16.na.qualcomm.com> In-Reply-To: <4728BF85.5030908@gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Status of draft-ietf-mip4-nemov4-fa Thread-Index: Acgb5ntb3iMD+ErIQpq+cnfsGH+HoAAAIdCA References: <4728BF85.5030908@gmail.com> From: "Tsirtsis, George" To: "Alexandru Petrescu" , "Mobile IPv4 Mailing List" X-OriginalArrivalTime: 31 Oct 2007 17:55:54.0263 (UTC) FILETIME=[48311270:01C81BE7] X-Spam-Score: -4.0 (----) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Alex, You probably remember draft-tsirtsis-nemov4-fa-01. When the draft become a WG doc it became draft-mip4-nemov4-fa-00 which I now see it is expired. I will resubmit before the Vancouver deadline. Now the base draft is done I will pick this up again and see if we can progress it. Thanks George -----Original Message----- From: Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com]=20 Sent: Wednesday, October 31, 2007 5:47 PM To: Mobile IPv4 Mailing List Subject: [Mip4] Status of draft-ietf-mip4-nemov4-fa Hi, while idnitting ('idnits') draft-ietf-mip4-nemo-v4-base the way it refers draft-ietf-mip4-nemov4-fa: " -- Unexpected draft version: The latest known version of draft-ietf-mip4-nemov4-fa is -00, but you're referring to -01" I think I've seen the NEMOv4 FA version 01 submitted, but is it still available or has it expired? Alex ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email=20 ______________________________________________________________________ --=20 Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.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://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 31 14:10:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InI0R-0003ig-Dd; Wed, 31 Oct 2007 14:09:31 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1InI0P-0003bk-He for mip4-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 14:09:29 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InI0P-0003bJ-6Y for mip4@ietf.org; Wed, 31 Oct 2007 14:09:29 -0400 Received: from mail119.messagelabs.com ([216.82.241.179]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1InI0O-0000Hn-Rx for mip4@ietf.org; Wed, 31 Oct 2007 14:09:29 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-3.tower-119.messagelabs.com!1193854167!33335452!1 X-StarScan-Version: 5.5.12.14.2; banners=.,-,- X-Originating-IP: [144.189.100.101] Received: (qmail 12567 invoked from network); 31 Oct 2007 18:09:27 -0000 Received: from motgate2.mot.com (HELO motgate2.mot.com) (144.189.100.101) by server-3.tower-119.messagelabs.com with SMTP; 31 Oct 2007 18:09:27 -0000 Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate2.mot.com (8.12.11/Motorola) with ESMTP id l9VI9RCV001848; Wed, 31 Oct 2007 11:09:27 -0700 (MST) Received: from az10vts02.mot.com (az10vts02.mot.com [10.64.251.243]) by az33exr04.mot.com (8.13.1/Vontu) with SMTP id l9VI9QT8025980; Wed, 31 Oct 2007 13:09:26 -0500 (CDT) Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id l9VI9OcS025920; Wed, 31 Oct 2007 13:09:24 -0500 (CDT) Message-ID: <4728C4CE.1020608@gmail.com> Date: Wed, 31 Oct 2007 19:09:18 +0100 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: mip4@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 071031-0, 31/10/2007), Outbound message X-Antivirus-Status: Clean X-CFilter-Loop: Reflected X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: gdommety@cisco.com, kleung@cisco.com, vidyan@qualcomm.com Subject: [Mip4] Re: New Version Notification for draft-ietf-mip4-nemo-v4-base-06 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org IETF I-D Submission Tool wrote: > A new version of I-D, draft-ietf-mip4-nemo-v4-base-06.txt has been successfuly submitted by Alexandru Petrescu and posted to the IETF repository. > > Filename: draft-ietf-mip4-nemo-v4-base > Revision: 06 > Title: Network Mobility (NEMO) Extensions for Mobile IPv4 > Creation_date: 2007-10-31 > WG ID: mip4 > Number_of_pages: 19 Hi, here's the changelog from 05 to this version: > -substituted "TBA" for "1" in Sub-type of Mobile Network Request > Extension. > -substituted "TBA" for "0" in Code of Mobile Network > Acknowledgement Extension and in the IANA Section. > -modified the IANA section to request definition two new spaces > (instead of just defining new values) for Sub-Type of Mobile > Network Extensions and for Code Values for Mobile Network > Acknowledgement Extension, and to suggest "Expert Review" as > method of new assignments in these two spaces (and not > necessarily "IETF Conssensus"). Alex ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 31 14:13:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InI4e-0000zO-Bx; Wed, 31 Oct 2007 14:13:52 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1InI4d-0000qq-6P for mip4-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 14:13:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InI4c-0000pH-SP; Wed, 31 Oct 2007 14:13:50 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1InI4b-0003Ck-HT; Wed, 31 Oct 2007 14:13:50 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-12.tower-128.messagelabs.com!1193854426!14696736!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [144.189.100.101] Received: (qmail 16998 invoked from network); 31 Oct 2007 18:13:46 -0000 Received: from motgate2.mot.com (HELO motgate2.mot.com) (144.189.100.101) by server-12.tower-128.messagelabs.com with SMTP; 31 Oct 2007 18:13:46 -0000 Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate2.mot.com (8.12.11/Motorola) with ESMTP id l9VIDf4j002984; Wed, 31 Oct 2007 11:13:46 -0700 (MST) Received: from az10vts04.mot.com (az10vts04.mot.com [10.64.251.245]) by az33exr04.mot.com (8.13.1/Vontu) with SMTP id l9VIDeq3028910; Wed, 31 Oct 2007 13:13:40 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id l9VIDd2N028899; Wed, 31 Oct 2007 13:13:39 -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: Wed, 31 Oct 2007 14:13:37 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Request to advance draft-ietf-mip4-nemo-v4-base-06.txt to Proposed Standard Thread-Index: Acgb6cIfwzfYovScSOahQlI0lMnNnQ== From: "McCann Peter-A001034" To: "IESG Secretary" X-CFilter-Loop: Reflected X-Spam-Score: -4.0 (----) X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576 Cc: mip4@ietf.org Subject: [Mip4] Request to advance draft-ietf-mip4-nemo-v4-base-06.txt to Proposed Standard X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Dear iesg-secretary, This is a request to advance the document draft-ietf-mip4-nemo-v4-base-06.txt to Proposed Standard RFC status. Please see the questionnaire answers below. > (1.a) Who is the Document Shepherd for this document? Has the > Document Shepherd personally reviewed this version of the > document and, in particular, does he or she believe this > version is ready for forwarding to the IESG for publication? Document shepherd: Pete McCann I have reviewed this version of the I-D and believe it is ready for=20 IESG review and publication. > (1.b) Has the document had adequate review both from key WG members > and from key non-WG members? Does the Document Shepherd have > any concerns about the depth or breadth of the reviews that > have been performed? The draft has been reviewed extensively by the working group, but has not gotten much exposure to non-WG members. I have no concern about the depth or breadth of the reviews. > (1.c) Does the Document Shepherd have concerns that the document > needs more review from a particular or broader perspective, > e.g., security, operational complexity, someone familiar with > AAA, internationalization, or XML? Perhaps the draft would benefit by some review from the Routing Area, due to its mention of running dynamic routing protocols over the tunnel between MN and HA. Hopefully this can happen=20 as part of IETF last call. > (1.d) Does the Document Shepherd have any specific concerns or > issues with this document that the Responsible Area Director > and/or the IESG should be aware of? For example, perhaps he > or she is uncomfortable with certain parts of the document, or > has concerns whether there really is a need for it. In any > event, if the WG has discussed those issues and has indicated > that it still wishes to advance the document, detail those > concerns here. Has an IPR disclosure related to this document > been filed? If so, please include a reference to the > disclosure and summarize the WG discussion and conclusion on > this issue. I have no areas of concern. No disclosures relating to the draft have been filed at this time. However, there is a rumor that one company does indeed hold IPR on the solution. > (1.e) How solid is the WG consensus behind this document? Does it > represent the strong concurrence of a few individuals, with > others being silent, or does the WG as a whole understand and > agree with it? There is strong WG consensus to advance the document. Consensus to advance it was exhibited during WGLC. > (1.f) Has anyone threatened an appeal or otherwise indicated extreme > discontent? If so, please summarize the areas of conflict in > separate email messages to the Responsible Area Director. (It > should be in a separate email because this questionnaire is > entered into the ID Tracker.) No appeals have been threatened. > (1.g) Has the Document Shepherd personally verified that the > document satisfies all ID nits? (See > http://www.ietf.org/ID-Checklist.html and > http://tools.ietf.org/tools/idnits/.) Boilerplate checks are > not enough; this check needs to be thorough. Has the document > met all formal review criteria it needs to, such as the MIB > Doctor, media type, and URI type reviews? If the document > does not already indicate its intended status at the top of > the first page, please indicate the intended status here. No nits were found during automatic checking or manual inspection. The document does have 2 informative references to drafts, which should be published in the not-to-distant future. > (1.h) Has the document split its references into normative and > informative? Are there normative references to documents that > are not ready for advancement or are otherwise in an unclear > state? If such normative references exist, what is the > strategy for their completion? Are there normative references > that are downward references, as described in [RFC3967]? If > so, list these downward references to support the Area > Director in the Last Call procedure for them [RFC3967]. The document split references into normative and informative sections. No downrefs exist in the normative references section. > (1.i) Has the Document Shepherd verified that the document's IANA > Considerations section exists and is consistent with the body > of the document? If the document specifies protocol > extensions, are reservations requested in appropriate IANA > registries? Are the IANA registries clearly identified? If > the document creates a new registry, does it define the > proposed initial contents of the registry and an allocation > procedure for future registrations? Does it suggest a > reasonable name for the new registry? See [RFC2434]. If the > document describes an Expert Review process, has the Document > Shepherd conferred with the Responsible Area Director so that > the IESG can appoint the needed Expert during IESG > Evaluation? The IANA considerations section is in the document and is complete. The document creates two new number spaces, each with an assignment policy of "Expert Review." We have not yet designated an Expert, but will confer with the ADs soon. > (1.j) Has the Document Shepherd verified that sections of the > document that are written in a formal language, such as XML > code, BNF rules, MIB definitions, etc., validate correctly in > an automated checker? No such formal languages are used. > (1.k) The IESG approval announcement includes a Document > Announcement Write-Up. Please provide such a Document > Announcement Write-Up. Recent examples can be found in the > "Action" announcements for approved documents. The approval > announcement contains the following sections: Technical Summary This document defines some new extensions to Mobile IPv4 that allow the Mobile Node to communicate with the Home Agent about additional network prefixes that it may serve in the capacity of a Mobile Router. A Mobile Router can be used to provide connectivity and mobility to an entire mobile network without any modification to other nodes in the mobile network. While it is technically possible to create a Mobile Router through static configuration, this extension allows the network prefixes to be signaled in Registration Request and Reply messages, so that the MN and HA can be explicit about which networks are requested and granted to the Mobile Router. Working Group Summary The working group made some recent changes to indicate that this is just an extension to the Mobile IPv4 protocol, rather than a new mobility management protocol. The document went through last call without any major disagreements coming up. Document Quality The document was reviewed for quality by Pete McCann. Personnel Document shepherd: Pete McCann Responsible AD: Jari Arkko -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 31 18:53:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InMQw-0007Mh-OH; Wed, 31 Oct 2007 18:53:10 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1InMQs-0007Kb-TK for mip4-confirm+ok@megatron.ietf.org; Wed, 31 Oct 2007 18:53:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InMQs-0007Jy-Ii; Wed, 31 Oct 2007 18:53:06 -0400 Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1InMQm-0001B5-Ct; Wed, 31 Oct 2007 18:53:06 -0400 Received: by bosco.isi.edu (Postfix, from userid 70) id C6D59E9EDE; Wed, 31 Oct 2007 15:52:44 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20071031225244.C6D59E9EDE@bosco.isi.edu> Date: Wed, 31 Oct 2007 15:52:44 -0700 (PDT) X-Spam-Score: -15.0 (---------------) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Cc: mip4@ietf.org, rfc-editor@rfc-editor.org Subject: [Mip4] RFC 4988 on Mobile IPv4 Fast Handovers X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4988 Title: Mobile IPv4 Fast Handovers Author: R. Koodli, C. Perkins Status: Experimental Date: October 2007 Mailbox: rajeev.koodli@nokia.com, charles.perkins@nokia.com Pages: 28 Characters: 57921 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip4-fmipv4-07.txt URL: http://www.rfc-editor.org/rfc/rfc4988.txt This document adapts the Mobile IPv6 Fast Handovers to improve delay and packet loss resulting from Mobile IPv4 handover operations. Specifically, this document addresses movement detection, IP address configuration, and location update latencies during a handover. For reducing the IP address configuration latency, the document proposes that the new Care-of Address is always made to be the new access router's IP address. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Mobility for IPv4 Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/