> NetichettaIt

Version as of 2004-12-13 00:13:30

Clear message

• FrontPage
• RecentChanges
• FindPage
• HelpContents

• Edit
• View
• Diffs
• Info
• Subscribe
• Raw
• Print

• LikePages
• LocalSiteMap
• SpellCheck

1. ITichetta

" quello che segue vorrebbe essere la reinvenzione dell'acqua calda; un tentativo, cioè di inutile 
miglioramento di qualcosa già esistente: riscrivere la [NETIQUETTE].
Non da capo, ovviamente! :-) ma adattandola ai tempi correnti.
Propongo l'esempio più banale: correggendo l'indicazione sull'uso delle lettere accentate 
(MUST ormai superato)."

Inserisco quindi il testo originale della RFC1855.
L'ipotesi di lavoro è la seguente:
- ovvia traduzione in lingua Italiana;
- depurazione dagli aspetti che non riguardano Usenet;
- aggiornamento alle prescrizioni tecnicamente valide oggigiorno.

----

Inizio dalla "depurazione "

-- CarloFusco

1.0 Introduction

----
Nota, l'introduzione mi piace, ma andrebbe anche emendata. Come facciamo, plagiamo
spudoratamente o separiamo le cose?

-- CarloFusco

In the past, the population of people using the Internet had "grown up" with the Internet, were technically minded, and understood the nature of the transport and the protocols. Today, the community of Internet users includes people who are new to the environment. These "Newbies" are unfamiliar with the culture and don't need to know about transport and protocols. In order to bring these new users into the Internet culture quickly, this Guide offers a minimum set of behaviors which organizations and individuals may take and adapt for their own use. Individuals should be aware that no matter who supplies their Internet access, be it an Internet Service Provider through a private account, or a student account at a University, or an account through a corporation, that those organizations have regulations about ownership of mail and files, about what is proper to post or send, and how to present yourself. Be sure to check with the local authority for specific guidelines.

We've organized this material into three sections: One-to-one communication, which includes mail and talk; One-to-many communications, which includes mailing lists and ?NetNews; and Information Services, which includes ftp, WWW, Wais, Gopher, MUDs and MOOs. Finally, we have a Selected Bibliography, which may be used for reference.

2.0 One-to-One Communication (electronic mail, talk)

We define one-to-one communications as those in which a person is communicating with another person as if face-to-face: a dialog. In general, rules of common courtesy for interaction with people should be in force for any situation and on the Internet it's doubly important where, for example, body language and tone of voice must be inferred. For more information on Netiquette for communicating via electronic mail and talk, check references [1,23,25,27] in the Selected Bibliography.

2.1 User Guidelines

2.1.1 For mail:

- Unless you have your own Internet access through an Internet
provider, be sure to check with your employer about ownership of electronic mail. Laws about the ownership of electronic mail vary from place to place.
- Unless you are using an encryption device (hardware or software),
you should assume that mail on the Internet is not secure. Never put in a mail message anything you would not put on a postcard.
- Respect the copyright on material that you reproduce. Almost
every country has copyright laws.
- If you are forwarding or re-posting a message you've received, do
not change the wording. If the message was a personal message to you and you are re-posting to a group, you should ask permission first. You may shorten the message and quote only relevant parts, but be sure you give proper attribution.
- Never send chain letters via electronic mail. Chain letters
are forbidden on the Internet. Your network privileges will be revoked. Notify your local system administrator

if your ever receive one.

- A good rule of thumb: Be conservative in what you send and
liberal in what you receive. You should not send heated messages (we call these "flames") even if you are provoked. On the other hand, you shouldn't be surprised if you get flamed and it's prudent not to respond to flames.
- In general, it's a good idea to at least check all your mail
subjects before responding to a message. Sometimes a person who asks you for help (or clarification) will send another message which effectively says "Never Mind". Also make sure that any message you respond to was directed to you. You might be cc:ed rather than the primary recipient.
- Make things easy for the recipient. Many mailers strip header
information which includes your return address. In order to ensure that people know who you are, be sure to include a line or two at the end of your message with contact information. You can create this file ahead of time and add it to the end of your messages. (Some mailers do this automatically.) In Internet parlance, this is known as a ".sig" or "signature" file. Your .sig file takes the place of your business card. (And you can have more than one to apply in different circumstances.)
- Be careful when addressing mail. There are addresses which
may go to a group but the address looks like it is just one person. Know to whom you are sending.
- Watch cc's when replying. Don't continue to include
people if the messages have become a 2-way conversation.
- In general, most people who use the Internet don't have time
to answer general questions about the Internet and its workings. Don't send unsolicited mail asking for information to people whose names you might have seen in RFCs or on mailing lists.
- Remember that people with whom you communicate are located across
the globe. If you send a message to which you want an immediate response, the person receiving it might be at home asleep when it arrives. Give them a chance to wake up, come to work, and login before assuming the mail didn't arrive or that they don't care.
- Verify all addresses before initiating long or personal discourse.
It's also a good practice to include the word "Long" in the subject header so the recipient knows the message will take time to read and respond to. Over 100 lines is considered "long".
- Know whom to contact for help. Usually you will have resources
close at hand. Check locally for people who can help you with software and system problems. Also, know whom to go to if you receive anything questionable or illegal. Most sites also have "Postmaster" aliased to a knowledgeable user, so you can send mail to this address to get help with mail.
- Remember that the recipient is a human being whose culture,
language, and humor have different points of reference from your own. Remember that date formats, measurements, and idioms may not travel well. Be especially careful with sarcasm.
- Use mixed case. UPPER CASE LOOKS AS IF YOU'RE SHOUTING.

- Use symbols for emphasis. That *is* what I meant. Use

underscores for underlining. _War and Peace_ is my favorite book.
- Use smileys to indicate tone of voice, but use them sparingly.
is an example of a smiley (Look sideways). Don't assume that the inclusion of a smiley will make the recipient happy with what you say or wipe out an otherwise insulting comment.
- Wait overnight to send emotional responses to messages. If you
have really strong feelings about a subject, indicate it via FLAME ON/OFF enclosures. For example: FLAME ON: This type of argument is not worth the bandwidth
it takes to send it. It's illogical and poorly reasoned. The rest of the world agrees with me.
FLAME OFF
- Do not include control characters or non-ASCII attachments in
messages unless they are MIME attachments or unless your mailer encodes these. If you send encoded messages make sure the recipient can decode them.
- Be brief without being overly terse. When replying to a message,
include enough original material to be understood but no more. It is extremely bad form to simply reply to a message by including all the previous message: edit out all the irrelevant material.
- Limit line length to fewer than 65 characters and end a line
with a carriage return.
- Mail should have a subject heading which reflects
the content of the message.
- If you include a signature keep it short. Rule of thumb
is no longer than 4 lines. Remember that many people pay for connectivity by the minute, and the longer your message is, the more they pay.
- Just as mail (today) may not be private, mail (and news) are
(today) subject to forgery and spoofing of various degrees of detectability. Apply common sense "reality checks" before assuming a message is valid.
- If you think the importance of a message justifies it, immediately
reply briefly to an e-mail message to let the sender know you got it, even if you will send a longer reply later.
- "Reasonable" expectations for conduct via e-mail depend on your
relationship to a person and the context of the communication. Norms learned in a particular e-mail environment may not apply in general to your e-mail communication with people across the Internet. Be careful with slang or local acronyms.
- The cost of delivering an e-mail message is, on the average, paid
about equally by the sender and the recipient (or their organizations). This is unlike other media such as physical mail, telephone, TV, or radio. Sending someone mail may also cost them in other specific ways like network bandwidth, disk space or CPU usage. This is a fundamental economic reason why unsolicited e-mail advertising is unwelcome (and is forbidden in many contexts).
- Know how large a message you are sending. Including large files
such as Postscript files or programs may make your message so large that it cannot be delivered or at least consumes excessive resources. A good rule of thumb would be not to send a file larger than 50 Kilobytes. Consider file transfer as an alternative, or cutting the file into smaller chunks and sending each as a separate message.
- Don't send large amounts of unsolicited information to people.

- If your mail system allows you to forward mail, beware the dreaded

forwarding loop. Be sure you haven't set up forwarding on several hosts so that a message sent to you gets into an endless loop from one computer to the next to the next.

2.1.2 For talk:

----

Questa la rimuovo perché non attinente

-- CarloFusco

3.0 One-to-Many Communication (Mailing Lists, ?NetNews)

Any time you engage in One-to-Many communications, all the rules for mail should also apply. After all, communicating with many people via one mail message or post is quite analogous to communicating with one person with the exception of possibly offending a great many more people than in one-to-one communication. Therefore, it's quite important to know as much as you can about the audience of your message.

3.1 User Guidelines

3.1.1 General Guidelines for mailing lists and ?NetNews

- Read both mailing lists and newsgroups for one to two months before
you post anything. This helps you to get an understanding of the culture of the group.
- Do not blame the system administrator for the behavior of the
system users.
- Consider that a large audience will see your posts.
That may include your present or your next boss. Take care in what you write. Remember too, that mailing lists and Newsgroups are frequently archived, and that your words may be

stored for a very long time in a place to which many people have access.

- Assume that individuals speak for themselves, and what they
say does not represent their organization (unless stated explicitly).
- Remember that both mail and news take system resources. Pay
attention to any specific rules covering their uses your organization may have.
- Messages and articles should be brief and to the point. Don't
wander off-topic, don't ramble and don't send mail or post messages solely to point out other people's errors in typing or spelling. These, more than any other behavior, mark you as an immature beginner.
- Subject lines should follow the conventions of the group.

- Forgeries and spoofing are not approved behavior.

- Advertising is welcomed on some lists and Newsgroups, and abhorred

on others! This is another example of knowing your audience before you post. Unsolicited advertising which is completely off-topic will most certainly guarantee that you get a lot of hate mail.
- If you are sending a reply to a message or a posting be sure you
summarize the original at the top of the message, or include just enough text of the original to give a context. This will make sure readers understand when they start to read your response. Since ?NetNews, especially, is proliferated by distributing the postings from one host to another, it is possible to see a response to a message before seeing the original. Giving context helps everyone. But do not include the entire original!
- Again, be sure to have a signature which you attach to your
message. This will guarantee that any peculiarities of mailers or newsreaders which strip header information will not delete the only reference in the message of how people may reach you.
- Be careful when you reply to messages or postings. Frequently
replies are sent back to the address which originated the post - which in many cases is the address of a list or group! You may accidentally send a personal response to a great many people, embarrassing all involved. It's best to type in the address instead of relying on "reply."
- Delivery receipts, non-delivery notices, and vacation programs
are neither totally standardized nor totally reliable across the range of systems connected to Internet mail. They are invasive when sent to mailing lists, and some people consider delivery receipts an invasion of privacy. In short, do not use them.
- If you find a personal message has gone to a list or group, send
an apology to the person and to the group.
- If you should find yourself in a disagreement with one person,
make your responses to each other via mail rather than continue to send messages to the list or the group. If you are debating a point on which the group might have some interest, you may summarize for them later.
- Don't get involved in flame wars. Neither post nor respond
to incendiary material.
- Avoid sending messages or posting articles which are no more than
gratuitous replies to replies.
- Be careful with monospacing fonts and diagrams. These will
display differently on different systems, and with different mailers on the same system.
- There are Newsgroups and Mailing Lists which discuss topics
of wide varieties of interests. These represent a diversity of lifestyles, religions, and cultures. Posting articles or sending messages to a group whose point of view is offensive to you simply to tell them they are offensive is not acceptable. Sexually and racially harassing messages may also have legal implications. There is software available to filter items you might find objectionable.

3.1.2 Mailing List Guidelines

There are several ways to find information about what mailing lists exist on the Internet and how to join them. Make sure you understand your organization's policy about joining these lists and posting to them. In general it is always better to check local resources first before trying to find information via the Internet. Nevertheless, there are a set of files posted periodically to news.answers which list the Internet mailing lists and how to subscribe to them. This is an invaluable resource for finding lists on any topic. See also references [9,13,15] in the Selected Bibliography.
- Send subscribe and unsubscribe messages to the appropriate
address. Although some mailing list software is smart enough

to catch these, not all can ferret these out. It is your responsibility to learn how the lists work, and to send the correct mail to the correct place. Although many many mailing lists adhere to the convention of having a "-request" alias for sending subscribe and unsubscribe messages, not all do. Be sure you know the conventions used by the lists to which you subscribe.

- Save the subscription messages for any lists you join. These
usually tell you how to unsubscribe as well.
- In general, it's not possible to retrieve messages once you have
sent them. Even your system administrator will not be able to get a message back once you have sent it. This means you must make sure you really want the message to go as you have written it.
- The auto-reply feature of many mailers is useful for in-house
communication, but quite annoying when sent to entire mailing lists. Examine "Reply-To" addresses when replying to messages from lists. Most auto-replys will go to all members of the list.
- Don't send large files to mailing lists when Uniform
Resource Locators (URLs) or pointers to ftp-able versions will do. If you want to send it as multiple files, be sure to follow the culture of the group. If you don't know what that is, ask.
- Consider unsubscribing or setting a "nomail" option (when it's
available) when you cannot check your mail for an extended period.
- When sending a message to more than one mailing list, especially
if the lists are closely related, apologize for cross-posting.
- If you ask a question, be sure to post a summary. When doing so,
truly summarize rather than send a cumulation of the messages you receive.
- Some mailing lists are private. Do not send mail to these lists
uninvited. Do not report mail from these lists to a wider audience.
- If you are caught in an argument, keep the discussion focused on
issues rather than the personalities involved.

3.1.3 ?NetNews Guidelines

?NetNews is a globally distributed system which allows people to communicate on topics of specific interest. It is divided into hierarchies, with the major divisions being: sci - science related discussions; comp - computer related discussions; news - for discussions which center around ?NetNews itself; rec - recreational activities; soc - social issues; talk - long-winded never-ending discussions; biz - business related postings; and alt - the alternate hierarchy. Alt is so named because creating an alt group does not go through the same process as creating a group in the other parts of the hierarchy. There are also regional hierarchies, hierarchies which are widely distributed such as Bionet, and your place of business may have its own groups as well. Recently, a "humanities" hierarchy was added, and as time goes on its likely more will be added. For longer discussions on News see references [2,8,22,23] in the Selected Bibliography.
- In ?NetNews parlance, "Posting" refers to posting a new article
to a group, or responding to a post someone else has posted. "Cross-Posting" refers to posting a message to more than one group. If you introduce Cross-Posting to a group, or if you direct "Followup-To:" in the header of your posting, warn readers! Readers will usually assume that the message was posted to a specific group and that followups will go to that group. Headers change this behavior.
- Read all of a discussion in progress (we call this a thread)
before posting replies. Avoid posting "Me Too" messages, where content is limited to agreement with previous posts. Content of a follow-up post should exceed quoted content.
- Send mail when an answer to a question is for one person only.
Remember that News has global distribution and the whole world probably is NOT interested in a personal response. However, don't hesitate to post when something will be of general interest to the Newsgroup participants.
- Check the "Distribution" section of the header, but don't
depend on it. Due to the complex method by which News is delivered, Distribution headers are unreliable. But, if you are posting something which will be of interest to a limited number or readers, use a distribution line that attempts to limit the distribution of your article to those people. For example, set the Distribution to be "nj" if you are posting an article that will be of interest only to New Jersey readers.
- If you feel an article will be of interest to more than one
Newsgroup, be sure to CROSSPOST the article rather than individually post it to those groups. In general, probably only five-to-six groups will have similar enough interests to warrant this.
- Consider using Reference sources (Computer Manuals, Newspapers,
help files) before posting a question. Asking a Newsgroup where answers are readily available elsewhere generates grumpy "RTFM" (read the fine manual - although a more vulgar meaning of the word beginning with "f" is usually implied) messages.
- Although there are Newsgroups which welcome advertising,
in general it is considered nothing less than criminal to advertise off-topic products. Sending an advertisement to each and every group will pretty much guarantee your loss of connectivity.
- If you discover an error in your post, cancel it as soon as
possible.
- DO NOT attempt to cancel any articles but your own. Contact
your administrator if you don't know how to cancel your post, or if some other post, such as a chain letter, needs canceling.
- If you've posted something and don't see it immediately,
don't assume it's failed and re-post it.
- Some groups permit (and some welcome) posts which in other
circumstances would be considered to be in questionable taste. Still, there is no guarantee that all people reading the group will appreciate the material as much as you do. Use the Rotate utility (which rotates all the characters in your post by 13 positions in the alphabet) to avoid giving offense. The Rot13 utility for Unix is an example.
- In groups which discuss movies or books it is considered essential
to mark posts which disclose significant content as "Spoilers". Put this word in your Subject: line. You may add blank lines to the beginning of your post to keep content out of sight, or you may Rotate it.
- Forging of news articles is generally censured. You can protect
yourself from forgeries by using software which generates a manipulation detection "fingerprint", such as PGP (in the US).
- Postings via anonymous servers are accepted in some Newsgroups
and disliked in others. Material which is inappropriate when posted under one's own name is still inappropriate when posted

anonymously.

- Expect a slight delay in seeing your post when posting to a
moderated group. The moderator may change your subject line to have your post conform to a particular thread.
- Don't get involved in flame wars. Neither post nor respond
to incendiary material.

3.2 Administrator Guidelines

3.2.1 General Issues

- Clarify any policies your site has regarding its subscription
to ?NetNews groups and about subscribing to mailing lists.
- Clarify any policies your site has about posting to ?NetNews
groups or to mailing lists, including use of disclaimers in .sigs.
- Clarify and publicize archive policy. (How long are articles
kept?)
- Investigate accusations about your users promptly and with an
open mind.
- Be sure to monitor the health of your system.

- Consider how long to archive system logs, and publicize your

policy on logging.

3.2.2 Mailing Lists

- Keep mailing lists up to date to avoid the "bouncing mail" problem.

- Help list owners when problems arise.

- Inform list owners of any maintenance windows or planned downtime.

- Be sure to have "-request" aliases for list subscription and

administration.
- Make sure all mail gateways operate smoothly.

3.2.3. ?NetNews

- Publicize the nature of the feed you receive. If you do not get
a full feed, people may want to know why not.
- Be aware that the multiplicity of News Reader clients may cause
the News Server being blamed for problems in the clients.
- Honor requests from users immediately if they request cancellation
of their own posts or invalid posts, such as chain letters.
- Have "Usenet", "Netnews" and "News" aliased and make sure someone
reads the mail.

3.3 Moderator Guidelines

3.3.1 General Guidelines

- Make sure your Frequestly Asked Questions (FAQ) is posted at
regular intervals. Include your guidelines for articles/messages. If you are not the FAQ maintainer, make sure they do so.
- Make sure you maintain a good welcome message, which contains
subscribe and unsubscribe information.
- Newsgroups should have their charter/guidelines posted
regularly.
- Keep mailing lists and Newsgroups up to date. Post
messages in a timely fashion. Designate a substitute when you go on vacation or out of town.

4.0 Information Services (Gopher, Wais, WWW, ftp, telnet)

---- 
anche qui, megasnippone. La bibliografia va anche rifatta.

-- CarloFusco

1.1. Introduzione

In passato le persone che utilizzavano Internet sono "cresciute" con la Rete, consapevoli degli aspetti tecnici della trasmissione dei dati. Oggi nella comunità di utilizzatori di Internet ci sono persone "nuove" a questo ambiente. Questi "niubbi" non hanno familiarità con la cultura della rete, e non hanno alcun bisogno di conoscere cose come i protocolli di trasmissione. Questa Guida offre un insieme minimo di comportamenti, che ciascuno potrà adattare alle proprie necessità, per guidare rapidamente i "niubbi" nella cultura della Rete.

La "Netiquette" è un insieme di regole, usi e consuetudini, più o meno codificate, adottate da chi utilizza la rete ("net") per comunicare con altre persone in modo educato ("etiquette").

Nei "luoghi telematici" ogni regolamento ha il sapore di un obbligo formale che limita la grande libertà di espressione che questo mezzo consente. Seguire le regole della netiquette, però, non è una questione formale, ma sostanziale. La comunicazione telematica ha l'immediatezza del colloquio diretto, ma manca di molti aspetti di comunicazione "non-verbale", e bisogna fare ogni sforzo per tentare di rendere il proprio messaggio chiaro e facilmente comprensibile; questo non solo dal punto di vista dei contenuti, ma anche dello stile, che deve garantire la massima chiarezza possibile. Quasi tutte le regole della netiquette hanno lo scopo di semplificare la comprensione dei messaggi. Non si tratta quindi di rispetto di regole astratte, di aderenza a norme formali a scapito dei contenuti: invece, è proprio per esaltare tali contenuti che è bene cercare di garantire con un po' di sforzo la massima intellegibilità del messaggio. Gli utenti devono rendersi conto che, sia che abbiano un accesso personale tramite un contratto privato con un Internet Service Provider (ISP), sia che si connettano da un computer di una Università o di una Azienda, ciascuna di queste entità avrà anche delle proprie regole che stabiliscono proprietà e responsabilità per la posta elettronica e i files, cosa è lecito inviare, come è opportuno presentarsi: bisogna perciò informarsi presso l'autorità locale su tali eventuali regolamenti.

Le modalità di comunicazione su Internet sono molte, e differenti ma qui ci occuperemo solo della Posta Elettronica (e-mail), un tipo di comunicazione "uno a uno" (cioè "da uno a un'altro"), e delle News, un tipo di comunicazione "da uno a molti".

----
Non so bene come tradurre one-to-one. "Uno a uno" è chiaro per me, ma mi 
chiedo se sia chiaro anche per un niubbo. E "da uno a un'altro" mi sembra 
un po' pesante: insomma, tipico "stile italiano" di fronte all'asciutto 
"stile inglese".
E dire "comunicazione diretta tra due persone"? E' un po' più lungo, ma credo renda l'idea.
...

1.2. Posta Elettronica (da uno a un'altro)

----
Io aggiungerei anche che in Usenet e' necessario farsi capire, ma non e' 
necessario usare il linguaggio da sms, ovvero il linguaggio frettoloso che 
cambia il "ch" in "k", che salta molte lettere in modo da rendere lo 
scritto al limite dell'incomprensibile.Si puo' scrivere con le abbreviazioni 
ormai codificate dall'uso, che tutti conosciamo, ma non rendiamo i messaggi 
dei testi crittati.
Aggiungerei anche, vista l'invasione di troll su molti news groups,la regola, 
rivolta ai frequentatori abituali del ng, del non rispondere alle provocazioni, 
ignorando i crosspost ed evitando di creare dei threads. Questo significherebbe 
meno OT , sicuramente meno flames e meno maleducazione.
...

1.3. nota sul significato delle RFC e la loro autorevolezza

Le RFC, ovvero Request For Comments, sono dei documenti di natura tecnica e organizzativa che riguardano Internet. Esistono varie categorie nella quale essi vengono catalogati tra le quali la più importante è certamente l'Internet Standard, ovvero come i software che utilizzino l'Internet Protocol debbano operare affinché sia garantito il buon fuzionamento del servizio di cui essi sono parte.

Ad esempio, il servizio di posta elettronica viene garantito da una suite di programmi che in ultima analisi opera sulla stessa struttura dati: il messaggio internet, ovvero un testo in formato elettronico che viene ad esser scambiato tra mittente ed il suo o i suoi destinatari. Questi programmi sono oggi basati sulla RFC 2822 per le specifiche su come questo testo debba essere strutturato e sulla RFC 2821 sulle procedure e le convenzioni stipulate affinché il messaggio venga scambiato in maniera corretta e affidabile.

Lo status di standard viene raggiunto attraverso un processo a varie fasi di revisione, chiamato "Standard Track", che serve a determinarne il suo progressivo stato di maturità, ovvero la stato di sviluppo, test e diffusione delle specifiche proposte. Esiste dunque il "Proposed Standard" che avendo attraversato una adeguta fase di revisione, suscita abbastanza interesse e gode di un sufficiente consenso, ma non necessita strettamente di implementazioni pratiche. Poi subito sopra c'è Il "Draft Standard" che richiede almeno due diverse implementazioni software totalmente interoperabili dello standard. Infine quando l'esperienza sul campo dimostra l'assoluta sffidabilità del Draft questo diventa finalmente un "Internet Standard" ed il documento che lo descrive cambia nome da RFC a STD.

Data la diffusione e l'omogeneità delle implementazioni software ragiunte dalle suite di programmi che costituiscono un Servizio descritto da uno Standard Internet, non seguire i consgli del STD porterà certamente a gravi e imprevedibili problemi operativi del servizio sul quale si cerca di operare. Questa considerazione probabilmente vale anche per un Draft o un Proposed Standard, sebbene infatti questi documenti godano di una inferiore esperienza sul campo, il loro livello di revisione e la loro diffusione è sufficiente a prevedere che un software non conforme, a meno di validissime e documentabili ragioni che dovrebbero quindi portare ad una revisione della RFC, porterà problemi più o meno gravi di interoperabilità del servizio su cui ci si basa.

Assieme alle RFC incanalate sui binari che devono portare ad un Iternet Standard, esistono documenti che hanno altri scopi e per questo vengono etichettati con un livello di maturità diverso, ovvero "Experimental", "Informational" e "Historic". Ad esempio la RFC 1855, la così detta Netiqutte, rientra nella categoria "Informational". Ora tale RFC non descrive come un software di una certa suite che opera su un dato servizio Internet debba funzionare, ma piuttosto come gli utenti di tal software debbano comportarsi affinché, a giudizio del suo autore, ci sia un beneficio comune tra tutti gli utilizzatori di quel servizio. Un comportamento non conforme quindi non porta certamente a problemi di interoperabilità e tutto quello che può accadere nel caso della RFC 1855 è che si suscitino le ire di alcuni utenti di quel servizio. Inoltre non essendo questi documenti il prodotto di un processo che garantisca un ampio e ben provato consenso, come per quelli in "Standard Track, le consenguenze di un comportamento non conforme sono certamente molto variabili. Ad esempio, nel caso precedente se e quanti utenti potrebbero infuriarsi dipende da quanto strettamente la RFC 1855 descriva bene una situazione di consenso generale e rispecchi adeguatamente la realtà dei tempi.

Ora, la RFC 1855 discutibilmente descriveva delle pratiche di comunicazione su Internet di largo consenso, ma certamente con i suoi 9 anni d'età essa nel suo complesso non è più attuale. Occorre una revisione che descriva qual è il consenso generale sul comportamento in Rete da tenere per un comune beneficio. In mancanza di una RFC, questo documento ha l'ambizione di colmare questa lacuna, almeno per quanto riguarda Usenet ed il servizio email.

1.4. Bibliografia

• RFC 2026, The Internet Standards Process ftp://ftp.isi.edu/in-notes/rfc2026.txt

• RFC 1855 / FYI 28 Documento ufficiale della Internet Society di Sally Hambridge: http://www.ietf.org/rfc/rfc1855.txt

• rfc 1855 in italiano di Roberto Villari: http://www.cgil.it/Cesi/internet/netiquette/rfc1855_it.htm

• Un'altra traduzione della RFC 1855 a cura di Carlo Montangero: http://bertola.eu.org/usenet/faq/testi/retichet.htm

• La netiquette dei newsreader, il GNKSA http://www.newsreaders.com/gnksa/gnksa.txt

• La copia delle netiquette della Registration Autority, da firmare se si registra un dominio: http://www.nic.it/NA/netiquette.txt

• Il libro di Virginia Shea sulla netiquette: http://www.albion.com/netiquette/book/

• La netiquette di Arlene H. Rinaldi: http://www.fau.edu/netiquette/net/

• La traduzione in italiano della netiquette della Rinaldi di Davide Migliavacca: http://www.efluxa.it/netiquette/

• La netiquette su Usenet secondo Spafford, di valore prevalentemente storico: http://www.faqs.org/faqs/usenet/posting-rules/part1/

• Emily Postnews di Brad Templeton: http://www.templetons.com/brad/emily.html

• Emily Postnews nella traduzione di Carlo Maria Chierotti: http://www.chierotti.net/galareteo.php

• Il capitolo 42 del libro "L’umanità dell’internet (le vie della rete sono infinite)" di Giancarlo Livraghi è dedicato alla netiquette: http://www.gandalf.it/uman/capitoli.htm

• No netiquette, un punto di vista alternativo: http://members.xoom.virgilio.it/nonet/index1.htm

EditText of this page (last edited 2006-01-23 20:57:00 by host-84-221-11-125)