Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 68 views

    Objective: Theory: RFC: To Write About RFC and IETF

    Uploaded by

    Julia West
    Request for Comments (RFCs) were created in 1969 by Steve Crocker to document the development of ARPANET and have become the official record of Internet specifications and standards. The Internet Engineering Task Force (IETF) generates RFCs which are reviewed before publication. The IETF was established in 1986 to coordinate the operation, management and evolution of the Internet in an open standards process.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Objective: Theory: RFC: To Write About RFC and IETF

    Uploaded by

    Julia West
    68 views2 pages
    Request for Comments (RFCs) were created in 1969 by Steve Crocker to document the development of ARPANET and have become the official record of Internet specifications and standards. The Internet Engineering Task Force (IETF) generates RFCs which are reviewed before publication. The IETF was established in 1986 to coordinate the operation, management and evolution of the Internet in an open standards process.

    Original Description:

    This is about RFC and IETF

    Original Title

    Rfc and Ietf

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Request for Comments (RFCs) were created in 1969 by Steve Crocker to document the development of ARPANET and have become the official record of Internet specifications and standards. The Internet Engineering Task Force (IETF) generates RFCs which are reviewed before publication. The IETF was established in 1986 to coordinate the operation, management and evolution of the Internet in an open standards process.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    68 views2 pages

    Objective: Theory: RFC: To Write About RFC and IETF

    Uploaded by

    Julia West
    Request for Comments (RFCs) were created in 1969 by Steve Crocker to document the development of ARPANET and have become the official record of Internet specifications and standards. The Internet Engineering Task Force (IETF) generates RFCs which are reviewed before publication. The IETF was established in 1986 to coordinate the operation, management and evolution of the Internet in an open standards process.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 2

    Objective : To write about RFC and IETF

    Theory :
    RFC
    Request For Comments (RFC's) documents were invented by Steve Crocker in 1969 to
    help record unofficial notes on the development of the ARPANET. They have since become the official
    record for Internet specifications, protocols, procedures, and events.
    Anyone can submit a document to be an RFC, although in practice they are generated by the Internet
    Engineering Task Force, and then reviewed by the IETF groups, various experts, and the RFC Editor
    before publication. An RFC is never updated, although it may be superseded by later revisions. RFC
    2026, The Internet Standards Process -- Revision 3, provides a good description of the Internet
    standards development process, and is updated by RFC 3932, The IESG and RFC Editor Documents:
    Procedures.

    History
    In 1968, as the ARPANET program progressed, representatives from various DARPA sites began to meet
    regularly to progress their plans. As more and more people began to attend, they named themselves the
    Network Working Group (NWG), although the group had no formal charter, membership, or
    organization -- laying the foundation for later formation of similar Internet bodies like the IETF. Steve
    Crocker volunteered to organize the NWG notes. At an ARPA meeting in March, 1969 in Utah, Crocker
    created the first Request For Comments document, titled "Host Software", RFC 001, to document the
    work of the NWG. (Crocker is also known for development of the first ARPANET network protocol,
    the Network Control Program.)
    The RFC's turned out to provide a convenient, useful vehicle for documentation and distribution of the
    research performed by the developers of the Internet, and ended up becoming the official record of the
    Internet's design decisions, architecture, and technical standards. Although they remained titled
    "Request For Comments", by consensus they are the Internet documents of record, and often include
    very detailed technical information.

    How To Use Request For Comments (RFC's)


    Several sites store RFC's in convenient hyperlinked web indexes, described below. Typically, these
    indexes enable you to enter an RFC number and retrieve a copy of the RFC. Some include keyword
    search, global listing, and other capabilities.

    When RFC's are updated they are given a new RFC number. SunSITE includes links in each document to
    older RFC's as well as to newer RFC's, and the official RFC-Editor site includes old and new links in search
    engine listings. These links enable you to go backward and forward in time -- you can read the earliest
    RFC's on a subject, and then move forward to read the later RFC's. Some RFC's replace more than one
    predecessor and unify the documentation on a subject, and some RFC's are replaced by several
    successors as a protocol breaks into two or more related technologies.

    IETF
    The IETF is an open international community of network designers, operators, vendors and researchers
    concerned with the evolution of the Internet architecture and the smooth operation of the Internet.
    The IETF was established in 1986 to coordinate the operation, management and evolution of the
    Internet. It is overseen by the Internet Architecture Board (IAB) and receives administrative
    support from the Internet Society (ISOC). This arrangement was formalized in 2005 as the IETF
    Administrative Support Activity (IASA).
    It is an open standards organization, with no formal membership or membership requirements. It
    started out as a US federal government organization, and today it operates as a non-commercial not-forprofit non-governmental organization. The work of the IETF takes place in more than 100 working
    groups, and all decisions are made on the basis of "rough consensus and running code".
    The IETF is responsible for the management and development of the Internet Protocol Suite, which
    includes the Transmission Control Protocol (TCP) and the Internet Protocol (IP). This role, which is
    overseen by the IESG, includes designating IP address ranges for specific purposes (including multicast,
    documentation, experimental use and general distribution to Internet users); IANA is responsible for
    carrying out the allocation and assignment of IP addresses according to the IETF's instructions.

    History
    The first IETF meeting was on January 16, 1986, consisting of 21 U.S.-government-funded researchers. It
    was a continuation of the work of the earlier GADS Task Force.
    Initially, it met quarterly, but from 1991, it has been meeting 3 times a year. Representatives from nongovernmental entities were invited starting with the fourth IETF meeting, during October of that year.
    Since that time all IETF meetings have been open to the public. The majority of the IETF's work is done
    on mailing lists, and meeting attendance is not required for contributors.

    You might also like