Text 2229, 77 rader
Skriven 2004-07-30 09:25:22 av Jasen Betts (3:640/1042)
   Kommentar till text 2192 av Alex Shakhaylo (2:461/701)
Ärende: internet connectivity FSP
=================================
Hello Alex.

29 Jul 04 04:24, you wrote to all:

 AS> Hi, All!

 AS> This is not a text, just a notes concerning future FSP.
 AS> This is a subject to discuss.

 AS> ===

 AS> The first reason to write this FSP is suggestion
 AS> to use common FTN-like authentication scheme for
 AS> all the internet protocols that are used in FTN.
 AS> (FTP, SMTP, POP3, IMAP, HTTP, forgot something ?)

pop3 and imap aren't used to send, only SMTP

 AS> This scheme is plain simple:

 AS> username is an FTN address
 AS> password is session password (for secure links)
 AS>             blank or anything (for insecure links and
 AS>             plain authentication)
 AS>             '-' (for insecure links and CRAM-MD5 based
 AS>             authentication)

 AS> This scheme gives a way to keep processing as close
 AS> to usual FTN processing as it is possible and allows
 AS> server to know remote FTN address at the very first
 AS> protocol stage.

I think allowance should be made where there is already an existing method
IE allow anonymous and FTN address for FTP.

otherwise noone with a standard FTP server will be able to support FTP.
(unless they add users with every name in the nodelist...)

 AS> The second reason is a need to clarify  HTTP usage
 AS> for FTN batch transfers.

 AS> This is also plain simple.

 AS> All the http requests use above described authentication
 AS> scheme.

 AS> 1.) when a client program wants to send a file to remote
 AS> it makes PUT request (for example: PUT /filename HTTP/1.<0|1>
 AS> where filename is a filename

 AS> 2.) when a client program wants to get a list of files
 AS> it makes GET request (GET /list? HTTP/1.<0|1>)

 AS> and gets a response with a plain-text list of files where
 AS> lines are separated by <cr><lf> and have format:

 AS> filename filesize filetime

 AS> 3.) when a client program wants to get file it makes
 AS> GET request (GET /filename HTTP/1.<0|1>)

 AS> Proposed http compataility can then be marked by IHT nodelist
 AS> flag.

 AS> http requests and responces headers should follow RFC-1945,
 AS> "Hypertext Transfer Protocol -- HTTP/1.0"

Hmm, what sort of CGI would be needed to do that with a regular webserer.

rather than painting an existing protocol in fidonet colours I think it may be
more useful to devise a way to use existing internet server software to handle
the FTN tasks

Jasen

--- GoldED+/LNX 1.1.4.7
 * Origin:  (3:640/1042)