KidCode: Naming Conventions for Protecting Children on the World Wide Web and Elsewhere on the Internet Without Censorship
draft-borenstein-kidcode-00

Document Type Expired Internet-Draft (individual)
Last updated 1995-06-05
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-borenstein-kidcode-00.txt

Abstract

This memo suggests a 'KidCode' naming convention to be used to inform web browsing programs when the material being made available on the web is of a nature that might be unsuitable for children. Some aspects of the convention are also applicable to browsing by FTP, to news reading, and to other protocols as well. Two separate conventions are specified. One convention is to be used for fixed URL's, where the permanent URL is itself used to specify the nature of the child-oriented restrictions. Another convention is to be used when the server site desires to use a simpler or pre-existing URL, with restrictions enforced using a naming convention in conjunction with the standard web forms mechanism. A web site or server is said to be KidCode-compliant when it conforms to one of the KidCode naming conventions for all material that might be considered inappropriate for children. A web client or browser is said to be KidCode-compliant when it blocks access to URL's that are labelled as inappropriate using the KidCode naming conventions, or when it offers an easy optional mechanism permitting adults to block children's access in that manner.

Authors

Nathaniel Borenstein (nborenst@us.ibm.com)
Darren New (dnew@sgf.fv.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)