Internet-Draft The New Webiquette May 2022
Kate Expires 27 November 2022 [Page]
Workgroup:
Internet Engineering Task Force
Internet-Draft:
draft-kate-the-new-webiquette-00
Published:
Intended Status:
Informational
Expires:
Author:
K. Kate, Ed.

The New Webiquette

Abstract

The inspiration for this document came from RFC 1855 ("Netiquette"), which is now partially obsolete and no longer maintained. A lot has happened on the Internet since then (social media, video conferencing, deepfakes, ad networks), which should be applied in a netiquette. Like in RFC 1855 this is only a minimal standard.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 27 November 2022.

Table of Contents

1. Introduction

A Webiquette to make the internet a better place.

1.1. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

2. Status of the Memo

This memo does not specify an Internet standard of any kind.

3. User Guidelines"

For making the Internet a place where many people feel comfortable, it needs some rules. What you can do in particular as a regular user can be found in section 1.1 to 1.4.

4. One-to-One-Messaging

We are talking about a direct conversation with a person (in writing). This can be via email, chat, private message in social media or similar.

5. One-to-Many-Messaging

This can represent a conversation with several participants via mail, mailing lists, chat, forum, microblogging services, social media or similar. All rules from One-to-One Messaging also appear to One-to-Many Messaging but One-to-Many also includes:

6. Videoconferences

Video conferencing has become an integral part of our daily lives, so it's important that we use courtesies here as well.

7. The Internet Use in General

8. Admin Guidelines

9. IANA Considerations

This memo includes no request to IANA.

10. Security Considerations

Security issues are not part of this memo.

11. References

11.1. Normative References

[RFC1855]
Hambridge, S., "Netiquette Guidelines", FYI 28, RFC 1855, DOI 10.17487/RFC1855, , <https://www.rfc-editor.org/info/rfc1855>.
[RFC0760]
Postel, J., "DoD standard Internet Protocol", RFC 760, DOI 10.17487/RFC0760, , <https://www.rfc-editor.org/info/rfc760>.
[RFC0791]
Postel, J., "Internet Protocol", STD 5, RFC 791, DOI 10.17487/RFC0791, , <https://www.rfc-editor.org/info/rfc791>.
[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.

Acknowledgements

I thank my beloved coffee machine for providing me with magic potion while writing.

Author's Address

Kate (editor)
Germany