From robmcm@microsoft.com Fri Oct 15 19:09:51 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7AB03A6B0B for ; Fri, 15 Oct 2010 19:09:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SPcBJg6ZcWyr for ; Fri, 15 Oct 2010 19:09:49 -0700 (PDT) Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id BB3653A63EB for ; Fri, 15 Oct 2010 19:09:49 -0700 (PDT) Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 15 Oct 2010 19:11:12 -0700 Received: from TK5EX14MBXC127.redmond.corp.microsoft.com ([169.254.6.93]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.01.0218.012; Fri, 15 Oct 2010 19:11:11 -0700 From: Robert McMurray To: "ftpext@ietf.org" Thread-Topic: Submitting new drafts Thread-Index: Acts12dO7mju2PbkRH6PeH4GsapAbg== Date: Sat, 16 Oct 2010 02:11:11 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [157.54.51.78] Content-Type: multipart/mixed; boundary="_002_A5FC996C3C37DC4DA5076F1046B5674C431FD205TK5EX14MBXC127r_" MIME-Version: 1.0 Subject: [ftpext] Submitting new drafts X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Oct 2010 02:09:52 -0000 --_002_A5FC996C3C37DC4DA5076F1046B5674C431FD205TK5EX14MBXC127r_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'd like to submit a new draft (see attached) that is unrelated to my other= draft - should we be using FTPEXT2 as the WG? Or should continue to submit= as individual drafts to the Applications Area? Robert McMurray Office Content Publishing (UA) Email: robmcm@microsoft.com --_002_A5FC996C3C37DC4DA5076F1046B5674C431FD205TK5EX14MBXC127r_ Content-Type: text/plain; name="draft-mcmurray-ftp-agnt-00.txt" Content-Description: draft-mcmurray-ftp-agnt-00.txt Content-Disposition: attachment; filename="draft-mcmurray-ftp-agnt-00.txt"; size=16097; creation-date="Sat, 16 Oct 2010 02:06:55 GMT"; modification-date="Sat, 16 Oct 2010 01:59:44 GMT" Content-Transfer-Encoding: base64 DQoNCg0KDQoNCg0KTmV0d29yayBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgIFIuIE1jTXVycmF5DQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBNaWNyb3NvZnQNClVwZGF0ZXM6IDk1 OSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIE9jdG9iZXIg MjAxMA0KSW50ZW5kZWQgc3RhdHVzOiBTdGFuZGFyZHMgVHJhY2sNCkV4cGlyZXM6IEFwcmlsIDEz LCAyMDExDQoNCg0KRmlsZSBUcmFuc2ZlciBQcm90b2NvbCBBR05UIENvbW1hbmQgZm9yIFVzZXIt RlRQIFByb2Nlc3MgSWRlbnRpZmljYXRpb24NCiAgICAgICAgICAgICAgICAgICAgICAgZHJhZnQt bWNtdXJyYXktZnRwLWFnbnQtMDANCg0KU3RhdHVzIG9mIHRoaXMgTWVtbw0KDQogICBUaGlzIElu dGVybmV0LURyYWZ0IGlzIHN1Ym1pdHRlZCB0byBJRVRGIGluIGZ1bGwgY29uZm9ybWFuY2Ugd2l0 aCB0aGUNCiAgIHByb3Zpc2lvbnMgb2YgQkNQIDc4IGFuZCBCQ1AgNzkuICBUaGlzIGRvY3VtZW50 IG1heSBjb250YWluIG1hdGVyaWFsDQogICBmcm9tIElFVEYgRG9jdW1lbnRzIG9yIElFVEYgQ29u dHJpYnV0aW9ucyBwdWJsaXNoZWQgb3IgbWFkZSBwdWJsaWNseQ0KICAgYXZhaWxhYmxlIGJlZm9y ZSBOb3ZlbWJlciAxMCwgMjAwOC4gIFRoZSBwZXJzb24ocykgY29udHJvbGxpbmcgdGhlDQogICBj b3B5cmlnaHQgaW4gc29tZSBvZiB0aGlzIG1hdGVyaWFsIG1heSBub3QgaGF2ZSBncmFudGVkIHRo ZSBJRVRGDQogICBUcnVzdCB0aGUgcmlnaHQgdG8gYWxsb3cgbW9kaWZpY2F0aW9ucyBvZiBzdWNo IG1hdGVyaWFsIG91dHNpZGUgdGhlDQogICBJRVRGIFN0YW5kYXJkcyBQcm9jZXNzLiAgV2l0aG91 dCBvYnRhaW5pbmcgYW4gYWRlcXVhdGUgbGljZW5zZSBmcm9tDQogICB0aGUgcGVyc29uKHMpIGNv bnRyb2xsaW5nIHRoZSBjb3B5cmlnaHQgaW4gc3VjaCBtYXRlcmlhbHMsIHRoaXMNCiAgIGRvY3Vt ZW50IG1heSBub3QgYmUgbW9kaWZpZWQgb3V0c2lkZSB0aGUgSUVURiBTdGFuZGFyZHMgUHJvY2Vz cywgYW5kDQogICBkZXJpdmF0aXZlIHdvcmtzIG9mIGl0IG1heSBub3QgYmUgY3JlYXRlZCBvdXRz aWRlIHRoZSBJRVRGIFN0YW5kYXJkcw0KICAgUHJvY2VzcywgZXhjZXB0IHRvIGZvcm1hdCBpdCBm b3IgcHVibGljYXRpb24gYXMgYW4gUkZDIG9yIHRvDQogICB0cmFuc2xhdGUgaXQgaW50byBsYW5n dWFnZXMgb3RoZXIgdGhhbiBFbmdsaXNoLg0KDQogICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtp bmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZw0KICAgVGFzayBGb3JjZSAo SUVURiksIGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5vdGUgdGhhdA0KICAg b3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGUgd29ya2luZyBkb2N1bWVudHMgYXMgSW50 ZXJuZXQtDQogICBEcmFmdHMuDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1l bnRzIHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocw0KICAgYW5kIG1heSBiZSB1cGRh dGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnkNCiAg IHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVm ZXJlbmNlDQogICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBp biBwcm9ncmVzcyIuDQoNCiAgIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtRHJhZnRzIGNh biBiZSBhY2Nlc3NlZCBhdA0KICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pZXRmLzFpZC1hYnN0cmFj dHMudHh0Lg0KDQogICBUaGUgbGlzdCBvZiBJbnRlcm5ldC1EcmFmdCBTaGFkb3cgRGlyZWN0b3Jp ZXMgY2FuIGJlIGFjY2Vzc2VkIGF0DQogICBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1s Lg0KDQogICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIEFwcmlsIDEzLCAyMDEx Lg0KDQpDb3B5cmlnaHQNCg0KICAgQ29weXJpZ2h0IChjKSAyMDEwIElFVEYgVHJ1c3QgYW5kIHRo ZSBwZXJzb25zIGlkZW50aWZpZWQgYXMgdGhlDQogICBkb2N1bWVudCBhdXRob3JzLiAgQWxsIHJp Z2h0cyByZXNlcnZlZC4NCg0KICAgVGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIEJDUCA3OCBh bmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbA0KICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRG IERvY3VtZW50cw0KDQpNY011cnJheSAgICAgICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAxMywg MjAxMSAgICAgICAgICAgICAgICAgW1BhZ2UgMV0NCgwNCklOVEVSTkVULURSQUZUICAgICAgICAg ICAgICAgRlRQIEFHTlQgQ29tbWFuZCAgICAgICAgICAgICAgIE9jdG9iZXIgMjAxMA0KDQogICAo aHR0cDovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRh dGUgb2YNCiAgIHB1YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuICBQbGVhc2UgcmV2aWV3IHRo ZXNlIGRvY3VtZW50cw0KICAgY2FyZWZ1bGx5LCBhcyB0aGV5IGRlc2NyaWJlIHlvdXIgcmlnaHRz IGFuZCByZXN0cmljdGlvbnMgd2l0aCByZXNwZWN0DQogICB0byB0aGlzIGRvY3VtZW50Lg0KDQpB YnN0cmFjdA0KDQogICBUaGlzIGRvY3VtZW50IGRlZmluZXMgYSBuZXcgRlRQIGNvbW1hbmQgdGhh dCBwcm92aWRlcyBhIG1lY2hhbmlzbSB0bw0KICAgaWRlbnRpZnkgdGhlIEZUUCBjbGllbnQgcHJv Y2VzcyB0aGF0IGlzIGJlaW5nIHVzZWQgdG8gY29ubmVjdCB0byBhbg0KICAgRlRQIHNlcnZlci4N Cg0KVGFibGUgb2YgQ29udGVudHMNCg0KICAgMS4gSW50cm9kdWN0aW9uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLm5uDQogICAyLiBEb2N1bWVudCBD b252ZW50aW9ucyAgLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4ubm4N CiAgICAgMi4xLiBCYXNpYyBUb2tlbnMgIC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi5ubg0KICAgICAyLjIuIFNlcnZlciBSZXBsaWVzICAuLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLm5uDQogICAzLiBUaGUgQUdOVCBjb21tYW5k IC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4ubm4NCiAgICAg My4xLiBTeW50YXggb2YgdGhlIEFHTlQgY29tbWFuZCAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi5ubg0KICAgICAzLjIuIEFHTlQgY29tbWFuZCBzZW1hbnRpY3MgLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLm5uDQogICAgIDMuMy4gQUdOVCBjb21tYW5kIGVycm9y cyAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4ubm4NCiAgICAgMy40LiBG RUFUIHJlc3BvbnNlIGZvciBBR05UIGNvbW1hbmQgLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li5ubg0KICAgNC4gU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLm5uDQogICA1LiBJQU5BIENvbnNpZGVyYXRpb25zIC4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4ubm4NCiAgIDYuIFJlZmVyZW5jZXMg Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi5ubg0K ICAgICA2LjEgTm9ybWF0aXZlIFJlZmVyZW5jZXMgLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLm5uDQogICAgIDYuMiBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzIC4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4ubm4NCiAgIEFja25vd2xlZGdtZW50cyAuLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi5ubg0KICAgQXV0 aG9yJ3MgQWRkcmVzcyAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLm5uDQoNCjEuIEludHJvZHVjdGlvbg0KICAgDQogICBUaGUgRmlsZSBUcmFuc2ZlciBQ cm90b2NvbCAoRlRQKSBwcm92aWRlcyBubyBtZWNoYW5pc20gZm9yIGEgdXNlci1GVFANCiAgIHBy b2Nlc3MgdG8gc3BlY2lmeSBhbnkgbWVhbmluZ2Z1bCBpbmZvcm1hdGlvbiBhYm91dCBpdHNlbGYg dG8gYW4gRlRQDQogICBzZXJ2ZXItUEksIHdoaWNoIGxpbWl0cyB0aGUgZ2F0aGVyaW5nIG9mIHN0 YXRpc3RpY2FsIGluZm9ybWF0aW9uIGZvcg0KICAgYSBzZXJ2ZXItRlRQIHByb2Nlc3MgYW5kIGxp bWl0cyB0aGUgYWJpbGl0eSBmb3IgYW4gRlRQIHNlcnZlci1QSSB0bw0KICAgdGFpbG9yIHJlc3Bv bnNlcyBmb3IgYSBzcGVjaWZpYyB1c2VyLUZUUCBwcm9jZXNzLiAgSFRUUCByZXNvbHZlcyB0aGlz DQogICBpc3N1ZSBpbiBbUkZDMTk0NV0gYW5kIFtSRkMyNjE2XSB0aHJvdWdoIHRoZSBkZWZpbml0 aW9uIG9mIHRoZQ0KICAgVXNlci1BZ2VudCByZXF1ZXN0IGhlYWRlci4NCg0KICAgVGhlIGdvYWwg b2YgdGhpcyBkb2N1bWVudCBpcyB0byBicmluZyBhIHNpbWlsYXIgbGV2ZWwgb2YgZmVhdHVyZQ0K ICAgcGFyaXR5IHRvIEZUUCBieSBpbnRyb2R1Y2luZyBhIG5ldyBBR05UIGNvbW1hbmQgdGhhdCBh bGxvd3MgYQ0KICAgdXNlci1GVFAgcHJvY2VzcyB0byBzcGVjaWZ5IGluZm9ybWF0aW9uIGFib3V0 IGl0c2VsZiB0byBhbiBGVFANCiAgIHNlcnZlci1QSS4NCg0KICAgW1sgRGlzY3Vzc2lvbiBvZiB0 aGlzIGRyYWZ0IHNob3VsZCB0YWtlIHBsYWNlIG9uIGZ0cGV4dEBpZXRmLm9yZyAob3INCiAgIGFw cHMtZGlzY3Vzc0BpZXRmLm9yZyBpZiBuZWNlc3NhcnkpLiBdXQ0KDQoyLiBEb2N1bWVudCBDb252 ZW50aW9ucw0KDQogICBUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVE IiwgIlNIQUxMIiwgIlNIQUxMIE5PVCIsDQoNCk1jTXVycmF5ICAgICAgICAgICAgICAgICBFeHBp cmVzIEFwcmlsIDEzLCAyMDExICAgICAgICAgICAgICAgICBbUGFnZSAyXQ0KDA0KSU5URVJORVQt RFJBRlQgICAgICAgICAgICAgICBGVFAgQUdOVCBDb21tYW5kICAgICAgICAgICAgICAgT2N0b2Jl ciAyMDEwDQoNCiAgICJTSE9VTEQiLCAiU0hPVUxEIE5PVCIsICJSRUNPTU1FTkRFRCIsICAiTUFZ IiwgYW5kICJPUFRJT05BTCIgaW4NCiAgIHRoaXMgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJl dGVkIGFzIGRlc2NyaWJlZCBpbiBbUkZDMjExOV0uDQoNCiAgIEluIGV4YW1wbGVzLCAiQz4iIGFu ZCAiUz4iIGluZGljYXRlIGxpbmVzIHNlbnQgYnkgdGhlIGNsaWVudCBhbmQNCiAgIHNlcnZlciwg cmVzcGVjdGl2ZWx5Lg0KDQogICBUaGlzIGRvY3VtZW50IGFsc28gdXNlcyBub3RhdGlvbiBkZWZp bmVkIGluIFtSRkM5NTldIGFuZCBbUkZDMTEyM10uDQogICBJbiBwYXJ0aWN1bGFyLCB0aGUgdGVy bXMgInJlcGx5IiwgInVzZXIiLCAiTlZGUyIsICJOVlQiLCAiZmlsZSIsDQogICAicGF0aG5hbWUi LCAiRlRQIGNvbW1hbmRzIiwgIkRUUCIsICJ1c2VyLUZUUCBwcm9jZXNzIiwgInVzZXItUEkiLA0K ICAgInVzZXItRFRQIiwgInNlcnZlci1GVFAgcHJvY2VzcyIsICJzZXJ2ZXItUEkiLCAic2VydmVy LURUUCIsICJtb2RlIiwNCiAgICJ0eXBlIiwgImNvbnRyb2wgY29ubmVjdGlvbiIsICJkYXRhIGNv bm5lY3Rpb24iLCBhbmQgIkFTQ0lJIiwgYXJlDQogICBhbGwgdXNlZCBoZXJlIGFzIGRlZmluZWQg dGhlcmUuDQoNCiAgIFN5bnRheCByZXF1aXJlZCBpcyBkZWZpbmVkIHVzaW5nIHRoZSBBdWdtZW50 ZWQgQk5GIGRlZmluZWQgaW4NCiAgIFtSRkM1MjM0XS4gU29tZSBnZW5lcmFsIEFCTkYgZGVmaW5p dGlvbnMgYXJlIHJlcXVpcmVkIHRocm91Z2hvdXQgdGhlDQogICBkb2N1bWVudDsgdGhvc2Ugd2ls bCBiZSBkZWZpbmVkIGxhdGVyIGluIHRoaXMgc2VjdGlvbi4gIEF0IGZpcnN0DQogICByZWFkaW5n LCBpdCBtYXkgYmUgd2lzZSB0byBzaW1wbHkgcmVjYWxsIHRoYXQgdGhlc2UgZGVmaW5pdGlvbnMN CiAgIGV4aXN0IGhlcmUsIGFuZCBza2lwIHRvIHRoZSBuZXh0IHNlY3Rpb24uDQoNCjIuMS4gQmFz aWMgVG9rZW5zDQoNCiAgIFRoaXMgZG9jdW1lbnQgaW1wb3J0cyB0aGUgY29yZSBkZWZpbml0aW9u cyBnaXZlbiBpbiBBcHBlbmRpeCBCIG9mDQogICBbUkZDNTIzNF0uICBUaGVyZSBkZWZpbml0aW9u cyB3aWxsIGJlIGZvdW5kIGZvciBiYXNpYyBBQk5GIGVsZW1lbnRzDQogICBsaWtlIEFMUEhBLCBE SUdJVCwgU1AsIGV0Yy4gIFRvIHRoYXQsIHRoZSBmb2xsb3dpbmcgdGVybSBpcyBhZGRlZA0KICAg Zm9yIHVzZSBpbiB0aGlzIGRvY3VtZW50Lg0KDQogICAgICAgIFRDSEFSID0gVkNIQVIgLyBTUCAv IEhUQUIgICAgOyB2aXNpYmxlIHBsdXMgd2hpdGUgc3BhY2UNCg0KICAgVGhlIFZDSEFSIChmcm9t IFtSRkM1MjM0XSkgYW5kIFRDSEFSIHJ1bGVzIGdpdmUgYmFzaWMgY2hhcmFjdGVyDQogICB0eXBl cyBmcm9tIHZhcnlpbmcgc3ViLXNldHMgb2YgdGhlIEFTQ0lJIGNoYXJhY3RlciBzZXQgZm9yIHVz ZSBpbg0KICAgdmFyaW91cyBjb21tYW5kcyBhbmQgcmVzcG9uc2VzLg0KDQogICBOb3RlIHRoYXQg aW4gQUJORiwgc3RyaW5nIGxpdGVyYWxzIGFyZSBjYXNlIGluc2Vuc2l0aXZlLiAgVGhhdA0KICAg Y29udmVudGlvbiBpcyBwcmVzZXJ2ZWQgaW4gdGhpcyBkb2N1bWVudCwgYW5kIGltcGxpZXMgdGhh dCBGVFANCiAgIGNvbW1hbmRzIGFuZCBwYXJhbWV0ZXJzIHRoYXQgYXJlIGFkZGVkIGJ5IHRoaXMg c3BlY2lmaWNhdGlvbiBoYXZlDQogICB2YWx1ZXMgdGhhdCBjYW4gYmUgcmVwcmVzZW50ZWQgaW4g YW55IGNhc2UuICBUaGF0IGlzLCAiQUdOVCIgaXMgdGhlDQogICBzYW1lIGFzICJhZ250IiwgIkFn bnQiLCAiQWdOdCIsIGV0Yy4sIGFuZCAiRm9vQmFyLzEuMCIgaXMgdGhlDQogICBzYW1lIGFzICJm b29iYXIvMS4wIiwgIkZPT0JBUi8xLjAiLCBldGMuDQoNCjIuMi4gU2VydmVyIFJlcGxpZXMNCg0K ICAgU2VjdGlvbiA0LjIgb2YgW1JGQzk1OV0gZGVmaW5lcyB0aGUgZm9ybWF0IGFuZCBtZWFuaW5n IG9mIHJlcGxpZXMNCiAgIGJ5IHRoZSBzZXJ2ZXItUEkgdG8gRlRQIGNvbW1hbmRzIGZyb20gdGhl IHVzZXItUEkuICBUaG9zZSByZXBseQ0KICAgY29udmVudGlvbnMgYXJlIHVzZWQgaGVyZSB3aXRo b3V0IGNoYW5nZS4NCg0KICAgICAgICBlcnJvci1yZXNwb25zZSA9IGVycm9yLWNvZGUgU1AgKlRD SEFSIENSTEYNCiAgICAgICAgZXJyb3ItY29kZSAgICAgPSAoIjQiIC8gIjUiKSAyRElHSVQNCg0K ICAgSW1wbGVtZW50ZXJzIHNob3VsZCBub3RlIHRoYXQgdGhlIEFCTkYgc3ludGF4ICh3aGljaCB3 YXMgbm90IHVzZWQgaW4NCiAgIFtSRkM5NTldKSB1c2VkIGluIHRoaXMgZG9jdW1lbnQsIGFuZCBv dGhlciBGVFAgcmVsYXRlZCBkb2N1bWVudHMsDQogICBzb21ldGltZXMgc2hvd3MgcmVwbGllcyB1 c2luZyB0aGUgb25lIGxpbmUgZm9ybWF0LiAgVW5sZXNzIG90aGVyd2lzZQ0KDQpNY011cnJheSAg ICAgICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAxMywgMjAxMSAgICAgICAgICAgICAgICAgW1Bh Z2UgM10NCgwNCklOVEVSTkVULURSQUZUICAgICAgICAgICAgICAgRlRQIEFHTlQgQ29tbWFuZCAg ICAgICAgICAgICAgIE9jdG9iZXIgMjAxMA0KDQogICBleHBsaWNpdGx5IHN0YXRlZCwgdGhhdCBp cyBub3QgaW50ZW5kZWQgdG8gaW1wbHkgdGhhdCBtdWx0aS1saW5lDQogICByZXNwb25zZXMgYXJl IG5vdCBwZXJtaXR0ZWQuICBJbXBsZW1lbnRlcnMgc2hvdWxkIGFzc3VtZSB0aGF0LCB1bmxlc3MN CiAgIHN0YXRlZCB0byB0aGUgY29udHJhcnksIGFueSByZXBseSB0byBhbnkgRlRQIGNvbW1hbmQg KGluY2x1ZGluZyBRVUlUKQ0KICAgY2FuIGJlIG9mIHRoZSBtdWx0aS1saW5lIGZvcm1hdCBkZXNj cmliZWQgaW4gW1JGQzk1OV0uDQoNCiAgIFRocm91Z2hvdXQgdGhpcyBkb2N1bWVudCwgcmVwbGll cyB3aWxsIGJlIGlkZW50aWZpZWQgYnkgdGhlIHRocmVlDQogICBkaWdpdCBjb2RlIHRoYXQgaXMg dGhlaXIgZmlyc3QgZWxlbWVudC4gIFRodXMgdGhlIHRlcm0gIjUwMCByZXBseSINCiAgIG1lYW5z IGEgcmVwbHkgZnJvbSB0aGUgc2VydmVyLVBJIHVzaW5nIHRoZSB0aHJlZSBkaWdpdCBjb2RlICI1 MDAiLg0KDQozLiBUaGUgQUdOVCBjb21tYW5kDQoNCiAgIEEgbmV3IGNvbW1hbmQgIkFHTlQiIGlz IGFkZGVkIHRvIHRoZSBGVFAgY29tbWFuZCBzZXQgdG8gYWxsb3cgYQ0KICAgdXNlci1GVFAgcHJv Y2VzcyB0byBpZGVudGlmeSBpdHNlbGYgYW5kIHByb3ZpZGUgb3RoZXIgaW5mb3JtYXRpb24NCiAg IHRoYXQgbWF5IGJlIG1lYW5pbmdmdWwgYWJvdXQgdGhlIHVzZXItRlRQIHByb2Nlc3MgdG8gYW4g RlRQDQogICBzZXJ2ZXItUEkuDQoNCiAgIEJ5IHVzaW5nIHRoaXMgY29tbWFuZCwgYSB1c2VyLUZU UCBwcm9jZXNzIG1heSBhZHZlcnRpc2UgKHRocm91Z2ggYQ0KICAgcGFyYW1ldGVyKSBhIHBhcnRp Y3VsYXIgcHJvZHVjdCB2ZXJzaW9uIHRvIGEgc2VydmVyLVBJLCBvciBpdCBtYXkNCiAgIHNwZWNp Znkgc3VwcG9ydCBmb3Igc3BlY2lmaWMgZmVhdHVyZXMsIG9yIGl0IG1heSBpbmNsdWRlIGluZm9y bWF0aW9uDQogICB0aGF0IGlzIHB1cmVseSBmb3Igc3RhdGlzdGljYWwgcHVycG9zZXMuICBUaGUg c2VydmVyLVBJIG1heSBjaG9vc2UNCiAgIHRvIGNvbXBsZXRlbHkgaWdub3JlIGFueSBvZiB0aGlz IGluZm9ybWF0aW9uLCBvciBpdCBtYXkgY2hvb3NlIHRvIHVzZQ0KICAgdGhlIGluZm9ybWF0aW9u IGZvciB0aGUgY3VycmVudCBGVFAgc2Vzc2lvbi4gIEZvciBleGFtcGxlLCBhIHVzZXItRlRQDQog ICBwcm9jZXNzIG1heSBzcGVjaWZ5IGl0cyBob3N0IG9wZXJhdGluZyBzeXN0ZW0sIHdoaWNoIG1h eSBoYXZlIG5vDQogICBpbXBhY3Qgb24gdGhlIHNlc3Npb24uICBJbiBjb250cmFzdCwgYW4gaW1w bGVtZW50ZXIgdGhhdCBjcmVhdGVzIGJvdGgNCiAgIGEgdXNlci1QSSBhbmQgc2VydmVyLVBJIG1h eSBjaG9vc2UgdG8gdXNlIHRoZSBwYXJhbWV0ZXIgZm9yIHRoZSBBR05UDQogICBjb21tYW5kIHRv IHRhaWxvciB0aGUgc2VydmVyLVBJIHJlc3BvbnNlcyBmb3IgdGhlaXIgc3BlY2lmaWMgdXNlci1Q STsNCiAgIHN1Y2ggYXMgcmVzcG9uc2VzIHRvIGNvbW1hbmRzIGxpa2UgTElTVC9OTFNULg0KDQog ICBFeGFtcGxlczoNCg0KICAgICAgIEFHTlQgRm9vLzEuMA0KICAgICAgIEFHTlQgQmFyLzQuNSAo VU5JWCkNCiAgICAgICBBR05UIEZvb0Jhci82LjEgKFdpbmRvd3M7IFRMUy8xLjI7IC5ORVQgNC4w KQ0KICAgICAgIEFHTlQgQmFyRm9vLzIuMSAoTGludXg7IGVuLXVzOyBSRkMyNjQwOyBSRkMzNjU5 OyBSRkM0MjE3KQ0KICAgDQogICBJbiB0aGUgcHJlY2VkaW5nIGV4YW1wbGVzLCBtb3N0IG9mIHRo ZSBpbmZvcm1hdGlvbiBpcyBzdHJpY3RseSBmb3INCiAgIGluZm9ybWF0aXZlIHB1cnBvc2VzLiAg SG93ZXZlciwgdGhlICJlbi11cyIgaWRlbnRpZmllciBpcyBhIHByYWN0aWNhbA0KICAgZXhhbXBs ZSBvZiBpbmZvcm1hdGlvbiB0aGF0IHNob3VsZCBvbmx5IGJlIHVzZWQgZm9yIHN0YXRpc3RpY2Fs DQogICB1c2FnZTsgc3VwcG9ydCBmb3IgaW50ZXJuYXRpb25hbGl6YXRpb24gTVVTVCBiZSBoYW5k bGVkIHRocm91Z2ggdGhlDQogICBtZWNoYW5pc21zIHRoYXQgYXJlIGRlc2NyaWJlZCBpbiBbUkZD MjY0MF0gYW5kIE1VU1QgTk9UIGJlIHNwZWNpZmllZA0KICAgdGhyb3VnaCB0aGUgQUdOVCBjb21t YW5kLg0KDQozLjEuIFN5bnRheCBvZiB0aGUgQUdOVCBjb21tYW5kDQoNCiAgIFRoZSBBR05UIGNv bW1hbmQgaXMgZGVmaW5lZCBhcyBmb2xsb3dzLg0KDQogICAgIGFnZW50LWNvbW1hbmQgPSAiQUdO VCIgU1AgdXNlci1hZ2VudCBDUkxGDQogICAgIHVzZXItYWdlbnQgICAgPSBhZ2VudGNoYXIgWyoo YWdlbnRjaGFyKV0NCiAgICAgYWdlbnRjaGFyICAgICA9IEFMUEhBIC8gRElHSVQgLyBTUCAvICIt IiAvICJfIiAvICIvIiAvICIuIiAvICIsIg0KICAgICAgICAgICAgICAgICAgICAgLyAiOyIgLyAi KCIgLyAiKSINCg0KDQpNY011cnJheSAgICAgICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAxMywg MjAxMSAgICAgICAgICAgICAgICAgW1BhZ2UgNF0NCgwNCklOVEVSTkVULURSQUZUICAgICAgICAg ICAgICAgRlRQIEFHTlQgQ29tbWFuZCAgICAgICAgICAgICAgIE9jdG9iZXIgMjAxMA0KDQogICAg IGhvc3QtcmVzcG9uc2UgPSBob3N0LW9rIC8gZXJyb3ItcmVzcG9uc2UNCiAgICAgaG9zdC1vayAg ICAgICA9ICIyMDAiIENSTEYNCg0KICAgQXMgd2l0aCBhbGwgRlRQIGNvbW1hbmRzLCB0aGUgIkFH TlQiIGNvbW1hbmQgd29yZCBpcyBjYXNlDQogICBpbmRlcGVuZGVudCwgYW5kIE1BWSBiZSBzcGVj aWZpZWQgaW4gYW55IGNoYXJhY3RlciBjYXNlIGRlc2lyZWQuDQoNCiAgIFRoZSAidXNlci1hZ2Vu dCIgKGdpdmVuIGFzIGEgcGFyYW1ldGVyIG9mIHRoZSAiYWdlbnQtY29tbWFuZCIpDQogICBzcGVj aWZpZXMgdGhlIGlkZW50aWZ5aW5nIGluZm9ybWF0aW9uIGZvciB0aGUgdXNlci1GVFAgcHJvY2Vz cy4NCiAgIA0KICAgVE9ETzogV2hhdCBhYm91dCBpbnRlcm5hdGlvbmFsaXphdGlvbiBvZiB1c2Vy IGFnZW50cz8NCg0KMy4yLiBBR05UIGNvbW1hbmQgc2VtYW50aWNzDQoNCiAgIFRoZSBBR05UIGNv bW1hbmQgaXMgdmFsaWQgYXQgYW55IHRpbWUgZHVyaW5nIGFuIEZUUCBzZXNzaW9uLCBhbHRob3Vn aA0KICAgaXQgd291bGQgbWFrZSBzZW5zZSBmb3IgdGhlIHVzZXItRlRQIHByb2Nlc3MgdG8gc2Vu ZCB0aGUgQUdOVCBjb21tYW5kDQogICBlYXJsaWVyIGluIHRoZSBzZXNzaW9uLg0KICAgDQogICBU T0RPOiBTaG91bGQgYSBzZXJ2ZXItUEkgYmUgYWxsb3dlZCB0byByZXF1aXJlIGEgc3VjY2Vzc2Z1 bCBsb2dpbg0KICAgYmVmb3JlIGFjY2VwdGluZyB0aGUgQUdOVCBjb21tYW5kPw0KDQogICBVcG9u IHJlY2VpdmluZyB0aGUgQUdOVCBjb21tYW5kLCB0aGUgRlRQIHNlcnZlci1QSSBTSE9VTEQgdmFs aWRhdGUNCiAgIHRoYXQgdGhlIHVzZXItYWdlbnQgZ2l2ZW4gaXMgc3ludGFjdGljYWxseSBjb3Jy ZWN0LCBhbmQsIGlmIGl0IGlzDQogICB2YWxpZCwgcmV0dXJuIHRoZSAiaG9zdC1vayIgcmVwbHkg dG8gdGhlIHVzZXItUEkuDQoNCiAgIFRoZSBmb2xsb3dpbmcgZXhhbXBsZSBpbGx1c3RyYXRlcyB3 aGF0IGEgdHlwaWNhbCBzZXF1ZW5jZSBtaWdodCBsb29rDQogICBsaWtlIHdoZW4gdGhlIEFHTlQg Y29tbWFuZCBpcyB1c2VkOg0KDQogICAgICAgIEM+IEFHTlQgRm9vQmFyLzEuMA0KICAgICAgICBT PiAyMDAgQ29tbWFuZCBva2F5Lg0KDQogICBUaGUgIjIwMCIgcmVwbHkgY29kZSBmb3IgdGhlIEFH TlQgY29tbWFuZCBpcyB0aGUgc3RhbmRhcmQgcmVwbHkgZm9yDQogICBhbiBGVFAgY29tbWFuZCB0 aGF0IHJlcXVpcmVzIG5vIGZ1cnRoZXIgcHJvY2Vzc2luZy4NCg0KICAgVE9ETzogU2hvdWxkIGEg c2VydmVyLVBJIGJlIGFsbG93ZWQgdG8gZGVueSBhIGNvbm5lY3Rpb24gYmFzZWQgb24NCiAgIGlu Zm9ybWF0aW9uIHRoYXQgaXMgcHJlc2VudGVkIGJ5IHRoZSBBR05UIGNvbW1hbmQ/IChGb3IgZXhh bXBsZSwNCiAgIGlmIGEgcGFydGljdWxhciB1c2VyLUZUUCBwcm9jZXNzIHZlcnNpb24gaXMgaW5z dWZmaWNpZW50IG9yIG5vdA0KICAgc3VwcG9ydGVkLikNCg0KMy4zLiBBR05UIGNvbW1hbmQgZXJy b3JzDQoNCiAgIFRoZSBzZXJ2ZXItUEkgU0hPVUxEIHJlcGx5IHdpdGggYSA1MDAgb3IgNTAyIHJl cGx5IGlmIHRoZSBBR05UDQogICBjb21tYW5kIGlzIHVucmVjb2duaXplZCBvciB1bmltcGxlbWVu dGVkLg0KICAgDQogICBBIDUwMSByZXBseSBTSE9VTEQgYmUgc2VudCBpZiB0aGUgdXNlci1hZ2Vu dCBnaXZlbiBpcyBzeW50YWN0aWNhbGx5DQogICBpbnZhbGlkLg0KDQogICBJbiBub25lIG9mIHRo ZXNlIGVycm9yIGNvbmRpdGlvbnMgc2hvdWxkIHRoZSBjb25uZWN0aW9uIGJlIGNsb3NlZC4NCg0K My40LiBGRUFUIHJlc3BvbnNlIGZvciBBR05UIGNvbW1hbmQNCg0KICAgV2hpbGUgdGhlIEFHTlQg Y29tbWFuZCBpcyBwcmltYXJpbHkgdXNlZCBmb3IgdGhlIHVzZXItRlRQIHByb2Nlc3MgdG8NCg0K TWNNdXJyYXkgICAgICAgICAgICAgICAgIEV4cGlyZXMgQXByaWwgMTMsIDIwMTEgICAgICAgICAg ICAgICAgIFtQYWdlIDVdDQoMDQpJTlRFUk5FVC1EUkFGVCAgICAgICAgICAgICAgIEZUUCBBR05U IENvbW1hbmQgICAgICAgICAgICAgICBPY3RvYmVyIDIwMTANCg0KICAgaWRlbnRpZnkgaXRzZWxm LCBhIHNlcnZlci1GVFAgcHJvY2VzcyB0aGF0IHN1cHBvcnRzIHRoZSBBR05UIGNvbW1hbmQNCiAg IFNIT1VMRCBpbmNsdWRlIGEgbGluZSBjb250YWluaW5nIHRoZSBzaW5nbGUgd29yZCAiQUdOVCIg d2hlbiByZXBseWluZw0KICAgdG8gdGhlIEZFQVQgY29tbWFuZCBbUkZDMjM4OV0gdG8gaW5kaWNh dGUgdGhhdCB0aGUgQUdOVCBjb21tYW5kIGlzDQogICBzdXBwb3J0ZWQuICBUaGlzIHdvcmQgaXMg Y2FzZSBpbnNlbnNpdGl2ZSwgYW5kIE1BWSBiZSBzZW50IGluIGFueQ0KICAgbWl4dHVyZSBvZiB1 cHBlciBvciBsb3dlciBjYXNlLCBob3dldmVyIGl0IFNIT1VMRCBiZSBzZW50IGluIHVwcGVyDQog ICBjYXNlLiAgVGhhdCBpcywgdGhlIHJlc3BvbnNlIFNIT1VMRCBiZToNCg0KICAgICAgICBDPiBG RUFUDQogICAgICAgIFM+IDIxMS0gPGFueSBkZXNjcmlwdGl2ZSB0ZXh0Pg0KICAgICAgICBTPiAg Li4uDQogICAgICAgIFM+ICBBR05UDQogICAgICAgIFM+ICAuLi4NCiAgICAgICAgUz4gMjExIEVu ZA0KDQogICBUaGUgZWxsaXBzZXMgaW5kaWNhdGUgcGxhY2UgaG9sZGVycyB3aGVyZSBvdGhlciBm ZWF0dXJlcyBtYXkgYmUNCiAgIGluY2x1ZGVkLCBhbmQgYXJlIG5vdCByZXF1aXJlZC4gIFRoZSBv bmUtc3BhY2UgaW5kZW50YXRpb24gb2YgdGhlDQogICBmZWF0dXJlIGxpbmVzIGlzIG1hbmRhdG9y eSBbUkZDMjM4OV0uDQoNCjQuIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zDQoNCiAgIEFuIEZUUCB1 c2VyLVBJIG1heSBzZW5kIGFuIGluY29ycmVjdCBvciBmYWxzZSBwYXJhbWV0ZXIgZm9yIHRoZSBB R05UDQogICBjb21tYW5kOyBIVFRQIHN1ZmZlcnMgZnJvbSB0aGlzIHNhbWUgaXNzdWUsIGFuZCBp biBtb3N0IHNpdHVhdGlvbnMNCiAgIHRoZSB1c2VyLWFnZW50IGluZm9ybWF0aW9uIHdpbGwgb25s eSBiZSB1c2VkIGZvciBnYXRoZXJpbmcgdXNhZ2UNCiAgIHN0YXRpc3RpY3Mgc28gYW4gaW5jb3Jy ZWN0IG9yIGZhbHNlIHBhcmFtZXRlciBmb3IgdGhlIEFHTlQgY29tbWFuZA0KICAgc2hvdWxkIG5v dCBwcmVzZW50IGEgcHJvYmxlbS4gIEhvd2V2ZXIsIGFuIEZUUCBzZXJ2ZXItUEkgaW1wbGVtZW50 ZXINCiAgIHdpbGwgbmVlZCB0byBiZSBhd2FyZSB0aGF0IHRoaXMgaXMgYSBwb3NzaWJpbHR5IHdo ZW4gY2hvb3Npbmcgd2hldGhlcg0KICAgdG8gZG8gYW55dGhpbmcgbWVhbmluZ2Z1bCB3aXRoIHRo ZSBpbmZvcm1hdGlvbiB0aGF0IGlzIHByZXNlbnRlZCBieQ0KICAgYW4gRlRQIHVzZXItUEkgdGhy b3VnaCB0aGUgQUdOVCBjb21tYW5kLg0KDQogICBBIGdlbmVyYWwgZGlzY3Vzc2lvbiBvZiBpc3N1 ZXMgcmVsYXRlZCB0byB0aGUgc2VjdXJpdHkgb2YgRlRQIGNhbiBiZQ0KICAgZm91bmQgaW4gW1JG QzI1NzddLg0KDQo1LiBJQU5BIENvbnNpZGVyYXRpb25zDQoNCiAgIElBTkEgaXMgcmVxdWVzdGVk IHRvIHJlZ2lzdGVyIHRoZSBmb2xsb3dpbmcgRlRQIGV4dGVuc2lvbiBhY2NvcmRpbmcNCiAgIHRv IHRoZSBwcm9jZWR1cmUgZXN0YWJsaXNoZWQgYnkgW1JGQzU3OTddOg0KDQogICArLS0tLS0tLSst LS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0rLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0t LSsNCiAgIHwgY21kICAgfCBGRUFUIHwgZGVzY3JpcHRpb24gICAgICAgfCB0eXBlIHwgY29uZiB8 IFJGQyNzL1JlZmVyZW5jZXMgfA0KICAgfCAgICAgICB8IENvZGUgfCAgICAgICAgICAgICAgICAg ICB8ICAgICAgfCAgICAgIHwgYW5kIE5vdGVzICAgICAgICB8DQogICArLS0tLS0tLSstLS0tLS0r LS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0rLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLSsNCiAg IHwgQUdOVCAgfCBBR05UIHwgVXNlci1GVFAgUHJvY2VzcyAgfCBhICAgIHwgbyAgICB8IFsjMV0g ICAgICAgICAgICAgfA0KICAgfCAgICAgICB8ICAgICAgfCBEZXNjcmlwdGlvbiAgICAgICB8ICAg ICAgfCAgICAgIHwgICAgICAgICAgICAgICAgICB8DQogICArLS0tLS0tLSstLS0tLS0rLS0tLS0t LS0tLS0tLS0tLS0tLSstLS0tLS0rLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLSsNCg0KICAgW1sg UkZDIEVkaXRvcjogUGxlYXNlIHVwZGF0ZSBub3RlICMxIGluIHRoZSBhYm92ZSB0YWJsZSB3aXRo IHRoZQ0KICAgbnVtYmVyIG9mIHRoaXMgZG9jdW1lbnQuIF1dDQoNCjYuIFJlZmVyZW5jZXMNCg0K Ni4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMNCg0KTWNNdXJyYXkgICAgICAgICAgICAgICAgIEV4 cGlyZXMgQXByaWwgMTMsIDIwMTEgICAgICAgICAgICAgICAgIFtQYWdlIDZdDQoMDQpJTlRFUk5F VC1EUkFGVCAgICAgICAgICAgICAgIEZUUCBBR05UIENvbW1hbmQgICAgICAgICAgICAgICBPY3Rv YmVyIDIwMTANCg0KDQogICBbUkZDOTU5XSAgUG9zdGVsLCBKLiwgUmV5bm9sZHMsIEouLCAiRmls ZSBUcmFuc2ZlciBQcm90b2NvbCAoRlRQKSIsDQogICAgICAgICAgICAgU1REIDksIFJGQyA5NTks IE9jdG9iZXIgMTk4NQ0KDQogICBbUkZDMjExOV0gQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9y IHVzZSBpbiBSRkNzIHRvIEluZGljYXRlDQogICAgICAgICAgICAgUmVxdWlyZW1lbnQgTGV2ZWxz IiwgQkNQIDE0LCBSRkMgMjExOSwgTWFyY2ggMTk5Nw0KDQogICBbUkZDMjM4OV0gSGV0aG1vbiwg UC4sIEVseiwgUi4sICJGZWF0dXJlIG5lZ290aWF0aW9uIG1lY2hhbmlzbSBmb3INCiAgICAgICAg ICAgICB0aGUgRmlsZSBUcmFuc2ZlciBQcm90b2NvbCIsIFJGQyAyMzg5LCBBdWd1c3QgMTk5OA0K DQogICBbUkZDMjY0MF0gQ3VydGluLCBXLiwgIkludGVybmF0aW9uYWxpemF0aW9uIG9mIHRoZSBG aWxlIFRyYW5zZmVyDQogICAgICAgICAgICAgUHJvdG9jb2wiLCBSRkMgMjY0MCwgSnVseSAxOTk5 DQoNCiAgIFtSRkM1MjM0XSBDcm9ja2VyLCBELiwgT3ZlcmVsbCwgUC4sICJBdWdtZW50ZWQgQk5G IGZvciBTeW50YXgNCiAgICAgICAgICAgICBTcGVjaWZpY2F0aW9uczogQUJORiIsIFJGQyA1MjM0 LCBKYW51YXJ5IDIwMDgNCg0KNi4yLiAgSW5mb3JtYXRpdmUgUmVmZXJlbmNlcw0KDQogICBbUkZD MTk0NV0gQmVybmVycy1MZWUsIFQuLCBGaWVsZGluZywgUi4sIEZyeXN0eWssIEguLCAiSHlwZXJ0 ZXh0DQogICAgICAgICAgICAgVHJhbnNmZXIgUHJvdG9jb2wgLS0gSFRUUC8xLjAiLCBSRkMgMTk0 NSwgTWF5IDE5OTYNCg0KICAgW1JGQzI1NzddIEFsbG1hbiwgTS4sIE9zdGVybWFubiwgUy4sICJG VFAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMiLA0KICAgICAgICAgICAgIFJGQyAyNTc3LCBNYXkg MTk5OQ0KDQogICBbUkZDMjYxNl0gRmllbGRpbmcsIFIuLCBHZXR0eXMsIEouLCBNb2d1bCwgSi4s IEZyeXN0eWssIEguLA0KICAgICAgICAgICAgIE1hc2ludGVyLCBMLiwgTGVhY2gsIFAuLCBCZXJu ZXJzLUxlZSwgVC4sICJIeXBlcnRleHQNCiAgICAgICAgICAgICBUcmFuc2ZlciBQcm90b2NvbCAt LSBIVFRQLzEuMSIsIFJGQyAyNjE2LCBKdW5lIDE5OTkNCg0KICAgW1JGQzU3OTddIEtsZW5zaW4s IEouLCBIb2VuZXMsIEEuLCAiRlRQIENvbW1hbmQgYW5kIEV4dGVuc2lvbg0KICAgICAgICAgICAg IFJlZ2lzdHJ5IiwgTWFyY2ggMjAxMA0KDQpBY2tub3dsZWRnbWVudHMNCg0KICAgTi9BIGZvciBu b3cuDQoNCkF1dGhvcidzIEFkZHJlc3MNCg0KICAgUm9iZXJ0IE1jTXVycmF5DQogICBNaWNyb3Nv ZnQgQ29ycG9yYXRpb24NCiAgIE9uZSBNaWNyb3NvZnQgV2F5DQogICBSZWRtb25kLCBXQSA5ODA1 Mi02Mzk5DQoNCiAgIEVtYWlsOiByb2JtY21AbWljcm9zb2Z0LmNvbQ0KDQoNCg0KDQoNCg0KDQoN Cg0KTWNNdXJyYXkgICAgICAgICAgICAgICAgIEV4cGlyZXMgQXByaWwgMTMsIDIwMTEgICAgICAg ICAgICAgICAgIFtQYWdlIDddDQoMDQo= --_002_A5FC996C3C37DC4DA5076F1046B5674C431FD205TK5EX14MBXC127r_-- From wmaton@ottix.net Sun Oct 17 07:16:52 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB7153A6A9E for ; Sun, 17 Oct 2010 07:16:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.553 X-Spam-Level: X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2kBOfLteglx for ; Sun, 17 Oct 2010 07:16:50 -0700 (PDT) Received: from iskra.ottix.net (iskra.ottix.net [IPv6:2001:410:90ff::2]) by core3.amsl.com (Postfix) with ESMTP id 13D0B3A6A5E for ; Sun, 17 Oct 2010 07:16:48 -0700 (PDT) Received: from iskra.ottix.net (localhost [127.0.0.1]) by iskra.ottix.net (8.14.4/8.14.4) with ESMTP id o9HEI445004146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Oct 2010 10:18:04 -0400 X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 iskra.ottix.net o9HEI445004146 Received: from localhost (wmaton@localhost) by iskra.ottix.net (8.14.4/8.14.3/Submit) with ESMTP id o9HEI3Qc004140; Sun, 17 Oct 2010 10:18:04 -0400 Date: Sun, 17 Oct 2010 10:18:03 -0400 (EDT) From: "William F. Maton" To: Robert McMurray In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "ftpext@ietf.org" Subject: Re: [ftpext] Submitting new drafts X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2010 14:16:53 -0000 Punt it into ftpext2 please, otherwise there's not much point to having one. On Sat, 16 Oct 2010, Robert McMurray wrote: > I'd like to submit a new draft (see attached) that is unrelated to my other draft - should we be using FTPEXT2 as the WG? Or should continue to submit as individual drafts to the Applications Area? > > Robert McMurray > Office Content Publishing (UA) > Email: robmcm@microsoft.com > wfms From anthonybryan@gmail.com Sun Oct 17 23:18:16 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82D233A6A63 for ; Sun, 17 Oct 2010 23:18:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.323 X-Spam-Level: X-Spam-Status: No, score=-2.323 tagged_above=-999 required=5 tests=[AWL=0.276, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y5aXcHPYfG2v for ; Sun, 17 Oct 2010 23:18:14 -0700 (PDT) Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 5F5EE3A683F for ; Sun, 17 Oct 2010 23:18:14 -0700 (PDT) Received: by iwn10 with SMTP id 10so859242iwn.31 for ; Sun, 17 Oct 2010 23:19:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=gtwyBYc7DulNwM+D+dvFaezh3OLZoP3L0XgHt01DfNw=; b=h8R7vdGAGCmBejFQ9wSEuHuUQon6vCdZ4ieqJTJjaMIv+JOyJOm9hfagmGoq4bkucl KGVVGlM5SU4FHJBVCKDd4M9WbemjSVybXFNBL5vvHkCZOIT5jDGeNvefH9vVFgURVsS7 TagBqIHPWrTTCimiqA243z+bGe3/pdmkL+MV8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qEi3xYr4q8dOaUNpEUwDzeKcTtoDf9WaLzPemqOzPhMZpv8qUaBGQHmneM5uyGv5DF pokWLtCfHhkrzYgSx4dEHFozx4WVm8bMEpmlfVqcnxIkOi5DRHnpOqTFltN6eqR87Jpk hr5M33Pk7HXpL/RyOEeCIn128n2tgfeJd8cpI= MIME-Version: 1.0 Received: by 10.231.192.80 with SMTP id dp16mr2905704ibb.39.1287382781425; Sun, 17 Oct 2010 23:19:41 -0700 (PDT) Received: by 10.231.12.72 with HTTP; Sun, 17 Oct 2010 23:19:41 -0700 (PDT) In-Reply-To: References: Date: Mon, 18 Oct 2010 02:19:41 -0400 Message-ID: From: Anthony Bryan To: "William F. Maton" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "ftpext@ietf.org" , Robert McMurray Subject: Re: [ftpext] Submitting new drafts X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2010 06:18:16 -0000 I think the problem is that there isn't a FTPEXT WG yet & it doesn't seem definite that there will be one. I've been posting a draft charter (included here) but...not sure what the next step is. I added draft-liu-ftp64-extension, which I just saw turn up. somewhat on topic, does anyone know how to change the WG in xml2rfc? FTP Extensions, 2nd edition (ftpext2) Charter Chair(s): TBD IETF Area: Applications Area Applications Area Directors: Alexey Melnikov Peter Saint-Andre Responsible Area Director: Alexey Melnikov Mailing list: General Discussion: ftpext@ietf.org Archive: http://www.ietf.org/mail-archive/web/ftpext/current/maillist.= html Description of Working Group: The Standard File Transfer Protocol specification in RFC 959 has been updated several times with command extensions of one sort or another, including those based on the extension mechanism of RFC 2389 (a complete list appears in RFC 5797 and the corresponding IANA registry at http://www.iana.org/assignments/ftp-commands-extensions/ftp-commands-extens= ions.xhtml ). The following are active FTP related drafts: draft-bryan-ftp-hash draft-hethmon-mcmurray-ftp-hosts draft-liu-ftp64-extension draft-peterson-streamlined-ftp-command-extensions draft-preston-ftpext-deflate The Working Group will: * Review and finalize drafts listed above. * Continue work on other drafts that are already in progress. * Review and confirm or reject errata of current FTP RFCs. * Investigate the differences between FTP in theory (current RFCs) and practice, and recommend future work to align them. The Working Group's specification deliverables are: * A document that specifies the HOST command (Proposed Standard). * A document that specifies the HASH command (Proposed Standard). * A document that specifies FTP extensions to support IPv4/IPv6 translation scenario. The Working Group must not introduce a new version of FTP, e.g. an incompatible FTP 2.0. Goals and Milestones Oct 2010 Submit 'File Transfer Protocol HOST Command for Virtual Hosts' as working group item (draft-hethmon-mcmurray-ftp-hosts will be used as a starting point) Oct 2010 Submit 'File Transfer Protocol HASH Command for Cryptographic Hashes' as working group item (draft-bryan-ftp-hash will be used as a starting point) TBD 2010 Working group Last Call of HOST document TBD 2010 Submit 'File Transfer Protocol HOST Command for Virtual Hosts' to the IESG for consideration as a Proposed Standard TBD 2011 Working group Last Call of HASH document TBD 2011 Submit 'File Transfer Protocol HASH Command for Cryptographic Hashes' to the IESG for consideration as a Proposed Standard TBD 2011 Close or recharter On Sun, Oct 17, 2010 at 10:18 AM, William F. Maton wrote= : > > Punt it into ftpext2 please, otherwise there's not much point to having o= ne. > > On Sat, 16 Oct 2010, Robert McMurray wrote: > >> I'd like to submit a new draft (see attached) that is unrelated to my >> other draft - should we be using FTPEXT2 as the WG? Or should continue t= o >> submit as individual drafts to the Applications Area? --=20 (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] =A0 )) Easier, More Reliable, Self Healing Downloads From robmcm@microsoft.com Mon Oct 18 11:05:34 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72E3D3A6BA1 for ; Mon, 18 Oct 2010 11:05:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o41R8KU3CLo7 for ; Mon, 18 Oct 2010 11:05:33 -0700 (PDT) Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 71F3F3A6B97 for ; Mon, 18 Oct 2010 11:05:33 -0700 (PDT) Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 18 Oct 2010 11:06:55 -0700 Received: from TK5EX14MBXC127.redmond.corp.microsoft.com ([169.254.6.93]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.01.0218.012; Mon, 18 Oct 2010 11:06:46 -0700 From: Robert McMurray To: 'Anthony Bryan' , "'William F. Maton'" Thread-Topic: [ftpext] Submitting new drafts Thread-Index: Acts12dO7mju2PbkRH6PeH4GsapAbgBaWEiAACGVrIAACbSPAA== Date: Mon, 18 Oct 2010 18:06:45 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [157.54.51.72] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "'ftpext@ietf.org'" Subject: Re: [ftpext] Submitting new drafts X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2010 18:05:34 -0000 Thanks, Anthony. The lack of an FTPEXT WG is the problem that I was referring to - I'd like = to add the proposed draft that I sent out last week to the proposed FTPEXT = WG's charter, but since it isn't a formal WG yet then I wasn't sure how bes= t to proceed. (e.g. Should I submit the draft to the applications area for = now just to start the peer review process while awaiting the next phase of = the FTPEXT WG process? ) Thanks again. -----Original Message----- From: Anthony Bryan [mailto:anthonybryan@gmail.com]=20 Sent: Sunday, October 17, 2010 11:20 PM To: William F. Maton Cc: Robert McMurray; ftpext@ietf.org Subject: Re: [ftpext] Submitting new drafts I think the problem is that there isn't a FTPEXT WG yet & it doesn't seem d= efinite that there will be one. I've been posting a draft charter (included here) but...not sure what the n= ext step is. I added draft-liu-ftp64-extension, which I just saw turn up. somewhat on topic, does anyone know how to change the WG in xml2rfc? On Sun, Oct 17, 2010 at 10:18 AM, William F. Maton wrote= : > > Punt it into ftpext2 please, otherwise there's not much point to having o= ne. > > On Sat, 16 Oct 2010, Robert McMurray wrote: > >> I'd like to submit a new draft (see attached) that is unrelated to my=20 >> other draft - should we be using FTPEXT2 as the WG? Or should=20 >> continue to submit as individual drafts to the Applications Area? From anthonybryan@gmail.com Mon Oct 18 13:18:50 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD8B93A6E71 for ; Mon, 18 Oct 2010 13:18:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.331 X-Spam-Level: X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[AWL=0.268, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i1lpyjSmjR3X for ; Mon, 18 Oct 2010 13:18:43 -0700 (PDT) Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 1306F3A6B02 for ; Mon, 18 Oct 2010 13:18:42 -0700 (PDT) Received: by ewy6 with SMTP id 6so1032947ewy.31 for ; Mon, 18 Oct 2010 13:20:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=pNB1jDgkDrNrzVp2bGESRaQHoUz5+NRu03VgHZsgz2E=; b=HpXpoEyMnnxHKiTe2qVc9PCNRDlLmzK7qtLTC8KZ+m0/TiFujBi4Od041LHPznJ/XH AnIzdx4kvQcyBOd7gYugVxsAQbHbaYNzZPsgW/RPDM/6UtuWETo+gh4ss5RCNiPrpfcq ev5NoLja9YVQ5GRO863fyLMVxRynBnLbTEOU0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=IiKQ2i1Uu8t1QmcDGq1gRLJBL1HUHWhobeixigblMai3qa2ABkx5fZTuVijkTV1h/n V1ZEdb+fDXA48ZCdTFFd3k4OohBBqrlrxWMPa6RfrQh1BgvFg+CYHtOXGbfWqjWlomRl tlJu90bdSHQxWUmi8ziWoNPuzmJEqPXsEYv4Q= MIME-Version: 1.0 Received: by 10.213.106.20 with SMTP id v20mr3868974ebo.40.1287433211444; Mon, 18 Oct 2010 13:20:11 -0700 (PDT) Received: by 10.213.4.148 with HTTP; Mon, 18 Oct 2010 13:20:11 -0700 (PDT) In-Reply-To: References: Date: Mon, 18 Oct 2010 16:20:11 -0400 Message-ID: From: Anthony Bryan To: Robert McMurray Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "ftpext@ietf.org" Subject: Re: [ftpext] Submitting new drafts X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2010 20:18:52 -0000 I would say submit it now (you only have a few hours left) under Apps, or you won't have it for discussion at the IETF meeting or be able to submit it until November 8. I'll add it to the draft charter once I see it's submitted. btw, (this is to everyone) any comments on how to improve the draft charter= ? "The pre-meeting cutoff date for new documents (i.e., version -00 Internet-Drafts) is 2010-10-18 at 5 PM (PT). You will not be able to submit a new document after this time until 2010-11-08, at midnight" also, I think there is some overlap between AGNT from your draft & CSID from http://tools.ietf.org/html/draft-peterson-streamlined-ftp-command= -extensions On Mon, Oct 18, 2010 at 2:06 PM, Robert McMurray wro= te: > Thanks, Anthony. > > The lack of an FTPEXT WG is the problem that I was referring to - I'd lik= e to add the proposed draft that I sent out last week to the proposed FTPEX= T WG's charter, but since it isn't a formal WG yet then I wasn't sure how b= est to proceed. (e.g. Should I submit the draft to the applications area fo= r now just to start the peer review process while awaiting the next phase o= f the FTPEXT WG process? ) > > Thanks again. > > -----Original Message----- > From: Anthony Bryan [mailto:anthonybryan@gmail.com] > Sent: Sunday, October 17, 2010 11:20 PM > To: William F. Maton > Cc: Robert McMurray; ftpext@ietf.org > Subject: Re: [ftpext] Submitting new drafts > > I think the problem is that there isn't a FTPEXT WG yet & it doesn't seem= definite that there will be one. > > I've been posting a draft charter (included here) but...not sure what the= next step is. > > I added draft-liu-ftp64-extension, which I just saw turn up. > > somewhat on topic, does anyone know how to change the WG in xml2rfc? > > On Sun, Oct 17, 2010 at 10:18 AM, William F. Maton wro= te: >> >> Punt it into ftpext2 please, otherwise there's not much point to having = one. >> >> On Sat, 16 Oct 2010, Robert McMurray wrote: >> >>> I'd like to submit a new draft (see attached) that is unrelated to my >>> other draft - should we be using FTPEXT2 as the WG? Or should >>> continue to submit as individual drafts to the Applications Area? > > --=20 (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] =A0 )) Easier, More Reliable, Self Healing Downloads From robmcm@microsoft.com Mon Oct 18 15:56:08 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A217A3A6C22 for ; Mon, 18 Oct 2010 15:56:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bsVyfn-t9TO0 for ; Mon, 18 Oct 2010 15:56:07 -0700 (PDT) Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 887753A6BC4 for ; Mon, 18 Oct 2010 15:56:07 -0700 (PDT) Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 18 Oct 2010 15:57:31 -0700 Received: from TK5EX14MBXC125.redmond.corp.microsoft.com ([169.254.5.159]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.01.0218.012; Mon, 18 Oct 2010 15:57:31 -0700 From: Robert McMurray To: 'Anthony Bryan' , "'mark.peterson@rhinosoft.com'" Thread-Topic: [ftpext] Submitting new drafts Thread-Index: Acts12dO7mju2PbkRH6PeH4GsapAbgBaWEiAACGVrIAACbSPAAATphmAAAq22KA= Date: Mon, 18 Oct 2010 22:57:28 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [157.54.51.72] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "ftpext@ietf.org" Subject: Re: [ftpext] Submitting new drafts X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2010 22:56:08 -0000 Anthony - great catch! Mark - I sincerely apologize, I had not seen the CSID addition to draft-pet= erson-streamlined-ftp-command-extensions; I had only seen earlier drafts be= fore that was added. You are welcome to scavenge anything that you might fi= nd useful from the AGNT draft that I sent out last week to ftpext@ietf.org.= ;-] -----Original Message----- From: Anthony Bryan [mailto:anthonybryan@gmail.com]=20 Sent: Monday, October 18, 2010 1:20 PM To: Robert McMurray Cc: William F. Maton; ftpext@ietf.org Subject: Re: [ftpext] Submitting new drafts I would say submit it now (you only have a few hours left) under Apps, or you won't have it for discussion at the IETF meeting or be able to submit it until November 8. I'll add it to the draft charter once I see it's submitted. btw, (this is to everyone) any comments on how to improve the draft charter= ? "The pre-meeting cutoff date for new documents (i.e., version -00 Internet-Drafts) is 2010-10-18 at 5 PM (PT). You will not be able to submit a new document after this time until 2010-11-08, at midnight" also, I think there is some overlap between AGNT from your draft & CSID from http://tools.ietf.org/html/draft-peterson-streamlined-ftp-command= -extensions On Mon, Oct 18, 2010 at 2:06 PM, Robert McMurray wro= te: > Thanks, Anthony. > > The lack of an FTPEXT WG is the problem that I was referring to - I'd lik= e to add the proposed draft that I sent out last week to the proposed FTPEX= T WG's charter, but since it isn't a formal WG yet then I wasn't sure how b= est to proceed. (e.g. Should I submit the draft to the applications area fo= r now just to start the peer review process while awaiting the next phase o= f the FTPEXT WG process? ) > > Thanks again. From alexey.melnikov@isode.com Tue Oct 19 00:05:12 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF0583A6C0F for ; Tue, 19 Oct 2010 00:05:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kXynTSA4W6rL for ; Tue, 19 Oct 2010 00:05:08 -0700 (PDT) Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 81AA23A6A3F for ; Tue, 19 Oct 2010 00:05:08 -0700 (PDT) Received: from [192.168.20.2] ((unknown) [212.183.140.17]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Tue, 19 Oct 2010 08:06:34 +0100 X-SMTP-Protocol-Errors: NORDNS Message-ID: <4CBD4371.7040202@isode.com> Date: Tue, 19 Oct 2010 08:06:25 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Anthony Bryan References: <4C8743B4.4030101@isode.com> <4C8F5A42.5000601@isode.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ftpext@ietf.org, John C Klensin , Peter Saint-Andre Subject: Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 07:05:12 -0000 Anthony Bryan wrote: >On Tue, Sep 14, 2010 at 7:19 AM, Alexey Melnikov > wrote: > > >>Anthony Bryan wrote: >> >> >>>On Sun, Sep 12, 2010 at 11:30 PM, liu dapeng wrote: >>> >>> >>>>Hi Anthony, >>>> >>>>For the draft: draft-ietf-behave-ftp64, during last IETF meeting, >>>>people are agreed to split the draft to two separate ones, ALG related >>>>wrok goes to Behave WG, FTP protocol related work goes to FTPEXT. >>>>Shall we include this work item to the charter? >>>> >>>>Following text for your refernece: >>>>Deliverables: FTP extensions to support IPv4/IPv6 transiation scenario. >>>> >>>hi, >>> >>>thanks for the info. should I remove draft-ietf-behave-ftp64 from the >>>list? >>> >>I think listing a draft from another WG is confusing, so I would say yes. >> >>But note that it is Ok to have a Charter listing deliverables for which >>there is no draft. >> >thanks, good to know. > > Hi, Sorry for slow response, I am just back from holidays. >should I also add something like "Review other drafts which may touch >on FTP in some way" (like draft-ietf-tcpm-urgent-data-06), or is that >pretty much implied? > This is implied. The WG will get such requests informally anyway. >does anyone else have any comments? deliverables/goals? > Looking at the original BOF request, I am wondering what should happen to the following: draft-hoffman-ftp-uri-04 - The ftp URI Scheme draft-klensin-ftp-typeu-00 - FTP Extension for Internationalized Text In particular, I would like this WG to revise the FTP URI spec, but I understand that there might be no interest in doing that. >FTP Extensions, 2nd edition (ftpext2) Charter > >Chair(s): > ? > >IETF Area: > Applications Area > >Applications Area Directors: > Alexey Melnikov > Peter Saint-Andre > >Responsible Area Director: > Alexey Melnikov > >Mailing list: > General Discussion: ftpext@ietf.org > Archive: http://www.ietf.org/mail-archive/web/ftpext/current/maillist.html > >Description of Working Group: > >The Standard File Transfer Protocol specification in RFC 959 >has been updated several times with command extensions of one >sort or another, including those based on the extension >mechanism of RFC 2389 (a complete list appears in RFC 5797 and >the corresponding IANA registry at >http://www.iana.org/assignments/ftp-commands-extensions/ftp-commands-extensions.xhtml >). > >The following are active FTP related drafts: > > draft-bryan-ftp-hash > draft-hethmon-mcmurray-ftp-hosts > draft-peterson-streamlined-ftp-command-extensions > draft-preston-ftpext-deflate > FTP extensions to support IPv4/IPv6 translation scenario > >The Working Group will: >* Review and finalize drafts listed above. >* Continue work on other drafts that are already in progress. >* Review and confirm or reject errata of current FTP RFCs. >* Investigate the differences between FTP in theory > (current RFCs) and practice, and recommend future work to align them. > >The Working Group's specification deliverables are: >* A document that specifies the HOST command (Proposed Standard). >* A document that specifies the HASH command (Proposed Standard). >* A document that specifies FTP extensions to support IPv4/IPv6 >translation scenario. > >The Working Group must not introduce a new version of FTP, e.g. >an incompatible FTP 2.0. > >Goals and Milestones >Oct 2010 Submit 'File Transfer Protocol HOST Command for Virtual >Hosts' as working group item (draft-hethmon-mcmurray-ftp-hosts will be >used as a starting point) >Oct 2010 Submit 'File Transfer Protocol HASH Command for >Cryptographic Hashes' as working group item (draft-bryan-ftp-hash will >be used as a starting point) >??? 2010 Working group Last Call of HOST document >??? 2010 Submit 'File Transfer Protocol HOST Command for Virtual >Hosts' to the IESG for consideration as a Proposed Standard >??? 2011 Working group Last Call of HASH document >??? 2011 Submit 'File Transfer Protocol HASH Command for >Cryptographic Hashes' to the IESG for consideration as a Proposed >Standard >??? 2011 Close or recharter > > Best Regards, Alexey -- IETF Application Area Director, Internet Messaging Team Lead, JID: same as my email address From maxpassion@gmail.com Tue Oct 19 01:25:20 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B6B63A6BAE for ; Tue, 19 Oct 2010 01:25:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.47 X-Spam-Level: X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zqFY-zxRguHM for ; Tue, 19 Oct 2010 01:25:18 -0700 (PDT) Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id B35CC3A6A96 for ; Tue, 19 Oct 2010 01:25:18 -0700 (PDT) Received: by iwn10 with SMTP id 10so2481582iwn.31 for ; Tue, 19 Oct 2010 01:26:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=pys1x3uIhWYzYvXxQds2AqRvQLvj+HvtDUGCFnqdtk8=; b=CqzraNtGX1Y9rNHt6wxk6HAG+Zq2SI2HV42peniVVhSqayQyGx94sC3N9sIhmeQngV ALq8Y/UGrhpoo+8uKF98Rdde3svG/OlBnx8LV1VavDfFzRlymvBoNUS1PD+o6VvNvBot mC45PWTTd/UjuSzrxOBibo+xIOhd3v7/TPCJQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=KXELqn6sznwaqrYlNfIrYthhbMlDnID7aDQIrEd6FUnOObIJpZaLqTiOsS+c1LhWeP cDDhAPbLRb8FlwdtSDLzoDXeOYjfkvqGiZ9qrCeghxtN3amg9uUDnNamTk0WK39fdiVc kTuN78rhpQ2oBIVCH5UnoyZOGmoPU4vbBYMQs= MIME-Version: 1.0 Received: by 10.231.20.2 with SMTP id d2mr325333ibb.135.1287476808458; Tue, 19 Oct 2010 01:26:48 -0700 (PDT) Received: by 10.220.10.211 with HTTP; Tue, 19 Oct 2010 01:26:48 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 Oct 2010 16:26:48 +0800 Message-ID: From: liu dapeng To: Anthony Bryan Content-Type: text/plain; charset=ISO-8859-1 Cc: Robert McMurray , "ftpext@ietf.org" Subject: Re: [ftpext] Submitting new drafts X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 08:25:20 -0000 2010/10/18, Anthony Bryan : > I think the problem is that there isn't a FTPEXT WG yet & it doesn't > seem definite that there will be one. > > I've been posting a draft charter (included here) but...not sure what > the next step is. > > I added draft-liu-ftp64-extension, which I just saw turn up. Thanks, Anthony, this is the split draft from draft-behave-ftp64 based on our discussion in Maastricht. Best Regards, Dapeng Liu > somewhat on topic, does anyone know how to change the WG in xml2rfc? > > > > FTP Extensions, 2nd edition (ftpext2) Charter > > Chair(s): > TBD > > IETF Area: > Applications Area > > Applications Area Directors: > Alexey Melnikov > Peter Saint-Andre > > Responsible Area Director: > Alexey Melnikov > > Mailing list: > General Discussion: ftpext@ietf.org > Archive: > http://www.ietf.org/mail-archive/web/ftpext/current/maillist.html > > Description of Working Group: > > The Standard File Transfer Protocol specification in RFC 959 > has been updated several times with command extensions of one > sort or another, including those based on the extension > mechanism of RFC 2389 (a complete list appears in RFC 5797 and > the corresponding IANA registry at > http://www.iana.org/assignments/ftp-commands-extensions/ftp-commands-extensions.xhtml > ). > > The following are active FTP related drafts: > > draft-bryan-ftp-hash > draft-hethmon-mcmurray-ftp-hosts > draft-liu-ftp64-extension > draft-peterson-streamlined-ftp-command-extensions > draft-preston-ftpext-deflate > > The Working Group will: > * Review and finalize drafts listed above. > * Continue work on other drafts that are already in progress. > * Review and confirm or reject errata of current FTP RFCs. > * Investigate the differences between FTP in theory > (current RFCs) and practice, and recommend future work to align them. > > The Working Group's specification deliverables are: > * A document that specifies the HOST command (Proposed Standard). > * A document that specifies the HASH command (Proposed Standard). > * A document that specifies FTP extensions to support IPv4/IPv6 > translation scenario. > > The Working Group must not introduce a new version of FTP, e.g. > an incompatible FTP 2.0. > > Goals and Milestones > Oct 2010 Submit 'File Transfer Protocol HOST Command for Virtual > Hosts' as working group item (draft-hethmon-mcmurray-ftp-hosts will be > used as a starting point) > Oct 2010 Submit 'File Transfer Protocol HASH Command for > Cryptographic Hashes' as working group item (draft-bryan-ftp-hash will > be used as a starting point) > TBD 2010 Working group Last Call of HOST document > TBD 2010 Submit 'File Transfer Protocol HOST Command for Virtual > Hosts' to the IESG for consideration as a Proposed Standard > TBD 2011 Working group Last Call of HASH document > TBD 2011 Submit 'File Transfer Protocol HASH Command for > Cryptographic Hashes' to the IESG for consideration as a Proposed > Standard > TBD 2011 Close or recharter > > On Sun, Oct 17, 2010 at 10:18 AM, William F. Maton wrote: >> >> Punt it into ftpext2 please, otherwise there's not much point to having >> one. >> >> On Sat, 16 Oct 2010, Robert McMurray wrote: >> >>> I'd like to submit a new draft (see attached) that is unrelated to my >>> other draft - should we be using FTPEXT2 as the WG? Or should continue to >>> submit as individual drafts to the Applications Area? > > > -- > (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] > )) Easier, More Reliable, Self Healing Downloads > _______________________________________________ > ftpext mailing list > ftpext@ietf.org > https://www.ietf.org/mailman/listinfo/ftpext > From A.Hoenes@TR-Sys.de Tue Oct 19 07:36:03 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7D4A3A681F for ; Tue, 19 Oct 2010 07:36:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -98.116 X-Spam-Level: X-Spam-Status: No, score=-98.116 tagged_above=-999 required=5 tests=[AWL=0.633, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9fN5RuXipTp1 for ; Tue, 19 Oct 2010 07:36:02 -0700 (PDT) Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id C72F83A67FD for ; Tue, 19 Oct 2010 07:36:01 -0700 (PDT) Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA062608945; Tue, 19 Oct 2010 16:35:45 +0200 Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id QAA21818; Tue, 19 Oct 2010 16:35:43 +0200 (MESZ) From: Alfred =?hp-roman8?B?SM5uZXM=?= Message-Id: <201010191435.QAA21818@TR-Sys.de> To: alexey.melnikov@isode.com Date: Tue, 19 Oct 2010 16:35:43 +0200 (MESZ) X-Mailer: ELM [$Revision: 1.17.214.3 $] Mime-Version: 1.0 Content-Type: text/plain; charset=hp-roman8 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Tue, 19 Oct 2010 07:49:49 -0700 Cc: ftpext@ietf.org, klensin@jck.com, stpeter@stpeter.im Subject: Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 14:36:03 -0000 Alexey, thanks for the sublime reminder ... > Looking at the original BOF request, I am wondering what should > happen to the following: > > draft-hoffman-ftp-uri-04 - The ftp URI Scheme > draft-klensin-ftp-typeu-00 - FTP Extension for Internationalized Text I'm the guilty one for the former; the pre-draft on the FTP URI scheme is still lingering in my pipeline. (Admittedly, it has lacked a bit of priority, but that can be changed.) Now that the -00 I-D submisison cutoff deadline has passed, I'll try to get an initial version ready for submisison soon after I-D submission is open again in the IETF meeting week. > In particular, I would like this WG to revise the FTP URI spec, > but I understand that there might be no interest in doing that. There indeed are a serious aspects that should be reviewed on the ftpext list, independent of the final decision on WG formation. I'll announce the I-D submisison on ftpext once it's done. Kind regards, Alfred HÎnes. -- +------------------------+--------------------------------------------+ | TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 Ditzingen | E-Mail: ah@TR-Sys.de | +------------------------+--------------------------------------------+ From A.Hoenes@TR-Sys.de Tue Oct 19 12:34:13 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AF3E3A6929 for ; Tue, 19 Oct 2010 12:34:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -98.134 X-Spam-Level: X-Spam-Status: No, score=-98.134 tagged_above=-999 required=5 tests=[AWL=0.615, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iwrTzALeDxbs for ; Tue, 19 Oct 2010 12:34:11 -0700 (PDT) Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 34FDD3A67AB for ; Tue, 19 Oct 2010 12:34:04 -0700 (PDT) Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA065146891; Tue, 19 Oct 2010 21:34:51 +0200 Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id VAA23423; Tue, 19 Oct 2010 21:34:49 +0200 (MESZ) From: Alfred =?hp-roman8?B?SM5uZXM=?= Message-Id: <201010191934.VAA23423@TR-Sys.de> To: iamvic@rambler.ru Date: Tue, 19 Oct 2010 21:34:48 +0200 (MESZ) In-Reply-To: <20101019190259.07FECE066E@rfc-editor.org> from RFC Errata System at Oct "19, " 2010 "12:02:58" pm X-Mailer: ELM [$Revision: 1.17.214.3 $] Mime-Version: 1.0 Content-Type: text/plain; charset=hp-roman8 Content-Transfer-Encoding: 7bit Cc: iana@iana.org, john+ietf@jck.com, ftpext@ietf.org, iesg@iesg.org, rfc-editor@rfc-editor.org Subject: Re: [ftpext] [Technical Errata Reported] RFC5797 (2581) X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2010 19:34:13 -0000 Correct! Thanks for catching this. To the verifier: The IANA registry (ftp-commands-extensions.*) needs to be corrected as well. I therefore have Cc'ed IANA. Kind regards, Alfred. -- +------------------------+--------------------------------------------+ | TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 Ditzingen | E-Mail: ah@TR-Sys.de | +------------------------+--------------------------------------------+ The RFC Errata system wrote: > The following errata report has been submitted for RFC5797, > "FTP Command and Extension Registry". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=5797&eid=2581 > > -------------------------------------- > Type: Technical > Reported by: VicTor Smirnoff > > Section: 3 > > Original Text > ------------- > | STOU | base | Store Unique | a | o | 959, 1123 | > > Corrected Text > -------------- > | STOU | base | Store Unique | s | o | 959, 1123 | > > Notes > ----- > RFC0959 has defined STOU as FTP (S)ervice command, but not > (A)ccess Control command > > Instructions: > ------------- > This errata is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC5797 (draft-klensin-ftp-registry-04) > -------------------------------------- > Title : FTP Command and Extension Registry > Publication Date : March 2010 > Author(s) : J. Klensin, A. Hoenes > Category : PROPOSED STANDARD > Source : IETF - NON WORKING GROUP > Area : N/A > Stream : IETF > Verifying Party : IESG From maxpassion@gmail.com Thu Oct 21 01:25:06 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 671983A69C7 for ; Thu, 21 Oct 2010 01:25:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.479 X-Spam-Level: X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cWL1lavJDwpd for ; Thu, 21 Oct 2010 01:25:05 -0700 (PDT) Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id C57953A686D for ; Thu, 21 Oct 2010 01:25:04 -0700 (PDT) Received: by gyc15 with SMTP id 15so2886617gyc.31 for ; Thu, 21 Oct 2010 01:26:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=0YE1trwJB9sf2Uy9vHPrAGUxmC3WOaIT3O864D0t0K4=; b=XjAGS216jTu54lBnV0B8Df0KuBX5KrmUKsZ8zjGwMmMUlHsZHczWuH5tINIOBCYitQ IERvuaokNvjQfz7mDBHKHYtdBjdP9J5oiGtKz4pNYUuqDvtNhAnAmPFYQNPk2yb6Tsrk cbaxmdTUslKxgu7f6/6OZ8AQAVDjV5vXNjlyw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IovlYwdTP/V2mB8bTqhK4v8IPX5sRcmxqtLVOocfJ3Xm8SXoqaA6w9uvGjziZ1kR40 7nXZOyLfd11irl1G3R+s6ZMwmjOT5Rn196REwRPLhEXmHzjKXm0wCW3PcOP6fcBJ91it CiCq+nUbaCMqAW6R0pcsd31+2M2pXcqucHILU= MIME-Version: 1.0 Received: by 10.42.230.193 with SMTP id jn1mr319555icb.257.1287649598386; Thu, 21 Oct 2010 01:26:38 -0700 (PDT) Received: by 10.220.10.211 with HTTP; Thu, 21 Oct 2010 01:26:38 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Oct 2010 16:26:38 +0800 Message-ID: From: liu dapeng To: Anthony Bryan Content-Type: text/plain; charset=ISO-8859-1 Cc: Robert McMurray , "ftpext@ietf.org" Subject: Re: [ftpext] Submitting new drafts X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 08:25:06 -0000 Hi Anthony, Thanks for posting the draft charter, just have one comment: The WG's specification deliverables include "A document that specifies FTP extensions to support IPv4/IPv6 translation scenario" but there is no corresponding Goals and Milestones? Best regards, Dapeng Liu 2010/10/18, Anthony Bryan : > I think the problem is that there isn't a FTPEXT WG yet & it doesn't > seem definite that there will be one. > > I've been posting a draft charter (included here) but...not sure what > the next step is. > > I added draft-liu-ftp64-extension, which I just saw turn up. > > somewhat on topic, does anyone know how to change the WG in xml2rfc? > > > > FTP Extensions, 2nd edition (ftpext2) Charter > > Chair(s): > TBD > > IETF Area: > Applications Area > > Applications Area Directors: > Alexey Melnikov > Peter Saint-Andre > > Responsible Area Director: > Alexey Melnikov > > Mailing list: > General Discussion: ftpext@ietf.org > Archive: > http://www.ietf.org/mail-archive/web/ftpext/current/maillist.html > > Description of Working Group: > > The Standard File Transfer Protocol specification in RFC 959 > has been updated several times with command extensions of one > sort or another, including those based on the extension > mechanism of RFC 2389 (a complete list appears in RFC 5797 and > the corresponding IANA registry at > http://www.iana.org/assignments/ftp-commands-extensions/ftp-commands-extensions.xhtml > ). > > The following are active FTP related drafts: > > draft-bryan-ftp-hash > draft-hethmon-mcmurray-ftp-hosts > draft-liu-ftp64-extension > draft-peterson-streamlined-ftp-command-extensions > draft-preston-ftpext-deflate > > The Working Group will: > * Review and finalize drafts listed above. > * Continue work on other drafts that are already in progress. > * Review and confirm or reject errata of current FTP RFCs. > * Investigate the differences between FTP in theory > (current RFCs) and practice, and recommend future work to align them. > > The Working Group's specification deliverables are: > * A document that specifies the HOST command (Proposed Standard). > * A document that specifies the HASH command (Proposed Standard). > * A document that specifies FTP extensions to support IPv4/IPv6 > translation scenario. > > The Working Group must not introduce a new version of FTP, e.g. > an incompatible FTP 2.0. > > Goals and Milestones > Oct 2010 Submit 'File Transfer Protocol HOST Command for Virtual > Hosts' as working group item (draft-hethmon-mcmurray-ftp-hosts will be > used as a starting point) > Oct 2010 Submit 'File Transfer Protocol HASH Command for > Cryptographic Hashes' as working group item (draft-bryan-ftp-hash will > be used as a starting point) > TBD 2010 Working group Last Call of HOST document > TBD 2010 Submit 'File Transfer Protocol HOST Command for Virtual > Hosts' to the IESG for consideration as a Proposed Standard > TBD 2011 Working group Last Call of HASH document > TBD 2011 Submit 'File Transfer Protocol HASH Command for > Cryptographic Hashes' to the IESG for consideration as a Proposed > Standard > TBD 2011 Close or recharter > > On Sun, Oct 17, 2010 at 10:18 AM, William F. Maton wrote: >> >> Punt it into ftpext2 please, otherwise there's not much point to having >> one. >> >> On Sat, 16 Oct 2010, Robert McMurray wrote: >> >>> I'd like to submit a new draft (see attached) that is unrelated to my >>> other draft - should we be using FTPEXT2 as the WG? Or should continue to >>> submit as individual drafts to the Applications Area? > > > -- > (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] > )) Easier, More Reliable, Self Healing Downloads > _______________________________________________ > ftpext mailing list > ftpext@ietf.org > https://www.ietf.org/mailman/listinfo/ftpext > From anthonybryan@gmail.com Thu Oct 21 10:43:45 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E28293A6A7C for ; Thu, 21 Oct 2010 10:43:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.338 X-Spam-Level: X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[AWL=0.261, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ui9xGmA10mFc for ; Thu, 21 Oct 2010 10:43:44 -0700 (PDT) Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 748A73A6A64 for ; Thu, 21 Oct 2010 10:43:44 -0700 (PDT) Received: by ewy27 with SMTP id 27so269159ewy.31 for ; Thu, 21 Oct 2010 10:45:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=544c7pxUeGLIjW4ODtshuanDQ3gW5xjwoD85zJWbkio=; b=kl8j8hsnSSoLX3xUVIf6e+17Ed0qoySYzniL8Ysg7bkSLwcisVo2E/UxbUX8X1veKG ZgC6j/Vw7O1Lkd23GguwXF5DvBleaUv1p4rZxAsO3MMc7rkHU6YbCzLlMnUD0XFRn/3e v+YEtuSQg4U8RpCDkEqfaBMIxEdQ9oOXhuZfI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Zk2+Hr9H7+pvh1sLvYDpU0A424ztL7QKK+BDmehCun8FBm/RXmdsOv9CNT97F5Diz3 Ib+fAu9ni3t8z+5twfSvRH9Xpjvr6n6iWBOffifI2K9LBVB0RM6hrO3d2wNiXzamDD1E 8ypirQys26tFJfYJIerSNXZ87q0Pm5RGDzzbM= MIME-Version: 1.0 Received: by 10.213.11.17 with SMTP id r17mr2058778ebr.66.1287683119037; Thu, 21 Oct 2010 10:45:19 -0700 (PDT) Received: by 10.213.28.143 with HTTP; Thu, 21 Oct 2010 10:45:19 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Oct 2010 13:45:19 -0400 Message-ID: From: Anthony Bryan To: liu dapeng Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "ftpext@ietf.org" Subject: Re: [ftpext] Submitting new drafts X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 17:43:46 -0000 On Thu, Oct 21, 2010 at 4:26 AM, liu dapeng wrote: > Hi Anthony, > > Thanks for posting the draft charter, just have one comment: > > The =A0WG's specification deliverables include "A document that > specifies FTP extensions to support IPv4/IPv6 translation scenario" > but there is no corresponding Goals and Milestones? I didn't add anything because I'm waiting for people to review and comment on the draft charter :) especially people like you, authors of drafts. how does this sound? do you want to suggest a date? TBD 2010 Submit 'FTP extensions to support IPv4/IPv6 translation' as working group item (draft-liu-ftp64-extension will be used as a starting point) TBD 2011 Submit 'FTP extensions to support IPv4/IPv6 translation' to the IESG for consideration as Informational here's the revised section, also w/ FTP URI: Goals and Milestones Nov 2010 Submit 'File Transfer Protocol HOST Command for Virtual Hosts' as working group item (draft-hethmon-mcmurray-ftp-hosts will be used as a starting point) Nov 2010 Submit 'File Transfer Protocol HASH Command for Cryptographic Hashes' as working group item (draft-bryan-ftp-hash will be used as a starting point) TBD 2010 Submit 'FTP extensions to support IPv4/IPv6 translation' as working group item (draft-liu-ftp64-extension will be used as a starting point) TBD 2010 Submit 'FTP URI Scheme' as working group item (draft-hoenes-ftp-uri? will be used as a starting point) TBD 2010 Working group Last Call of HOST document TBD 2010 Submit 'File Transfer Protocol HOST Command for Virtual Hosts' to the IESG for consideration as a Proposed Standard TBD 2011 Working group Last Call of HASH document TBD 2011 Submit 'File Transfer Protocol HASH Command for Cryptographic Hashes' to the IESG for consideration as a Proposed Standard TBD 2011 Submit 'FTP extensions to support IPv4/IPv6 translation' to the IESG for consideration as Informational TBD 2011 Submit 'FTP URI Scheme' to the IESG for consideration as a Proposed Standard TBD 2011 Close or recharter --=20 (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] =A0 )) Easier, More Reliable, Self Healing Downloads From alexey.melnikov@isode.com Sun Oct 24 01:41:38 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 769883A6407 for ; Sun, 24 Oct 2010 01:41:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.73 X-Spam-Level: X-Spam-Status: No, score=-102.73 tagged_above=-999 required=5 tests=[AWL=-0.131, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHPE-5ZofW+h for ; Sun, 24 Oct 2010 01:41:37 -0700 (PDT) Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 1742B3A6784 for ; Sun, 24 Oct 2010 01:41:37 -0700 (PDT) Received: from [192.168.20.2] ((unknown) [212.183.140.35]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Sun, 24 Oct 2010 09:43:16 +0100 X-SMTP-Protocol-Errors: NORDNS Message-ID: <4CC3F19B.2020302@isode.com> Date: Sun, 24 Oct 2010 09:43:07 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Anthony Bryan References: <4C8743B4.4030101@isode.com> <4C8F5A42.5000601@isode.com> <4CBD4371.7040202@isode.com> In-Reply-To: <4CBD4371.7040202@isode.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ftpext@ietf.org, John C Klensin , Peter Saint-Andre Subject: Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2010 08:41:38 -0000 Alexey Melnikov wrote: > Anthony Bryan wrote: > >> On Tue, Sep 14, 2010 at 7:19 AM, Alexey Melnikov >> wrote: >> >>> Anthony Bryan wrote: >> [...] >> does anyone else have any comments? deliverables/goals? > I took the liberty of submitting your last version of the charter to IESG/IAB for review. I've made some minor adjustments to milestone dates. If people can agree on the mailing list about the 2 documents I've asked about, they can be added to the charter before the WG is approved. > Looking at the original BOF request, I am wondering what should happen > to the following: > > draft-hoffman-ftp-uri-04 - The ftp URI Scheme > draft-klensin-ftp-typeu-00 - FTP Extension for Internationalized Text > > In particular, I would like this WG to revise the FTP URI spec, but I > understand that there might be no interest in doing that. Best Regards, Alexey -- IETF Application Area Director, Internet Messaging Team Lead, JID: same as my email address From klensin@jck.com Mon Oct 25 06:43:51 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F10533A6A4D for ; Mon, 25 Oct 2010 06:43:50 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Improper folded header field made up entirely of whitespace: References: ...iy4A8@mail.gmail.com> \n \n ; Mon, 25 Oct 2010 06:43:49 -0700 (PDT) Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id ECAD63A69F5 for ; Mon, 25 Oct 2010 06:43:25 -0700 (PDT) Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PANLF-000PwO-Qj; Mon, 25 Oct 2010 09:44:02 -0400 Date: Mon, 25 Oct 2010 09:44:00 -0400 From: John C Klensin To: Alexey Melnikov , Anthony Bryan Message-ID: <8DA204088E94DC87D76AF49A@PST.JCK.COM> In-Reply-To: <4CC3F19B.2020302@isode.com> References: <4C8743B4.4030101@isode.com> <4C8F5A42.5000601@isode.com> <4CBD4371.7040202@isode.com> <4CC3F19B.2020302@isode.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mailman-Approved-At: Mon, 25 Oct 2010 06:52:14 -0700 Cc: ftpext@ietf.org, Peter Saint-Andre Subject: Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2010 13:43:51 -0000 --On Sunday, October 24, 2010 09:43 +0100 Alexey Melnikov wrote: > Alexey Melnikov wrote: > >> Anthony Bryan wrote: >> >>> On Tue, Sep 14, 2010 at 7:19 AM, Alexey Melnikov >>> wrote: >>> >>>> Anthony Bryan wrote: >>> > [...] > >>> does anyone else have any comments? deliverables/goals? >> > I took the liberty of submitting your last version of the > charter to IESG/IAB for review. I've made some minor > adjustments to milestone dates. > > If people can agree on the mailing list about the 2 documents > I've asked about, they can be added to the charter before the > WG is approved. > >> Looking at the original BOF request, I am wondering what >> should happen to the following: >> >> draft-hoffman-ftp-uri-04 - The ftp URI Scheme While I think this is important, it gets tied up with the entire URI/ i18n/ IRI situation as well as evolving i18n work on FTP (e.g., an eventual review of RFC 2640). I don't know (1) whether FTPEXT2 is the optimal place to do that work nor (2) whether this is the right time to do it given that FTP extensions work could affect the URI definition. >> draft-klensin-ftp-typeu-00 - FTP Extension for >> Internationalized Text Well, I think that one is important, but I'm biased by a combination of too much time in the i18n space and a continued belief that TYPE A has actually been useful. I think it will be particularly important if we continue to see a variety of CCSs in use in local filesystems (ISO8859-x, BIG5, GBxxxx, ISO2022-JP, etc.) and/or some local filesystems using Unicode in UTF-16, others in UTF-8, and perhaps still others in UTF-32. On the other hand, if no one sees a reason to implement it, it should remain on hold until and unless that changes. >> In particular, I would like this WG to revise the FTP URI >> spec, but I understand that there might be no interest in >> doing that. I'm less concerned about interest than I am about the right mix of skills. I note that draft-hoffman-ftp-uri-04 expired over five years ago and that there has been a lot of thinking about URIs since. I wonder if that draft would even still be a good foundation (I just glanced at it but haven't looked carefully at it in a couple of years). My recollection is that it carries forward the URI definition from RFC 1738 and therefore has no provisions for extensions (commands or functions not found in RFC 959) at all. It also appears to have assumed that FTP was going to be static: not only is that unlikely to be true in a world in which we have an extension mechanism and are using it but overloading NLST (or other commands) on TYPE could turn out to be a really bad plan. My instinct is that it might be reasonable to put "new/updated FTP URI scheme" somewhere in the WG's queue, but that, while such an effort should consider the RFC 1738 / draft-hoffman-ftp-uri approach, it may well want to start over and design something appropriate for "modern" FTP, even if that requires a different scheme keyword. best regards, john From iana-shared@icann.org Wed Oct 27 00:13:01 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA0FA3A6997 for ; Wed, 27 Oct 2010 00:13:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.215 X-Spam-Level: X-Spam-Status: No, score=-5.215 tagged_above=-999 required=5 tests=[AWL=-3.908, BAYES_00=-2.599, MISSING_HEADERS=1.292] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14gK0sqMozEB for ; Wed, 27 Oct 2010 00:13:01 -0700 (PDT) Received: from pechora3.lax.icann.org (pechora3.icann.org [208.77.188.38]) by core3.amsl.com (Postfix) with ESMTP id 8A8D83A6915 for ; Wed, 27 Oct 2010 00:13:01 -0700 (PDT) Received: from request1.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id o9R7E4K4028656; Wed, 27 Oct 2010 00:14:24 -0700 Received: from request1.lax.icann.org (localhost.localdomain [127.0.0.1]) by request1.lax.icann.org (8.13.8/8.13.8) with ESMTP id o9R7E4Bd019993; Wed, 27 Oct 2010 07:14:04 GMT Received: (from apache@localhost) by request1.lax.icann.org (8.13.8/8.13.8/Submit) id o9R7E37g019990; Wed, 27 Oct 2010 07:14:03 GMT From: "Amanda Baber via RT" In-Reply-To: <201010191934.VAA23423@TR-Sys.de> References: System at Message-ID: Precedence: bulk X-RT-Loop-Prevention: IANA RT-Ticket: IANA #400731 Managed-by: RT 3.8.HEAD (http://www.bestpractical.com/rt/) RT-Originator: amanda.baber@icann.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Wed, 27 Oct 2010 07:14:03 +0000 X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [208.77.188.38]); Wed, 27 Oct 2010 00:14:24 -0700 (PDT) X-Mailman-Approved-At: Wed, 27 Oct 2010 04:46:39 -0700 Cc: john+ietf@jck.com, ftpext@ietf.org, iesg@iesg.org, rfc-editor@rfc-editor.org Subject: [ftpext] [IANA #400731] Re: [Technical Errata Reported] RFC5797 (2581) X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Reply-To: iana-questions@iana.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2010 07:13:01 -0000 Hi Alfred, all, We'll make the change after we receive word that the errata has been verified. Thanks, Amanda Baber IANA On Tue Oct 19 19:35:34 2010, ah@tr-sys.de wrote: > Correct! > > Thanks for catching this. > > To the verifier: The IANA registry (ftp-commands-extensions.*) > needs to be corrected as well. I therefore have Cc'ed IANA. > > Kind regards, > Alfred. > From A.Hoenes@TR-Sys.de Fri Oct 29 10:45:07 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 226313A677C for ; Fri, 29 Oct 2010 10:45:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -98.322 X-Spam-Level: X-Spam-Status: No, score=-98.322 tagged_above=-999 required=5 tests=[AWL=0.427, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9S5hLwAYuqlg for ; Fri, 29 Oct 2010 10:45:05 -0700 (PDT) Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 239153A67FC for ; Fri, 29 Oct 2010 10:44:59 -0700 (PDT) Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA122844392; Fri, 29 Oct 2010 19:46:32 +0200 Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id TAA10758; Fri, 29 Oct 2010 19:46:30 +0200 (MESZ) From: Alfred =?hp-roman8?B?SM5uZXM=?= Message-Id: <201010291746.TAA10758@TR-Sys.de> To: klensin@jck.com, ftpext@ietf.org Date: Fri, 29 Oct 2010 19:46:30 +0200 (MESZ) X-Mailer: ELM [$Revision: 1.17.214.3 $] Mime-Version: 1.0 Content-Type: text/plain; charset=hp-roman8 Content-Transfer-Encoding: 8bit Cc: alexey.melnikov@isode.com, stpeter@stpeter.im Subject: Re: [ftpext] Followup on FTPEXT2 BOF in Maastricht X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2010 17:45:07 -0000 John, thanks for your additional considerations. You wrote, in response to Alexey's appeal: >>> [Alexey] >>> In particular, I would like this WG to revise the FTP URI spec, >>> but I understand that there might be no interest in doing that. > > [John] > I'm less concerned about interest than I am about the right mix > of skills. I note that draft-hoffman-ftp-uri-04 expired over > five years ago and that there has been a lot of thinking about > URIs since. I wonder if that draft would even still be a good > foundation (I just glanced at it but haven't looked carefully at > it in a couple of years). My recollection is that it carries > forward the URI definition from RFC 1738 and therefore has no That's what has Paul confirmed. That draft essentially only was an excerpt from the old RFCs and there was a lack of energy and resources, and of interest from the community, in doing improvements. > provisions for extensions (commands or functions not found in > RFC 959) at all. It also appears to have assumed that FTP was > going to be static: not only is that unlikely to be true in a > world in which we have an extension mechanism and are using it > but overloading NLST (or other commands) on TYPE could turn out > to be a really bad plan. > > My instinct is that it might be reasonable to put "new/updated > FTP URI scheme" somewhere in the WG's queue, but that, while > such an effort should consider the RFC 1738 / > draft-hoffman-ftp-uri approach, it may well want to start over > and design something appropriate for "modern" FTP, even if that > requires a different scheme keyword. My existing pre-draft already _is_ different from draft-hoffman-ftp-uri-04, but it is still imcomplete and not yet ready to be submitted. I indeed plan to do that ASAP, most likely shortly after the IETF. One of the points where I got stuck when this work started out also was related to the perceived mismatch between the very conservative approach of the old 'ftp' URI scheme and the capabilities of more modern FTP servers that you describe. In particular, one raw idea I had started off during working on the text to describe the tedious step-by-step navigation procedures prescribed in the old spec for a "consumer" of an 'ftp' URI (see Section 3.2.2, "FTP url-path", of RFC 1738). This procedure was based on the lack of an accepted model for the (abstract or concrete) hierarchical naming system (supported by URIs in general, but not expected by FTP servers at the time of RFC 959). Since those days, the old FTPEXT WG has produced a specification of the TVFS, published in RFC 3659. My idea then was: If an 'ftp' URI could carry an indication that the server specified in the part if the URI supports the TVFS model (it will announce TVFS capability if asked), and therefore that URI follows TVFS semantics, an application interpreting such URIs could save a lot of round trips and gain performance (on both sides of the control connection and on the network) by directly changing directory in a single step over multiple hierarchical levels. The proper way I envision to encode this extra information is via a URI parameter, say ";tvfs". This would maintain backwards compatibility (a client that doesn't understand and support the parameter would ignore it -- following the robustness principle -- and behave as inefficiently as it did before, and the original creator/publisher of an 'ftp' URI is expected to know the capabilities of her server(s) and therefore would only add this parameter if the related expected "new" client behavior would be supported by the server(s). Similar extensions could be conceived for other server capabilities (yet to be determined) for which it would make sense to make prospective URI consumers aware of beforehands, without having to negotiate with the server. Questions: +++++++++ A) John: Does this idea match what you had in mind ? B) to the list: (1) What do you think about this idea ? In detail: (2) Is there actually a problem in practice, i.e. are there opportunities and needs, e.g. for optimization, that actually need to be addressed? (3) Does the general approach of encoding server capabilities in 'ftp' URIs make sense? (4) Would there be good chance this would be supported by (client) implementations and 'ftp' URI creators ? (5) Does the encoding in a URI parameter make sense to you? (6) Is the above idea worth being specified in the inital new ftp-uri draft ? Feedback welcome! Kind regards, Alfred HÎnes. -- +------------------------+--------------------------------------------+ | TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 Ditzingen | E-Mail: ah@TR-Sys.de | +------------------------+--------------------------------------------+ Appendix -- for more context: ++++++++ The introduction of my current pre-draft currently says: 1. Introduction Uniform Resource Identifiers (URIs) were initially described for the IETF in RFC 1630 [RFC1630], and later on more precisely specified, first in RFC 1738 [RFC1738] and RFC 1808 [RFC1808], then by RFC 2396 [RFC2396], which eventually was obsoleted by STD 66, RFC 3986 [RFC3986]. The earlier documents also specified how to define schemes for URIs; the applicable rules and procedures for URI schemes are now prescribed by BCP 35, RFC 4395 [RFC4395]. The first definition for many 'classical' URI schemes also appeared in RFC 1630 [RFC1630]; the first standard specifications for these were contained in RFC 1738 [RFC1738], and RFC 1808 [RFC1808] has elaborated on "relative URLs" (now more precisely called "relative URI references" in STD 66). These documents were made obsolete without creating replacement documents for all parts of their URI scheme specific content. Thereby, some basic URI schemes that are in widespread use have been orphaned, leaving the IANA Registry of URI schemes without a valid reference to a normative definition document. Most of these gaps already have been closed (by RFCs 4156, 4157, 4248, 4266, and 5538). This document recollects and updates the definition of the 'ftp' URI scheme from the older RFCs to allow that material to remain on the Standards Track and bring it in alignment with current IETF STD and BCP documents. Note that the 'file' and 'ftp' URIs are not the same, even when the target of the 'ftp' URI is the local host. Specification of the 'file' URI scheme is out of scope for this draft. And this is what I have in the central syntax and semantics part, *without* any mention of the aforementioned extension: 2.4. FTP url-path The of an FTP URI has the following form: //...//[;type=] through and are (possibly encoded) strings and is one of the characters "a", "i", or "d". The and parts may be empty. The part ";type=" may be omitted. In fact, the whole url-path, including the leading "/", may be omitted. The is interpreted as a series of FTP commands as follows: o Each of the elements is to be supplied, sequentially, as the argument to a CWD (change working directory) command. o If the typecode is "d", perform a NLST (name list) command with as the argument, and interpret the results as a file directory listing. o Otherwise, perform a TYPE command with as the argument, and then access the file whose name is (for example, using the RETR command.) Within a or component, the characters "/" and ";" are reserved and must be encoded. The components are decoded prior to their use in the FTP protocol. In particular, if the appropriate FTP sequence to access a particular file requires supplying a string containing a "/" as an argument to a CWD or RETR command, it is necessary to encode each "/". Historical note: Most FTP client implementations precede the with a "/" before sending the CWD command. This is in conflict with RFC 1738, although the practice is quite widespread. Thus, a client that is presented with the URI ftp://myname@example.com/abc/def might send the two commands "CWD /abc" and "RETR def" or it might send the two commands "CWD abc" and "RETR def". Server implementers should be aware of these two different interpretations of the same URI. FTP URIs may also be used for other operations; for example, it is possible to update a file on a remote file server, or infer information about it from the directory listings or FTP extension commands. The mechanism for doing so is not spelled out here. 2.5. FTP Typecode is Optional The entire ;type= part of a FTP URI is optional and is rarely used. Historically, the typecode option was rarely implemented and, in practice, dereferencing is done by guessing. If the typecode is omitted, the client program interpreting the URI must guess the appropriate mode to use. In general, the data content type of a file can only be guessed from the name, such as from the suffix of the name; the appropriate type code to be used for the transfer of the file can then be deduced from the data content of the file. Additional question to the list: I have been told that in practice RFC 1738 behavior described above is not followed and RFC 1630 behavior is implemented: In current practice, a trailing "/" in the (i.e. an empty is regarded as equivalent to (and a substitute for) ";type=d". Is that correct ? From john-ietf@jck.com Fri Oct 29 12:52:33 2010 Return-Path: X-Original-To: ftpext@core3.amsl.com Delivered-To: ftpext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D0CF3A682A for ; Fri, 29 Oct 2010 12:52:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.45 X-Spam-Level: X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tSaoogYQ30qC for ; Fri, 29 Oct 2010 12:52:32 -0700 (PDT) Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id E2D733A6A74 for ; Fri, 29 Oct 2010 12:52:31 -0700 (PDT) Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PBv1p-000KyW-Cz; Fri, 29 Oct 2010 15:54:21 -0400 Date: Fri, 29 Oct 2010 15:54:20 -0400 From: John C Klensin To: "Alfred H?nes" , ftpext@ietf.org Message-ID: In-Reply-To: <201010291746.TAA10758@TR-Sys.de> References: <201010291746.TAA10758@TR-Sys.de> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: alexey.melnikov@isode.com, stpeter@stpeter.im Subject: [ftpext] RFC 959Re: Followup on FTPEXT2 BOF in Maastricht X-BeenThere: ftpext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2010 19:52:33 -0000 --On Friday, October 29, 2010 19:46 +0200 "Alfred H?nes" wrote: >... > Questions: > +++++++++ > > A) John: Does this idea match what you had in mind ? No, but mostly because I'm trying to remain agnostic. Historically, the reason why the navigation facilities of RFC 959 are so primitive is because, at the time FTP was developed, we had a wide variety of file system organizations and no general model was possible. With RFC 3659 and TVFS, the community recognized that virtually all contemporary file systems use a hierarchical model that, when abstracted from issues of syntax, actual file storage forms, and encoding of content types into file names, all turn out to be pretty much the same. If we expect that to remain the case, or decide that FTP should make that case easy and any other cases hard, then your idea, plus or minus details, makes a lot of sense. However, consider the following strawman fantasy: say that various "semantic connections among data" take off and that some were to actually develop a file system and data model that is semantic-relational rather than hierarchical or multihierarchical. At that point, TVFS becomes as irrelevant as some of the historical data storage models are to the hierarchical one. > B) to the list: > > (1) What do you think about this idea ? In detail: > > (2) Is there actually a problem in practice, i.e. are there > opportunities and needs, e.g. for optimization, that > actually need to be addressed? Note that these issues might be an additional argument for "streamlined" or combination commands such as those for which there is at least one proposal in the hopper. I'd rather see aggressive, asynchronous-command pipelining (which is part of what we had in mind in the early 70s when the two-stream model was defined) but it may be too late for that. > (3) Does the general approach of encoding server capabilities > in 'ftp' URIs make sense? I rather doubt it, but that is a much more complicated question. >... john p.s. This list is not on the non-WG mailing lists page. Unless we anticipate a charter approval _really_ quickly, that should probably be fixed.