On Tue, Nov 15, 2005 at 07:27:22PM +0100, Torsten Marek wrote: > I am thankful for all comments and corrections!
Hi! Great work! I'd just split the identification and the teaching part a bit more: > Tag: protocol::atm > Description: ATM > Asynchronous Transfer Mode, a high speed protocol for communication > between computers in a network. While ATM is used to implement *DSL network, > it has never gained widespread use as a technology for building local > area networks (LANs), for which it was originally intended. > . > http://en.wikipedia.org/wiki/Asynchronous_Transfer_Mode Tag: protocol::atm Description: ATM Asynchronous Transfer Mode, a high speed protocol for communication between computers in a network. . While ATM is used to implement *DSL network, it has never gained widespread use as a technology for building local area networks (LANs), for which it was originally intended. . http://en.wikipedia.org/wiki/Asynchronous_Transfer_Mode > Tag: protocol::corba > Description: CORBA > Common Object Request Broker Architecture, a standard for interoperability > between programs written in different languages and running on different > Hardware platforms. CORBA includes a client-server network protocol for > distributed computing. With this network protocol, CORBA clients on > different computers and written in different languages can exchange objects > over a CORBA server such as orbit2 or omniORB. > . > Link: http://www.corba.org/ Tag: protocol::corba Description: CORBA Common Object Request Broker Architecture, a standard for interoperability between programs written in different languages and running on different Hardware platforms. CORBA includes a client-server network protocol for distributed computing. . With this network protocol, CORBA clients on different computers and written in different languages can exchange objects over a CORBA server such as orbit2 or omniORB. . Link: http://www.corba.org/ > Tag: protocol::dns > Description: DNS > Domain Name System, a protocol to request information associated with > domain names (like "www.debian.org"), most prominently the IP address. The > protocol is used in communication with a DNS server (like BIND). For the > Internet, there are 13 root DNS servers around the world, that keep the > addresses of all registered domain names and provide this information to > the DNS servers of internet service providers. > . > Link: http://en.wikipedia.org/wiki/Domain_Name_System Tag: protocol::dns Description: DNS Domain Name System, a protocol to request information associated with domain names (like "www.debian.org"), most prominently the IP address. The protocol is used in communication with a DNS server (like BIND). . For the Internet, there are 13 root DNS servers around the world, that keep the addresses of all registered domain names and provide this information to the DNS servers of internet service providers. . Link: http://en.wikipedia.org/wiki/Domain_Name_System > Tag: protocol::ethernet > Description: Ethernet > Ethernet is the most popular networking technology for creatig local area > networks (LANs). The computers in an Ethernet network communicate over > twisted-pair or fibre cables and are identified by their MAC address. Several > different types of Ethernet exist, distinguishable by the maximum connection > speed. The most widespread types today are 100MBit/s (100BASE-*) or > 1GBit/s (1000BASE-*). > . > Link: http://en.wikipedia.org/wiki/Ethernet Tag: protocol::ethernet Description: Ethernet Ethernet is the most popular networking technology for creatig local area networks (LANs). . The computers in an Ethernet network communicate over twisted-pair or fibre cables and are identified by their MAC address. Several different types of Ethernet exist, distinguishable by the maximum connection speed. The most widespread types today are 100MBit/s (100BASE-*) or 1GBit/s (1000BASE-*). . Link: http://en.wikipedia.org/wiki/Ethernet > Tag: protocol::fidonet > Description: FidoNet > FidoNet is a mailbox system that enjoyed large popularity in the 1980s and > 1990s. The communication between the clients and FidoNet servers was usually > carried out over the telephone network using modems and could be used for > transferring messages (comparable to e-mail) and files. > . > Link: http://www.fidonet.org/ > Link: http://en.wikipedia.org/wiki/Fidonet Tag: protocol::fidonet Description: FidoNet FidoNet is a mailbox system that enjoyed large popularity in the 1980s and 1990s. . The communication between the clients and FidoNet servers was usually carried out over the telephone network using modems and could be used for transferring messages (comparable to e-mail) and files. . Link: http://www.fidonet.org/ Link: http://en.wikipedia.org/wiki/Fidonet [ah... the good old times of FidoNet :)] > Tag: protocol::finger > Description: Finger > The Name/Finger protocol is a simple network protocol to provide extensive, > public information about users of a computer, such as e-mail address, > telephone numbers, full names etc. Due to privacy concerns, the Finger > protocols is not widely used any more, while it widespread distribution > in the early 1990s. > . > Link: http://en.wikipedia.org/wiki/Finger_protocol > Link: http://www.ietf.org/rfc/rfc1288.txt Tag: protocol::finger Description: Finger The Name/Finger protocol is a simple network protocol to provide extensive, public information about users of a computer, such as e-mail address, telephone numbers, full names etc. . Due to privacy concerns, the Finger protocols is not widely used any more, while it had widespread distribution in the early 1990s. . Link: http://en.wikipedia.org/wiki/Finger_protocol Link: http://www.ietf.org/rfc/rfc1288.txt > Tag: protocol::ftp > Description: FTP > File Transfer Protocol, a protocol for exchanging files over networks and > extensively used in the Internet. The communication between FTP servers and > clients uses two channels, the control and the data channel. While FTP was > originally used with authentication only, most FTP servers on the internet > provide anonymous, passwordless access. Since FTP does not support > encryption, > sensitive data transfer is carried out over SFTP today. > . > Link: http://en.wikipedia.org/wiki/File_Transfer_Protocol > Link: http://www.ietf.org/rfc/rfc0959.txt Tag: protocol::ftp Description: FTP File Transfer Protocol, a protocol for exchanging files over networks and extensively used in the Internet. . The communication between FTP servers and clients uses two channels, the control and the data channel. While FTP was originally used with authentication only, most FTP servers on the internet provide anonymous, passwordless access. Since FTP does not support encryption, sensitive data transfer is carried out over SFTP today. . Link: http://en.wikipedia.org/wiki/File_Transfer_Protocol Link: http://www.ietf.org/rfc/rfc0959.txt > Tag: protocol::http > Description: HTTP > HyperText Transfer Protocol, one of the most important protocols for the > World Wide Web. It controls the data transfer between HTTP servers such as > Apache and HTTP clients, which are web browsers in most cases. HTTP > resources are requested via URLs (Universal Resource Locators). While HTTP > normally only supports file transfer from server to client, the protocol > supports sending information to HTTP server, most prominently used in HTML > forms. > . > Link: http://en.wikipedia.org/wiki/Http > Link: http://www.ietf.org/rfc/rfc2616.txt Tag: protocol::http Description: HTTP HyperText Transfer Protocol, one of the most important protocols for the World Wide Web. . It controls the data transfer between HTTP servers such as Apache and HTTP clients, which are web browsers in most cases. HTTP resources are requested via URLs (Universal Resource Locators). While HTTP normally only supports file transfer from server to client, the protocol supports sending information to HTTP server, most prominently used in HTML forms. . Link: http://en.wikipedia.org/wiki/Http Link: http://www.ietf.org/rfc/rfc2616.txt Or, we can even totally delegate teaching to wikipedia leaving only the initial description and the links: this would avoid us needing to maintain the replicated information. > * protocol::lp > Tag misnamed, should be lpr, maybe unix-lpr (see > http://www.ietf.org/rfc/rfc1179.txt). I'm fine with renaming it. > * protocol::aol-messenger, protocol::icq: > "Real" ICQ is dispreferred, ICQ uses OSCAR nowadays > Thus, it would be better to merge protocol::aol-messenger and protocol::icq > into > new protocol::oscar with the description "OSCAR (AIM/ICQ)". I'd rename this only if all ICQ clients we have are also AIM clients, and vice-versa. > * Why isn't it protocol::pop3, but protocol::pop? I guess because grep pop /etc/services gives pop2, pop3, pop3s and kpop, so we went for something that could include them all. I don't know if it makes sense nowadays, though, and pop3 could really be the one that includes them all anyway. Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
_______________________________________________ Debtags-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debtags-devel
