@TECHREPORT{rfc31,
AUTHOR="D. Bobrow and William R. Sutherland",
TITLE="Binary Message Forms in Computer",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=31,
PAGES=7,
DAYS=15,
MONTH=feb,
YEAR=1968,
ABSTRACT="Suggest alternative approaches and methods for describing
messages.",
URL="http://www.rfc-editor.org/rfc/rfc31.txt"
}

@TECHREPORT{rfc1,
AUTHOR="S. D. Crocker",
TITLE="Host Software",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1,
PAGES=11,
DAYS=15,
MONTH=apr,
YEAR=1969,
ABSTRACT="Discusses the Host software and initial experiments on the
ARPA Network.",
URL="http://www.rfc-editor.org/rfc/rfc1.txt"
}

@TECHREPORT{rfc11,
AUTHOR="G. Deloche",
TITLE="Implementation of the {Host-Host} software procedures in {GORDO}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=11,
DAYS=15,
MONTH=aug,
YEAR=1969,
ABSTRACT="Discussion of Host-Host Procedures and GORDO as a time-sharing
system that was implemented on a SDS Sigma 7."
}

@TECHREPORT{rfc12,
AUTHOR="M. Wingfield",
TITLE="{IMP-Host} interface flow diagrams",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=12,
PAGES=1,
DAYS=15,
MONTH=aug,
YEAR=1969,
ABSTRACT="Flow Diagrams Flow diagrams that indicate the logical sequence
of hardware operations which occur within the IMP-HOST interface.",
URL="http://www.rfc-editor.org/rfc/rfc12.txt"
}

@TECHREPORT{rfc13,
AUTHOR="V. G. Cerf",
TITLE="Zero Text Length {EOF} Message",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=13,
PAGES=1,
DAYS=15,
MONTH=aug,
YEAR=1969,
ABSTRACT="Proposes a zero text length EOF (End-Of-File) message.",
URL="http://www.rfc-editor.org/rfc/rfc13.txt"
}

@TECHREPORT{rfc15,
AUTHOR="C. S. Carr",
TITLE="Network subsystem for time sharing hosts",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=15,
PAGES=5,
DAYS=15,
MONTH=sep,
YEAR=1969,
ABSTRACT={Proposes a subsystem called {"}Telnet{"}, which would be a shell
program around the network system primitives, allowing a teletype or
similar terminal at a remote host to function as a teletype at the
serving host.},
URL="http://www.rfc-editor.org/rfc/rfc15.txt"
}

@TECHREPORT{rfc16,
AUTHOR="S. D. Crocker",
TITLE="{M.I.T}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=16,
PAGES=1,
DAYS=15,
MONTH=aug,
YEAR=1969,
ABSTRACT="Announcement that MIT is now to receive all Network Working
Group memos.",
URL="http://www.rfc-editor.org/rfc/rfc16.txt"
}

@TECHREPORT{rfc17,
AUTHOR="J. E. Kreznar",
TITLE="Some questions re: {Host-IMP} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=17,
PAGES=4,
DAYS=15,
MONTH=aug,
YEAR=1969,
ABSTRACT="Queries and opinions regarding the HOST-IMP Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc17.txt"
}

@TECHREPORT{rfc18,
AUTHOR="V. G. Cerf",
TITLE="{IMP-IMP} and {HOST-HOST} Control Links",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=18,
PAGES=1,
DAYS=15,
MONTH=sep,
YEAR=1969,
ABSTRACT="Suggestions regarding the Host-Host control link. 017a
Comments in response to Kreznar's questions which were raised in RFC 17.",
URL="http://www.rfc-editor.org/rfc/rfc18.txt"
}

@TECHREPORT{rfc19,
AUTHOR="J. E. Kreznar",
TITLE="Two protocol suggestions to reduce congestion at swap bound nodes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=19,
PAGES=2,
DAYS=15,
MONTH=oct,
YEAR=1969,
ABSTRACT="Suggests alternatives in reducing congestion at swap-bound
nodes.",
URL="http://www.rfc-editor.org/rfc/rfc19.txt"
}

@TECHREPORT{rfc20,
AUTHOR="V. G. Cerf",
TITLE="{ASCII} format for network interchange",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=20,
PAGES=9,
DAYS=15,
MONTH=oct,
YEAR=1969,
ABSTRACT="Discusses the use of standard 7-bit ASCII embedded in an 8-bit
byte whose high order bit is always 1.",
URL="http://www.rfc-editor.org/rfc/rfc20.txt"
}

@TECHREPORT{rfc21,
AUTHOR="V. G. Cerf",
TITLE="Network meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=21,
DAYS=15,
MONTH=oct,
YEAR=1969,
ABSTRACT="Attendance list and topics discussed.",
URL="http://www.rfc-editor.org/rfc/rfc21.txt"
}

@TECHREPORT{rfc22,
AUTHOR="V. G. Cerf",
TITLE="Host-host control message formats",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=22,
PAGES=2,
DAYS=15,
MONTH=oct,
YEAR=1969,
ABSTRACT="Reports on a new control message format which does not use the
7-bit ASCII character mode of transmission.",
URL="http://www.rfc-editor.org/rfc/rfc22.txt"
}

@TECHREPORT{rfc23,
AUTHOR="G. Gregg",
TITLE="Transmission of Multiple Control Messages",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=23,
DAYS=15,
MONTH=oct,
YEAR=1969,
ABSTRACT="Discusses how a network program at a site should be prepared
to send or receive more than one control message in a single control
communication.",
URL="http://www.rfc-editor.org/rfc/rfc23.txt"
}

@TECHREPORT{rfc25,
AUTHOR="S. D. Crocker",
TITLE="No High Link Numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=25,
DAYS=15,
MONTH=oct,
YEAR=1969,
ABSTRACT="Suggests that no link number over 63 be used.",
URL="http://www.rfc-editor.org/rfc/rfc25.txt"
}

@TECHREPORT{rfc3,
AUTHOR="S. D. Crocker",
TITLE="Documentation conventions",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=3,
DAYS=15,
MONTH=apr,
YEAR=1969,
ABSTRACT="Establishes a definition of style, content, form, and
distribution of the Network Working Group's notes (Obsoleted by RFC 10).",
URL="http://www.rfc-editor.org/rfc/rfc3.txt"
}

@TECHREPORT{rfc4,
AUTHOR="Ehud Shapiro",
TITLE="Network timetable",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=4,
PAGES=6,
DAYS=15,
MONTH=mar,
YEAR=1969,
ABSTRACT="Discusses installation, configuration, network checkout, and
test messages run between SRI and UCLA.",
URL="http://www.rfc-editor.org/rfc/rfc4.txt"
}

@TECHREPORT{rfc5,
AUTHOR="J. Rulifson",
TITLE="Decode Encode Language {(DEL)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=5,
DAYS=15,
MONTH=jun,
YEAR=1969,
ABSTRACT="Details the machine independent language DEL (Decode-Encode
Language).",
URL="http://www.rfc-editor.org/rfc/rfc5.txt"
}

@TECHREPORT{rfc6,
AUTHOR="S. D. Crocker",
TITLE="Conversation with Bob Kahn",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=6,
DAYS=15,
MONTH=apr,
YEAR=1969,
ABSTRACT="Conversations regarding code conversion in the IMP's, IMP-HOST
communication, and HOST software.",
URL="http://www.rfc-editor.org/rfc/rfc6.txt"
}

@TECHREPORT{rfc7,
AUTHOR="G. Deloche",
TITLE="{Host-IMP} interface",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=7,
PAGES=7,
DAYS=15,
MONTH=may,
YEAR=1969,
ABSTRACT="Discusses Host-IMP interface issues.",
URL="http://www.rfc-editor.org/rfc/rfc7.txt"
}

@TECHREPORT{rfc8,
AUTHOR="G. Deloche",
TITLE="Functional specifications for the {ARPA} Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=8,
DAYS=15,
MONTH=may,
YEAR=1969,
ABSTRACT="Discusses transmission features, functional software
specifications, and the Link establishment procedure."
}

@TECHREPORT{rfc28,
AUTHOR="W. K. English",
TITLE="Time Standards",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=28,
DAYS=15,
MONTH=jan,
YEAR=1970,
ABSTRACT="Request for comments relative to Network time standards.",
URL="http://www.rfc-editor.org/rfc/rfc28.txt"
}

@TECHREPORT{rfc29,
AUTHOR="R. E. Kahn",
TITLE="Response to {RFC} 28",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=29,
DAYS=15,
MONTH=jan,
YEAR=1970,
ABSTRACT="Comments in response to English's question which was raised in
RFC 28.",
URL="http://www.rfc-editor.org/rfc/rfc29.txt"
}

@TECHREPORT{rfc30,
AUTHOR="S. D. Crocker",
TITLE="Documentation Conventions",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=30,
DAYS=15,
MONTH=feb,
YEAR=1970,
ABSTRACT="Revises the definition of style, content, form, and
distribution of the Network Working Group's notes. Replaces RFCs
10,16,24,27.",
URL="http://www.rfc-editor.org/rfc/rfc30.txt"
}

@TECHREPORT{rfc32,
AUTHOR="J. B. Cole",
TITLE="Some Thoughts on {SRI's} Proposed Real Time Clock",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=32,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1970,
ABSTRACT="References and comments on RFCs 28,29.",
URL="http://www.rfc-editor.org/rfc/rfc32.txt"
}

@TECHREPORT{rfc33,
AUTHOR="S. D. Crocker",
TITLE="New {Host-Host} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=33,
PAGES=19,
DAYS=15,
MONTH=feb,
YEAR=1970,
ABSTRACT="Revises RFC 11, and indicates numerous changes in the old
protocol.",
URL="http://www.rfc-editor.org/rfc/rfc33.txt"
}

@TECHREPORT{rfc34,
AUTHOR="W. K. English",
TITLE="Some Brief Preliminary Notes on the Augmentation Research Center Clock",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=34,
PAGES=2,
DAYS=15,
MONTH=feb,
YEAR=1970,
ABSTRACT="Describes the ARC Clock system.",
URL="http://www.rfc-editor.org/rfc/rfc34.txt"
}

@TECHREPORT{rfc35,
AUTHOR="S. D. Crocker",
TITLE="Network Meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=35,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1970,
ABSTRACT="Announcement of a network meeting: date, time, place, and
proposed agenda.",
URL="http://www.rfc-editor.org/rfc/rfc35.txt"
}

@TECHREPORT{rfc36,
AUTHOR="S. D. Crocker",
TITLE="Protocol Notes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=36,
PAGES=8,
DAYS=15,
MONTH=mar,
YEAR=1970,
ABSTRACT="A three part overview of the Network Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc36.txt"
}

@TECHREPORT{rfc37,
AUTHOR="S. D. Crocker",
TITLE="Network Meeting Epilogue, etc",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=37,
PAGES=5,
DAYS=15,
MONTH=mar,
YEAR=1970,
ABSTRACT="Network Meeting notes from 17 March 1970.",
URL="http://www.rfc-editor.org/rfc/rfc37.txt"
}

@TECHREPORT{rfc38,
AUTHOR="S. M. Wolfe",
TITLE="Comments on Network Protocol from {NWG/RFC} {#36}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=38,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1970,
ABSTRACT="Continued discussion on the proposed Network Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc38.txt"
}

@TECHREPORT{rfc39,
AUTHOR="E. Harslem and John F. Heafner",
TITLE="Comments on Protocol Re: {NWG/RFC} {#36}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=39,
PAGES=3,
DAYS=15,
MONTH=mar,
YEAR=1970,
ABSTRACT="More suggestions to be considered as additions to RFC 36 -
Network Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc39.txt"
}

@TECHREPORT{rfc40,
AUTHOR="E. Harslem and John F. Heafner",
TITLE="More Comments on the Forthcoming Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=40,
PAGES=3,
DAYS=15,
MONTH=mar,
YEAR=1970,
ABSTRACT="Further elaborations on the errors, queries, and Host status
that were mentioned in RFC 39.",
URL="http://www.rfc-editor.org/rfc/rfc40.txt"
}

@TECHREPORT{rfc41,
AUTHOR="J. T. Melvin",
TITLE="{IMP-IMP} Teletype Communication",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=41,
DAYS=15,
MONTH=mar,
YEAR=1970,
ABSTRACT="Comments that transmitting IMP sites should use 24 hour time
and include the time zone designation.",
URL="http://www.rfc-editor.org/rfc/rfc41.txt"
}

@TECHREPORT{rfc42,
AUTHOR="E. Ancona",
TITLE="Message Data Types",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=42,
PAGES=3,
DAYS=15,
MONTH=mar,
YEAR=1970,
ABSTRACT="A proposal that the first eight bits of a normal message be
reserved for a message data type.",
URL="http://www.rfc-editor.org/rfc/rfc42.txt"
}

@TECHREPORT{rfc43,
AUTHOR="A. G. Nemeth",
TITLE="Proposed Meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=43,
DAYS=15,
MONTH=apr,
YEAR=1970,
ABSTRACT="An announcement of a meeting to discuss the Local Interaction
Language system.",
URL="http://www.rfc-editor.org/rfc/rfc43.txt"
}

@TECHREPORT{rfc44,
AUTHOR="A. Shoshani and R. Long and A. Landsberg",
TITLE="Comments on {NWG/RFC} 33 and 36",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=44,
PAGES=3,
DAYS=15,
MONTH=apr,
YEAR=1970,
ABSTRACT="General discussion and suggestions for refinements to the
HOST-HOST Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc44.txt"
}

@TECHREPORT{rfc45,
AUTHOR="J. B. Postel and S. D. Crocker",
TITLE="New Protocol is Coming",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=45,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1970,
ABSTRACT="Announcement of a new version of the Network Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc45.txt"
}

@TECHREPORT{rfc46,
AUTHOR="E. Meyer",
TITLE="{ARPA} Network protocol notes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=46,
PAGES=17,
DAYS=15,
MONTH=apr,
YEAR=1970,
ABSTRACT="Comments and suggestions from the NWG at Project MAC, based
upon the protocol outlined in RFCs 33,36.",
URL="http://www.rfc-editor.org/rfc/rfc46.txt"
}

@TECHREPORT{rfc47,
AUTHOR="J. B. Postel and S. D. Crocker",
TITLE="{BBN's} Comments on {NWG/RFC} {#33}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=47,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1970,
ABSTRACT="Comments from BBN regarding RFC 33 (New HOST-HOST Protocol).",
URL="http://www.rfc-editor.org/rfc/rfc47.txt"
}

@TECHREPORT{rfc48,
AUTHOR="J. B. Postel and S. D. Crocker",
TITLE="Possible protocol plateau",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=48,
PAGES=18,
DAYS=15,
MONTH=apr,
YEAR=1970,
ABSTRACT="Reporting activities since the Network meeting of 17 March
1970.",
URL="http://www.rfc-editor.org/rfc/rfc48.txt"
}

@TECHREPORT{rfc49,
AUTHOR="Edwin W. Meyer",
TITLE="Conversations with {S.} Crocker {(UCLA)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=49,
MONTH=apr,
YEAR=1970,
ABSTRACT="Discussion of telephone conversations relating to the Network
Protocol, specifically regarding Meyer's proposal in RFC 46.",
URL="http://www.rfc-editor.org/rfc/rfc49.txt"
}

@TECHREPORT{rfc50,
AUTHOR="E. Harslen and J. Heafner",
TITLE="Comments on the Meyer Proposal",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=50,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1970,
ABSTRACT="General acceptance on RFC 46, plus comments on the seven
issues raised in RFC 47.",
URL="http://www.rfc-editor.org/rfc/rfc50.txt"
}

@TECHREPORT{rfc51,
AUTHOR="M. Elie",
TITLE="Proposal for a Network Interchange Language",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=51,
DAYS=15,
MONTH=may,
YEAR=1970,
ABSTRACT="A proposal to specify a high level programming language for
computer networks, specifically the ARPA network."
}

@TECHREPORT{rfc52,
AUTHOR="J. B. Postel and S. D. Crocker",
TITLE="Updated distribution list",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=52,
PAGES=3,
DAYS=15,
MONTH=jul,
YEAR=1970,
ABSTRACT="Mailing list for distributing the RFCs.",
URL="http://www.rfc-editor.org/rfc/rfc52.txt"
}

@TECHREPORT{rfc53,
AUTHOR="S. D. Crocker",
TITLE="Official protocol mechanism",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=53,
PAGES=1,
DAYS=15,
MONTH=jun,
YEAR=1970,
ABSTRACT="Group discussion on rules for establishing and modifying an
official Host-Host protocol.",
URL="http://www.rfc-editor.org/rfc/rfc53.txt"
}

@TECHREPORT{rfc54,
AUTHOR="S. D. Crocker and J. B. Postel and J. Newkirk and M. F. Kraley",
TITLE="Official Protocol Proffering",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=54,
PAGES=9,
DAYS=15,
MONTH=jun,
YEAR=1970,
ABSTRACT="Submission of the Official Protocol for comments and
suggestions.",
URL="http://www.rfc-editor.org/rfc/rfc54.txt"
}

@TECHREPORT{rfc55,
AUTHOR="J. Newkirk and M. F. Kraley and J. B. Postel and S. D. Crocker",
TITLE="Prototypical implementation of the {NCP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=55,
PAGES=23,
DAYS=15,
MONTH=jun,
YEAR=1970,
ABSTRACT="A prototypical specification in a prose format of what the NCP
could look like.",
URL="http://www.rfc-editor.org/rfc/rfc55.txt"
}

@TECHREPORT{rfc56,
AUTHOR="E. Belove and D. L. Black and R. Flegal and L. G. Farquar",
TITLE="Third Level Protocol: Logger Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=56,
PAGES=6,
DAYS=15,
MONTH=jun,
YEAR=1970,
ABSTRACT="All explanations in this RFC are meant to describe functional
characteristics rather than design.",
URL="http://www.rfc-editor.org/rfc/rfc56.txt"
}

@TECHREPORT{rfc57,
AUTHOR="M. F. Kraley and J. Newkirk",
TITLE="Thoughts and Reflections on {NWG/RFC} 54",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=57,
PAGES=5,
DAYS=15,
MONTH=jun,
YEAR=1970,
URL="http://www.rfc-editor.org/rfc/rfc57.txt"
}

@TECHREPORT{rfc58,
AUTHOR="T. P. Skinner",
TITLE="Logical Message Synchronization",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=58,
PAGES=2,
DAYS=15,
MONTH=jun,
YEAR=1970,
ABSTRACT="A discussion on a question raised at the last network meeting
regarding the question of logical and physical message distinctions.",
URL="http://www.rfc-editor.org/rfc/rfc58.txt"
}

@TECHREPORT{rfc59,
AUTHOR="E. Meyer",
TITLE="Flow Control - Fixed Versus Demand Allocation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=59,
PAGES=7,
DAYS=15,
MONTH=jun,
YEAR=1970,
ABSTRACT="Discussion of the advantages and disadvantages of the method
of flow control as described in RFC 54.",
URL="http://www.rfc-editor.org/rfc/rfc59.txt"
}

@TECHREPORT{rfc60,
AUTHOR="R. B. Kalin",
TITLE="Simplified {NCP} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=60,
PAGES=8,
DAYS=15,
MONTH=jul,
YEAR=1970,
ABSTRACT="Definition of a new NCP Protocol that is simple enough to be
implemented on a very small computer, yet can be extended for efficient
operation on large timesharing machines.",
URL="http://www.rfc-editor.org/rfc/rfc60.txt"
}

@TECHREPORT{rfc61,
AUTHOR="D. C. Walden",
TITLE="Note on Interprocess Communication in a Resource Sharing Computer Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=61,
PAGES=18,
DAYS=15,
MONTH=jul,
YEAR=1970,
ABSTRACT="A draft request for comments of a resource sharing study that
may be of general interest to network participants.",
URL="http://www.rfc-editor.org/rfc/rfc61.txt"
}

@TECHREPORT{rfc62,
AUTHOR="D. C. Walden",
TITLE="Systems for Interprocess Communication in a Resource Sharing Computer
Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=62,
PAGES=20,
DAYS=15,
MONTH=aug,
YEAR=1970,
ABSTRACT="Supercedes RFC 61.",
URL="http://www.rfc-editor.org/rfc/rfc62.txt"
}

@TECHREPORT{rfc63,
AUTHOR="V. G. Cerf",
TITLE="Belated Network Meeting Report",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=63,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1970,
ABSTRACT="Network meeting report of the Network Working Group from 8 May
70.",
URL="http://www.rfc-editor.org/rfc/rfc63.txt"
}

@TECHREPORT{rfc64,
AUTHOR="M. Elie",
TITLE="Getting rid of marking",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=64,
PAGES=4,
DAYS=15,
MONTH=jul,
YEAR=1970,
ABSTRACT="Suggests simple modifications and solutions to the IMP-HOST
interface which would be a better solution than marking.",
URL="http://www.rfc-editor.org/rfc/rfc64.txt"
}

@TECHREPORT{rfc65,
AUTHOR="D. C. Walden",
TITLE="Comments on {Host/Host} Protocol document {#1}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=65,
PAGES=8,
DAYS=15,
MONTH=aug,
YEAR=1970,
ABSTRACT="Critique and suggestions for improvement of the Host-Host
Protocol document.",
URL="http://www.rfc-editor.org/rfc/rfc65.txt"
}

@TECHREPORT{rfc66,
AUTHOR="S. D. Crocker",
TITLE="{NIC} - third level ideas and other noise",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=66,
PAGES=3,
DAYS=15,
MONTH=aug,
YEAR=1970,
ABSTRACT="Meeting notes from 12 Aug 70 between Crocker and
representatives from BBN and MIT regarding the third level protocol.",
URL="http://www.rfc-editor.org/rfc/rfc66.txt"
}

@TECHREPORT{rfc67,
AUTHOR="William R. Crowther",
TITLE="Proposed Change to {Host/IMP} Spec to Eliminate Marking",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=67,
PAGES=1,
DAYS=15,
MONTH=jan,
YEAR=1970,
ABSTRACT="Proposed change to eliminate marking, per Walden's comments.",
URL="http://www.rfc-editor.org/rfc/rfc67.txt"
}

@TECHREPORT{rfc68,
AUTHOR="M. Elie",
TITLE="Comments on Memory Allocation Control Commands: {CEASE,} {ALL,} {GVB,}
{RET,} and {RFNM}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=68,
PAGES=2,
DAYS=15,
MONTH=aug,
YEAR=1970,
ABSTRACT="Provides a scheme for buffer allocation.",
URL="http://www.rfc-editor.org/rfc/rfc68.txt"
}

@TECHREPORT{rfc69,
AUTHOR="A. K. Bhushan",
TITLE="Distribution List Change for {MIT}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=69,
PAGES=1,
DAYS=15,
MONTH=sep,
YEAR=1970,
ABSTRACT="Announcement of name change.",
URL="http://www.rfc-editor.org/rfc/rfc69.txt"
}

@TECHREPORT{rfc70,
AUTHOR="S. D. Crocker",
TITLE="Note on Padding",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=70,
PAGES=9,
DAYS=15,
MONTH=oct,
YEAR=1970,
ABSTRACT="Discussion of padding on a message.",
URL="http://www.rfc-editor.org/rfc/rfc70.txt"
}

@TECHREPORT{rfc71,
AUTHOR="T. Schipper",
TITLE="Reallocation in Case of Input Error",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=71,
DAYS=15,
MONTH=sep,
YEAR=1970,
ABSTRACT="Discussion of how to resynchronize flow control using a
proposed protocol for the CCN-Host at UCLA.",
URL="http://www.rfc-editor.org/rfc/rfc71.txt"
}

@TECHREPORT{rfc72,
AUTHOR="R. D. Bressler",
TITLE="Proposed Moratorium on Changes to Network Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=72,
PAGES=3,
DAYS=15,
MONTH=sep,
YEAR=1970,
ABSTRACT="Cites critical changes that could occur in hardware/software
development efforts and advanced debugging if changes in the Network
Protocol aren't kept in check.",
URL="http://www.rfc-editor.org/rfc/rfc72.txt"
}

@TECHREPORT{rfc73,
AUTHOR="S. D. Crocker",
TITLE="Response to {NWG/RFC} 67",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=73,
PAGES=1,
DAYS=15,
MONTH=sep,
YEAR=1970,
ABSTRACT="General agreement with proposed policy.",
URL="http://www.rfc-editor.org/rfc/rfc73.txt"
}

@TECHREPORT{rfc74,
AUTHOR="J. A. White",
TITLE="Specifications for network use of the {UCSB} {On-Line} System",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=74,
DAYS=15,
MONTH=oct,
YEAR=1970,
ABSTRACT="Announcement of UCSB's On-Line System (OLS) availability to
ARPA Network users."
}

@TECHREPORT{rfc76,
AUTHOR="J. Bouknight and J. Madden and Gary R. Grossman",
TITLE="Connection by name: User oriented protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=76,
PAGES=15,
DAYS=15,
MONTH=oct,
YEAR=1970,
ABSTRACT="Suggests a user level interface to network protocol where all
user protocol is handled symbolically with system procedures making the
translation into host-to-host protocol. Proposes general solutions.",
URL="http://www.rfc-editor.org/rfc/rfc76.txt"
}

@TECHREPORT{rfc77,
AUTHOR="J. B. Postel",
TITLE="Network meeting report",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=77,
PAGES=9,
DAYS=15,
MONTH=nov,
YEAR=1970,
ABSTRACT="Report on three Network Working Group meetings held during
November 16, 17, and 18.",
URL="http://www.rfc-editor.org/rfc/rfc77.txt"
}

@TECHREPORT{rfc78,
AUTHOR="E. Harslem and John F. Heafner and J. A. White",
TITLE="{NCP} Status Report: {UCSB/Rand}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=78,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1970,
ABSTRACT="Conducted an excercise between UCSB console to/from RAND
console validation of the respective NCPs.",
URL="http://www.rfc-editor.org/rfc/rfc78.txt"
}

@TECHREPORT{rfc79,
AUTHOR="E. Meyer",
TITLE="Logger Protocol error",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=79,
PAGES=1,
DAYS=15,
MONTH=nov,
YEAR=1970,
URL="http://www.rfc-editor.org/rfc/rfc79.txt"
}

@TECHREPORT{rfc80,
AUTHOR="E. Harslem and John F. Heafner",
TITLE="Protocols and Data Formats",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=80,
PAGES=9,
DAYS=15,
MONTH=dec,
YEAR=1970,
ABSTRACT="Proposes general solutions concerning Initial Connection
Protocols, Pre-specificed Data Formats, and Adaptable Mechanisms.",
URL="http://www.rfc-editor.org/rfc/rfc80.txt"
}

@TECHREPORT{rfc81,
AUTHOR="J. Bouknight",
TITLE="Request for Reference Information",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=81,
PAGES=1,
DAYS=15,
MONTH=dec,
YEAR=1970,
ABSTRACT="Request for documents in the subject areas of data
communications and communications theory.",
URL="http://www.rfc-editor.org/rfc/rfc81.txt"
}

@TECHREPORT{rfc82,
AUTHOR="E. Meyer",
TITLE="Network Meeting Notes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=82,
PAGES=18,
DAYS=15,
MONTH=dec,
YEAR=1970,
ABSTRACT="A transcribed summary of the Fall 1970 network meeting notes.",
URL="http://www.rfc-editor.org/rfc/rfc82.txt"
}

@TECHREPORT{rfc83,
AUTHOR="Ross  Anderson and E. Harslem and John F. Heafner",
TITLE="Language-machine for data reconfiguration",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=83,
PAGES=13,
DAYS=15,
MONTH=dec,
YEAR=1970,
ABSTRACT="Describes a syntax-driven interpreter that operates on a
grammar which is an orderd set of replacement rules for the Form
Machine.",
URL="http://www.rfc-editor.org/rfc/rfc83.txt"
}

@TECHREPORT{rfc84,
AUTHOR="J. B. North",
TITLE="List of {NWG/RFC's} {1-80}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=84,
PAGES=8,
DAYS=15,
MONTH=dec,
YEAR=1970,
ABSTRACT="Lists RFCs 1-80.",
URL="http://www.rfc-editor.org/rfc/rfc84.txt"
}

@TECHREPORT{rfc85,
AUTHOR="S. D. Crocker",
TITLE="Network Working Group meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=85,
PAGES=1,
DAYS=15,
MONTH=dec,
YEAR=1970,
ABSTRACT="Announcement of regularly scheduled Network Working Group
Meetings every three months.",
URL="http://www.rfc-editor.org/rfc/rfc85.txt"
}

@TECHREPORT{rfc91,
AUTHOR="G. H. Mealy",
TITLE="Proposed {User-User} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=91,
PAGES=12,
DAYS=15,
MONTH=dec,
YEAR=1970,
ABSTRACT="Discussion of UCLA's Campus Computing Network of services and
implementation priorities.",
URL="http://www.rfc-editor.org/rfc/rfc91.txt"
}

@TECHREPORT{rfc100,
AUTHOR="P. M. Karp",
TITLE="Categorization and guide to {NWG/RFCs}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=100,
PAGES=37,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT="Categorizes, identifies, and summarizes RFCS 1-100.",
URL="http://www.rfc-editor.org/rfc/rfc100.txt"
}

@TECHREPORT{rfc101,
AUTHOR="R. W. Watson",
TITLE="Notes on the Network Working Group meeting, Urbana, Illinois, February
{17,} 1971",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=101,
PAGES=14,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT="Transcript of the Network Working Group Meeting, February
1970.",
URL="http://www.rfc-editor.org/rfc/rfc101.txt"
}

@TECHREPORT{rfc102,
AUTHOR="S. D. Crocker",
TITLE="Output of the {Host-Host} Protocol glitch cleaning committee",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=102,
PAGES=4,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT="Numerous topics were discussed.",
URL="http://www.rfc-editor.org/rfc/rfc102.txt"
}

@TECHREPORT{rfc103,
AUTHOR="R. B. Kalin",
TITLE="Implementation of Interrupt Keys",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=103,
PAGES=4,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT="This paper discusses the problems and solutions that are
simple to implement in the current protocol specifications that contain
serious logical errors in the interrupt functions.",
URL="http://www.rfc-editor.org/rfc/rfc103.txt"
}

@TECHREPORT{rfc104,
AUTHOR="J. B. Postel and S. D. Crocker",
TITLE="Link 191",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=104,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT="General agreement to reserve a link for use in measurements.
Therefore, Link 191 will be assigned for measurement use.",
URL="http://www.rfc-editor.org/rfc/rfc104.txt"
}

@TECHREPORT{rfc105,
AUTHOR="J. A. White",
TITLE="Network Specifications for Remote Job Entry and Remote Job Output Retrieval
at {UCSB}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=105,
PAGES=9,
DAYS=15,
MONTH=mar,
YEAR=1971,
ABSTRACT="Describes the remote job entry service at UCSB.",
URL="http://www.rfc-editor.org/rfc/rfc105.txt"
}

@TECHREPORT{rfc106,
AUTHOR="T. C. O'Sullivan",
TITLE="{User/Server} Site Protocol Network Host Questionnaire",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=106,
PAGES=5,
DAYS=15,
MONTH=mar,
YEAR=1971,
ABSTRACT="An attempt to gather information for creating the Telnet
Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc106.txt"
}

@TECHREPORT{rfc108,
AUTHOR="R. W. Watson",
TITLE="Attendance list at the Urbana {NWG} meeting, February {17-19,} 1971",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=108,
PAGES=2,
DAYS=15,
MONTH=mar,
YEAR=1971,
ABSTRACT="Lists attendees at the NWG meeting held February 1971.",
URL="http://www.rfc-editor.org/rfc/rfc108.txt"
}

@TECHREPORT{rfc109,
AUTHOR="J. M. Winett",
TITLE="Level {III} Server Protocol for the Lincoln Laboratory {NIC} {360/67} Host",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=109,
DAYS=15,
MONTH=mar,
YEAR=1971,
ABSTRACT="Telnet implementation and the 360/67."
}

@TECHREPORT{rfc110,
AUTHOR="J. M. Winett",
TITLE="Conventions for using an {IBM} 2741 terminal as a user console for access
to network server hosts",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=110,
DAYS=15,
MONTH=mar,
YEAR=1971,
ABSTRACT="Telnet implementation and the 2741."
}

@TECHREPORT{rfc111,
AUTHOR="S. D. Crocker",
TITLE="Pressure from the Chairman",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=111,
PAGES=2,
DAYS=15,
MONTH=mar,
YEAR=1971,
ABSTRACT="Proposed scheduling for the implementation of NCPs and
Telnets.",
URL="http://www.rfc-editor.org/rfc/rfc111.txt"
}

@TECHREPORT{rfc112,
AUTHOR="T. C. O'Sullivan",
TITLE="{User/Server} Site Protocol: Network host questionnaire responses",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=112,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="A summary of the responses to the referenced questionnaire."
}

@TECHREPORT{rfc113,
AUTHOR="E. Harslem and John F. Heafner and J. A. White",
TITLE="Network activity report: {UCSB} Rand",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=113,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Report on the network use and validity between UCSB's RJE and
RJOR systems and RAND.",
URL="http://www.rfc-editor.org/rfc/rfc113.txt"
}

@TECHREPORT{rfc114,
AUTHOR="A. K. Bhushan",
TITLE="File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=114,
PAGES=17,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Proposed file transfer mechanisms that have been developed for
immediate implementation on hosts at MIT.",
URL="http://www.rfc-editor.org/rfc/rfc114.txt"
}

@TECHREPORT{rfc115,
AUTHOR="R. W. Watson and J. B. North",
TITLE="Some Network Information Center policies on handling documents",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=115,
PAGES=8,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Discusses current document policies between the Network
Information Center and sites on the network.",
URL="http://www.rfc-editor.org/rfc/rfc115.txt"
}

@TECHREPORT{rfc116,
AUTHOR="S. D. Crocker",
TITLE="Structure of the May {NWG} Meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=116,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Proposed meeting agenda centering around discussions of
advertised topics, with published status reports and position papers.",
URL="http://www.rfc-editor.org/rfc/rfc116.txt"
}

@TECHREPORT{rfc117,
AUTHOR="J. W. Wong",
TITLE="Some comments on the official protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=117,
PAGES=5,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Cites weaknesses in RFC 107, and provides suggestions for
correction and handling.",
URL="http://www.rfc-editor.org/rfc/rfc117.txt"
}

@TECHREPORT{rfc118,
AUTHOR="R. W. Watson",
TITLE="Recommendations for facility documentation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=118,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Cites two classes of information which each site needs to
provide for every service or process it makes available over the ARPA
network.",
URL="http://www.rfc-editor.org/rfc/rfc118.txt"
}

@TECHREPORT{rfc119,
AUTHOR="M. Krilanovich",
TITLE="Network Fortran subprograms",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=119,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Descriptions of a set of assembly-language subprograms, their
functions and calling sequences."
}

@TECHREPORT{rfc120,
AUTHOR="M. Krilanovich",
TITLE="Network {PL1} subprograms",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=120,
PAGES=16,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Descriptions of subroutines that have been implemented at UCSB
and make the network (via NCP) accessible to PL1 programs executing in
the IBM 360/75.",
URL="http://www.rfc-editor.org/rfc/rfc120.txt"
}

@TECHREPORT{rfc121,
AUTHOR="M. Krilanovich",
TITLE="Network on-line operators",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=121,
PAGES=13,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Descriptions of operators that have been implemented within
UCSB's On-Line System and make the network (via NCP) accessible to
On-Line system users.",
URL="http://www.rfc-editor.org/rfc/rfc121.txt"
}

@TECHREPORT{rfc122,
AUTHOR="J. A. White",
TITLE="Network specifications for {UCSB's} {Simple-Minded} File System",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=122,
PAGES=21,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="UCSB's Simple Minded File System (SMFS) which will provide
file storage for network users. This document provides programmers with
the information necessary to communicate with SMFS.",
URL="http://www.rfc-editor.org/rfc/rfc122.txt"
}

@TECHREPORT{rfc123,
AUTHOR="S. D. Crocker",
TITLE="Proffered Official {ICP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=123,
PAGES=3,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Description of a family of ICPs (Initial Connection Protocol)
suitable for establishing one pair of connections (one in each
direction) between any user process and any server process, and proposes
a particular subset of this family as the standard ICP for connecting
user processes to loggers on systems which accept teletype-like devices.",
URL="http://www.rfc-editor.org/rfc/rfc123.txt"
}

@TECHREPORT{rfc124,
AUTHOR="J. T. Melvin",
TITLE="Typographical error in {RFC} 107",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=124,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Points out an error in RFC 107.",
URL="http://www.rfc-editor.org/rfc/rfc124.txt"
}

@TECHREPORT{rfc125,
AUTHOR="J. McConnell",
TITLE="Response to {RFC} {86:} Proposal for Network Standard Format for a Graphics
Data Stream",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=125,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Improves and updates RFC 86.",
URL="http://www.rfc-editor.org/rfc/rfc125.txt"
}

@TECHREPORT{rfc126,
AUTHOR="J. McConnell",
TITLE="Graphics Facilities at Ames Research Center",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=126,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Discusses the graphical facilities at Ames for the IBM 360/67
TSS.",
URL="http://www.rfc-editor.org/rfc/rfc126.txt"
}

@TECHREPORT{rfc127,
AUTHOR="J. B. Postel",
TITLE="Comments on {RFC} 123",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=127,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Continued interpretations of the exchange between NCP's which
would be necessary to carry out the Initial Connection Protocol of RFC
123.",
URL="http://www.rfc-editor.org/rfc/rfc127.txt"
}

@TECHREPORT{rfc128,
AUTHOR="J. B. Postel",
TITLE="Bytes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=128,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Discussion of the Byte size parameter allowed by the 2nd level
protocol.",
URL="http://www.rfc-editor.org/rfc/rfc128.txt"
}

@TECHREPORT{rfc129,
AUTHOR="E. Harslem and J. Heafner and E. Meyer",
TITLE="Request for comments on socket name structure",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=129,
PAGES=6,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Comments on several suggested socket name structures.",
URL="http://www.rfc-editor.org/rfc/rfc129.txt"
}

@TECHREPORT{rfc130,
AUTHOR="John F. Heafner",
TITLE="Response to {RFC} {111:} Pressure from the chairman",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=130,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Discussion of RAND's role in testing other host
implementations and schedule dependences.",
URL="http://www.rfc-editor.org/rfc/rfc130.txt"
}

@TECHREPORT{rfc131,
AUTHOR="E. Harslem and John F. Heafner",
TITLE="Response to {RFC} {116:} May {NWG} meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=131,
PAGES=3,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="A description of networr plans at RAND, including the data
reconfiguration service, and a comment on the role of the NWG.",
URL="http://www.rfc-editor.org/rfc/rfc131.txt"
}

@TECHREPORT{rfc133,
AUTHOR="R. L. Sunberg",
TITLE="File Transfer and Error Recovery",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=133,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Sample interchanges and comments on file transfer and errors.",
URL="http://www.rfc-editor.org/rfc/rfc133.txt"
}

@TECHREPORT{rfc134,
AUTHOR="A. Vezza",
TITLE="Network Graphics meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=134,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Announcement of the next Network Graphics Meeting at Project
MAC in July 1971.",
URL="http://www.rfc-editor.org/rfc/rfc134.txt"
}

@TECHREPORT{rfc135,
AUTHOR="W. Hathaway",
TITLE="Response to {NWG/RFC} 110",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=135,
PAGES=3,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Comments and proposals of new conventions to replace the ones
proposed in RFC 110.",
URL="http://www.rfc-editor.org/rfc/rfc135.txt"
}

@TECHREPORT{rfc136,
AUTHOR="R. E. Kahn",
TITLE="Host accounting and administrative procedures",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=136,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Discussion of a plan to be formulated and accepted for the
development of a Host accounting system in the ARPA Network.",
URL="http://www.rfc-editor.org/rfc/rfc136.txt"
}

@TECHREPORT{rfc137,
AUTHOR="T. C. O'Sullivan",
TITLE="Telnet Protocol - a proposed document",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=137,
PAGES=11,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Solicitation for review and comment before the Atlantic City
NWG meetings.",
URL="http://www.rfc-editor.org/rfc/rfc137.txt"
}

@TECHREPORT{rfc138,
AUTHOR="Ross  Anderson and V. G. Cerf and E. Harslem and John F. Heafner and J.
Madden and Robert M. Metcalfe and A. Shoshani and J. A. White",
TITLE="Status report on proposed Data Reconfiguration Service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=138,
PAGES=23,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Provides a description of a proposed Network experiment and to
solicit comments on any aspect of the experiment.",
URL="http://www.rfc-editor.org/rfc/rfc138.txt"
}

@TECHREPORT{rfc139,
AUTHOR="T. C. O'Sullivan",
TITLE="Discussion of Telnet Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=139,
PAGES=11,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="An extension of RFC 137.",
URL="http://www.rfc-editor.org/rfc/rfc139.txt"
}

@TECHREPORT{rfc140,
AUTHOR="S. D. Crocker",
TITLE="Agenda for the May {NWG} meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=140,
PAGES=4,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="A list of topics to be discussed at the upcoming meeting, plus
a listing of relevant RFCs that should be reviewed prior to the meeting.",
URL="http://www.rfc-editor.org/rfc/rfc140.txt"
}

@TECHREPORT{rfc141,
AUTHOR="E. Harslem and John F. Heafner",
TITLE="Comments on {RFC} {114:} A File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=141,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Further discussion on the File Transfer Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc141.txt"
}

@TECHREPORT{rfc142,
AUTHOR="C. S. Kline and J. W. Wong",
TITLE="{Time-Out} Mechanism in the {Host-Host} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=142,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Discussion on potential situations that can occur when sending
a message to a foreign site.",
URL="http://www.rfc-editor.org/rfc/rfc142.txt"
}

@TECHREPORT{rfc143,
AUTHOR="W. E. Naylor and J. W. Wong and C. S. Kline and J. B. Postel",
TITLE="Regarding proffered official {ICP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=143,
PAGES=4,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Comments on a race condition discovered in the ICP as proposed
in RFC 123.",
URL="http://www.rfc-editor.org/rfc/rfc143.txt"
}

@TECHREPORT{rfc144,
AUTHOR="A. Shoshani",
TITLE="Data sharing on computer networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=144,
PAGES=6,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="An introductory paper for the upcoming NWG meeting in Atlantic
City.",
URL="http://www.rfc-editor.org/rfc/rfc144.txt"
}

@TECHREPORT{rfc145,
AUTHOR="J. B. Postel",
TITLE="Initial Connection Protocol Control Commands",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=145,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="An interpretation of the exchange between NCP's which would be
necessary to carry out the Initial Connection Protocol (ICP) of RFC 123.",
URL="http://www.rfc-editor.org/rfc/rfc145.txt"
}

@TECHREPORT{rfc146,
AUTHOR="P. M. Karp and D. B. McKay and D. P. M.",
TITLE="Views on issues relevant to data sharing on computer networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=146,
PAGES=6,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Concurrence with the views presented in RFC 140.",
URL="http://www.rfc-editor.org/rfc/rfc146.txt"
}

@TECHREPORT{rfc147,
AUTHOR="J. M. Winett",
TITLE="Definition of a socket",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=147,
PAGES=3,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Defining, specifying, and identifying sockets.",
URL="http://www.rfc-editor.org/rfc/rfc147.txt"
}

@TECHREPORT{rfc149,
AUTHOR="S. D. Crocker",
TITLE="Best Laid Plans",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=149,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Changes to the topics and attendees of the upcoming NWG
meeting.",
URL="http://www.rfc-editor.org/rfc/rfc149.txt"
}

@TECHREPORT{rfc150,
AUTHOR="R. B. Kalin",
TITLE="Use of {IPC} Facilities: A Working Paper",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=150,
PAGES=11,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="A working paper discussing the exposition of the types of
usage to which an IPC facility would be subjected. This document hopes
to clarify the goals being pursued and should provide a benchmark for
gauging various implementation strategies.",
URL="http://www.rfc-editor.org/rfc/rfc150.txt"
}

@TECHREPORT{rfc151,
AUTHOR="A. Shoshani",
TITLE="Comments on a proffered official {ICP:} {RFCs} {123,} 127",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=151,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Specific and general remarks regarding the ICP.",
URL="http://www.rfc-editor.org/rfc/rfc151.txt"
}

@TECHREPORT{rfc152,
AUTHOR="M. Wilber",
TITLE="{SRI} Artificial Intelligence status report",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=152,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Status report on SRAI's connection to the ARPANET as a
research center.",
URL="http://www.rfc-editor.org/rfc/rfc152.txt"
}

@TECHREPORT{rfc153,
AUTHOR="J. T. Melvin and R. W. Watson",
TITLE="{SRI} {ARC-NIC} status",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=153,
PAGES=4,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Discusses the current computer and network status of the SRI
ARC-NIC.",
URL="http://www.rfc-editor.org/rfc/rfc153.txt"
}

@TECHREPORT{rfc154,
AUTHOR="S. D. Crocker",
TITLE="Exposition Style",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=154,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="A note on style in documentation.",
URL="http://www.rfc-editor.org/rfc/rfc154.txt"
}

@TECHREPORT{rfc155,
AUTHOR="J. B. North",
TITLE="{ARPA} Network mailing lists",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=155,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Mailing list of people who are receiving the initial
distribution of RFCs.",
URL="http://www.rfc-editor.org/rfc/rfc155.txt"
}

@TECHREPORT{rfc156,
AUTHOR="J. Bouknight",
TITLE="Status of the Illinois site: Response to {RFC} 116",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=156,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1971,
ABSTRACT="Discusses the status of the operational hardware at the
Illinois site.",
URL="http://www.rfc-editor.org/rfc/rfc156.txt"
}

@TECHREPORT{rfc157,
AUTHOR="V. G. Cerf",
TITLE="Invitation to the Second Symposium on Problems in the Optimization of Data
Communications Systems",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=157,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Announcement of an ACM/IEEE conference on data communication.",
URL="http://www.rfc-editor.org/rfc/rfc157.txt"
}

@TECHREPORT{rfc158,
AUTHOR="T. C. O'Sullivan",
TITLE="Telnet Protocol: A Proposed Document",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=158,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Solicitation of comments, evaluation, and requests for
modification of the proposed Telnet protocol."
}

@TECHREPORT{rfc160,
AUTHOR=" {{Network Information Center, Stanford Research Institute}}",
TITLE="{RFC} brief list",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=160,
MONTH=may,
YEAR=1971,
ABSTRACT="Title or Partial Title RFC List (1-160)",
URL="http://www.rfc-editor.org/rfc/rfc160.txt"
}

@TECHREPORT{rfc161,
AUTHOR="A. Shoshani",
TITLE="Solution to the race condition in the {ICP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=161,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="A proposed solution to a problem that arose out of RFC 143.",
URL="http://www.rfc-editor.org/rfc/rfc161.txt"
}

@TECHREPORT{rfc162,
AUTHOR="M. Kampe",
TITLE="{NETBUGGER3}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=162,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="Discussion of NETBUGGER3 as a third level program for the
debugging of second and third level programs, experimentation with and
simulation of third level protocols.",
URL="http://www.rfc-editor.org/rfc/rfc162.txt"
}

@TECHREPORT{rfc163,
AUTHOR="V. G. Cerf",
TITLE="Data transfer protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=163,
PAGES=3,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="An informal statement on Data Transfer Protocols, in relation
to material discussed at the SJCC.",
URL="http://www.rfc-editor.org/rfc/rfc163.txt"
}

@TECHREPORT{rfc164,
AUTHOR="John F. Heafner",
TITLE="Minutes of Network Working Group meeting, {5/16} through {5/19/71}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=164,
PAGES=32,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="A 38 page reference on the discussions held at the Network
Working Group Meeting.",
URL="http://www.rfc-editor.org/rfc/rfc164.txt"
}

@TECHREPORT{rfc165,
AUTHOR="J. B. Postel",
TITLE="Proffered official Initial Connection Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=165,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="This document specifies the third level protocol used to
connect a user process at one site with a server process at another
site."
}

@TECHREPORT{rfc166,
AUTHOR="Ross  Anderson and V. G. Cerf and E. Harslem and John F. Heafner and J.
Madden and Robert M. Metcalfe and A. Shoshani and J. A. White",
TITLE="Data Reconfiguration Service: An implementation specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=166,
PAGES=20,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="This DRS experiment involved a software mechanism to reformat
Network data streams. The mechanism can be adapted to numerous Network
application programs.",
URL="http://www.rfc-editor.org/rfc/rfc166.txt"
}

@TECHREPORT{rfc167,
AUTHOR="A. K. Bhushan and Robert M. Metcalfe and J. M. Winett",
TITLE="Socket conventions reconsidered",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=167,
PAGES=4,
DAYS=15,
MONTH=may,
YEAR=1971,
ABSTRACT="The recent NCP Protocol said nothing about how hosts should
assign socket numbers to process ports, except that the low-order bit is
to specify socket gender. This document discusses two recent proposals
that call for additional network-wide conventions on the 32-bit socket
number.",
URL="http://www.rfc-editor.org/rfc/rfc167.txt"
}

@TECHREPORT{rfc169,
AUTHOR="S. D. Crocker",
TITLE="Computer networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=169,
DAYS=15,
MONTH=may,
YEAR=1971
}

@TECHREPORT{rfc170,
AUTHOR=" {{Network Information Center, Stanford Research Institute}}",
TITLE="{RFC} List by Number",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=170,
MONTH=jun,
YEAR=1971,
ABSTRACT="A list of RFCs 1-170.",
URL="http://www.rfc-editor.org/rfc/rfc170.txt"
}

@TECHREPORT{rfc171,
AUTHOR="A. K. Bhushan and B. Braden and W. Crowther and E. Harslem and J. Heafner
and A. McKenize and J. T. Melvin and B. Sundberg",
TITLE="The Data Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=171,
PAGES=9,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="Definition of a low-level Data Transfer Protocol (DTP) to be
used for transfer of data in file transfer, remote job entry, and other
applications oriented protocols. A companion paper (RFC 172) describes
file transfer protocol.",
URL="http://www.rfc-editor.org/rfc/rfc171.txt"
}

@TECHREPORT{rfc172,
AUTHOR="A. K. Bhushan and B. Braden and W. Crowther and E. Harslem and J. Heafner
and A. A. McKenzie and J. T. Melvin and B. Sundberg",
TITLE="The File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=172,
PAGES=12,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="This protocol is a user-level protocol for file transfer
between host computers (including terminal IMPs), on the ARPA computer
network. The File Transfer Protocol (FTP) uses the data transfer
protocol described in RFC 171. This paper assumes knowledge of RFC 171.",
URL="http://www.rfc-editor.org/rfc/rfc172.txt"
}

@TECHREPORT{rfc173,
AUTHOR="P. M. Karp and D. B. McKay",
TITLE="Network Data Management Committee Meeting Announcement",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=173,
PAGES=2,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="A report on the formation of a data managment committee and on
its first meeting.",
URL="http://www.rfc-editor.org/rfc/rfc173.txt"
}

@TECHREPORT{rfc174,
AUTHOR="J. B. Postel and V. G. Cerf",
TITLE="{UCLA} - Computer Science Graphics Overview",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=174,
PAGES=3,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="This document provides an overview of the hardware, software,
and intentions of the UCLA Computer Science Department's Graphics
project.",
URL="http://www.rfc-editor.org/rfc/rfc174.txt"
}

@TECHREPORT{rfc175,
AUTHOR="E. Harslem and John F. Heafner",
TITLE={Comments on {"}Socket Conventions Reconsidered{"}},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=175,
PAGES=1,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="Pro and con discussion regarding RFC 167.",
URL="http://www.rfc-editor.org/rfc/rfc175.txt"
}

@TECHREPORT{rfc176,
AUTHOR="A. K. Bhushan and R. Kanodia and Robert M. Metcalfe and J. B. Postel",
TITLE={Comments on {"}Byte size for connections{"}},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=176,
PAGES=5,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="This document points out three views on the use of byte size
for network connections: 1) Byte size should not be used at all. 2) Byte
size is solely for the convenience of NCP's. 3) Byte size choice is a
user-level prerogative.",
URL="http://www.rfc-editor.org/rfc/rfc176.txt"
}

@TECHREPORT{rfc177,
AUTHOR="J. McConnell",
TITLE="Device independent graphical display description",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=177,
PAGES=9,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="As more nodes are connected to the ARPA network, the types of
graphical display processors available to users is quite varied. To
attempt to facilitate the transmission of graphical information over the
network, a device independent description of a display is described.",
URL="http://www.rfc-editor.org/rfc/rfc177.txt"
}

@TECHREPORT{rfc178,
AUTHOR="I. W. Cotton",
TITLE="Network graphic attention handling",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=178,
PAGES=11,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="The process of attention handling is briefly described,
various graphic configurations are discussed, input devices are surveyed
to identify the types of data which they produce, and an attention
protocol is proposed.",
URL="http://www.rfc-editor.org/rfc/rfc178.txt"
}

@TECHREPORT{rfc179,
AUTHOR="A. A. McKenzie",
TITLE="Link Number Assignments",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=179,
PAGES=1,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="This RFC has been replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc179.txt"
}

@TECHREPORT{rfc180,
AUTHOR="A. A. McKenzie",
TITLE="File system questionnaire",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=180,
PAGES=4,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="An attempt to gather information about local file and data
conventions.",
URL="http://www.rfc-editor.org/rfc/rfc180.txt"
}

@TECHREPORT{rfc181,
AUTHOR="J. McConnell",
TITLE="Modifications to {RFC} 177",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=181,
PAGES=3,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="This document is intended to modify the proposal for a device
independent graphical display description discussed in RFC 177. The main
changes are in the definition of coordinate areas to avoid one problem
encountered with the old definition and to provide more flexibility.",
URL="http://www.rfc-editor.org/rfc/rfc181.txt"
}

@TECHREPORT{rfc182,
AUTHOR="J. B. North",
TITLE="Compilation of list of relevant site reports",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=182,
PAGES=1,
DAYS=15,
MONTH=jun,
YEAR=1971,
ABSTRACT="A Network Information Center compilation list of all
site-produced reports which are of interest to Network participants.",
URL="http://www.rfc-editor.org/rfc/rfc182.txt"
}

@TECHREPORT{rfc183,
AUTHOR="J. M. Winett",
TITLE="{EBCDIC} codes and their mapping to {ASCII}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=183,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="This document defines and describes the IBM Standard Extended
BCD Interchange Code. This is done in order to uniquely map the ASCII
codes into corresponding EBCDIC codes in a consistent manner throughout
the ARPA Network."
}

@TECHREPORT{rfc184,
AUTHOR="K. C. Kelley",
TITLE="Proposed graphic display modes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=184,
PAGES=7,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="The ARPA Network node at the University of Illinois' Center
for Advanced Computation is different from other nodes. It is not just a
simple attachment to the net. Establishment of the computer system
specifically for use of the ILLIAC IV and the network is in process.
This paper describes the operating systems, network interface and
utility routines, and ILLIAC IV routines to be used over the network.",
URL="http://www.rfc-editor.org/rfc/rfc184.txt"
}

@TECHREPORT{rfc185,
AUTHOR="J. B. North",
TITLE="{NIC} distribution of manuals and handbooks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=185,
PAGES=1,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="The NIC request that sites send copies of manuals and
handbooks to them.",
URL="http://www.rfc-editor.org/rfc/rfc185.txt"
}

@TECHREPORT{rfc186,
AUTHOR="J. C. Michener",
TITLE="Network graphics loader",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=186,
PAGES=17,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="The Network Graphics Loader described in this document
proposes to permit remote users on the ARPA network to obtain graphics
output from programs they write for the Evans and Sutherland Line
Drawing System.",
URL="http://www.rfc-editor.org/rfc/rfc186.txt"
}

@TECHREPORT{rfc187,
AUTHOR="D. B. McKay and D. P. Karp",
TITLE="Network/440 Protocol Concept",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=187,
PAGES=11,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="An information Request for Comments that is intended to convey
some of the thinking and philosophy that went into IBM's network
protocol and overall network design.",
URL="http://www.rfc-editor.org/rfc/rfc187.txt"
}

@TECHREPORT{rfc188,
AUTHOR="P. M. Karp and D. B. McKay",
TITLE="Data management meeting announcement",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=188,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1971,
ABSTRACT="Plans for a data management meeting to be held Auguest 1971.",
URL="http://www.rfc-editor.org/rfc/rfc188.txt"
}

@TECHREPORT{rfc189,
AUTHOR="R. Braden",
TITLE="Interim {NETRJS} specifications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=189,
PAGES=19,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="A description of the operation and protocol of the remote job
entry service to CCN's 360 Model 91. This interim protocol will be
implemented as a production service before the end of July.",
URL="http://www.rfc-editor.org/rfc/rfc189.txt"
}

@TECHREPORT{rfc190,
AUTHOR="L. P. Deutsch",
TITLE="{DEC} {PDP-10-IMLAC} communications system",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=190,
PAGES=16,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="This document describes an operational system for
communicating textual display information between a main-site computer
and a remote display processor.",
URL="http://www.rfc-editor.org/rfc/rfc190.txt"
}

@TECHREPORT{rfc191,
AUTHOR="C. Irby",
TITLE="Graphics implementation and conceptualization at Augmentation Research
Center",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=191,
PAGES=4,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="A brief description of the way in which graphics terminals are
conceptualized and used at the Augmentation Research Center.",
URL="http://www.rfc-editor.org/rfc/rfc191.txt"
}

@TECHREPORT{rfc192,
AUTHOR="R. W. Watson",
TITLE="Some factors which a Network Graphics Protocol must consider",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=192,
PAGES=19,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="Discussion on what any network graphics protocol should come
to grips with.",
URL="http://www.rfc-editor.org/rfc/rfc192.txt"
}

@TECHREPORT{rfc193,
AUTHOR="E. Harslem and John F. Heafner",
TITLE="{NETWORK} {CHECKOUT}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=193,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="A report form RAND on testing ten other hosts.",
URL="http://www.rfc-editor.org/rfc/rfc193.txt"
}

@TECHREPORT{rfc194,
AUTHOR="V. G. Cerf and E. Harslem and J. Heafner and B. Metcalfe and J. A. White",
TITLE="The data reconfiguration service {--} compiler/interpreter implementation
notesThe Data Reconfiguration Service {--} {Compiler/Interpreter}
Implementation Notes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=194,
PAGES=18,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="This document describes the new features of the language, the
new syntax, the form interpreter, and the instruction set.",
URL="http://www.rfc-editor.org/rfc/rfc194.txt"
}

@TECHREPORT{rfc195,
AUTHOR="G. H. Mealy",
TITLE="Data computers-data descriptions and access language",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=195,
PAGES=4,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="This document discusses some of the problems involved in the
unified approach to Network data management, and to suggest possible
avenues of approach toward their resolution.",
URL="http://www.rfc-editor.org/rfc/rfc195.txt"
}

@TECHREPORT{rfc196,
AUTHOR="R. W. Watson",
TITLE="Mail Box Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=196,
PAGES=4,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="The purpose of this protocol is to provide at each site a
standard mechanism to receive sequential files for immediate or deferred
printing or other uses.",
URL="http://www.rfc-editor.org/rfc/rfc196.txt"
}

@TECHREPORT{rfc197,
AUTHOR="A. Shoshani and E. Harslem",
TITLE="Initial Connection Protocol - Reviewed",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=197,
PAGES=5,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="An attempt at a simple version of ICP, assuming one may add
commands to Host-Host protocol.",
URL="http://www.rfc-editor.org/rfc/rfc197.txt"
}

@TECHREPORT{rfc198,
AUTHOR="John F. Heafner",
TITLE="Site Certification - Lincoln Labs {360/67}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=198,
PAGES=1,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="A report from RAND that Lincoln Labs protocol implementations
are correct.",
URL="http://www.rfc-editor.org/rfc/rfc198.txt"
}

@TECHREPORT{rfc199,
AUTHOR="T. Williams",
TITLE="Suggestions for a network data-tablet graphics protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=199,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="SDC's comments to the discussion of a protocol for network
graphics within the ARPA Network community. Concern is focused on the
development of the graphics protocol in two areas: non-interactive
graphics and data-tablet graphics, as opposed to fully interactive
graphics."
}

@TECHREPORT{rfc202,
AUTHOR="S. M. Wolfe and J. B. Postel",
TITLE="Possible Deadlock in {ICP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=202,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="A notation of a possible deadlock that will occur if both
sides open thier send or both sides open their receive sockets first.",
URL="http://www.rfc-editor.org/rfc/rfc202.txt"
}

@TECHREPORT{rfc203,
AUTHOR="R. B. Kalin",
TITLE="Achieving reliable communication",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=203,
PAGES=4,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="This is a non-standard protocol, suitable for either second or
third level use and is proposed with the intent of providing error
resistant and highly reliable communication channels.",
URL="http://www.rfc-editor.org/rfc/rfc203.txt"
}

@TECHREPORT{rfc204,
AUTHOR="J. B. Postel",
TITLE="Sockets in use",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=204,
PAGES=1,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="Announcement to collect information on the use of socket
numbers for standard service programs.",
URL="http://www.rfc-editor.org/rfc/rfc204.txt"
}

@TECHREPORT{rfc205,
AUTHOR="R. Braden",
TITLE="{NETCRT} - a character display protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=205,
PAGES=13,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="A significant revision of the character-display protocol
(NETCRT), based on CCN's proposed NETCRT from the May NWG Meeting.",
URL="http://www.rfc-editor.org/rfc/rfc205.txt"
}

@TECHREPORT{rfc206,
AUTHOR="J. A. White",
TITLE="User Telnet - description of an initial implementation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=206,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="This document describes a program whose function is to make an
Online System terminal appear to any teletype-compatible, time-sharing
system in the Network as if it were directly connected to that system."
}

@TECHREPORT{rfc207,
AUTHOR="A. Vezza",
TITLE="September Network Working Group meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=207,
PAGES=2,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="Next meeting announcement.",
URL="http://www.rfc-editor.org/rfc/rfc207.txt"
}

@TECHREPORT{rfc208,
AUTHOR="A. A. McKenzie",
TITLE="Address tables",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=208,
PAGES=3,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="A table of hosts on or soon to be on the ARPANET.",
URL="http://www.rfc-editor.org/rfc/rfc208.txt"
}

@TECHREPORT{rfc209,
AUTHOR="B. Cosell",
TITLE="{Host/IMP} interface documentation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=209,
PAGES=1,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="Discussion of a change to the IMP and the documentation (BBN
report 1822).",
URL="http://www.rfc-editor.org/rfc/rfc209.txt"
}

@TECHREPORT{rfc210,
AUTHOR="W. Conrad",
TITLE="Improvement of Flow Control",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=210,
PAGES=2,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT={Discussion of the current {"}give back{"} - {"}return{"} scheme.},
URL="http://www.rfc-editor.org/rfc/rfc210.txt"
}

@TECHREPORT{rfc212,
AUTHOR=" {{Information Sciences Institute University of Southern California}}",
TITLE="{NWG} meeting on network usage",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=212,
MONTH=aug,
YEAR=1971,
ABSTRACT="A mailing list for RFC distribution.",
URL="http://www.rfc-editor.org/rfc/rfc212.txt"
}

@TECHREPORT{rfc213,
AUTHOR="B. Cosell",
TITLE="{IMP} System change notification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=213,
PAGES=1,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="Several changes in the IMP internal procedures.",
URL="http://www.rfc-editor.org/rfc/rfc213.txt"
}

@TECHREPORT{rfc214,
AUTHOR="E. Harslem",
TITLE="Network checkpoint",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=214,
PAGES=2,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="Notification of the verification of certain sites.",
URL="http://www.rfc-editor.org/rfc/rfc214.txt"
}

@TECHREPORT{rfc215,
AUTHOR="A. A. McKenzie",
TITLE="{NCP,} {ICP,} and Telnet: The Terminal {IMP} implementation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=215,
PAGES=7,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="Announcement of six Terminal IMPs being incorporated into the
Network, with additional Terminal IMPS scheduled for delivery.",
URL="http://www.rfc-editor.org/rfc/rfc215.txt"
}

@TECHREPORT{rfc216,
AUTHOR="J. A. White",
TITLE="Telnet access to {UCSB's} {On-Line} System",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=216,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Discussion of the implementation of a teletype-compatible
interface to UCSB's On-Line System."
}

@TECHREPORT{rfc217,
AUTHOR="J. A. White",
TITLE="Specifications changes for {OLS,} {RJE/RJOR,} and {SMFS}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=217,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Current listing of documents that have been revised.",
URL="http://www.rfc-editor.org/rfc/rfc217.txt"
}

@TECHREPORT{rfc218,
AUTHOR="B. Cosell",
TITLE="Changing the {IMP} status reporting facility",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=218,
PAGES=1,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="A change in internal procedures in the ARPANET status reports
from the IMPs to the NIC.",
URL="http://www.rfc-editor.org/rfc/rfc218.txt"
}

@TECHREPORT{rfc219,
AUTHOR="R. Winter",
TITLE="User's view of the datacomputer",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=219,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="A description of the Datacomputer."
}

@TECHREPORT{rfc221,
AUTHOR="R. W. Watson",
TITLE="Mail Box Protocol: Version 2",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=221,
PAGES=5,
DAYS=15,
MONTH=aug,
YEAR=1971,
ABSTRACT="Discussion of the initial reaction to RFC 196.",
URL="http://www.rfc-editor.org/rfc/rfc221.txt"
}

@TECHREPORT{rfc222,
AUTHOR="Robert M. Metcalfe",
TITLE="Subject: System programmer's workshop",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=222,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Announcement of the next workshop.",
URL="http://www.rfc-editor.org/rfc/rfc222.txt"
}

@TECHREPORT{rfc223,
AUTHOR="J. T. Melvin and R. W. Watson",
TITLE="Network Information Center schedule for network users",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=223,
PAGES=4,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Access schedule for remote users of the NIC.",
URL="http://www.rfc-editor.org/rfc/rfc223.txt"
}

@TECHREPORT{rfc224,
AUTHOR="A. A. McKenzie",
TITLE="Comments on Mailbox Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=224,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Comments on electronic mail and TIP's.",
URL="http://www.rfc-editor.org/rfc/rfc224.txt"
}

@TECHREPORT{rfc225,
AUTHOR="E. Harslem and R. Stoughton",
TITLE="{Rand/UCSB} network graphics experiment",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=225,
PAGES=5,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Describes use from RAND of the UCSB-OLS system.",
URL="http://www.rfc-editor.org/rfc/rfc225.txt"
}

@TECHREPORT{rfc226,
AUTHOR="P. M. Karp",
TITLE="Standardization of host mnemonics",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=226,
PAGES=1,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="A list of Host Mnemonics is provided.",
URL="http://www.rfc-editor.org/rfc/rfc226.txt"
}

@TECHREPORT{rfc227,
AUTHOR="John F. Heafner and E. Harslem",
TITLE="Data transfer rates {(Rand/UCLA)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=227,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="A memo on data rates typical of the RJS use at UCLA CCN.",
URL="http://www.rfc-editor.org/rfc/rfc227.txt"
}

@TECHREPORT{rfc228,
AUTHOR="D. C. Walden",
TITLE="Clarification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=228,
PAGES=1,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="A correction to RFC 70.",
URL="http://www.rfc-editor.org/rfc/rfc228.txt"
}

@TECHREPORT{rfc229,
AUTHOR="J. B. Postel",
TITLE="Standard host names",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=229,
PAGES=3,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="A suggestion of eight character names and a proposed list of
names.",
URL="http://www.rfc-editor.org/rfc/rfc229.txt"
}

@TECHREPORT{rfc230,
AUTHOR="T. Pyke",
TITLE="Toward reliable operation of minicomputer-based terminals on a {TIP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=230,
PAGES=3,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Points out inadequate error detection and initiation of
corrective measures in the present protocol for communication between a
TIP and attached terminals. References RFC 203.",
URL="http://www.rfc-editor.org/rfc/rfc230.txt"
}

@TECHREPORT{rfc231,
AUTHOR="John F. Heafner and E. Harslem",
TITLE="Service center standards for remote usage: A user's view",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=231,
PAGES=4,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="A statement of views on service center standards. An input to
the service center panel discussion of the October Network meeting.",
URL="http://www.rfc-editor.org/rfc/rfc231.txt"
}

@TECHREPORT{rfc232,
AUTHOR="A. Vezza",
TITLE="Postponement of network graphics meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=232,
PAGES=1,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Schedule conflict and postponement of the graphics meeting.",
URL="http://www.rfc-editor.org/rfc/rfc232.txt"
}

@TECHREPORT{rfc233,
AUTHOR="A. K. Bhushan and R. Metcalfe",
TITLE="Standardization of host call letters",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=233,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="A currently recommended list of call letters.",
URL="http://www.rfc-editor.org/rfc/rfc233.txt"
}

@TECHREPORT{rfc234,
AUTHOR="A. Vezza",
TITLE="Network Working Group meeting schedule",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=234,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="Plans for a Network Working Group meeting in October 1971.",
URL="http://www.rfc-editor.org/rfc/rfc234.txt"
}

@TECHREPORT{rfc235,
AUTHOR="E. Westheimer",
TITLE="Site status",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=235,
PAGES=5,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Starting with this RFC, BBN will report on the status of most
Network Hosts.",
URL="http://www.rfc-editor.org/rfc/rfc235.txt"
}

@TECHREPORT{rfc237,
AUTHOR="R. W. Watson",
TITLE="{NIC} view of standard host names",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=237,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="The NIC strongly favors standardization of host names. In this
RFC, the NIC proposes that any standard naming scheme should take into
account certain considerations.",
URL="http://www.rfc-editor.org/rfc/rfc237.txt"
}

@TECHREPORT{rfc238,
AUTHOR="R. Braden",
TITLE="Comments on {DTP} and {FTP} proposals",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=238,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="This RFC updates RFCs 171,172.",
URL="http://www.rfc-editor.org/rfc/rfc238.txt"
}

@TECHREPORT{rfc239,
AUTHOR="R. Braden",
TITLE="Host mnemonics proposed in {RFC} 226 {(NIC} {7625)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=239,
PAGES=1,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Discussion and comments on RFC 226.",
URL="http://www.rfc-editor.org/rfc/rfc239.txt"
}

@TECHREPORT{rfc241,
AUTHOR="A. A. McKenzie",
TITLE="Connecting computers to {MLC} ports",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=241,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1971,
ABSTRACT="Discussion on the pros and cons of computers being connected
through serial communication lines to ports on the Terminal IMP's
Multi-Line Controller (MLC).",
URL="http://www.rfc-editor.org/rfc/rfc241.txt"
}

@TECHREPORT{rfc242,
AUTHOR="L. Haibt and A. Mullery",
TITLE="Data Descriptive Language for Shared Data",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=242,
PAGES=10,
DAYS=15,
MONTH=jul,
YEAR=1971,
ABSTRACT="Discussion of representation differences. Three categories are
defined: very local representation, representation of collections of
data, and other more complex structures that data collections may have.",
URL="http://www.rfc-editor.org/rfc/rfc242.txt"
}

@TECHREPORT{rfc243,
AUTHOR="A. Mullery",
TITLE="Network and data sharing bibliography",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=243,
PAGES=7,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="Updated by RFC 290.",
URL="http://www.rfc-editor.org/rfc/rfc243.txt"
}

@TECHREPORT{rfc245,
AUTHOR="C. Falls",
TITLE="Reservations for Network Group meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=245,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1971,
URL="http://www.rfc-editor.org/rfc/rfc245.txt"
}

@TECHREPORT{rfc247,
AUTHOR="P. M. Karp",
TITLE="Proffered set of standard host names",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=247,
PAGES=4,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="Proposed general set of rules for forming Host Names.
Obsoletes RFC 226.",
URL="http://www.rfc-editor.org/rfc/rfc247.txt"
}

@TECHREPORT{rfc249,
AUTHOR="R. F. Borelli",
TITLE="Coordination of equipment and supplies purchase",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=249,
PAGES=2,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="Announcement of an agreement reached regarding the study of
the feasibility of a coordinating point for purchases of equipment and
supplies to be used on the network.",
URL="http://www.rfc-editor.org/rfc/rfc249.txt"
}

@TECHREPORT{rfc250,
AUTHOR="H. Brodie",
TITLE="Some thoughts on file transfer",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=250,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="Further clarification and proposed revision on several aspects
of the proposed Data Transfer Protocol and the File Transfer Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc250.txt"
}

@TECHREPORT{rfc251,
AUTHOR="D. Stern",
TITLE="Weather data",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=251,
PAGES=2,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="Announcement of the USAF Environmental Technical Application
Center (ETAC) services in providing weather data for the ARPA Network.",
URL="http://www.rfc-editor.org/rfc/rfc251.txt"
}

@TECHREPORT{rfc252,
AUTHOR="E. Westheimer",
TITLE="Network host status",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=252,
PAGES=3,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="Updates RFC 240.",
URL="http://www.rfc-editor.org/rfc/rfc252.txt"
}

@TECHREPORT{rfc253,
AUTHOR="J. A. Moorer",
TITLE="Second Network Graphics meeting details",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=253,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="Plans for a graphics meeting to be held November 1971. See RFC
282.",
URL="http://www.rfc-editor.org/rfc/rfc253.txt"
}

@TECHREPORT{rfc254,
AUTHOR="A. K. Bhushan",
TITLE="Scenarios for using {ARPANET} computers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=254,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="This document is provided to facilitate the use of ARPANET
host computer systems via the ARPANET. The objective of these scenarios
is to aid a user in sampling host computers on the ARPANET, thereby
stimulating his interest in using the ARPANET."
}

@TECHREPORT{rfc255,
AUTHOR="E. Westheimer",
TITLE="Status of network hosts",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=255,
PAGES=2,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="Updates RFC 252.",
URL="http://www.rfc-editor.org/rfc/rfc255.txt"
}

@TECHREPORT{rfc256,
AUTHOR="B. Cosell",
TITLE="{IMPSYS} change notification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=256,
PAGES=1,
DAYS=15,
MONTH=nov,
YEAR=1971,
ABSTRACT="Announcement of a new version of the IMP system, Version 2513.",
URL="http://www.rfc-editor.org/rfc/rfc256.txt"
}

@TECHREPORT{rfc263,
AUTHOR="A. A. McKenzie",
TITLE={{"}Very Distant{"} Host interface},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=263,
PAGES=2,
DAYS=15,
MONTH=dec,
YEAR=1971,
ABSTRACT="Discussion on the best solutions to the general problem of
interfacing Hosts to IMPs.",
URL="http://www.rfc-editor.org/rfc/rfc263.txt"
}

@TECHREPORT{rfc268,
AUTHOR="J. B. Postel",
TITLE="Graphics facilities information",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=268,
PAGES=1,
DAYS=15,
MONTH=nov,
YEAR=1971,
ABSTRACT="Request for graphics information.",
URL="http://www.rfc-editor.org/rfc/rfc268.txt"
}

@TECHREPORT{rfc269,
AUTHOR="H. Brodie",
TITLE="Some Experience with File Transfer",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=269,
PAGES=3,
DAYS=15,
MONTH=dec,
YEAR=1971,
ABSTRACT="Updates RFCs 122,238,172.",
URL="http://www.rfc-editor.org/rfc/rfc269.txt"
}

@TECHREPORT{rfc273,
AUTHOR="R. W. Watson",
TITLE="More on standard host names",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=273,
PAGES=3,
DAYS=15,
MONTH=oct,
YEAR=1971,
ABSTRACT="Discussion on the best way to set up naming schemes for
standard Host names.",
URL="http://www.rfc-editor.org/rfc/rfc273.txt"
}

@TECHREPORT{rfc274,
AUTHOR="E. Forman",
TITLE="Establishing a local guide for network usage",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=274,
PAGES=5,
DAYS=15,
MONTH=nov,
YEAR=1971,
ABSTRACT="Discussion on the best solutions to the general problem of
interfacing Hosts to IMPs.",
URL="http://www.rfc-editor.org/rfc/rfc274.txt"
}

@TECHREPORT{rfc276,
AUTHOR="R. W. Watson",
TITLE="{NIC} course",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=276,
PAGES=1,
DAYS=15,
MONTH=nov,
YEAR=1971,
ABSTRACT="A course announcement from the NIC on the use of its Online
System (NLS).",
URL="http://www.rfc-editor.org/rfc/rfc276.txt"
}

@TECHREPORT{rfc278,
AUTHOR="A. K. Bhushan and R. Braden and E. Harslem and John F. Heafner and A. A.
McKenzie and J. T. Melvin and R. L. Sundberg and R. W. Watson",
TITLE="Revision of the Mail Box Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=278,
PAGES=4,
DAYS=15,
MONTH=nov,
YEAR=1971,
ABSTRACT="This paper obsoletes RFC 221. The changes to RFC 221 are
presented in this document. The protocol is also restated for additional
review.",
URL="http://www.rfc-editor.org/rfc/rfc278.txt"
}

@TECHREPORT{rfc280,
AUTHOR="R. W. Watson",
TITLE="A Draft of Host Names",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=280,
PAGES=3,
DAYS=15,
MONTH=nov,
YEAR=1971,
ABSTRACT="A proposed list of names for hosts.",
URL="http://www.rfc-editor.org/rfc/rfc280.txt"
}

@TECHREPORT{rfc281,
AUTHOR="A. A. McKenzie",
TITLE="Suggested addition to File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=281,
PAGES=8,
DAYS=15,
MONTH=dec,
YEAR=1971,
ABSTRACT="Suggests an improved restart procedure in FTP.",
URL="http://www.rfc-editor.org/rfc/rfc281.txt"
}

@TECHREPORT{rfc282,
AUTHOR="M. A. Padlipsky",
TITLE="Graphics meeting report",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=282,
PAGES=8,
DAYS=15,
MONTH=dec,
YEAR=1971,
ABSTRACT="Describes a graphics meeting held November 1972.",
URL="http://www.rfc-editor.org/rfc/rfc282.txt"
}

@TECHREPORT{rfc283,
AUTHOR="R. Braden",
TITLE="{NETRJT:} Remote Job Service Protocol for {TIPS}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=283,
PAGES=9,
DAYS=15,
MONTH=dec,
YEAR=1971,
ABSTRACT="Discusses how it may be feasible in the future to use TIPS for
remote job entry in one or more of three ways: attach local card
readers, line printer, and card punches directly to TIP ports, connect a
remote batch terminal to a full-duplex TIP port via a communication
line, and/or use the tape drive, and do card-to-tape and/or
tape-to-print on another computer.",
URL="http://www.rfc-editor.org/rfc/rfc283.txt"
}

@TECHREPORT{rfc285,
AUTHOR="D. Huff",
TITLE="Network graphics",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=285,
DAYS=15,
MONTH=dec,
YEAR=1971,
ABSTRACT="This paper is aimed at bringing together the present state of
graphics on the NET for the newcomer and attempting to add a little more
documentation to the current ground covered in graphics research by
ARPA.",
URL="http://www.rfc-editor.org/rfc/rfc285.txt"
}

@TECHREPORT{rfc286,
AUTHOR="E. Forman",
TITLE="Network Library Information System",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=286,
PAGES=1,
DAYS=15,
MONTH=dec,
YEAR=1971,
ABSTRACT="This RFC solicites interested parties in the ARPA community to
form a working group whose interests include developing a new system
that would enable computer query of Library holdings. Georgetown
University is currently designing a Learning Resource Center which could
be the prototype of the proposed working group.",
URL="http://www.rfc-editor.org/rfc/rfc286.txt"
}

@TECHREPORT{rfc289,
AUTHOR="R. W. Watson",
TITLE="What we hope is an official list of host names",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=289,
PAGES=3,
DAYS=15,
MONTH=dec,
YEAR=1971,
ABSTRACT="An accepted list of official formal host names and nicknames.",
URL="http://www.rfc-editor.org/rfc/rfc289.txt"
}

@TECHREPORT{rfc86,
AUTHOR="S. D. Crocker",
TITLE="Proposal for a Network Standard Format for a Data Stream to Control
Graphics Display",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=86,
PAGES=6,
DAYS=15,
MONTH=jan,
YEAR=1971,
ABSTRACT="Proposes specifying the form of an output stream for the case
that the output portion of the console (which is attached to a computer
at the user's site) is a typical refresh display with point, vector, and
character drawing capability.",
URL="http://www.rfc-editor.org/rfc/rfc86.txt"
}

@TECHREPORT{rfc87,
AUTHOR="A. Vezza",
TITLE="Topic for Discussion at the Next Network Working Group Meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=87,
PAGES=3,
DAYS=15,
MONTH=jan,
YEAR=1971,
ABSTRACT="Suggests Network Working Group discussion on topics germane to
network graphics.",
URL="http://www.rfc-editor.org/rfc/rfc87.txt"
}

@TECHREPORT{rfc88,
AUTHOR="R. Braden and S. M. Wolfe",
TITLE="{NETRJS:} A third level protocol for Remote Job Entry",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=88,
PAGES=9,
DAYS=15,
MONTH=jan,
YEAR=1971,
ABSTRACT="Description of NETRJS, which is the name for a message
protocol and a set of control conventions which will allow users at
remote Hosts to access the RJS remote batch subsystem of UCLA/CCN.",
URL="http://www.rfc-editor.org/rfc/rfc88.txt"
}

@TECHREPORT{rfc89,
AUTHOR="Robert M. Metcalfe",
TITLE="Some historic moments in networking",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=89,
PAGES=7,
DAYS=15,
MONTH=jan,
YEAR=1971,
ABSTRACT="Noteworthy achievements for the MIT-Project MAC Dynamic
Modeling/Computer Graphics PDP-6/10 System, while awaiting the
completion of an interim network control program.",
URL="http://www.rfc-editor.org/rfc/rfc89.txt"
}

@TECHREPORT{rfc90,
AUTHOR="R. Braden",
TITLE="{CCN} as a Network Service Center",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=90,
PAGES=6,
DAYS=15,
MONTH=jan,
YEAR=1971,
ABSTRACT="Discussion of UCLA's Campus Computing Network of services and
implementation priorities.",
URL="http://www.rfc-editor.org/rfc/rfc90.txt"
}

@TECHREPORT{rfc93,
AUTHOR="A. A. McKenzie",
TITLE="Initial Connection Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=93,
PAGES=1,
DAYS=15,
MONTH=jan,
YEAR=1971,
ABSTRACT="A review of the Initial Connection Protocol (ICP), first
described in RFC 66 and restated in RFC 80.",
URL="http://www.rfc-editor.org/rfc/rfc93.txt"
}

@TECHREPORT{rfc94,
AUTHOR="E. Harslem and John F. Heafner",
TITLE="Some thoughts on Network Graphics",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=94,
PAGES=6,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT="Discussion of the initial reaction to RFC 86, whose purpose
was to provide a basis for discussion and development of Network
graphics.",
URL="http://www.rfc-editor.org/rfc/rfc94.txt"
}

@TECHREPORT{rfc95,
AUTHOR="S. D. Crocker",
TITLE="Distribution of {NWG/RFC's} through the {NIC}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=95,
PAGES=5,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT="Standards for establishing lines of communication of all of
the sites with the Network Information Center, in regards to
distribution of RFC's.",
URL="http://www.rfc-editor.org/rfc/rfc95.txt"
}

@TECHREPORT{rfc96,
AUTHOR="R. W. Watson",
TITLE="An Interactive Network Experiment to Study Modes of Access the Network
Information Center",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=96,
PAGES=5,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT="Outlines the framework for a simple interactive experiment to
study modes of access to the Network Information Center (NIC).",
URL="http://www.rfc-editor.org/rfc/rfc96.txt"
}

@TECHREPORT{rfc97,
AUTHOR="J. T. Melvin and R. W. Watson",
TITLE="First Cut at a Proposed Telnet Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=97,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT="This document was motivated by the need to set specifications
for a protocol which would allow on-line access to the Network
Information Center (NIC)."
}

@TECHREPORT{rfc98,
AUTHOR="E. Meyer and T. P. Skinner",
TITLE="Logger Protocol Proposal",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=98,
PAGES=10,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT={This {"}network logger protocol{"} is intended to specify how the
existing logger of a network host is to interface to the network so as
to permit a login from a console attached to another host.},
URL="http://www.rfc-editor.org/rfc/rfc98.txt"
}

@TECHREPORT{rfc99,
AUTHOR="P. M. Karp",
TITLE="Network Meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=99,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1971,
ABSTRACT="Announcement of the next meeting of the Network Working Group
for 20 May 1970.",
URL="http://www.rfc-editor.org/rfc/rfc99.txt"
}

@TECHREPORT{rfc264,
AUTHOR="A. K. Bhushan and B. Braden and W. Crowther and E. Harslem and J. Heafner
and A. McKenize and B. Sundberg and D. Watson",
TITLE="The Data Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=264,
PAGES=9,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="This paper is a revision of RFC 171. The changes to RFC 171
are presented in this document. The protocol is also restated for
additional review.",
URL="http://www.rfc-editor.org/rfc/rfc264.txt"
}

@TECHREPORT{rfc270,
AUTHOR="A. A. McKenzie",
TITLE="Correction to {BBN} Report No.1822 {(NIC} {NO} {7958)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=270,
PAGES=1,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="Updates pages 25 and 26 of BBN report 1822.",
URL="http://www.rfc-editor.org/rfc/rfc270.txt"
}

@TECHREPORT{rfc271,
AUTHOR="B. Cosell",
TITLE="{IMP} System change notifications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=271,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="Announcement of a new version of the IMP System, Version 2514.",
URL="http://www.rfc-editor.org/rfc/rfc271.txt"
}

@TECHREPORT{rfc288,
AUTHOR="E. Westheimer",
TITLE="Network host status",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=288,
PAGES=4,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="Updates RFC 287.",
URL="http://www.rfc-editor.org/rfc/rfc288.txt"
}

@TECHREPORT{rfc290,
AUTHOR="A. Mullery",
TITLE="Computer networks and data sharing: A bibliography",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=290,
PAGES=15,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="Updates RFC 243.",
URL="http://www.rfc-editor.org/rfc/rfc290.txt"
}

@TECHREPORT{rfc291,
AUTHOR="D. B. McKay",
TITLE="Data Management Meeting Announcement",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=291,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="A meeting about datamanagement will be held February 1972.",
URL="http://www.rfc-editor.org/rfc/rfc291.txt"
}

@TECHREPORT{rfc292,
AUTHOR="J. C. Michener and I. W. Cotton and K. C. Kelley and D. E. Liddle and E.
Meyer",
TITLE="Graphics Protocol: Level 0 only",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=292,
PAGES=10,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="A description of part of the proposed Network Standard
Graphics Protocol for transmitting graphics data within the ARPA
network. The particular aspects covered are related to the form and
content of graphics information sent from a source of graphical
information to a display package for output to a graphics console.",
URL="http://www.rfc-editor.org/rfc/rfc292.txt"
}

@TECHREPORT{rfc294,
AUTHOR="A. K. Bhushan",
TITLE={The Use of {"}Set Data Type{"} Transaction in File Transfer Protocol},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=294,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="Updates RFC 265.",
URL="http://www.rfc-editor.org/rfc/rfc294.txt"
}

@TECHREPORT{rfc295,
AUTHOR="J. B. Postel",
TITLE="Report of the Protocol Workshop, 12 October 1971",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=295,
PAGES=4,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="A report on the decisions reached at the protocol workshop
held in conjunction with the NWG meeting of 10 October 1971.",
URL="http://www.rfc-editor.org/rfc/rfc295.txt"
}

@TECHREPORT{rfc296,
AUTHOR="D. E. Liddle",
TITLE="{DS-1} display system",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=296,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="This RFC describes a proposed modular graphic/alphanumeric
display system containing a 512 by 512 line, 60 line per inch plasma
display/memory panel and a minprocessor. It is intended to combine the
advantages of display memory and local processing power in three general
modes."
}

@TECHREPORT{rfc297,
AUTHOR="D. C. Walden",
TITLE="{TIP} Message Buffers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=297,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="Discussion regarding the size of the TIP's message buffers.",
URL="http://www.rfc-editor.org/rfc/rfc297.txt"
}

@TECHREPORT{rfc299,
AUTHOR="D. Hopkin",
TITLE="Information Management System",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=299,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1972,
ABSTRACT="Announcement of intent to build an Information Management and
Statistical System for the ILLIAC IV.",
URL="http://www.rfc-editor.org/rfc/rfc299.txt"
}

@TECHREPORT{rfc300,
AUTHOR="J. B. North",
TITLE="{ARPA} Network mailing lists",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=300,
PAGES=9,
DAYS=15,
MONTH=jan,
YEAR=1972,
ABSTRACT="Obsoletes RFC 211.",
URL="http://www.rfc-editor.org/rfc/rfc300.txt"
}

@TECHREPORT{rfc301,
AUTHOR="R. Alter",
TITLE="{BBN} {IMP} {(#5)} and {NCC} Schedule March {4,} 1971",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=301,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1972,
ABSTRACT="BBN host will be down for a day for moving equipment.",
URL="http://www.rfc-editor.org/rfc/rfc301.txt"
}

@TECHREPORT{rfc302,
AUTHOR="R. F. Bryan",
TITLE="Exercising The {ARPANET}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=302,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1972,
ABSTRACT="Describes a class project to tryout hosts on the ARPANET.",
URL="http://www.rfc-editor.org/rfc/rfc302.txt"
}

@TECHREPORT{rfc304,
AUTHOR="D. B. McKay",
TITLE="Data management system proposal for the {ARPA} network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=304,
DAYS=15,
MONTH=feb,
YEAR=1972,
ABSTRACT="A proposal to provide a framework that will allow the ARPA
community to recognize and develop the necessary tools in a unified
manner enabling the network to manage its resources to the best
advantage of the user."
}

@TECHREPORT{rfc305,
AUTHOR="R. Alter",
TITLE="Unknown Host Numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=305,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1972,
ABSTRACT="Discusses testing of IMPs and notes that this may cause some
hosts to receive messages from unregistered addresses.",
URL="http://www.rfc-editor.org/rfc/rfc305.txt"
}

@TECHREPORT{rfc307,
AUTHOR="E. Harslem",
TITLE="Using network Remote Job Entry",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=307,
PAGES=6,
DAYS=15,
MONTH=feb,
YEAR=1972,
ABSTRACT="Announcement of a program on a PDP-10 allowing access to the
Remote Job Service (RJS) at UCLA.",
URL="http://www.rfc-editor.org/rfc/rfc307.txt"
}

@TECHREPORT{rfc308,
AUTHOR="M. Seriff",
TITLE="{ARPANET} host availability data",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=308,
PAGES=4,
DAYS=15,
MONTH=mar,
YEAR=1972,
ABSTRACT="A SURVEY program is up and working to aid in gathering
information on the availability of various Hosts on the ARPANET.",
URL="http://www.rfc-editor.org/rfc/rfc308.txt"
}

@TECHREPORT{rfc309,
AUTHOR="A. K. Bhushan",
TITLE="Data and File Transfer Workshop Announcement",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=309,
PAGES=6,
DAYS=15,
MONTH=mar,
YEAR=1972,
ABSTRACT="Describes plans for a meeting on FTP to be held April 1972.",
URL="http://www.rfc-editor.org/rfc/rfc309.txt"
}

@TECHREPORT{rfc310,
AUTHOR="A. K. Bhushan",
TITLE="Another Look at Data and File Transfer Protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=310,
PAGES=7,
DAYS=15,
MONTH=apr,
YEAR=1972,
ABSTRACT="This paper suggests some specific changes in DTP and FTP that
should make them more useful and/or simplify implementation.",
URL="http://www.rfc-editor.org/rfc/rfc310.txt"
}

@TECHREPORT{rfc311,
AUTHOR="R. F. Bryan",
TITLE="New Console Attachments to the {USCB} Host",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=311,
PAGES=2,
DAYS=15,
MONTH=feb,
YEAR=1972,
ABSTRACT="Describes types of terminals used at UCSB.",
URL="http://www.rfc-editor.org/rfc/rfc311.txt"
}

@TECHREPORT{rfc312,
AUTHOR="A. A. McKenzie",
TITLE="Proposed Change in {IMP-to-Host} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=312,
PAGES=2,
DAYS=15,
MONTH=mar,
YEAR=1972,
ABSTRACT="This RFC proposes a redefinition of the IMP-to-Host error
message types and the creation of additional IMP-to-Host error message
types. These changes should assist the Hosts in determining appropriate
recovery action without causing any serious reprogramming problems.",
URL="http://www.rfc-editor.org/rfc/rfc312.txt"
}

@TECHREPORT{rfc313,
AUTHOR="T. C. O'Sullivan",
TITLE="Computer based instruction",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=313,
PAGES=8,
DAYS=15,
MONTH=mar,
YEAR=1972,
ABSTRACT="This paper has two purposes: to solicit comments from the NWG
and others on how selected classes of resources of a General Purpose
Network might be applied to the field of Computer Based Instructions;
and initiate a dialog between interested parties on the problem of
Computer Base Instruction.",
URL="http://www.rfc-editor.org/rfc/rfc313.txt"
}

@TECHREPORT{rfc314,
AUTHOR="I. W. Cotton",
TITLE="Network Graphics Working Group Meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=314,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1972,
ABSTRACT="Describes plans for a graphics meeting to be held in April
1972.",
URL="http://www.rfc-editor.org/rfc/rfc314.txt"
}

@TECHREPORT{rfc316,
AUTHOR="D. B. McKay and A. Mullery",
TITLE="{ARPA} Network Data Management Working Group",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=316,
PAGES=7,
DAYS=15,
MONTH=feb,
YEAR=1972,
URL="http://www.rfc-editor.org/rfc/rfc316.txt"
}

@TECHREPORT{rfc317,
AUTHOR="J. B. Postel",
TITLE="Official {Host-Host} Protocol Modification: Assigned Link Numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=317,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1972,
ABSTRACT="Lists current Link number assignments. This RFC has been
replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc317.txt"
}

@TECHREPORT{rfc318,
AUTHOR="J. B. Postel",
TITLE="Telnet Protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=318,
PAGES=16,
DAYS=15,
MONTH=apr,
YEAR=1972,
ABSTRACT="Obsoletes RFC 158. This Telnet specification was effective for
several years.",
URL="http://www.rfc-editor.org/rfc/rfc318.txt"
}

@TECHREPORT{rfc320,
AUTHOR="R. Reddy",
TITLE="Workshop on Hard Copy Line Printers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=320,
DAYS=15,
MONTH=mar,
YEAR=1972,
ABSTRACT="Announcement of a one day workshop on the XCRIBL system at
CMU."
}

@TECHREPORT{rfc321,
AUTHOR="P. M. Karp",
TITLE="{CBI} Networking Activity at {MITRE}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=321,
PAGES=14,
DAYS=15,
MONTH=mar,
YEAR=1972,
ABSTRACT="Response to RFC 313 - comments on Computer Based Instruction.",
URL="http://www.rfc-editor.org/rfc/rfc321.txt"
}

@TECHREPORT{rfc322,
AUTHOR="V. G. Cerf and J. B. Postel",
TITLE="Well known socket numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=322,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1972,
ABSTRACT="Announcement of intent to catalog all sockets which are
supposed to be well-known.",
URL="http://www.rfc-editor.org/rfc/rfc322.txt"
}

@TECHREPORT{rfc323,
AUTHOR="V. G. Cerf",
TITLE="Formation of Network Measurement Group {(NMG)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=323,
PAGES=9,
DAYS=15,
MONTH=mar,
YEAR=1972,
ABSTRACT="Describes some network measurement results, some plans for
further measurement and the formation of an interest group.",
URL="http://www.rfc-editor.org/rfc/rfc323.txt"
}

@TECHREPORT{rfc324,
AUTHOR="J. B. Postel",
TITLE="{RJE} Protocol meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=324,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1972,
ABSTRACT="Announcement of a RJE Protocol meeting at UCLA.",
URL="http://www.rfc-editor.org/rfc/rfc324.txt"
}

@TECHREPORT{rfc325,
AUTHOR="G. W. Hicks",
TITLE="Network Remote Job Entry program - {NETRJS}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=325,
PAGES=9,
DAYS=15,
MONTH=apr,
YEAR=1972,
ABSTRACT="Report on the NETRJS running at the University of Utah.",
URL="http://www.rfc-editor.org/rfc/rfc325.txt"
}

@TECHREPORT{rfc327,
AUTHOR="A. K. Bhushan",
TITLE="Data and File Transfer workshop notes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=327,
PAGES=5,
DAYS=15,
MONTH=apr,
YEAR=1972,
URL="http://www.rfc-editor.org/rfc/rfc327.txt"
}

@TECHREPORT{rfc328,
AUTHOR="J. B. Postel",
TITLE="Suggested Telnet Protocol Changes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=328,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1972,
ABSTRACT="This RFC proposes changes to the Telnet protocol.",
URL="http://www.rfc-editor.org/rfc/rfc328.txt"
}

@TECHREPORT{rfc331,
AUTHOR="J. M. McQuillan",
TITLE="{IMP} System Change Notification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=331,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1972,
ABSTRACT="Announcement of the release of IMPSYS 2600.",
URL="http://www.rfc-editor.org/rfc/rfc331.txt"
}

@TECHREPORT{rfc333,
AUTHOR="R. D. Bressler and D. J. Murphy and D. C. Walden",
TITLE="Proposed experiment with a Message Switching Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=333,
PAGES=26,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT="This document attempts to sketch how one would organize the
lowest level host-host protocol in the ARPANET around Message Switching
Protocols (MSPs) and how this organization would affect the
implementation of the host software.",
URL="http://www.rfc-editor.org/rfc/rfc333.txt"
}

@TECHREPORT{rfc334,
AUTHOR="A. A. McKenzie",
TITLE="Network Use on May 8",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=334,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1972,
URL="http://www.rfc-editor.org/rfc/rfc334.txt"
}

@TECHREPORT{rfc335,
AUTHOR="R. F. Bryan",
TITLE="New Interface - {IMP/360}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=335,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT="Announcement of a new interface and requests to hear of any
difficulties network users encounter while operating with UCSB.",
URL="http://www.rfc-editor.org/rfc/rfc335.txt"
}

@TECHREPORT{rfc336,
AUTHOR="I. W. Cotton",
TITLE="Level 0 Graphic Input Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=336,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT="A description of the graphics input protocol as discussed at a
Network Graphics Working Group meeting.",
URL="http://www.rfc-editor.org/rfc/rfc336.txt"
}

@TECHREPORT{rfc338,
AUTHOR="R. Braden",
TITLE="{EBCDIC/ASCII} Mapping for Network {RJE}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=338,
PAGES=6,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT="This RFC proposes: to make all users of NETRJS aware of the
changed ASCII mapping; to call this problem to the attention of the
Network RJE Protocol committee; and to knowledge and support Joel
Winett's pioneering work in this area.",
URL="http://www.rfc-editor.org/rfc/rfc338.txt"
}

@TECHREPORT{rfc339,
AUTHOR="R. Thomas",
TITLE={{MLTNET:} A {"}Multi Telnet{"} Subsystem for Tenex},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=339,
PAGES=4,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT="This RFC describes MLTNET as a Telnet-like facility for Tenex
which enables a user to control a number of jobs, running on different
ARPANET hosts. MLTNET is currently a subsystem on the BBN-Tenex host.",
URL="http://www.rfc-editor.org/rfc/rfc339.txt"
}

@TECHREPORT{rfc340,
AUTHOR="T. C. O'Sullivan",
TITLE="Proposed Telnet Changes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=340,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT="A proposed change to the Telnet protocol calling for one
standard protocol and dropping the idea of minimum implementation.",
URL="http://www.rfc-editor.org/rfc/rfc340.txt"
}

@TECHREPORT{rfc345,
AUTHOR="K. C. Kelley",
TITLE="Interest in Mixed Integer Programming {(MPSX} on {NIC} {360/91} at {CCN)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=345,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT="Request for interested persons in the MPSX to contact author.",
URL="http://www.rfc-editor.org/rfc/rfc345.txt"
}

@TECHREPORT{rfc346,
AUTHOR="J. B. Postel",
TITLE="Satellite Considerations",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=346,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT="Discussion on using space satellite transmission links in the
ARPANET.",
URL="http://www.rfc-editor.org/rfc/rfc346.txt"
}

@TECHREPORT{rfc347,
AUTHOR="J. B. Postel",
TITLE="Echo process",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=347,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT={A RFC discussing debugging and measurement puposes for those
hosts which are willing to implement an {"}Echo{"} process. Old version;
see
RFC 862.},
URL="http://www.rfc-editor.org/rfc/rfc347.txt"
}

@TECHREPORT{rfc348,
AUTHOR="J. B. Postel",
TITLE="Discard Process",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=348,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT={A RFC discussing debugging and measurement puposes for those
hosts which are willing to implement a {"}Discard{"} process. Old version;
see RFC 863.},
URL="http://www.rfc-editor.org/rfc/rfc348.txt"
}

@TECHREPORT{rfc349,
AUTHOR="J. B. Postel",
TITLE="Proposed Standard Socket Numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=349,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT="A proposal to officially standardize socket number
assignments.",
URL="http://www.rfc-editor.org/rfc/rfc349.txt"
}

@TECHREPORT{rfc350,
AUTHOR="R. Stoughton",
TITLE="User Accounts for {UCSB} {On-Line} System",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=350,
PAGES=3,
DAYS=15,
MONTH=may,
YEAR=1972,
ABSTRACT="Announcement of new login parameters for the UCSB On-Line
System.",
URL="http://www.rfc-editor.org/rfc/rfc350.txt"
}

@TECHREPORT{rfc351,
AUTHOR="D. H. Crocker",
TITLE="Graphics information form for the {ARPANET} graphics resources notebook",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=351,
PAGES=2,
DAYS=15,
MONTH=jun,
YEAR=1972,
ABSTRACT="A questionnaire about the state of graphics resources at
various sites.",
URL="http://www.rfc-editor.org/rfc/rfc351.txt"
}

@TECHREPORT{rfc352,
AUTHOR="D. H. Crocker",
TITLE="{TIP} Site Information Form",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=352,
PAGES=3,
DAYS=15,
MONTH=jun,
YEAR=1972,
ABSTRACT="An information form to provide additional information for TIP
users of the NET.",
URL="http://www.rfc-editor.org/rfc/rfc352.txt"
}

@TECHREPORT{rfc354,
AUTHOR="A. K. Bhushan",
TITLE="File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=354,
PAGES=25,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT="This RFC obsoletes RFCs 264,265. The File Transfer Protocol
(FTP) is a protocol for file transfer between HOSTs on the ARPANET. The
primary function of FTP is to transfer files efficiently and reliably
among hosts and to allow the convenient use of remote file storage
capabilities.",
URL="http://www.rfc-editor.org/rfc/rfc354.txt"
}

@TECHREPORT{rfc355,
AUTHOR="J. Davidson",
TITLE="Response to {NWG/RFC} 346",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=355,
PAGES=3,
DAYS=15,
MONTH=jun,
YEAR=1972,
URL="http://www.rfc-editor.org/rfc/rfc355.txt"
}

@TECHREPORT{rfc356,
AUTHOR="R. Alter",
TITLE="{ARPA} Network Control Center",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=356,
PAGES=1,
DAYS=15,
MONTH=jun,
YEAR=1972,
ABSTRACT="Announcement of the NCC's new operation schedule.",
URL="http://www.rfc-editor.org/rfc/rfc356.txt"
}

@TECHREPORT{rfc357,
AUTHOR="J. Davidson",
TITLE="Echoing strategy for satellite links",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=357,
PAGES=13,
DAYS=15,
MONTH=jun,
YEAR=1972,
ABSTRACT="This document describes a strategy which will eliminate the
delay associated with simple echoing and allow the transmission delay to
be hidden in the cost of computation only. This scheme is proposed as an
optional addition to existing User Telnets; its use requires the
explicit support of a cooperating server process.",
URL="http://www.rfc-editor.org/rfc/rfc357.txt"
}

@TECHREPORT{rfc359,
AUTHOR="D. C. Walden",
TITLE="Status of the Release of the New {IMP} System {(2600)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=359,
PAGES=1,
DAYS=15,
MONTH=jun,
YEAR=1972,
ABSTRACT="Obsoletes RFC 343.",
URL="http://www.rfc-editor.org/rfc/rfc359.txt"
}

@TECHREPORT{rfc360,
AUTHOR="C. Holland",
TITLE="Proposed Remote Job Entry Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=360,
DAYS=15,
MONTH=jun,
YEAR=1972,
ABSTRACT="This protocol specifies the Network standard procedures for
remote job entry as a mechanism whereby a user at one location causes a
batch-processing job to be run at some other location."
}

@TECHREPORT{rfc361,
AUTHOR="R. D. Bressler",
TITLE="Deamon Processes on Host 106",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=361,
PAGES=1,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT="Deamon Processes on Host 106.",
URL="http://www.rfc-editor.org/rfc/rfc361.txt"
}

@TECHREPORT{rfc364,
AUTHOR="M. D. Abrams",
TITLE="Serving remote users on the {ARPANET}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=364,
PAGES=6,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT="This paper asserts that a problem exists in serving remote
users and offers a set of suggestions for its amelioration.",
URL="http://www.rfc-editor.org/rfc/rfc364.txt"
}

@TECHREPORT{rfc365,
AUTHOR="D. C. Walden",
TITLE="Letter to All {TIP} Users",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=365,
PAGES=5,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT={Descriptions of new commands that have recently been added to
the {"}TIP Users Guide{"}.},
URL="http://www.rfc-editor.org/rfc/rfc365.txt"
}

@TECHREPORT{rfc368,
AUTHOR="R. Braden",
TITLE={Comments on {"}Proposed Remote Job Entry Protocol{"}},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=368,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT="Suggestions on honing the final standard of the RJE protocol
(references RFC 360).",
URL="http://www.rfc-editor.org/rfc/rfc368.txt"
}

@TECHREPORT{rfc369,
AUTHOR="J. R. Pickens",
TITLE="Evaluation of {ARPANET} services {January-March,} 1972",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=369,
PAGES=11,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT="This paper provides descriptions, surveys, critiques of
ARPANET services, and suggestions for improvement.",
URL="http://www.rfc-editor.org/rfc/rfc369.txt"
}

@TECHREPORT{rfc371,
AUTHOR="R. E. Kahn",
TITLE="Demonstration at International Computer Communications Conference",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=371,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT="Observation and notes on the ICCC meeting demonstration.",
URL="http://www.rfc-editor.org/rfc/rfc371.txt"
}

@TECHREPORT{rfc372,
AUTHOR="R. W. Watson",
TITLE="Notes on a Conversation with Bob Kahn on the {ICCC}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=372,
PAGES=4,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT="Discussion on some aspects of the ICCC meeting demonstration.",
URL="http://www.rfc-editor.org/rfc/rfc372.txt"
}

@TECHREPORT{rfc373,
AUTHOR="J. McCarthy",
TITLE="Arbitrary Character Sets",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=373,
PAGES=4,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT="Suggests how to get arbitrary characters sets stored in
computers and to be able to display them on any CRT screen, edit them
using any keyboard, and print them on any printer.",
URL="http://www.rfc-editor.org/rfc/rfc373.txt"
}

@TECHREPORT{rfc374,
AUTHOR="A. A. McKenzie",
TITLE="{IMP} System Announcement",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=374,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT="Updates RFCs 331,343,359.",
URL="http://www.rfc-editor.org/rfc/rfc374.txt"
}

@TECHREPORT{rfc377,
AUTHOR="R. Braden",
TITLE="Using {TSO} via {ARPA} Network Virtual Terminal",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=377,
PAGES=4,
DAYS=15,
MONTH=aug,
YEAR=1972,
ABSTRACT="Announcement of IBM's Time Sharing Option (TSO) availability
at UCLA/CCN on Socket 1, using the standard Telnet protocol.",
URL="http://www.rfc-editor.org/rfc/rfc377.txt"
}

@TECHREPORT{rfc378,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (July {1972)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=378,
PAGES=3,
DAYS=15,
MONTH=aug,
YEAR=1972,
ABSTRACT="Traffic statistics for the month of July 1972.",
URL="http://www.rfc-editor.org/rfc/rfc378.txt"
}

@TECHREPORT{rfc379,
AUTHOR="R. Braden",
TITLE="Using {TSO} at {CCN}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=379,
PAGES=5,
DAYS=15,
MONTH=aug,
YEAR=1972,
ABSTRACT="Announcement that IBM's Time Sharing Option (TSO) is up on a
regularly scheduled basis at UCLA/CCN.",
URL="http://www.rfc-editor.org/rfc/rfc379.txt"
}

@TECHREPORT{rfc381,
AUTHOR="J. M. McQuillan",
TITLE="Three aids to improved network operation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=381,
PAGES=4,
DAYS=15,
MONTH=jul,
YEAR=1972,
ABSTRACT="Discusses helpful aids to improved network operation:
schedules of software maintenance, IMP-to-Host communication, and
network news service.",
URL="http://www.rfc-editor.org/rfc/rfc381.txt"
}

@TECHREPORT{rfc382,
AUTHOR="L. McDaniel",
TITLE="Mathematical Software on the {ARPA} Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=382,
PAGES=1,
DAYS=15,
MONTH=aug,
YEAR=1972,
ABSTRACT="Comments on the efforts to develop high quality libraries of
mathematical and statistical subroutines.",
URL="http://www.rfc-editor.org/rfc/rfc382.txt"
}

@TECHREPORT{rfc384,
AUTHOR="J. B. North",
TITLE="Official site idents for organizations in the {ARPA} Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=384,
PAGES=4,
DAYS=15,
MONTH=aug,
YEAR=1972,
ABSTRACT="Includes two lists, a list in alpha order and a list by Site
address. Obsoletes RFC 289.",
URL="http://www.rfc-editor.org/rfc/rfc384.txt"
}

@TECHREPORT{rfc385,
AUTHOR="A. K. Bhushan",
TITLE="Comments on the File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=385,
PAGES=6,
DAYS=15,
MONTH=aug,
YEAR=1972,
ABSTRACT="The comments in this document include errata, further
discussion, emphasis points, and additions to the protocol. Updates RFC
354.",
URL="http://www.rfc-editor.org/rfc/rfc385.txt"
}

@TECHREPORT{rfc386,
AUTHOR="B. Cosell and D. C. Walden",
TITLE="Letter to {TIP} users-2",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=386,
PAGES=5,
DAYS=15,
MONTH=aug,
YEAR=1972,
ABSTRACT="A second point of information letter to TIP users. Updates RFC
365.",
URL="http://www.rfc-editor.org/rfc/rfc386.txt"
}

@TECHREPORT{rfc387,
AUTHOR="K. C. Kelley and J. Meir",
TITLE="Some experiences in implementing Network Graphics Protocol Level 0",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=387,
PAGES=5,
DAYS=15,
MONTH=aug,
YEAR=1972,
URL="http://www.rfc-editor.org/rfc/rfc387.txt"
}

@TECHREPORT{rfc388,
AUTHOR="V. G. Cerf",
TITLE="{NCP} statistics",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=388,
PAGES=5,
DAYS=15,
MONTH=aug,
YEAR=1972,
ABSTRACT="Updates RFC 323. Announcement that UCLA/NMC is prepared to
gather NCP statistics on a daily basis.",
URL="http://www.rfc-editor.org/rfc/rfc388.txt"
}

@TECHREPORT{rfc389,
AUTHOR="B. Noble",
TITLE="{UCLA} Campus Computing Network Liaison Staff for {ARPA} Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=389,
PAGES=2,
DAYS=15,
MONTH=aug,
YEAR=1972,
ABSTRACT="A list for ARPA Network contacts at UCLA/CCN.",
URL="http://www.rfc-editor.org/rfc/rfc389.txt"
}

@TECHREPORT{rfc390,
AUTHOR="R. Braden",
TITLE="{TSO} Scenario",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=390,
PAGES=4,
DAYS=15,
MONTH=sep,
YEAR=1972,
ABSTRACT="An example session with TSO on UCLA-CCN.",
URL="http://www.rfc-editor.org/rfc/rfc390.txt"
}

@TECHREPORT{rfc391,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (August {1972)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=391,
PAGES=3,
DAYS=15,
MONTH=sep,
YEAR=1972,
ABSTRACT="A report on the Host traffic statistics for the month of
August 1972. Updates RFC 378.",
URL="http://www.rfc-editor.org/rfc/rfc391.txt"
}

@TECHREPORT{rfc392,
AUTHOR="G. W. Hicks and B. D. Wessler",
TITLE="Measurement of host costs for transmitting network data",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=392,
PAGES=6,
DAYS=15,
MONTH=sep,
YEAR=1972,
ABSTRACT={Discussion of Utah's development of a program to use the
Remote Job Service System (RJS) at UCLA-CCN in conjunction with Utah's
{"}batch{"} users.},
URL="http://www.rfc-editor.org/rfc/rfc392.txt"
}

@TECHREPORT{rfc393,
AUTHOR="J. M. Winett",
TITLE="Comments on Telnet Protocol Changes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=393,
PAGES=4,
DAYS=15,
MONTH=oct,
YEAR=1972,
ABSTRACT="Comments and objections to two of the three recent suggestions
for changing the Telnet protocol as described in RFC 328.",
URL="http://www.rfc-editor.org/rfc/rfc393.txt"
}

@TECHREPORT{rfc394,
AUTHOR="J. M. McQuillan",
TITLE="Two Proposed Changes to the {IMP-Host} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=394,
PAGES=3,
DAYS=15,
MONTH=sep,
YEAR=1972,
ABSTRACT="Updates RFC 381. This note describes two changes to the
IMP-Host communication protocol described in BBN Report 1822.",
URL="http://www.rfc-editor.org/rfc/rfc394.txt"
}

@TECHREPORT{rfc395,
AUTHOR="J. M. McQuillan",
TITLE="Switch Settings on {IMPs} and {TIPs}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=395,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1972,
ABSTRACT="Discussion on a description of the switches on the front panel
of IMPs and TIPs that are important to the correct operation of the
network software.",
URL="http://www.rfc-editor.org/rfc/rfc395.txt"
}

@TECHREPORT{rfc396,
AUTHOR="S. Bunch",
TITLE="Network Graphics Working Group Meeting - Second Iteration",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=396,
PAGES=1,
DAYS=15,
MONTH=nov,
YEAR=1972,
URL="http://www.rfc-editor.org/rfc/rfc396.txt"
}

@TECHREPORT{rfc398,
AUTHOR="J. R. Pickens and E. Faeh",
TITLE="{ICP} Sockets",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=398,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1972,
ABSTRACT="Announcement that users with Tektronix or IMLAC terminals, or
with systems that support the proposed Level 0 graphics protocol can
access UCSB graphics.",
URL="http://www.rfc-editor.org/rfc/rfc398.txt"
}

@TECHREPORT{rfc399,
AUTHOR="M. Krilanovich",
TITLE="{SMFS} Login and Logout",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=399,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1972,
URL="http://www.rfc-editor.org/rfc/rfc399.txt"
}

@TECHREPORT{rfc400,
AUTHOR="A. A. McKenzie",
TITLE="Traffic Statistics (September {1972)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=400,
PAGES=3,
DAYS=15,
MONTH=oct,
YEAR=1972,
ABSTRACT="A report on the Host traffic statistics for the month of
September 1972. Updates RFC 391.",
URL="http://www.rfc-editor.org/rfc/rfc400.txt"
}

@TECHREPORT{rfc401,
AUTHOR="J. E. Hansen",
TITLE="Conversion of {NGP-0} Coordinates to Device Specific Coordinates",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=401,
PAGES=2,
DAYS=15,
MONTH=oct,
YEAR=1972,
ABSTRACT="A means is described to convert NGP coordinates to interger
coordinates in the range zero to M, where M is the maximum address of
the device screen on a machine using 2's complement arithmetic.",
URL="http://www.rfc-editor.org/rfc/rfc401.txt"
}

@TECHREPORT{rfc404,
AUTHOR="A. A. McKenzie",
TITLE="Host Address Changes Involving Rand and {ISI}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=404,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1972,
ABSTRACT="The new address of ISI is IMP 22. THe new address of RAND is
IMP 7.",
URL="http://www.rfc-editor.org/rfc/rfc404.txt"
}

@TECHREPORT{rfc405,
AUTHOR="A. A. McKenzie",
TITLE="Correction to {RFC} 404",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=405,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1972,
ABSTRACT="Typographical error notation. Obsoletes RFC 404.",
URL="http://www.rfc-editor.org/rfc/rfc405.txt"
}

@TECHREPORT{rfc406,
AUTHOR="J. M. McQuillan",
TITLE="Scheduled {IMP} Software Releases",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=406,
PAGES=2,
DAYS=15,
MONTH=oct,
YEAR=1972,
ABSTRACT="Explains the plans and schedule for IMP software maintenance.",
URL="http://www.rfc-editor.org/rfc/rfc406.txt"
}

@TECHREPORT{rfc407,
AUTHOR="R. D. Bressler and R. Guida and A. A. McKenzie",
TITLE="Remote Job Entry Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=407,
DAYS=15,
MONTH=oct,
YEAR=1972,
ABSTRACT="The release of the official Remote Job Entry Protocol, per the
ARPA office.",
URL="http://www.rfc-editor.org/rfc/rfc407.txt"
}

@TECHREPORT{rfc408,
AUTHOR="A. D. Owen and J. B. Postel",
TITLE="{NETBANK}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=408,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1972,
ABSTRACT="A proposed idea for a protocol (or service) that is offered as
an aid to network use for new users.",
URL="http://www.rfc-editor.org/rfc/rfc408.txt"
}

@TECHREPORT{rfc409,
AUTHOR="J. A. White",
TITLE="Tenex interface to {UCSB's} {Simple-Minded} File System",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=409,
PAGES=8,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="This document is intended to provide users with the
information necessary to use SMFS from a terminal; the reader is assumed
familiar with Tenex.",
URL="http://www.rfc-editor.org/rfc/rfc409.txt"
}

@TECHREPORT{rfc410,
AUTHOR="J. M. McQuillan",
TITLE="Removal of the 30-Second Delay When Hosts Come Up",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=410,
PAGES=2,
DAYS=15,
MONTH=nov,
YEAR=1972,
ABSTRACT="A proposal to elminate the 30-second delay altogether.",
URL="http://www.rfc-editor.org/rfc/rfc410.txt"
}

@TECHREPORT{rfc411,
AUTHOR="M. A. Padlipsky",
TITLE="New {MULTICS} Network Software Features",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=411,
PAGES=2,
DAYS=15,
MONTH=nov,
YEAR=1972,
ABSTRACT="Discussion on two recently-installed features of the Multics
Network software.",
URL="http://www.rfc-editor.org/rfc/rfc411.txt"
}

@TECHREPORT{rfc412,
AUTHOR="G. W. Hicks",
TITLE="User {FTP} Documentation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=412,
PAGES=10,
DAYS=15,
MONTH=nov,
YEAR=1972,
ABSTRACT={A {"}help{"} file for the Utah-10 implementation of the User FTP
process.},
URL="http://www.rfc-editor.org/rfc/rfc412.txt"
}

@TECHREPORT{rfc413,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (October {1972)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=413,
PAGES=10,
DAYS=15,
MONTH=nov,
YEAR=1972,
ABSTRACT="Three sets of network traffic statistic reports. Updates RFC
400.",
URL="http://www.rfc-editor.org/rfc/rfc413.txt"
}

@TECHREPORT{rfc414,
AUTHOR="A. K. Bhushan",
TITLE="File Transfer Protocol {(FTP)} status and further comments",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=414,
PAGES=5,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="A status report on working server and user FTPs.",
URL="http://www.rfc-editor.org/rfc/rfc414.txt"
}

@TECHREPORT{rfc415,
AUTHOR="H. Murray",
TITLE="Tenex bandwidth",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=415,
PAGES=2,
DAYS=15,
MONTH=nov,
YEAR=1972,
ABSTRACT="Considerations of the performances of each host. References
RFC 392.",
URL="http://www.rfc-editor.org/rfc/rfc415.txt"
}

@TECHREPORT{rfc416,
AUTHOR="J. C. Norton",
TITLE="{ARC} System Will Be Unavailable for Use During Thanksgiving Week",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=416,
PAGES=2,
DAYS=15,
MONTH=nov,
YEAR=1972,
ABSTRACT="The SRI-ARC machine will be down for 9-10 days.",
URL="http://www.rfc-editor.org/rfc/rfc416.txt"
}

@TECHREPORT{rfc417,
AUTHOR="J. B. Postel and C. S. Kline",
TITLE="Link usage violation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=417,
PAGES=1,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="The protocol police issue a citation.",
URL="http://www.rfc-editor.org/rfc/rfc417.txt"
}

@TECHREPORT{rfc418,
AUTHOR="W. Hathaway",
TITLE="Server file transfer under {TSS/360} at {NASA} Ames",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=418,
DAYS=15,
MONTH=nov,
YEAR=1972,
ABSTRACT="This RFC is a description of the initial implementation of
Server File Transfer at NASA-Ames Research Center."
}

@TECHREPORT{rfc419,
AUTHOR="A. Vezza",
TITLE="To: Network liaisons and station agents",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=419,
PAGES=1,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="The MIT Dynamic Modeling System will be down for 2-4 weeks.",
URL="http://www.rfc-editor.org/rfc/rfc419.txt"
}

@TECHREPORT{rfc421,
AUTHOR="A. A. McKenzie",
TITLE="Software Consulting Service for Network Users",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=421,
DAYS=15,
MONTH=nov,
YEAR=1972,
ABSTRACT="An announcement of a BBN software consulting service that has
been established for ARPA network users.",
URL="http://www.rfc-editor.org/rfc/rfc421.txt"
}

@TECHREPORT{rfc422,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (November {1972)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=422,
PAGES=4,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="Report on the Host traffic statistics for the month of
November 1972. Updates RFC 413.",
URL="http://www.rfc-editor.org/rfc/rfc422.txt"
}

@TECHREPORT{rfc423,
AUTHOR="B. Noble",
TITLE="{UCLA} Campus Computing Network Liaison Staff for {ARPANET}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=423,
PAGES=2,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="A list of ARPA network contacts at CCN. Updates RFC 389.",
URL="http://www.rfc-editor.org/rfc/rfc423.txt"
}

@TECHREPORT{rfc425,
AUTHOR="R. D. Bressler",
TITLE={{"}But my {NCP} costs {$500} a day{"}},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=425,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="Discussion on the cost of network software and network use.",
URL="http://www.rfc-editor.org/rfc/rfc425.txt"
}

@TECHREPORT{rfc429,
AUTHOR="J. B. Postel",
TITLE="Character Generator Process",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=429,
PAGES=1,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="A proposal that there be a standard process implemented on
whatever hosts desire which generates character data with out any regard
to input.",
URL="http://www.rfc-editor.org/rfc/rfc429.txt"
}

@TECHREPORT{rfc431,
AUTHOR="M. Krilanovich",
TITLE="Update on {SMFS} Login and Logout",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=431,
PAGES=3,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="This document obsoletes RFC 399, which introduced the Login
and Logout commands for UCSB's SMFS, but was incomplete. RFC 399 is
restated more fully in this RFC.",
URL="http://www.rfc-editor.org/rfc/rfc431.txt"
}

@TECHREPORT{rfc432,
AUTHOR="N. Neigus",
TITLE="Network logical map",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=432,
PAGES=1,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="Attachment of the network logical map as of December 30, 1972.",
URL="http://www.rfc-editor.org/rfc/rfc432.txt"
}

@TECHREPORT{rfc433,
AUTHOR="J. B. Postel",
TITLE="Socket number list",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=433,
PAGES=5,
DAYS=15,
MONTH=dec,
YEAR=1972,
ABSTRACT="Establishment of assigned socket numbers to be used for public
functions. This RFC has been replaced by RFC 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc433.txt"
}

@TECHREPORT{rfc403,
AUTHOR="G. W. Hicks",
TITLE="Desirability of a network 1108 service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=403,
DAYS=15,
MONTH=jan,
YEAR=1973
}

@TECHREPORT{rfc420,
AUTHOR="H. Murray",
TITLE="{CCA} {ICCC} weather demo",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=420,
PAGES=8,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="Announcement that the weather demo for the ICCC show is now
generally available.",
URL="http://www.rfc-editor.org/rfc/rfc420.txt"
}

@TECHREPORT{rfc426,
AUTHOR="R. Thomas",
TITLE="Reconnection Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=426,
PAGES=12,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="This document describes several situations in which the
ability to reconnect is useful, presents a mechanism to achieve
reconnections, sketches how the mechanism could be added to Host-Host or
Telnet protocol, and recommends a place for the mechanism in the
protocol hierarchy.",
URL="http://www.rfc-editor.org/rfc/rfc426.txt"
}

@TECHREPORT{rfc430,
AUTHOR="R. Braden",
TITLE="Comments on File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=430,
PAGES=8,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="Discusses several issues in FTP.",
URL="http://www.rfc-editor.org/rfc/rfc430.txt"
}

@TECHREPORT{rfc434,
AUTHOR="A. A. McKenzie",
TITLE="{IMP/TIP} memory retrofit schedule",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=434,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="Explains plans and schedule for IMP and TIP upgrades.",
URL="http://www.rfc-editor.org/rfc/rfc434.txt"
}

@TECHREPORT{rfc435,
AUTHOR="B. Cosell and D. C. Walden",
TITLE="Telnet issues",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=435,
PAGES=10,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="This RFC discusses a number of Telnet related issues, with the
central issue of discussion being echoing.",
URL="http://www.rfc-editor.org/rfc/rfc435.txt"
}

@TECHREPORT{rfc436,
AUTHOR="M. Krilanovich",
TITLE="Announcement of {RJS} at {UCSB}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=436,
PAGES=1,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="Announcement of the availability of RJS at UCSB.",
URL="http://www.rfc-editor.org/rfc/rfc436.txt"
}

@TECHREPORT{rfc437,
AUTHOR="E. Faeh",
TITLE="Data Reconfiguration Service at {UCSB}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=437,
PAGES=10,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="Announcement of the availability of the Data Reconfiguration
Service (DRS) at UCSB.",
URL="http://www.rfc-editor.org/rfc/rfc437.txt"
}

@TECHREPORT{rfc438,
AUTHOR="R. Thomas and R. Clements",
TITLE="{FTP} server-server interaction",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=438,
PAGES=3,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="This document suggests a simple extension to FTP which would
allow a FTP user process at one site to arrange for FTP server processes
at other sites to act cooperatively on its behalf.",
URL="http://www.rfc-editor.org/rfc/rfc438.txt"
}

@TECHREPORT{rfc439,
AUTHOR="V. G. Cerf",
TITLE="{PARRY} encounters the {DOCTOR}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=439,
PAGES=7,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="A lighthearted documentation on a session that actually
happened on September 18, 1972.",
URL="http://www.rfc-editor.org/rfc/rfc439.txt"
}

@TECHREPORT{rfc440,
AUTHOR="D. C. Walden",
TITLE="Scheduled network software maintenance",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=440,
PAGES=1,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="Explains plans and schedule for IMP software maintenance,
expands the normal time slot.",
URL="http://www.rfc-editor.org/rfc/rfc440.txt"
}

@TECHREPORT{rfc441,
AUTHOR="R. D. Bressler and R. Thomas",
TITLE="{Inter-Entity} Communication - an experiment",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=441,
PAGES=7,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="A status report concerning an experiment based on the desire
of users, at their consoles, to converse with one another, and to
receive some debugging assistance.",
URL="http://www.rfc-editor.org/rfc/rfc441.txt"
}

@TECHREPORT{rfc442,
AUTHOR="V. G. Cerf",
TITLE="Current flow-control scheme for {IMPSYS}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=442,
PAGES=7,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="This RFC discusses the current flow-control scheme for IMPSYS.",
URL="http://www.rfc-editor.org/rfc/rfc442.txt"
}

@TECHREPORT{rfc443,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (December {1972)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=443,
PAGES=3,
DAYS=15,
MONTH=jan,
YEAR=1973,
ABSTRACT="Report on the Host traffic statistics for the month of
December 1972. Updates RFC 422.",
URL="http://www.rfc-editor.org/rfc/rfc443.txt"
}

@TECHREPORT{rfc445,
AUTHOR="A. A. McKenzie",
TITLE="{IMP/TIP} preventive maintenance schedule",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=445,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1973,
URL="http://www.rfc-editor.org/rfc/rfc445.txt"
}

@TECHREPORT{rfc446,
AUTHOR="L. P. Deutsch",
TITLE="Proposal to consider a network program resource notebook",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=446,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1973,
URL="http://www.rfc-editor.org/rfc/rfc446.txt"
}

@TECHREPORT{rfc447,
AUTHOR="Alex A. McKenzie",
TITLE="{IMP/TIP} Memory Retrofit Schedule (Revision {1)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=447,
MONTH=jan,
YEAR=1973,
URL="http://www.rfc-editor.org/rfc/rfc447.txt"
}

@TECHREPORT{rfc448,
AUTHOR="R. Braden",
TITLE="Print files in {FTP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=448,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="This document reviews the problem of print files.",
URL="http://www.rfc-editor.org/rfc/rfc448.txt"
}

@TECHREPORT{rfc449,
AUTHOR="D. C. Walden",
TITLE="The Current Flow-control Scheme for {IMPSYS.}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=449,
MONTH=jan,
YEAR=1973,
URL="http://www.rfc-editor.org/rfc/rfc449.txt"
}

@TECHREPORT{rfc450,
AUTHOR="M. A. Padlipsky",
TITLE="{MULTICS} sampling timeout change",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=450,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="Announcement of better service for experimental users of MIT
Multics.",
URL="http://www.rfc-editor.org/rfc/rfc450.txt"
}

@TECHREPORT{rfc451,
AUTHOR="M. A. Padlipsky",
TITLE="Tentative proposal for a Unified User Level Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=451,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="A suggestion for the idea of a network standard command
language for interactive systems.",
URL="http://www.rfc-editor.org/rfc/rfc451.txt"
}

@TECHREPORT{rfc452,
AUTHOR="J. M. Winett",
TITLE="{TELENET} Command at Host {LL}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=452,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="This RFC documents the use of the Telnet command at Host LL
for uses under the CP/CMS time-sharing system."
}

@TECHREPORT{rfc453,
AUTHOR="M. D. Kudlick",
TITLE="Meeting announcement to discuss a network mail system",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=453,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="Plans for a meeting on electronic mail held February 1973. See
RFC 469.",
URL="http://www.rfc-editor.org/rfc/rfc453.txt"
}

@TECHREPORT{rfc454,
AUTHOR="A. A. McKenzie",
TITLE="File Transfer Protocol - meeting announcement and a new proposed document",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=454,
PAGES=35,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="The specification of the File Transfer Protocol and the
announcement of a meeting (March 1973) to discuss it.",
URL="http://www.rfc-editor.org/rfc/rfc454.txt"
}

@TECHREPORT{rfc455,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (January {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=455,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="Report on the Host traffic statistics for the month of January
1973. Updates RFC 443.",
URL="http://www.rfc-editor.org/rfc/rfc455.txt"
}

@TECHREPORT{rfc456,
AUTHOR="M. D. Kudlick",
TITLE="Memorandum: Date change of mail meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=456,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="Change in the meeting time for the Network Mail meeting
discussed in RFC 453.",
URL="http://www.rfc-editor.org/rfc/rfc456.txt"
}

@TECHREPORT{rfc457,
AUTHOR="D. C. Walden",
TITLE="{TIPUG}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=457,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="How to get updates to the TIP Users Guide.",
URL="http://www.rfc-editor.org/rfc/rfc457.txt"
}

@TECHREPORT{rfc458,
AUTHOR="R. D. Bressler and R. Thomas",
TITLE="Mail retrieval via {FTP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=458,
PAGES=2,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="Proposal of two new FTP commands called ReaDMailFile and
ReaDMail.",
URL="http://www.rfc-editor.org/rfc/rfc458.txt"
}

@TECHREPORT{rfc459,
AUTHOR="W. Kantrowitz",
TITLE="Network questionnaires",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=459,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="Suggests that there is too much or too many different people
trying to gather data from all the other sites.",
URL="http://www.rfc-editor.org/rfc/rfc459.txt"
}

@TECHREPORT{rfc460,
AUTHOR="C. S. Kline",
TITLE="{NCP} survey",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=460,
PAGES=7,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="This RFC is a first in a series which will request information
on implmentation of host-to-host protocol.",
URL="http://www.rfc-editor.org/rfc/rfc460.txt"
}

@TECHREPORT{rfc461,
AUTHOR="A. A. McKenzie",
TITLE="Telnet Protocol meeting announcement",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=461,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="Plans for a meeting on Telnet to be held March 1973.",
URL="http://www.rfc-editor.org/rfc/rfc461.txt"
}

@TECHREPORT{rfc462,
AUTHOR="J. Iseli and D. H. Crocker",
TITLE="Responding to user needs",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=462,
PAGES=2,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="A proposal to have network documentation maintained at the
source, that is, by each site, and available as a distributed database.",
URL="http://www.rfc-editor.org/rfc/rfc462.txt"
}

@TECHREPORT{rfc463,
AUTHOR="A. K. Bhushan",
TITLE="{FTP} comments and response to {RFC} 430",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=463,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="This RFC represents the author's response to RFC 430 and other
similar views.",
URL="http://www.rfc-editor.org/rfc/rfc463.txt"
}

@TECHREPORT{rfc464,
AUTHOR="M. D. Kudlick",
TITLE="Resource notebook framework",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=464,
PAGES=2,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT={This document presents a framework for coordinating all the
surveys and data gathering efforts concerned with {"}resource notebook{"}
type of information.},
URL="http://www.rfc-editor.org/rfc/rfc464.txt"
}

@TECHREPORT{rfc466,
AUTHOR="J. M. Winett",
TITLE="Telnet logger/server for host {LL-67}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=466,
PAGES=9,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="This RFC contains writeup documents on the Telnet
Logger/Server for the CP/CMS system on the Lincoln Laboratory 360/67.",
URL="http://www.rfc-editor.org/rfc/rfc466.txt"
}

@TECHREPORT{rfc467,
AUTHOR="Jerry Burchfiel and Raymond Tomlinson",
TITLE="Proposed change to {Host-Host} Protocol: Resynchronization of connection
status",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=467,
PAGES=7,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="To achieve resynchronization of allocation, this RFC proposes
the addition of two commands to the host-host protocol.",
URL="http://www.rfc-editor.org/rfc/rfc467.txt"
}

@TECHREPORT{rfc468,
AUTHOR="R. Braden",
TITLE="{FTP} data compression",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=468,
PAGES=7,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT={This RFC describes the definition of the {"}HASP{"} or compressed
mode.},
URL="http://www.rfc-editor.org/rfc/rfc468.txt"
}

@TECHREPORT{rfc469,
AUTHOR="M. D. Kudlick",
TITLE="Network mail meeting summary",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=469,
PAGES=10,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="A description of a meeting on mail held February 1973.",
URL="http://www.rfc-editor.org/rfc/rfc469.txt"
}

@TECHREPORT{rfc470,
AUTHOR="R. Thomas",
TITLE="Change in socket for {TIP} news facility",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=470,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1973,
URL="http://www.rfc-editor.org/rfc/rfc470.txt"
}

@TECHREPORT{rfc471,
AUTHOR="R. Thomas",
TITLE="Workshop on multi-site executive programs",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=471,
PAGES=2,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="A suggestion for a workshop and a query for interest.",
URL="http://www.rfc-editor.org/rfc/rfc471.txt"
}

@TECHREPORT{rfc472,
AUTHOR="S. Bunch",
TITLE="Illinois' reply to Maxwell's request for graphics information {(NIC}
{14925)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=472,
PAGES=2,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="This RFC represents the author's response to NIC document
14925.",
URL="http://www.rfc-editor.org/rfc/rfc472.txt"
}

@TECHREPORT{rfc473,
AUTHOR="D. C. Walden",
TITLE="{MIX} and {MIXAL?}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=473,
PAGES=1,
DAYS=15,
MONTH=feb,
YEAR=1973,
URL="http://www.rfc-editor.org/rfc/rfc473.txt"
}

@TECHREPORT{rfc474,
AUTHOR="S. Bunch",
TITLE="Announcement of {NGWG} meeting: Call for papers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=474,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="Plans for a graphics meeting to be held in May 1973.",
URL="http://www.rfc-editor.org/rfc/rfc474.txt"
}

@TECHREPORT{rfc475,
AUTHOR="A. K. Bhushan",
TITLE="{FTP} and network mail system",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=475,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="This paper describes the author's understanding of the results
of the Network Mail System meeting and the implications for FTP."
}

@TECHREPORT{rfc476,
AUTHOR="A. A. McKenzie",
TITLE="{IMP/TIP} memory retrofit schedule (rev {2)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=476,
PAGES=2,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="Describes plans and schedule for upgrading IMPs and TIPs.",
URL="http://www.rfc-editor.org/rfc/rfc476.txt"
}

@TECHREPORT{rfc477,
AUTHOR="M. Krilanovich",
TITLE="Remote Job Service at {UCSB}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=477,
PAGES=19,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="This RFC is the follow-on document to RFC 436. This document
restates the essence of the official RJE Protocol and documents in
detail UCSB's implementation of it. Obsoletes RFC 436.",
URL="http://www.rfc-editor.org/rfc/rfc477.txt"
}

@TECHREPORT{rfc478,
AUTHOR="R. D. Bressler and R. Thomas",
TITLE="{FTP} server-server interaction - {II}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=478,
PAGES=2,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="Discusses server-server interaction where, in a typical
situation, a user conversing with two servers is interested in
retrieving a file from one site and sending it to another.",
URL="http://www.rfc-editor.org/rfc/rfc478.txt"
}

@TECHREPORT{rfc479,
AUTHOR="J. A. White",
TITLE="Use of {FTP} by the {NIC} Journal",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=479,
PAGES=5,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="This RFC states how the NIC outlined its requirements for
implementing FTP Journal delivery and submission.",
URL="http://www.rfc-editor.org/rfc/rfc479.txt"
}

@TECHREPORT{rfc480,
AUTHOR="J. A. White",
TITLE="Host-dependent {FTP} parameters",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=480,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="This memo is in response to RFC 430.",
URL="http://www.rfc-editor.org/rfc/rfc480.txt"
}

@TECHREPORT{rfc482,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (February {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=482,
PAGES=4,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="A report on the Host traffic statistics for the month of
February 1973. Updates RFC 455.",
URL="http://www.rfc-editor.org/rfc/rfc482.txt"
}

@TECHREPORT{rfc483,
AUTHOR="M. D. Kudlick",
TITLE="Cancellation of the resource notebook framework meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=483,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1973,
URL="http://www.rfc-editor.org/rfc/rfc483.txt"
}

@TECHREPORT{rfc485,
AUTHOR="J. R. Pickens",
TITLE="{MIX} and {MIXAL} at {UCSB}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=485,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="A response to Walden's MIX query (RFC 473).",
URL="http://www.rfc-editor.org/rfc/rfc485.txt"
}

@TECHREPORT{rfc486,
AUTHOR="R. D. Bressler",
TITLE="Data transfer revisited",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=486,
PAGES=2,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="A proposeal to base RJE and FTP on a common data transfer
protocol.",
URL="http://www.rfc-editor.org/rfc/rfc486.txt"
}

@TECHREPORT{rfc487,
AUTHOR="R. D. Bressler",
TITLE="Free file transfer",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=487,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="This memo is in response to RFC 430.",
URL="http://www.rfc-editor.org/rfc/rfc487.txt"
}

@TECHREPORT{rfc488,
AUTHOR="M. F. Auerbach",
TITLE="{NLS} classes at network sites",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=488,
PAGES=2,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="This RFC solicits comments from the Network community on the
desirability of doing on-site classes.",
URL="http://www.rfc-editor.org/rfc/rfc488.txt"
}

@TECHREPORT{rfc489,
AUTHOR="J. B. Postel",
TITLE="Comment on resynchronization of connection status proposal",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=489,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="Comments on ideas proposed in RFC 467.",
URL="http://www.rfc-editor.org/rfc/rfc489.txt"
}

@TECHREPORT{rfc490,
AUTHOR="J. R. Pickens",
TITLE="Surrogate {RJS} for {UCLA-CCN}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=490,
PAGES=6,
DAYS=15,
MONTH=mar,
YEAR=1973,
ABSTRACT="A description of how UCLA's RJS can be accessed from UCSB's
standard remote job entry service.",
URL="http://www.rfc-editor.org/rfc/rfc490.txt"
}

@TECHREPORT{rfc491,
AUTHOR="M. A. Padlipsky",
TITLE={What is {"}Free{"}?},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=491,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="This memo discusses the assertion that network mail should be
free; i.e., no login or USER command should be required.",
URL="http://www.rfc-editor.org/rfc/rfc491.txt"
}

@TECHREPORT{rfc492,
AUTHOR="E. Meyer",
TITLE="Response to {RFC} 467",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=492,
PAGES=7,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="This document briefly describes the problems and proposed
solutions, offers comments and alternative suggestions in response to
RFC 467.",
URL="http://www.rfc-editor.org/rfc/rfc492.txt"
}

@TECHREPORT{rfc493,
AUTHOR="J. C. Michener and I. W. Cotton and K. C. Kelley and D. E. Liddle and E.
Meyer",
TITLE="Graphics Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=493,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="Discuses the opinions and decisions reached at the second
meeting of the Network Graphics Group."
}

@TECHREPORT{rfc494,
AUTHOR="D. C. Walden",
TITLE="Availability of {MIX} and {MIXAL} in the Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=494,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="A list of hosts that support programming in MIX and MIXAL.",
URL="http://www.rfc-editor.org/rfc/rfc494.txt"
}

@TECHREPORT{rfc495,
AUTHOR="A. A. McKenzie",
TITLE="Telnet Protocol specifications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=495,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="Results of an open meeting discussing Telnet, with two
attached documents which report the results of that meeting.",
URL="http://www.rfc-editor.org/rfc/rfc495.txt"
}

@TECHREPORT{rfc496,
AUTHOR="M. F. Auerbach",
TITLE="{TNLS} quick reference card is available",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=496,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="Announcement of a new TNLS Quick Reference Card.",
URL="http://www.rfc-editor.org/rfc/rfc496.txt"
}

@TECHREPORT{rfc497,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (March {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=497,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="A report on the Host traffic statistics for the month of March
1973. Updates RFC 482."
}

@TECHREPORT{rfc498,
AUTHOR="R. Braden",
TITLE="On mail service to {CCN}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=498,
PAGES=3,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="A description of the electronic mail service at UCLA-CCN.",
URL="http://www.rfc-editor.org/rfc/rfc498.txt"
}

@TECHREPORT{rfc499,
AUTHOR="B. R. Reussow",
TITLE="Harvard's network {RJE}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=499,
PAGES=6,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="A description of the remote job entry service at Harvard.",
URL="http://www.rfc-editor.org/rfc/rfc499.txt"
}

@TECHREPORT{rfc500,
AUTHOR="A. Shoshani and I. Spiegler",
TITLE="Integration of data management systems on a computer network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=500,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="In this paper, discussion is focused on an approach to
integrating data management systems on a computer network for the
purpose of data sharing."
}

@TECHREPORT{rfc501,
AUTHOR="K. T. Pogran",
TITLE={Un-muddling {"}free file transfer{"}},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=501,
PAGES=5,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="This memo is in response to RFC 487.",
URL="http://www.rfc-editor.org/rfc/rfc501.txt"
}

@TECHREPORT{rfc503,
AUTHOR="N. Neigus and J. B. Postel",
TITLE="Socket number list",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=503,
PAGES=8,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="This RFC has been replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc503.txt"
}

@TECHREPORT{rfc504,
AUTHOR="R. Thomas",
TITLE="Distributed resources workshop announcement",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=504,
PAGES=5,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="Detailed plans for a workshop on Automated Resource Sharing to
be held May 1973.",
URL="http://www.rfc-editor.org/rfc/rfc504.txt"
}

@TECHREPORT{rfc505,
AUTHOR="M. A. Padlipsky",
TITLE="Two solutions to a file transfer access problem",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=505,
PAGES=3,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="This memo is in response to RFCs 487 and 501.",
URL="http://www.rfc-editor.org/rfc/rfc505.txt"
}

@TECHREPORT{rfc506,
AUTHOR="M. A. Padlipsky",
TITLE="{FTP} command naming problem",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=506,
PAGES=1,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="This RFC discusses a problem when using the File Transfer
Protocol: the choice of names for two crucial commands is faulty.",
URL="http://www.rfc-editor.org/rfc/rfc506.txt"
}

@TECHREPORT{rfc508,
AUTHOR="L. Pfeifer and J. McAfee",
TITLE="Real-time data transmission on the {ARPANET}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=508,
PAGES=10,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="Discussion on the pros and cons of support of real-time
processes on the ARPA Network.",
URL="http://www.rfc-editor.org/rfc/rfc508.txt"
}

@TECHREPORT{rfc509,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (April {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=509,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1973,
ABSTRACT="A report on the Host traffic statistics for the month of April
1973. Updates RFC 497.",
URL="http://www.rfc-editor.org/rfc/rfc509.txt"
}

@TECHREPORT{rfc510,
AUTHOR="J. A. White",
TITLE="Request for network mailbox addresses",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=510,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="Announcement of Network Journal delivery by the NIC and a
request for updated/additional network mailbox addresses.",
URL="http://www.rfc-editor.org/rfc/rfc510.txt"
}

@TECHREPORT{rfc511,
AUTHOR="J. B. North",
TITLE="Enterprise phone service to {NIC} from {ARPANET} sites",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=511,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="Discussion of cost and alternatives for special telephone
numbers for the NIC.",
URL="http://www.rfc-editor.org/rfc/rfc511.txt"
}

@TECHREPORT{rfc512,
AUTHOR="W. Hathaway",
TITLE="More on lost message detection",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=512,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="This RFC is replaced by RFC 534.",
URL="http://www.rfc-editor.org/rfc/rfc512.txt"
}

@TECHREPORT{rfc513,
AUTHOR="W. Hathaway",
TITLE="Comments on the new Telnet specifications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=513,
PAGES=3,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="Discussion of the Telnet Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc513.txt"
}

@TECHREPORT{rfc514,
AUTHOR="W. Kantrowitz",
TITLE="Network make-work",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=514,
PAGES=4,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="Updates RFC 459.",
URL="http://www.rfc-editor.org/rfc/rfc514.txt"
}

@TECHREPORT{rfc515,
AUTHOR="R. Winter",
TITLE="Specifications for datalanguage: Version {0/9}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=515,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="This specification for Datalanguage is extremely primitive.
Version 0/9 is currently running at CCA and offers an opportunity for
experience with the Datacomputer and with fundamental Datalanguage
concepts."
}

@TECHREPORT{rfc516,
AUTHOR="D. C. Walden",
TITLE="Lost message detection",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=516,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="This RFC is replaced by RFC 534.",
URL="http://www.rfc-editor.org/rfc/rfc516.txt"
}

@TECHREPORT{rfc518,
AUTHOR="N. Vaughan and Elizabeth J. Feinler",
TITLE="{ARPANET} accounts",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=518,
PAGES=9,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="A memo on information regarding opening an account at a given
site on the ARPANET.",
URL="http://www.rfc-editor.org/rfc/rfc518.txt"
}

@TECHREPORT{rfc519,
AUTHOR="J. R. Pickens",
TITLE="Resource evaluation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=519,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="UCSB announces a new test group based upon RFC 369, which
attempts to take a detailed look at specific network resources and
develop initial site dependent and function dependent MINIMAN's."
}

@TECHREPORT{rfc520,
AUTHOR="John Day",
TITLE="Memo to {FTP} group: Proposal for File Access Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=520,
PAGES=8,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="This document discusses the File Access Protocol as an
extension to FTP.",
URL="http://www.rfc-editor.org/rfc/rfc520.txt"
}

@TECHREPORT{rfc521,
AUTHOR="A. A. McKenzie",
TITLE="Restricted use of {IMP} {DDT}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=521,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="Proposal of restricted use of IMP DDT due to opinions from
representatives of several sites feeling that uncontrolled use of IMP
DDT made access control mechanisms too vulnerable to interception or
tampering.",
URL="http://www.rfc-editor.org/rfc/rfc521.txt"
}

@TECHREPORT{rfc522,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (May {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=522,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="A report on the Host traffic statistics for the month of May
1973. Updates RFC 509."
}

@TECHREPORT{rfc523,
AUTHOR="A. K. Bhushan",
TITLE="{SURVEY} is in operation again",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=523,
PAGES=2,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="The purpose of this RFC is to alert the network community that
the survey program at MIT-DMCG computer system is in operation.",
URL="http://www.rfc-editor.org/rfc/rfc523.txt"
}

@TECHREPORT{rfc524,
AUTHOR="J. A. White",
TITLE="Proposed Mail Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=524,
PAGES=40,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="A proposed specification for handling mail in the ARPA
network.",
URL="http://www.rfc-editor.org/rfc/rfc524.txt"
}

@TECHREPORT{rfc525,
AUTHOR="W. Parrish and J. R. Pickens",
TITLE="{MIT-MATHLAB} meets {UCSB-OLS} -an example of resource sharing",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=525,
PAGES=9,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="A description of problem solving using both the MIT-P1ACSYM
system and the UCSB-OLS system.",
URL="http://www.rfc-editor.org/rfc/rfc525.txt"
}

@TECHREPORT{rfc526,
AUTHOR="W. K. Pratt",
TITLE="Technical meeting: Digital image processing software systems",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=526,
PAGES=3,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="Announcement of a technical meeting on digital image
processing software systems.",
URL="http://www.rfc-editor.org/rfc/rfc526.txt"
}

@TECHREPORT{rfc527,
AUTHOR="R. Merryman",
TITLE="{ARPAWOCKY}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=527,
DAYS=15,
MONTH=may,
YEAR=1973,
ABSTRACT="A parody by D. L. Covill of the ARPANET based on the
Jabberwocky of Lewis Carroll",
URL="http://www.rfc-editor.org/rfc/rfc527.txt"
}

@TECHREPORT{rfc528,
AUTHOR="J. M. McQuillan",
TITLE="Software checksumming in the {IMP} and network reliability",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=528,
PAGES=9,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="A description of some of the modifications that have recently
been made to the IMP and TIP programs.",
URL="http://www.rfc-editor.org/rfc/rfc528.txt"
}

@TECHREPORT{rfc529,
AUTHOR="A. A. McKenzie and R. Thomas and Raymond Tomlinson and K. T. Pogran",
TITLE="Note on protocol synch sequences",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=529,
PAGES=4,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="A response to RFC 513.",
URL="http://www.rfc-editor.org/rfc/rfc529.txt"
}

@TECHREPORT{rfc530,
AUTHOR="A. K. Bhushan",
TITLE="Report on the Survey project",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=530,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="The purpose of this paper is 1) to report on the status of the
SURVEY project and current data, 2) to inform the ARPANET community of
the services offered related to this project, 3) to report on future
plans, and 4) to ask for suggestions and improvements."
}

@TECHREPORT{rfc531,
AUTHOR="M. A. Padlipsky",
TITLE="Feast or famine? A response to two recent {RFC's} about network information",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=531,
PAGES=2,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="This memo is in response to RFCs 514 and 519.",
URL="http://www.rfc-editor.org/rfc/rfc531.txt"
}

@TECHREPORT{rfc532,
AUTHOR="R. Merryman",
TITLE="{UCSD-CC} {Server-FTP} facility",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=532,
PAGES=4,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="A description of the FTP service at UCSD.",
URL="http://www.rfc-editor.org/rfc/rfc532.txt"
}

@TECHREPORT{rfc533,
AUTHOR="D. C. Walden",
TITLE="{Message-ID} numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=533,
PAGES=1,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="Notice that the ARPANET link field of 8-bits has been expanded
to 12-bits and renamed the message-id field.",
URL="http://www.rfc-editor.org/rfc/rfc533.txt"
}

@TECHREPORT{rfc535,
AUTHOR="R. Thomas",
TITLE="Comments on File Access Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=535,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="This memo is in response to RFC 420."
}

@TECHREPORT{rfc537,
AUTHOR="S. Bunch",
TITLE="Announcement of {NGG} meeting July {16-17}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=537,
PAGES=2,
DAYS=15,
MONTH=jun,
YEAR=1973,
ABSTRACT="Arrangement details for a graphics meeting held July 1973. See
RFC 549.",
URL="http://www.rfc-editor.org/rfc/rfc537.txt"
}

@TECHREPORT{rfc538,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (June {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=538,
PAGES=4,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="A report on the Host traffic statistics for the month of June
1973. Updates RFC 522.",
URL="http://www.rfc-editor.org/rfc/rfc538.txt"
}

@TECHREPORT{rfc539,
AUTHOR="D. H. Crocker and J. B. Postel",
TITLE="Thoughts on the mail protocol proposed in {RFC} 524",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=539,
PAGES=3,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="This memo is in response to RFC 524. In general, the authors
of this RFC feel that the protocol is extremely rich. They also feel
that there are some minor and some major problems.",
URL="http://www.rfc-editor.org/rfc/rfc539.txt"
}

@TECHREPORT{rfc542,
AUTHOR="N. Neigus",
TITLE="File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=542,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT={This RFC states that there are considerable changes from the
last {"}official{"} version of FTP, but the gross structure still remains
the same. References RFCs 354, 454, and 495.},
URL="http://www.rfc-editor.org/rfc/rfc542.txt"
}

@TECHREPORT{rfc543,
AUTHOR="N. D. Meyer",
TITLE="Network journal submission and delivery",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=543,
PAGES=8,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="Announcement that the first implementation of a Network
Journal Submission and Delivery system is now experimentally up.",
URL="http://www.rfc-editor.org/rfc/rfc543.txt"
}

@TECHREPORT{rfc544,
AUTHOR="N. D. Meyer and K. C. Kelley",
TITLE="Locating on-line documentation at {SRI-ARC}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=544,
PAGES=1,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="Updated memo on how to access on-line documentation at the
NIC.",
URL="http://www.rfc-editor.org/rfc/rfc544.txt"
}

@TECHREPORT{rfc545,
AUTHOR="J. R. Pickens",
TITLE="Of what quality be the {UCSB} resources evaluators?",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=545,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="This memo is in response to RFC 531.",
URL="http://www.rfc-editor.org/rfc/rfc545.txt"
}

@TECHREPORT{rfc546,
AUTHOR="R. Thomas",
TITLE="Tenex load averages for July 1973",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=546,
PAGES=4,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT="Report on the load on two of the key service computers on the
ARPANET.",
URL="http://www.rfc-editor.org/rfc/rfc546.txt"
}

@TECHREPORT{rfc547,
AUTHOR="D. C. Walden",
TITLE="Change to the Very Distant Host specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=547,
PAGES=3,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT="A document on a new version of figure F-4 for BBN Report 1822.",
URL="http://www.rfc-editor.org/rfc/rfc547.txt"
}

@TECHREPORT{rfc548,
AUTHOR="D. C. Walden",
TITLE="Hosts using the {IMP} Going Down message",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=548,
PAGES=1,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT={Discusses the user and intention of the ARPANET IMP's {"}going
down{"} message.},
URL="http://www.rfc-editor.org/rfc/rfc548.txt"
}

@TECHREPORT{rfc549,
AUTHOR="J. C. Michener",
TITLE="Minutes of Network Graphics Group meeting, {15-17} July 1973",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=549,
PAGES=12,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="Description of a meeting on graphics held in July 1973.",
URL="http://www.rfc-editor.org/rfc/rfc549.txt"
}

@TECHREPORT{rfc550,
AUTHOR="L. P. Deutsch",
TITLE="{NIC} {NCP} experiment",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=550,
PAGES=2,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT="Statistics on total incoming messages, incoming host-host
control opcodes, and size of outgoing messages.",
URL="http://www.rfc-editor.org/rfc/rfc550.txt"
}

@TECHREPORT{rfc552,
AUTHOR="A. D. Owen",
TITLE="Single access to standard protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=552,
PAGES=1,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="Queries and statements regarding a socket number assignment
for a single access protocol before the proposed mail protocol becomes
official.",
URL="http://www.rfc-editor.org/rfc/rfc552.txt"
}

@TECHREPORT{rfc553,
AUTHOR="C. Irby and K. Victor",
TITLE="Draft design for a text/graphics protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=553,
PAGES=19,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="This document was proposed as a synthesis of existing ideas
rather than an attempt to put forth new ones. It draws upon the concerns
about the lack of text-handling capabilities of the protoocl suggested
in RFC 493.",
URL="http://www.rfc-editor.org/rfc/rfc553.txt"
}

@TECHREPORT{rfc555,
AUTHOR="J. A. White",
TITLE="Responses to critiques of the proposed mail protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=555,
PAGES=11,
DAYS=15,
MONTH=jul,
YEAR=1973,
ABSTRACT="Response to the proposal for a Mail Protocol (RFC 524).",
URL="http://www.rfc-editor.org/rfc/rfc555.txt"
}

@TECHREPORT{rfc556,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (July {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=556,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT="A report on the Host traffic statistics for the month of July
1973. Updates RFC 538."
}

@TECHREPORT{rfc557,
AUTHOR="B. D. Wessler",
TITLE="Revelations in network host measurements",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=557,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT="A report to the RFC community on the current network host
measurements."
}

@TECHREPORT{rfc559,
AUTHOR="A. K. Bushan",
TITLE="Comments on The New Telnet Protocol and its Implementation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=559,
PAGES=5,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT="This RFC describes the experience that MIT-DM had with the
implementation of the new Telnet protocol (both server and user).",
URL="http://www.rfc-editor.org/rfc/rfc559.txt"
}

@TECHREPORT{rfc560,
AUTHOR="D. H. Crocker and J. B. Postel",
TITLE="Remote Controlled Transmission and Echoing Telnet option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=560,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT="Defines a Telnet option for detailed control of echoing to
promote interactive use on long delay paths."
}

@TECHREPORT{rfc561,
AUTHOR="A. K. Bhushan and K. T. Pogran and Raymond Tomlinson and J. A. White",
TITLE="Standardizing Network Mail Headers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=561,
DAYS=15,
MONTH=sep,
YEAR=1973,
ABSTRACT="A proposed document for the explicit specification of such
header information as author, title, and date within the current FTP
mail protocol.",
URL="http://www.rfc-editor.org/rfc/rfc561.txt"
}

@TECHREPORT{rfc562,
AUTHOR="A. A. McKenzie",
TITLE="Modifications to the Telnet specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=562,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT="Presenting two documents that update RFC 495, plus summarizing
the changes."
}

@TECHREPORT{rfc563,
AUTHOR="J. Davidson",
TITLE="Comments on the {RCTE} Telnet option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=563,
PAGES=5,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT="A critique based on inferences drawn from the sample Tenex
interaction in RFC 560.",
URL="http://www.rfc-editor.org/rfc/rfc563.txt"
}

@TECHREPORT{rfc565,
AUTHOR="D. G. Cantor",
TITLE="Storing network survey data at the datacomputer",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=565,
PAGES=5,
DAYS=15,
MONTH=aug,
YEAR=1973,
ABSTRACT="A project summary report describing the programs developed and
implemented that have been operating successfully with the datacomputer
since July 10.",
URL="http://www.rfc-editor.org/rfc/rfc565.txt"
}

@TECHREPORT{rfc566,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (August {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=566,
PAGES=4,
DAYS=15,
MONTH=sep,
YEAR=1973,
ABSTRACT="A report on the Host traffic statistics for the month of
August 1973. Updates RFC 556.",
URL="http://www.rfc-editor.org/rfc/rfc566.txt"
}

@TECHREPORT{rfc567,
AUTHOR="L. P. Deutsch",
TITLE="Cross Country Network Bandwidth",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=567,
DAYS=15,
MONTH=sep,
YEAR=1973,
ABSTRACT="Computation of cross-country network bandwidth.",
URL="http://www.rfc-editor.org/rfc/rfc567.txt"
}

@TECHREPORT{rfc568,
AUTHOR="J. M. McQuillan",
TITLE="Response to {RFC} 567 - cross country network bandwidth",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=568,
DAYS=15,
MONTH=sep,
YEAR=1973,
ABSTRACT="This RFC serves as a brief correction to several fundamental
errors in RFC 567.",
URL="http://www.rfc-editor.org/rfc/rfc568.txt"
}

@TECHREPORT{rfc569,
AUTHOR="M. A. Padlipsky",
TITLE="{NETED:} A Common Editor for the {ARPA} Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=569,
DAYS=15,
MONTH=oct,
YEAR=1973,
ABSTRACT="Defines a simple line style text editor and suggests that it
be made available on every host in the network.",
URL="http://www.rfc-editor.org/rfc/rfc569.txt"
}

@TECHREPORT{rfc570,
AUTHOR="J. R. Pickens",
TITLE="Experimental input mapping between {NVT} {ASCII} and {UCSB} On Line System",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=570,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1973,
ABSTRACT="This RFC updates RFC 216. This document describes the proposed
solutions from the requests to improve the human interface to the UCSB
On-Line System.",
URL="http://www.rfc-editor.org/rfc/rfc570.txt"
}

@TECHREPORT{rfc571,
AUTHOR="R. Braden",
TITLE="Tenex {FTP} problem",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=571,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="A report on a problem in the current Tenex implementation
which is likely to cause incorrect results when transferring files to a
non-Tenex site."
}

@TECHREPORT{rfc573,
AUTHOR="A. K. Bhushan",
TITLE="Data and file transfer: Some measurement results",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=573,
DAYS=15,
MONTH=sep,
YEAR=1973,
ABSTRACT="A report on the results of the performance of MIT-DM's
FTP-user and FTP-server programs."
}

@TECHREPORT{rfc574,
AUTHOR="M. Krilanovich",
TITLE="Announcement of a mail facility at {UCSB}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=574,
DAYS=15,
MONTH=sep,
YEAR=1973,
ABSTRACT="An announcement of a server program which supports that subset
of the File Transfer Protocol necessary for mail delivery."
}

@TECHREPORT{rfc576,
AUTHOR="K. Victor",
TITLE="Proposal for modifying linking",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=576,
DAYS=15,
MONTH=sep,
YEAR=1973,
ABSTRACT="This RFC presents a plan to modify the link jsys in Tenex to
work in a better way in terms of the user interface."
}

@TECHREPORT{rfc577,
AUTHOR="D. H. Crocker",
TITLE="Mail priority",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=577,
DAYS=15,
MONTH=oct,
YEAR=1973,
ABSTRACT="A paper that suggests interpretations for urgency values,
based on arguments presented in RFC 555. References RFC 539."
}

@TECHREPORT{rfc578,
AUTHOR="A. K. Bhushan and N. D. Ryan",
TITLE="Using {MIT-Mathlab} {MACSYMA} from {MIT-DMS} Muddle",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=578,
DAYS=15,
MONTH=oct,
YEAR=1973,
ABSTRACT="This paper describes an experiment in non-trivial automated
resource sharing between dissimilar systems. The goal of this experiment
was to interface the Muddle system at MIT-DMS to the MACSYMA system at
MIT-Mathlab."
}

@TECHREPORT{rfc579,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (September {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=579,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="A report on the Host traffic statistics for the month of
September 1973. Updates RFC 566."
}

@TECHREPORT{rfc580,
AUTHOR="J. B. Postel",
TITLE="Note to Protocol Designers and Implementers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=580,
DAYS=15,
MONTH=oct,
YEAR=1973,
ABSTRACT="An announcement that future proposed protocols shall be
submitted in the form of on-line documents, preferably in NLS files, to
the Network Information Center.",
URL="http://www.rfc-editor.org/rfc/rfc580.txt"
}

@TECHREPORT{rfc581,
AUTHOR="D. H. Crocker and J. B. Postel",
TITLE="Corrections to {RFC} {560:} Remote Controlled Transmission and Echoing
Telnet Option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=581,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="This RFC contains corrections to RFC 560, which described the
Remote Controlled Transmission and Echoing Telnet Option."
}

@TECHREPORT{rfc582,
AUTHOR="R. Clements",
TITLE="Comments on {RFC} {580:} Machine readable protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=582,
PAGES=1,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT={Cites objections to the phrase {"}preferably NLS files{"}.},
URL="http://www.rfc-editor.org/rfc/rfc582.txt"
}

@TECHREPORT{rfc584,
AUTHOR="J. Iseli and D. H. Crocker and N. Neigus",
TITLE="Charter for {ARPANET} Users Interest Working Group",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=584,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="Describes the background, membership, and scope of the newly
formed Users Interest Working Group.",
URL="http://www.rfc-editor.org/rfc/rfc584.txt"
}

@TECHREPORT{rfc585,
AUTHOR="D. H. Crocker and N. Neigus and Elizabeth J. Feinler and J. Iseli",
TITLE="{ARPANET} users interest working group meeting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=585,
PAGES=9,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="Meeting notes of the first Users Interest Working Group.",
URL="http://www.rfc-editor.org/rfc/rfc585.txt"
}

@TECHREPORT{rfc586,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (October {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=586,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="A report on the Host traffic statistics for the month of
October 1973. Updates RFC 579."
}

@TECHREPORT{rfc587,
AUTHOR="J. B. Postel",
TITLE="Announcing new Telnet options",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=587,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="Announcement of Negotiate About Output Line Width (NAOL), and
Negotiate About Output Page Size (NAOP)."
}

@TECHREPORT{rfc588,
AUTHOR="A. Stokes",
TITLE="London node is now up",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=588,
DAYS=15,
MONTH=oct,
YEAR=1973,
ABSTRACT="Notice that an ARPANET node is operational at University
College, London."
}

@TECHREPORT{rfc589,
AUTHOR="R. Braden",
TITLE="{CCN} {NETRJS} server messages to remote user",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=589,
PAGES=5,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="Describes the system to user messages at UCLA-CCN's remote job
entry service.",
URL="http://www.rfc-editor.org/rfc/rfc589.txt"
}

@TECHREPORT{rfc590,
AUTHOR="M. A. Padlipsky",
TITLE="{MULTICS} address change",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=590,
PAGES=1,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="Announcement of a plan to change the address of MIT Multics.",
URL="http://www.rfc-editor.org/rfc/rfc590.txt"
}

@TECHREPORT{rfc591,
AUTHOR="D. C. Walden",
TITLE="Addition to the Very Distant Host specifications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=591,
PAGES=1,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="A sentence correction notation that should be inserted in
Appendix F of BBN Report 1822.",
URL="http://www.rfc-editor.org/rfc/rfc591.txt"
}

@TECHREPORT{rfc592,
AUTHOR="R. W. Watson",
TITLE="Some thoughts on system design to facilitate resource sharing",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=592,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="Proposes a system interconnection approach which would help in
moving toward more resource sharing on the ARPANET."
}

@TECHREPORT{rfc593,
AUTHOR="A. A. McKenzie and J. B. Postel",
TITLE="Telnet and {FTP} implementation schedule change",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=593,
PAGES=1,
DAYS=15,
MONTH=nov,
YEAR=1973,
URL="http://www.rfc-editor.org/rfc/rfc593.txt"
}

@TECHREPORT{rfc594,
AUTHOR="Jerry Burchfiel",
TITLE="Speedup of {Host-IMP} interface",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=594,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="A discussion on how to make the full performance capabilities
of the subnet available for interprocess communication."
}

@TECHREPORT{rfc595,
AUTHOR="W. Hathaway",
TITLE="Second thoughts in defense of the Telnet {Go-Ahead}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=595,
PAGES=5,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="This RFC is in reply to RFC 596.",
URL="http://www.rfc-editor.org/rfc/rfc595.txt"
}

@TECHREPORT{rfc596,
AUTHOR="Edward A. Taft",
TITLE="Second thoughts on Telnet {Go-Ahead}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=596,
PAGES=5,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="Cited objections to the requirement that hosts implement the
Telnet Go-Ahead (GA) command, as specified in the Telnet Protocol
Specification.",
URL="http://www.rfc-editor.org/rfc/rfc596.txt"
}

@TECHREPORT{rfc597,
AUTHOR="N. Neigus and Elizabeth J. Feinler",
TITLE="Host status",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=597,
PAGES=6,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="This RFC provides the most current network maps, geographic
and logical, plus a list of hosts connected to the ARPANET.",
URL="http://www.rfc-editor.org/rfc/rfc597.txt"
}

@TECHREPORT{rfc598,
AUTHOR=" {{Network Information Center, Stanford Research Institute}}",
TITLE="{RFC} index - December {5,} 1973",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=598,
MONTH=dec,
YEAR=1973,
ABSTRACT="Lists RFCs 1-593."
}

@TECHREPORT{rfc599,
AUTHOR="R. Braden",
TITLE="Update on {NETRJS}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=599,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="A status report and update on UCLA-CCN's remote job entry
service.",
URL="http://www.rfc-editor.org/rfc/rfc599.txt"
}

@TECHREPORT{rfc600,
AUTHOR="A. Berggreen",
TITLE="Interfacing an Illinois plasma terminal to the {ARPANET}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=600,
DAYS=15,
MONTH=nov,
YEAR=1973,
ABSTRACT="Discusses plans to map Plato terminal codes to network ASCII
for accessing the Plato system via the network using Telnet."
}

@TECHREPORT{rfc601,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (November {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=601,
PAGES=5,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="A report on Host traffic statistics for the month of November
1973. Updates RFC 586.",
URL="http://www.rfc-editor.org/rfc/rfc601.txt"
}

@TECHREPORT{rfc602,
AUTHOR="Robert M. Metcalfe",
TITLE={{"}The stockings were hung by the chimney with care{"}},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=602,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="Susceptibility of ARPANET to security violations.",
URL="http://www.rfc-editor.org/rfc/rfc602.txt"
}

@TECHREPORT{rfc603,
AUTHOR="Jerry Burchfiel",
TITLE="Response to {RFC} {597:} Host status",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=603,
PAGES=1,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="Questions about the ARPANET topology described in RFC 597.",
URL="http://www.rfc-editor.org/rfc/rfc603.txt"
}

@TECHREPORT{rfc604,
AUTHOR="J. B. Postel",
TITLE="Assigned link numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=604,
PAGES=2,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="Modifies official host-host protocol. Replaced by RFCs 997 and
990.",
URL="http://www.rfc-editor.org/rfc/rfc604.txt"
}

@TECHREPORT{rfc606,
AUTHOR="L. P. Deutsch",
TITLE="Host names on-line",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=606,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="Resolving differences in hostname-address mappings; see also
RFCs 627, 625, 623 and 608.",
URL="http://www.rfc-editor.org/rfc/rfc606.txt"
}

@TECHREPORT{rfc610,
AUTHOR="R. Winter and J. S. Hill and W. Greiff",
TITLE="Further datalanguage design concepts",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=610,
PAGES=88,
DAYS=15,
MONTH=dec,
YEAR=1973,
ABSTRACT="Preliminary results of the language design; a model for data
languagea semantics; future considerations.",
URL="http://www.rfc-editor.org/rfc/rfc610.txt"
}

@TECHREPORT{rfc616,
AUTHOR="D. C. Walden",
TITLE="Latest network maps",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=616,
DAYS=15,
MONTH=feb,
YEAR=1973,
ABSTRACT="Geographic ad Topologic maps of the ARPANET of January 1974."
}

@TECHREPORT{rfc607,
AUTHOR="M. Krilanovich and G. Gregg",
TITLE="Comments on the File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=607,
DAYS=15,
MONTH=jan,
YEAR=1974,
ABSTRACT="An old version; see RFC 624; see also RFCs 614, 542 and 640.",
URL="http://www.rfc-editor.org/rfc/rfc607.txt"
}

@TECHREPORT{rfc608,
AUTHOR="M. D. Kudlick",
TITLE="Host names on-line",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=608,
PAGES=4,
DAYS=15,
MONTH=jan,
YEAR=1974,
ABSTRACT="Response to RFC 606; see also RFCs 627, 625 and 623.",
URL="http://www.rfc-editor.org/rfc/rfc608.txt"
}

@TECHREPORT{rfc609,
AUTHOR="B. Ferguson",
TITLE="Statement of upcoming move of {NIC/NLS} service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=609,
DAYS=15,
MONTH=jan,
YEAR=1974,
ABSTRACT="See also RFCs 621 and 620.",
URL="http://www.rfc-editor.org/rfc/rfc609.txt"
}

@TECHREPORT{rfc611,
AUTHOR="D. C. Walden",
TITLE="Two changes to the {IMP/Host} Protocol to improve user/network
communications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=611,
PAGES=4,
DAYS=15,
MONTH=feb,
YEAR=1974,
ABSTRACT="Expansion of Host-Going-Down and addition of Dead-Host-Status
Message.",
URL="http://www.rfc-editor.org/rfc/rfc611.txt"
}

@TECHREPORT{rfc612,
AUTHOR="A. A. McKenzie",
TITLE="Traffic statistics (December {1973)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=612,
PAGES=6,
DAYS=15,
MONTH=jan,
YEAR=1974,
ABSTRACT="A report on Host traffic statistics for the month of December
1973. Updates RFC 601.",
URL="http://www.rfc-editor.org/rfc/rfc612.txt"
}

@TECHREPORT{rfc613,
AUTHOR="A. A. McKenzie",
TITLE="Network connectivity: A response to {RFC} 603",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=613,
PAGES=1,
DAYS=15,
MONTH=jan,
YEAR=1974,
ABSTRACT="Remarks about connectivity and robustness of networks.",
URL="http://www.rfc-editor.org/rfc/rfc613.txt"
}

@TECHREPORT{rfc614,
AUTHOR="K. T. Pogran and N. Neigus",
TITLE={Response to {RFC} {607:} {"}Comments on the File Transfer Protocol{"}},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=614,
DAYS=15,
MONTH=jan,
YEAR=1974,
ABSTRACT="See also RFCs 624, 542 and 640.",
URL="http://www.rfc-editor.org/rfc/rfc614.txt"
}

@TECHREPORT{rfc615,
AUTHOR="D. H. Crocker",
TITLE="Proposed Network Standard Data Pathname syntax",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=615,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="A suggestion for a network wide standard for naming data (such
as files).",
URL="http://www.rfc-editor.org/rfc/rfc615.txt"
}

@TECHREPORT{rfc617,
AUTHOR="Edward A. Taft",
TITLE="Note on socket number assignment",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=617,
DAYS=15,
MONTH=feb,
YEAR=1974,
ABSTRACT="Danger of imposing more fixed socket number requirements; see
also RFCs 542, 503 and 451.",
URL="http://www.rfc-editor.org/rfc/rfc617.txt"
}

@TECHREPORT{rfc618,
AUTHOR="Edward A. Taft",
TITLE="Few observations on {NCP} statistics",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=618,
DAYS=15,
MONTH=feb,
YEAR=1974,
ABSTRACT="Distribution of NCP and IMP message types by actual
measurement.",
URL="http://www.rfc-editor.org/rfc/rfc618.txt"
}

@TECHREPORT{rfc619,
AUTHOR="W. E. Naylor and H. Opderbeck",
TITLE="Mean round-trip times in the {ARPANET}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=619,
PAGES=14,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="Actual measurements of round-trip times.",
URL="http://www.rfc-editor.org/rfc/rfc619.txt"
}

@TECHREPORT{rfc620,
AUTHOR="B. Ferguson",
TITLE="Request for monitor host table updates",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=620,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="Changes in the hosts Office-1 and SRI-ARC.",
URL="http://www.rfc-editor.org/rfc/rfc620.txt"
}

@TECHREPORT{rfc621,
AUTHOR="M. D. Kudlick",
TITLE="{NIC} user directories at {SRI} {ARC}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=621,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="Changes in user accounts at the NIC.",
URL="http://www.rfc-editor.org/rfc/rfc621.txt"
}

@TECHREPORT{rfc622,
AUTHOR="A. A. McKenzie",
TITLE="Scheduling {IMP/TIP} down time",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=622,
PAGES=3,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="Modification of previous policy.",
URL="http://www.rfc-editor.org/rfc/rfc622.txt"
}

@TECHREPORT{rfc623,
AUTHOR="M. Krilanovich",
TITLE="Comments on on-line host name service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=623,
PAGES=2,
DAYS=15,
MONTH=feb,
YEAR=1974,
ABSTRACT="See also RFCs 627, 625, 608 and 606.",
URL="http://www.rfc-editor.org/rfc/rfc623.txt"
}

@TECHREPORT{rfc624,
AUTHOR="M. Krilanovich and G. Gregg and W. Hathaway and J. A. White",
TITLE="This document replaces {RFC} {607,} which was inadvertently released while
still in rough draft form. It would be appreciated if {RFC} 607 were
disregarded, and this document considered the accurate statement of the
authors' opinions.",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=624,
MONTH=feb,
YEAR=1974,
URL="http://www.rfc-editor.org/rfc/rfc624.txt"
}

@TECHREPORT{rfc625,
AUTHOR="M. D. Kudlick and Elizabeth J. Feinler",
TITLE="On-line hostnames service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=625,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="See also RFCs 606, 608, 623 and 627.",
URL="http://www.rfc-editor.org/rfc/rfc625.txt"
}

@TECHREPORT{rfc626,
AUTHOR="L. Kleinrock and H. Opderbeck",
TITLE="On a possible lockup condition in {IMP} subnet due to message sequencing",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=626,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="A potential problem in the IMP processing of messages. A
detailed description of how this condition can arise.",
URL="http://www.rfc-editor.org/rfc/rfc626.txt"
}

@TECHREPORT{rfc627,
AUTHOR="M. D. Kudlick and Elizabeth J. Feinler",
TITLE="{ASCII} text file of hostnames",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=627,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="See also RFCs 606, 608, 623 and 625.",
URL="http://www.rfc-editor.org/rfc/rfc627.txt"
}

@TECHREPORT{rfc628,
AUTHOR="M. L. Keeney",
TITLE="Status of {RFC} numbers and a note on pre-assigned journal numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=628,
PAGES=1,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="A method for getting the next RFC number to use on a new memo.",
URL="http://www.rfc-editor.org/rfc/rfc628.txt"
}

@TECHREPORT{rfc629,
AUTHOR="J. B. North",
TITLE="Scenario for using the Network Journal",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=629,
PAGES=3,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="An example of how to access information in the NIC's Journal
database.",
URL="http://www.rfc-editor.org/rfc/rfc629.txt"
}

@TECHREPORT{rfc630,
AUTHOR="J. M. Sussman",
TITLE="{FTP} error code usage for more reliable mail service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=630,
PAGES=3,
DAYS=15,
MONTH=apr,
YEAR=1974,
ABSTRACT="Describes FTP reply-code usage in TENEX mail processing.",
URL="http://www.rfc-editor.org/rfc/rfc630.txt"
}

@TECHREPORT{rfc631,
AUTHOR="A. Danthine",
TITLE="International meeting on minicomputers and data communication: Call for
papers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=631,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1974,
ABSTRACT="A meeting on data communications held January 1975 in Liege,
Belgium.",
URL="http://www.rfc-editor.org/rfc/rfc631.txt"
}

@TECHREPORT{rfc632,
AUTHOR="H. Opderbeck",
TITLE="Throughput degradations for single packet messages",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=632,
PAGES=6,
DAYS=15,
MONTH=may,
YEAR=1974,
ABSTRACT="A study of packet throughput.",
URL="http://www.rfc-editor.org/rfc/rfc632.txt"
}

@TECHREPORT{rfc633,
AUTHOR="Alex A. McKenzie",
TITLE="{IMP/TIP} preventive maintenance schedule",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=633,
PAGES=4,
DAYS=15,
MONTH=mar,
YEAR=1974,
ABSTRACT="An old version; see RFC 638.",
URL="http://www.rfc-editor.org/rfc/rfc633.txt"
}

@TECHREPORT{rfc634,
AUTHOR="A. A. McKenzie",
TITLE="Change in network address for Haskins Lab",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=634,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1974,
ABSTRACT="A host a Haskins Lab changes its address from 5/3 to 9/3.",
URL="http://www.rfc-editor.org/rfc/rfc634.txt"
}

@TECHREPORT{rfc635,
AUTHOR="V. G. Cerf",
TITLE="Assessment of {ARPANET} protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=635,
DAYS=15,
MONTH=apr,
YEAR=1974,
ABSTRACT="Theoretical and practical motivation for redesign. Multipacket
messages; host retransmission; duplicate detection; sequencing;
acknowledgement."
}

@TECHREPORT{rfc636,
AUTHOR="Jerry Burchfiel and B. Cosell and Raymond Tomlinson and D. C. Walden",
TITLE="{TIP/Tenex} reliability improvements",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=636,
DAYS=15,
MONTH=jun,
YEAR=1974,
ABSTRACT="Obtaining/maintaining connections; recovery from lost
connections; connection-state changes.",
URL="http://www.rfc-editor.org/rfc/rfc636.txt"
}

@TECHREPORT{rfc637,
AUTHOR="A. A. McKenzie",
TITLE="Change of network address for {SU-DSL}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=637,
PAGES=1,
DAYS=15,
MONTH=apr,
YEAR=1974,
ABSTRACT="A host at Stanford changes its address from 2/2 to 2/3.",
URL="http://www.rfc-editor.org/rfc/rfc637.txt"
}

@TECHREPORT{rfc640,
AUTHOR="J. B. Postel",
TITLE="Revised {FTP} reply codes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=640,
DAYS=15,
MONTH=jun,
YEAR=1974,
ABSTRACT="Updates RFC 542.",
URL="http://www.rfc-editor.org/rfc/rfc640.txt"
}

@TECHREPORT{rfc642,
AUTHOR="Jerry Burchfiel",
TITLE="Ready line philosophy and implementation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=642,
PAGES=4,
DAYS=15,
MONTH=jul,
YEAR=1974,
URL="http://www.rfc-editor.org/rfc/rfc642.txt"
}

@TECHREPORT{rfc643,
AUTHOR="E. Mader",
TITLE="Network Debugging Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=643,
PAGES=8,
DAYS=15,
MONTH=jul,
YEAR=1974,
ABSTRACT="To be used in an implementation of a PDP-11 network bootstrap
device and a cross-network debugger.",
URL="http://www.rfc-editor.org/rfc/rfc643.txt"
}

@TECHREPORT{rfc644,
AUTHOR="R. Thomas",
TITLE="On the problem of signature authentication for network mail",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=644,
DAYS=15,
MONTH=jul,
YEAR=1974,
ABSTRACT="Proposes that the mail sender be an authorized system process
and that the mail sender and mail receiver processes exchange a
password. The sender process takes responsibility for authentication of
the signature on the mail.",
URL="http://www.rfc-editor.org/rfc/rfc644.txt"
}

@TECHREPORT{rfc645,
AUTHOR="D. H. Crocker",
TITLE="Network Standard Data Specification syntax",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=645,
DAYS=15,
MONTH=jun,
YEAR=1974,
ABSTRACT="Providing a mechanism for specifying all attributes of a
collection of bits; see also RFC 615."
}

@TECHREPORT{rfc647,
AUTHOR="M. A. Padlipsky",
TITLE="Proposed protocol for connecting host computers to {ARPA-like} networks via
front end processors",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=647,
DAYS=15,
MONTH=nov,
YEAR=1974,
ABSTRACT="Approaches to Front-End protocol processing using available
hardware and software."
}

@TECHREPORT{rfc651,
AUTHOR="D. H. Crocker",
TITLE="Revised Telnet status option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=651,
DAYS=15,
MONTH=oct,
YEAR=1974,
ABSTRACT="Revises the Telnet Option for communicating the status of all
Telnet options over the network.",
URL="http://www.rfc-editor.org/rfc/rfc651.txt"
}

@TECHREPORT{rfc652,
AUTHOR="D. H. Crocker",
TITLE="Telnet output carriage-return disposition option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=652,
PAGES=4,
DAYS=15,
MONTH=oct,
YEAR=1974,
ABSTRACT="Defines a Telnet option for specific control of Carriage
Return.",
URL="http://www.rfc-editor.org/rfc/rfc652.txt"
}

@TECHREPORT{rfc653,
AUTHOR="D. H. Crocker",
TITLE="Telnet output horizontal tabstops option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=653,
DAYS=15,
MONTH=oct,
YEAR=1974,
ABSTRACT="Defines a Telnet option for setting the stops for Horizontal
Tab.",
URL="http://www.rfc-editor.org/rfc/rfc653.txt"
}

@TECHREPORT{rfc654,
AUTHOR="D. H. Crocker",
TITLE="Telnet output horizontal tab disposition option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=654,
DAYS=15,
MONTH=oct,
YEAR=1974,
ABSTRACT="Defines a Telnet option for specific control of Horizontal
Tab.",
URL="http://www.rfc-editor.org/rfc/rfc654.txt"
}

@TECHREPORT{rfc655,
AUTHOR="D. H. Crocker",
TITLE="Telnet output formfeed disposition option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=655,
DAYS=15,
MONTH=oct,
YEAR=1974,
ABSTRACT="Defines a Telnet option for specific control of Form Feed.",
URL="http://www.rfc-editor.org/rfc/rfc655.txt"
}

@TECHREPORT{rfc656,
AUTHOR="D. H. Crocker",
TITLE="Telnet output vertical tabstops option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=656,
DAYS=15,
MONTH=oct,
YEAR=1974,
ABSTRACT="Defines a Telnet option for setting the stops for Vertical
Tab.",
URL="http://www.rfc-editor.org/rfc/rfc656.txt"
}

@TECHREPORT{rfc657,
AUTHOR="D. H. Crocker",
TITLE="Telnet output vertical tab disposition option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=657,
DAYS=15,
MONTH=oct,
YEAR=1974,
ABSTRACT="Defines a Telnet option for specific control of Vertical Tab.",
URL="http://www.rfc-editor.org/rfc/rfc657.txt"
}

@TECHREPORT{rfc658,
AUTHOR="D. H. Crocker",
TITLE="Telnet output linefeed disposition",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=658,
DAYS=15,
MONTH=oct,
YEAR=1974,
ABSTRACT="Defines a Telnet option for specific control of Line Feed.",
URL="http://www.rfc-editor.org/rfc/rfc658.txt"
}

@TECHREPORT{rfc659,
AUTHOR="J. B. Postel",
TITLE="Announcing additional Telnet options",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=659,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1974,
ABSTRACT="Options defined in RFCs 651-658.",
URL="http://www.rfc-editor.org/rfc/rfc659.txt"
}

@TECHREPORT{rfc660,
AUTHOR="D. C. Walden",
TITLE="Some changes to the {IMP} and the {IMP/Host} interface",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=660,
DAYS=15,
MONTH=oct,
YEAR=1974,
ABSTRACT="Decoupling of message number sequences of hosts; host-host
access control; message number window; messages outside normal
mechanism; see also BBN 1822.",
URL="http://www.rfc-editor.org/rfc/rfc660.txt"
}

@TECHREPORT{rfc661,
AUTHOR="J. B. Postel",
TITLE="Protocol information",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=661,
DAYS=15,
MONTH=nov,
YEAR=1974,
ABSTRACT="This RFC has been replaced by RFC 991."
}

@TECHREPORT{rfc662,
AUTHOR="R. Kanodia",
TITLE="Performance improvement in {ARPANET} file transfers from Multics",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=662,
DAYS=15,
MONTH=nov,
YEAR=1974,
ABSTRACT="Experimenting with host output buffers to improve throughput.",
URL="http://www.rfc-editor.org/rfc/rfc662.txt"
}

@TECHREPORT{rfc663,
AUTHOR="R. Kanodia",
TITLE="Lost message detection and recovery protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=663,
DAYS=15,
MONTH=nov,
YEAR=1974,
ABSTRACT="Proposed extension of host-host protocol; see also RFCs 534,
516, 512, 492 and 467.",
URL="http://www.rfc-editor.org/rfc/rfc663.txt"
}

@TECHREPORT{rfc666,
AUTHOR="M. A. Padlipsky",
TITLE="Specification of the Unified {User-Level} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=666,
DAYS=15,
MONTH=nov,
YEAR=1974,
ABSTRACT="Discusses and proposes a common command language."
}

@TECHREPORT{rfc667,
AUTHOR="S. G. Chipman",
TITLE="{BBN} host ports",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=667,
DAYS=15,
MONTH=dec,
YEAR=1974,
ABSTRACT="Approved scheme to connect host ports to the network."
}

@TECHREPORT{rfc669,
AUTHOR="D. W. Dodds",
TITLE="November, {1974,} survey of {New-Protocol} Telnet servers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=669,
PAGES=3,
DAYS=15,
MONTH=dec,
YEAR=1974,
ABSTRACT="An earlier poll of Telnet server implementation status.
Updates RFC 702; see also RFCs 703 and 679."
}

@TECHREPORT{rfc671,
AUTHOR="R. E. Schantz",
TITLE="Note on Reconnection Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=671,
DAYS=15,
MONTH=dec,
YEAR=1974,
ABSTRACT="Experience with implementation in RSEXEC context."
}

@TECHREPORT{rfc672,
AUTHOR="R. E. Schantz",
TITLE="Multi-site data collection facility",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=672,
DAYS=15,
MONTH=dec,
YEAR=1974,
ABSTRACT="Applicability of TIP/Tenex protocols beyond TIP accounting.",
URL="http://www.rfc-editor.org/rfc/rfc672.txt"
}

@TECHREPORT{rfc674,
AUTHOR="J. B. Postel and J. A. White",
TITLE="Procedure call documents: Version 2",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=674,
DAYS=15,
MONTH=dec,
YEAR=1974,
ABSTRACT="A host level protocol used in the NSW--a slightly constrained
version of ARPANET Host-to-Host protocol, affecting allocation, RFNM
wait, and retransmission; see also RFC 684.",
URL="http://www.rfc-editor.org/rfc/rfc674.txt"
}

@TECHREPORT{rfc675,
AUTHOR="V. G. Cerf and Y. Dalal and C. A. Sunshine",
TITLE="Specification of Internet Transmission Control Program",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=675,
PAGES=70,
DAYS=15,
MONTH=dec,
YEAR=1974,
ABSTRACT="The first detailed specification of TCP; see RFC 793.",
URL="http://www.rfc-editor.org/rfc/rfc675.txt"
}

@TECHREPORT{rfc678,
AUTHOR="J. B. Postel",
TITLE="Standard file formats",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=678,
DAYS=15,
MONTH=dec,
YEAR=1974,
ABSTRACT="For transmission of documents across different environments.",
URL="http://www.rfc-editor.org/rfc/rfc678.txt"
}

@TECHREPORT{rfc700,
AUTHOR="E. Mader and William W. Plummer and Raymond Tomlinson",
TITLE="Protocol experiment",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=700,
DAYS=15,
MONTH=aug,
YEAR=1974,
ABSTRACT="Describes a protocol based loosely on a very early version of
TCP, used to send data to a printer server.",
URL="http://www.rfc-editor.org/rfc/rfc700.txt"
}

@TECHREPORT{rfc701,
AUTHOR="D. W. Dodds",
TITLE="August, {1974,} survey of {New-Protocol} Telnet servers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=701,
DAYS=15,
MONTH=aug,
YEAR=1974,
ABSTRACT="An earlier poll of Telnet server implementation status; see
also RFCs 703, 702, 679 and 669.",
URL="http://www.rfc-editor.org/rfc/rfc701.txt"
}

@TECHREPORT{rfc702,
AUTHOR="D. W. Dodds",
TITLE="September, {1974,} survey of {New-Protocol} Telnet servers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=702,
PAGES=3,
DAYS=15,
MONTH=sep,
YEAR=1974,
ABSTRACT="An earlier poll of Telnet server implementation status; see
also RFC's703, 701, 679, and 669.",
URL="http://www.rfc-editor.org/rfc/rfc702.txt"
}

@TECHREPORT{rfc677,
AUTHOR="P. Johnson and R. Thomas",
TITLE="Maintenance of duplicate databases",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=677,
PAGES=10,
DAYS=15,
MONTH=jan,
YEAR=1975,
URL="http://www.rfc-editor.org/rfc/rfc677.txt"
}

@TECHREPORT{rfc679,
AUTHOR="D. W. Dodds",
TITLE="February, {1975,} survey of {New-Protocol} Telnet servers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=679,
DAYS=15,
MONTH=feb,
YEAR=1975,
ABSTRACT="An earlier poll of Telnet server implementation status.
Updates RFCs 701, 702 and 669; see also RFC 703."
}

@TECHREPORT{rfc680,
AUTHOR="Theodore Myer and D. Henderson",
TITLE="Message Transmission Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=680,
DAYS=15,
MONTH=apr,
YEAR=1975,
ABSTRACT="Extends message field definition beyond RFC 561 attempts to
establish syntactic and semantic standards for ARPANET; see also RFCs
733 and 822."
}

@TECHREPORT{rfc681,
AUTHOR="S. Holmgren",
TITLE="Network {UNIX}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=681,
DAYS=15,
MONTH=mar,
YEAR=1975,
ABSTRACT="Capabilities as an ARPANET Mini-Host: standard I/O, Telnet,
NCP, Hardware/Software requirements, reliability, availability.",
URL="http://www.rfc-editor.org/rfc/rfc681.txt"
}

@TECHREPORT{rfc683,
AUTHOR="R. Clements",
TITLE="{FTPSRV} - Tenex extension for paged files",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=683,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1975,
ABSTRACT="Defines an extension to FTP for page-mode transfers between
Tenex systems; also discusses file transfer reliability.",
URL="http://www.rfc-editor.org/rfc/rfc683.txt"
}

@TECHREPORT{rfc684,
AUTHOR="R. E. Schantz",
TITLE="Commentary on procedure calling as a network protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=684,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1975,
ABSTRACT="Describes issues in designing distributed computing systems.
Shortcomings of RFC 674; see also RFCs 542 and 354.",
URL="http://www.rfc-editor.org/rfc/rfc684.txt"
}

@TECHREPORT{rfc685,
AUTHOR="M. Beeler",
TITLE="Response time in cross network debugging",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=685,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1975,
ABSTRACT="This memo discusses the contribution of ARPANET communication
to response time.",
URL="http://www.rfc-editor.org/rfc/rfc685.txt"
}

@TECHREPORT{rfc686,
AUTHOR="B. Harvey",
TITLE="Leaving well enough alone",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=686,
PAGES=9,
DAYS=15,
MONTH=may,
YEAR=1975,
ABSTRACT="Discusses the difference between early and later versions of
FTP; see also RFCs 691, 640, 630, 542, 454, 448, 414, 385 and 354.",
URL="http://www.rfc-editor.org/rfc/rfc686.txt"
}

@TECHREPORT{rfc687,
AUTHOR="D. C. Walden",
TITLE="{IMP/Host} and {Host/IMP} Protocol changes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=687,
DAYS=15,
MONTH=jun,
YEAR=1975,
ABSTRACT="This RFC discusses addressing hosts on more than 63 IMPs, and
other backwards compatible expansions; see also RFCs 690 and 692.",
URL="http://www.rfc-editor.org/rfc/rfc687.txt"
}

@TECHREPORT{rfc688,
AUTHOR="D. C. Walden",
TITLE="Tentative schedule for the new Telnet implementation for the {TIP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=688,
PAGES=1,
DAYS=15,
MONTH=jun,
YEAR=1975,
URL="http://www.rfc-editor.org/rfc/rfc688.txt"
}

@TECHREPORT{rfc689,
AUTHOR="R. Clements",
TITLE="Tenex {NCP} finite state machine for connections",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=689,
PAGES=6,
DAYS=15,
MONTH=may,
YEAR=1975,
ABSTRACT="Describes the internal states of an NCP connection in the
Tenex implementation.",
URL="http://www.rfc-editor.org/rfc/rfc689.txt"
}

@TECHREPORT{rfc690,
AUTHOR="J. B. Postel",
TITLE="Comments on the proposed {Host/IMP} Protocol changes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=690,
PAGES=3,
DAYS=15,
MONTH=jun,
YEAR=1975,
ABSTRACT="Comments on suggestions in RFC 687; see also RFCs 692 and 696.",
URL="http://www.rfc-editor.org/rfc/rfc690.txt"
}

@TECHREPORT{rfc691,
AUTHOR="B. Harvey",
TITLE="One more try on the {FTP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=691,
DAYS=15,
MONTH=jun,
YEAR=1975,
ABSTRACT="A slight revision of RFC 686, regarding the subject of print
files; see also RFCs 640, 630, 542, 454, 448, 414, 385 and 354.",
URL="http://www.rfc-editor.org/rfc/rfc691.txt"
}

@TECHREPORT{rfc692,
AUTHOR="S. M. Wolfe",
TITLE="Comments on {IMP/Host} Protocol changes {(RFCs} 687 and {690)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=692,
PAGES=2,
DAYS=15,
MONTH=jun,
YEAR=1975,
ABSTRACT="A proposed solution to the problem of combined length of IMP
and Host leaders; see also RFCs 696, 690 and 687.",
URL="http://www.rfc-editor.org/rfc/rfc692.txt"
}

@TECHREPORT{rfc694,
AUTHOR="J. B. Postel",
TITLE="Protocol information",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=694,
DAYS=15,
MONTH=jun,
YEAR=1975,
ABSTRACT="This RFC has been replaced by RFC 991."
}

@TECHREPORT{rfc695,
AUTHOR="M. Krilanovich",
TITLE="Official change in {Host-Host} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=695,
DAYS=15,
MONTH=jul,
YEAR=1975,
ABSTRACT="Corrects an ambiguity concerning the ERR command; changes NIC
8246 and NIC 7104.",
URL="http://www.rfc-editor.org/rfc/rfc695.txt"
}

@TECHREPORT{rfc696,
AUTHOR="V. G. Cerf",
TITLE="Comments on the {IMP/Host} and {Host/IMP} Protocol changes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=696,
DAYS=15,
MONTH=jul,
YEAR=1975,
ABSTRACT="Observations on current international standards
recommendations from IFIP working group 6.1; see also RFCs 692, 690 687."
}

@TECHREPORT{rfc697,
AUTHOR="J. Lieb",
TITLE="{CWD} command of {FTP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=697,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1975,
ABSTRACT={Discusses FTP login access to {"}files only{"} directories.},
URL="http://www.rfc-editor.org/rfc/rfc697.txt"
}

@TECHREPORT{rfc698,
AUTHOR="T. Mock",
TITLE="Telnet extended {ASCII} option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=698,
DAYS=15,
MONTH=jul,
YEAR=1975,
ABSTRACT="Describes an option to allow transmission of a special kind of
extended ASCII used at the Stanford AI and MIT AI Labs.",
URL="http://www.rfc-editor.org/rfc/rfc698.txt"
}

@TECHREPORT{rfc703,
AUTHOR="D. W. Dodds",
TITLE="July, {1975,} survey of {New-Protocol} Telnet Servers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=703,
PAGES=3,
DAYS=15,
MONTH=jul,
YEAR=1975,
ABSTRACT="A poll of Telnet servers to check implementation status and
Telnet options. Updates RFCs 702, 701, 679 and 669.",
URL="http://www.rfc-editor.org/rfc/rfc703.txt"
}

@TECHREPORT{rfc704,
AUTHOR="P. J. Santos",
TITLE="{IMP/Host} and {Host/IMP} Protocol change",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=704,
DAYS=15,
MONTH=sep,
YEAR=1975,
ABSTRACT="Describes the changes to the 1822 interface to eliminate the
restriction of 63 IMPs.",
URL="http://www.rfc-editor.org/rfc/rfc704.txt"
}

@TECHREPORT{rfc705,
AUTHOR="R. F. Bryan",
TITLE="Front-end Protocol {B6700} version",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=705,
DAYS=15,
MONTH=nov,
YEAR=1975,
ABSTRACT="This RFC describes a protocol used between a PDP-11 (the
ARPANET front end) and a B6700 to support network communication.",
URL="http://www.rfc-editor.org/rfc/rfc705.txt"
}

@TECHREPORT{rfc706,
AUTHOR="J. B. Postel",
TITLE="On the junk mail problem",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=706,
DAYS=15,
MONTH=nov,
YEAR=1975,
ABSTRACT={A short note pointing out that the ARPANET maybe subject to a
{"}denial of service{"} attack by a misbehaving host.},
URL="http://www.rfc-editor.org/rfc/rfc706.txt"
}

@TECHREPORT{rfc707,
AUTHOR="J. A. White",
TITLE="High-level framework for network-based resource sharing",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=707,
DAYS=15,
MONTH=dec,
YEAR=1975,
ABSTRACT="A description of a programming environment for network-based
programs; see also RFC 708.",
URL="http://www.rfc-editor.org/rfc/rfc707.txt"
}

@TECHREPORT{rfc708,
AUTHOR="J. A. White",
TITLE="Elements of a Distributed Programming System",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=708,
PAGES=30,
DAYS=15,
MONTH=jan,
YEAR=1976,
ABSTRACT="A description of a distributed programming system; see also
RFC 707.",
URL="http://www.rfc-editor.org/rfc/rfc708.txt"
}

@TECHREPORT{rfc712,
AUTHOR="J. E. Donnelley",
TITLE="Distributed Capability Computing System {(DCCS)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=712,
DAYS=15,
MONTH=feb,
YEAR=1976,
ABSTRACT="A description of a Distributed Capability based computing
system."
}

@TECHREPORT{rfc713,
AUTHOR="J. Haverty",
TITLE="{MSDTP-Message} Services Data Transmission Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=713,
PAGES=22,
DAYS=15,
MONTH=apr,
YEAR=1976,
ABSTRACT="The specification of a set of Data Primitives for building
interactive services.",
URL="http://www.rfc-editor.org/rfc/rfc713.txt"
}

@TECHREPORT{rfc714,
AUTHOR="A. A. McKenzie",
TITLE="{Host-Host} Protocol for an {ARPANET-Type} Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=714,
DAYS=15,
MONTH=apr,
YEAR=1976,
ABSTRACT="A specification of a NCP-like protocol for an ARPA-like
network. Interesting to compare to the NCP specification to see what the
author would do differently."
}

@TECHREPORT{rfc716,
AUTHOR="D. C. Walden and J. Levin",
TITLE="Interim Revision to Appendix F of {BBN} 1822",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=716,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1976,
ABSTRACT="A short note updating the specification of the Very Distant
Host 1822 interface.",
URL="http://www.rfc-editor.org/rfc/rfc716.txt"
}

@TECHREPORT{rfc717,
AUTHOR="J. B. Postel",
TITLE="Assigned Network Numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=717,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1976,
ABSTRACT="This RFC has been replaced by RFC 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc717.txt"
}

@TECHREPORT{rfc718,
AUTHOR="J. B. Postel",
TITLE="Comments on {RCTE} from the Tenex Implementation Experience",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=718,
PAGES=2,
DAYS=15,
MONTH=jun,
YEAR=1976,
ABSTRACT="A short note on the Tenex implementation of RCTE; see also
RFCs 726 and 719.",
URL="http://www.rfc-editor.org/rfc/rfc718.txt"
}

@TECHREPORT{rfc719,
AUTHOR="J. B. Postel",
TITLE="Discussion on {RCTE}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=719,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1976,
ABSTRACT="A short discussion of RCTE implementation issues; see also
RFCs 726 and 718.",
URL="http://www.rfc-editor.org/rfc/rfc719.txt"
}

@TECHREPORT{rfc720,
AUTHOR="D. H. Crocker",
TITLE="Address Specification Syntax for Network Mail",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=720,
PAGES=4,
DAYS=15,
MONTH=aug,
YEAR=1976,
ABSTRACT="A discussion of computer mail addresses, with comments on real
names vs. mailboxes, and mailing lists; see also RFC 819.",
URL="http://www.rfc-editor.org/rfc/rfc720.txt"
}

@TECHREPORT{rfc721,
AUTHOR="L. L. Garlick",
TITLE="{Out-of-Band} Control Signals in a {Host-to-Host} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=721,
PAGES=7,
DAYS=15,
MONTH=sep,
YEAR=1976,
ABSTRACT="A discussion of the control signals in transport protocols
(e.g., NCP's Interrupt or TCP's Urgent).",
URL="http://www.rfc-editor.org/rfc/rfc721.txt"
}

@TECHREPORT{rfc722,
AUTHOR="J. Haverty",
TITLE="Thoughts on Interactions in Distributed Services",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=722,
PAGES=14,
DAYS=15,
MONTH=sep,
YEAR=1976,
ABSTRACT="A discussion on the design of interactive distributed services
and the kinds of primitive operations that are needed.",
URL="http://www.rfc-editor.org/rfc/rfc722.txt"
}

@TECHREPORT{rfc724,
AUTHOR="D. H. Crocker and K. T. Pogran and J. Vittal and D. Henderson",
TITLE="Proposed official standard for the format of {ARPA} Network messages",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=724,
DAYS=15,
MONTH=may,
YEAR=1977,
ABSTRACT="An old version; see RFC 822.",
URL="http://www.rfc-editor.org/rfc/rfc724.txt"
}

@TECHREPORT{rfc725,
AUTHOR="John Day and Gary R. Grossman",
TITLE="{RJE} protocol for a resource sharing network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=725,
DAYS=15,
MONTH=mar,
YEAR=1977,
ABSTRACT="Describes a possible Remote Job Entry protocol.",
URL="http://www.rfc-editor.org/rfc/rfc725.txt"
}

@TECHREPORT{rfc726,
AUTHOR="J. B. Postel and D. H. Crocker",
TITLE="Remote Controlled Transmission and Echoing Telnet option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=726,
DAYS=15,
MONTH=mar,
YEAR=1977,
ABSTRACT="Defines a Telnet option for controlling the transmission and
echoing of data to smooth the response to use in high transmission delay
environments; see also RFCs 719 and 718.",
URL="http://www.rfc-editor.org/rfc/rfc726.txt"
}

@TECHREPORT{rfc727,
AUTHOR="M. R. Crispin",
TITLE="Telnet logout option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=727,
DAYS=15,
MONTH=apr,
YEAR=1977,
ABSTRACT="Defines a Telnet option for causing a logout.",
URL="http://www.rfc-editor.org/rfc/rfc727.txt"
}

@TECHREPORT{rfc728,
AUTHOR="John Day",
TITLE="Minor pitfall in the Telnet Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=728,
DAYS=15,
MONTH=apr,
YEAR=1977,
ABSTRACT="This RFC warns of the possibility of an unexpected occurence
in Telnet resulting from the interaction between option subnegotiations
and the Telnet SYNCH operation.",
URL="http://www.rfc-editor.org/rfc/rfc728.txt"
}

@TECHREPORT{rfc729,
AUTHOR="D. H. Crocker",
TITLE="Telnet byte macro option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=729,
PAGES=4,
DAYS=15,
MONTH=may,
YEAR=1977,
ABSTRACT="An old version; see RFC 735.",
URL="http://www.rfc-editor.org/rfc/rfc729.txt"
}

@TECHREPORT{rfc730,
AUTHOR="J. B. Postel",
TITLE="Extensible field addressing",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=730,
DAYS=15,
MONTH=may,
YEAR=1977,
ABSTRACT="Discusses some ideas on addressing that come up in the context
of changing from 8-bit to 24-bit network addresses.",
URL="http://www.rfc-editor.org/rfc/rfc730.txt"
}

@TECHREPORT{rfc731,
AUTHOR="J. Day",
TITLE="Telnet Data Entry Terminal option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=731,
PAGES=14,
DAYS=15,
MONTH=jun,
YEAR=1977,
ABSTRACT="An old version; see RFC 732.",
URL="http://www.rfc-editor.org/rfc/rfc731.txt"
}

@TECHREPORT{rfc733,
AUTHOR="D. H. Crocker and J. Vittal and K. T. Pogran and D. Henderson",
TITLE="Standard for the format of {ARPA} network text messages",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=733,
DAYS=15,
MONTH=nov,
YEAR=1977,
ABSTRACT="Specification of the format for the headers of computer mail.
An old version; see RFC 822.",
URL="http://www.rfc-editor.org/rfc/rfc733.txt"
}

@TECHREPORT{rfc734,
AUTHOR="M. R. Crispin",
TITLE="{SUPDUP} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=734,
PAGES=14,
DAYS=15,
MONTH=oct,
YEAR=1977,
ABSTRACT="Description of a terminal control protocol used at Stanford
and MIT; see also RFCs 736, 746-749.",
URL="http://www.rfc-editor.org/rfc/rfc734.txt"
}

@TECHREPORT{rfc735,
AUTHOR="D. H. Crocker and R. H. Gumpertz",
TITLE="Revised Telnet byte macro option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=735,
DAYS=15,
MONTH=nov,
YEAR=1977,
ABSTRACT="Defines a Telnet option for assigning codes to stand for
strings in Telnet connections. Replaces RFC 729. Obsoletes NIC 40306.",
URL="http://www.rfc-editor.org/rfc/rfc735.txt"
}

@TECHREPORT{rfc736,
AUTHOR="M. R. Crispin",
TITLE="Telnet {SUPDUP} option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=736,
DAYS=15,
MONTH=oct,
YEAR=1977,
ABSTRACT="Defines the procedure for negotiating to use the SUPDUP,
protocol as a Telnet option; see also RFCs 734, 746, 747 and 749.",
URL="http://www.rfc-editor.org/rfc/rfc736.txt"
}

@TECHREPORT{rfc737,
AUTHOR="K. Harrenstien",
TITLE="{FTP} extension: {XSEN}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=737,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1977,
ABSTRACT="An extension to the Mail procedures. This function is
incorporated in the SMTP; see also RFC 821.",
URL="http://www.rfc-editor.org/rfc/rfc737.txt"
}

@TECHREPORT{rfc738,
AUTHOR="K. Harrenstien",
TITLE="Time server",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=738,
PAGES=1,
DAYS=15,
MONTH=oct,
YEAR=1977,
ABSTRACT="Defines the Time Server Protocol; see IEN 142 for the TCP and
VDP versions.",
URL="http://www.rfc-editor.org/rfc/rfc738.txt"
}

@TECHREPORT{rfc739,
AUTHOR="J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=739,
PAGES=11,
DAYS=15,
MONTH=nov,
YEAR=1977,
ABSTRACT="This RFC has been replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc739.txt"
}

@TECHREPORT{rfc740,
AUTHOR="R. Braden",
TITLE="{NETRJS} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=740,
DAYS=15,
MONTH=nov,
YEAR=1977,
ABSTRACT="Defines the protocol used for Remote Job Entry on the UCLA CCN
IBM system; replaces RFCs 599 and 189.",
URL="http://www.rfc-editor.org/rfc/rfc740.txt"
}

@TECHREPORT{rfc741,
AUTHOR="D. Cohen",
TITLE="Specifications for the Network Voice Protocol {(NVP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=741,
PAGES=30,
DAYS=15,
MONTH=nov,
YEAR=1977,
ABSTRACT="Defines the protocol used in the ARPANET packet speech
experiments. Replaced by NVP-II and ST for Internet packet speech
experiments. ST is documented in ISN 119; NVP-II is documented in an ISI
Internal memo.",
URL="http://www.rfc-editor.org/rfc/rfc741.txt"
}

@TECHREPORT{rfc742,
AUTHOR="K. Harrenstien",
TITLE="{NAME/FINGER} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=742,
PAGES=7,
DAYS=15,
MONTH=dec,
YEAR=1977,
ABSTRACT={Defines the Name or Finger Protocol which allows one to get
{"}who is on{"} or {"}where is user x{"} information from another host.},
URL="http://www.rfc-editor.org/rfc/rfc742.txt"
}

@TECHREPORT{rfc743,
AUTHOR="K. Harrenstien",
TITLE="{FTP} extension: {XRSQ/XRCP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=743,
PAGES=8,
DAYS=15,
MONTH=dec,
YEAR=1977,
ABSTRACT="An extension to FTP mail to allow more efficient transmission
of computer mail. Now incorporated into SMTP; see RFC788.",
URL="http://www.rfc-editor.org/rfc/rfc743.txt"
}

@TECHREPORT{rfc744,
AUTHOR="J. Sattley",
TITLE="{MARS} - a Message Archiving and Retrieval Service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=744,
PAGES=6,
DAYS=15,
MONTH=jan,
YEAR=1978,
ABSTRACT="The description of a database service for computer mail
messages, which operates via computer mail.",
URL="http://www.rfc-editor.org/rfc/rfc744.txt"
}

@TECHREPORT{rfc745,
AUTHOR="M. Beeler",
TITLE="{JANUS} interface specifications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=745,
DAYS=15,
MONTH=mar,
YEAR=1978,
ABSTRACT="The specification of a symmetrical 1822 style interface.",
URL="http://www.rfc-editor.org/rfc/rfc745.txt"
}

@TECHREPORT{rfc746,
AUTHOR="R. Stallman",
TITLE="{SUPDUP} graphics extension",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=746,
DAYS=15,
MONTH=mar,
YEAR=1978,
ABSTRACT="An extension of SUPDUP for Graphics; see also RFCs 734, 736,
747 and 749.",
URL="http://www.rfc-editor.org/rfc/rfc746.txt"
}

@TECHREPORT{rfc747,
AUTHOR="M. R. Crispin",
TITLE="Recent extensions to the {SUPDUP} Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=747,
DAYS=15,
MONTH=mar,
YEAR=1978,
ABSTRACT="An update to the SUPDUP protocol (RFC 734); see also RFCs 749,
746 and 736.",
URL="http://www.rfc-editor.org/rfc/rfc747.txt"
}

@TECHREPORT{rfc748,
AUTHOR="M. R. Crispin",
TITLE="Telnet randomly-lose option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=748,
DAYS=15,
MONTH=apr,
YEAR=1978,
ABSTRACT="Defines this Telnet option (note the date of this memo).",
URL="http://www.rfc-editor.org/rfc/rfc748.txt"
}

@TECHREPORT{rfc749,
AUTHOR="B. S. Greenberg",
TITLE="Telnet {SUPDUP-Output} option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=749,
DAYS=15,
MONTH=sep,
YEAR=1978,
ABSTRACT="Updates RFC 736; see also RFCs 734, 746, and 747.",
URL="http://www.rfc-editor.org/rfc/rfc749.txt"
}

@TECHREPORT{rfc750,
AUTHOR="J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=750,
PAGES=12,
DAYS=15,
MONTH=sep,
YEAR=1978,
ABSTRACT="This RFC has been replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc750.txt"
}

@TECHREPORT{rfc751,
AUTHOR="P. D. Lebling",
TITLE="Survey of {FTP} mail and {MLFL}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=751,
PAGES=5,
DAYS=15,
MONTH=dec,
YEAR=1978,
ABSTRACT="A survey of hosts' responses to probes of their FTP servers to
see if servers (a) accept mail for unknown users and (b) support the
MAIL and MLFL commands.",
URL="http://www.rfc-editor.org/rfc/rfc751.txt"
}

@TECHREPORT{rfc752,
AUTHOR="M. R. Crispin",
TITLE="Universal host table",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=752,
DAYS=15,
MONTH=jan,
YEAR=1979,
ABSTRACT="Describes the host table used at MIT and Stanford. This has
several extensions and generalizations from the NIC standard and the
table used by most Tenex and TOPS20 hosts.",
URL="http://www.rfc-editor.org/rfc/rfc752.txt"
}

@TECHREPORT{rfc753,
AUTHOR="J. B. Postel",
TITLE="Internet Message Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=753,
PAGES=56,
DAYS=15,
MONTH=mar,
YEAR=1979,
ABSTRACT="An old version; see RFC 759.",
URL="http://www.rfc-editor.org/rfc/rfc753.txt"
}

@TECHREPORT{rfc754,
AUTHOR="J. B. Postel",
TITLE="Out-of-net host addresses for mail",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=754,
DAYS=15,
MONTH=apr,
YEAR=1979,
ABSTRACT="A discussion of options for addressing computer mail beyond
the ARPANET.",
URL="http://www.rfc-editor.org/rfc/rfc754.txt"
}

@TECHREPORT{rfc755,
AUTHOR="J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=755,
PAGES=12,
DAYS=15,
MONTH=may,
YEAR=1979,
ABSTRACT="This RFC has been replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc755.txt"
}

@TECHREPORT{rfc756,
AUTHOR="J. R. Pickens and Elizabeth J. Feinler and J. E. Mathis",
TITLE="{NIC} name server - a datagram-based information utility",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=756,
PAGES=12,
DAYS=15,
MONTH=jul,
YEAR=1979,
ABSTRACT="Describes a Host Name to Address look up service.",
URL="http://www.rfc-editor.org/rfc/rfc756.txt"
}

@TECHREPORT{rfc757,
AUTHOR="D. P. Deutsch",
TITLE="Suggested solution to the naming, addressing, and delivery problem for
{ARPANET} message systems",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=757,
DAYS=15,
MONTH=sep,
YEAR=1979,
ABSTRACT="Discusses several proposals for handing the name to address to
route processing for computer mail. Favors a solution based on
unique-ids and a data base, see also RFCs 759, 821 and 822.",
URL="http://www.rfc-editor.org/rfc/rfc757.txt"
}

@TECHREPORT{rfc758,
AUTHOR="J. B. Postel",
TITLE="Obsoletes {RFCs:} {755,} {750,739,} {604,} {503,} {433,} 349 Obsoletes
{IENs:} 93",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=758,
MONTH=aug,
YEAR=1979,
URL="http://www.rfc-editor.org/rfc/rfc758.txt"
}

@TECHREPORT{rfc759,
AUTHOR="J. B. Postel",
TITLE="Internet Message Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=759,
PAGES=71,
DAYS=15,
MONTH=aug,
YEAR=1980,
ABSTRACT="The definition of the protocol and format for the exchange of
multimedia mail. Replaces RFC 753.",
URL="http://www.rfc-editor.org/rfc/rfc759.txt"
}

@TECHREPORT{rfc760,
AUTHOR="J. B. Postel",
TITLE="{DoD} standard Internet Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=760,
PAGES=42,
DAYS=15,
MONTH=jan,
YEAR=1980,
ABSTRACT="An old version; see RFC 791.",
URL="http://www.rfc-editor.org/rfc/rfc760.txt"
}

@TECHREPORT{rfc761,
AUTHOR="J. B. Postel",
TITLE="{DoD} standard Transmission Control Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=761,
PAGES=84,
DAYS=15,
MONTH=jan,
YEAR=1980,
ABSTRACT="An old version; see RFC 793.",
URL="http://www.rfc-editor.org/rfc/rfc761.txt"
}

@TECHREPORT{rfc762,
AUTHOR="J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=762,
PAGES=13,
DAYS=15,
MONTH=jan,
YEAR=1980,
ABSTRACT="This RFC has been replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc762.txt"
}

@TECHREPORT{rfc763,
AUTHOR="M. D. Abrams",
TITLE="Role mailboxes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=763,
DAYS=15,
MONTH=may,
YEAR=1980,
ABSTRACT={A call for mailboxes with role names, such as {"}Management{"}.},
URL="http://www.rfc-editor.org/rfc/rfc763.txt"
}

@TECHREPORT{rfc764,
AUTHOR="J. B. Postel",
TITLE="Telnet Protocol specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=764,
PAGES=15,
DAYS=15,
MONTH=jun,
YEAR=1980,
ABSTRACT="The specification of Telnet.",
URL="http://www.rfc-editor.org/rfc/rfc764.txt"
}

@TECHREPORT{rfc765,
AUTHOR="J. B. Postel",
TITLE="File Transfer Protocol specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=765,
DAYS=15,
MONTH=jun,
YEAR=1980,
ABSTRACT="The specification of FTP.",
URL="http://www.rfc-editor.org/rfc/rfc765.txt"
}

@TECHREPORT{rfc766,
AUTHOR="J. B. Postel",
TITLE="Internet Protocol Handbook: Table of contents",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=766,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1980,
ABSTRACT="An out-of-date table of contents for the Internet Protocol
Handbook.",
URL="http://www.rfc-editor.org/rfc/rfc766.txt"
}

@TECHREPORT{rfc767,
AUTHOR="J. B. Postel",
TITLE="Structured format for transmission of multi-media documents",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=767,
PAGES=34,
DAYS=15,
MONTH=aug,
YEAR=1980,
ABSTRACT="The definition of the format for the document of a multimedia
message.",
URL="http://www.rfc-editor.org/rfc/rfc767.txt"
}

@TECHREPORT{rfc768,
AUTHOR="J. B. Postel",
TITLE="User Datagram Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=768,
DAYS=15,
MONTH=aug,
YEAR=1980,
ABSTRACT="The specification of the UDP.",
URL="http://www.rfc-editor.org/rfc/rfc768.txt"
}

@TECHREPORT{rfc769,
AUTHOR="J. B. Postel",
TITLE="Rapicom 450 facsimile file format",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=769,
DAYS=15,
MONTH=sep,
YEAR=1980,
ABSTRACT="The definition of the exchange format of the encoded facsimile
data of the Rapicom 450; see also RFC 798.",
URL="http://www.rfc-editor.org/rfc/rfc769.txt"
}

@TECHREPORT{rfc770,
AUTHOR="J. B. Postel",
TITLE="Obsoletes {RFCs:} {762,} {758,} {755,} {750,} {739,} {604,} {503,} {433,}
349 Obsoletes {IENs:} {127,} {117,} 93",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=770,
MONTH=sep,
YEAR=1980,
URL="http://www.rfc-editor.org/rfc/rfc770.txt"
}

@TECHREPORT{rfc771,
AUTHOR="V. G. Cerf and J. B. Postel",
TITLE="Mail transition plan",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=771,
DAYS=15,
MONTH=sep,
YEAR=1980,
ABSTRACT="A plan for supporting mail service in the transition from NCP
to TCP; see also RFC 801.",
URL="http://www.rfc-editor.org/rfc/rfc771.txt"
}

@TECHREPORT{rfc772,
AUTHOR="S. Sluizer and J. B. Postel",
TITLE="Mail Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=772,
DAYS=15,
MONTH=sep,
YEAR=1980,
ABSTRACT="An old version of a Mail Protocol; see RFC 821.",
URL="http://www.rfc-editor.org/rfc/rfc772.txt"
}

@TECHREPORT{rfc773,
AUTHOR="V. G. Cerf",
TITLE="Comments on {NCP/TCP} mail service transition strategy",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=773,
DAYS=15,
MONTH=oct,
YEAR=1980,
ABSTRACT="A discussion of issues in the transition from NCP to TCP,
particularly as related to MAIL Service.",
URL="http://www.rfc-editor.org/rfc/rfc773.txt"
}

@TECHREPORT{rfc774,
AUTHOR="J. B. Postel",
TITLE="Internet Protocol Handbook Table of Contents",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=774,
MONTH=oct,
YEAR=1980,
URL="http://www.rfc-editor.org/rfc/rfc774.txt"
}

@TECHREPORT{rfc775,
AUTHOR="D. Mankins and D. Franklin and A. D. Owen",
TITLE="Directory oriented {FTP} commands",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=775,
PAGES=6,
DAYS=15,
MONTH=dec,
YEAR=1980,
ABSTRACT="The definition of additional FTP Commands related to directory
management.",
URL="http://www.rfc-editor.org/rfc/rfc775.txt"
}

@TECHREPORT{rfc776,
AUTHOR="J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=776,
PAGES=13,
DAYS=15,
MONTH=jan,
YEAR=1981,
ABSTRACT="This RFC has been replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc776.txt"
}

@TECHREPORT{rfc777,
AUTHOR="J. B. Postel",
TITLE="Internet Control Message Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=777,
PAGES=14,
DAYS=15,
MONTH=apr,
YEAR=1981,
ABSTRACT="An old version; see RFC 792.",
URL="http://www.rfc-editor.org/rfc/rfc777.txt"
}

@TECHREPORT{rfc778,
AUTHOR="D. L. Mills",
TITLE="{DCNET} Internet Clock Service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=778,
DAYS=15,
MONTH=apr,
YEAR=1981,
ABSTRACT="Specifies a format and procedure for the exchange of messages
to maintain synchronized clocks.",
URL="http://www.rfc-editor.org/rfc/rfc778.txt"
}

@TECHREPORT{rfc779,
AUTHOR="E. Killian",
TITLE="Telnet send-location option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=779,
DAYS=15,
MONTH=apr,
YEAR=1981,
ABSTRACT="Definition of this Telnet option.",
URL="http://www.rfc-editor.org/rfc/rfc779.txt"
}

@TECHREPORT{rfc780,
AUTHOR="S. Sluizer and J. B. Postel",
TITLE="Mail Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=780,
PAGES=43,
DAYS=15,
MONTH=may,
YEAR=1981,
ABSTRACT="An outdated Mail protocol; see RFC 821.",
URL="http://www.rfc-editor.org/rfc/rfc780.txt"
}

@TECHREPORT{rfc781,
AUTHOR="Z. Su",
TITLE="Specification of the Internet Protocol {(IP)} timestamp option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=781,
DAYS=15,
MONTH=may,
YEAR=1981,
ABSTRACT="The description of IP Timestamp option, now included in the IP
specification (RFC 791).",
URL="http://www.rfc-editor.org/rfc/rfc781.txt"
}

@TECHREPORT{rfc782,
AUTHOR="J. Nabielsky and A. P. Skelton",
TITLE="Virtual Terminal management model",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=782,
DAYS=15,
MONTH=jan,
YEAR=1981,
ABSTRACT="A description of the elements of a virtual terminal and the
management of communications between them.",
URL="http://www.rfc-editor.org/rfc/rfc782.txt"
}

@TECHREPORT{rfc783,
AUTHOR="Karen Sollins",
TITLE="{TFTP} Protocol (revision {2)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=783,
DAYS=15,
MONTH=jun,
YEAR=1981,
ABSTRACT="The specification of TFTP. Replaces RFCs 768, 764 and IEN 133.",
URL="http://www.rfc-editor.org/rfc/rfc783.txt"
}

@TECHREPORT{rfc784,
AUTHOR="S. Sluizer and J. B. Postel",
TITLE="Mail Transfer Protocol: {ISI} {TOPS20} implementation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=784,
PAGES=62,
DAYS=15,
MONTH=jul,
YEAR=1981,
ABSTRACT="The description of the program structure for the MTP
implementation in the ISI TOPS-20. Outdated.",
URL="http://www.rfc-editor.org/rfc/rfc784.txt"
}

@TECHREPORT{rfc785,
AUTHOR="S. Sluizer and J. B. Postel",
TITLE="Mail Transfer Protocol: {ISI} {TOPS20} file definitions",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=785,
PAGES=62,
DAYS=15,
MONTH=jul,
YEAR=1981,
ABSTRACT="The description of the file format for passing mail to the MTP
program from user mail programs in ISI TOPS-20. Outdated.",
URL="http://www.rfc-editor.org/rfc/rfc785.txt"
}

@TECHREPORT{rfc786,
AUTHOR="S. Sluizer and J. B. Postel",
TITLE="Mail Transfer Protocol: {ISI} {TOPS20} {MTP-NIMAIL} interface",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=786,
PAGES=62,
DAYS=15,
MONTH=jul,
YEAR=1981,
ABSTRACT="The description of the way mail is passed between the MTP and
the NIMAIL programs in ISI TOPS-20. Outdated.",
URL="http://www.rfc-editor.org/rfc/rfc786.txt"
}

@TECHREPORT{rfc787,
AUTHOR="A. Lyman Chapin",
TITLE="Connectionless data transmission survey/tutorial",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=787,
DAYS=15,
MONTH=jul,
YEAR=1981,
ABSTRACT="A discussion of datagram service. Intended for submission to
international standards bodies.",
URL="http://www.rfc-editor.org/rfc/rfc787.txt"
}

@TECHREPORT{rfc788,
AUTHOR="J. B. Postel",
TITLE="Simple Mail Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=788,
PAGES=62,
DAYS=15,
MONTH=nov,
YEAR=1981,
ABSTRACT="An old version; see RFC 821.",
URL="http://www.rfc-editor.org/rfc/rfc788.txt"
}

@TECHREPORT{rfc789,
AUTHOR="E. C. Rosen",
TITLE="Vulnerabilities of network control protocols: An example",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=789,
DAYS=15,
MONTH=jul,
YEAR=1981,
ABSTRACT="A description of an outage in ARPANET service and the process
of determining the cause; also, subtleties of designing network
protocols.",
URL="http://www.rfc-editor.org/rfc/rfc789.txt"
}

@TECHREPORT{rfc790,
AUTHOR="J. B. Postel",
TITLE="Obsoletes {RFCs:} {776,} {770,} {762,} {758,} {755,} {750,} {739,} {604,}
{503,} {433,} 349 Obsoletes {IENs:} {127,} {117,} 93",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=790,
MONTH=sep,
YEAR=1981,
URL="http://www.rfc-editor.org/rfc/rfc790.txt"
}

@TECHREPORT{rfc791,
AUTHOR="J. B. Postel",
TITLE="Internet Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=791,
PAGES=45,
DAYS=15,
MONTH=sep,
YEAR=1981,
ABSTRACT="An updated specification of IP. Replaces RFC 760. This
document specifies the DoD Standard Internet Protocol. This document is
based on six earlier editions of the ARPA Internet Protocol
Specification, and the present text draws heavily from them. This
edition revises aspects of addressing, error handling, option codes, and
the security, precedence, compartments, and handling restriction
features of the internet protocol.",
URL="http://www.rfc-editor.org/rfc/rfc791.txt"
}

@TECHREPORT{rfc792,
AUTHOR="John Postel",
TITLE="Internet Control Message Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=792,
MONTH=sep,
YEAR=1981,
KEYWORDS="ICMP",
ABSTRACT="The Internet Protocol (IP) is used for host-to-host datagram
   service in a system of interconnected networks called the
   Catenet.  The network connecting devices are called Gateways.
   These gateways communicate between themselves for control purposes
   via a Gateway to Gateway Protocol (GGP).  Occasionally a
   gateway or destination host will communicate with a source host, for
   example, to report an error in datagram processing.  For such
   purposes this protocol, the Internet Control Message Protocol (ICMP),
   is used.  ICMP, uses the basic support of IP as if it were a higher
   level protocol, however, ICMP is actually an integral part of IP, and
   must be implemented by every IP module.",
URL="http://www.rfc-editor.org/rfc/rfc792.txt"
}

@TECHREPORT{rfc793,
AUTHOR="J. B. Postel",
TITLE="Transmission Control Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=793,
PAGES=85,
DAYS=15,
MONTH=sep,
YEAR=1981,
ABSTRACT="The specification of TCP. Replaces RFCs 761 and 675. This
document describes the DoD Standard Transmission Control Protocol (TCP).
There have been nine earlier editions of the ARPA TCP specification on
which this standard is based, and the present text draws heavily from
them. There have been many contributors to this work both in terms of
concepts and in terms of text. This edition clarifies several details
and removes the end-of-letter buffer-size adjustments, and redescribes
the letter mechanism as a push function.",
URL="http://www.rfc-editor.org/rfc/rfc793.txt"
}

@TECHREPORT{rfc794,
AUTHOR="V. G. Cerf",
TITLE="Pre-emption",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=794,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1981,
ABSTRACT="Discusses how pre-emption of TCP connection can be
implemented. Replaces IEN 125.",
URL="http://www.rfc-editor.org/rfc/rfc794.txt"
}

@TECHREPORT{rfc795,
AUTHOR="J. B. Postel",
TITLE="Service mappings",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=795,
PAGES=4,
DAYS=15,
MONTH=sep,
YEAR=1981,
ABSTRACT="A description of how the internet type of service is mapped
into the actual service parameters of a few particular networks, and
vice versa.",
URL="http://www.rfc-editor.org/rfc/rfc795.txt"
}

@TECHREPORT{rfc796,
AUTHOR="J. B. Postel",
TITLE="Address mappings",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=796,
PAGES=7,
DAYS=15,
MONTH=sep,
YEAR=1981,
ABSTRACT="A description of the way the addresses of a few actual
networks are mapped into internet addresses.",
URL="http://www.rfc-editor.org/rfc/rfc796.txt"
}

@TECHREPORT{rfc797,
AUTHOR="A. R. Katz",
TITLE="Format for Bitmap files",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=797,
DAYS=15,
MONTH=sep,
YEAR=1981,
ABSTRACT="The description of a simple file format for bitmap data.",
URL="http://www.rfc-editor.org/rfc/rfc797.txt"
}

@TECHREPORT{rfc798,
AUTHOR="A. R. Katz",
TITLE="Decoding facsimile data from the Rapicom 450",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=798,
DAYS=15,
MONTH=sep,
YEAR=1981,
ABSTRACT="A description of the encoding/decoding procedure for Rapicom
450 facsimile machine.",
URL="http://www.rfc-editor.org/rfc/rfc798.txt"
}

@TECHREPORT{rfc799,
AUTHOR="D. L. Mills",
TITLE="Internet name domains",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=799,
DAYS=15,
MONTH=sep,
YEAR=1981,
ABSTRACT="This document suggests that, as the Internet grows, the space
of host names cannot remain a flat space of globally unique names,
therefore a hierarchy of name domains must be introduced; see also RFC
822.",
URL="http://www.rfc-editor.org/rfc/rfc799.txt"
}

@TECHREPORT{rfc801,
AUTHOR="J. B. Postel",
TITLE="{NCP/TCP} transition plan",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=801,
PAGES=21,
DAYS=15,
MONTH=nov,
YEAR=1981,
ABSTRACT="This RFC discusses the conversion of hosts from NCP to TCP.
And making available the principle services: Telnet, File Transfer, and
Mail. These protocols allow all hosts in the ARPA community to share a
common interprocess communication environment.",
URL="http://www.rfc-editor.org/rfc/rfc801.txt"
}

@TECHREPORT{rfc802,
AUTHOR="Andrew G. Malis",
TITLE="{ARPANET} {1822L} Host Access Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=802,
DAYS=15,
MONTH=nov,
YEAR=1981,
ABSTRACT="This document proposed two major changes to the current
ARPANET host access protocol. The first change will allow hosts to use
logical addressing (i.e., host addresses that are independent of their
physical location on the ARPANET) to communicate with each other, and
the second will allow a host to shorten the amount of time that it may
be blocked by its IMP after it presents a message to the network
(currently, the IMP can block further input from a host for up to 15
seconds). See RFCs 852 and 851.",
URL="http://www.rfc-editor.org/rfc/rfc802.txt"
}

@TECHREPORT{rfc803,
AUTHOR="A. Agarwal and M. J. O'Connor and D. L. Mills",
TITLE="Dacom {450/500} facsimile data transcoding",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=803,
DAYS=15,
MONTH=nov,
YEAR=1981,
ABSTRACT="The first part of this RFC describes in detail the Dacom 450
data compression algorithms and is an update and correction to an
earlier memorandum. The second part of this RFC describes briefly the
Dacom 500 data compression algorithm as used by the INTELPOST
electronic-mail network under development by the US Postal Service and
several foreign administrators.",
URL="http://www.rfc-editor.org/rfc/rfc803.txt"
}

@TECHREPORT{rfc804,
AUTHOR="International Telegraph and  ",
TITLE="{CCITT} draft recommendation {T.4}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=804,
DAYS=15,
MONTH=jan,
YEAR=1981,
ABSTRACT="This is the CCITT standard for group 3 facsimile encoding.
This is useful for data compression of bit map data.",
URL="http://www.rfc-editor.org/rfc/rfc804.txt"
}

@TECHREPORT{rfc806,
AUTHOR=" {{National Bureau of Standards}}",
TITLE="Proposed Federal Information Processing Standard: Specification for message
format for computer based message systems",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=806,
MONTH=sep,
YEAR=1981,
ABSTRACT="This RFC deals with Computer Based Message systems which
provides a basis for interaction between different CBMS by defining the
format of messages passed between them. This RFC is replaced by RFC 841.",
URL="http://www.rfc-editor.org/rfc/rfc806.txt"
}

@TECHREPORT{rfc699,
AUTHOR="J. B. Postel and J. Vernon",
TITLE="Request For Comments summary notes: {600-699}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=699,
DAYS=15,
MONTH=nov,
YEAR=1982,
ABSTRACT="A summary of the Request for Comments documents from RFC
600-699.",
URL="http://www.rfc-editor.org/rfc/rfc699.txt"
}

@TECHREPORT{rfc800,
AUTHOR="J. B. Postel and J. Vernon",
TITLE="Request For Comments summary notes: {700-799}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=800,
DAYS=15,
MONTH=nov,
YEAR=1982,
ABSTRACT="This RFC is a slightly annotated list of the 100 RFCs from RFC
700 through RFC 799. This is a status report on these RFCs.",
URL="http://www.rfc-editor.org/rfc/rfc800.txt"
}

@TECHREPORT{rfc805,
AUTHOR="J. B. Postel",
TITLE="Computer mail meeting notes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=805,
PAGES=6,
DAYS=15,
MONTH=feb,
YEAR=1982,
ABSTRACT={This RFC consists of notes from a meeting that was held at
USC/Information Sciences Institute on 11 January 1982, to discuss
addressing issues in computer mail. The major conclusion reached at the
meeting is to extend the {"}username(at)hostname{"} mailbox format to
{"}username(at)host.domain{"}, where the domain itself can be further
structured.},
URL="http://www.rfc-editor.org/rfc/rfc805.txt"
}

@TECHREPORT{rfc807,
AUTHOR="J. B. Postel",
TITLE="Multimedia mail meeting notes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=807,
PAGES=6,
DAYS=15,
MONTH=feb,
YEAR=1982,
ABSTRACT="This RFC consists of notes from a meeting held at
USC/Information Sciences Institute on the 12th of January to discuss
common interests in multimedia computer mail issues and to agree on some
specific initial experiments.",
URL="http://www.rfc-editor.org/rfc/rfc807.txt"
}

@TECHREPORT{rfc808,
AUTHOR="J. B. Postel",
TITLE="Summary of computer mail services meeting held at {BBN} on 10 January 1979",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=808,
PAGES=8,
DAYS=15,
MONTH=mar,
YEAR=1982,
ABSTRACT="This RFC is a very belated attempt to document a meeting that
was held three years earlier to discuss the state of computer mail in
the ARPA community and to reach some conclusions to guide the further
development of computer mail systems such that a coherent total mail
service would continue to be provided.",
URL="http://www.rfc-editor.org/rfc/rfc808.txt"
}

@TECHREPORT{rfc809,
AUTHOR="T. Chang",
TITLE="{UCL} facsimile system",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=809,
DAYS=15,
MONTH=feb,
YEAR=1982,
ABSTRACT="This RFC describes the features of the computerised facsimile
system developed in the Department of Computer Science at UCL. First its
functions are considered and the related experimental work are reported.
Then the disciplines for system design are discussed. Finally, the
implementation of the system are described, while detailed description
are given as appendices.",
URL="http://www.rfc-editor.org/rfc/rfc809.txt"
}

@TECHREPORT{rfc810,
AUTHOR="Elizabeth J. Feinler and K. Harrenstien and Z. Su and V. White",
TITLE="{DoD} Internet host table specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=810,
PAGES=8,
DAYS=15,
MONTH=mar,
YEAR=1982,
ABSTRACT="This RFC specifies a new host table format applicable to both
ARPANET and Internet needs. In addition to host name to host address
translation and selected protocol information, we have also included
network and gateway name to address correspondence, and host operating
system information. This RFC obsoletes the host table described in RFC
608.",
URL="http://www.rfc-editor.org/rfc/rfc810.txt"
}

@TECHREPORT{rfc811,
AUTHOR="K. Harrenstien and V. White and Elizabeth J. Feinler",
TITLE="Hostnames Server",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=811,
PAGES=4,
DAYS=15,
MONTH=mar,
YEAR=1982,
ABSTRACT="This RFC gives a description of what the Hostnames Server is
and how to access it. The function of this particular server is to
deliver machine-readable name/address information describing networks,
gateways, hosts, and eventually domains, within the Internet
environment.",
URL="http://www.rfc-editor.org/rfc/rfc811.txt"
}

@TECHREPORT{rfc812,
AUTHOR="K. Harrenstien and V. White",
TITLE="{NICNAME/WHOIS}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=812,
PAGES=3,
DAYS=15,
MONTH=mar,
YEAR=1982,
ABSTRACT="This RFC gives a description of what the NICNAME/WHOIS Server
is and how to access it. This server together with the corresponding
Identification Data Base provides online directory look-up equivalent to
the ARPANET Directory.",
URL="http://www.rfc-editor.org/rfc/rfc812.txt"
}

@TECHREPORT{rfc813,
AUTHOR="D. D. Clark",
TITLE="Window and Acknowledgement Strategy in {TCP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=813,
DAYS=15,
MONTH=jul,
YEAR=1982,
ABSTRACT="This RFC describes implementation strategies to deal with two
mechanisms in TCP, the window and the acknowledgement. It also presents
a particular set of algorithms which have received testing in the field,
and which appear to work properly with each other. With more experience,
these algorithms may become part of the formal specification, until such
time their use is recommended.",
URL="http://www.rfc-editor.org/rfc/rfc813.txt"
}

@TECHREPORT{rfc814,
AUTHOR="D. D. Clark",
TITLE="Name, addresses, ports, and routes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=814,
DAYS=15,
MONTH=jul,
YEAR=1982,
ABSTRACT="This RFC gives suggestions and guidance for the design of the
tables and algorithms necessary to keep track of these various sorts of
identifiers inside a host implementation of TCP/IP.",
URL="http://www.rfc-editor.org/rfc/rfc814.txt"
}

@TECHREPORT{rfc815,
AUTHOR="D. D. Clark",
TITLE="{IP} datagram reassembly algorithms",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=815,
DAYS=15,
MONTH=jul,
YEAR=1982,
ABSTRACT="This RFC describes an alternate approach of dealing with
reassembly which reduces the bookkeeping problem to a minimum, and
requires only one buffer for storage equal in size to the final datagram
being reassembled, which can reassemble a datagram from any number of
fragments arriving in any order with any possible pattern of overlap and
duplication, and which is appropriate for almost any sort of operating
system.",
URL="http://www.rfc-editor.org/rfc/rfc815.txt"
}

@TECHREPORT{rfc816,
AUTHOR="D. D. Clark",
TITLE="Fault isolation and recovery",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=816,
DAYS=15,
MONTH=jul,
YEAR=1982,
ABSTRACT="This RFC describes the portion of fault isolation and recovery
which is the responsibility of the host.",
URL="http://www.rfc-editor.org/rfc/rfc816.txt"
}

@TECHREPORT{rfc817,
AUTHOR="D. D. Clark",
TITLE="Modularity and efficiency in protocol implementation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=817,
DAYS=15,
MONTH=jul,
YEAR=1982,
ABSTRACT="This RFC will discuss some of the commonly encountered reasons
why protocol implementations seem to run slowly.",
URL="http://www.rfc-editor.org/rfc/rfc817.txt"
}

@TECHREPORT{rfc818,
AUTHOR="J. B. Postel",
TITLE="Remote User Telnet service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=818,
PAGES=2,
DAYS=15,
MONTH=nov,
YEAR=1982,
ABSTRACT="This RFC is the specification of an application protocol. Any
host that implements this application level service must follow this
protocol.",
URL="http://www.rfc-editor.org/rfc/rfc818.txt"
}

@TECHREPORT{rfc819,
AUTHOR="Z. Su and J. B. Postel",
TITLE="Domain naming convention for Internet user applications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=819,
PAGES=18,
DAYS=15,
MONTH=aug,
YEAR=1982,
ABSTRACT="This RFC is an attempt to clarify the generalization of the
Domain Naming Convention, the Internet Naming Convention, and to explore
the implications of its adoption for ARPA-Internet name service and user
applications.",
URL="http://www.rfc-editor.org/rfc/rfc819.txt"
}

@TECHREPORT{rfc820,
AUTHOR="J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=820,
PAGES=22,
DAYS=15,
MONTH=aug,
YEAR=1982,
ABSTRACT="This RFC is is replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc820.txt"
}

@TECHREPORT{rfc821,
AUTHOR="J. B. Postel",
TITLE="Simple Mail Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=821,
PAGES=68,
DAYS=15,
MONTH=aug,
YEAR=1982,
ABSTRACT="The objective of Simple Mail Transfer Protocol (SMTP) is to
transfer mail reliably and efficiently. SMTP is independent of the
particular transmission subsystem and requires only a reliable ordered
data stream channel. Obsoletes RFCs 788, 780, 772.",
URL="http://www.rfc-editor.org/rfc/rfc821.txt"
}

@TECHREPORT{rfc822,
AUTHOR="D. H. Crocker",
TITLE="Standard for the format of {ARPA} Internet text messages",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=822,
DAYS=15,
MONTH=aug,
YEAR=1982,
ABSTRACT="This document revises the specifications in RFC 733, in order
to serve the needs of the larger and more complex ARPA-Internet. Some of
RFC 733's features failed to gain adequate acceptance. In order to
simplify the standard and the software that follows it, these features
have been removed. A different addressing scheme is used, to handle the
case of internetwork mail; and the concept of re-transmission has been
introduced. Obsoletes RFC 733, NIC 41952.",
URL="http://www.rfc-editor.org/rfc/rfc822.txt"
}

@TECHREPORT{rfc823,
AUTHOR="Robert Hinden and A. Sheltzer",
TITLE="{DARPA} Internet gateway",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=823,
DAYS=15,
MONTH=sep,
YEAR=1982,
ABSTRACT="This RFC is a status report on the Internet Gateway developed
by BBN. It describes the Internet Gateway as of September 1982. This
memo presents detailed descriptions of message formats and gateway
procedures, however, this is not an implementation specification, and
such details are subject to change.",
URL="http://www.rfc-editor.org/rfc/rfc823.txt"
}

@TECHREPORT{rfc824,
AUTHOR="W. I. MacGregor and D. C. Tappan",
TITLE="{CRONUS} Virtual Local Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=824,
DAYS=15,
MONTH=aug,
YEAR=1982,
ABSTRACT="The purpose of this note is to describe the CRONUS Virtual
Local Network, especially the addressing related features. These
features include a method for mapping between Internet Addresses and
Local Network addresses. This is a topic of current concern in the
ARPA-Internet community. This note is intended to stimulate discussion.
This is not a specification of an ARPA-Internet Standard.",
URL="http://www.rfc-editor.org/rfc/rfc824.txt"
}

@TECHREPORT{rfc825,
AUTHOR="J. B. Postel",
TITLE="Request for comments on Requests For Comments",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=825,
PAGES=2,
DAYS=15,
MONTH=nov,
YEAR=1982,
ABSTRACT="This RFC is intended to clarify the status of RFCs and to
provide some guidance for the authors of RFCs in the future. It is in a
sense a specification for RFCs.",
URL="http://www.rfc-editor.org/rfc/rfc825.txt"
}

@TECHREPORT{rfc826,
AUTHOR="D. C. Plummer",
TITLE="Ethernet Address Resolution Protocol: Or converting network protocol
addresses to 48.bit Ethernet address for transmission on Ethernet hardware",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=826,
DAYS=15,
MONTH=nov,
YEAR=1982,
ABSTRACT="The purpose of this RFC is to present a method of Converting
Protocol Addresses (e.g., IP addresses) to Local Network Addresses
(e.g., Ethernet addresses). This is an issue of general concern in the
ARPA-Internet Community at this time. The method proposed here is
presented for your consideration and comment. This is not the
specification of an ARPA-Internet Standard.",
URL="http://www.rfc-editor.org/rfc/rfc826.txt"
}

@TECHREPORT{rfc827,
AUTHOR="E. C. Rosen",
TITLE="Exterior Gateway Protocol {(EGP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=827,
DAYS=15,
MONTH=oct,
YEAR=1982,
ABSTRACT="This RFC is proposed to establish a standard for Gateway to
Gateway procedures that allow the Gateways to be mutually suspicious.
This document is a DRAFT for that standard. Your comments are strongly
encouraged.",
URL="http://www.rfc-editor.org/rfc/rfc827.txt"
}

@TECHREPORT{rfc828,
AUTHOR="K. Owen",
TITLE={Data communications: {IFIP's} international {"}network{"} of experts},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=828,
DAYS=15,
MONTH=aug,
YEAR=1982,
ABSTRACT="This RFC is distributed to inform the ARPA-Internet community
of the activities of the IFIP technical committee on Data
Communications, and to encourage participation in those activities.",
URL="http://www.rfc-editor.org/rfc/rfc828.txt"
}

@TECHREPORT{rfc829,
AUTHOR="V. G. Cerf",
TITLE="Packet satellite technology reference sources",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=829,
PAGES=5,
DAYS=15,
MONTH=nov,
YEAR=1982,
ABSTRACT="This RFC describes briefly the packet satellite technology
developed by the Defense Advanced Research Projects Agency and several
other participating organizations in the U.K. and Norway and provides a
bibliography of relevant papers for researchers interested in
experimental and operational experience with this dynamic
satellite-sharing technique.",
URL="http://www.rfc-editor.org/rfc/rfc829.txt"
}

@TECHREPORT{rfc830,
AUTHOR="Z. Su",
TITLE="Distributed system for Internet name service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=830,
DAYS=15,
MONTH=oct,
YEAR=1982,
ABSTRACT="This RFC proposes a distributed name service for
ARPA-Internet. Its purpose is to focus discussion on the subject. It is
hoped that a general consensus will emerge leading eventually to the
adoption of standards.",
URL="http://www.rfc-editor.org/rfc/rfc830.txt"
}

@TECHREPORT{rfc831,
AUTHOR="R. Braden",
TITLE="Backup access to the European side of {SATNET}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=831,
DAYS=15,
MONTH=dec,
YEAR=1982,
ABSTRACT="The purpose of this RFC is to focus discussion on a particular
Internet problem: a backup path for software maintenance of the European
sector of the Internet, for use when SATNET is partitioned. We propose a
mechanism, based upon the Source Routing option of IP, to reach European
Internet sites via the VAN Gateway and UCL. This proposal is not
intended as a standard at this time.",
URL="http://www.rfc-editor.org/rfc/rfc831.txt"
}

@TECHREPORT{rfc832,
AUTHOR="D. Smallberg",
TITLE="Who talks {TCP?}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=832,
PAGES=13,
DAYS=15,
MONTH=dec,
YEAR=1982,
ABSTRACT="This RFC is a survey of hosts to identify the implementation
status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from
the NIC hostname table of 2-Dec-82. The tests were run on 7-Dec-82.",
URL="http://www.rfc-editor.org/rfc/rfc832.txt"
}

@TECHREPORT{rfc871,
AUTHOR="M. A. Padlipsky",
TITLE="Perspective on the {ARPANET} reference model",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=871,
DAYS=15,
MONTH=sep,
YEAR=1982,
ABSTRACT="This RFC is primarily intended as a perspective on the ARM and
points out some of the differences between the ARM and the ISORM which
were expressed by members in NWG general meetings, NWG protocol design
committee meetings, the ARPA-Internet Working Group, and private
conversations over the intervening years. Originally published as M82-47
by the MITRE Corporation, Bedford, Massachusetts.",
URL="http://www.rfc-editor.org/rfc/rfc871.txt"
}

@TECHREPORT{rfc872,
AUTHOR="M. A. Padlipsky",
TITLE="{TCP-on-a-LAN}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=872,
DAYS=15,
MONTH=sep,
YEAR=1982,
ABSTRACT="This memo attacks the notion that TCP cannot be appropriate
for use on a Local Area Network. Originally published as M82-48 by the
MITRE Corporation, Bedford Massachusetts.",
URL="http://www.rfc-editor.org/rfc/rfc872.txt"
}

@TECHREPORT{rfc873,
AUTHOR="M. A. Padlipsky",
TITLE="Illusion of vendor support",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=873,
DAYS=15,
MONTH=sep,
YEAR=1982,
ABSTRACT="This memo takes issue with the claim that international
standards in computer protocols presently provide a basis for low cost
vendor supported protocol implementations. Originally published as
M82-49 by the MITRE Corporation, Bedford, Massachusetts.",
URL="http://www.rfc-editor.org/rfc/rfc873.txt"
}

@TECHREPORT{rfc874,
AUTHOR="M. A. Padlipsky",
TITLE="Critique of {X.25}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=874,
DAYS=15,
MONTH=sep,
YEAR=1982,
ABSTRACT="This RFC is an analysis of X.25 pointing out some problems in
the conceptual model, particularly the conflict between the interface
aspects and the end-to-end aspects. The memo also touches on security,
and implementation issues. Originally published as M82-50 by the MITRE
Corporation, Bedford, Massachusetts.",
URL="http://www.rfc-editor.org/rfc/rfc874.txt"
}

@TECHREPORT{rfc875,
AUTHOR="M. A. Padlipsky",
TITLE="Gateways, architectures, and heffalumps",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=875,
DAYS=15,
MONTH=sep,
YEAR=1982,
ABSTRACT={This RFC is a discussion about the role of gateways in an
internetwork, especially the problems of translating or mapping
protocols between different protocol suites. The discussion notes
possible functionality mis-matches, undesirable routing {"}singularity
points{"}, flow control issues, and high cost of translating gateways.
Originally published as M82-51 by the MITRE Corporation, Bedford,
Massachusetts.},
URL="http://www.rfc-editor.org/rfc/rfc875.txt"
}

@TECHREPORT{rfc836,
AUTHOR="D. Smallberg",
TITLE="Who talks {TCP?}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=836,
PAGES=13,
DAYS=15,
MONTH=jan,
YEAR=1983,
ABSTRACT="This RFC is a survey of hosts to identify the implementation
status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from
the NIC hostname table of 20-Dec-82. The tests were run on 4-Jan-83
through 5-Jan-83.",
URL="http://www.rfc-editor.org/rfc/rfc836.txt"
}

@TECHREPORT{rfc840,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Official protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=840,
PAGES=23,
DAYS=15,
MONTH=apr,
YEAR=1983,
ABSTRACT="This RFC has been replaced by RFC 991.",
URL="http://www.rfc-editor.org/rfc/rfc840.txt"
}

@TECHREPORT{rfc841,
AUTHOR=" {{National Bureau of Standards}}",
TITLE="Specification for message format for Computer Based Message Systems",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=841,
MONTH=jan,
YEAR=1983,
ABSTRACT="This RFC is FIPS 98. The purpose of distributing this document
as an RFC is to make it easily accessible to the ARPA research
community. This RFC does not specify a standard for the ARPA-Internet.
Obsoletes RFC 806.",
URL="http://www.rfc-editor.org/rfc/rfc841.txt"
}

@TECHREPORT{rfc842,
AUTHOR="D. Smallberg",
TITLE="Who talks {TCP?} - survey of 1 February 83",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=842,
PAGES=14,
DAYS=15,
MONTH=feb,
YEAR=1983,
ABSTRACT="This RFC is a survey of hosts to identify the implementation
status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from
the NIC hostname table of 28-Jan-83. The tests were run on 1-Feb-83 and
on 2-Feb-83 ISI-VAXA.ARPA.",
URL="http://www.rfc-editor.org/rfc/rfc842.txt"
}

@TECHREPORT{rfc843,
AUTHOR="D. Smallberg",
TITLE="Who talks {TCP?} - survey of 8 February 83",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=843,
PAGES=14,
DAYS=15,
MONTH=feb,
YEAR=1983,
ABSTRACT="This RFC is a survey of hosts to identify the implementation
status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from
the NIC hostname table of 3-Feb-83. The tests were run on 8-Feb-83 and
on 9-Feb-83 from ISI-VAXA.ARPA.",
URL="http://www.rfc-editor.org/rfc/rfc843.txt"
}

@TECHREPORT{rfc844,
AUTHOR="R. Clements",
TITLE="Who talks {ICMP,} too? - Survey of 18 February 1983",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=844,
PAGES=5,
DAYS=15,
MONTH=feb,
YEAR=1983,
ABSTRACT="This survey determines how many hosts are able to respond to
Telnet connections from a user at a class C site. This requires, in
addition to IP and TCP, participation in gateway routing via ICMP and
handling of Class C addresses. The list of hosts was taken from RFC 843,
extracting only those hosts which are listed there as accepting Telnet
connection. The tests were run on 18-Feb-83.",
URL="http://www.rfc-editor.org/rfc/rfc844.txt"
}

@TECHREPORT{rfc845,
AUTHOR="D. Smallberg",
TITLE="Who talks {TCP?} - survey of 15 February 1983",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=845,
PAGES=14,
DAYS=15,
MONTH=feb,
YEAR=1983,
ABSTRACT="This RFC is a survey of hosts to identify the implementation
status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from
the NIC hostname table of 3-Feb-83. The tests were run on 15-Feb-83 from
ISI-VAXA.ARPA.",
URL="http://www.rfc-editor.org/rfc/rfc845.txt"
}

@TECHREPORT{rfc846,
AUTHOR="D. Smallberg",
TITLE="Who talks {TCP?} - survey of 22 February 1983",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=846,
PAGES=14,
DAYS=15,
MONTH=feb,
YEAR=1983,
ABSTRACT="This RFC is a survey of hosts to identify the implementation
status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from
the NIC hostname table of 18-Feb-83. The tests were run on 22-Feb-83
from ISI-VAXA.ARPA.",
URL="http://www.rfc-editor.org/rfc/rfc846.txt"
}

@TECHREPORT{rfc847,
AUTHOR="A. Westine and D. Smallberg and J. B. Postel",
TITLE="Summary of Smallberg surveys",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=847,
PAGES=2,
DAYS=15,
MONTH=feb,
YEAR=1983,
ABSTRACT="This is a summary of the surveys of Telnet, FTP and Mail
(SMTP) servers conducted by David Smallberg in December 1982, January
and February 1983 as reported in RFC 832-843, 845-846. This memo
extracts the number of hosts that accepted the connection to their
server for each of Telnet, FTP, and SMTP, and compares it to the total
host in the ARPA-Internet (not counting TACs or ECHOS).",
URL="http://www.rfc-editor.org/rfc/rfc847.txt"
}

@TECHREPORT{rfc848,
AUTHOR="D. Smallberg",
TITLE={Who provides the {"}little{"} {TCP} services?},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=848,
PAGES=5,
DAYS=15,
MONTH=mar,
YEAR=1983,
ABSTRACT={This RFC lists those hosts which provide any of these {"}little{"}
TCP services: The list of hosts were taken from the NIC hostname table
of 24-Feb-83. The tests were run on February 23 and 24, and March 3 and
5 from ISI-VAXA.ARPA.},
URL="http://www.rfc-editor.org/rfc/rfc848.txt"
}

@TECHREPORT{rfc849,
AUTHOR="M. R. Crispin",
TITLE="Suggestions for improved host table distribution",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=849,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This RFC actually is a request for comments. The issue dealt
with is that of a naming registry update procedure, both as exists
currently and what could exist in the future. None of the proposed
solutions are intended as standards at this time; rather it is hoped
that a general consensus will emerge as the appropriate solution,
leaving eventually to the adoption of standards.",
URL="http://www.rfc-editor.org/rfc/rfc849.txt"
}

@TECHREPORT{rfc850,
AUTHOR="M. R. Horton",
TITLE="Standard for interchange of {USENET} messages",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=850,
DAYS=15,
MONTH=jun,
YEAR=1983,
ABSTRACT="This memo is distributed as an RFC only to make this
information easily accessible to researchers in the ARPA-Internet
community. It does not specify an Internet standard. This RFC defines
the standard format for interchange of Network News articles among
USENET sites. It describes the format for articles themselves, and gives
partial standards for transmission of news. The news transmission is not
entirely standardized in order to give a good deal of flexibility to the
individual hosts to choose transmission hardware and software, whether
to batch news and so on.",
URL="http://www.rfc-editor.org/rfc/rfc850.txt"
}

@TECHREPORT{rfc851,
AUTHOR="Andrew G. Malis",
TITLE="{ARPANET} {1822L} Host Access Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=851,
DAYS=15,
MONTH=apr,
YEAR=1983,
ABSTRACT="This RFC specifies the ARPANET 1822L Host Access Protocol,
which is a successor to the existing 1822 Host Access Protocol. 1822L
allows ARPANET hosts to use logical names as well as 1822's physical
port locations to address each other. This RFC is also being presented
as a solicitation of comments on 1822L, especially from host network
software implementers and maintainers. Obsoletes RFC 802.",
URL="http://www.rfc-editor.org/rfc/rfc851.txt"
}

@TECHREPORT{rfc852,
AUTHOR="Andrew G. Malis",
TITLE="{ARPANET} short blocking feature",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=852,
DAYS=15,
MONTH=apr,
YEAR=1983,
ABSTRACT="This RFC specifies the ARPANET Short Blocking Feature, which
will allow ARPANET hosts to optionally shorten the IMP's host blocking
timer. This Feature is a replacement of the ARPANET non-blocking host
interface, which was never implemented, and will be available to hosts
using either the 1822 or 1822L Host Access Protocol. This RFC is also
being presented as a solicitation of comments on the Short Blocking
Feature, especially from host network software implementers and
maintainers.",
URL="http://www.rfc-editor.org/rfc/rfc852.txt"
}

@TECHREPORT{rfc854,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="Telnet Protocol Specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=854,
PAGES=15,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT={This is the specification of the Telnet protocol used for
remote terminal access in the ARPA-Internet. The purpose of the Telnet
Protocol is to provide a fairly general, bi-directional, eight-bit byte
oriented communications facility. Its primary goal is to allow a
standard method of interfacing terminal devices and terminal-oriented
processes to each other. It is envisioned that the protocol may also be
used for terminal-terminal communication ({"}linking{"}) and
process-process
communication (distributed computation). This RFC specifies a standard
for the ARPA-Internet community. Hosts on the ARPA-Internet are expected
to adopt and implement this standard. Obsoletes NIC 18639.},
URL="http://www.rfc-editor.org/rfc/rfc854.txt"
}

@TECHREPORT{rfc855,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="Telnet Option Specifications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=855,
PAGES=3,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This memo specifies the general form for Telnet options and
the directions for their specification. This RFC specifies a standard
for the ARPA-Internet community. Hosts on the ARPA-Internet are expected
to adopt and implement this standard. Obsoletes RFC 651, NIC 18640.",
URL="http://www.rfc-editor.org/rfc/rfc855.txt"
}

@TECHREPORT{rfc856,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="Telnet Binary Transmission",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=856,
PAGES=4,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This Telnet Option enables a binary data mode between the
Telnet modules. This RFC specifies a standard for the ARPA-Internet
community. Hosts on the ARPA-Internet are expected to adopt and
implement this standard. Obsoletes NIC 15389.",
URL="http://www.rfc-editor.org/rfc/rfc856.txt"
}

@TECHREPORT{rfc857,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="Telnet Echo Option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=857,
PAGES=5,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This Telnet Option enables remote echoing by the other Telnet
module. This RFC specifies a standard for the ARPA-Internet community.
Hosts on the ARPA-Internet are expected to adopt and implement this
standard. Obsoletes NIC 15390.",
URL="http://www.rfc-editor.org/rfc/rfc857.txt"
}

@TECHREPORT{rfc858,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="Telnet Suppress Go Ahead Option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=858,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This Telnet Option disables the exchange of go-ahead signals
between the Telnet modules. This RFC specifies a standard for the
ARPA-Internet community. Hosts on the ARPA-Internet are expected to
adopt and implement this standard. Obsoletes NIC 15392.",
URL="http://www.rfc-editor.org/rfc/rfc858.txt"
}

@TECHREPORT{rfc859,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="Telnet Status Option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=859,
PAGES=3,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This Telnet Option provides a way to determine the other
Telnet module's view of the status of options. This RFC specifies a
standard for the ARPA-Internet community. Hosts on the ARPA-Internet are
expected to adopt and implement this standard. Obsoletes RFC 651 (NIC
31154).",
URL="http://www.rfc-editor.org/rfc/rfc859.txt"
}

@TECHREPORT{rfc860,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="Telnet Timing Mark Option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=860,
PAGES=4,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This Telnet Option provides a way to check the roundtrip path
between two Telnet modules. This RFC specifies a standard for the
ARPA-Internet community. Hosts on the ARPA-Internet are expected to
adopt and implement this standard. Obsoletes NIC 16238.",
URL="http://www.rfc-editor.org/rfc/rfc860.txt"
}

@TECHREPORT{rfc861,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="Telnet Extended Options: List Option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=861,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This Telnet Option provides a mechanism for extending the set
of possible options. This RFC specifies a standard for the ARPA-Internet
community. Hosts on the ARPA-Internet are expected to adopt and
implement this standard. Obsoletes NIC 16239.",
URL="http://www.rfc-editor.org/rfc/rfc861.txt"
}

@TECHREPORT{rfc862,
AUTHOR="J. B. Postel",
TITLE="Echo Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=862,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This RFC specifies a standard for the ARPA-Internet community.
Hosts on the ARPA-Internet that choose to implement a Echo Protocol are
expected to adopt and implement this standard. The Echo service simply
sends back to the originating source any data it receives.",
URL="http://www.rfc-editor.org/rfc/rfc862.txt"
}

@TECHREPORT{rfc863,
AUTHOR="J. B. Postel",
TITLE="Discard Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=863,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This RFC specifies a standard for the ARPA-Internet community.
Hosts on the ARPA-Internet that choose to implement a Discard Protocol
are expected to adopt and implement this standard. The Discard service
simply throws away any data it receives.",
URL="http://www.rfc-editor.org/rfc/rfc863.txt"
}

@TECHREPORT{rfc864,
AUTHOR="J. B. Postel",
TITLE="Character Generator Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=864,
PAGES=3,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This RFC specifies a standard for the ARPA-Internet community.
Hosts on the ARPA-Internet that choose to implement a Character
Generator Protocol are expected to adopt and implement this standard.
The Character Generator service simply sends data without regard to the
input.",
URL="http://www.rfc-editor.org/rfc/rfc864.txt"
}

@TECHREPORT{rfc865,
AUTHOR="J. B. Postel",
TITLE="Quote of the Day Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=865,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This RFC specifies a standard for the ARPA-Internet community.
Hosts on the ARPA-Internet that choose to implement a Quote of the Day
Protocol are expected to adopt and implement this standard. The Quote of
the Day service simply sends a short message without regard to the
input.",
URL="http://www.rfc-editor.org/rfc/rfc865.txt"
}

@TECHREPORT{rfc866,
AUTHOR="J. B. Postel",
TITLE="Active users",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=866,
PAGES=1,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This RFC specifies a standard for the ARPA-Internet community.
Hosts on the ARPA-Internet that choose to implement an Active Users
Protocol are expected to adopt and implement this standard. The Active
Users service simply sends a list of the currently active users on the
host without regard to the input.",
URL="http://www.rfc-editor.org/rfc/rfc866.txt"
}

@TECHREPORT{rfc867,
AUTHOR="J. B. Postel",
TITLE="Daytime Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=867,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This RFC specifies a standard for the ARPA-Internet community.
Hosts on the ARPA-Internet that choose to implement a Daytime Protocol
are expected to adopt and implement this standard. The Daytime service
simply sends the current date and time as a character string without
regard to the input.",
URL="http://www.rfc-editor.org/rfc/rfc867.txt"
}

@TECHREPORT{rfc868,
AUTHOR="J. B. Postel and K. Harrenstien",
TITLE="Time Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=868,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1983,
ABSTRACT="This RFC specifies a standard for the ARPA-Internet community.
Hosts on the ARPA-Internet that choose to implement a Time Protocol are
expected to adopt and implement this standard. This protocol provides a
site-independent, machine readable date and time. The Time service sends
back to the originating source the time in seconds since midnight on
January first 1900.",
URL="http://www.rfc-editor.org/rfc/rfc868.txt"
}

@TECHREPORT{rfc869,
AUTHOR="R. Hinden",
TITLE="Host Monitoring Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=869,
DAYS=15,
MONTH=dec,
YEAR=1983,
ABSTRACT="This RFC specifies the Host Monitoring Protocol used to
collect information from various types of hosts in the Internet.
Designers of Internet communications software are encouraged to consider
this protocol as a means of monitoring the behavior of their creations.",
URL="http://www.rfc-editor.org/rfc/rfc869.txt"
}

@TECHREPORT{rfc870,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=870,
PAGES=26,
DAYS=15,
MONTH=oct,
YEAR=1983,
ABSTRACT="This RFC has been replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc870.txt"
}

@TECHREPORT{rfc876,
AUTHOR="D. Smallberg",
TITLE="Survey of {SMTP} implementations",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=876,
PAGES=13,
DAYS=15,
MONTH=sep,
YEAR=1983,
ABSTRACT="This RFC is a survey of implementation status. It does not
specify an official protocol, but rather notes the status of
implementation of aspects of a protocol. It is expected that the status
of the hosts reported on will change. This information must be treated
as a snapshot of the state of these implemetations.",
URL="http://www.rfc-editor.org/rfc/rfc876.txt"
}

@TECHREPORT{rfc877,
AUTHOR="John T. Korb",
TITLE="Standard for the transmission of {IP} datagrams over public data networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=877,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1983,
ABSTRACT="This RFC specifies a standard adopted by CSNET, the VAN
gateway, and other organizations for the transmission of IP datagrams
over the X.25-based public data networks.",
URL="http://www.rfc-editor.org/rfc/rfc877.txt"
}

@TECHREPORT{rfc879,
AUTHOR="J. B. Postel",
TITLE="{TCP} maximum segment size and related topics",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=879,
PAGES=11,
DAYS=15,
MONTH=nov,
YEAR=1983,
ABSTRACT={This RFC discusses the TCP Maximum Segment Size Option and
related topics. The purpose is to clarify some aspects of TCP and its
interaction with IP. This memo is a clarification to the TCP
specification, and contains information that may be considered as
{"}advice to implementers{"}.},
URL="http://www.rfc-editor.org/rfc/rfc879.txt"
}

@TECHREPORT{rfc881,
AUTHOR="J. B. Postel",
TITLE="Domain names plan and schedule",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=881,
PAGES=10,
DAYS=15,
MONTH=nov,
YEAR=1983,
ABSTRACT="This RFC outlines a plan and schedule for the implementation
of domain style names throughout the DDN/ARPA-Internet community. The
introduction of domain style names will impact all hosts on the
DDN/ARPA-Internet.",
URL="http://www.rfc-editor.org/rfc/rfc881.txt"
}

@TECHREPORT{rfc882,
AUTHOR="P. V. Mockapetris",
TITLE="Domain names: Concepts and facilities",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=882,
PAGES=31,
DAYS=15,
MONTH=nov,
YEAR=1983,
ABSTRACT="This RFC introduces domain style names, their use for
DDN/ARPA-Internet mail and host address support, and the protocol and
servers used to implement domain name facilities.",
URL="http://www.rfc-editor.org/rfc/rfc882.txt"
}

@TECHREPORT{rfc883,
AUTHOR="P. V. Mockapetris",
TITLE="Domain names: Implementation specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=883,
PAGES=73,
DAYS=15,
MONTH=nov,
YEAR=1983,
ABSTRACT="This RFC discusses the implementation of domain name servers
and resolvers, specifies the format of transactions, and discusses the
use of domain names in the context of existing mail systems and other
network software.",
URL="http://www.rfc-editor.org/rfc/rfc883.txt"
}

@TECHREPORT{rfc884,
AUTHOR="M. Solomon and E. Wimmers",
TITLE="Telnet terminal type option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=884,
PAGES=5,
DAYS=15,
MONTH=dec,
YEAR=1983,
ABSTRACT="This RFC specifies a standard for the ARPA-Internet community.
It specifies a method for exchanging terminal type information in the
Telnet protocol.",
URL="http://www.rfc-editor.org/rfc/rfc884.txt"
}

@TECHREPORT{rfc885,
AUTHOR="J. B. Postel",
TITLE="Telnet end of record option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=885,
PAGES=2,
DAYS=15,
MONTH=dec,
YEAR=1983,
ABSTRACT="This RFC specifies a standard for the ARPA-Internet community.
It specifies a method for marking the end of records in data transmitted
on Telnet connections.",
URL="http://www.rfc-editor.org/rfc/rfc885.txt"
}

@TECHREPORT{rfc886,
AUTHOR="Marshall T. Rose",
TITLE="Proposed standard for message header munging",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=886,
PAGES=16,
DAYS=15,
MONTH=dec,
YEAR=1983,
ABSTRACT="This RFC specifies a draft standard for the ARPA-Internet
community. It describes the rules to be used when transforming mail from
the conventions of one message system to those of another message
system. In particular, the treatment of header fields, and recipient
addresses is specified.",
URL="http://www.rfc-editor.org/rfc/rfc886.txt"
}

@TECHREPORT{rfc887,
AUTHOR="M. J. Accetta",
TITLE="Resource Location Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=887,
PAGES=16,
DAYS=15,
MONTH=dec,
YEAR=1983,
ABSTRACT="This RFC specifies a draft standard for the ARPA-Internet
community. It describes a resource location protocol for use in the
ARPA-Internet. It is most useful on networks employing technologies
which support some method of broadcast addressing, however it may also
be used on other types of networks. For maximum benefit, all hosts which
provide significant resources or services to other hosts on the
ARPA-Internet should implement this protocol. Hosts failing to implement
the Resource Location Protocol risk being ignored by other hosts which
are attempting to locate resources on the ARPA-Internet.",
URL="http://www.rfc-editor.org/rfc/rfc887.txt"
}

@TECHREPORT{rfc889,
AUTHOR="D. L. Mills",
TITLE="Internet delay experiments",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=889,
DAYS=15,
MONTH=dec,
YEAR=1983,
ABSTRACT="This memo reports on some measurements of round-trip times in
the Internet and suggests some possible improvements to the TCP
retransmission timeout calculation. This memo is both a status report on
the ARPA-Internet and advice to TCP implementers.",
URL="http://www.rfc-editor.org/rfc/rfc889.txt"
}

@TECHREPORT{rfc891,
AUTHOR="D. L. Mills",
TITLE="{DCN} local-network protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=891,
PAGES=26,
DAYS=15,
MONTH=dec,
YEAR=1983,
ABSTRACT="This RFC provides a description of the DCN protocols for
maintaining connectivity, routing, and clock information in a local
network. These procedures may be of interest to the designers and
implementers of other local networks.",
URL="http://www.rfc-editor.org/rfc/rfc891.txt"
}

@TECHREPORT{rfc892,
AUTHOR=" {{International Organization for Standardization}}",
TITLE="{ISO} Transport Protocol specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=892,
MONTH=dec,
YEAR=1983,
ABSTRACT="This is a draft version of the transport protocol being
standardized by the ISO. This version also appeared in the ACM SIGCOMM
Computer Communication Review (V.12, N.3-4) July-October 1982. This
version is now out of date.",
URL="http://www.rfc-editor.org/rfc/rfc892.txt"
}

@TECHREPORT{rfc888,
AUTHOR="L. Seamonson and E. C. Rosen",
TITLE={{{"}STUB{"}} Exterior Gateway Protocol},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=888,
DAYS=15,
MONTH=jan,
YEAR=1984,
ABSTRACT="This RFC describes the Exterior Gateway Protocol (EGP) used to
connect Stub Gateways to an Autonomous System of core Gateways. This
document specifies the working protocol, and defines an ARPA official
protocol. All implementers of Gateways should carefully review this
document.",
URL="http://www.rfc-editor.org/rfc/rfc888.txt"
}

@TECHREPORT{rfc890,
AUTHOR="J. B. Postel",
TITLE="Exterior Gateway Protocol implementation schedule",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=890,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1984,
ABSTRACT="This memo is a policy statement on the implementation of the
Exterior Gateway Protocol (EGP) in the ARPA-Internet. This is an
official policy statement of ICCB and DARPA. After 1-Aug-84 there shall
be no dumb gateways in the Internet. Every gateway must be a member of
some autonomous system. Some gateway of each autonomous system must
exchange routing information with some gateway of the core autonomous
system using the Exterior Gateway Protocol.",
URL="http://www.rfc-editor.org/rfc/rfc890.txt"
}

@TECHREPORT{rfc893,
AUTHOR="S. Leffler and Mike Karels",
TITLE="Trailer encapsulations",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=893,
PAGES=6,
DAYS=15,
MONTH=apr,
YEAR=1984,
ABSTRACT={This RFC discusses the motivation for use of {"}trailer
encapsulations{"} on local-area networks and describes the implementation
of such an encapsulation on various media. This document is for
information only. This is NOT an official protocol for the ARPA-Internet
community.},
URL="http://www.rfc-editor.org/rfc/rfc893.txt"
}

@TECHREPORT{rfc894,
AUTHOR="C. Hornig",
TITLE="Standard for the transmission of {IP} datagrams over Ethernet networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=894,
PAGES=3,
DAYS=15,
MONTH=apr,
YEAR=1984,
ABSTRACT="This RFC specifies a standard method of encapsulating Internet
Protocol (IP) datagrams on an Ethernet. This RFC specifies a standard
protocol for the ARPA-Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc894.txt"
}

@TECHREPORT{rfc895,
AUTHOR="J. B. Postel",
TITLE="Standard for the transmission of {IP} datagrams over experimental Ethernet
networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=895,
PAGES=3,
DAYS=15,
MONTH=apr,
YEAR=1984,
ABSTRACT="This RFC specifies a standard method of encapsulating Internet
Protocol (IP) datagrams on an Experimental Ethernet. This RFC specifies
a standard protocol for the ARPA-Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc895.txt"
}

@TECHREPORT{rfc896,
AUTHOR="J. Nagle",
TITLE="Congestion control in {IP/TCP} internetworks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=896,
DAYS=15,
MONTH=jan,
YEAR=1984,
ABSTRACT="This memo discusses some aspects of congestion control in
IP/TCP Internetworks. It is intended to stimulate thought and further
discussion of this topic. While some specific suggestions are made for
improved congestion control implementation, this memo does not specify
any standards.",
URL="http://www.rfc-editor.org/rfc/rfc896.txt"
}

@TECHREPORT{rfc897,
AUTHOR="J. B. Postel",
TITLE="Domain name system implementation schedule",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=897,
PAGES=8,
DAYS=15,
MONTH=feb,
YEAR=1984,
ABSTRACT="This memo is a policy statement on the implementation of the
Domain Style Naming System in the ARPA-Internet. This memo is a partial
update of RFC 881. The intent of this memo is to detail the schedule for
the implementation of the Domain Style Naming System. The names of hosts
will be changed to Domain style names. Hosts will begin to use Domain
style names on 14-Mar-84, and the use of old style names will be
completely phased out before 2-May-84. This applies to both the ARPA
research hosts and the DDN operational hosts. This is an official policy
statement of the ICCB and the DARPA.",
URL="http://www.rfc-editor.org/rfc/rfc897.txt"
}

@TECHREPORT{rfc898,
AUTHOR="Robert Hinden and J. B. Postel and M. Muuss and J. F. Reynolds",
TITLE="Gateway special interest group meeting notes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=898,
PAGES=24,
DAYS=15,
MONTH=apr,
YEAR=1984,
ABSTRACT="This memo is a report on the Gateway Special Interest Group
Meeting that was held at ISI on 28 and 29 February 1984. Robert Hinden
of BBNCC chaired, and Jon Postel of ISI hosted the meeting.
Approximately 35 gateway designers and implementors attended. These
notes are based on the recollections of Jon Postel and Mike Muuss. Under
each topic area are Jon Postel's brief notes, and additional details
from Mike Muuss. This memo is a report on the meeting. No conclusions,
decisions, or policy statements are documented in this note.",
URL="http://www.rfc-editor.org/rfc/rfc898.txt"
}

@TECHREPORT{rfc899,
AUTHOR="J. B. Postel and A. Westine",
TITLE="Request For Comments summary notes: {800-899}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=899,
DAYS=15,
MONTH=may,
YEAR=1984,
ABSTRACT="A summary of the Request for Comments documents from RFC
800-898.",
URL="http://www.rfc-editor.org/rfc/rfc899.txt"
}

@TECHREPORT{rfc900,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Assigned Numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=900,
PAGES=43,
DAYS=15,
MONTH=jun,
YEAR=1984,
ABSTRACT="This RFC has been replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc900.txt"
}

@TECHREPORT{rfc901,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Official {ARPA-Internet} protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=901,
PAGES=28,
DAYS=15,
MONTH=jun,
YEAR=1984,
ABSTRACT="This RFC has been replaced by RFC 991.",
URL="http://www.rfc-editor.org/rfc/rfc901.txt"
}

@TECHREPORT{rfc902,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="{ARPA} Internet Protocol policy",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=902,
PAGES=5,
DAYS=15,
MONTH=jul,
YEAR=1984,
ABSTRACT="The purpose of this memo is to explain how protocol standards
are adopted for the ARPA-Internet and the DARPA research community.
There are three important aspects to be discussed: the process, the
authority, and the complex relationship between the DARPA community and
the DDN community. This memo is a policy statement on how protocols
become official standards for the ARPA-Internet and the DARPA research
community. This is an official policy statement of the ICCB and the
DARPA.",
URL="http://www.rfc-editor.org/rfc/rfc902.txt"
}

@TECHREPORT{rfc903,
AUTHOR="R. Finlayson and T. P. Mann and J. C. Mogul and M. M. Theimer",
TITLE="Reverse Address Resolution Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=903,
PAGES=4,
DAYS=15,
MONTH=jun,
YEAR=1984,
ABSTRACT="This RFC suggests a method for workstations to dynamically
find their protocol address (e.g., their Internet Address), when they
know only their hardware address (e.g., their attached physical network
address). This RFC specifies a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvement.",
URL="http://www.rfc-editor.org/rfc/rfc903.txt"
}

@TECHREPORT{rfc904,
AUTHOR="D. L. Mills",
TITLE="Exterior Gateway Protocol formal specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=904,
PAGES=30,
DAYS=15,
MONTH=apr,
YEAR=1984,
ABSTRACT="This is the specification of the Exterior Gateway Protocol
(EGP). This memo updates portions of RFC 888 and RFC 827. This RFC
specifies an official protocol of the DARPA community for use between
gateways of different autonomous systems in the ARPA-Internet.",
URL="http://www.rfc-editor.org/rfc/rfc904.txt"
}

@TECHREPORT{rfc905,
AUTHOR="David Hutchison",
TITLE="{ISO} Transport Protocol specification {ISO} {DP} 8073",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=905,
DAYS=15,
MONTH=apr,
YEAR=1984,
ABSTRACT="This is the current specification of the ISO Transport
Protocol. This document is the text of ISO/TC97/SC16/N1576 as corrected
by ISO/TC97/SC16/N1695. This is the specification currently being voted
on in ISO as a Draft International Standard (DIS). This document is
distributed as an RFC for your information only, it does not specify a
standard for the ARPA-Internet or DARPA research community. Our thanks
to Alex McKenzie of BBN for making this online version available. Please
note the size of this document, the file contains 258,729 characters.",
URL="http://www.rfc-editor.org/rfc/rfc905.txt"
}

@TECHREPORT{rfc906,
AUTHOR="R. Finlayson",
TITLE="Bootstrap loading using {TFTP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=906,
PAGES=4,
DAYS=15,
MONTH=jun,
YEAR=1984,
ABSTRACT="It is often convenient to be able to bootstrap a computer
system from a communications network. This RFC proposes the use of the
IP/TFTP protocol for bootstrap loading in this case.",
URL="http://www.rfc-editor.org/rfc/rfc906.txt"
}

@TECHREPORT{rfc907,
AUTHOR="Bolt Beranek and Newman Inc",
TITLE="Host Access Protocol specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=907,
PAGES=75,
DAYS=15,
MONTH=jul,
YEAR=1984,
ABSTRACT="This document specifies the Host Access Protocol (HAP).
Although HAP was originally designed as the network-access level
protocol for the DARPA/DCA sponsored Wideband Packet Satellite Network,
it is intended that it evolve into a standard interface SATNET and
TACNET (aka MATNET) as well as the Wideband Network. HAP is an
experimental protocol, and will undergo further revision as new
capabilities are added and/or different satellite networks are suported.
Implementations of HAP should be performed in coordination with
satellite network development and operations personnel.",
URL="http://www.rfc-editor.org/rfc/rfc907.txt"
}

@TECHREPORT{rfc908,
AUTHOR="D. Velten and Robert Hinden and J. Sax",
TITLE="Reliable Data Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=908,
PAGES=57,
DAYS=15,
MONTH=jul,
YEAR=1984,
ABSTRACT="The Reliable Data Protocol (RDP) is designed to provide a
reliable data transport service for packet-based applications. This RFC
specifies a proposed protocol for the ARPA-Internet and DARPA research
community, and requests discussion and suggestions for improvemts.",
URL="http://www.rfc-editor.org/rfc/rfc908.txt"
}

@TECHREPORT{rfc909,
AUTHOR="C. Welles and W. Milliken",
TITLE="Loader Debugger Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=909,
PAGES=128,
DAYS=15,
MONTH=jul,
YEAR=1984,
ABSTRACT="The Loader Debugger Protocol (LDP) is an application layer
protocol for loading, dumping, and debugging target machines from hosts
in a network environment. This RFC specifies a proposed protocol for the
ARPA-Internet and DARPA research community, and requests discussion and
suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc909.txt"
}

@TECHREPORT{rfc910,
AUTHOR="H. C. Forsdick",
TITLE="Multimedia mail meeting notes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=910,
PAGES=11,
DAYS=15,
MONTH=aug,
YEAR=1984,
ABSTRACT="This memo is a report on a meeting about the experimental
multimedia mail system (and in a sense a status report on that
experiment). The meeting was held at Bolt Beranek and Newman on 23-24
July 1984 to discuss recent progress by groups who are building
multimedia mail systems and to discuss a variety of issues related to
the further development of multimedia systems. Representatives were
present from BBN, ISI, SRI and Linkabit. Distribution of this memo is
unlimited.",
URL="http://www.rfc-editor.org/rfc/rfc910.txt"
}

@TECHREPORT{rfc911,
AUTHOR="P. Kirton",
TITLE="{EGP} Gateway under Berkeley {UNIX} {4.2}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=911,
PAGES=22,
DAYS=15,
MONTH=aug,
YEAR=1984,
ABSTRACT="This memo describes an implementation of the Exterior Gateway
Protocol (EGP) (in that sense it is a status report). The memo also
discusses some possible extentions and some design issues (in that sense
it is an invitation for further discussion).",
URL="http://www.rfc-editor.org/rfc/rfc911.txt"
}

@TECHREPORT{rfc912,
AUTHOR="M. St. Johns",
TITLE="Authentication service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=912,
PAGES=3,
DAYS=15,
MONTH=sep,
YEAR=1984,
ABSTRACT="This memo describes a proposed authentication protocol for
verifying the identity of a user of a TCP connection. Given a TCP port
number pair, it returns a character string which identifies the owner of
that connection on the server's system. Suggested uses include automatic
identification and verification of a user during an FTP session,
additional verification of a TAC dial up user, and access verification
for a generalized network file server.",
URL="http://www.rfc-editor.org/rfc/rfc912.txt"
}

@TECHREPORT{rfc913,
AUTHOR="M. Lottor",
TITLE="Simple File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=913,
PAGES=15,
DAYS=15,
MONTH=sep,
YEAR=1984,
ABSTRACT="This memo describes a proposed Simple File Transfer Protocol
(SFTP). It fills the need of people wanting a protocol that is more
useful than TFTP but easier to implement (and less powerful) than FTP.
SFTP supports user access control, file transfers, directory listing,
directory changing, file renaming, and deleting. Discussion of this
proposal is encouraged, and suggestions for improvements may be sent to
the author.",
URL="http://www.rfc-editor.org/rfc/rfc913.txt"
}

@TECHREPORT{rfc914,
AUTHOR="D. Farber and G. S. Delp and Thomas M. Conte",
TITLE="Thinwire protocol for connecting personal computers to the Internet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=914,
PAGES=22,
DAYS=15,
MONTH=sep,
YEAR=1984,
ABSTRACT="This document focuses discussion on the particular problems in
the ARPA-Internet of low speed network interconnection with personal
computers, and possible methods of solution. None of the proposed
solutions in this document are intended as standards for the
ARPA-Internet. Rather, it is hoped that a general consensus will emerge
as to the appropriate solution to the problems, leading eventually to
the adoption of standards.",
URL="http://www.rfc-editor.org/rfc/rfc914.txt"
}

@TECHREPORT{rfc915,
AUTHOR="M. A. Elvy and R. Nedved",
TITLE="Network mail path service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=915,
PAGES=11,
DAYS=15,
MONTH=dec,
YEAR=1984,
ABSTRACT="The network mail path service fills the current need of people
to determine mailbox addresses for hosts that are not part of the
ARPA-Internet but can be reached by one or more relay hosts that have
Unix to Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, BITNET mail,
etc. Anyone can use the service if they have TCP/TELENET to one of the
hosts with a mail path server. This RFC proposes a new service for the
ARPA-Internet community and requests discussion and suggestions for
improvements.",
URL="http://www.rfc-editor.org/rfc/rfc915.txt"
}

@TECHREPORT{rfc916,
AUTHOR="G. D. Finn",
TITLE="Reliable Asynchronous Transfer Protocol {(RATP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=916,
PAGES=54,
DAYS=15,
MONTH=oct,
YEAR=1984,
ABSTRACT="This paper proposes and specifies a protocol which allows two
programs to reliably communicate over a communication link. It ensures
that the data entering one end of the link if received arrives at the
other end intact and unaltered. The protocol, named RATP, is designed to
operate over a full duplex point-to-point connection. It contains some
features which tailor it to the RS-232 links now in common use. This RFC
suggests a proposed protocol for the ARPA-Internet community, and
requests discussion and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc916.txt"
}

@TECHREPORT{rfc917,
AUTHOR="J. C. Mogul",
TITLE="Internet subnets",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=917,
PAGES=22,
DAYS=15,
MONTH=oct,
YEAR=1984,
ABSTRACT="This memo discusses subnets and proposes procedures for the
use of subnets, including approaches to solving the problems that arise,
particularly that of routing. A subnet of an Internet network is a
logically visible sub-section of a single Internet network. For
administrative or technical reasons, many organizations have chosen to
divide one Internet network into several subnets, instead of acquiring a
set of Internet network numbers. This RFC suggests a proposed protocol
for the ARPA-Internet community, and requests discussion and suggestions
for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc917.txt"
}

@TECHREPORT{rfc918,
AUTHOR="J. F. Reynolds",
TITLE="Post Office Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=918,
PAGES=5,
DAYS=15,
MONTH=oct,
YEAR=1984,
ABSTRACT="Updated by RFC 937.",
URL="http://www.rfc-editor.org/rfc/rfc918.txt"
}

@TECHREPORT{rfc919,
AUTHOR="J. C. Mogul",
TITLE="Broadcasting Internet Datagrams",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=919,
PAGES=8,
DAYS=15,
MONTH=oct,
YEAR=1984,
ABSTRACT="This RFC proposes simple rules for broadcasting Internet
datagrams on local networks that support broadcast, for addressing
broadcasts, and for how gateways should handle them. This RFC suggests a
proposed protocol for the ARPA-Internet community, and requests
discussion and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc919.txt"
}

@TECHREPORT{rfc920,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="Domain requirements",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=920,
PAGES=14,
DAYS=15,
MONTH=oct,
YEAR=1984,
ABSTRACT="This memo states the requirements on establishing a Domain,
and introduces the limited set of top level domains. This memo is a
policy statement on the requirements of establishing a new domain in the
ARPA-Internet and the DARPA research community. This is an official
policy statement of the IAB and the DARPA.",
URL="http://www.rfc-editor.org/rfc/rfc920.txt"
}

@TECHREPORT{rfc921,
AUTHOR="J. B. Postel",
TITLE="Domain name system implementation schedule - revised",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=921,
PAGES=13,
DAYS=15,
MONTH=oct,
YEAR=1984,
ABSTRACT="This memo is a policy statement on the implementation of the
Domain Style Naming System in the ARPA-Internet. This memo is an update
of RFC 881, and RFC 897. This is an official policy statement of the IAB
and the DARPA. The intent of this memo is to detail the schedule for the
implementation for the Domain Style Naming System. The explanation of
how this system works is to be found in the references.",
URL="http://www.rfc-editor.org/rfc/rfc921.txt"
}

@TECHREPORT{rfc922,
AUTHOR="J. C. Mogul",
TITLE="Broadcasting Internet datagrams in the presence of subnets",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=922,
PAGES=12,
DAYS=15,
MONTH=oct,
YEAR=1984,
ABSTRACT="We propose simple rules for broadcasting Internet datagrams on
local networks that support broadcast, for addressing broadcasts, and
for how gateways should handle them. This RFC suggests a proposed
protocol for the ARPA-Internet community, and requests discussion and
suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc922.txt"
}

@TECHREPORT{rfc924,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Official {ARPA-Internet} protocols for connecting personal computers to the
Internet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=924,
PAGES=35,
DAYS=15,
MONTH=oct,
YEAR=1984,
ABSTRACT="This RFC has been replaced by RFC 991.",
URL="http://www.rfc-editor.org/rfc/rfc924.txt"
}

@TECHREPORT{rfc925,
AUTHOR="J. B. Postel",
TITLE="{Multi-LAN} address resolution",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=925,
PAGES=15,
DAYS=15,
MONTH=oct,
YEAR=1984,
ABSTRACT={The problem of treating a set of local area networks (LANs) as
one Internet network has generated some interest and concern. It is
inappropriate to give each LAN within a site a distinct ARPA-Internet
network number. It is desirable to hide the details of the
interconnections between the LANs within a site from people, gateways,
and hosts outside the site. The question arises on how to best do this,
and even how to do it at all. In RFC 917, Jeffery Mogul makes a case for
the use of {"}explicit subnets{"} in a multi-LAN environment. The explicit
subnet scheme is a call to recursively apply the mechanisms the
ARPA-Internet uses to manage networks to the problem of managing LANs
within one network. In this note I urge another approach: the use of
{"}transparent subnets{"} supported by a multi-LAN extension of the Address
Resolution Protocol. This RFC suggests a proposed protocol for the
ARPA-Internet community, and requests discussion and suggestions for
improvements.},
URL="http://www.rfc-editor.org/rfc/rfc925.txt"
}

@TECHREPORT{rfc926,
AUTHOR=" {{International Organization for Standardization}}",
TITLE="Protocol for providing the connectionless mode network services",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=926,
MONTH=dec,
YEAR=1984,
ABSTRACT="This note is the draft ISO protocol roughly similar to the DoD
Internet Protocol. This document has been prepared by retyping the text
of ISO DIS 8473 of May 1984, which is currently undergoing voting within
ISO as a Draft International Standard (DIS). This document is
distributed as an RFC for information only. It does not specify a
standard for the ARPA-Internet.",
URL="http://www.rfc-editor.org/rfc/rfc926.txt"
}

@TECHREPORT{rfc927,
AUTHOR="B. Anderson",
TITLE="{TACACS} user identification Telnet option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=927,
PAGES=4,
DAYS=15,
MONTH=dec,
YEAR=1984,
ABSTRACT="The following is the description of a Telnet option designed
to facilitate double login avoidance. It is intended primarily for TAC
connections to target hosts on behalf of TAC users, but it can be used
between any two consenting hosts. For example, all hosts at one site
(e.g., BBN) can use this option to avoid double login when TELNETing to
one another. This RFC suggests a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc927.txt"
}

@TECHREPORT{rfc928,
AUTHOR="M. A. Padlipsky",
TITLE="Introduction to proposed {DoD} standard {H-FP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=928,
PAGES=21,
DAYS=15,
MONTH=dec,
YEAR=1984,
ABSTRACT={The broad outline of the Host-Front End Protocol introduced
here and described in RFC 929 is the result of the deliberations of a
number of experienced H-FP designers, who sat as a committee of the DoD
Protocol Standards Technical Panel. It is the intent of the designers
that the protocol be subjected to multiple test implementations and
probable iteration before being agreed upon as any sort of {"}standard{"}.
Therefore, the first order of business is to declare that THIS IS A
PROPOSAL, NOT A FINAL STANDARD, and the second order of business is to
request that any readers of these documents who are able to do test
implementations (a) do so and (b) coordinate their efforts with the
author. This RFC suggests a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvements.},
URL="http://www.rfc-editor.org/rfc/rfc928.txt"
}

@TECHREPORT{rfc929,
AUTHOR="J. Lilienkamp and R. L. Mandell and M. A. Padlipsky",
TITLE="Proposed {Host-Front} End Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=929,
PAGES=56,
DAYS=15,
MONTH=dec,
YEAR=1984,
ABSTRACT="The Host-Front End Protocol introduced in RFC 928 is described
in detail in this memo. The first order of business is to declare that
THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of
business is to request that any readers of these documents who are able
to do test implementations (a) do so and (b) coordinate their efforts
with the author. This RFC suggests a proposed protocol for the
ARPA-Internet community, and requests discussion and suggestions for
improvements.",
URL="http://www.rfc-editor.org/rfc/rfc929.txt"
}

@TECHREPORT{rfc930,
AUTHOR="M. Solomon and E. Wimmers",
TITLE="Telnet terminal type option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=930,
PAGES=4,
DAYS=15,
MONTH=jan,
YEAR=1985,
ABSTRACT="This RFC specifies a standard for the ARPA-Internet community.
Hosts on the ARPA-Internet that exchange terminal type information
within the Telnet protocol are expected to adopt and implement this
standard. Distribution of this memo is unlimited. This standard
supersedes RFC 884. The only change is to specify that the TERMINAL-TYPE
IS sub-negotiation should be sent only in response to the TERMINAL-TYPE
SEND sub-negotiation.",
URL="http://www.rfc-editor.org/rfc/rfc930.txt"
}

@TECHREPORT{rfc931,
AUTHOR="M. St. Johns",
TITLE="Authentication server",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=931,
PAGES=5,
DAYS=15,
MONTH=jan,
YEAR=1985,
ABSTRACT="This RFC suggests a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvements.
This is the second draft of this proposal (superseding RFC 912) and
incorporates a more formal description of the syntax for the request and
response dialog, as well as a change to specify the type of user
identification returned.",
URL="http://www.rfc-editor.org/rfc/rfc931.txt"
}

@TECHREPORT{rfc932,
AUTHOR="D. D. Clark",
TITLE="Subnetwork addressing scheme",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=932,
PAGES=4,
DAYS=15,
MONTH=jan,
YEAR=1985,
ABSTRACT="This RFC proposes an alternative addressing scheme for subnets
which, in most cases, requires no modification to host software
whatsoever. The drawbacks of this scheme are that the total number of
subnets in any one network are limited, and that modification is
required to all gateways.",
URL="http://www.rfc-editor.org/rfc/rfc932.txt"
}

@TECHREPORT{rfc933,
AUTHOR="S. Silverman",
TITLE="Output marking Telnet option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=933,
PAGES=4,
DAYS=15,
MONTH=jan,
YEAR=1985,
ABSTRACT="This proposed option would allow a Server-Telnet to send a
banner to a User-Telnet so that this banner would be displayed on the
workstation screen independently of the application software running in
the Server-Telnet.",
URL="http://www.rfc-editor.org/rfc/rfc933.txt"
}

@TECHREPORT{rfc934,
AUTHOR="Marshall T. Rose and Einar Stefferud",
TITLE="Proposed standard for message encapsulation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=934,
PAGES=10,
DAYS=15,
MONTH=jan,
YEAR=1985,
ABSTRACT={This memo concerns itself with message forwarding. Forwarding
can be thought of as encapsulating one or more messages inside another.
Although this is useful for transfer of past correspondence to new
recipients, without a decapsulation process (which this memo terms
{"}bursting{"}), the forwarded messages are of little use to the recipients
because they can not be distributed, forwarded, replied-to, or otherwise
processed as separate individual messages. In order to burst a message
it is necessary to know how the component messages were encapsulated in
the draft. At present there is no unambiguous standard for interest
group digests. This RFC proposes a proposed protocol for the
ARPA-Internet community, and requests discussion and suggestions for
improvements.},
URL="http://www.rfc-editor.org/rfc/rfc934.txt"
}

@TECHREPORT{rfc935,
AUTHOR="J. T. Robinson",
TITLE="Reliable link layer protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=935,
PAGES=13,
DAYS=15,
MONTH=jan,
YEAR=1985,
ABSTRACT="This RFC discusses protocols proposed recently in RFCs 914 and
916, and suggests a proposed protocol that could meet the same needs
addressed in those memos. The stated need is reliable communication
between two programs over a full-duplex, point-to-point communication
link, and in particular the RFCs address the need for such communication
over an asynchronous link at relatively low speeds. The suggested
protocol uses the methods of existing national and international data
link layer standards. This RFC suggests a proposed protocol for the
ARPA-Internet community, and requests discussion and suggestions for
improvements.",
URL="http://www.rfc-editor.org/rfc/rfc935.txt"
}

@TECHREPORT{rfc936,
AUTHOR="Mike Karels",
TITLE="Another Internet subnet addressing scheme",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=936,
PAGES=4,
DAYS=15,
MONTH=feb,
YEAR=1985,
ABSTRACT="There have been several proposals for schemes to allow the use
of a single Internet network number to refer to a collection of physical
networks under common administration which are reachable from the rest
of the Internet by a common route. Such schemes allow a simplified view
of an otherwise complicated topology from hosts and gateways outside of
this collection. They allow the complexity of the number and type of
these networks, and routing to them, to be localized. Additions and
changes in configuration thus cause no detectable change, and no
interruption of service, due to slow propagation of routing and other
information outside of the local environment. These schemes also
simplify the administration of the network, as changes do not require
allocation of new network numbers for each new cable installed. This
proposal discusses an alternative scheme, one that has been in use at
the University of California, Berkeley since April 1984. This RFC
suggests a proposed protocol for the ARPA-Internet community, and
requests discussion and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc936.txt"
}

@TECHREPORT{rfc937,
AUTHOR="M. Butler and J. B. Postel and D. Chase and J. Goldberger and J. F.
Reynolds",
TITLE="Post Office Protocol: Version 2",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=937,
PAGES=24,
DAYS=15,
MONTH=feb,
YEAR=1985,
ABSTRACT="This RFC suggests a simple method for workstations to
dynamically access mail from a mailbox server. This RFC specifies a
proposed protocol for the ARPA-Internet community, and requests
discussion and suggestions for improvement. This memo is a revision of
RFC 918.",
URL="http://www.rfc-editor.org/rfc/rfc937.txt"
}

@TECHREPORT{rfc938,
AUTHOR="T. Miller",
TITLE="Internet Reliable Transaction Protocol functional and interface
specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=938,
PAGES=16,
DAYS=15,
MONTH=feb,
YEAR=1985,
ABSTRACT="This RFC is being distributed to members of the DARPA research
community in order to solicit their reactions to the proposals contained
in it. While the issues discussed may not be directly relevant to the
research problems of the DARPA community, they may be interesting to a
number of researchers and implementors. This RFC suggests a proposed
protocol for the ARPA-Internet community, and requests discussion and
suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc938.txt"
}

@TECHREPORT{rfc939,
AUTHOR=" {National Research Council}",
TITLE="Executive summary of the {NRC} report on transport protocols for Department
of Defense data networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=939,
PAGES=20,
DAYS=15,
MONTH=feb,
YEAR=1985,
ABSTRACT={This RFC reproduces the material from the {"}front pages{"} of the
National Research Council report resulting from a study of the DOD
Internet Protocol (IP) and Transmission Control Protocol (TCP) in
comparison with the ISO Internet Protocol (ISO-IP) and Transport
Protocol level 4 (TP-4). The point of this RFC is to make the text of
the Executive Summary widely available in a timely way. The order of
presentation has been altered, and the pagination changed.},
URL="http://www.rfc-editor.org/rfc/rfc939.txt"
}

@TECHREPORT{rfc940,
AUTHOR="Gateway Algorithms and  ",
TITLE="Toward an Internet standard scheme for subnetting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=940,
PAGES=3,
DAYS=15,
MONTH=apr,
YEAR=1985,
ABSTRACT="Several sites now contain a complex of local links connected
to the Internet via a gateway. The details of the internal connectivity
are of little interest to the rest of the Internet. One way of
organizing these local complexes of links is to use the same strategy as
the Internet uses to organize networks, that is, to declare each link to
be an entity (like a network) and to interconnect the links with devices
that perform routing functions (like gateways). This general scheme is
called subnetting, the individual links are called subnets, and the
connecting devices are called subgateways (or bridges, or gateways).
This RFC discusses standardizing the protocol used in subnetted
environments in the ARPA-Internet. Distribution of this memo is
unlimited. The author of this RFC is the Gateway Algorithms and Data
Structures (GADS) Task Force, chaired by David L. Mills.",
URL="http://www.rfc-editor.org/rfc/rfc940.txt"
}

@TECHREPORT{rfc941,
AUTHOR=" {{International Organization for Standardization}}",
TITLE="Addendum to the network service definition covering network layer
addressing",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=941,
MONTH=apr,
YEAR=1985,
ABSTRACT="This Addendum to the Network Service Definition Standard, ISO
8348, defines the abstract syntax and semantics of the Network Address
(Network Service Access Point Address). The Network Address defined in
this Addendum is the address that appears in the primitives of the
connection-mode Network Service as the calling address, called address,
and responding address parameters, and in the primitives of the
connectionless-mode Network Service as the source address and
destination address parameters. This document is distributed as an RFC
for information only. It does not specify a standard for the
ARPA-Internet.",
URL="http://www.rfc-editor.org/rfc/rfc941.txt"
}

@TECHREPORT{rfc942,
AUTHOR=" {National Research Council}",
TITLE="Transport protocols for Department of Defense data networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=942,
PAGES=68,
DAYS=15,
MONTH=feb,
YEAR=1985,
ABSTRACT="This RFC reproduces the National Research Council report
resulting from a study of the DoD Internet Protocol (IP) and
Transmission Control Protocol (TCP) in comparison with the ISO Internet
Protocol (ISO-IP) and Transport Protocol level 4 (TP-4).",
URL="http://www.rfc-editor.org/rfc/rfc942.txt"
}

@TECHREPORT{rfc943,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=943,
PAGES=50,
DAYS=15,
MONTH=apr,
YEAR=1985,
ABSTRACT="This RFC has been replaced by RFCs 997 and 990.",
URL="http://www.rfc-editor.org/rfc/rfc943.txt"
}

@TECHREPORT{rfc944,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Official {ARPA-Internet} protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=944,
PAGES=40,
DAYS=15,
MONTH=apr,
YEAR=1985,
ABSTRACT="This RFC has been replaced by RFC 991.",
URL="http://www.rfc-editor.org/rfc/rfc944.txt"
}

@TECHREPORT{rfc945,
AUTHOR="J. B. Postel",
TITLE="{DoD} statement on the {NRC} report",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=945,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1985,
ABSTRACT="In May 1983, the National Research Council (NRC) was asked
jointly by the DoD and NBS to study the issues and recommend a course of
action. The final report of the NRC committee was published in February
1985 (see RFC-942). The enclosed letter is from Donald C. Latham
(ASDC3I) to DCA transmitting the NRC report and requesting specific
actions relative to the recommendations of the report. This RFC
reproduces a letter from the Assistant Secretary of Defense for Command,
Control, Communications, and Intelligence (ASDC3I) to the Director of
the Defense Communications Agency (DCA). This letter is distributed for
information only.",
URL="http://www.rfc-editor.org/rfc/rfc945.txt"
}

@TECHREPORT{rfc946,
AUTHOR="R. Nedved",
TITLE="Telnet terminal location number option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=946,
PAGES=4,
DAYS=15,
MONTH=may,
YEAR=1985,
ABSTRACT="Many systems provide a mechanism for finding out where a user
is logged in from usually including information about telephone
extension and office occupants names. The information is useful for
physically locating people and/or calling them on the phone. In 1982 CMU
designed and implemented a terminal location database and modified
existing network software to handle a 64-bit number called the Terminal
Location Number (or TTYLOC). It now seems appropriate to incorporate
this mechanism into the TCP-based network protocol family. The mechanism
is not viewed as a replacement for the Terminal Location Telnet Option
(SEND-LOCATION) but as a shorthand mechansim for communicating terminal
location information between hosts in a localized community. This RFC
proposes a new option for Telnet for the ARPA-Internet community, and
requests discussion and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc946.txt"
}

@TECHREPORT{rfc947,
AUTHOR="K. Lebowitz and D. Mankins",
TITLE="Multi-network broadcasting within the Internet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=947,
PAGES=5,
DAYS=15,
MONTH=jun,
YEAR=1985,
ABSTRACT="This RFC describes the extension of a network's broadcast
domain to include more than one physical network through the use of a
broadcast packet repeater.",
URL="http://www.rfc-editor.org/rfc/rfc947.txt"
}

@TECHREPORT{rfc948,
AUTHOR="I. Winston",
TITLE="Two methods for the transmission of {IP} datagrams over {IEEE} {802.3}
networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=948,
PAGES=5,
DAYS=15,
MONTH=jun,
YEAR=1985,
ABSTRACT="This memo describes two methods of encapsulating Internet
Protocol (IP) datagrams on an IEEE 802.3 network.",
URL="http://www.rfc-editor.org/rfc/rfc948.txt"
}

@TECHREPORT{rfc949,
AUTHOR="M. A. Padlipsky",
TITLE="{FTP} unique-named store command",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=949,
PAGES=2,
DAYS=15,
MONTH=jul,
YEAR=1985,
ABSTRACT="There are various contexts in which it would be desirable to
have an FTP command that had the effect of the present STOR but rather
than requiring the sender to specify a file name istead caused the
resultant file to have a unique name relative to the current directory.
This RFC proposes an extension to the File Transfer Protocol for the
ARPA-Internet community, and requests discussion and suggestions for
improvements.",
URL="http://www.rfc-editor.org/rfc/rfc949.txt"
}

@TECHREPORT{rfc950,
AUTHOR="J. C. Mogul and J. B. Postel",
TITLE="Internet Standard Subnetting Procedure",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=950,
PAGES=18,
DAYS=15,
MONTH=aug,
YEAR=1985,
ABSTRACT={This memo discusses the utility of {"}subnets{"} of Internet
networks, which are logically visible sub-sections of a single Internet
network. For administrative or technical reasons, many organizations
have chosen to divide one Internet network into several subnets, instead
of acquiring a set of Internet network numbers. This memo specifies
procedures for the use of subnets. These procedures are for hosts (e.g.,
workstations). The procedures used in and between subnet gateways are
not fully described. Important motivation and background information for
a subnetting standard is provided in RFC-940. This RFC specifies a
protocol for the ARPA-Internet community. If subnetting is implemented
it is strongly recommended that these procedures be followed.},
URL="http://www.rfc-editor.org/rfc/rfc950.txt"
}

@TECHREPORT{rfc951,
AUTHOR="W. J. Croft and J. Gilmore",
TITLE="Bootstrap Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=951,
PAGES=12,
DAYS=15,
MONTH=sep,
YEAR=1985,
ABSTRACT="This RFC describes an IP/UDP bootstrap protocol (BOOTP) which
allows a diskless client machine to discover its own IP address, the
address of a server host, and the name of a file to be loaded into
memory and executed. The bootstrap operation can be thought of as
consisting of TWO PHASES. This RFC describes the first phase, which
could be labeled `address determination and bootfile selection'. After
this address and filename information is obtained, control passes to the
second phase of the bootstrap where a file transfer occurs. The file
transfer will typically use the TFTP protocol, since it is intended that
both phases reside in PROM on the client. However BOOTP could also work
with other protocols such as SFTP or FTP. This RFC suggests a proposed
protocol for the ARPA-Internet community, and requests discussion and
suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc951.txt"
}

@TECHREPORT{rfc952,
AUTHOR="K. Harrenstien and Mary K. Stahl and Elizabeth J. Feinler",
TITLE="{DoD} Internet host table specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=952,
PAGES=6,
DAYS=15,
MONTH=oct,
YEAR=1985,
ABSTRACT="This RFC is the official specification of the format of the
Internet Host Table. This edition of the specification includes minor
revisions to RFC 810 which brings it up to date. Obsoletes RFCs 810,
608.",
URL="http://www.rfc-editor.org/rfc/rfc952.txt"
}

@TECHREPORT{rfc953,
AUTHOR="K. Harrenstien and Mary K. Stahl and Elizabeth J. Feinler",
TITLE="Hostname Server",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=953,
PAGES=5,
DAYS=15,
MONTH=oct,
YEAR=1985,
ABSTRACT="This RFC is the official specification of the Hostname Server
Protocol. This edition of the specification includes minor revisions to
RFC 811 which brings it up to date. Obsoletes RFC 811.",
URL="http://www.rfc-editor.org/rfc/rfc953.txt"
}

@TECHREPORT{rfc954,
AUTHOR="K. Harrenstien and Mary K. Stahl and Elizabeth J. Feinler",
TITLE="{NICNAME/WHOIS}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=954,
PAGES=4,
DAYS=15,
MONTH=oct,
YEAR=1985,
ABSTRACT="This RFC is the official specification of the NICNAME/WHOIS
protocol. This memo describes the protocol and the service. This is an
update of RFC 812. Obsoletes RFC 812.",
URL="http://www.rfc-editor.org/rfc/rfc954.txt"
}

@TECHREPORT{rfc955,
AUTHOR="R. Braden",
TITLE="Towards a transport service for transaction processing applications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=955,
PAGES=10,
DAYS=15,
MONTH=sep,
YEAR=1985,
ABSTRACT={The DoD Internet Protocol Suite includes two alternative
transport service protocols, TCP and UDP, which provide virtual circuit
and datagram service, respectively. These two protocols represent points
in the space of possible transport service attributes which are quite
{"}far apart{"}. We want to examine an important class of applications,
those which perform what is often called {"}transaction processing{"}. We
will see that the communication needs for these applications fall into
the gap {"}between{"} TCP and UDP -- neither protocol is very appropriate.},
URL="http://www.rfc-editor.org/rfc/rfc955.txt"
}

@TECHREPORT{rfc956,
AUTHOR="D. L. Mills",
TITLE="Algorithms for synchronizing network clocks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=956,
PAGES=26,
DAYS=15,
MONTH=sep,
YEAR=1985,
ABSTRACT="This RFC discussed clock synchronization algorithms for the
ARPA-Internet community, and requests discussion and suggestions for
improvements. The recent interest within the Internet community in
determining accurate time from a set of mutually suspicious network
clocks has been prompted by several occasions in which errors were found
in usually reliable, accurate clock servers after thunderstorms which
disrupted their power supply. To these sources of error should be added
those due to malfunctioning hardware, defective software and operator
mistakes, as well as random errors in the mechanism used to set and
synchronize clocks. This report suggests a stochastic model and
algorithms for computing a good estimator from time-offset samples
measured between clocks connected via network links. Included in this
report are descriptions of certain experiments which give an indication
of the effectiveness of the algorithms.",
URL="http://www.rfc-editor.org/rfc/rfc956.txt"
}

@TECHREPORT{rfc957,
AUTHOR="D. L. Mills",
TITLE="Experiments in network clock synchronization",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=957,
PAGES=27,
DAYS=15,
MONTH=sep,
YEAR=1985,
ABSTRACT="This RFC discusses some experiments in clock synchronization
in the ARPA-Internet community, and requests discussion and suggestions
for improvements. One of the services frequently neglected in computer
network design is a high-quality, time-of-day clock capable of
generating accurate timestamps with small errors compared to one-way
network delays. Such a service would be useful for tracing the progress
of complex transactions, synchronizing cached data bases, monitoring
network performance and isolating problems. In this memo, one such clock
service design will be described and its performance assessed. This
design has been incorporated as an integral part of the network routing
and control protocols of the Distributed Computer Network (DCnet)
architecture.",
URL="http://www.rfc-editor.org/rfc/rfc957.txt"
}

@TECHREPORT{rfc958,
AUTHOR="D. L. Mills",
TITLE="Network Time Protocol {(NTP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=958,
PAGES=14,
DAYS=15,
MONTH=sep,
YEAR=1985,
ABSTRACT="This document describes the Network Time Protocol (NTP), a
protocol for synchronizing a set of network clocks using a set of
distributed clients and servers. NTP is built on the User Datagram
Protocol (UDP), which provides a connectionless transport mechanism. It
evolved from the Time Protocol and the ICMP Timestamp message and is a
suitable replacement for both. This RFC suggests a proposed protocol for
the ARPA-Internet community, and requests discussion and suggestions for
improvements.",
URL="http://www.rfc-editor.org/rfc/rfc958.txt"
}

@TECHREPORT{rfc959,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="File Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=959,
PAGES=69,
DAYS=15,
MONTH=oct,
YEAR=1985,
ABSTRACT="This memo is the official specification of the File Transfer
Protocol (FTP) for the DARPA-Internet community. The primary intent is
to clarify and correct the documentation of the FTP specification, not
to change the protocol. The following new optional commands are included
in this edition of the specification: Change to Parent Directory (CDUP),
Structure Mount (SMNT), Store Unique (STOU), Remove Directory (RMD),
Make Directory (MKD), Print Directory (PWD), and System (SYST). Note
that this specification is compatible with the previous edition.",
URL="http://www.rfc-editor.org/rfc/rfc959.txt"
}

@TECHREPORT{rfc962,
AUTHOR="M. A. Padlipsky",
TITLE="{TCP-4} prime",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=962,
PAGES=2,
DAYS=15,
MONTH=nov,
YEAR=1985,
ABSTRACT="This memo is in response to Bob Braden's call for a
transaction oriented protocol (RFC-955), and continues the discussion of
a possible transaction oriented transport protocol. This memo does not
propose a standard.",
URL="http://www.rfc-editor.org/rfc/rfc962.txt"
}

@TECHREPORT{rfc963,
AUTHOR="Deepinder Sidhu",
TITLE="Some problems with the specification of the Military Standard Internet
Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=963,
PAGES=19,
DAYS=15,
MONTH=nov,
YEAR=1985,
ABSTRACT="The purpose of this RFC is to provide helpful information on
the Military Standard Internet Protocol (MIL-STD-1777) so that one can
obtain a reliable implementation of this protocol. This paper points out
several problems in this specification. This note also proposes
solutions to these problems.",
URL="http://www.rfc-editor.org/rfc/rfc963.txt"
}

@TECHREPORT{rfc964,
AUTHOR="Deepinder Sidhu",
TITLE="Some problems with the specification of the Military Standard Transmission
Control Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=964,
PAGES=10,
DAYS=15,
MONTH=nov,
YEAR=1985,
ABSTRACT="The purpose of this RFC is to provide helpful information on
the Military Standard Transmission Control Protocol (MIL-STD-1778) so
that one can obtain a reliable implementation of this protocol standard.
This note points out three errors with this specification. This note
also proposes solutions to these problems.",
URL="http://www.rfc-editor.org/rfc/rfc964.txt"
}

@TECHREPORT{rfc965,
AUTHOR="L. Aguilar",
TITLE="Format for a graphical communication protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=965,
PAGES=51,
DAYS=15,
MONTH=dec,
YEAR=1985,
ABSTRACT="This RFC describes the requirements for a graphical format on
which to base a graphical on-line communication protocol, and proposes
an Interactive Graphical Communication Format using the GKSM session
metafile. We hope this contribution will encourage the discussion of
multimedia data exchange and the proposal of solutions.",
URL="http://www.rfc-editor.org/rfc/rfc965.txt"
}

@TECHREPORT{rfc966,
AUTHOR="S. E. Deering and D. R. Cheriton",
TITLE="Host groups: A multicast extension to the Internet Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=966,
PAGES=27,
DAYS=15,
MONTH=dec,
YEAR=1985,
ABSTRACT="This RFC defines a model of service for Internet multicasting
and proposes an extension to the Internet Protocol (IP) to support such
a multicast service. Discussion and suggestions for improvements are
requested.",
URL="http://www.rfc-editor.org/rfc/rfc966.txt"
}

@TECHREPORT{rfc967,
AUTHOR="M. A. Padlipsky",
TITLE="All victims together",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=967,
PAGES=2,
DAYS=15,
MONTH=dec,
YEAR=1985,
ABSTRACT="This RFC proposes a new set of RFCs on how the networking code
is integrated with various operating systems. It appears that this topic
has not received enough exposure in the literature. Comments and
suggestions are encouraged.",
URL="http://www.rfc-editor.org/rfc/rfc967.txt"
}

@TECHREPORT{rfc968,
AUTHOR="V. G. Cerf",
TITLE="Twas the night before start-up",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=968,
PAGES=2,
DAYS=15,
MONTH=dec,
YEAR=1985,
ABSTRACT="This memo discusses problems that arise and debugging
techniques used in bringing a new network into operation.",
URL="http://www.rfc-editor.org/rfc/rfc968.txt"
}

@TECHREPORT{rfc969,
AUTHOR="D. D. Clark and Mark L. Lambert and L. Zhang",
TITLE="{NETBLT:} A bulk data transfer protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=969,
PAGES=15,
DAYS=15,
MONTH=dec,
YEAR=1985,
ABSTRACT="This RFC has been replaced by RFC 998. This is a preliminary
discussion of the Network Block Transfer (NETBLT) protocol. NETBLT is
intended for the rapid transfer of a large quantity of data between
computers. It provides a transfer that is reliable and flow controlled,
and is structured to provide maximum throughput over a wide variety of
networks. This description is published for discussion and comment, and
does not constitute a standard. As the proposal may change,
implementation of this document is not advised.",
URL="http://www.rfc-editor.org/rfc/rfc969.txt"
}

@TECHREPORT{rfc970,
AUTHOR="J. Nagle",
TITLE="On packet switches with infinite storage",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=970,
PAGES=9,
DAYS=15,
MONTH=dec,
YEAR=1985,
ABSTRACT="The purpose of this RFC is to focus discussion on a particular
problem in the ARPA-Internet and possible methods of solution. Most
prior work on congestion in datagram systems focuses on buffer
management. In this memo, the case of a packet switch with infinite
storage is considered. Such a packet switch can never run out of
buffers. It can, however, still become congested. The meaning of
congestion in an infinite-storage system is explored. An unexpected
result is found that shows a datagram network with infinite storage,
first-in-first-out queuing, at least two packet switches, and a finite
packet lifetime will, under overload, drop all packets. By attacking the
problem of congestion for the infinite-storage case, new solutions
applicable to switches with finite storage may be found. No proposed
solutions this document are intended as standards for the ARPA-Internet
at this time.",
URL="http://www.rfc-editor.org/rfc/rfc970.txt"
}

@TECHREPORT{rfc971,
AUTHOR="A. L. DeSchon",
TITLE="Survey of data representation standards",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=971,
PAGES=9,
DAYS=15,
MONTH=jan,
YEAR=1986,
ABSTRACT="This RFC is a comparison of several data representation
standards that are currently in use. The standards discussed are the
CCITT X.409 recommendation, the NBS Computer Based Message System (CBMS)
standard, DARPA Multimedia Mail system, the Courier remote procedure
call protocol, and the SUN Remote Procedure Call package. No proposals
in this document are intended as standards for the ARPA-Internet at this
time. Rather, it is hoped that a general consensus will emerge as to the
appropriate approach to a data representation standard, leading
eventually to the adoption of an ARPA-Internet standard.",
URL="http://www.rfc-editor.org/rfc/rfc971.txt"
}

@TECHREPORT{rfc972,
AUTHOR="F. J. Wancho",
TITLE="Password Generator Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=972,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1986,
ABSTRACT={This RFC specifies a standard for the ARPA-Internet community.
The Password Generator Service (PWDGEN) provides a set of six randomly
generated eight-character {"}words{"} with a reasonable level of
pronounceability, using a multi-level algorithm. Hosts on the
ARPA-Internet that choose to implement a password generator service are
expected to adopt and implement this standard.},
URL="http://www.rfc-editor.org/rfc/rfc972.txt"
}

@TECHREPORT{rfc973,
AUTHOR="P. V. Mockapetris",
TITLE="Domain system changes and observations",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=973,
PAGES=10,
DAYS=15,
MONTH=jan,
YEAR=1986,
ABSTRACT="This RFC documents updates to Domain Name System
specifications RFC-882 and RFC-883, suggests some operational
guidelines, and discusses some experiences and problem areas in the
present system.",
URL="http://www.rfc-editor.org/rfc/rfc973.txt"
}

@TECHREPORT{rfc974,
AUTHOR="C. Partridge",
TITLE="Mail routing and the domain system",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=974,
PAGES=7,
DAYS=15,
MONTH=jan,
YEAR=1986,
ABSTRACT="This RFC presents a description of how mail systems on the
Internet are expected to route messages based on information from the
domain system. This involves a discussion of how mailers interpret MX
RRs, which are used for message routing.",
URL="http://www.rfc-editor.org/rfc/rfc974.txt"
}

@TECHREPORT{rfc975,
AUTHOR="D. L. Mills",
TITLE="Autonomous confederations",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=975,
PAGES=10,
DAYS=15,
MONTH=feb,
YEAR=1986,
ABSTRACT="This RFC proposes enhancements to the Exterior Gateway
Protocol (EGP) to support a simple, multiple-level routing capability
while preserving the robustness features of the current EGP model. The
enhancements generalize the concept of core system to include multiple
communities of autonomous systems, called autonomous confederations.
Discussion and suggestions for improvement are requested.",
URL="http://www.rfc-editor.org/rfc/rfc975.txt"
}

@TECHREPORT{rfc976,
AUTHOR="M. R. Horton",
TITLE="{UUCP} mail interchange format standard",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=976,
PAGES=12,
DAYS=15,
MONTH=feb,
YEAR=1986,
ABSTRACT="This document defines the standard format for the transmission
of mail messages between computers in the UUCP Project. It does not
however, address the format for storage of messages on one machine, nor
the lower level transport mechanisms used to get the date from one
machine to the next. It represents a standard for conformance by hosts
in the UUCP zone.",
URL="http://www.rfc-editor.org/rfc/rfc976.txt"
}

@TECHREPORT{rfc977,
AUTHOR="B. Kantor and P. Lapsley",
TITLE="Network News Transfer Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=977,
PAGES=27,
DAYS=15,
MONTH=feb,
YEAR=1986,
ABSTRACT="NNTP specifies a protocol for the distribution, inquiry,
retrieval, and posting of news articles using a reliable stream-based
transmission of news among the ARPA-Internet community. NNTP is designed
so that news articles are stored in a central database allowing a
subscriber to select only those items he wishes to read. Indexing,
cross-referencing, and expiration of aged messages are also provided.
This RFC suggests a proposed protocol for the ARPA-Internet community,
and requests discussion and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc977.txt"
}

@TECHREPORT{rfc978,
AUTHOR="J. F. Reynolds and R. Gillman and W. A. Brackenridge and A. Witkowski and
J. B. Postel",
TITLE="Voice File Interchange Protocol {(VFIP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=978,
PAGES=5,
DAYS=15,
MONTH=feb,
YEAR=1986,
ABSTRACT="The purpose of the Voice File Interchange Protocol (VFIP) is
to permit the interchange of various types of speech files between
different systems in the ARPA-Internet community. Suggestions for
improvement are encouraged.",
URL="http://www.rfc-editor.org/rfc/rfc978.txt"
}

@TECHREPORT{rfc979,
AUTHOR="Andrew G. Malis",
TITLE="{PSN} {End-to-End} functional specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=979,
PAGES=15,
DAYS=15,
MONTH=mar,
YEAR=1986,
ABSTRACT={This memo is an updated version of BBN Report 5775,
{"}End-to-End Functional Specification{"}. It describes important changes
to
the functionality of the interface between a host and the PSN (Packet
Switch Node), and should be carefully reviewed by anyone involved in
supporting a host on either the ARPANET or MILNET. The new End-to-End
Protocol (EE) is being developed in order to correct a number of
deficiencies in the old End-to-End Protocol, to improve its performance
and overall throughput, and to better equip the Packet Switch Node (also
known as the IMP) to support its current and anticipated host
population.},
URL="http://www.rfc-editor.org/rfc/rfc979.txt"
}

@TECHREPORT{rfc980,
AUTHOR="Ole J. Jacobsen and J. B. Postel",
TITLE="Protocol document order information",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=980,
PAGES=12,
DAYS=15,
MONTH=mar,
YEAR=1986,
ABSTRACT="This RFC indicates how to obtain various protocol documents
used in the DARPA research community. Included is an overview of the new
1985 DDN Protocol Handbook and available sources for obtaining related
documents (such as DOD, ISO, and CCITT).",
URL="http://www.rfc-editor.org/rfc/rfc980.txt"
}

@TECHREPORT{rfc981,
AUTHOR="D. L. Mills",
TITLE="Experimental multiple-path routing algorithm",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=981,
PAGES=22,
DAYS=15,
MONTH=mar,
YEAR=1986,
ABSTRACT="This document introduces wiretap algorithms, a class of
experimental, multiple routing algorithms that compute quasi-optimum
routes for stations sharing a packet-radio broadcast channel. The
primary route (a minimum-distance path), and additional paths ordered by
distance, which serve as alternate routes should the primary route fail,
are computed. This prototype is presented as an example of a class of
routing algorithms and data-base management techniques that may find
wider application in the Internet community. Discussions and suggestions
for improvements are welcomed.",
URL="http://www.rfc-editor.org/rfc/rfc981.txt"
}

@TECHREPORT{rfc982,
AUTHOR="H. Braun",
TITLE="Guidelines for the specification of the structure of the Domain Specific
Part {(DSP)} of the {ISO} standard {NSAP} address",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=982,
PAGES=11,
DAYS=15,
MONTH=apr,
YEAR=1986,
ABSTRACT={This RFC is a draft working document of the ANSI {"}Guidelines
for the Specification of the Structure of the Domain Specific Part (DSP)
of the ISO Standard NSAP Address{"}. It provides guidance to private
address administration authorities on preferred formats and semantics
for the Domain Specific Part (DSP) of an NSAP address. This RFC
specifies the way in which the DSP may be constructed so as to
facilitate efficient address assignment. This RFC is for informational
purposes only and its distribution is unlimited and does not specify a
standard of the ARPA-Internet.},
URL="http://www.rfc-editor.org/rfc/rfc982.txt"
}

@TECHREPORT{rfc983,
AUTHOR="D. E. Cass and Marshall T. Rose",
TITLE="{ISO} transport arrives on top of the {TCP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=983,
PAGES=27,
DAYS=15,
MONTH=apr,
YEAR=1986,
ABSTRACT="This memo describes a proposed protocol standard for the
ARPA-Internet community. The CCITT and the ISO have defined various
session, presentation, and application recommendations which have been
adopted by the international community and numerous vendors. To the
largest extent possible, it is desirable to offer these higher level
services directly to the ARPA-Internet, without disrupting existing
facilities. This permits users to develop expertise with ISO and CCITT
applications which previously were not available in the ARPA-Internet.
The intention is that hosts within the ARPA-Internet that choose to
implement ISO TSAP services on top of the TCP be expected to adopt and
implement this standard. Suggestions for improvement are encouraged.",
URL="http://www.rfc-editor.org/rfc/rfc983.txt"
}

@TECHREPORT{rfc984,
AUTHOR="David D. Clark (M. I. T) and Mark L. Lambert (M. I. T)",
TITLE="{PCMAIL:} A distributed mail system for personal computers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=984,
PAGES=31,
DAYS=15,
MONTH=may,
YEAR=1986,
ABSTRACT={This document is a preliminary discussion of the design of a
personal-computer-based distributed mail system. Pcmail is a distributed
mail system that provides mail service to an arbitrary number of users,
each of which owns one or more personal computers (PCs). The system is
divided into two halves. The first consists of a single entity called
the {"}repository{"}. The repository is a storage center for incoming mail.
Mail for a Pcmail user can arrive externally from the Internet or
internally from other repository users. The repository also maintains a
stable copy of each user's mail state. The repository is therefore
typically a computer with a large amount of disk storage. It is
published for discussion and comment, and does not constitute a
standard. As the proposal may change, implementation of this document is
not advised.},
URL="http://www.rfc-editor.org/rfc/rfc984.txt"
}

@TECHREPORT{rfc985,
AUTHOR=" {National Science Foundation} and  ",
TITLE="Requirements for Internet gateways - draft",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=985,
PAGES=23,
DAYS=15,
MONTH=may,
YEAR=1986,
ABSTRACT="This RFC summarizes the requirements for gateways to be used
on networks supporting the DARPA Internet protocols. While it applies
specifically to the National Science Foundation research programs, the
requirements are stated in a general context and are believed applicable
throughout the Internet community. The purpose of this document is to
present guidance for vendors offering products that might be used or
adapted for use in an Internet application. It enumerates the protocols
required and gives references to RFCs and other documents describing the
current specification. Suggestions and comments on this document are
welcomed and can be sent to Dave Mills (Mills(at)D.ISI.EDU) or Dave Farber
(Farber(at)HUEY.UDEL.EDU).",
URL="http://www.rfc-editor.org/rfc/rfc985.txt"
}

@TECHREPORT{rfc986,
AUTHOR="R. Callon and H. Braun",
TITLE="Guidelines for the use of {Internet-IP} addresses in the {ISO}
{Connectionless-Mode} Network Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=986,
PAGES=7,
DAYS=15,
MONTH=jun,
YEAR=1986,
ABSTRACT={This RFC suggests a method to allow the existing IP
addressing, including the IP protocol field, to be used for the ISO
Connectionless Network Protocol (CLNP). This is a draft solution to one
of the problems inherent in the use of {"}ISO-grams{"} in the DoD Internet.
Related issues will be discussed in subsequent RFCs. This RFC suggests a
proposed protocol for the ARPA-Internet community, and requests
discussion and suggestions for improvements.},
URL="http://www.rfc-editor.org/rfc/rfc986.txt"
}

@TECHREPORT{rfc987,
AUTHOR="S. E. Kille",
TITLE="Mapping between {X.400} and {RFC} 822",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=987,
PAGES=69,
DAYS=15,
MONTH=jun,
YEAR=1986,
ABSTRACT="The X.400 series of protocols have been defined by CCITT to
provide an Interpersonal Messaging Service (IPMS), making use of a store
and forward Message Transfer Service. It is expected that this standard
will be implemented very widely. This document describes a set of
mappings which will enable interworking between systems operating the
X.400 protocols and systems using RFC 822 mail protocol or protocols
derived from RFC 822. This RFC suggests a proposed protocol for the
ARPA-Internet community, and requests discussion and suggestions for
improvements.",
URL="http://www.rfc-editor.org/rfc/rfc987.txt"
}

@TECHREPORT{rfc988,
AUTHOR="S. E. Deering",
TITLE="Host extensions for {IP} multicasting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=988,
PAGES=20,
DAYS=15,
MONTH=jul,
YEAR=1986,
ABSTRACT="This memo specifies the extensions required of a host
implementation of the Internet Protocol (IP) to support internetwork
multicasting. This specification supersedes that given in RFC 966, and
constitutes a proposed protocol standard for IP multicasting in the
ARPA-Internet. The reader is directed to RFC 966 for a discussion of the
motivation and rationale behind the multicasting extension specified
here.",
URL="http://www.rfc-editor.org/rfc/rfc988.txt"
}

@TECHREPORT{rfc990,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=990,
PAGES=75,
DAYS=15,
MONTH=nov,
YEAR=1986,
ABSTRACT="This Network Working Group Request for Comments documents the
currently assigned values from several series of numbers used in network
protocol implementations. This memo is an official status report on the
numbers used in protocols in the ARPA-Internet community. This memo
obsoletes RFCs 960, 943, 923, 900, 870, 820, 790, 776, 770, 762, 758,
755, 750, 739, 717, 604, 503, 433, 349, 322, 317, 204, 179, 175, 167.",
URL="http://www.rfc-editor.org/rfc/rfc990.txt"
}

@TECHREPORT{rfc991,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Official {ARPA-Internet} protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=991,
PAGES=46,
DAYS=15,
MONTH=nov,
YEAR=1986,
ABSTRACT="This RFC identifies the documents specifying the official
protocols used in the Internet. Comments indicate any revisions or
changes planned. This memo is an official status report on the numbers
used in protocols in the ARPA-Internet community. This memo obsoletes
RFCs 961, 944, 924, 901, 880, 840, 694, 661, 617, 582, 580, 552.",
URL="http://www.rfc-editor.org/rfc/rfc991.txt"
}

@TECHREPORT{rfc992,
AUTHOR="K. Birman and T. A. Joseph",
TITLE="On communication support for fault tolerant process groups",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=992,
PAGES=18,
DAYS=15,
MONTH=nov,
YEAR=1986,
ABSTRACT={This memo describes a collection of multicast communication
primitives integrated with a mechanism for handling process failure and
recovery. These primitives facilitate the implementation of
fault-tolerant process groups, which can be used to provide distributed
services in an environment subject to non-malicious crash failures.
Here, we argue that the form of {"}best effort{"} reliability provided by
host groups may not address the requirements of those researchers who
are building fault tolerant software. Our basic premise is that reliable
handling of failures, recoveries, and dynamic process migration are
important aspects of programming in distributed environments, and that
communication support that provides unpredictable behavior in the
presence of such events places an unacceptable burden of complexity on
higher level application software. This complexity does not arise when
using the fault-tolerant process group alternative.},
URL="http://www.rfc-editor.org/rfc/rfc992.txt"
}

@TECHREPORT{rfc994,
AUTHOR=" {{International Organization for Standardization}}",
TITLE="Final text of {DIS} {8473,} Protocol for Providing the Connectionless-mode
Network Service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=994,
MONTH=mar,
YEAR=1986,
ABSTRACT="This Protocol Standard is one of a set of International
Standards produced to facilitate the interconnection of open systems.
The set of standards covers the services and protocols required to
achieve such interconnection. This Protocol Standard is positioned with
respect to other related standards by the layers defined in the
Reference Model for Open Systems Interconnection (ISO 7498). In
particular, it is a protocol of the Network Layer. This Protocol may be
used between network-entities in end systems or in Network Layer relay
systems (or both). It provides the Connectionless-mode Network Service
as defined in Addendum 1 to the Network Service Definition Covering
Connectionless-mode Transmission (ISO 8348/AD1).",
URL="http://www.rfc-editor.org/rfc/rfc994.txt"
}

@TECHREPORT{rfc995,
AUTHOR=" {{International Organization for Standardization}}",
TITLE="End System to Intermediate System Routing Exchange Protocol for use in
conjunction with {ISO} 8473",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=995,
MONTH=apr,
YEAR=1986,
ABSTRACT="This Protocol is one of a set of International Standards
produced to facilitate the interconnection of open systems. The set of
standards covers the services and protocols required to achieve such
interconnection. This Protocol is positioned with respect to other
related standards by the layers defined in the Reference Model for Open
Systems Interconnection (ISO 7498) and by the structure defined in the
Internal Organization of the Network Layer (DIS 8648). In particular, it
is a protocol of the Network Layer. This Protocol permits End Systems
and Intermediate Systems to exchange configuration and routing
information to facilitate the operation of the routing and relaying
functions of the Network Layer.",
URL="http://www.rfc-editor.org/rfc/rfc995.txt"
}

@TECHREPORT{rfc1000,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Request For Comments reference guide",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1000,
PAGES=149,
DAYS=15,
MONTH=aug,
YEAR=1987,
ABSTRACT="This RFC Reference Guide is intended to provide a historical
account by categorizing and summarizing of the Request for Comments
numbers 1 through 999 issued between the years 1969-1987. These
documents have been crossed referenced to indicate which RFCs are
current, obsolete, or revised.",
URL="http://www.rfc-editor.org/rfc/rfc1000.txt"
}

@TECHREPORT{rfc1001,
AUTHOR="  and Internet Activities Board",
TITLE="Protocol standard for a {NetBIOS} service on a {TCP/UDP} transport:
Concepts and methods",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1001,
PAGES=68,
DAYS=15,
MONTH=mar,
YEAR=1987,
ABSTRACT={This RFC defines a proposed standard protocol to support
NetBIOS services in a TCP/IP environment. Both local network and
internet operation are supported. Various node types are defined to
accommodate local and internet topologies and to allow operation with or
without the use of IP broadcast. This RFC describes the NetBIOS-over-TCP
protocols in a general manner, emphasizing the underlying ideas and
techniques. Detailed specifications are found in a companion RFC,
{"}Protocol Standard For a NetBIOS Service on a TCP/UDP Transport:
Detailed Specifications{"}.},
URL="http://www.rfc-editor.org/rfc/rfc1001.txt"
}

@TECHREPORT{rfc1002,
AUTHOR="  and Internet Activities Board",
TITLE="Protocol standard for a {NetBIOS} service on a {TCP/UDP} transport:
Detailed specifications",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1002,
PAGES=85,
DAYS=15,
MONTH=mar,
YEAR=1987,
ABSTRACT={This RFC defines a proposed standard protocol to support
NetBIOS services in a TCP/IP environment. Both local network and
internet operation are supported. Various node types are defined to
accommodate local and internet topologies and to allow operation with or
without the use of IP broadcast. This RFC gives the detailed
specifications of the netBIOS-over-TCP packets, protocols, and defined
constants and variables. A more general overview is found in a companion
RFC, {"}Protocol Standard For NetBIOS Service on TCP/UDP Transport:
Concepts and Methods{"}.},
URL="http://www.rfc-editor.org/rfc/rfc1002.txt"
}

@TECHREPORT{rfc1003,
AUTHOR="A. R. Katz",
TITLE="Issues in defining an equations representation standard",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1003,
PAGES=7,
DAYS=15,
MONTH=mar,
YEAR=1987,
ABSTRACT="This memo is intended to identify and explore issues in
defining a standard for the exchange of mathematical equations. No
attempt is made at a complete definition and more questions are asked
than are answered. Questions about the user interface are only addressed
to the extent that they affect interchange issues.",
URL="http://www.rfc-editor.org/rfc/rfc1003.txt"
}

@TECHREPORT{rfc1004,
AUTHOR="D. L. Mills",
TITLE="Distributed-protocol authentication scheme",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1004,
PAGES=8,
DAYS=15,
MONTH=apr,
YEAR=1987,
ABSTRACT="The purpose of this RFC is to focus discussion on
authentication problems in the Internet and possible methods of
solution. The proposed solutions this document are not intended as
standards for the Internet at this time. Rather, it is hoped that a
general consensus will emerge as to the appropriate solution to
authentication problems, leading eventually to the adoption of
standards. This document suggests mediated access-control and
authentication procedures suitable for those cases when an association
is to be set up between users belonging to different trust environments.",
URL="http://www.rfc-editor.org/rfc/rfc1004.txt"
}

@TECHREPORT{rfc1005,
AUTHOR="A. Khanna and Andrew G. Malis",
TITLE="{ARPANET} {AHIP-E} Host Access Protocol (enhanced {AHIP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1005,
PAGES=34,
DAYS=15,
MONTH=may,
YEAR=1987,
ABSTRACT="This RFC is a proposed specification for the encoding of Class
A IP addresses for use on ARPANET-style networks such as the Milnet and
Arpanet, and for enhancements to the ARPANET AHIP Host Access Protocol
(AHIP; formerly known as 1822). These enhancements increase the size of
the PSN field, allow ARPANET hosts to use logical names to address each
other, allow for the communication of type-of-service information from
the host to the PSN and enable the PSN to provide congestion feedback to
the host on a connection basis.",
URL="http://www.rfc-editor.org/rfc/rfc1005.txt"
}

@TECHREPORT{rfc1006,
AUTHOR="Marshall T. Rose and D. E. Cass",
TITLE="{ISO} transport services on top of the {TCP:} Version 3",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1006,
PAGES=18,
DAYS=15,
MONTH=may,
YEAR=1987,
ABSTRACT="This memo specifies a standard for the Internet community.
Hosts on the Internet that choose to implement ISO transport services on
top of the TCP are expected to adopt and implement this standard. TCP
port 102 is reserved for hosts which implement this standard. This memo
specifies version 3 of the protocol and supersedes RFC-983. Changes
between the protocol is described in RFC-983 and this memo are minor,
but unfortunately incompatible.",
URL="http://www.rfc-editor.org/rfc/rfc1006.txt"
}

@TECHREPORT{rfc1007,
AUTHOR="W. McCoy",
TITLE="Military supplement to the {ISO} Transport Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1007,
PAGES=23,
DAYS=15,
MONTH=jun,
YEAR=1987,
ABSTRACT="This document supplements the Transport Service and Protocol
of the International Standards Organization (ISO), IS 8072 and IS 8073,
respectively, and their formal descriptions by providing conventions,
option selections and parameter values. This RFC is being distributed to
members of the Internet community in order to solicit comments on the
Draft Military Supplement. While this document may not be directly
relevant to the research problems of the Internet, it may be of some
interest to a number of researchers and implementors.",
URL="http://www.rfc-editor.org/rfc/rfc1007.txt"
}

@TECHREPORT{rfc1008,
AUTHOR="W. McCoy",
TITLE="Implementation guide for the {ISO} Transport Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1008,
PAGES=73,
DAYS=15,
MONTH=jun,
YEAR=1987,
ABSTRACT="This RFC is being distributed to members of the Internet
community in order to solicit comments on the Implementors Guide. While
this document may not be directly relevant to the research problems of
the Internet, it may be of some interest to a number of researchers and
implementors.",
URL="http://www.rfc-editor.org/rfc/rfc1008.txt"
}

@TECHREPORT{rfc1009,
AUTHOR="R. Braden and J. B. Postel",
TITLE="Requirements for Internet gateways",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1009,
PAGES=55,
DAYS=15,
MONTH=jun,
YEAR=1987,
ABSTRACT="This RFC summarizes the requirements for gateways to be used
between networks supporting the Internet protocols. This document is a
formal statement of the requirements to be met by gateways used in the
Internet system. As such, it is an official specification for the
Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc1009.txt"
}

@TECHREPORT{rfc1010,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1010,
PAGES=44,
DAYS=15,
MONTH=may,
YEAR=1987,
ABSTRACT="This memo is an official status report on the numbers used in
protocols in the Internet community. It documents the currently assigned
values from several series of numbers including link, socket, port, and
protocol, used in network protocol implementations.",
URL="http://www.rfc-editor.org/rfc/rfc1010.txt"
}

@TECHREPORT{rfc1011,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Official Internet protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1011,
PAGES=52,
DAYS=15,
MONTH=may,
YEAR=1987,
ABSTRACT="This memo is an official status report on the protocols used
in the Internet community. It identifies the documents specifying the
official protocols used in the Internet. Comments indicate any revisions
or changes planned.",
URL="http://www.rfc-editor.org/rfc/rfc1011.txt"
}

@TECHREPORT{rfc1012,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Bibliography of Request For Comments 1 through 999",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1012,
PAGES=64,
DAYS=15,
MONTH=jun,
YEAR=1987,
ABSTRACT="This RFC is a reference guide for the Internet community which
provides a bibliographic summary of the Request for Comments numbers 1
through 999 issued between the years 1969-1987.",
URL="http://www.rfc-editor.org/rfc/rfc1012.txt"
}

@TECHREPORT{rfc1013,
AUTHOR="R. Scheifler",
TITLE="X Window System Protocol, version {11:} Alpha update April 1987",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1013,
PAGES=101,
DAYS=15,
MONTH=jun,
YEAR=1987,
ABSTRACT="This RFC is distributed to the Internet community for
information only. It does not establish an Internet standard. The X
window system has been widely reviewed and tested. The Internet
community is encouraged to experiment with it.",
URL="http://www.rfc-editor.org/rfc/rfc1013.txt"
}

@TECHREPORT{rfc1014,
AUTHOR=" {Sun Microsystems}",
TITLE="{XDR:} External Data Representation standard",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1014,
PAGES=20,
DAYS=15,
MONTH=jun,
YEAR=1987,
ABSTRACT="XDR is a standard for the description and encoding of data. It
is useful for transferring data between different computer
architectures. XDR fits into ISO presentation layer, and is roughly
analogous in purpose to X.409, ISO Abstract Syntax Notation. The major
difference between these two is that XDR uses implicit typing, while
X.409 uses explicit typing. This RFC is distributed for information
only, it does not establish a Internet standard.",
URL="http://www.rfc-editor.org/rfc/rfc1014.txt"
}

@TECHREPORT{rfc1015,
AUTHOR="B. M. Leiner",
TITLE="Implementation plan for interagency research Internet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1015,
PAGES=24,
DAYS=15,
MONTH=jul,
YEAR=1987,
ABSTRACT={This RFC proposes an Interagency Research Internet as the
natural outgrowth of the current Internet. This is an {"}idea paper{"} and
discussion is strongly encouraged.},
URL="http://www.rfc-editor.org/rfc/rfc1015.txt"
}

@TECHREPORT{rfc1016,
AUTHOR="W. Prue and J. B. Postel",
TITLE="Something a host could do with source quench: The Source Quench Introduced
Delay {(SQuID)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1016,
PAGES=18,
DAYS=15,
MONTH=jul,
YEAR=1987,
ABSTRACT={The memo is intended to explore the issue of what a host could
do with a source quench. The proposal is for each source host IP module
to introduce some delay between datagrams sent to the same destination
host. This is a {"}crazy idea paper{"} and discussion is essential.},
URL="http://www.rfc-editor.org/rfc/rfc1016.txt"
}

@TECHREPORT{rfc1017,
AUTHOR="B. M. Leiner",
TITLE="Network requirements for scientific research: Internet task force on
scientific computing",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1017,
PAGES=19,
DAYS=15,
MONTH=aug,
YEAR=1987,
ABSTRACT={This RFC identifies the requirements on communication networks
for supporting scientific research. It proposes some specific areas for
near term work, as well as some long term goals. This is an {"}idea{"}
paper
and discussion is strongly encouraged.},
URL="http://www.rfc-editor.org/rfc/rfc1017.txt"
}

@TECHREPORT{rfc1018,
AUTHOR="A. A. McKenzie",
TITLE="Some comments on {SQuID}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1018,
PAGES=3,
DAYS=15,
MONTH=aug,
YEAR=1987,
ABSTRACT={This memo is a discussion of some of the ideas expressed in
RFC-1016 on Source Quench. This memo introduces the distinction of the
cause of congestion in a gateway between the effects of {"}Funneling{"} and
Mismatch{"}. It is offered in the same spirit as RFC-1016; to stimulate
discussion. The opinions offered are personal, not corporate, opinions.},
URL="http://www.rfc-editor.org/rfc/rfc1018.txt"
}

@TECHREPORT{rfc1019,
AUTHOR="D. Arnon",
TITLE="Report of the Workshop on Environments for Computational Mathematics",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1019,
PAGES=8,
DAYS=15,
MONTH=sep,
YEAR=1987,
ABSTRACT="This memo is a report on the discussion of the representation
of equations in a workshop at the ACM SIGGRAPH Conference held in
Anaheim, California on 30 July 1987.",
URL="http://www.rfc-editor.org/rfc/rfc1019.txt"
}

@TECHREPORT{rfc1021,
AUTHOR="C. Partridge and G. Trewitt",
TITLE="High-level Entity Management System {(HEMS)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1021,
PAGES=5,
DAYS=15,
MONTH=oct,
YEAR=1987,
ABSTRACT="This memo provides a general overview of the High-level Entity
management system (HEMS). This system is experimental, and is currently
being tested in portions of the Internet.",
URL="http://www.rfc-editor.org/rfc/rfc1021.txt"
}

@TECHREPORT{rfc1022,
AUTHOR="C. Partridge and G. Trewitt",
TITLE="High-level Entity Management Protocol {(HEMP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1022,
PAGES=12,
DAYS=15,
MONTH=oct,
YEAR=1987,
ABSTRACT="This memo presents an application protocol for managing
network entities such as hosts, gateways, and front end machines. This
protocol is a component of the High-level Entity Management System
HEMS), described is RFC-1021. This memo also assumes a knowledge of the
ISO data encoding standard, ASN.1.",
URL="http://www.rfc-editor.org/rfc/rfc1022.txt"
}

@TECHREPORT{rfc1023,
AUTHOR="G. Trewitt and C. Partridge",
TITLE="{HEMS} monitoring and control language",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1023,
PAGES=17,
DAYS=15,
MONTH=oct,
YEAR=1987,
ABSTRACT="This RFC specifies the High-Level Entity Management System
(HEMS) Monitoring and Control Language. This language defines the
requests and replies used in HEMS. This memo assumes knowledge of the
HEMS system described in RFC-1021, and of the ISO data encoding
standard, ASN.1.",
URL="http://www.rfc-editor.org/rfc/rfc1023.txt"
}

@TECHREPORT{rfc1024,
AUTHOR="C. Partridge and G. Trewitt",
TITLE="{HEMS} variable definitions",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1024,
PAGES=74,
DAYS=15,
MONTH=oct,
YEAR=1987,
ABSTRACT="This memo assigns instruction codes, defines object formats
and object semantics for use with the High-Level Monitoring and Control
Language, defined in RFC-1023. A general system has been described in
previous memos (RFC-1021, RFC-1022). This system is called the
High-Level Entity Management System (HEMS). This memo is provisional and
the definitions are subject to change. Readers should confirm with the
authors that they have the most recent version. This RFC assumes a
working knowledge of the ISO data encoding standard, ASN.1, and a
general understanding of the IP protocol suite.",
URL="http://www.rfc-editor.org/rfc/rfc1024.txt"
}

@TECHREPORT{rfc1025,
AUTHOR="J. B. Postel",
TITLE="{TCP} and {IP} bake off",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1025,
PAGES=6,
DAYS=15,
MONTH=sep,
YEAR=1987,
ABSTRACT="This memo describes some of the procedures, scoring and tests
used in the TCP and IP bake offs held in the early development of these
protocols. These procedures and tests may still be of use in testing
newly implemented TCP and IP modules.",
URL="http://www.rfc-editor.org/rfc/rfc1025.txt"
}

@TECHREPORT{rfc1026,
AUTHOR="S. E. Kille",
TITLE="Addendum to {RFC} {987:} (Mapping between {X.400} and {RFC-822)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1026,
PAGES=4,
DAYS=15,
MONTH=sep,
YEAR=1987,
ABSTRACT="This memo suggest a proposed protocol for the Internet
community, and request discussion and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc1026.txt"
}

@TECHREPORT{rfc1027,
AUTHOR="S. Carl-Mitchell and J. S. Quarterman",
TITLE="Using {ARP} to implement transparent subnet gateways",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1027,
PAGES=8,
DAYS=15,
MONTH=oct,
YEAR=1987,
ABSTRACT={This RFC describes the use of the Address Resolution Protocol
(ARP) by subnet gateways to permit hosts on the connected subnets to
communicate without being aware of the existence of subnets, using the
technique of {"}Proxy ARP{"}.},
URL="http://www.rfc-editor.org/rfc/rfc1027.txt"
}

@TECHREPORT{rfc1028,
AUTHOR="J. R. Davin and J. D. Case and M. S. Fedor and M. L. Schoffstall",
TITLE="Simple Gateway Monitoring Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1028,
PAGES=35,
DAYS=15,
MONTH=nov,
YEAR=1987,
ABSTRACT="This memo defines a simple application-layer protocol by which
management information for a gateway may be inspected or altered by
remote users. This proposal is intended only as an interim response to
immediate gateway monitoring needs.",
URL="http://www.rfc-editor.org/rfc/rfc1028.txt"
}

@TECHREPORT{rfc1030,
AUTHOR="Mark L. Lambert",
TITLE="On testing the {NETBLT} Protocol over divers networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1030,
PAGES=16,
DAYS=15,
MONTH=nov,
YEAR=1987,
ABSTRACT="This memo describes the results gathered from testing NETBLT
over three networks of different bandwidths and round-trip delays. The
results are not complete, but the information gathered so far has not
been promising. The NETBLT protocol is specified in RFC-998; this
document assumes an understanding of the specification as described in
RFC-998.",
URL="http://www.rfc-editor.org/rfc/rfc1030.txt"
}

@TECHREPORT{rfc1031,
AUTHOR="W. D. Lazear",
TITLE="{MILNET} name domain transition",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1031,
PAGES=10,
DAYS=15,
MONTH=nov,
YEAR=1987,
ABSTRACT="This RFC consolidates information necessary for the
implementation of domain style names throughout the DDN/MILNET Internet
community. The introduction of domain style names will impact all hosts
in the DDN/MILNET Internet. This RFC is designed as an aid to
implementors and administrators by providing: 1) an overview of the
transition process from host tables to domains, 2) a timetable for the
transition, and 3) references to documentation and software relating to
the domain system.",
URL="http://www.rfc-editor.org/rfc/rfc1031.txt"
}

@TECHREPORT{rfc1032,
AUTHOR="Mary K. Stahl",
TITLE="Domain administrators guide",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1032,
PAGES=14,
DAYS=15,
MONTH=nov,
YEAR=1987,
ABSTRACT="Domains are administrative entities that provide decentralized
management of host naming and addressing. The domain-naming system is
distributed and hierarchical. This memo describes procedures for
registering a domain with the Network Information Center (NIC) of
Defense Data Network (DDN), and offers guidelines on the establishment
and administration of a domain in accordance with the requirements
specified in RFC-920. It is recommended that the guidelines described in
this document be used by domain administrators in the establishment and
control of second-level domains. The role of the domain administrator
(DA) is that of coordinator, manager, and technician. If his domain is
established at the second level or lower in the tree, the domain
administrator must register by interacting with the management of the
domain directly above this.",
URL="http://www.rfc-editor.org/rfc/rfc1032.txt"
}

@TECHREPORT{rfc1033,
AUTHOR="M. Lottor",
TITLE="Domain administrators operations guide",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1033,
PAGES=22,
DAYS=15,
MONTH=nov,
YEAR=1987,
ABSTRACT="This RFC provides guidelines for domain administrators in
operating a domain server and maintaining their portion of the
hierarchical database. Familiarity with the domain system is assumed
(see RFCs 1031, 1032, 1034, and 1035).",
URL="http://www.rfc-editor.org/rfc/rfc1033.txt"
}

@TECHREPORT{rfc1034,
AUTHOR="P. V. Mockapetris",
TITLE="Domain names - concepts and facilities",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1034,
PAGES=55,
DAYS=15,
MONTH=nov,
YEAR=1987,
ABSTRACT="This RFC is the revised basic definition of The Domain Name
System. It obsoletes RFC-882. This memo describes the domain style names
and their used for host address look up and electronic mail forwarding.
It discusses the clients and servers in the domain name system and the
protocol used between them.",
URL="http://www.rfc-editor.org/rfc/rfc1034.txt"
}

@TECHREPORT{rfc1035,
AUTHOR="P. V. Mockapetris",
TITLE="Domain names - implementation and specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1035,
PAGES=55,
DAYS=15,
MONTH=nov,
YEAR=1987,
ABSTRACT="This RFC is the revised specification of the protocol and
format used in the implementation of the Domain Name System. It
obsoletes RFC-883. This memo documents the details of the domain name
client - server communication.",
URL="http://www.rfc-editor.org/rfc/rfc1035.txt"
}

@TECHREPORT{rfc1036,
AUTHOR="M. R. Horton and R. Adams",
TITLE="Standard for interchange of {USENET} messages",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1036,
PAGES=19,
DAYS=15,
MONTH=dec,
YEAR=1987,
ABSTRACT="This RFC defines the standard format for the interchange of
network News messages among USENET hosts. It updates and replaces
RFC-850, reflecting version B2.11 of the News program. This memo is
distributed as an RFC to make this information easily accessible to the
Internet community. It does not specify an Internet standard.",
URL="http://www.rfc-editor.org/rfc/rfc1036.txt"
}

@TECHREPORT{rfc1037,
AUTHOR="B. S. Greenberg and S. Keene",
TITLE="{NFILE} - a file access protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1037,
PAGES=86,
DAYS=15,
MONTH=dec,
YEAR=1987,
ABSTRACT="This document includes a specification of the NFILE file
access protocol and its underlying levels of protocol, the Token List
Transport Layer and Byte Stream with Mark. The goal of this
specification is to promote discussion of the ideas described here, and
to encourage designers of future file protocols to take advantage of
these ideas. A secondary goal is to make the specification available to
sites that might benefit from implementing NFILE.",
URL="http://www.rfc-editor.org/rfc/rfc1037.txt"
}

@TECHREPORT{rfc989,
AUTHOR="J. R. Linn",
TITLE="Privacy enhancement for Internet electronic mail: Part {I:} Message
encipherment and authentication procedures",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=989,
PAGES=23,
DAYS=15,
MONTH=feb,
YEAR=1987,
ABSTRACT="This RFC suggests a proposed protocol for the Internet
community and requests discussion and suggestions for improvements. This
RFC is the outgrowth of a series of IAB Privacy Task Force meetings and
of internal working papers distributed for those meetings. This RFC
defines message encipherment and authentication procedures, as the
initial phase of an effort to provide privacy enhancement services for
electronic mail transfer in the Internet. It is intended that the
procedures defined here be compatible with a wide range of key
management approaches, including both conventional (symmetric) and
public-key (asymmetric) approaches for encryption of data encrypting
keys. Use of conventional cryptography for message text encryption
and/or authentication is anticipated. Privacy enhancement services
(confidentiality, authentication, and message integrity assurance) are
offered through the use of end-to- end cryptography between originator
and recipient User Agent processes, with no special processing
requirements imposed on the Message Transfer System at endpoints or at
intermediate relay sites. This approach allows privacy enhancement
facilities to be incorporated on a site-by-site or user-by-user basis
without impact on other Internet entities. Interoperability among
heterogeneous components and mail transport facilities is supported.",
URL="http://www.rfc-editor.org/rfc/rfc989.txt"
}

@TECHREPORT{rfc996,
AUTHOR="D. L. Mills",
TITLE="Statistics server",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=996,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1987,
ABSTRACT="This RFC specifies a standard for the ARPA Internet community.
Hosts and gateways on the DARPA Internet that choose to implement a
remote statistics monitoring facility may use this protocol to send
statistics data upon request to a monitoring center or debugging host.",
URL="http://www.rfc-editor.org/rfc/rfc996.txt"
}

@TECHREPORT{rfc997,
AUTHOR="S. Romano and Mark Stahl",
TITLE="Internet numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=997,
PAGES=42,
DAYS=15,
MONTH=mar,
YEAR=1987,
ABSTRACT="This memo is an official status report on the network numbers
used in the Internet community. As of 1-Mar-87 the Network Information
Center (NIC) at SRI International has assumed responsibility for
assignment of Network Numbers and Autonomous System Numbers. This RFC
documents the current assignments of these numbers at the time of this
transfer of responsibility.",
URL="http://www.rfc-editor.org/rfc/rfc997.txt"
}

@TECHREPORT{rfc998,
AUTHOR="D. D. Clark and Mark L. Lambert and L. Zhang",
TITLE="{NETBLT:} A bulk data transfer protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=998,
PAGES=21,
DAYS=15,
MONTH=mar,
YEAR=1987,
ABSTRACT="This document is a description of and a specification for the
NETBLT protocol. It is a revision of the specification published in
RFC-969. NETBLT (NETwork BLock Transfer) is a transport level protocol
intended for the rapid transfer of a large quantity of data between
computers. It provides a transfer that is reliable and flow controlled,
and is designed to provide maximum throughput over a wide variety of
networks. Although NETBLT currently runs on top of the Internet Protocol
(IP), it should be able to operate on top of any datagram protocol
similar in function to IP. This document is published for discussion and
comment, and does not constitute a standard. The proposal may change and
certain parts of the protocol have not yet been specified;
implementation of this document is therefore not advised.",
URL="http://www.rfc-editor.org/rfc/rfc998.txt"
}

@TECHREPORT{rfc999,
AUTHOR="A. Westine and J. B. Postel",
TITLE="Requests For Comments summary notes: {900-999}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=999,
PAGES=22,
DAYS=15,
MONTH=apr,
YEAR=1987,
ABSTRACT="A summary of the Request for Comments Documents from RFC
900-999.",
URL="http://www.rfc-editor.org/rfc/rfc999.txt"
}

@TECHREPORT{rfc1029,
AUTHOR="G. Parr",
TITLE="More fault tolerant approach to address resolution for a {Multi-LAN} system
of Ethernets",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1029,
PAGES=17,
DAYS=15,
MONTH=may,
YEAR=1988,
ABSTRACT="This memo discusses an extension to a Bridge Protocol to
detect and disclose changes in heighbouring host address parameters in a
Multi-Lan system of Ethernets. The problem is one which is appearing
more and more regularly as the interconnected systems grow larger on
Campuses and in Commercial Institutions. This RFC suggests a protocol
enhancement for the Internet community, and requests discussion and
suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc1029.txt"
}

@TECHREPORT{rfc1038,
AUTHOR="M. St. Johns",
TITLE="Draft revised {IP} security option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1038,
PAGES=7,
DAYS=15,
MONTH=jan,
YEAR=1988,
ABSTRACT={This memo is a pre-publication draft of the revised Internet
Protocol Security Option. This RFC reflects the version as approved by
the Protocol Standards Steering group, and is provided for informational
purposes only. The final version of this document will be available from
Navy publications and should not differ from this document in any major
fashion. This document will be published as a change to the MIL- STD
1777, {"}Internet Protocol{"}.},
URL="http://www.rfc-editor.org/rfc/rfc1038.txt"
}

@TECHREPORT{rfc1039,
AUTHOR="D. Latham",
TITLE="{DoD} statement on Open Systems Interconnection protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1039,
PAGES=3,
DAYS=15,
MONTH=jan,
YEAR=1988,
ABSTRACT="This RFC reproduces a memorandum issued on 2-JUL-87 from the
Assistant Secretary of Defense for Command, Control, Communications, and
Intelligence (ASDC31) to the Director of the Defense Communications
Agency (DCA). This memo is distributed for information only.",
URL="http://www.rfc-editor.org/rfc/rfc1039.txt"
}

@TECHREPORT{rfc1040,
AUTHOR="J. R. Linn",
TITLE="Privacy enhancement for Internet electronic mail: Part {I:} Message
encipherment and authentication procedures",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1040,
PAGES=29,
DAYS=15,
MONTH=jan,
YEAR=1988,
ABSTRACT="This RFC is the Outgrowth of a series of IAB Privacy Task
Force meetings and of internal working papers distributed for those
meetings. This memo defines message encipherment and authentication
procedures, as the initial phase of an effort to provide privacy
enhancement services for electronic mail transfer in the Internet.
Detailed key management mechanisms to support these procedures will be
defined in a subsequent RFC. As a goal of this initial phase, it is
intended that the procedures defined here be compatible with a wide
range of key management approaches, including both conventional
(symmetric) and public-key (asymmetric) approaches for encryption of
data encrypting keys. Use of conventional cryptography for message text
encryption and/or integrity check computation is anticipated.",
URL="http://www.rfc-editor.org/rfc/rfc1040.txt"
}

@TECHREPORT{rfc1041,
AUTHOR="Y. Rekhter",
TITLE="Telnet 3270 regime option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1041,
PAGES=6,
DAYS=15,
MONTH=jan,
YEAR=1988,
ABSTRACT="This RFC specifies a proposed standard for the Internet
community. Hosts on the Internet that want to support 3270 data stream
within the Telnet protocol, are expected to adopt and implement this
standard.",
URL="http://www.rfc-editor.org/rfc/rfc1041.txt"
}

@TECHREPORT{rfc1042,
AUTHOR="J. B. Postel and J. F. Reynolds",
TITLE="Standard for the transmission of {IP} datagrams over {IEEE} 802 networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1042,
PAGES=15,
DAYS=15,
MONTH=feb,
YEAR=1988,
ABSTRACT="This RFC specifies a standard method of encapsulating the
Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP)
requests and replies on IEEE 802 Networks to allow compatible and
interoperable implementations. This RFC specifies a protocol standard
for the Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc1042.txt"
}

@TECHREPORT{rfc1043,
AUTHOR="A. Yasuda and T. Thompson",
TITLE="Telnet Data Entry Terminal option: {DODIIS} implementation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1043,
PAGES=26,
DAYS=15,
MONTH=feb,
YEAR=1988,
ABSTRACT="This RFC suggests a proposed protocol on the TELNET Data Entry
Terminal (DET) Option - DODIIS Implementation for the Internet
community. It is intended that this specification be capatible with the
specification of DET Option in RFC-732. Discussion and suggests for
improvements are encouraged.",
URL="http://www.rfc-editor.org/rfc/rfc1043.txt"
}

@TECHREPORT{rfc1044,
AUTHOR="K. Hardwick and J. Lekashman",
TITLE="Internet Protocol on Network System's {HYPERchannel:} Protocol
specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1044,
PAGES=43,
DAYS=15,
MONTH=feb,
YEAR=1988,
ABSTRACT="This memo intends to provide a complete discussion of the
protocols and techniques used to embed DoD standard Internet Protocol
datagrams (and its associated higher level protocols) on Network Systems
Corporation's HYPERchannel equipment. This document is directed toward
network planners and implementors who are already familiar with the
TCP/IP protocol suite and the techniques used to carry TCP/IP traffic on
common networks such as the DDN or the Ethernet. No great familiarity
with NSC products is assumed; an appendix is devoted to a review of NSC
technologies and protocols.",
URL="http://www.rfc-editor.org/rfc/rfc1044.txt"
}

@TECHREPORT{rfc1045,
AUTHOR="D. R. Cheriton",
TITLE="{VMTP:} Versatile Message Transaction Protocol: Protocol specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1045,
PAGES=123,
DAYS=15,
MONTH=feb,
YEAR=1988,
ABSTRACT="This memo specifies the Versatile Message Transaction Protocol
(VMTP) [Version 0.7 of 19-Feb-88], a transport protocol specifically
designed to support the transaction model of communication, as
exemplified by remote procedure call (RPC). The full function of VMTP,
including support for security, real-time, asynchronous message
exchanges, streaming, multicast and idempotency, provides a rich
selection to the VMTP user level. Subsettability allows the VMTP module
for particular clients and servers to be specialized and simplified to
the services actually required. Examples of such simple clients and
servers include PROM network bootload programs, network boot servers,
data sensors and simple controllers, to mention but a few examples. This
RFC describes a protocol proposed as a standard for the Internet
community.",
URL="http://www.rfc-editor.org/rfc/rfc1045.txt"
}

@TECHREPORT{rfc1046,
AUTHOR="W. Prue and J. B. Postel",
TITLE="Queuing algorithm to provide type-of-service for {IP} links",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1046,
PAGES=11,
DAYS=15,
MONTH=feb,
YEAR=1988,
ABSTRACT={This memo is intended to explore how Type-of-Service might be
implemented in the Internet. The proposal describes a method of queuing
which can provide the different classes of service. The technique also
prohibits one class of service from consuming excessive resources or
excluding other classes of service. This is an {"}idea paper{"} and
discussion is strongly encouraged.},
URL="http://www.rfc-editor.org/rfc/rfc1046.txt"
}

@TECHREPORT{rfc1047,
AUTHOR="C. Partridge",
TITLE="Duplicate messages and {SMTP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1047,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1988,
ABSTRACT="An examination of a synchronization problem in the Simple Mail
Transfer Protocol (SMTP) is presented. This synchronization problem can
cause a message to be delivered multiple times. A method for avoiding
this problem is suggested. Nodding familiarity with the SMTP
specification, RFC-821, is required.",
URL="http://www.rfc-editor.org/rfc/rfc1047.txt"
}

@TECHREPORT{rfc1048,
AUTHOR="J. F. Reynolds",
TITLE="{BOOTP} vendor information extensions",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1048,
PAGES=7,
DAYS=15,
MONTH=feb,
YEAR=1988,
ABSTRACT="This memo proposes an addition to the Bootstrap Protocol
(BOOTP). Comments and suggestions for improvements are sought.",
URL="http://www.rfc-editor.org/rfc/rfc1048.txt"
}

@TECHREPORT{rfc1049,
AUTHOR="M. A. Sirbu",
TITLE="Content-type header field for Internet messages",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1049,
PAGES=8,
DAYS=15,
MONTH=mar,
YEAR=1988,
ABSTRACT="This memo suggests proposed additions to the Internet Mail
Protocol, RFC-822, for the Internet community, and requests discussion
and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc1049.txt"
}

@TECHREPORT{rfc1050,
AUTHOR=" {Sun Microsystems}",
TITLE="{RPC:} Remote Procedure Call Protocol specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1050,
PAGES=24,
DAYS=15,
MONTH=apr,
YEAR=1988,
ABSTRACT="This memo specifies a message protocol used in implementing
Sun's Remote Procedure Call (RPC) package. This RFC describes a standard
that Sun Microsystems and others are using and is one they wish to
propose for the Internet's consideration. It is not an Internet standard
at this time.",
URL="http://www.rfc-editor.org/rfc/rfc1050.txt"
}

@TECHREPORT{rfc1051,
AUTHOR="P. A. Prindeville",
TITLE="Standard for the transmission of {IP} datagrams and {ARP} packets over
{ARCNET} networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1051,
PAGES=4,
DAYS=15,
MONTH=mar,
YEAR=1988,
ABSTRACT="This memo specifies a standard method of encapsulating
Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams
on an ARCNET. This RFC is a standard protocol for the Internet
community.",
URL="http://www.rfc-editor.org/rfc/rfc1051.txt"
}

@TECHREPORT{rfc1052,
AUTHOR="V. G. Cerf",
TITLE="{IAB} recommendations for the development of Internet network management
standards",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1052,
PAGES=14,
DAYS=15,
MONTH=apr,
YEAR=1988,
ABSTRACT="This RFC is intended to convey to the Internet community and
other interested parties the recommendations of the Internet Activities
Board (IAB) for the development of network management protocols for use
in the TCP/IP environment. This memo does NOT, in and of itself, define
or propose an Official Internet Protocol. It does reflect, however, the
policy of the IAB with respect to further network management development
in the short and long term.",
URL="http://www.rfc-editor.org/rfc/rfc1052.txt"
}

@TECHREPORT{rfc1053,
AUTHOR="S. Levy and T. Jacobson",
TITLE="Telnet {X.3} {PAD} option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1053,
PAGES=21,
DAYS=15,
MONTH=apr,
YEAR=1988,
ABSTRACT="This RFC proposes a new option to Telnet for the Internet
community, and requests discussion and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc1053.txt"
}

@TECHREPORT{rfc1054,
AUTHOR="S. E. Deering",
TITLE="Host extensions for {IP} multicasting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1054,
PAGES=19,
DAYS=15,
MONTH=may,
YEAR=1988,
ABSTRACT={This memo specifies the extensions required of a host
implementation of the Internet Protocol (IP) to support multicasting. IP
multicasting is the transmission of an IP datagram to a {"}host group{"}, a
set hosts identified by a single IP destination address. A multicast
datagram is delivered to all members of its destination host group with
the same {"}best-efforts{"} reliability as regular unicast IP datagrams. It
is proposed as a standard for IP multicasting in the Internet. This
specification is a major revision of RFC-988.},
URL="http://www.rfc-editor.org/rfc/rfc1054.txt"
}

@TECHREPORT{rfc1055,
AUTHOR="J. L. Romkey",
TITLE="Nonstandard for transmission of {IP} datagrams over serial lines: {SLIP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1055,
PAGES=6,
DAYS=15,
MONTH=jun,
YEAR=1988,
ABSTRACT="The TCP/IP protocol family runs over a variety of network
media: IEEE 802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines,
satellite links, and serial lines. There are standard encapsulations for
IP packets defined for many of these networks, but there is no standard
for serial lines. SLIP, Serial Line IP, is a currently a de facto
standard, commonly used for point-to-point serial connections running
TCP/IP. It is not an Internet standard.",
URL="http://www.rfc-editor.org/rfc/rfc1055.txt"
}

@TECHREPORT{rfc1056,
AUTHOR="Mark L. Lambert",
TITLE="{PCMAIL:} A distributed mail system for personal computers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1056,
PAGES=38,
DAYS=15,
MONTH=jun,
YEAR=1988,
ABSTRACT="This memo is a discussion of the Pcmail workstation based
distributed mail system. It is identical to the discussion in RFC-993,
save that a new, much simpler mail transport protocol is described. The
new transport protocol is the result of continued research into ease of
protocol implementation and use issues.",
URL="http://www.rfc-editor.org/rfc/rfc1056.txt"
}

@TECHREPORT{rfc1057,
AUTHOR=" {Sun Microsystems}",
TITLE="{RPC:} Remote Procedure Call Protocol specification: Version 2",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1057,
PAGES=25,
DAYS=15,
MONTH=jun,
YEAR=1988,
ABSTRACT="This RFC describes a standard that Sun Microsystems and others
are using, and is one we wish to propose for the Internet's
consideration. This memo is not an Internet standard at this time.",
URL="http://www.rfc-editor.org/rfc/rfc1057.txt"
}

@TECHREPORT{rfc1058,
AUTHOR="C. Hedrick",
TITLE="Routing Information Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1058,
PAGES=33,
DAYS=15,
MONTH=jun,
YEAR=1988,
ABSTRACT="This RFC describes an existing protocol for exchanging routing
information among gateways and other hosts. It is intended to be used as
a basis for developing gateway software for use in the Internet
community.",
URL="http://www.rfc-editor.org/rfc/rfc1058.txt"
}

@TECHREPORT{rfc1059,
AUTHOR="D. L. Mills",
TITLE="Network Time Protocol (version {1)} specification and implementation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1059,
PAGES=58,
DAYS=15,
MONTH=jul,
YEAR=1988,
ABSTRACT="This memo describes the Network Time Protocol (NTP), specifies
its formal structure and summarizes information useful for its
implementation. NTP provides the mechanisms to synchronize time and
coordinate time distribution in a large, diverse internet operating at
rates from mundane to lightwave. It uses a returnable-time design in
which a distributed subnet of time servers operating in a self-
organizing, hierarchical master-slave configuration synchronizes logical
clocks within the subnet and to national time standards via wire or
radio. The servers can also redistribute reference time via local
routing algorithms and time daemons. The NTP architectures, algorithms
and protocols which have evolved over several years of implementation
and refinement are described in this document. The prototype system,
which has been in regular operation in the Internet for the last two
years, is described in an Appendix along with performance data which
shows that timekeeping accuracy throughout most portions of the Internet
can be ordinarily maintained to within a few tens of milliseconds, even
the cases of failure or disruption of clocks, time servers or nets. This
is a Draft Standard for an Elective protocol.",
URL="http://www.rfc-editor.org/rfc/rfc1059.txt"
}

@TECHREPORT{rfc1062,
AUTHOR="S. Romano and Mary K. Stahl and M. Recker",
TITLE="Internet numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1062,
PAGES=65,
DAYS=15,
MONTH=aug,
YEAR=1988,
ABSTRACT="This memo is an official status report on the network numbers
and gateway autonomous system numbers used in the Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc1062.txt"
}

@TECHREPORT{rfc1063,
AUTHOR="J. C. Mogul and Christopher A. Kent and C. Partridge and K. McCloghrie",
TITLE="{IP} {MTU} discovery options",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1063,
PAGES=11,
DAYS=15,
MONTH=jul,
YEAR=1988,
ABSTRACT="A pair of IP options that can be used to learn the minimum MTU
of a path through an internet is described, along with its possible
uses. This is a proposal for an Experimental protocol.",
URL="http://www.rfc-editor.org/rfc/rfc1063.txt"
}

@TECHREPORT{rfc1064,
AUTHOR="M. R. Crispin",
TITLE="Interactive Mail Access Protocol: Version 2",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1064,
PAGES=26,
DAYS=15,
MONTH=jul,
YEAR=1988,
ABSTRACT={This memo suggests a method for workstations to dynamically
access mail from a mailbox server ({"}respository{"}). This RFC specifies a
standard for the SUMEX-AIM community and a proposed experimental
protocol for the Internet community. Discussion and suggestions for
improvement are requested.},
URL="http://www.rfc-editor.org/rfc/rfc1064.txt"
}

@TECHREPORT{rfc1065,
AUTHOR="K. McCloghrie and Marshall T. Rose",
TITLE="Structure and identification of management information for {TCP/IP-based}
internets",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1065,
PAGES=21,
DAYS=15,
MONTH=aug,
YEAR=1988,
ABSTRACT="This RFC provides the common definitions for the structure and
identification of management information for TCP/IP-based internets. In
particular, together with its companion memos, which describe the
initial management information base along with the initial network
management protocol, these documents provide a simple, working
architecture and system for managing TCP/IP-based internets and in
particular, the Internet. This memo specifies a draft standard for the
Internet community. TCP/IP implementation in the Internet which are
network manageable are expected to adopt and implement this
specification.",
URL="http://www.rfc-editor.org/rfc/rfc1065.txt"
}

@TECHREPORT{rfc1066,
AUTHOR="K. McCloghrie and Marshall T. Rose",
TITLE="Management Information Base for network management of {TCP/IP-based}
internets",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1066,
PAGES=90,
DAYS=15,
MONTH=aug,
YEAR=1988,
ABSTRACT="This RFC provides the initial version of the Management
Information Base (MIB) for use with network management protocols in
TCP/IP-based internets in the short-term. In particular, together with
its companion memos which describe the structure of management
information along with the initial network management protocol, these
documents provide a simple, workable architecture and system for
managing TCP/IP-based internets, and in particular, the Internet. This
memo specifies a draft standard for the Internet community. TCP/IP
implementations in the Internet which are network manageable are
expected to adopt and implement this specification.",
URL="http://www.rfc-editor.org/rfc/rfc1066.txt"
}

@TECHREPORT{rfc1067,
AUTHOR="J. D. Case and M. S. Fedor and M. L. Schoffstall and J. R. Davin",
TITLE="Simple Network Management Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1067,
PAGES=33,
DAYS=15,
MONTH=aug,
YEAR=1988,
ABSTRACT="This RFC defines a simple protocol by which management
information for a network element may be inspected or altered by
logically remote users. In particular, together with its companion memos
which describe the structure of management information along with the
initial management information base, these documents provide a simple,
workable architecture and system for managing TCP/IP-based internets and
in particular, the Internet. This memo specifies a draft standard for
the Internet community. TCP/IP implementations in the Internet which are
network manageable are expected to adopt and implement this
specification.",
URL="http://www.rfc-editor.org/rfc/rfc1067.txt"
}

@TECHREPORT{rfc1068,
AUTHOR="A. L. DeSchon and R. Braden",
TITLE="Background File Transfer Program {(BFTP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1068,
PAGES=27,
DAYS=15,
MONTH=aug,
YEAR=1988,
ABSTRACT="This RFC describes an Internet background file transfer
service that is built upon the third-party transfer model of FTP. No new
protocols are involved. The purpose of this memo is to stimulate
discussions on new Internet service modes.",
URL="http://www.rfc-editor.org/rfc/rfc1068.txt"
}

@TECHREPORT{rfc1071,
AUTHOR="R. Braden and David A. Borman and C. Partridge",
TITLE="Computing the Internet checksum",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1071,
PAGES=24,
DAYS=15,
MONTH=sep,
YEAR=1988,
ABSTRACT="This RFC summarizes techniques and algorithms for efficiently
computing the Internet checksum. It is not a standard, but a set of
useful implementation techniques.",
URL="http://www.rfc-editor.org/rfc/rfc1071.txt"
}

@TECHREPORT{rfc1072,
AUTHOR="V. Jacobson and R. Braden",
TITLE="{TCP} extensions for long-delay paths",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1072,
PAGES=16,
DAYS=15,
MONTH=oct,
YEAR=1988,
ABSTRACT="This RFC proposes a set of extensions to the TCP protocol to
provide efficient operation over a path with a high bandwidth*delay
product. These extensions are not proposed as an Internet standard at
this time. Instead, they are intended as a basis for further
experimentation and research on transport protocol performance.",
URL="http://www.rfc-editor.org/rfc/rfc1072.txt"
}

@TECHREPORT{rfc1073,
AUTHOR="D. Waitzman",
TITLE="Telnet window size option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1073,
PAGES=4,
DAYS=15,
MONTH=oct,
YEAR=1988,
ABSTRACT="This RFC describes a proposed Telnet option to allow a client
to convey window size to a Telnet server.",
URL="http://www.rfc-editor.org/rfc/rfc1073.txt"
}

@TECHREPORT{rfc1074,
AUTHOR="J. Rekhter",
TITLE="{NSFNET} backbone {SPF} based Interior Gateway Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1074,
PAGES=5,
DAYS=15,
MONTH=oct,
YEAR=1988,
ABSTRACT="This RFC is an implementation description of the standard ANSI
IS-IS and ISO ES-IS routing protocols within the NSFNET backbone
network.",
URL="http://www.rfc-editor.org/rfc/rfc1074.txt"
}

@TECHREPORT{rfc1075,
AUTHOR="D. Waitzman and C. Partridge and S. E. Deering",
TITLE="Distance Vector Multicast Routing Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1075,
PAGES=24,
DAYS=15,
MONTH=nov,
YEAR=1988,
ABSTRACT="This RFC describes a distance-vector-style routing protocol
for routing multicast datagrams through an internet. It is derived from
the Routing Information Protocol (RIP), and implements multicasting as
described in RFC-1054. This is an experimental protocol, and its
implementation is not recommended at this time.",
URL="http://www.rfc-editor.org/rfc/rfc1075.txt"
}

@TECHREPORT{rfc1076,
AUTHOR="G. Trewitt and C. Partridge",
TITLE="{HEMS} monitoring and control language",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1076,
PAGES=42,
DAYS=15,
MONTH=nov,
YEAR=1988,
ABSTRACT="This RFC specifies a query language for monitoring and control
of network entities. This RFC supercedes RFC 1023, extending the query
language and providing more discussion of the underlying issues. This
language is a component of the High-Level Entity Monitoring System
(HEMS) described in RFC 1021 and RFC 1022. Readers may wish to consult
these RFCs when reading this memo. RFC 1024 contains detailed
assignments of numbers and structures used in this system. Portions of
RFC 1024 that define query language structures are superceded by
definitions in this memo. This memo assumes a knowledge of the ISO data
encoding standard, ASN.1.",
URL="http://www.rfc-editor.org/rfc/rfc1076.txt"
}

@TECHREPORT{rfc1077,
AUTHOR="B. M. Leiner",
TITLE="Critical issues in high bandwidth networking",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1077,
PAGES=46,
DAYS=15,
MONTH=nov,
YEAR=1988,
ABSTRACT="This memo presents the results of a working group on High
Bandwidth Networking. This RFC is for your information and you are
encouraged to comment on the issues presented. Use of Gigabit scale
networks include supercomputer imaging, Miltary C2 and sensor data
distribution from space. A Gigabit Network (GN) must support these
services: - Currently Provided Packet Services - Multi-Media Mail -
Multi-Media Conferencing - Computer Generated Real Time Graphics -
High-Speed Transaction Processing - Wide Area Distributed
Database/Knowledge Base Management Systems For a stream or synchronous
service a reservation system is used to set up and guarantee a constant
and steady amount of bandwidth between any two subscribers. For Gigabit
Backbones (GB), LAN speeds should be able to change irrespective of GB
speeds and vice versa. Directory services such as those found in CCITT
X.500/ISO DIS 9594 need to be provided. Usage policy is expressed by a
tariff which is upheld by accounting. Routing policies are enforced by
traffic controls. Trusted and secure communications on GNs is provided
by authentication, integrity, confidentiality, access control, and
nonrepudiation. Speeds of trunks in the next generation networks is
rising faster than the speeds of the switching elements. New designs of
switch are required to handle expensive but large bandwidths without the
switch becoming the bottleneck. Hierarchically designed networks may be
the key to managability in the next generation networks. Reliablity is
needed in future networks and is achieved through the use of
fault-tolerant switches, distributed control with self-correcting
algorithms and the protection of network control traffic. Architecture
of future networks must be divorced from the underlying transmission
technology. There is a heirarchy of progressively more effective network
management techniques: 1) Reactive Problem Management 2) Reactive
Resource Management 3) Proactive Problem Management 4) Proactive
Resource Management To prevent information overflow on human operators,
the system with have to provide increasing amounts of filtering.
thresholding and altering mechanisms. Expert systems capable of early
fault detection, diagnosis and problem resolution will become mandatory
for GNs. High level entities should have a name or logical address that
identifies them independently of location. Multicast should be provided
as a user level service as in RFC1054 for IP. The GN will alsmost
certainly be made up from point to point fibre links that will not
provide broadcast or multicast for free. Open group multicast means that
any host can multicast to the group; closed group multicast means that
only hosts which are members of the group may multicast to the group.
Closed group multicasting is adequate for applications such as
conferencing but open group multicasting is required for more
client-server applications such as file and database servers. TCP places
the checksum in the packet header, forcing the packet to be formed and
read fully before transmission can begin. ISO TP4 is worse than TCP in
that the checksum is in a variable location in the header and thus
hardware implementation is made very difficult. Special purpose
transport protocols can be designed for applications with more stringent
requirements than generic transport protocols (such as TCP and ISO TP4)
can provide. Current special purpose transport protocols include: o UDP
(user datagram protocol) o RDP (reliable datagram protocol) o LDP
(loader/debugger protocol) o NETBLT (high-speed block transfer protocol)
o NVP (network voice protocol) o PVP (packet video protocol) New generic
transport protocols such as VMTP hope to offer a wide range of service
options that help remove the need to resort to special purpose
protocols. New transport protocols should not be over optimised for
current networks and yet must not ignore the fundamental deficiencies of
current protocols. Forward Error Correction (FEC) is useful when the
bandwidth/delay ratio of the physical medium is high (ie photonic
transcontinental or transatlantic links). Operating systems must be
refined to the level of performance required of them for use with a
gigabit/sec network. Decentralised approaches to network management
should be emphasised over centralised systems. Compromising the security
of one part of a GN should not compromise the security of the entire
network. With changes future bandwidth and computing costs and
performance ratios, the trade off between user data and network control
data flows needs to be re-explored. Resource requests made by an
application to the network system must be in real terms desipte the fact
that most operating systems attempt to present a 'virtual world' to the
application level code. A protocol implementation can adapt to changes
in that [lower level] service by tuning its internal mechanisms
(time-outs, retransmission strategies, etc.)''. To minimise the effects
of failures in future networks, the system must reconfigure itself to
adapt to the new network state when a failure occurs. Small messages
(that fit into one RTD such as those generated by most applications
today) will require open-loop controls on flow and congestion. Large
messages (those taking longer than one RTD such as voice or video
streams) will require explicit resource commitment. The speed of light
and queuing delays are the most critical sources of delay faces future
gigabit/sec networks. Depending upon the actual (physical) size of the
network, the application layer programs can expect to experience delays
which differe by several orders of magnitude. The current Internet is
more or less unmanagable and is having problems with network
administrators using one logical subnet address to cover widely
geographically dispersed LANs connected with fibre or satelite links.
Routing can be based on policy (such as access rights) instead of simply
minimising some 'cost' such as delay. Connectionless protocols make
imposing a policy difficult and increase processing overhead, especially
at gateways, as no state is kept and policy decisions must be made for
every packet. Variables which can be taken into account in policy based
routing include: o Classes of users (ie large, small, commerical,
governmental, academic, etc), o) Classes of Service (what quality is
required), o) Time varying (on or off peak transmission), o) Volume
(discount and surcharges), o) Access charges (per port or bandwidth of
the ports in use), o) Distance (circuit miles, as the crow flies, number
of hops). A list of 'current' (as of November 1988) research efforts in
the USA is given.",
URL="http://www.rfc-editor.org/rfc/rfc1077.txt"
}

@TECHREPORT{rfc1078,
AUTHOR="M. Lottor",
TITLE="{TCP} port service Multiplexer {(TCPMUX)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1078,
PAGES=2,
DAYS=15,
MONTH=nov,
YEAR=1988,
ABSTRACT="This RFC proposes an Internet standard which can be used by
future TCP services instead of using 'well-known ports'.",
URL="http://www.rfc-editor.org/rfc/rfc1078.txt"
}

@TECHREPORT{rfc1079,
AUTHOR="C. Hedrick",
TITLE="Telnet terminal speed option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1079,
PAGES=3,
DAYS=15,
MONTH=dec,
YEAR=1988,
ABSTRACT="This RFC specifies a standard for the Internet community.
Hosts on the Internet that exchange terminal speed information within
the Telnet protocol are expected to adopt and implement this standard.",
URL="http://www.rfc-editor.org/rfc/rfc1079.txt"
}

@TECHREPORT{rfc1080,
AUTHOR="C. Hedrick",
TITLE="Telnet remote flow control option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1080,
PAGES=4,
DAYS=15,
MONTH=nov,
YEAR=1988,
ABSTRACT="This RFC specifies a standard for the Internet community.
Hosts on the Internet that do remote flow control within the Telnet
protocol are expected to adopt and implement this standard.",
URL="http://www.rfc-editor.org/rfc/rfc1080.txt"
}

@TECHREPORT{rfc1081,
AUTHOR="Marshall T. Rose",
TITLE="Post Office Protocol: Version 3",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1081,
PAGES=16,
DAYS=15,
MONTH=nov,
YEAR=1988,
ABSTRACT="This memo suggests a simple method for workstations to
dynamically access mail from a mailbox server. This RFC specifies a
proposed protocol for the Internet community, and requests discussion
and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc1081.txt"
}

@TECHREPORT{rfc1082,
AUTHOR="Marshall T. Rose",
TITLE="Post Office Protocol: Version {3:} Extended service offerings",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1082,
PAGES=11,
DAYS=15,
MONTH=nov,
YEAR=1988,
ABSTRACT="This memo suggests a simple method for workstations to
dynamically access mail from a discussion group server, as an extension
to an earlier memo which dealt with dynamically accessing mail from a
mailbox server using the Post Office Protocol - Version 3 (POP3). This
RFC specifies a proposed protocol for the Internet community, and
requests discussion and suggestions for improvements. All of the
extensions described in this memo to the POP3 are OPTIONAL.",
URL="http://www.rfc-editor.org/rfc/rfc1082.txt"
}

@TECHREPORT{rfc1083,
AUTHOR="  and Internet Activities Board",
TITLE="{IAB} official protocol standards",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1083,
PAGES=12,
DAYS=15,
MONTH=dec,
YEAR=1988,
ABSTRACT="This memo describes the state of standardization of protocols
used in the Internet as determined by the Internet Activities Board
(IAB). An overview of the standards procedures is presented first,
followed by discussions of the standardization process and the RFC
document series, then the explanation of the terms is presented, the
lists of protocols in each stage of standardization follows, and finally
pointers to references and contacts for further information. This memo
is issued quarterly, please be sure the copy you are reading is dated
within the last three months.",
URL="http://www.rfc-editor.org/rfc/rfc1083.txt"
}

@TECHREPORT{rfc1085,
AUTHOR="Marshall T. Rose",
TITLE="{ISO} presentation services on top of {TCP/IP} based internets",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1085,
PAGES=32,
DAYS=15,
MONTH=dec,
YEAR=1988,
ABSTRACT={RFC 1006 describes a mechanism for providing the ISO transport
service on top of TCP/IP. Once this method is applied, one may implement
{"}real{"} ISO applications on top of TCP/IP-based internets, by simply
implementing OSI session, presentation, and application services on top
of the transport service access point which is provided on top of the
TCP. Although straight-forward, there are some environments in which the
richness provided by the OSI application layer is desired, but it is
nonetheless impractical to implement the underlying OSI infrastructure
(i.e., the presentation, session, and transport services on top of the
TCP). This memo describes an approach for providing {"}stream-lined{"}
support of OSI application services on top of TCP/IP-based internets for
such constrained environments. This memo proposes a standard for the
Internet community.},
URL="http://www.rfc-editor.org/rfc/rfc1085.txt"
}

@TECHREPORT{rfc1086,
AUTHOR="Julian P. Onions and Marshall T. Rose",
TITLE="{ISO-TP0} bridge between {TCP} and {X.25}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1086,
PAGES=9,
DAYS=15,
MONTH=dec,
YEAR=1988,
ABSTRACT="This memo proposes a standard for the Internet community.
Hosts on the Internet that choose to implement ISO TP0 transport
connectivity between TCP and X.25 based hosts are expected to experiment
with this proposal. TCP port 146 is reserved for this proposal.",
URL="http://www.rfc-editor.org/rfc/rfc1086.txt"
}

@TECHREPORT{rfc1069,
AUTHOR="R. Callon and H. Braun",
TITLE="Guidelines for the use of {Internet-IP} addresses in the {ISO}
{Connectionless-Mode} Network Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1069,
PAGES=10,
DAYS=15,
MONTH=feb,
YEAR=1989,
ABSTRACT={This RFC suggests an addressing scheme for use with the ISO
Connectionless Network Protocol (CLNP) in the Internet. This is a
solution to one of the problems inherent in the use of {"}ISO-grams{"} in
the Internet. This memo is a revision of RFC 986. This RFC suggests a
proposed protocol for the Internet community, and requests discussion
and suggestions for improvements.},
URL="http://www.rfc-editor.org/rfc/rfc1069.txt"
}

@TECHREPORT{rfc1070,
AUTHOR="R. A. Hagens and N. E. Hall and Marshall T. Rose",
TITLE="Use of the Internet as a subnetwork for experimentation with the {OSI}
network layer",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1070,
PAGES=17,
DAYS=15,
MONTH=feb,
YEAR=1989,
ABSTRACT="This RFC proposes a scenario for experimentation with the
International Organization for Standardization (ISO) Open Systems
Interconnection (OSI) network layer protocols over the Internet and
requests discussion and suggestions for improvements to this scenario.
This RFC also proposes the creation of an experimental OSI internet. To
participate in the experimental OSI internet, a system must abide by the
agreements set forth in this RFC.",
URL="http://www.rfc-editor.org/rfc/rfc1070.txt"
}

@TECHREPORT{rfc1087,
AUTHOR="  and Internet Activities Board",
TITLE="Ethics and the Internet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1087,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1989,
ABSTRACT="This memo is a statement of policy by the Internet Activities
Board (IAB) concerning the proper use of the resources of the Internet.",
URL="http://www.rfc-editor.org/rfc/rfc1087.txt"
}

@TECHREPORT{rfc1088,
AUTHOR="L. J. McLaughlin",
TITLE="Standard for the transmission of {IP} datagrams over {NetBIOS} networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1088,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1989,
ABSTRACT="This document specifies a standard method of encapsulating the
Internet Protocol (IP) datagrams on NetBIOS networks.",
URL="http://www.rfc-editor.org/rfc/rfc1088.txt"
}

@TECHREPORT{rfc1089,
AUTHOR="M. L. Schoffstall and C. Davin and M. S. Fedor and J. D. Case",
TITLE="{SNMP} over Ethernet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1089,
PAGES=3,
DAYS=15,
MONTH=feb,
YEAR=1989,
ABSTRACT="This memo describes an experimental method by which the Simple
Network Management Protocol (SNMP) can be used over Ethernet MAC layer
framing instead of the Internet UDP/IP protocol stack. This
specification is useful for LAN based network elements that support no
higher layer protocols beyond the MAC sub-layer.",
URL="http://www.rfc-editor.org/rfc/rfc1089.txt"
}

@TECHREPORT{rfc1090,
AUTHOR="R. Ullmann",
TITLE="{SMTP} on {X.25}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1090,
PAGES=4,
DAYS=15,
MONTH=feb,
YEAR=1989,
ABSTRACT="This memo proposes a standard for SMTP on the virtual circuit
facility provided by the X.25 standard of the CCITT.",
URL="http://www.rfc-editor.org/rfc/rfc1090.txt"
}

@TECHREPORT{rfc1091,
AUTHOR="J. VanBokkelen",
TITLE="Telnet terminal-type option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1091,
PAGES=7,
DAYS=15,
MONTH=feb,
YEAR=1989,
ABSTRACT="This RFC specifies a standard for the Internet community.
Hosts on the Internet that exchange terminal type information within the
Telnet protocol are expected to adopt and implement this standard. This
standard supersedes RFC 930. A change is made to permit cycling through
a list of possible terminal types and selecting the most appropriate",
URL="http://www.rfc-editor.org/rfc/rfc1091.txt"
}

@TECHREPORT{rfc1092,
AUTHOR="J. Rekhter",
TITLE="{EGP} and policy based routing in the new {NSFNET} backbone",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1092,
PAGES=5,
DAYS=15,
MONTH=feb,
YEAR=1989,
ABSTRACT="This memo discusses implementation decisions for routing
issues in the NSFNET, especially in the NSFNET Backbone. Of special
concern is the restriction of routing information to advertize the best
route as established by a policy decision.",
URL="http://www.rfc-editor.org/rfc/rfc1092.txt"
}

@TECHREPORT{rfc1093,
AUTHOR="H. Braun",
TITLE="{NSFNET} routing architecture",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1093,
PAGES=9,
DAYS=15,
MONTH=feb,
YEAR=1989,
ABSTRACT="This document describes the routing architecture for the
NSFNET centered around the new NSFNET Backbone, with specific emphasis
on the interface between the backbone and its attached networks.",
URL="http://www.rfc-editor.org/rfc/rfc1093.txt"
}

@TECHREPORT{rfc1094,
AUTHOR=" {Sun Microsystems}",
TITLE="{NFS:} Network File System Protocol specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1094,
PAGES=27,
DAYS=15,
MONTH=mar,
YEAR=1989,
ABSTRACT="This RFC describes a protocol that Sun Microsystems, Inc., and
others are using. A new version of the protocol is under development,
but others may benefit from the descriptions of the current protocol,
and discussion of some of the design issues.",
URL="http://www.rfc-editor.org/rfc/rfc1094.txt"
}

@TECHREPORT{rfc1095,
AUTHOR="U. Warrier and L. Besaw",
TITLE="Common Management Information Services and Protocol over {TCP/IP} {(CMOT)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1095,
PAGES=67,
DAYS=15,
MONTH=apr,
YEAR=1989,
ABSTRACT="This memo defines a network management architecture that uses
the International Organization for Standardization's (ISO) Common
Management Information Services/Common Management Information Protocol
(CMIS/CMIP) in a TCP/IP environment. This architecture provides a means
by which control and monitoring information can be exchanged between a
manager and a remote network element. In particular, this memo defines
the means for implementing the Draft International Standard (DIS)
version of CMIS/CMIP on top of Internet transport protocols for the
purpose of carrying management information defined in the
Internet-standard management information base. DIS CMIS/CMIP is suitable
for deployment in TCP/IP networks while CMIS/CMIP moves toward becoming
an International Standard. Together with the relevant ISO standards and
the companion RFCs that describe the initial structure of management
information and management information base, these documents provide the
basis for a comprehensive architecture and system for managing TCP/IP-
based internets, and in particular the Internet.",
URL="http://www.rfc-editor.org/rfc/rfc1095.txt"
}

@TECHREPORT{rfc1096,
AUTHOR="G. A. Marcy",
TITLE="Telnet X display location option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1096,
PAGES=3,
DAYS=15,
MONTH=mar,
YEAR=1989,
ABSTRACT="This RFC specifies a standard for the Internet community.
Hosts on the Internet that transmit the X display location within the
Telnet protocol are expected to adopt and implement this standard.",
URL="http://www.rfc-editor.org/rfc/rfc1096.txt"
}

@TECHREPORT{rfc1097,
AUTHOR="B. I. Miller",
TITLE="Telnet subliminal-message option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1097,
PAGES=3,
DAYS=15,
MONTH=apr,
YEAR=1989,
ABSTRACT="This RFC specifies a standard for the Internet community.
Hosts on the Internet that display subliminal messages within the Telnet
protocol are expected to adopt and implement this standard.",
URL="http://www.rfc-editor.org/rfc/rfc1097.txt"
}

@TECHREPORT{rfc1098,
AUTHOR="J. D. Case and M. S. Fedor and M. L. Schoffstall and C. Davin",
TITLE="Simple Network Management Protocol {(SNMP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1098,
PAGES=34,
DAYS=15,
MONTH=apr,
YEAR=1989,
ABSTRACT={This RFC is a re-release of RFC 1067, with a changed {"}Status
of this Memo{"} section. This memo defines a simple protocol by which
management information for a network element may be inspected or altered
by logically remote users. In particular, together with its companion
memos which describe the structure of management information along with
the initial management information base, these documents provide a
simple, workable architecture and system for managing TCP/IP-based
internets and in particular the Internet.},
URL="http://www.rfc-editor.org/rfc/rfc1098.txt"
}

@TECHREPORT{rfc1100,
AUTHOR="Editor J. Postel",
TITLE="{IAB} official protocol standards",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1100,
PAGES=14,
DAYS=15,
MONTH=apr,
YEAR=1989,
ABSTRACT="This memo describes the state of standardization of protocols
used in the Internet as determined by the Internet Activities Board
(IAB). An overview of the standards procedures is presented first,
followed by discussions of the standardization process and the RFC
document series, then the explanation of the terms is presented, the
lists of protocols in each stage of standardization follows, and finally
pointers to references and contacts for further information. This memo
is issued quarterly, please be sure the copy you are reading is dated
within the last three months. Current copies may be obtained from the
Network Information Center or from the Internet Assigned Numbers
Authority (see the contact information at the end of this memo). Do not
use this memo after 31-July-89.",
URL="http://www.rfc-editor.org/rfc/rfc1100.txt"
}

@TECHREPORT{rfc1101,
AUTHOR="P. V. Mockapetris",
TITLE="{DNS} encoding of network names and other types",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1101,
PAGES=14,
DAYS=15,
MONTH=apr,
YEAR=1989,
ABSTRACT="This RFC proposes two extensions to the Domain Name System: 1)
A specific method for entering and retrieving RRs which map between
network names and numbers. 2) Ideas for a general method for describing
mappings between arbitrary identifiers and numbers. The method for
mapping between network names and addresses is a proposed standard, the
ideas for a general method are experimental.",
URL="http://www.rfc-editor.org/rfc/rfc1101.txt"
}

@TECHREPORT{rfc1102,
AUTHOR="D. D. Clark",
TITLE="Policy routing in Internet protocols",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1102,
PAGES=22,
DAYS=15,
MONTH=may,
YEAR=1989,
ABSTRACT="The purpose of this RFC is to focus discussion on particular
problems in the Internet and possible methods of solution. No proposed
solutions in this document are intended as standards for the Internet.",
URL="http://www.rfc-editor.org/rfc/rfc1102.txt"
}

@TECHREPORT{rfc1103,
AUTHOR="D. Katz",
TITLE="Proposed standard for the transmission of {IP} datagrams over {FDDI}
Networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1103,
PAGES=9,
DAYS=15,
MONTH=jun,
YEAR=1989,
ABSTRACT="This RFC specifies a method of encapsulating the Internet
Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests
and replies on Fiber Distributed Data Interface (FDDI) Networks.",
URL="http://www.rfc-editor.org/rfc/rfc1103.txt"
}

@TECHREPORT{rfc1104,
AUTHOR="H. Braun",
TITLE="Models of policy based routing",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1104,
PAGES=10,
DAYS=15,
MONTH=jun,
YEAR=1989,
ABSTRACT="The purpose of this RFC is to outline a variety of models for
policy based routing. The relative benefits of the different approaches
are reviewed. Discussions and comments are explicitly encouraged to move
toward the best policy based routing model that scales well within a
large internetworking environment.",
URL="http://www.rfc-editor.org/rfc/rfc1104.txt"
}

@TECHREPORT{rfc1105,
AUTHOR="K. Lougheed and Y. Rekhter",
TITLE="Border Gateway Protocol {(BGP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1105,
PAGES=17,
DAYS=15,
MONTH=jun,
YEAR=1989,
ABSTRACT="This RFC outlines a specific approach for the exchange of
network reachability information between Autonomous Systems. Updated by
RFCs 1163 and 1164.",
URL="http://www.rfc-editor.org/rfc/rfc1105.txt"
}

@TECHREPORT{rfc1106,
AUTHOR="R. Fox",
TITLE="{TCP} big window and {NAK} options",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1106,
PAGES=13,
DAYS=15,
MONTH=jun,
YEAR=1989,
ABSTRACT="This memo discusses two extensions to the TCP protocol to
provide a more efficient operation over a network with a high
bandwidth*delay product. The extensions described in this document have
been implemented and shown to work using resources at NASA. This memo
describes an Experimental Protocol, these extensions are not proposed as
an Internet standard, but as a starting point for further research.",
URL="http://www.rfc-editor.org/rfc/rfc1106.txt"
}

@TECHREPORT{rfc1107,
AUTHOR="Karen Sollins",
TITLE="Plan for Internet directory services",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1107,
PAGES=19,
DAYS=15,
MONTH=jul,
YEAR=1989,
ABSTRACT="This memo proposes a program to develop a directory service
for the Internet. It reports the results of a meeting held in February
1989, which was convened to review requirements and options for such a
service. This proposal is offered for comment, and does not represent a
committed research activity of the Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc1107.txt"
}

@TECHREPORT{rfc1109,
AUTHOR="V. G. Cerf",
TITLE="Report of the second Ad Hoc Network Management Review Group",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1109,
PAGES=8,
DAYS=15,
MONTH=aug,
YEAR=1989,
ABSTRACT="This RFC reports an official Internet Activities Board (IAB)
policy position on the treatment of Network Management in the Internet.
This RFC presents the results and recommendations of the second Ad Hoc
Network Management Review on June 12, 1989. The results of the first
such meeting were reported in RFC 1052.",
URL="http://www.rfc-editor.org/rfc/rfc1109.txt"
}

@TECHREPORT{rfc1110,
AUTHOR="A. A. McKenzie",
TITLE="Problem with the {TCP} big window option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1110,
PAGES=3,
DAYS=15,
MONTH=aug,
YEAR=1989,
ABSTRACT="This memo comments on the TCP Big Window option described in
RFC 1106.",
URL="http://www.rfc-editor.org/rfc/rfc1110.txt"
}

@TECHREPORT{rfc1111,
AUTHOR="J. B. Postel",
TITLE="Request for comments on Request for Comments: Instructions to {RFC} authors",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1111,
PAGES=6,
DAYS=15,
MONTH=aug,
YEAR=1989,
ABSTRACT="This RFC specifies a standard for the Internet community.
Authors of RFCs are expected to adopt and implement this standard.",
URL="http://www.rfc-editor.org/rfc/rfc1111.txt"
}

@TECHREPORT{rfc1112,
AUTHOR="S. E. Deering",
TITLE="Host extensions for {IP} multicasting",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1112,
PAGES=17,
DAYS=15,
MONTH=aug,
YEAR=1989,
ABSTRACT="This memo specifies the extensions required of a host
implementation of the Internet Protocol (IP) to support multicasting.
Recommended procedure for IP multicasting in the Internet. This RFC
obsoletes RFCs 998 and 1054.",
URL="http://www.rfc-editor.org/rfc/rfc1112.txt"
}

@TECHREPORT{rfc1113,
AUTHOR="J. R. Linn",
TITLE="Privacy enhancement for Internet electronic mail: Part I - message
encipherment and authentication procedures",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1113,
PAGES=34,
DAYS=15,
MONTH=aug,
YEAR=1989,
ABSTRACT="This RFC specifies features for private electronic mail based
on encryption technology.",
URL="http://www.rfc-editor.org/rfc/rfc1113.txt"
}

@TECHREPORT{rfc1114,
AUTHOR="Stephen T. Kent and J. R. Linn",
TITLE="Privacy enhancement for Internet electronic mail: Part {II} -
certificate-based key management",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1114,
PAGES=25,
DAYS=15,
MONTH=aug,
YEAR=1989,
ABSTRACT="This RFC specifies the key management aspects of Privacy
Enhanced Mail.",
URL="http://www.rfc-editor.org/rfc/rfc1114.txt"
}

@TECHREPORT{rfc1115,
AUTHOR="J. R. Linn",
TITLE="Privacy enhancement for Internet electronic mail: Part {III} - algorithms,
modes, and identifiers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1115,
PAGES=8,
DAYS=15,
MONTH=aug,
YEAR=1989,
ABSTRACT="This RFC provides definitions, references, and citations for
algorithms, usage modes, and associated identifiers used in RFC-1113 and
RFC-1114 in support of privacy-enhanced electronic mail.",
URL="http://www.rfc-editor.org/rfc/rfc1115.txt"
}

@TECHREPORT{rfc1116,
AUTHOR="David A. Borman",
TITLE="Telnet Linemode option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1116,
PAGES=21,
DAYS=15,
MONTH=aug,
YEAR=1989,
ABSTRACT="Hosts on the Internet that support Linemode within the Telnet
protocol are expected to adopt and implement this protocol. Obsoleted by
RFC 1184.",
URL="http://www.rfc-editor.org/rfc/rfc1116.txt"
}

@TECHREPORT{rfc1117,
AUTHOR="S. Romano and Mary K. Stahl and M. Recker",
TITLE="Internet numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1117,
PAGES=109,
DAYS=15,
MONTH=aug,
YEAR=1989,
ABSTRACT="This memo is an official status report on the network numbers
and the autonomous system numbers used in the Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc1117.txt"
}

@TECHREPORT{rfc1118,
AUTHOR="E. Krol",
TITLE="Hitchhikers guide to the Internet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1118,
PAGES=24,
DAYS=15,
MONTH=sep,
YEAR=1989,
ABSTRACT={This RFC is being distributed to members of the Internet
community in order to make available some {"}hints{"} which will allow new
network participants to understand how the direction of the Internet is
set, how to acquire online information and how to be a good Internet
neighbor. While the information discussed may not be relevant to the
research problems of the Internet, it may be interesting to a number of
researchers and implementors. No standards are defined or specified in
this memo.},
URL="http://www.rfc-editor.org/rfc/rfc1118.txt"
}

@TECHREPORT{rfc1119,
AUTHOR="D. L. Mills",
TITLE="Network Time Protocol (version {2)} specification and implementation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1119,
DAYS=15,
MONTH=sep,
YEAR=1989,
ABSTRACT="This document describes the Network Time Protocol (NTP),
specifies its formal structure and summarizes information useful for its
implementation. NTP provides the mechanisms to synchronize time and
coordinate time distribution in a large, diverse internet operating at
rates from mundane to lightwave. It uses a returnable-time design in
which a distributed subnet of time servers operating in a self-
organizing, hierarchical-master-slave configuration synchronizes local
clocks within the subnet and to national time standards via wire or
radio. The servers can also redistribute reference time via local
routing algorithms and time daemons.",
URL="http://www.rfc-editor.org/rfc/rfc1119.txt"
}

@TECHREPORT{rfc1120,
AUTHOR="V. G. Cerf",
TITLE="Internet Activities Board",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1120,
PAGES=11,
DAYS=15,
MONTH=sep,
YEAR=1989,
ABSTRACT="This RFC provides a history and description of the Internet
Activities Board (IAB) and its subsidiary organizations. This memo is
for informational use and does not constitute a standard.",
URL="http://www.rfc-editor.org/rfc/rfc1120.txt"
}

@TECHREPORT{rfc1121,
AUTHOR="J. B. Postel and L. Kleinrock and V. G. Cerf and B. W. Boehm",
TITLE="Act one - the poems",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1121,
PAGES=6,
DAYS=15,
MONTH=sep,
YEAR=1989,
ABSTRACT={This RFC presents a collection of poems that were presented at
{"}Act One{"}, a symposium held partially in celebration of the 20th
anniversary of the ARPANET.},
URL="http://www.rfc-editor.org/rfc/rfc1121.txt"
}

@TECHREPORT{rfc1122,
EDITOR="R. Braden",
TITLE="Requirements for Internet Hosts - Communication Layers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1122,
PAGES=116,
DAYS=15,
MONTH=oct,
YEAR=1989,
ABSTRACT="This RFC is an official specification for the Internet
community. It incorporates by reference, amends, corrects, and
supplements the primary protocol standards documents relating to hosts.",
URL="http://www.rfc-editor.org/rfc/rfc1122.txt"
}

@TECHREPORT{rfc1123,
EDITOR="R. Braden",
TITLE="Requirements for Internet Hosts - Application and Support",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1123,
PAGES=98,
DAYS=15,
MONTH=oct,
YEAR=1989,
ABSTRACT="This RFC is an official specification for the Internet
community. It incorporates by reference, amends, corrects, and
supplements the primary protocol standards documents relating to hosts.",
URL="http://www.rfc-editor.org/rfc/rfc1123.txt"
}

@TECHREPORT{rfc1124,
AUTHOR="B. M. Leiner",
TITLE="Policy issues in interconnecting networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1124,
DAYS=15,
MONTH=sep,
YEAR=1989,
ABSTRACT="To support the activities of the Federal Research Internet
Coordinating Committee (FRICC) in creating an interconnected set of
networks to serve the research community, two workshops were held to
address the technical support of policy issues that arise when
interconnecting such networks. Held under the suspices of the Internet
Activities Board at the request of the FRICC, and sponsored by NASA
through RIACS, the workshops addressed the required and feasible
technologies and architectures that could be used to satisfy the desired
policies for interconnection. The purpose of this RFC is to report the
results of these workshops.",
URL="http://www.rfc-editor.org/rfc/rfc1124.txt"
}

@TECHREPORT{rfc1125,
AUTHOR="D. Estrin",
TITLE="Policy requirements for inter Administrative Domain routing",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1125,
PAGES=21,
DAYS=15,
MONTH=nov,
YEAR=1989,
ABSTRACT="The purpose of this memo is to focus discussion on particular
problems in the Internet and possible methods of solution. No proposed
solutions in this document are intended as standards for the Internet.
Rather, it is hoped that a general consensus will emerge as to the
appropriate solution to such problems, leading eventually to the
development and adoption of standards.",
URL="http://www.rfc-editor.org/rfc/rfc1125.txt"
}

@TECHREPORT{rfc1126,
AUTHOR="M. Little",
TITLE="Goals and functional requirements for inter-autonomous system routing",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1126,
PAGES=25,
DAYS=15,
MONTH=oct,
YEAR=1989,
ABSTRACT="This document describes the functional requirements for a
routing protocol to be used between autonomous systems. This document is
intended as a necessary precursor to the design of a new inter-
autonomous system routing protocol and specifies requirements for the
Internet applicable for use with the current DoD IP, the ISO IP, and
future Internet Protocols. It is intended that these requirements will
form the basis for the future development of a new inter-autonomous
systems routing architecture and protocol. This memo does not specify a
standard.",
URL="http://www.rfc-editor.org/rfc/rfc1126.txt"
}

@TECHREPORT{rfc1127,
AUTHOR="R. Braden",
TITLE="Perspective on the Host Requirements {RFCs}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1127,
PAGES=20,
DAYS=15,
MONTH=oct,
YEAR=1989,
ABSTRACT="This RFC is for information only; it does not constitute a
standard, draft standard, or proposed standard, and it does not define a
protocol.",
URL="http://www.rfc-editor.org/rfc/rfc1127.txt"
}

@TECHREPORT{rfc1128,
AUTHOR="D. L. Mills",
TITLE="Measured performance of the Network Time Protocol in the Internet system",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1128,
DAYS=15,
MONTH=oct,
YEAR=1989,
ABSTRACT="This paper describes a series of experiments involving over
100,000 hosts of the Internet system and located in the U.S., Europe and
the Pacific. The experiments are designed to evaluate the availability,
accuracy and reliability of international standard time distribution
using the DARPA/NSF Internet and the Network Time Protocol (NTP), which
is specified in RFC-1119. NTP is designed specifically for use in a
large, diverse internet system operating at speeds from mundane to
lightwave. In NTP a distributed subnet of time servers operating in a
self-organizing, hierarchical, master-slave configuration exchange
precision timestamps in order to synchronize subnet clocks to each other
and national time standards via wire or radio. The experiments are
designed to locate Internet hosts and gateways that provide time by one
of three time distribution protocols and evaluate the accuracy of their
indications. For those hosts that support NTP, the experiments determine
the distribution of errors and other statistics over paths spanning
major portions of the globe. Finally, the experiments evaluate the
accuracy and reliability of precision timekeeping using NTP and typical
Internet paths involving DARPA, NSFNET and other agency networks. The
experiments demonstrate that timekeeping accuracy throughout most
portions of the Internet can be ordinarily maintained to within a few
tens of milliseconds, even in cases of failure or disruption of clocks,
time servers or networks. This memo does not specify a standard.",
URL="http://www.rfc-editor.org/rfc/rfc1128.txt"
}

@TECHREPORT{rfc1129,
AUTHOR="D. L. Mills",
TITLE="Internet Time Synchronization: The Network Time Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1129,
DAYS=15,
MONTH=oct,
YEAR=1989,
ABSTRACT="This memo describes the Network Time Protocol (NTP) designed
to distribute time information in a large, diverse internet system
operating at speeds from mundane to lightwave. It uses a returnable-
time architecture in which a distributed subnet of time servers
operating in a self-organizing, hierarchical, master-slave configuration
synchronizes local clocks within the subnet and to national time
standards via wire or radio. The servers can also redistribute time
information within a network via local routing algorithms and time
daemons. The architectures, algorithms and protocols which have evolved
to NTP over several years of implementation and refinement are described
in this paper. The synchronization subnet which has been in regular
operation in the Internet for the last several years is described along
with performance data which shows that timekeeping accuracy throughout
most portions of the Internet can be ordinarily maintained to within a
few tens of milliseconds, even in cases of failure or disruption of
clocks, time servers or networks. This memo describes the Network Time
Protocol in RFC-1119.",
URL="http://www.rfc-editor.org/rfc/rfc1129.txt"
}

@TECHREPORT{rfc1131,
AUTHOR="J. Moy",
TITLE="{OSPF} specification",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1131,
DAYS=15,
MONTH=oct,
YEAR=1989,
ABSTRACT="This RFC is the specification of the Open Shortest Path First
(OSPF) Internet routing protocol. OSPF is in the class of Internal
Gateway Protocols (IGPs) for distributing routing information between
gateways of a single Autonomous System. This routing protocol is based
on the link-state approach (in contrast to the distance-vector
approach). This specification was developed by the OSPF Working Group of
the Internet Engineering Task Force.",
URL="http://www.rfc-editor.org/rfc/rfc1131.txt"
}

@TECHREPORT{rfc1132,
AUTHOR="L. J. McLaughlin",
TITLE="Standard for the transmission of {802.2} packets over {IPX} networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1132,
PAGES=4,
DAYS=15,
MONTH=nov,
YEAR=1989,
ABSTRACT="This document specifies a standard method of encapsulating
802.2 packets on networks supporting Novell's Internet Packet Exchange
Protocol (IPX). It obsoletes earlier documents detailing the
transmission of Internet packets over IPX networks. It differs from
these earlier documents in that it allows for the transmission of
multiple network protocols over IPX and for the transmission of packets
through IPX bridges.",
URL="http://www.rfc-editor.org/rfc/rfc1132.txt"
}

@TECHREPORT{rfc1133,
AUTHOR="Jiunn-Hwa. Yu and H. Braun",
TITLE="Routing between the {NSFNET} and the {DDN}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1133,
PAGES=10,
DAYS=15,
MONTH=nov,
YEAR=1989,
ABSTRACT="This document is a case study of the implementation of routing
between the NSFNET and the DDN components (the MILNET and the ARPANET).
We hope that it can be used to expand towards interconnection of other
Administrative Domains. We would welcome discussion and suggestions
about the methods employed for the interconnections. No standards are
specified in this memo.",
URL="http://www.rfc-editor.org/rfc/rfc1133.txt"
}

@TECHREPORT{rfc1134,
AUTHOR="D. Perkins",
TITLE="{Point-to-Point} Protocol: A proposal for multi-protocol transmission of
datagrams over {Point-to-Point} links",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1134,
PAGES=38,
DAYS=15,
MONTH=nov,
YEAR=1989,
ABSTRACT="This proposal is the product of the Point-to-Point Protocol
Working Group of the Internet Engineering Task Force (IETF). Comments on
this memo should be submitted to the IETF Point-to-Point Protocol
Working Group chair by January 15, 1990. Comments will be reviewed at
the February 1990 IETF meeting, with the goal of advancing PPP to draft
standard status.",
URL="http://www.rfc-editor.org/rfc/rfc1134.txt"
}

@TECHREPORT{rfc1135,
AUTHOR="J. F. Reynolds",
TITLE="Helminthiasis of the Internet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1135,
PAGES=33,
DAYS=15,
MONTH=dec,
YEAR=1989,
ABSTRACT="This memo takes a look back at the helminthiasis (infestation
with, or disease caused by parasitic worms) of the Internet that was
unleashed the evening of 2 November 1988. This RFC provides information
about an event that occurred in the life of the Internet. This memo does
not specify any standard. This document provides a glimpse at the
infection, its festering, and cure. The impact of the worm on the
Internet community, ethics statements, the role of the news media, crime
in the computer world, and future prevention is discussed. A
documentation review presents four publications that describe in detail
this particular parasitic computer program. Reference and bibliography
sections are also included.",
URL="http://www.rfc-editor.org/rfc/rfc1135.txt"
}

@TECHREPORT{rfc1136,
AUTHOR="S. Hares and D. Katz",
TITLE="Administrative Domains and Routing Domains: A model for routing in the
Internet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1136,
PAGES=10,
DAYS=15,
MONTH=dec,
YEAR=1989,
ABSTRACT={This RFC proposes a model for describing routing within the
Internet. The model is an adaptation of the {"}OSI Routeing Framework{"}.
This memo does not specify an Internet standard.},
URL="http://www.rfc-editor.org/rfc/rfc1136.txt"
}

@TECHREPORT{rfc1137,
AUTHOR="S. E. Kille",
TITLE="Mapping between full {RFC} 822 and {RFC} 822 with restricted encoding",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1137,
PAGES=3,
DAYS=15,
MONTH=dec,
YEAR=1989,
ABSTRACT="This RFC suggests an electronic mail protocol mapping for the
Internet community and UK Academic Community, and requests discussion
and suggestions for improvements. This memo does not specify an Internet
standard.",
URL="http://www.rfc-editor.org/rfc/rfc1137.txt"
}

@TECHREPORT{rfc1138,
AUTHOR="S. E. Kille",
TITLE="Mapping between {X.400(1988)} / {ISO} 10021 and {RFC} 822",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1138,
PAGES=92,
DAYS=15,
MONTH=dec,
YEAR=1989,
ABSTRACT="Ths RFC suggests an electronic mail protocol mapping for the
Internet community and UK Academic Community, and requests discussion
and suggestions for improvements. This memo does not specify an Internet
standard. This memo updates RFCs 822, 987, and 1026.",
URL="http://www.rfc-editor.org/rfc/rfc1138.txt"
}

@TECHREPORT{rfc1060,
AUTHOR="J. F. Reynolds and J. B. Postel",
TITLE="Assigned numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1060,
PAGES=86,
DAYS=15,
MONTH=mar,
YEAR=1990,
ABSTRACT="This memo is a status report on the parameters (i.e., numbers
and keywords) used in protocols in the Internet community. Distribution
of this memo is unlimited.",
URL="http://www.rfc-editor.org/rfc/rfc1060.txt"
}

@TECHREPORT{rfc1139,
AUTHOR="R. A. Hagens",
TITLE="Echo function for {ISO} 8473",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1139,
PAGES=6,
DAYS=15,
MONTH=jan,
YEAR=1990,
ABSTRACT="This memo defines an echo function for the connection-less
network layer protocol. Two mechanisms are introduced that may be used
to implement the echo function. The first mechanism is recommended as an
interim solution for the Internet community. The second mechanism will
be progressed to the ANSI X3S3.3 working group for consideration as a
work item. When an ISO standard is adopted that provides functionality
similar to that described by this memo, then this memo will become
obsolete and superceded by the ISO standard. This memo is not intended
to compete with an ISO standard.",
URL="http://www.rfc-editor.org/rfc/rfc1139.txt"
}

@TECHREPORT{rfc1140,
AUTHOR="  and Internet Activities Board",
TITLE="{IAB} official protocol standards",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1140,
PAGES=27,
DAYS=15,
MONTH=may,
YEAR=1990,
ABSTRACT="This memo describes the state of standardization of protocols
used in the Internet as determined by the Internet Activities Board
(IAB). This memo is issued quarterly, please be sure the copy you are
reading is dated within the last three months. Current copies may be
obtained from the Network Information Center or from the Internet
Assigned Numbers Authority. Do not use this edition after 31-Aug-90.",
URL="http://www.rfc-editor.org/rfc/rfc1140.txt"
}

@TECHREPORT{rfc1141,
AUTHOR="T. Mallory and A. Kullberg",
TITLE="Incremental updating of the Internet checksum",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1141,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1990,
ABSTRACT="This memo correctly describes the incremental update procedure
for use with the standard Internet checksum. It is intended to replace
the description of Incremental Update in RFC 1071. This is not a
standard but rather, an implementation technique.",
URL="http://www.rfc-editor.org/rfc/rfc1141.txt"
}

@TECHREPORT{rfc1142,
EDITOR="D. Oran",
TITLE="{OSI} {IS-IS} Intra-domain Routing Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1142,
PAGES=115,
DAYS=15,
MONTH=feb,
YEAR=1990,
ABSTRACT="This RFC is a republication of ISO DP 10589 as a service to
the Internet community. This is not an Internet standard.",
URL="http://www.rfc-editor.org/rfc/rfc1142.txt"
}

@TECHREPORT{rfc1143,
AUTHOR="D. Bernstein",
TITLE="The Q Method of Implementing {TELNET} Option Negotiation",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1143,
PAGES=10,
DAYS=15,
MONTH=feb,
YEAR=1990,
ABSTRACT="This is RFC discusses an implementation approach to option
negotiation in the Telnet protocol (RFC 854). It does not propose any
changes to the TELNET protocol. Rather, it discusses the implementation
of the protocol of one feature, only. This is not a protocol
specification. This is an experimental method of implementing a
protocol.",
URL="http://www.rfc-editor.org/rfc/rfc1143.txt"
}

@TECHREPORT{rfc1144,
AUTHOR="V. Jacobson",
TITLE="Compressing {TCP/IP} headers for low-speed serial links",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1144,
PAGES=46,
DAYS=15,
MONTH=feb,
YEAR=1990,
ABSTRACT="This RFC describes a method for compressing the headers of
TCP/IP datagrams to improve performance over low speed serial links. The
motivation, implementation and performance of the method are described.
C code for a sample implementation is given for reference.",
URL="http://www.rfc-editor.org/rfc/rfc1144.txt"
}

@TECHREPORT{rfc1145,
AUTHOR="J. Zweig and C. Partridge",
TITLE="{TCP} alternate checksum options",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1145,
PAGES=5,
DAYS=15,
MONTH=feb,
YEAR=1990,
ABSTRACT="This memo is suggests a pair of TCP options to allow use of
alternate data checksum algorithms in the TCP header. The use of these
options is experimental, and not recommended for production use.",
URL="http://www.rfc-editor.org/rfc/rfc1145.txt"
}

@TECHREPORT{rfc1147,
AUTHOR="R. H. Stine",
TITLE="{FYI} on a Network Management Tool Catalog: Tools for Monitoring and
Debugging {TCP/IP} Internets and Interconnected Devices",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1147,
PAGES=177,
DAYS=15,
MONTH=apr,
YEAR=1990,
ABSTRACT="The goal of this FYI memo is to provide practical information
to site administrators and network managers. This memo provides
information for the Internet community. It does not specify any
standard. It is not a statement of IAB policy or recommendations. (Also
FYI 2.) This catalog contains descriptions of several tools available to
assist network managers in debugging and maintaining TCP/IP internets
and interconnected communications resources. Entries in the catalog tell
what a tool does, how it works, and how it can be obtained.",
URL="http://www.rfc-editor.org/rfc/rfc1147.txt"
}

@TECHREPORT{rfc1148,
AUTHOR="S. E. Kille",
TITLE="Mapping between {X.400(1988)} / {ISO} 10021 and {RFC} 822",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1148,
PAGES=94,
DAYS=15,
MONTH=mar,
YEAR=1990,
ABSTRACT="This RFC suggests an electronic mail protocol mapping for the
Internet community and UK Academic Community, and requests discussion
and suggestions for improvements. This memo does not specify an Internet
standard. This edition includes material lost in editing.",
URL="http://www.rfc-editor.org/rfc/rfc1148.txt"
}

@TECHREPORT{rfc1149,
AUTHOR="D. Waitzman",
TITLE="Standard for the transmission of {IP} datagrams on avian carriers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1149,
PAGES=2,
DAYS=15,
MONTH=apr,
YEAR=1990,
ABSTRACT="This memo describes an experimental method for the
encapsulation of IP datagrams in avian carriers. This specification is
primarily useful in Metropolitan Area Networks. This is an experimental,
not recommended standard.",
URL="http://www.rfc-editor.org/rfc/rfc1149.txt"
}

@TECHREPORT{rfc1150,
AUTHOR="Gary Scott Malkin and J. F. Reynolds",
TITLE="{FYI} on {FYI:} Introduction to the {FYI} Notes",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1150,
PAGES=4,
DAYS=15,
MONTH=mar,
YEAR=1990,
ABSTRACT="This memo is the first in a new sub-series of RFCs called FYIs
(For Your Information). This memo provides information for the Internet
community. It does not specify any standard. (Also FYI 1.)",
URL="http://www.rfc-editor.org/rfc/rfc1150.txt"
}

@TECHREPORT{rfc1151,
AUTHOR="C. Partridge and Robert Hinden",
TITLE="Version 2 of the Reliable Data Protocol {(RDP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1151,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1990,
ABSTRACT="This RFC suggests several updates to the specification of the
Reliable Data Protocol (RDP) in RFC-908 based on experience with the
protocol. This revised version of the protocol is experimental.",
URL="http://www.rfc-editor.org/rfc/rfc1151.txt"
}

@TECHREPORT{rfc1152,
AUTHOR="C. Partridge",
TITLE="Workshop report: Internet research steering group workshop on
very-high-speed networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1152,
PAGES=23,
DAYS=15,
MONTH=apr,
YEAR=1990,
ABSTRACT="This memo is a report on a workshop sponsored by the Internet
Research Steering Group. This memo is for information only. This RFC
does not specify an Internet standard.",
URL="http://www.rfc-editor.org/rfc/rfc1152.txt"
}

@TECHREPORT{rfc1153,
AUTHOR="F. J. Wancho",
TITLE="Digest message format",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1153,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1990,
ABSTRACT="This memo describes the de facto standard Digest Message
Format. This is an elective experimental protocol.",
URL="http://www.rfc-editor.org/rfc/rfc1153.txt"
}

@TECHREPORT{rfc1154,
AUTHOR="D. Robinson and R. Ullmann",
TITLE="Encoding header field for internet messages",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1154,
PAGES=7,
DAYS=15,
MONTH=apr,
YEAR=1990,
ABSTRACT="This RFC proposes an elective experimental Encoding header
field to permit the mailing of multi-part, multi-structured messages.
The use of Encoding updates RFC 1049 (Content-Type), and is a suggested
update to RFCs 1113, 1114, and 1115 (Privacy Enhancement).",
URL="http://www.rfc-editor.org/rfc/rfc1154.txt"
}

@TECHREPORT{rfc1155,
AUTHOR="Marshall T. Rose and K. McCloghrie",
TITLE="Structure and identification of management information for {TCP/IP-based}
internets",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1155,
PAGES=22,
DAYS=15,
MONTH=may,
YEAR=1990,
ABSTRACT={This RFC is a re-release of RFC 1065, with a changed {"}Status
of this Memo{"}, plus a few minor typographical corrections. The technical
content of the document is unchanged from RFC 1065.},
URL="http://www.rfc-editor.org/rfc/rfc1155.txt"
}

@TECHREPORT{rfc1156,
AUTHOR="K. McCloghrie and Marshall T. Rose",
TITLE="Management Information Base for network management of {TCP/IP-based}
internets",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1156,
PAGES=91,
DAYS=15,
MONTH=may,
YEAR=1990,
ABSTRACT={This RFC is a re-release of RFC 1066, with a changed {"}Status
of this Memo{"}, {"}IAB Policy Statement{"}, and {"}Introduction{"}
sections plus
a few minor typographical corrections. The technical content of the
document is unchanged from RFC 1066.},
URL="http://www.rfc-editor.org/rfc/rfc1156.txt"
}

@TECHREPORT{rfc1157,
AUTHOR="J. D. Case and M. S. Fedor and M. L. Schoffstall and C. Davin",
TITLE="Simple Network Management Protocol {(SNMP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1157,
PAGES=36,
DAYS=15,
MONTH=may,
YEAR=1990,
ABSTRACT={This RFC is a re-release of RFC 1098, with a changed {"}Status
of this Memo{"} section plus a few minor typographical corrections. This
memo defines a simple protocol by which management information for a
network element may be inspected or altered by logically remote users.},
URL="http://www.rfc-editor.org/rfc/rfc1157.txt"
}

@TECHREPORT{rfc1158,
AUTHOR="Marshall T. Rose",
TITLE="Management Information Base for network management of {TCP/IP-based}
internets: {MIB-II}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1158,
PAGES=133,
DAYS=15,
MONTH=may,
YEAR=1990,
ABSTRACT="This memo defines the second version of the Management
Information Base (MIB-II) for use with network management protocols in
TCP/IP- based internets. In particular, together with its companion
memos which describe the structure of management information (RFC 1155)
along with the network management protocol (RFC 1157) for TCP/IP- based
internets, these documents provide a simple, workable architecture and
system for managing TCP/IP-based internets and in particular the
Internet community. This document on MIB-II incorporates all of the
technical content of RFC 1156 on MIB-I and extends it, without loss of
compatibilty.",
URL="http://www.rfc-editor.org/rfc/rfc1158.txt"
}

@TECHREPORT{rfc1159,
AUTHOR="R. T. Nelson",
TITLE="Message Send Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1159,
PAGES=2,
DAYS=15,
MONTH=jun,
YEAR=1990,
ABSTRACT="This RFC suggests an Experimental Protocol for the Internet
community. Hosts on the Internet that choose to implement a Message Send
Protocol may experiment with this protocol.",
URL="http://www.rfc-editor.org/rfc/rfc1159.txt"
}

@TECHREPORT{rfc1160,
AUTHOR="V. G. Cerf",
TITLE="Internet Activities Board",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1160,
PAGES=11,
DAYS=15,
MONTH=may,
YEAR=1990,
ABSTRACT="This RFC provides a history and description of the Internet
Activities Board (IAB) and its subsidiary organizations. This memo is
for informational use and does not constitute a standard. This is a
revision of RFC 1120.",
URL="http://www.rfc-editor.org/rfc/rfc1160.txt"
}

@TECHREPORT{rfc1161,
AUTHOR="Marshall T. Rose",
TITLE="{SNMP} over {OSI}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1161,
PAGES=8,
DAYS=15,
MONTH=jun,
YEAR=1990,
ABSTRACT="This memo defines an experimental means for running the Simple
Network Management Protocol (SNMP) over OSI transports. This memo does
not specify a standard for the Internet community,",
URL="http://www.rfc-editor.org/rfc/rfc1161.txt"
}

@TECHREPORT{rfc1162,
AUTHOR="G. Satz",
TITLE="Connectionless Network Protocol {(ISO} {8473)} and End System to
Intermediate System {(ISO} {9542)} Management Information Base",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1162,
PAGES=70,
DAYS=15,
MONTH=jun,
YEAR=1990,
ABSTRACT="This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
TCP/IP-based internets. This memo does not specify a standard for the
Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc1162.txt"
}

@TECHREPORT{rfc1163,
AUTHOR="K. Lougheed and Y. Rekhter",
TITLE="Border Gateway Protocol {(BGP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1163,
PAGES=29,
DAYS=15,
MONTH=jun,
YEAR=1990,
ABSTRACT={This RFC, together with its companion RFC-1164, {"}Application
of the Border Gateway Protocol in the Internet{"}, specify an
inter-autonomous system routing protocol for the Internet.},
URL="http://www.rfc-editor.org/rfc/rfc1163.txt"
}

@TECHREPORT{rfc1164,
AUTHOR="J. C. Honig and D. Katz and M. Mathis and Y. Rekhter and Jiunn-Hwa. Yu",
TITLE="Application of the Border Gateway Protocol in the Internet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1164,
PAGES=23,
DAYS=15,
MONTH=jun,
YEAR=1990,
ABSTRACT={This RFC, together with its companion RFC-1163, {"}A Border
Gateway Protocol (BGP){"}, specify an inter-autonomous system routing
protocol for the Internet.},
URL="http://www.rfc-editor.org/rfc/rfc1164.txt"
}

@TECHREPORT{rfc1165,
AUTHOR="Jon Crowcroft and Julian P. Onions",
TITLE="Network Time Protocol {(NTP)} over the {OSI} Remote Operations Service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1165,
PAGES=10,
DAYS=15,
MONTH=jun,
YEAR=1990,
ABSTRACT="This memo suggests an Experimental Protocol for the OSI and
Internet communities. Hosts in either community, and in particular those
on both are encouraged to experiment with this mechanism.",
URL="http://www.rfc-editor.org/rfc/rfc1165.txt"
}

@TECHREPORT{rfc1166,
AUTHOR="S. Kirkpatrick and Mary K. Stahl and M. Recker",
TITLE="Internet numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1166,
PAGES=182,
DAYS=15,
MONTH=jul,
YEAR=1990,
ABSTRACT="This memo is a status report on the network numbers and
autonomous system numbers used in the Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc1166.txt"
}

@TECHREPORT{rfc1167,
AUTHOR="V. G. Cerf",
TITLE="Thoughts on the National Research and Education Network",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1167,
PAGES=8,
DAYS=15,
MONTH=jul,
YEAR=1990,
ABSTRACT="The memo provides a brief outline of a National Research and
Education Network (NREN). This memo provides information for the
Internet community. It does not specify any standard. It is not a
statement of IAB policy or recommendations.",
URL="http://www.rfc-editor.org/rfc/rfc1167.txt"
}

@TECHREPORT{rfc1168,
AUTHOR="A. Westine and A. L. DeSchon and J. B. Postel and Christopher Ward",
TITLE="Intermail and Commercial Mail Relay services",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1168,
PAGES=18,
DAYS=15,
MONTH=jul,
YEAR=1990,
ABSTRACT="This RFC discusses the history and evolution of the Intermail
and Commercial mail systems. The problems encountered in operating a
store-and-forward mail relay between commercial systems such as
Telemail, MCI Mail and Dialcom are also discussed. This RFC provides
information for the Internet community, and does not specify any
standard.",
URL="http://www.rfc-editor.org/rfc/rfc1168.txt"
}

@TECHREPORT{rfc1169,
AUTHOR="V. G. Cerf and K. Mills",
TITLE="Explaining the role of {GOSIP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1169,
PAGES=15,
DAYS=15,
MONTH=aug,
YEAR=1990,
ABSTRACT="This informational RFC represents the official view of the
Internet Activities Board (IAB), after coordination with the Federal
Networking Council (FNC). This RFC does not specify a standard.",
URL="http://www.rfc-editor.org/rfc/rfc1169.txt"
}

@TECHREPORT{rfc1171,
AUTHOR="D. Perkins",
TITLE="{Point-to-Point} Protocol for the transmission of multi-protocol datagrams
over {Point-to-Point} links",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1171,
PAGES=48,
DAYS=15,
MONTH=jul,
YEAR=1990,
ABSTRACT="This memo specifies the Point-to-Point Protocol (PPP) as a
Draft Standard Protocol for the Internet community. When it becomes a
full Standard, this protocol will be recommended for all TCP/IP
implementations that communicate over serial links.",
URL="http://www.rfc-editor.org/rfc/rfc1171.txt"
}

@TECHREPORT{rfc1172,
AUTHOR="D. Perkins and R. Hobby",
TITLE="{Point-to-Point} Protocol {(PPP)} initial configuration options",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1172,
PAGES=38,
DAYS=15,
MONTH=jul,
YEAR=1990,
ABSTRACT="This memo specifies the Point-to-Point Protocol (PPP) Initial
Configuration Options as a Proposed Standard Protocol for the Internet
community. When it becomes a full Standard, this protocol will be
recommended for all TCP/IP implementations that communicate over serial
links.",
URL="http://www.rfc-editor.org/rfc/rfc1172.txt"
}

@TECHREPORT{rfc1173,
AUTHOR="J. VanBokkelen",
TITLE={Responsibilities of host and network managers: A summary of the {"}oral
tradition{"} of the Internet},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1173,
PAGES=5,
DAYS=15,
MONTH=aug,
YEAR=1990,
ABSTRACT={This informational RFC describes the conventions to be
followed by those in charge of networks and hosts in the Internet. It is
a summary of the {"}oral tradition{"} of the Internet on this subject. (RFC
Editor's note: This memo is a contribution by the author of his view of
these conventions. It is expected that this RFC will provide a basis for
the development of official policies in the future.) These conventions
may be supplemented or amended by the policies of specific local and
regional components of the Internet. This RFC does not specify a
standard, or a policy of the IAB.},
URL="http://www.rfc-editor.org/rfc/rfc1173.txt"
}

@TECHREPORT{rfc1174,
AUTHOR="V. G. Cerf",
TITLE={{IAB} recommended policy on distributing internet identifier assignment and
{IAB} recommended policy change to internet {"}connected{"} status},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1174,
PAGES=9,
DAYS=15,
MONTH=aug,
YEAR=1990,
ABSTRACT="This informational RFC represents the official view of the
Internet Activities Board (IAB), and describes the recommended policies
and procedures on distributing Internet identifier assignments and
dropping the connected status requirement. This RFC does not specify a
standard.",
URL="http://www.rfc-editor.org/rfc/rfc1174.txt"
}

@TECHREPORT{rfc1175,
AUTHOR="K. L. Bowers and T. LaQuey and J. F. Reynolds and K. Roubicek and Mary K.
Stahl and A. Yuan",
TITLE="{FYI} on where to start: A bibliography of internetworking information",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1175,
PAGES=42,
DAYS=15,
MONTH=aug,
YEAR=1990,
ABSTRACT="This FYI RFC is a bibliography of information about TCP/IP
internetworking, prepared by the User Services Working Group (USWG) of
the Internet Engineering Task Force (IETF). This memo provides
information for the Internet community. It does not specify any
standard. (Also FYI 3.)",
URL="http://www.rfc-editor.org/rfc/rfc1175.txt"
}

@TECHREPORT{rfc1176,
AUTHOR="M. R. Crispin",
TITLE="Interactive Mail Access Protocol: Version 2",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1176,
PAGES=30,
DAYS=15,
MONTH=aug,
YEAR=1990,
ABSTRACT={This RFC suggests a method for personal computers and
workstations to dynamically access mail from a mailbox server
({"}repository{"}). It obosoletes RFC 1064. This RFC specifies an
Experimental Protocol for the Internet community. Discussion and
suggestions for improvement are requested. Please refer to the current
edition of the {"}IAB Official Protocol Standards{"} for the
standardization
state and status of this protocol.},
URL="http://www.rfc-editor.org/rfc/rfc1176.txt"
}

@TECHREPORT{rfc1177,
AUTHOR="Gary Scott Malkin and A. N. Marine and J. F. Reynolds",
TITLE={{FYI} on Questions and Answers: Answers to commonly asked {"}new internet
user{"} questions},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1177,
PAGES=24,
DAYS=15,
MONTH=aug,
YEAR=1990,
ABSTRACT={This FYI RFC is one of three FYI's called, {"}Questions and
Answers{"} (Q/A), produced by the User Services Working Group (USWG) of
the Internet Engineering Task Force (IETF). The goal is to document the
most commonly asked questions and answers in the Internet. This memo
provides information for the Internet community. It does not specify any
standard. (Also FYI 4.)},
URL="http://www.rfc-editor.org/rfc/rfc1177.txt"
}

@TECHREPORT{rfc1178,
AUTHOR="D. Libes",
TITLE="Choosing a name for your computer",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1178,
PAGES=8,
DAYS=15,
MONTH=aug,
YEAR=1990,
ABSTRACT="This FYI RFC is a republication of a Communications of the ACM
article on guidelines on what to do and what not to do when naming your
computer. This memo provides information for the Internet community. It
does not specify any standard. (Also FYI 5.)",
URL="http://www.rfc-editor.org/rfc/rfc1178.txt"
}

@TECHREPORT{rfc1179,
AUTHOR="L. J. McLaughlin",
TITLE="Line printer daemon protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1179,
PAGES=14,
DAYS=15,
MONTH=aug,
YEAR=1990,
ABSTRACT={This RFC describes an existing print server protocol widely
used on the Internet for communicating between line printer daemons
(both clients and servers). This memo is for informational purposes
only, and does not specify an Internet standard. Please refer to the
current edition of the {"}IAB Official Protocol Standards{"} for the
standardization state and status of this protocol.},
URL="http://www.rfc-editor.org/rfc/rfc1179.txt"
}

@TECHREPORT{rfc1181,
AUTHOR="R. Blokzijl",
TITLE="{RIPE} Terms of Reference",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1181,
PAGES=2,
DAYS=15,
MONTH=sep,
YEAR=1990,
ABSTRACT="This RFC describes the Terms of Reference of RIPE (Reseaux IP
Europeens), the cooperation of European IP networks. This memo provides
information for the Internet community. It does not specify any
standard.",
URL="http://www.rfc-editor.org/rfc/rfc1181.txt"
}

@TECHREPORT{rfc1183,
AUTHOR="C. Everhart and L. A. Mamakos and R. Ullmann and P. V. Mockapetris",
TITLE="New {DNS} {RR} Definitions",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1183,
PAGES=11,
DAYS=15,
MONTH=oct,
YEAR=1990,
ABSTRACT="This memo defines five new DNS types for experimental
purposes. This RFC describes an Experimental Protocol for the Internet
community, and requests discussion and suggestions for improvements.",
URL="http://www.rfc-editor.org/rfc/rfc1183.txt"
}

@TECHREPORT{rfc1184,
AUTHOR="David A. Borman",
TITLE="Telnet Linemode Option",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1184,
PAGES=23,
DAYS=15,
MONTH=oct,
YEAR=1990,
ABSTRACT="This RFC specifies a procedure for line at a time terminal
interaction based on the Telnet Protocol. It obsoletes RFC 1116.",
URL="http://www.rfc-editor.org/rfc/rfc1184.txt"
}

@TECHREPORT{rfc1185,
AUTHOR="V. Jacobson and R. Braden and L. Zhang",
TITLE="{TCP} Extension for {High-Speed} Paths",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1185,
PAGES=21,
DAYS=15,
MONTH=oct,
YEAR=1990,
ABSTRACT={This memo describes an Experimental Protocol extension to TCP
for the Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the {"}IAB Official
Protocol Standards{"} for the standardization state and status of this
protocol.},
URL="http://www.rfc-editor.org/rfc/rfc1185.txt"
}

@TECHREPORT{rfc1186,
AUTHOR="Ronald L. Rivest",
TITLE="{MD4} Message Digest Algorithm",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1186,
PAGES=18,
DAYS=15,
MONTH=oct,
YEAR=1990,
ABSTRACT="This RFC is the specification of the MD4 Digest Algorithm. If
you are going to implement MD4, it is suggested you do it this way. This
memo is for informational use and does not constitute a standard.",
URL="http://www.rfc-editor.org/rfc/rfc1186.txt"
}

@TECHREPORT{rfc1187,
AUTHOR="Marshall T. Rose and K. McCloghrie and J. R. Davin",
TITLE="Bulk Table Retrieval with the {SNMP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1187,
PAGES=12,
DAYS=15,
MONTH=oct,
YEAR=1990,
ABSTRACT={This memo reports an interesting family of algorithms for bulk
table retrieval using the Simple Network Management Protocol (SNMP).
This memo describes an Experimental Protocol for the Internet community,
and requests discussion and suggestions for improvements. This memo does
not specify a standard for the Internet community. Please refer to the
current edition of the {"}IAB Official Protocol Standards{"} for the
standardization state and status of this protocol.},
URL="http://www.rfc-editor.org/rfc/rfc1187.txt"
}

@TECHREPORT{rfc1188,
AUTHOR="D. Katz",
TITLE="Proposed Standard for the Transmission of {IP} Datagrams over {FDDI}
Networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1188,
PAGES=11,
DAYS=15,
MONTH=oct,
YEAR=1990,
ABSTRACT="This memo defines a method of encapsulating the Internet
Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests
and replies on Fiber Distributed Data Interface (FDDI) Networks.",
URL="http://www.rfc-editor.org/rfc/rfc1188.txt"
}

@TECHREPORT{rfc1189,
AUTHOR="U. Warrier and L. Besaw and L. LaBarre and B. D. Handspicker",
TITLE="Common Management Information Services and Protocols for the Internet
{(CMOT} and {CMIP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1189,
PAGES=15,
DAYS=15,
MONTH=oct,
YEAR=1990,
ABSTRACT="This memo defines a network management architecture that uses
the International Organization for Standardization's (ISO) Common
Management Information Services/Common Management Information Protocol
(CMIS/CMIP) in the Internet.",
URL="http://www.rfc-editor.org/rfc/rfc1189.txt"
}

@TECHREPORT{rfc1190,
AUTHOR="C. Topolcic",
TITLE="Experimental Internet Stream Protocol: Version 2 {(ST-II)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1190,
PAGES=148,
DAYS=15,
MONTH=oct,
YEAR=1990,
ABSTRACT={This memo defines a revised version of the Internet Stream
Protocol, originally defined in IEN-119, based on results from
experiments with the original version, and subsequent requests,
discussion, and suggestions for improvements. This is a Limited-Use
Experimental Protocol. Please refer to the current edition of the {"}IAB
Official Protocol Standards{"} for the standardization state and status of
this protocol.},
URL="http://www.rfc-editor.org/rfc/rfc1190.txt"
}

@TECHREPORT{rfc1191,
AUTHOR="J. C. Mogul and S. E. Deering",
TITLE="Path {MTU} discovery",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1191,
PAGES=19,
DAYS=15,
MONTH=nov,
YEAR=1990,
ABSTRACT="This memo describes a technique for dynamically discovering
the maximum transmission unit (MTU) of an arbitrary internet path. It
specifies a small change to the way routers generate one type of ICMP
message. For a path that passes through a router that has not been so
changed, this technique might not discover the correct Path MTU, but it
will always choose a Path MTU as accurate as, and in many cases more
accurate than, the Path MTU that would be chosen by current practice.",
URL="http://www.rfc-editor.org/rfc/rfc1191.txt"
}

@TECHREPORT{rfc1192,
AUTHOR="B. Kahin",
TITLE="Commercialization of the Internet summary report",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1192,
PAGES=13,
DAYS=15,
MONTH=nov,
YEAR=1990,
ABSTRACT="This memo is based on a workshop held by the Science,
Technology and Public Policy Program of the John F. Kennedy School of
Government, Harvard University, March 1-3, 1990. This memo provides
information for the Internet community. It does not specify any
standard.",
URL="http://www.rfc-editor.org/rfc/rfc1192.txt"
}

@TECHREPORT{rfc1193,
AUTHOR="D. Ferrari",
TITLE="Client requirements for real-time communication services",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1193,
PAGES=24,
DAYS=15,
MONTH=nov,
YEAR=1990,
ABSTRACT="This memo describes client requirements for real-time
communication services. This memo provides information for the Internet
community, and requests discussion and suggestions for improvements. It
does not specify any standard. A real-time communication service
provides its clients with the ability to specify their performance
requirements and to obtain guarantees about the satisfaction of those
requirements. In this paper, we propose a set of performance
specifications that seem appropriate for such services; they include
various types of delay bounds, throughput bounds, and reliability
bounds. We also describe other requirements and desirable properties
from a client's viewpoint, and the ways in which each requirement is to
be translated to make it suitable for lower levels in the protocol
hierarchy. Finally, we present some examples of requirements
specification, and discuss some of the possible objections to our
approach.",
URL="http://www.rfc-editor.org/rfc/rfc1193.txt"
}

@TECHREPORT{rfc1194,
AUTHOR="D. Patrick Zimmerman",
TITLE="Finger User Information Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1194,
PAGES=12,
DAYS=15,
MONTH=nov,
YEAR=1990,
ABSTRACT="This memo describes the Finger User Information Protocol. This
is a simple protocol which provides an interface to a remote user
information program. Based on RFC 742, a description of the original
Finger protocol, this memo attempts to clarify the expected
communication between the two ends of a Finger connection. It also tries
not to invalidate the many existing implementations or add unnecessary
restrictions to the original protocol definition.",
URL="http://www.rfc-editor.org/rfc/rfc1194.txt"
}

@TECHREPORT{rfc1195,
AUTHOR="R. Callon",
TITLE="Use of {OSI} {IS-IS} for routing in {TCP/IP} and dual environments",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1195,
PAGES=85,
DAYS=15,
MONTH=dec,
YEAR=1990,
ABSTRACT="This memo specifies an integrated routing protocol, based on
the OSI Intra-Domain IS-IS Routing Protocol, which may be used as an
interior gateway protocol (IGP) to support TCP/IP as well as OSI. This
allows a single routing protocol to be used to support pure IP
environments, pure OSI environments, and dual environments. This
specification was developed by the IS-IS working group of the Internet
Engineering Task Force.",
URL="http://www.rfc-editor.org/rfc/rfc1195.txt"
}

@TECHREPORT{rfc1196,
AUTHOR="D. Patrick Zimmerman",
TITLE="The Finger User Information Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1196,
MONTH=dec,
YEAR=1990,
ABSTRACT="1.1. Intent",
URL="http://www.rfc-editor.org/rfc/rfc1196.txt"
}

@TECHREPORT{rfc1197,
AUTHOR="M. Sherman",
TITLE="Using {ODA} for translating multimedia information",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1197,
PAGES=2,
DAYS=15,
MONTH=dec,
YEAR=1990,
ABSTRACT="The purpose of this RFC is to inform implementors of
multimedia systems about our experiences using ISO 8613: Office Document
Architecture (ODA). Because ODA is being proposed as an encoding format
for use in multimedia mail and file exchange, implementors wishing to
use ODA in an open systems environment may profit from our experiences.
This memo provides information for the Internet community. It does not
specify any standard.",
URL="http://www.rfc-editor.org/rfc/rfc1197.txt"
}

@TECHREPORT{rfc1099,
AUTHOR="J. F. Reynolds",
TITLE="Request for Comments Summary: {RFC} Numbers {1000-1099}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1099,
PAGES=22,
DAYS=15,
MONTH=dec,
YEAR=1991,
ABSTRACT="This memo is a slightly annotated list of the 100 RFCs from
RFC 1000 through RFCs 1099.",
URL="http://www.rfc-editor.org/rfc/rfc1099.txt"
}

@TECHREPORT{rfc1108,
AUTHOR="Stephen T. Kent",
TITLE="{U.S.} Department of Defense Security Options for the Internet Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1108,
MONTH=nov,
YEAR=1991,
ABSTRACT={This RFC specifies the U.S. Department of Defense Basic
Security Option and the top-level description of the Extended Security
Option for use with the Internet Protocol. This RFC obsoletes RFC 1038,
{"}Revised IP Security Option{"}, dated January 1988.},
URL="http://www.rfc-editor.org/rfc/rfc1108.txt"
}

@TECHREPORT{rfc1170,
AUTHOR="R. B. Fougner",
TITLE="Public key standards and licenses",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1170,
PAGES=2,
DAYS=15,
MONTH=jan,
YEAR=1991,
ABSTRACT="This RFC is a public statement by Public Key Partners
regarding Public Key Standards and Licenses. This memo is for
informational use only, and does not constitute an Internet standard.",
URL="http://www.rfc-editor.org/rfc/rfc1170.txt"
}

@TECHREPORT{rfc1180,
AUTHOR="T. J. Socolofsky and C. J. Kale",
TITLE="{TCP/IP} tutorial",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1180,
PAGES=28,
DAYS=15,
MONTH=jan,
YEAR=1991,
ABSTRACT="This RFC is a tutorial on the TCP-IP protocol suite, focusing
particularly on the steps in forwarding an IP datagram from source host
to destination host through a router. It does not specify an Internet
standard.",
URL="http://www.rfc-editor.org/rfc/rfc1180.txt"
}

@TECHREPORT{rfc1198,
AUTHOR="R. Scheifler",
TITLE="{FYI} on the X window system",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1198,
PAGES=3,
DAYS=15,
MONTH=jan,
YEAR=1991,
ABSTRACT="This FYI RFC provides pointers to the published standards of
the MIT X Consortium. This memo provides information for the Internet
community. It does not specify any Internet standard.",
URL="http://www.rfc-editor.org/rfc/rfc1198.txt"
}

@TECHREPORT{rfc1199,
AUTHOR="J. F. Reynolds",
TITLE="Request for Comments Summary Notes: {1100-1199}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1199,
PAGES=22,
DAYS=15,
MONTH=dec,
YEAR=1991,
ABSTRACT="This RFC is a slightly annotated list of the 100 RFCs from RFC
1100 through RFCs 1199. This is a status report on these RFCs.",
URL="http://www.rfc-editor.org/rfc/rfc1199.txt"
}

@TECHREPORT{rfc1200,
AUTHOR="J. B. Postel",
TITLE="{IAB} official protocol standards",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1200,
PAGES=31,
DAYS=15,
MONTH=apr,
YEAR=1991,
ABSTRACT="Discussion of the standardization process and the RFC document
series is presented first, followed by an explanation of the terms.
Sections 6.2 - 6.8 contain the lists of protocols in each stage of
standardization. Finally come pointers to references and contacts for
further information. This memo is intended to be issued quarterly;
please be sure the copy you are reading is current. Current copies may
be obtained from the Network Information Center or from the Internet
Assigned Numbers Authority (see the contact information at the end of
this memo). Do not use this edition after 30-Jun-91. See Section 6.1 for
a description of recent changes. In the official lists in sections 6.2 -
6.8, an asterisk (*) next to a protocol denotes that it is new to this
document or has been moved from one protocol level to another.",
URL="http://www.rfc-editor.org/rfc/rfc1200.txt"
}

@TECHREPORT{rfc1201,
AUTHOR="D. Provan",
TITLE="Transmitting {IP} traffic over {ARCNET} networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1201,
PAGES=7,
DAYS=15,
MONTH=feb,
YEAR=1991,
ABSTRACT={This memo specifies a method of encapsulating Internet
Protocol (IP) and Address Resolution Protocol (ARP) datagrams for
transmission across ARCNET using the {"}ARCNET Packet Header Definition
Standard{"}. This memo offers a replacement for RFC 1051. RFC 1051 uses an
ARCNET framing protocol which limits unfragmented IP packets to 508
octets.},
URL="http://www.rfc-editor.org/rfc/rfc1201.txt"
}

@TECHREPORT{rfc1202,
AUTHOR="Marshall T. Rose",
TITLE="Directory Assistance service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1202,
PAGES=11,
DAYS=15,
MONTH=feb,
YEAR=1991,
ABSTRACT="The OSI Directory provides a powerful infrastructure for the
retrieval of information objects. This infrastructure can be used to
support, e.g., white pages applications, application entity lookup, and
so on.",
URL="http://www.rfc-editor.org/rfc/rfc1202.txt"
}

@TECHREPORT{rfc1203,
AUTHOR="J. Rice",
TITLE="Interactive Mail Access Protocol: Version 3",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1203,
PAGES=49,
DAYS=15,
MONTH=feb,
YEAR=1991,
ABSTRACT={The intent of the Interactive Mail Access Protocol, Version 3
(IMAP3) is to allow a (possibly unreliable) workstation or similar
machine to access electronic mail from a reliable mailbox server in an
efficient manner. Although different in many ways from POP2 (RFC 937),
IMAP3 may be thought of as a functional superset of POP2, and the POP2
RFC was used as a model for this RFC. There was a cognizant reason for
this; RFC 937 deals with an identical problem and it was desirable to
offer a basis for comparison. Like POP2, IMAP3 specifies a means of
accessing stored mail and not of posting mail; this function is handled
by a mail transfer protocol such as SMTP (RFC 821). A comparison with
the DMSP protocol of PCMAIL can be found at the end of {"}System Model and
Philosophy{"} section. This protocol assumes a reliable data stream such
as provided by TCP or any similar protocol. When TCP is used, the IMAP
server listens on port 220. When CHAOS is used the IMAP server listens
for the logical contact name {"}IMAP3{"}. Communication in IMAP is defined
to be using the ASCII character interpretation of data. Communication
using other conventions may be possible by the selection of features on
some servers.},
URL="http://www.rfc-editor.org/rfc/rfc1203.txt"
}

@TECHREPORT{rfc1204,
AUTHOR="S. Yeh and D. Lee",
TITLE="Message Posting Protocol {(MPP)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1204,
PAGES=6,
DAYS=15,
MONTH=feb,
YEAR=1991,
ABSTRACT="Operating systems for personal computers do not provide a
mechanism for user authentication. However, such a mechanism is crucial
for electronic mail system since authenticating message sender's
identity is important in preventing mail forgery. Hence, adding personal
computers to an electronic mail network requires an agent (message
posting server) to authenticate sender's identity and then submit mail
to the message delivery system (e.g., Sendmail, MMDF) on behalf of the
sender at a PC. The Netix Message Posting Protocol is developed to be
the interface between the message posting server and the PC (client).
The protocol is designed to use TCP and is based on the command and
reply structures defined for Simple Mail Transfer Protocol (RFC 821) and
File Transfer Protocol (RFC 959).",
URL="http://www.rfc-editor.org/rfc/rfc1204.txt"
}

@TECHREPORT{rfc1205,
AUTHOR="P. Chmielewski",
TITLE="5250 Telnet interface",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1205,
PAGES=12,
DAYS=15,
MONTH=feb,
YEAR=1991,
ABSTRACT="This RFC describes the interface to the IBM 5250 Telnet
implementation. The purpose of this memo is to describe the details of
the interface so that a person wanting to implement a client Telnet
which emulates an IBM 5250 work station would be able to do so. This
memo does not describe all of the 5250 commands, aid codes, and other
information specific to the 5250 data stream. That information is
contained in the IBM 5250 Information Display System, Functions
Reference Manual, IBM publication number SA21-9247. Corrections and
additions to this manual are documented in this RFC in section 5.",
URL="http://www.rfc-editor.org/rfc/rfc1205.txt"
}

@TECHREPORT{rfc1206,
AUTHOR="Gary Scott Malkin and A. N. Marine",
TITLE={{FYI} on Questions and Answers: Answers to commonly asked {"}new Internet
user{"} questions},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1206,
PAGES=32,
DAYS=15,
MONTH=feb,
YEAR=1991,
ABSTRACT="New users joining the Internet community have the same
questions as did everyone else who has ever joined. Our quest is to
provide the Internet community with up to date, basic Internet knowledge
and experience, while moving the redundancies away from the electronic
mailing lists so that the lists' subscribers do not have to read the
same queries and answers over and over again. Future updates of this
memo will be produced as User Services members",
URL="http://www.rfc-editor.org/rfc/rfc1206.txt"
}

@TECHREPORT{rfc1207,
AUTHOR="Gary Scott Malkin and A. N. Marine and J. F. Reynolds",
TITLE={{FYI} on Questions and Answers: Answers to commonly asked {"}experienced
Internet user{"} questions},
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1207,
PAGES=15,
DAYS=15,
MONTH=feb,
YEAR=1991,
ABSTRACT="During the last few months, several people have monitored
various major mailing lists and have extracted questions that are
important or commonly asked. This FYI RFC is one of two in a series of
FYI's which present the questions and their answers. The first FYI, FYI
4, presented questions new Internet users commonly ask and their
answers.",
URL="http://www.rfc-editor.org/rfc/rfc1207.txt"
}

@TECHREPORT{rfc1208,
AUTHOR="Ole J. Jacobsen and Dan Lynch",
TITLE="Glossary of networking terms",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1208,
PAGES=18,
DAYS=15,
MONTH=mar,
YEAR=1991,
ABSTRACT={This glossary is adapted from {"}The INTEROP Pocket Glossary of
Networking Terms{"} produced to help you understand the many terms--and in
particular the myriad of acronyms--that can be encountered at the
INTEROP Tutorials, Conference, and Exhibition. To keep this document
reasonably small we have deliberately omitted common computer and
communications terms such as disk, modem, byte, and VLSI. In addition,
the definitions have been kept brief. We recommend that you consult the
glossaries found in the major computer networking textbooks for more
comprehensive definitions. We also realize that producing this glossary
is akin to shooting at a moving target. The computer and communications
industries are moving very rapidly, and terms and acronyms are born
every day. You are invited to submit words which you think should be
included in future editions.},
URL="http://www.rfc-editor.org/rfc/rfc1208.txt"
}

@TECHREPORT{rfc1209,
AUTHOR="D. Piscitello and J. Lawrence",
TITLE="Transmission of {IP} datagrams over the {SMDS} Service",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1209,
PAGES=11,
DAYS=15,
MONTH=mar,
YEAR=1991,
ABSTRACT="This memo describes an initial use of IP and ARP in an SMDS
service environment configured as a logical IP subnetwork, LIS
(described below). The encapsulation method used is described, as well
as various service-specific issues. This memo does not preclude
subsequent treatment of the SMDS Service in configurations other than
LIS; specifically, public or inter-company, inter-enterprise
configurations may be treated differently and will be described in
future documents. This document considers only directly connected IP
end-stations or routers; issues raised by MAC level bridging are beyond
the scope of this paper.",
URL="http://www.rfc-editor.org/rfc/rfc1209.txt"
}

@TECHREPORT{rfc1210,
AUTHOR="V. G. Cerf and P. T. Kirstein and B. Randell",
TITLE="Network and infrastructure user requirements for transatlantic research
collaboration: Brussels, July {16-18,} and Washington July {24-25,} 1990",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1210,
PAGES=36,
DAYS=15,
MONTH=mar,
YEAR=1991,
ABSTRACT="This report summarises user requirements for networking and
related infrastructure facilities needed to enable effective cooperation
between US and European research teams participating in the planned
ESPRIT-DARPA/NSF programme of collaborative research in Information
Science and Technology. It analyses the problems and disparities of the
current facilities, and suggests appropriate one and three year targets
for improvements. It proposes a number of initial actions aimed at
achieving these targets. Finally, the workshop has identified a
non-exhaustive set of important issues upon which support of future
research will depend. These issues could be studied in the short term,
with the aim of initiating a programme of joint research in
collaboration technology within the next year.",
URL="http://www.rfc-editor.org/rfc/rfc1210.txt"
}

@TECHREPORT{rfc1211,
AUTHOR="A. Westine and J. B. Postel",
TITLE="Problems with the maintenance of large mailing lists",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1211,
PAGES=54,
DAYS=15,
MONTH=mar,
YEAR=1991,
ABSTRACT="Maintaining large mailing lists, especially the processing of
error reports, poses many problems. Most of the examples come from the
experience of managing the Internet Engineering Task Force (IETF)
mailing list. Many examples are presented in this memo. Most of the
specific problems shown have already been corrected.",
URL="http://www.rfc-editor.org/rfc/rfc1211.txt"
}

@TECHREPORT{rfc1212,
AUTHOR="Marshall T. Rose and K. McCloghrie",
TITLE="Concise {MIB} definitions",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1212,
PAGES=19,
DAYS=15,
MONTH=mar,
YEAR=1991,
ABSTRACT="This memo describes a straight-forward approach toward
producing concise, yet descriptive, MIB modules. It is intended that all
future MIB modules be written in this format.",
URL="http://www.rfc-editor.org/rfc/rfc1212.txt"
}

@TECHREPORT{rfc1213,
AUTHOR="K. McCloghrie and Marshall T. Rose",
TITLE="Management Information Base for Network Management of {TCP/IP-based}
{internets:MIB-II}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1213,
PAGES=70,
DAYS=15,
MONTH=mar,
YEAR=1991,
ABSTRACT="This memo defines the second version of the Management
Information Base (MIB-II) for use with network management protocols in
TCP/IP- based internets. In particular, together with its companion
memos which describe the structure of management information (RFC 1155)
along with the network management protocol (RFC 1157) for TCP/IP- based
internets, these documents provide a simple, workable architecture and
system for managing TCP/IP-based internets and in particular the
Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc1213.txt"
}

@TECHREPORT{rfc1214,
AUTHOR="L. LaBarre",
TITLE="{OSI} internet management: Management Information Base",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1214,
PAGES=83,
DAYS=15,
MONTH=apr,
YEAR=1991,
ABSTRACT="This RFC documents a MIB for use with CMIP, either over pure
OSI stacks or with the CMIP over TCP specification. It redefines objects
comprised by the second revision of the Management Information Base for
Network Management of TCP/IP-based internets: MIB-II so as to conform to
the OSI structure of management information. This document is a product
of the IETF OIM working group.",
URL="http://www.rfc-editor.org/rfc/rfc1214.txt"
}

@TECHREPORT{rfc1215,
AUTHOR="Marshall T. Rose",
TITLE="Convention for defining traps for use with the {SNMP}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1215,
PAGES=9,
DAYS=15,
MONTH=mar,
YEAR=1991,
ABSTRACT="This memo suggests a straight-forward approach towards
defining traps used with the SNMP. Readers should note that the use of
traps in the Internet-standard network management framework is
controversial. As such, this memo is being put forward for information
purposes. Network management practitioners who employ traps are
encouraged to make use of this document. Practitioners who do not employ
traps can safely ignore this document.",
URL="http://www.rfc-editor.org/rfc/rfc1215.txt"
}

@TECHREPORT{rfc1216,
AUTHOR="P. Richard and P. Kynikos",
TITLE="Gigabit network economics and paradigm shifts",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1216,
PAGES=4,
DAYS=15,
MONTH=apr,
YEAR=1991,
ABSTRACT="The history of computer communication contains many examples
of efforts to align the capabilities of processors to that of
communication media. Packet switching is the classic case of a careful
tradeoff between the costs of memory, processing, and communications
bandwidth. With all of the attention and publicity focused on gigabit
networks, not much notice has been given to small and largely unfunded
research efforts which are studying innovative approaches for dealing
with technical issues within the constraints of economic science. This
memo defines one such paradigm.",
URL="http://www.rfc-editor.org/rfc/rfc1216.txt"
}

@TECHREPORT{rfc1217,
AUTHOR="V. G. Cerf",
TITLE="Memo from the Consortium for Slow Commotion Research {(CSCR)}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1217,
PAGES=5,
DAYS=15,
MONTH=apr,
YEAR=1991,
ABSTRACT="Military requirements place a high premium on ultra-robust
systems capable of supporting communication in extremely hostile
environments. A major contributing factor in the survivability of
systems is a high degree of redundancy. CSCR believes that the system
designs offered below exhibit extraordinary redundancy features which
should be of great interest to DARPA and the Department of Defense.",
URL="http://www.rfc-editor.org/rfc/rfc1217.txt"
}

@TECHREPORT{rfc1218,
AUTHOR=" {{North American Directory Forum}}",
TITLE="Naming scheme for {c=US}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1218,
MONTH=apr,
YEAR=1991,
ABSTRACT="This is one of a series of documents produced for discussion
within the North American Directory Forum. Distribution, with
attribution, is unlimited. This document is being circulated for
comment. The deadline for comments is July 1, 1991. Comments should be
directed to the contact given on page 16.",
URL="http://www.rfc-editor.org/rfc/rfc1218.txt"
}

@TECHREPORT{rfc1219,
AUTHOR="Paul F. Tsuchiya",
TITLE="On the assignment of subnet numbers",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1219,
PAGES=13,
DAYS=15,
MONTH=apr,
YEAR=1991,
ABSTRACT={RFC-950 specifies a procedure for subnetting Internet
addresses using a bit-mask. While RFC-950 allows the {"}ones{"} in the
subnet mask to be non-contiguous, RFC-950 recommends that 1) they be
contiguous, and 2) that they occupy the most significant bits of the
{"}host{"} part of the internet address. RFC-950 did not specify whether
different subnets of the same network may have different masks. This
ambiguity was unfortunate, as it resulted in development of routing
protocols that do not support different masks; see e.g., RIP. The
Gateway Requirements RFC settled the issue in favor of allowing
different masks, and therefore future routing protocols may be expected
to support this feature; OSPF is an example. The network administrator
must of course determine the mask for each subnet. This involves making
an estimate of how many hosts each subnet is expected to have. As it is
often impossible to predict how large each subnet will grow, inefficient
choices are often made, with some subnets under-utilized, and others
possibly requiring renumbering because of exceeded capacity. This memo
specifies a procedure for assigning subnet numbers that eliminates the
need to estimate subnet size. Essentially, host bits (mask = 0) are
assigned from the least significant bit working towards the most, and
subnet bits (mask = 1) are assigned from the most significant bit
working towards the least. As subnets grow, more host bits are assigned.
As the number of subnets grows, more subnet bits are assigned. While
this process does sometimes result},
URL="http://www.rfc-editor.org/rfc/rfc1219.txt"
}

@TECHREPORT{rfc1220,
AUTHOR="F. Baker",
TITLE="{Point-to-Point} Protocol extensions for bridging",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1220,
PAGES=18,
DAYS=15,
MONTH=apr,
YEAR=1991,
ABSTRACT="This document defines an extension of the Internet
Point-to-Point Protocol (PPP) described in RFC 1171, targeting the use
of Point-to-Point lines for Remote Bridging.",
URL="http://www.rfc-editor.org/rfc/rfc1220.txt"
}

@TECHREPORT{rfc1221,
AUTHOR="W. Edmond",
TITLE="Host Access Protocol {(HAP)} specification: Version 2",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1221,
PAGES=68,
DAYS=15,
MONTH=apr,
YEAR=1991,
ABSTRACT={The Host Access Protocol (HAP) is a network layer protocol (as
is X.25). ({"}Network layer{"} here means ISO layer 3 lower, the protocol
layer below the DoD Internet Protocol (IP) layer and above any link
layer protocol.) HAP defines the different types of host-to- network
control messages and host-to-host data messages that may be exchanged
over the access link connecting a host and the network packet switch
node. The protocol establishes formats for these messages, and describes
procedures for determining when each type of message should be
transmitted and what it means when one is received. HAP has been
implemented in the wide-area network called the Terrestrial Wideband
Network (TWBNET) and in the routers and other hosts that connect to
TWBNET. The packet switch nodes that compose the TWBNET are called
Wideband Packet Switches (WPS). Both the precursor to HAP, the
Host/SATNET Protocol, used in the Atlantic Packet Satellite Network
(SATNET) and the Mobile Access Terminal Network (MATNET), and HAP, used
in the original Wideband Satellite Network (WBNET), were originally
designed to provide efficient access to the single satellite channel
each network used to connect all sites. The HAP protocol designers
reflected some of the peculiarities of the single satellite channel
environment in the HAP protocol itself. The current Terrestrial Wideband
Network (TWBNET) utilizes T1-speed fiber connections between sites.
Future networks and TWBNET may use a combination of terrestrial
connections and satellite connections, and may have more than one of
each. The HAP protocol has been changed to accommodate these extensions.
Section 2 presents an overview of HAP. Details of HAP formats and
message exchange procedures are contained in Sections 3 through 10.
Further explanation of some of the topics addressed in this HAP
specification can be found elsewhere. Any protocol employed to provide
sufficiently reliable message exchange over the Host-WPS link is assumed
to be transparent to the protocol defined in this document. Examples of
such link-level protocols are ARPANET 1822 local and distant host,
ARPANET VDH protocol, and HDLC.},
URL="http://www.rfc-editor.org/rfc/rfc1221.txt"
}

@TECHREPORT{rfc1222,
AUTHOR="H. Braun and Y. Rekhter",
TITLE="Advancing the {NSFNET} routing architecture",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1222,
PAGES=6,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="This memo describes the history of NSFNET Backbone routing and
outlines two suggested phases for further evolution of the Backbone's
routing interface. The intent is to provide a more flexible interface
for NSFNET Backbone service subscribers, by providing an attachment
option that is simpler and lower-cost than the current one.",
URL="http://www.rfc-editor.org/rfc/rfc1222.txt"
}

@TECHREPORT{rfc1223,
AUTHOR="J. Y. Halpern",
TITLE="{OSI} {CLNS} and {LLC1} protocols on Network Systems {HYPERchannel}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1223,
PAGES=12,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="The intent of this document is to provide a complete
discussion of the protocols and techniques used to transmit OSI CLNS and
LLC1 datagrams (and any associated higher level protocols) on Network
Systems Corporation's HYPERchannel equipment. This document is intended
for network planners and implementers who are already familiar with the
OSI protocol suite and the techniques used to carry OSI traffic on
standard networks such as 802.3.",
URL="http://www.rfc-editor.org/rfc/rfc1223.txt"
}

@TECHREPORT{rfc1224,
AUTHOR="L. Steinberg",
TITLE="Techniques for managing asynchronously generated alerts",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1224,
PAGES=22,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT={This RFC explores mechanisms to prevent a remotely managed
entity from burdening a manager or network with an unexpected amount of
network management information, and to ensure delivery of {"}important{"}
information. The focus is on controlling the flow of asynchronously
generated information, and not how the information is generated.},
URL="http://www.rfc-editor.org/rfc/rfc1224.txt"
}

@TECHREPORT{rfc1225,
AUTHOR="Marshall T. Rose",
TITLE="Post Office Protocol: Version 3",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1225,
PAGES=16,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="This memo is a republication of RFC 1081 which was based on
RFC 918 (since revised as RFC 937). Although similar in form to the
original Post Office Protocol (POP) proposed for the Internet community,
the protocol discussed in this memo is similar in spirit to the ideas
investigated by the MZnet project at the University of California,
Irvine. Further, substantial work was done on examining POP in a
PC-based environment. This work, which resulted in additional
functionality in this protocol, was performed by the ACIS Networking
Systems Group at Stanford University. The author gratefully acknowledges
their interest.",
URL="http://www.rfc-editor.org/rfc/rfc1225.txt"
}

@TECHREPORT{rfc1226,
AUTHOR="B. Kantor",
TITLE="Internet protocol encapsulation of {AX.25} frames",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1226,
PAGES=2,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="This memo describes a method for the encapsulation of AX.25
(the Amateur Packet-Radio Link-Layer Protocol) frames within IP packets.
This technique is an Experimental Protocol for the Internet community.",
URL="http://www.rfc-editor.org/rfc/rfc1226.txt"
}

@TECHREPORT{rfc1227,
AUTHOR="Marshall T. Rose",
TITLE="{SNMP} {MUX} protocol and {MIB}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1227,
PAGES=13,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="On typical kernel/user systems, an agent speaking the SNMP is
often implemented as a user-process, that reads kernel variables in
order to realize the Internet-standard MIB. This approach works fine as
long as all of the information needed by the SNMP agent resides in
either the kernel or in stable storage (i.e., files). However, when
other user-processes are employed to implement other",
URL="http://www.rfc-editor.org/rfc/rfc1227.txt"
}

@TECHREPORT{rfc1228,
AUTHOR="G. A. Carpenter and B. Wijnen",
TITLE="{SNMP-DPI:} Simple Network Management Protocol Distributed Program
Interface",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1228,
PAGES=50,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="The Simple Network Management Protocol (SNMP) Distributed
Program Interface (DPI) is an extension to SNMP agents that permits
end-users to dynamically add, delete or replace management variables in
the local Management Information Base without requiring recompilation of
the SNMP agent. This is achieved by writing a so-called sub-agent that
communicates with the agent via the SNMP-DPI. For the author of a
sub-agent, the SNMP-DPI eliminates the need to know the details of ASN.1
or SNMP PDU (Protocol Data Unit) encoding/decoding. This protocol has
been in use within IBM since 1989 and is included in the SNMP agents for
VM, MVS and OS/2. Potentially useful sample sub-agent code and
implementation examples are available for anonymous FTP from the
University of Toronto.",
URL="http://www.rfc-editor.org/rfc/rfc1228.txt"
}

@TECHREPORT{rfc1229,
AUTHOR="K. McCloghrie",
TITLE="Extensions to the generic-interface {MIB}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1229,
PAGES=16,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
TCP/IP-based internets. In particular, it defines managed object types
as experimental extensions to the generic interfaces structure of
MIB-II.",
URL="http://www.rfc-editor.org/rfc/rfc1229.txt"
}

@TECHREPORT{rfc1230,
AUTHOR="K. McCloghrie and R. Fox",
TITLE="{IEEE} {802.4} Token Bus {MIB}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1230,
PAGES=23,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
TCP/IP-based internets. In particular, this memo defines managed objects
used for managing subnetworks which use the IEEE 802.4 Token Bus
technology described in 802.4 Token-Passing Bus Access Method and
Physical Layer Specifications, IEEE Standard 802.4.",
URL="http://www.rfc-editor.org/rfc/rfc1230.txt"
}

@TECHREPORT{rfc1231,
AUTHOR="K. McCloghrie and R. Fox and E. Decker",
TITLE="{IEEE} {802.5} Token Ring {MIB}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1231,
PAGES=23,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
TCP/IP-based internets. In particular, this memo defines managed objects
used for managing subnetworks which use the IEEE 802.5 Token Ring
technology described in 802.5 Token Ring Access Method and Physical
Layer Specifications, IEEE Standard 802.5-1989.",
URL="http://www.rfc-editor.org/rfc/rfc1231.txt"
}

@TECHREPORT{rfc1232,
AUTHOR="F. Baker and C. P. Kolb",
TITLE="Definitions of managed objects for the {DS1} Interface type",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1232,
PAGES=28,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
TCP/IP-based internets. In particular, this memo defines MIB objects for
representing DS1 physical interfaces. Implementors should consult in
addition to this memo the companion document that describes that DS3
managed objects.",
URL="http://www.rfc-editor.org/rfc/rfc1232.txt"
}

@TECHREPORT{rfc1233,
AUTHOR="T. F. Cox and K. Tesink",
TITLE="Definitions of managed objects for the {DS3} Interface type",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1233,
PAGES=23,
DAYS=15,
MONTH=may,
YEAR=1991,
ABSTRACT="This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
TCP/IP-based internets. In particular, this memo defines MIB objects for
representing DS3 physical interfaces. Implementors should consult in
addition to this memo the companion document that",
URL="http://www.rfc-editor.org/rfc/rfc1233.txt"
}

@TECHREPORT{rfc1234,
AUTHOR="D. Provan",
TITLE="Tunneling {IPX} traffic through {IP} networks",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1234,
PAGES=6,
DAYS=15,
MONTH=jun,
YEAR=1991,
ABSTRACT="Internet Packet eXchange protocol (IPX) is the internetwork
protocol used by Novell's NetWare protocol suite. For the purposes of
this paper, IPX is functionally equivalent to the Internet Datagram
Protocol (IDP) from the Xerox Network Systems (XNS) protocol suite. This
memo describes a method of encapsulating IPX datagrams within UDP
packets so that IPX traffic can travel across an IP internet. This RFC
allows an IPX implementation to view an IP internet as a single IPX
network. An implementation of this memo will encapsulate IPX datagrams
in UDP packets in the same way any hardware implementation might
encapsulate IPX datagrams in that hardware's frames. IPX networks can be
connected thusly across internets that carry only IP traffic.",
URL="http://www.rfc-editor.org/rfc/rfc1234.txt"
}

@TECHREPORT{rfc1235,
AUTHOR="J. Ioannidis and Gerald (Chip) Maguire",
TITLE="Coherent File Distribution Protocol",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1235,
PAGES=12,
DAYS=15,
MONTH=jun,
YEAR=1991,
ABSTRACT={The Coherent File Distribution Protocol (CFDP) has been
designed to speed up one-to-many file transfer operations that exhibit
traffic coherence on media with broadcast capability. Examples of such
coherent file transfers are identical diskless workstations booting
simultaneously, software upgrades being distributed to more than one
machines at a site, a certain {"}object{"} (bitmap, graph, plain text,
etc.)
that is being discussed in a real-time electronic conference or class
being sent to all participants, and so on. In all these cases, we have a
limited number of servers, usually only one, and <n> clients (where <n>
can be large) that are being sent the same file. If these files are sent
via multiple one-to-one transfers, the load on both the server and the
network is greatly increased, as the same data are sent <n> times. We
propose a file distribution protocol that takes advantage of the
broadcast nature of the communications medium (e.g., fiber, ethernet,
packet radio) to drastically reduce the time needed for file transfer
and the impact on the file server and the network. While this protocol
was developed to allow the simultaneous booting of diskless workstations
over our experimental packet-radio network, it can be used in any
situation where coherent transfers take place. CFDP was originally
designed as a back-end protocol; a front-end interface (to convert file
names and requests for them to file handles) is still needed, but a
number of existing protocols can be adapted to use with CFDP. Two such
reference applications have been developed; one is for diskless booting
of workstations, a simplified},
URL="http://www.rfc-editor.org/rfc/rfc1235.txt"
}

@TECHREPORT{rfc1236,
AUTHOR="L. Morales and P. Hasse",
TITLE="{IP} to {X.121} address mapping for {DDN}",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1236,
PAGES=7,
DAYS=15,
MONTH=jun,
YEAR=1991,
ABSTRACT="This memo defines a standard way of converting IP addresses to
CCITT X.121 addresses and is the recommended standard for use on the
Internet, specifically for the Defense Data Network (DDN).",
URL="http://www.rfc-editor.org/rfc/rfc1236.txt"
}

@TECHREPORT{rfc1237,
AUTHOR="R. Colella and E. Gardner and R. Callon",
TITLE="Guidelines for {OSI} {NSAP} Allocation in the Internet",
TYPE="RFC",
INSTITUTION="Internet Engineering Task Force",
NUMBER=1237,
PAGES=49,
DAYS=15,
MONTH=jul,
YEAR=1991,
ABSTRACT="The Internet is moving towards a multi-protocol environment
that includes OSI. To support OSI in the Internet, an OSI lower layers
infrastructure is required. This infrastructure comprises the
connectionless network protocol (CLNP) and supporting routing protocols.
Also required as part of this infrastructure are guidelines for network
service access point (NSAP) address assignment. This paper provides
guidelines for allocating NSAPs in the Internet. This document provides
our current best judgment for the allocation of NSAP addresses in the
Internet. This is intended to guide initial deployment of OSI 8473
(Connectionless Network Layer Protocol) in the Internet, as well as to
solicit comments. It is expected that