22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Generally, Internet standards define interoperability of systems on the Internet by<br />

defining protocols, message formats, schemas, and languages. The most<br />

fundamental of the standards are the ones defining the Internet protocol (IP).<br />

All Internet standards are given a number in the STD series. The first document<br />

in this series, STD 1, describes the remaining documents in the series, and has a<br />

list of proposed standards. Often, documents in the STD series are copies of<br />

RFCs or are a few RFCs collected together. STD numbers do not have version<br />

numbers since all updates are made via RFCs and the RFC numbers are unique.<br />

To clearly specify which version of a standard one is referring to, the standard<br />

number and all of the RFCs which it includes should be stated.<br />

Request for comment (RFC)<br />

Requests for comments (RFCs) are a series, begun in 1969, of numbered<br />

Internet informational documents and standards widely followed by commercial<br />

software and freeware developers in the Internet and UNIX communities. Few<br />

RFCs are standards, but all Internet standards are recorded in RFCs. Perhaps<br />

the single most influential RFC has been RFC 822, the Internet electronic mail<br />

(e-mail) format standard.<br />

The RFCs issued by the IETF and its predecessors are the most well-known<br />

series named “RFCs”; this series is almost always what is meant by RFC without<br />

further qualification. However, other organizations have, in the past, also issued<br />

series called RFCs.<br />

The RFCs are unusual in that they are floated by technical experts acting on their<br />

own initiative and reviewed by the Internet at large, rather than being formally<br />

promulgated through an institution such as ANSI. For this reason, they remain<br />

known as RFCs even once adopted as standards. This tradition of pragmatic,<br />

experience-driven, after-the-fact standard writing done by individuals or small<br />

working groups has important advantages over the more formal,<br />

committee-driven process. Emblematic of some of these advantages is the<br />

existence of a flourishing tradition of “joke” RFCs. Usually at least one a year is<br />

published, usually on April Fool's Day.<br />

The RFCs are most remarkable for how well they work; they manage to have<br />

neither the ambiguities that are usually rife in informal specifications, nor the<br />

committee-perpetrated misfeatures that often haunt formal standards, and they<br />

define a network that has grown to truly worldwide proportions.<br />

Accessing STDs and RFCs<br />

STDs and RFCs are available publicly and online. The easiest way to obtain<br />

them is from the IETF Web site at the following URL:<br />

http://www.ietf.org<br />

Chapter 6. Public key infrastructures 231

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!