@misc{rfc1, author="S. Crocker", title="{Host Software}", howpublished="RFC 1", series="Internet Request for Comments", type="RFC", number="1", pages="1--11", year=1969, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1.txt", key="RFC 1", doi="10.17487/RFC0001", } @misc{rfc2, author="B. Duvall", title="{Host software}", howpublished="RFC 2", series="Internet Request for Comments", type="RFC", number="2", pages="1--10", year=1969, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc2.txt", key="RFC 2", doi="10.17487/RFC0002", } @misc{rfc3, author="S.D. Crocker", title="{Documentation conventions}", howpublished="RFC 3", series="Internet Request for Comments", type="RFC", number="3", pages="1--2", year=1969, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 10", url="https://www.rfc-editor.org/rfc/rfc3.txt", key="RFC 3", doi="10.17487/RFC0003", } @misc{rfc4, author="E.B. Shapiro", title="{Network timetable}", howpublished="RFC 4", series="Internet Request for Comments", type="RFC", number="4", pages="1--6", year=1969, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc4.txt", key="RFC 4", doi="10.17487/RFC0004", } @misc{rfc5, author="J. Rulifson", title="{Decode Encode Language (DEL)}", howpublished="RFC 5", series="Internet Request for Comments", type="RFC", number="5", pages="1--17", year=1969, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc5.txt", key="RFC 5", doi="10.17487/RFC0005", } @misc{rfc6, author="S.D. Crocker", title="{Conversation with Bob Kahn}", howpublished="RFC 6", series="Internet Request for Comments", type="RFC", number="6", pages="1--1", year=1969, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc6.txt", key="RFC 6", doi="10.17487/RFC0006", } @misc{rfc7, author="G. Deloche", title="{Host-IMP interface}", howpublished="RFC 7", series="Internet Request for Comments", type="RFC", number="7", pages="1--7", year=1969, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc7.txt", key="RFC 7", doi="10.17487/RFC0007", } @misc{rfc8, author="G. Deloche", title="{ARPA Network Functional Specifications}", howpublished="RFC 8", series="Internet Request for Comments", type="RFC", number="8", year=1969, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc8.txt", key="RFC 8", doi="10.17487/RFC0008", } @misc{rfc9, author="G. Deloche", title="{Host Software}", howpublished="RFC 9", series="Internet Request for Comments", type="RFC", number="9", year=1969, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc9.txt", key="RFC 9", doi="10.17487/RFC0009", } @misc{rfc10, author="S.D. Crocker", title="{Documentation conventions}", howpublished="RFC 10", series="Internet Request for Comments", type="RFC", number="10", pages="1--3", year=1969, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 16, updated by RFCs 24, 27, 30", url="https://www.rfc-editor.org/rfc/rfc10.txt", key="RFC 10", doi="10.17487/RFC0010", } @misc{rfc11, author="G. Deloche", title="{Implementation of the Host - Host Software Procedures in GORDO}", howpublished="RFC 11", series="Internet Request for Comments", type="RFC", number="11", pages="1--23", year=1969, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 33", url="https://www.rfc-editor.org/rfc/rfc11.txt", key="RFC 11", doi="10.17487/RFC0011", } @misc{rfc12, author="M. Wingfield", title="{IMP-Host interface flow diagrams}", howpublished="RFC 12", series="Internet Request for Comments", type="RFC", number="12", pages="1--1", year=1969, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc12.txt", key="RFC 12", doi="10.17487/RFC0012", } @misc{rfc13, author="V. Cerf", title="{Zero Text Length EOF Message}", howpublished="RFC 13", series="Internet Request for Comments", type="RFC", number="13", pages="1--1", year=1969, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc13.txt", key="RFC 13", doi="10.17487/RFC0013", } @misc{rfc15, author="C.S. Carr", title="{Network subsystem for time sharing hosts}", howpublished="RFC 15", series="Internet Request for Comments", type="RFC", number="15", pages="1--5", year=1969, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc15.txt", key="RFC 15", doi="10.17487/RFC0015", } @misc{rfc16, author="S. Crocker", title="{M.I.T}", howpublished="RFC 16", series="Internet Request for Comments", type="RFC", number="16", pages="1--1", year=1969, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 24, updated by RFCs 24, 27, 30", url="https://www.rfc-editor.org/rfc/rfc16.txt", key="RFC 16", doi="10.17487/RFC0016", } @misc{rfc17, author="J.E. Kreznar", title="{Some questions re: Host-IMP Protocol}", howpublished="RFC 17", series="Internet Request for Comments", type="RFC", number="17", pages="1--4", year=1969, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc17.txt", key="RFC 17", doi="10.17487/RFC0017", } @misc{rfc18, author="V. Cerf", title="{IMP-IMP and HOST-HOST Control Links}", howpublished="RFC 18", series="Internet Request for Comments", type="RFC", number="18", pages="1--1", year=1969, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc18.txt", key="RFC 18", doi="10.17487/RFC0018", } @misc{rfc19, author="J.E. Kreznar", title="{Two protocol suggestions to reduce congestion at swap bound nodes}", howpublished="RFC 19", series="Internet Request for Comments", type="RFC", number="19", pages="1--2", year=1969, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc19.txt", key="RFC 19", doi="10.17487/RFC0019", } @misc{rfc20, author="V.G. Cerf", title="{ASCII format for network interchange}", howpublished="RFC 20 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="20", pages="1--9", year=1969, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc20.txt", key="RFC 20", doi="10.17487/RFC0020", } @misc{rfc21, author="V.G. Cerf", title="{Network meeting}", howpublished="RFC 21", series="Internet Request for Comments", type="RFC", number="21", pages="1--2", year=1969, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc21.txt", key="RFC 21", doi="10.17487/RFC0021", } @misc{rfc22, author="V.G. Cerf", title="{Host-host control message formats}", howpublished="RFC 22", series="Internet Request for Comments", type="RFC", number="22", pages="1--2", year=1969, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc22.txt", key="RFC 22", doi="10.17487/RFC0022", } @misc{rfc23, author="G. Gregg", title="{Transmission of Multiple Control Messages}", howpublished="RFC 23", series="Internet Request for Comments", type="RFC", number="23", pages="1--1", year=1969, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc23.txt", key="RFC 23", doi="10.17487/RFC0023", } @misc{rfc24, author="S.D. Crocker", title="{Documentation Conventions}", howpublished="RFC 24", series="Internet Request for Comments", type="RFC", number="24", pages="1--3", year=1969, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 27, 30", url="https://www.rfc-editor.org/rfc/rfc24.txt", key="RFC 24", doi="10.17487/RFC0024", } @misc{rfc25, author="S.D. Crocker", title="{No High Link Numbers}", howpublished="RFC 25", series="Internet Request for Comments", type="RFC", number="25", pages="1--1", year=1969, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc25.txt", key="RFC 25", doi="10.17487/RFC0025", } @misc{rfc27, author="S.D. Crocker", title="{Documentation Conventions}", howpublished="RFC 27", series="Internet Request for Comments", type="RFC", number="27", pages="1--3", year=1969, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 30", url="https://www.rfc-editor.org/rfc/rfc27.txt", key="RFC 27", doi="10.17487/RFC0027", } @misc{rfc28, author="W.K. English", title="{Time Standards}", howpublished="RFC 28", series="Internet Request for Comments", type="RFC", number="28", pages="1--1", year=1970, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc28.txt", key="RFC 28", doi="10.17487/RFC0028", } @misc{rfc29, author="R.E. Kahn", title="{Response to RFC 28}", howpublished="RFC 29", series="Internet Request for Comments", type="RFC", number="29", pages="1--1", year=1970, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc29.txt", key="RFC 29", doi="10.17487/RFC0029", } @misc{rfc30, author="S.D. Crocker", title="{Documentation Conventions}", howpublished="RFC 30", series="Internet Request for Comments", type="RFC", number="30", pages="1--3", year=1970, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc30.txt", key="RFC 30", doi="10.17487/RFC0030", } @misc{rfc31, author="D. Bobrow and W.R. Sutherland", title="{Binary Message Forms in Computer}", howpublished="RFC 31", series="Internet Request for Comments", type="RFC", number="31", pages="1--7", year=1968, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc31.txt", key="RFC 31", doi="10.17487/RFC0031", } @misc{rfc32, author="J. Cole", title="{Some Thoughts on SRI's Proposed Real Time Clock}", howpublished="RFC 32", series="Internet Request for Comments", type="RFC", number="32", pages="1--1", year=1970, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc32.txt", key="RFC 32", doi="10.17487/RFC0032", } @misc{rfc33, author="S.D. Crocker", title="{New Host-Host Protocol}", howpublished="RFC 33", series="Internet Request for Comments", type="RFC", number="33", pages="1--19", year=1970, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 36, 47", url="https://www.rfc-editor.org/rfc/rfc33.txt", key="RFC 33", doi="10.17487/RFC0033", } @misc{rfc34, author="W.K. English", title="{Some Brief Preliminary Notes on the Augmentation Research Center Clock}", howpublished="RFC 34", series="Internet Request for Comments", type="RFC", number="34", pages="1--2", year=1970, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc34.txt", key="RFC 34", doi="10.17487/RFC0034", } @misc{rfc35, author="S.D. Crocker", title="{Network Meeting}", howpublished="RFC 35 (Informational)", series="Internet Request for Comments", type="RFC", number="35", pages="1--1", year=1970, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc35.txt", key="RFC 35", doi="10.17487/RFC0035", } @misc{rfc36, author="S.D. Crocker", title="{Protocol Notes}", howpublished="RFC 36", series="Internet Request for Comments", type="RFC", number="36", pages="1--8", year=1970, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 39, 44", url="https://www.rfc-editor.org/rfc/rfc36.txt", key="RFC 36", doi="10.17487/RFC0036", } @misc{rfc37, author="S.D. Crocker", title="{Network Meeting Epilogue, etc}", howpublished="RFC 37", series="Internet Request for Comments", type="RFC", number="37", pages="1--5", year=1970, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc37.txt", key="RFC 37", doi="10.17487/RFC0037", } @misc{rfc38, author="S.M. Wolfe", title="{Comments on Network Protocol from NWG/RFC \#36}", howpublished="RFC 38", series="Internet Request for Comments", type="RFC", number="38", pages="1--1", year=1970, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc38.txt", key="RFC 38", doi="10.17487/RFC0038", } @misc{rfc39, author="E. Harslem and J.F. Heafner", title="{Comments on Protocol Re: NWG/RFC \#36}", howpublished="RFC 39", series="Internet Request for Comments", type="RFC", number="39", pages="1--3", year=1970, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc39.txt", key="RFC 39", doi="10.17487/RFC0039", } @misc{rfc40, author="E. Harslem and J.F. Heafner", title="{More Comments on the Forthcoming Protocol}", howpublished="RFC 40", series="Internet Request for Comments", type="RFC", number="40", pages="1--3", year=1970, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc40.txt", key="RFC 40", doi="10.17487/RFC0040", } @misc{rfc41, author="J.T. Melvin", title="{IMP-IMP Teletype Communication}", howpublished="RFC 41", series="Internet Request for Comments", type="RFC", number="41", pages="1--1", year=1970, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc41.txt", key="RFC 41", doi="10.17487/RFC0041", } @misc{rfc42, author="E. Ancona", title="{Message Data Types}", howpublished="RFC 42", series="Internet Request for Comments", type="RFC", number="42", pages="1--3", year=1970, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc42.txt", key="RFC 42", doi="10.17487/RFC0042", } @misc{rfc43, author="A.G. Nemeth", title="{Proposed Meeting}", howpublished="RFC 43", series="Internet Request for Comments", type="RFC", number="43", pages="1--2", year=1970, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc43.txt", key="RFC 43", doi="10.17487/RFC0043", } @misc{rfc44, author="A. Shoshani and R. Long and A. Landsberg", title="{Comments on NWG/RFC 33 and 36}", howpublished="RFC 44", series="Internet Request for Comments", type="RFC", number="44", pages="1--3", year=1970, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc44.txt", key="RFC 44", doi="10.17487/RFC0044", } @misc{rfc45, author="J. Postel and S.D. Crocker", title="{New Protocol is Coming}", howpublished="RFC 45", series="Internet Request for Comments", type="RFC", number="45", pages="1--1", year=1970, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc45.txt", key="RFC 45", doi="10.17487/RFC0045", } @misc{rfc46, author="E. Meyer", title="{ARPA Network protocol notes}", howpublished="RFC 46", series="Internet Request for Comments", type="RFC", number="46", pages="1--17", year=1970, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc46.txt", key="RFC 46", doi="10.17487/RFC0046", } @misc{rfc47, author="J. Postel and S. Crocker", title="{BBN's Comments on NWG/RFC \#33}", howpublished="RFC 47", series="Internet Request for Comments", type="RFC", number="47", pages="1--4", year=1970, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc47.txt", key="RFC 47", doi="10.17487/RFC0047", } @misc{rfc48, author="J. Postel and S.D. Crocker", title="{Possible protocol plateau}", howpublished="RFC 48", series="Internet Request for Comments", type="RFC", number="48", pages="1--18", year=1970, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc48.txt", key="RFC 48", doi="10.17487/RFC0048", } @misc{rfc49, author="E. Meyer", title="{Conversations with S. Crocker (UCLA)}", howpublished="RFC 49", series="Internet Request for Comments", type="RFC", number="49", pages="1--5", year=1970, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc49.txt", key="RFC 49", doi="10.17487/RFC0049", } @misc{rfc50, author="E. Harslen and J. Heafner", title="{Comments on the Meyer Proposal}", howpublished="RFC 50", series="Internet Request for Comments", type="RFC", number="50", pages="1--2", year=1970, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc50.txt", key="RFC 50", doi="10.17487/RFC0050", } @misc{rfc51, author="M. Elie", title="{Proposal for a Network Interchange Language}", howpublished="RFC 51", series="Internet Request for Comments", type="RFC", number="51", year=1970, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc51.txt", key="RFC 51", doi="10.17487/RFC0051", } @misc{rfc52, author="J. Postel and S.D. Crocker", title="{Updated distribution list}", howpublished="RFC 52", series="Internet Request for Comments", type="RFC", number="52", pages="1--3", year=1970, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 69", url="https://www.rfc-editor.org/rfc/rfc52.txt", key="RFC 52", doi="10.17487/RFC0052", } @misc{rfc53, author="S.D. Crocker", title="{Official protocol mechanism}", howpublished="RFC 53", series="Internet Request for Comments", type="RFC", number="53", pages="1--1", year=1970, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc53.txt", key="RFC 53", doi="10.17487/RFC0053", } @misc{rfc54, author="S.D. Crocker and J. Postel and J. Newkirk and M. Kraley", title="{Official Protocol Proffering}", howpublished="RFC 54", series="Internet Request for Comments", type="RFC", number="54", pages="1--9", year=1970, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 57", url="https://www.rfc-editor.org/rfc/rfc54.txt", key="RFC 54", doi="10.17487/RFC0054", } @misc{rfc55, author="J. Newkirk and M. Kraley and J. Postel and S.D. Crocker", title="{Prototypical implementation of the NCP}", howpublished="RFC 55", series="Internet Request for Comments", type="RFC", number="55", pages="1--23", year=1970, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc55.txt", key="RFC 55", doi="10.17487/RFC0055", } @misc{rfc56, author="E. Belove and D. Black and R. Flegal and L.G. Farquar", title="{Third Level Protocol: Logger Protocol}", howpublished="RFC 56", series="Internet Request for Comments", type="RFC", number="56", pages="1--6", year=1970, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc56.txt", key="RFC 56", doi="10.17487/RFC0056", } @misc{rfc57, author="M. Kraley and J. Newkirk", title="{Thoughts and Reflections on NWG/RFC 54}", howpublished="RFC 57", series="Internet Request for Comments", type="RFC", number="57", pages="1--5", year=1970, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc57.txt", key="RFC 57", doi="10.17487/RFC0057", } @misc{rfc58, author="T.P. Skinner", title="{Logical Message Synchronization}", howpublished="RFC 58", series="Internet Request for Comments", type="RFC", number="58", pages="1--2", year=1970, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc58.txt", key="RFC 58", doi="10.17487/RFC0058", } @misc{rfc59, author="E. Meyer", title="{Flow Control - Fixed Versus Demand Allocation}", howpublished="RFC 59", series="Internet Request for Comments", type="RFC", number="59", pages="1--7", year=1970, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc59.txt", key="RFC 59", doi="10.17487/RFC0059", } @misc{rfc60, author="R. Kalin", title="{A Simplified NCP Protocol}", howpublished="RFC 60", series="Internet Request for Comments", type="RFC", number="60", pages="1--8", year=1970, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc60.txt", key="RFC 60", doi="10.17487/RFC0060", } @misc{rfc61, author="D.C. Walden", title="{Note on Interprocess Communication in a Resource Sharing Computer Network}", howpublished="RFC 61", series="Internet Request for Comments", type="RFC", number="61", pages="1--18", year=1970, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 62", url="https://www.rfc-editor.org/rfc/rfc61.txt", key="RFC 61", doi="10.17487/RFC0061", } @misc{rfc62, author="D.C. Walden", title="{Systems for Interprocess Communication in a Resource Sharing Computer Network}", howpublished="RFC 62", series="Internet Request for Comments", type="RFC", number="62", pages="1--20", year=1970, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc62.txt", key="RFC 62", doi="10.17487/RFC0062", } @misc{rfc63, author="V.G. Cerf", title="{Belated Network Meeting Report}", howpublished="RFC 63", series="Internet Request for Comments", type="RFC", number="63", pages="1--2", year=1970, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc63.txt", key="RFC 63", doi="10.17487/RFC0063", } @misc{rfc64, author="M. Elie", title="{Getting rid of marking}", howpublished="RFC 64", series="Internet Request for Comments", type="RFC", number="64", pages="1--4", year=1970, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc64.txt", key="RFC 64", doi="10.17487/RFC0064", } @misc{rfc65, author="D.C. Walden", title="{Comments on Host/Host Protocol document \#1}", howpublished="RFC 65", series="Internet Request for Comments", type="RFC", number="65", pages="1--2", year=1970, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc65.txt", key="RFC 65", doi="10.17487/RFC0065", } @misc{rfc66, author="S.D. Crocker", title="{NIC - third level ideas and other noise}", howpublished="RFC 66", series="Internet Request for Comments", type="RFC", number="66", pages="1--3", year=1970, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 123, updated by RFCs 80, 93", url="https://www.rfc-editor.org/rfc/rfc66.txt", key="RFC 66", doi="10.17487/RFC0066", } @misc{rfc67, author="W.R. Crowther", title="{Proposed Change to Host/IMP Spec to Eliminate Marking}", howpublished="RFC 67", series="Internet Request for Comments", type="RFC", number="67", pages="1--1", year=1970, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc67.txt", key="RFC 67", doi="10.17487/RFC0067", } @misc{rfc68, author="M. Elie", title="{Comments on Memory Allocation Control Commands: CEASE, ALL, GVB, RET, and RFNM}", howpublished="RFC 68", series="Internet Request for Comments", type="RFC", number="68", pages="1--2", year=1970, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc68.txt", key="RFC 68", doi="10.17487/RFC0068", } @misc{rfc69, author="A.K. Bhushan", title="{Distribution List Change for MIT}", howpublished="RFC 69", series="Internet Request for Comments", type="RFC", number="69", pages="1--1", year=1970, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc69.txt", key="RFC 69", doi="10.17487/RFC0069", } @misc{rfc70, author="S.D. Crocker", title="{Note on Padding}", howpublished="RFC 70", series="Internet Request for Comments", type="RFC", number="70", pages="1--9", year=1970, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 228", url="https://www.rfc-editor.org/rfc/rfc70.txt", key="RFC 70", doi="10.17487/RFC0070", } @misc{rfc71, author="T. Schipper", title="{Reallocation in Case of Input Error}", howpublished="RFC 71", series="Internet Request for Comments", type="RFC", number="71", pages="1--1", year=1970, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc71.txt", key="RFC 71", doi="10.17487/RFC0071", } @misc{rfc72, author="R.D. Bressler", title="{Proposed Moratorium on Changes to Network Protocol}", howpublished="RFC 72", series="Internet Request for Comments", type="RFC", number="72", pages="1--4", year=1970, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc72.txt", key="RFC 72", doi="10.17487/RFC0072", } @misc{rfc73, author="S.D. Crocker", title="{Response to NWG/RFC 67}", howpublished="RFC 73", series="Internet Request for Comments", type="RFC", number="73", pages="1--1", year=1970, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc73.txt", key="RFC 73", doi="10.17487/RFC0073", } @misc{rfc74, author="J.E. White", title="{Specifications for Network Use of the UCSB On-Line System}", howpublished="RFC 74", series="Internet Request for Comments", type="RFC", number="74", pages="1--9", year=1970, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 217, 225", url="https://www.rfc-editor.org/rfc/rfc74.txt", key="RFC 74", doi="10.17487/RFC0074", } @misc{rfc75, author="S.D. Crocker", title="{Network Meeting}", howpublished="RFC 75", series="Internet Request for Comments", type="RFC", number="75", pages="1--1", year=1970, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc75.txt", key="RFC 75", doi="10.17487/RFC0075", } @misc{rfc76, author="J. Bouknight and J. Madden and G.R. Grossman", title="{Connection by name: User oriented protocol}", howpublished="RFC 76", series="Internet Request for Comments", type="RFC", number="76", pages="1--15", year=1970, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc76.txt", key="RFC 76", doi="10.17487/RFC0076", } @misc{rfc77, author="J. Postel", title="{Network meeting report}", howpublished="RFC 77", series="Internet Request for Comments", type="RFC", number="77", pages="1--9", year=1970, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc77.txt", key="RFC 77", doi="10.17487/RFC0077", } @misc{rfc78, author="E. Harslem and J.F. Heafner and J.E. White", title="{NCP Status Report: UCSB/Rand}", howpublished="RFC 78", series="Internet Request for Comments", type="RFC", number="78", pages="1--1", year=1970, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc78.txt", key="RFC 78", doi="10.17487/RFC0078", } @misc{rfc79, author="E. Meyer", title="{Logger Protocol error}", howpublished="RFC 79", series="Internet Request for Comments", type="RFC", number="79", pages="1--1", year=1970, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc79.txt", key="RFC 79", doi="10.17487/RFC0079", } @misc{rfc80, author="E. Harslem and J.F. Heafner", title="{Protocols and Data Formats}", howpublished="RFC 80", series="Internet Request for Comments", type="RFC", number="80", pages="1--9", year=1970, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 123, updated by RFC 93", url="https://www.rfc-editor.org/rfc/rfc80.txt", key="RFC 80", doi="10.17487/RFC0080", } @misc{rfc81, author="J. Bouknight", title="{Request for Reference Information}", howpublished="RFC 81", series="Internet Request for Comments", type="RFC", number="81", pages="1--1", year=1970, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc81.txt", key="RFC 81", doi="10.17487/RFC0081", } @misc{rfc82, author="E. Meyer", title="{Network Meeting Notes}", howpublished="RFC 82", series="Internet Request for Comments", type="RFC", number="82", pages="1--18", year=1970, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc82.txt", key="RFC 82", doi="10.17487/RFC0082", } @misc{rfc83, author="R.H. Anderson and E. Harslem and J.F. Heafner", title="{Language-machine for data reconfiguration}", howpublished="RFC 83", series="Internet Request for Comments", type="RFC", number="83", pages="1--13", year=1970, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc83.txt", key="RFC 83", doi="10.17487/RFC0083", } @misc{rfc84, author="J.B. North", title="{List of NWG/RFC's 1-80}", howpublished="RFC 84", series="Internet Request for Comments", type="RFC", number="84", pages="1--8", year=1970, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc84.txt", key="RFC 84", doi="10.17487/RFC0084", } @misc{rfc85, author="S.D. Crocker", title="{Network Working Group meeting}", howpublished="RFC 85", series="Internet Request for Comments", type="RFC", number="85", pages="1--1", year=1970, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc85.txt", key="RFC 85", doi="10.17487/RFC0085", } @misc{rfc86, author="S.D. Crocker", title="{Proposal for a Network Standard Format for a Data Stream to Control Graphics Display}", howpublished="RFC 86", series="Internet Request for Comments", type="RFC", number="86", pages="1--6", year=1971, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 125", url="https://www.rfc-editor.org/rfc/rfc86.txt", key="RFC 86", doi="10.17487/RFC0086", } @misc{rfc87, author="A. Vezza", title="{Topic for Discussion at the Next Network Working Group Meeting}", howpublished="RFC 87", series="Internet Request for Comments", type="RFC", number="87", pages="1--3", year=1971, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc87.txt", key="RFC 87", doi="10.17487/RFC0087", } @misc{rfc88, author="R.T. Braden and S.M. Wolfe", title="{NETRJS: A third level protocol for Remote Job Entry}", howpublished="RFC 88", series="Internet Request for Comments", type="RFC", number="88", pages="1--9", year=1971, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 189", url="https://www.rfc-editor.org/rfc/rfc88.txt", key="RFC 88", doi="10.17487/RFC0088", } @misc{rfc89, author="R.M. Metcalfe", title="{Some historic moments in networking}", howpublished="RFC 89", series="Internet Request for Comments", type="RFC", number="89", pages="1--7", year=1971, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc89.txt", key="RFC 89", doi="10.17487/RFC0089", } @misc{rfc90, author="R.T. Braden", title="{CCN as a Network Service Center}", howpublished="RFC 90", series="Internet Request for Comments", type="RFC", number="90", pages="1--6", year=1971, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc90.txt", key="RFC 90", doi="10.17487/RFC0090", } @misc{rfc91, author="G.H. Mealy", title="{Proposed User-User Protocol}", howpublished="RFC 91", series="Internet Request for Comments", type="RFC", number="91", pages="1--12", year=1970, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc91.txt", key="RFC 91", doi="10.17487/RFC0091", } @misc{rfc93, author="A.M. McKenzie", title="{Initial Connection Protocol}", howpublished="RFC 93", series="Internet Request for Comments", type="RFC", number="93", pages="1--1", year=1971, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc93.txt", key="RFC 93", doi="10.17487/RFC0093", } @misc{rfc94, author="E. Harslem and J.F. Heafner", title="{Some thoughts on Network Graphics}", howpublished="RFC 94", series="Internet Request for Comments", type="RFC", number="94", pages="1--6", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc94.txt", key="RFC 94", doi="10.17487/RFC0094", } @misc{rfc95, author="S. Crocker", title="{Distribution of NWG/RFC's through the NIC}", howpublished="RFC 95", series="Internet Request for Comments", type="RFC", number="95", pages="1--5", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 155", url="https://www.rfc-editor.org/rfc/rfc95.txt", key="RFC 95", doi="10.17487/RFC0095", } @misc{rfc96, author="R.W. Watson", title="{An Interactive Network Experiment to Study Modes of Access the Network Information Center}", howpublished="RFC 96 (Informational)", series="Internet Request for Comments", type="RFC", number="96", pages="1--5", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc96.txt", key="RFC 96", doi="10.17487/RFC0096", } @misc{rfc97, author="J.T. Melvin and R.W. Watson", title="{First Cut at a Proposed Telnet Protocol}", howpublished="RFC 97", series="Internet Request for Comments", type="RFC", number="97", pages="1--11", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc97.txt", key="RFC 97", doi="10.17487/RFC0097", } @misc{rfc98, author="E. Meyer and T. Skinner", title="{Logger Protocol Proposal}", howpublished="RFC 98", series="Internet Request for Comments", type="RFC", number="98", pages="1--10", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 123", url="https://www.rfc-editor.org/rfc/rfc98.txt", key="RFC 98", doi="10.17487/RFC0098", } @misc{rfc99, author="P.M. Karp", title="{Network Meeting}", howpublished="RFC 99", series="Internet Request for Comments", type="RFC", number="99", pages="1--1", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 116", url="https://www.rfc-editor.org/rfc/rfc99.txt", key="RFC 99", doi="10.17487/RFC0099", } @misc{rfc100, author="P.M. Karp", title="{Categorization and guide to NWG/RFCs}", howpublished="RFC 100", series="Internet Request for Comments", type="RFC", number="100", pages="1--37", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc100.txt", key="RFC 100", doi="10.17487/RFC0100", } @misc{rfc101, author="R.W. Watson", title="{Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971}", howpublished="RFC 101", series="Internet Request for Comments", type="RFC", number="101", pages="1--14", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 108, 123", url="https://www.rfc-editor.org/rfc/rfc101.txt", key="RFC 101", doi="10.17487/RFC0101", } @misc{rfc102, author="S.D. Crocker", title="{Output of the Host-Host Protocol glitch cleaning committee}", howpublished="RFC 102", series="Internet Request for Comments", type="RFC", number="102", pages="1--4", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 107", url="https://www.rfc-editor.org/rfc/rfc102.txt", key="RFC 102", doi="10.17487/RFC0102", } @misc{rfc103, author="R.B. Kalin", title="{Implementation of Interrupt Keys}", howpublished="RFC 103", series="Internet Request for Comments", type="RFC", number="103", pages="1--4", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc103.txt", key="RFC 103", doi="10.17487/RFC0103", } @misc{rfc104, author="J.B. Postel and S.D. Crocker", title="{Link 191}", howpublished="RFC 104", series="Internet Request for Comments", type="RFC", number="104", pages="1--1", year=1971, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc104.txt", key="RFC 104", doi="10.17487/RFC0104", } @misc{rfc105, author="J.E. White", title="{Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB}", howpublished="RFC 105", series="Internet Request for Comments", type="RFC", number="105", pages="1--9", year=1971, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 217", url="https://www.rfc-editor.org/rfc/rfc105.txt", key="RFC 105", doi="10.17487/RFC0105", } @misc{rfc106, author="T.C. O'Sullivan", title="{User/Server Site Protocol Network Host Questionnaire}", howpublished="RFC 106", series="Internet Request for Comments", type="RFC", number="106", pages="1--5", year=1971, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc106.txt", key="RFC 106", doi="10.17487/RFC0106", } @misc{rfc107, author="R.D. Bressler and S.D. Crocker and W.R. Crowther and G.R. Grossman and R.S. Tomlinson and J.E. White", title="{Output of the Host-Host Protocol Glitch Cleaning Committee}", howpublished="RFC 107", series="Internet Request for Comments", type="RFC", number="107", pages="1--12", year=1971, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 111, 124, 132, 154, 179", url="https://www.rfc-editor.org/rfc/rfc107.txt", key="RFC 107", doi="10.17487/RFC0107", } @misc{rfc108, author="R.W. Watson", title="{Attendance list at the Urbana NWG meeting, February 17-19, 1971}", howpublished="RFC 108", series="Internet Request for Comments", type="RFC", number="108", pages="1--2", year=1971, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc108.txt", key="RFC 108", doi="10.17487/RFC0108", } @misc{rfc109, author="J. Winett", title="{Level III Server Protocol for the Lincoln Laboratory 360/67 Host}", howpublished="RFC 109", series="Internet Request for Comments", type="RFC", number="109", pages="1--12", year=1971, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc109.txt", key="RFC 109", doi="10.17487/RFC0109", } @misc{rfc110, author="J. Winett", title="{Conventions for Using an IBM 2741 Terminal as a User Console for Access to Network Server Hosts}", howpublished="RFC 110", series="Internet Request for Comments", type="RFC", number="110", pages="1--4", year=1971, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 135", url="https://www.rfc-editor.org/rfc/rfc110.txt", key="RFC 110", doi="10.17487/RFC0110", } @misc{rfc111, author="S.D. Crocker", title="{Pressure from the Chairman}", howpublished="RFC 111", series="Internet Request for Comments", type="RFC", number="111", pages="1--2", year=1971, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 130", url="https://www.rfc-editor.org/rfc/rfc111.txt", key="RFC 111", doi="10.17487/RFC0111", } @misc{rfc112, author="T.C. O'Sullivan", title="{User/Server Site Protocol: Network Host Questionnaire}", howpublished="RFC 112", series="Internet Request for Comments", type="RFC", number="112", pages="1--1", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc112.txt", key="RFC 112", doi="10.17487/RFC0112", } @misc{rfc113, author="E. Harslem and J.F. Heafner and J.E. White", title="{Network activity report: UCSB Rand}", howpublished="RFC 113", series="Internet Request for Comments", type="RFC", number="113", pages="1--2", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 227", url="https://www.rfc-editor.org/rfc/rfc113.txt", key="RFC 113", doi="10.17487/RFC0113", } @misc{rfc114, author="A.K. Bhushan", title="{File Transfer Protocol}", howpublished="RFC 114", series="Internet Request for Comments", type="RFC", number="114", pages="1--17", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 133, 141, 171, 172", url="https://www.rfc-editor.org/rfc/rfc114.txt", key="RFC 114", keywords="FTP", doi="10.17487/RFC0114", } @misc{rfc115, author="R.W. Watson and J.B. North", title="{Some Network Information Center policies on handling documents}", howpublished="RFC 115", series="Internet Request for Comments", type="RFC", number="115", pages="1--8", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc115.txt", key="RFC 115", doi="10.17487/RFC0115", } @misc{rfc116, author="S.D. Crocker", title="{Structure of the May NWG Meeting}", howpublished="RFC 116", series="Internet Request for Comments", type="RFC", number="116", pages="1--1", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 131, 156", url="https://www.rfc-editor.org/rfc/rfc116.txt", key="RFC 116", doi="10.17487/RFC0116", } @misc{rfc117, author="J. Wong", title="{Some comments on the official protocol}", howpublished="RFC 117", series="Internet Request for Comments", type="RFC", number="117", pages="1--5", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc117.txt", key="RFC 117", doi="10.17487/RFC0117", } @misc{rfc118, author="R.W. Watson", title="{Recommendations for facility documentation}", howpublished="RFC 118", series="Internet Request for Comments", type="RFC", number="118", pages="1--2", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc118.txt", key="RFC 118", doi="10.17487/RFC0118", } @misc{rfc119, author="M. Krilanovich", title="{Network Fortran Subprograms}", howpublished="RFC 119", series="Internet Request for Comments", type="RFC", number="119", pages="1--19", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc119.txt", key="RFC 119", doi="10.17487/RFC0119", } @misc{rfc120, author="M. Krilanovich", title="{Network PL1 subprograms}", howpublished="RFC 120", series="Internet Request for Comments", type="RFC", number="120", pages="1--16", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc120.txt", key="RFC 120", doi="10.17487/RFC0120", } @misc{rfc121, author="M. Krilanovich", title="{Network on-line operators}", howpublished="RFC 121", series="Internet Request for Comments", type="RFC", number="121", pages="1--13", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc121.txt", key="RFC 121", doi="10.17487/RFC0121", } @misc{rfc122, author="J.E. White", title="{Network specifications for UCSB's Simple-Minded File System}", howpublished="RFC 122", series="Internet Request for Comments", type="RFC", number="122", pages="1--21", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 217, 269, 399, 431", url="https://www.rfc-editor.org/rfc/rfc122.txt", key="RFC 122", doi="10.17487/RFC0122", } @misc{rfc123, author="S.D. Crocker", title="{Proffered Official ICP}", howpublished="RFC 123", series="Internet Request for Comments", type="RFC", number="123", pages="1--3", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 165, updated by RFCs 127, 143, 148", url="https://www.rfc-editor.org/rfc/rfc123.txt", key="RFC 123", doi="10.17487/RFC0123", } @misc{rfc124, author="J.T. Melvin", title="{Typographical error in RFC 107}", howpublished="RFC 124", series="Internet Request for Comments", type="RFC", number="124", pages="1--1", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc124.txt", key="RFC 124", doi="10.17487/RFC0124", } @misc{rfc125, author="J. McConnell", title="{Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream}", howpublished="RFC 125", series="Internet Request for Comments", type="RFC", number="125", pages="1--4", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 177", url="https://www.rfc-editor.org/rfc/rfc125.txt", key="RFC 125", doi="10.17487/RFC0125", } @misc{rfc126, author="J. McConnell", title="{Graphics Facilities at Ames Research Center}", howpublished="RFC 126", series="Internet Request for Comments", type="RFC", number="126", pages="1--1", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc126.txt", key="RFC 126", doi="10.17487/RFC0126", } @misc{rfc127, author="J. Postel", title="{Comments on RFC 123}", howpublished="RFC 127", series="Internet Request for Comments", type="RFC", number="127", pages="1--2", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 145, updated by RFC 151", url="https://www.rfc-editor.org/rfc/rfc127.txt", key="RFC 127", doi="10.17487/RFC0127", } @misc{rfc128, author="J. Postel", title="{Bytes}", howpublished="RFC 128", series="Internet Request for Comments", type="RFC", number="128", pages="1--2", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc128.txt", key="RFC 128", doi="10.17487/RFC0128", } @misc{rfc129, author="E. Harslem and J. Heafner and E. Meyer", title="{Request for comments on socket name structure}", howpublished="RFC 129", series="Internet Request for Comments", type="RFC", number="129", pages="1--6", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 147", url="https://www.rfc-editor.org/rfc/rfc129.txt", key="RFC 129", doi="10.17487/RFC0129", } @misc{rfc130, author="J.F. Heafner", title="{Response to RFC 111: Pressure from the chairman}", howpublished="RFC 130", series="Internet Request for Comments", type="RFC", number="130", pages="1--1", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc130.txt", key="RFC 130", doi="10.17487/RFC0130", } @misc{rfc131, author="E. Harslem and J.F. Heafner", title="{Response to RFC 116: May NWG meeting}", howpublished="RFC 131", series="Internet Request for Comments", type="RFC", number="131", pages="1--3", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc131.txt", key="RFC 131", doi="10.17487/RFC0131", } @misc{rfc132, author="J.E. White", title="{Typographical Error in RFC 107}", howpublished="RFC 132", series="Internet Request for Comments", type="RFC", number="132", pages="1--1", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 154", url="https://www.rfc-editor.org/rfc/rfc132.txt", key="RFC 132", doi="10.17487/RFC0132", } @misc{rfc133, author="R.L. Sunberg", title="{File Transfer and Error Recovery}", howpublished="RFC 133", series="Internet Request for Comments", type="RFC", number="133", pages="1--4", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc133.txt", key="RFC 133", keywords="FTP", doi="10.17487/RFC0133", } @misc{rfc134, author="A. Vezza", title="{Network Graphics meeting}", howpublished="RFC 134", series="Internet Request for Comments", type="RFC", number="134", pages="1--2", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc134.txt", key="RFC 134", doi="10.17487/RFC0134", } @misc{rfc135, author="W. Hathaway", title="{Response to NWG/RFC 110}", howpublished="RFC 135", series="Internet Request for Comments", type="RFC", number="135", pages="1--3", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc135.txt", key="RFC 135", doi="10.17487/RFC0135", } @misc{rfc136, author="R.E. Kahn", title="{Host accounting and administrative procedures}", howpublished="RFC 136", series="Internet Request for Comments", type="RFC", number="136", pages="1--4", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc136.txt", key="RFC 136", doi="10.17487/RFC0136", } @misc{rfc137, author="T.C. O'Sullivan", title="{Telnet Protocol - a proposed document}", howpublished="RFC 137", series="Internet Request for Comments", type="RFC", number="137", pages="1--11", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 139", url="https://www.rfc-editor.org/rfc/rfc137.txt", key="RFC 137", doi="10.17487/RFC0137", } @misc{rfc138, author="R.H. Anderson and V.G. Cerf and E. Harslem and J.F. Heafner and J. Madden and R.M. Metcalfe and A. Shoshani and J.E. White and D.C.M. Wood", title="{Status report on proposed Data Reconfiguration Service}", howpublished="RFC 138", series="Internet Request for Comments", type="RFC", number="138", pages="1--23", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc138.txt", key="RFC 138", doi="10.17487/RFC0138", } @misc{rfc139, author="T.C. O'Sullivan", title="{Discussion of Telnet Protocol}", howpublished="RFC 139", series="Internet Request for Comments", type="RFC", number="139", pages="1--11", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 158", url="https://www.rfc-editor.org/rfc/rfc139.txt", key="RFC 139", doi="10.17487/RFC0139", } @misc{rfc140, author="S.D. Crocker", title="{Agenda for the May NWG meeting}", howpublished="RFC 140", series="Internet Request for Comments", type="RFC", number="140", pages="1--4", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 149", url="https://www.rfc-editor.org/rfc/rfc140.txt", key="RFC 140", doi="10.17487/RFC0140", } @misc{rfc141, author="E. Harslem and J.F. Heafner", title="{Comments on RFC 114: A File Transfer Protocol}", howpublished="RFC 141", series="Internet Request for Comments", type="RFC", number="141", pages="1--2", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc141.txt", key="RFC 141", keywords="FTP", doi="10.17487/RFC0141", } @misc{rfc142, author="C. Kline and J. Wong", title="{Time-Out Mechanism in the Host-Host Protocol}", howpublished="RFC 142", series="Internet Request for Comments", type="RFC", number="142", pages="1--2", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc142.txt", key="RFC 142", doi="10.17487/RFC0142", } @misc{rfc143, author="W. Naylor and J. Wong and C. Kline and J. Postel", title="{Regarding proffered official ICP}", howpublished="RFC 143", series="Internet Request for Comments", type="RFC", number="143", pages="1--4", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 165", url="https://www.rfc-editor.org/rfc/rfc143.txt", key="RFC 143", doi="10.17487/RFC0143", } @misc{rfc144, author="A. Shoshani", title="{Data sharing on computer networks}", howpublished="RFC 144", series="Internet Request for Comments", type="RFC", number="144", pages="1--6", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc144.txt", key="RFC 144", doi="10.17487/RFC0144", } @misc{rfc145, author="J. Postel", title="{Initial Connection Protocol Control Commands}", howpublished="RFC 145", series="Internet Request for Comments", type="RFC", number="145", pages="1--2", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 165, updated by RFC 143", url="https://www.rfc-editor.org/rfc/rfc145.txt", key="RFC 145", doi="10.17487/RFC0145", } @misc{rfc146, author="P.M. Karp and D.B. McKay and D.C.M. Wood", title="{Views on issues relevant to data sharing on computer networks}", howpublished="RFC 146", series="Internet Request for Comments", type="RFC", number="146", pages="1--6", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc146.txt", key="RFC 146", doi="10.17487/RFC0146", } @misc{rfc147, author="J.M. Winett", title="{Definition of a socket}", howpublished="RFC 147", series="Internet Request for Comments", type="RFC", number="147", pages="1--3", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc147.txt", key="RFC 147", doi="10.17487/RFC0147", } @misc{rfc148, author="A.K. Bhushan", title="{Comments on RFC 123}", howpublished="RFC 148", series="Internet Request for Comments", type="RFC", number="148", pages="1--1", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc148.txt", key="RFC 148", doi="10.17487/RFC0148", } @misc{rfc149, author="S.D. Crocker", title="{Best Laid Plans}", howpublished="RFC 149", series="Internet Request for Comments", type="RFC", number="149", pages="1--1", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc149.txt", key="RFC 149", doi="10.17487/RFC0149", } @misc{rfc150, author="R.B. Kalin", title="{Use of IPC Facilities: A Working Paper}", howpublished="RFC 150", series="Internet Request for Comments", type="RFC", number="150", pages="1--11", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc150.txt", key="RFC 150", doi="10.17487/RFC0150", } @misc{rfc151, author="A. Shoshani", title="{Comments on a proffered official ICP: RFCs 123, 127}", howpublished="RFC 151", series="Internet Request for Comments", type="RFC", number="151", pages="1--2", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc151.txt", key="RFC 151", doi="10.17487/RFC0151", } @misc{rfc152, author="M. Wilber", title="{SRI Artificial Intelligence status report}", howpublished="RFC 152", series="Internet Request for Comments", type="RFC", number="152", pages="1--1", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc152.txt", key="RFC 152", doi="10.17487/RFC0152", } @misc{rfc153, author="J.T. Melvin and R.W. Watson", title="{SRI ARC-NIC status}", howpublished="RFC 153", series="Internet Request for Comments", type="RFC", number="153", pages="1--4", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc153.txt", key="RFC 153", doi="10.17487/RFC0153", } @misc{rfc154, author="S.D. Crocker", title="{Exposition Style}", howpublished="RFC 154", series="Internet Request for Comments", type="RFC", number="154", pages="1--1", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc154.txt", key="RFC 154", doi="10.17487/RFC0154", } @misc{rfc155, author="J.B. North", title="{ARPA Network mailing lists}", howpublished="RFC 155", series="Internet Request for Comments", type="RFC", number="155", pages="1--13", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 168", url="https://www.rfc-editor.org/rfc/rfc155.txt", key="RFC 155", doi="10.17487/RFC0155", } @misc{rfc156, author="J. Bouknight", title="{Status of the Illinois site: Response to RFC 116}", howpublished="RFC 156", series="Internet Request for Comments", type="RFC", number="156", pages="1--1", year=1971, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc156.txt", key="RFC 156", doi="10.17487/RFC0156", } @misc{rfc157, author="V.G. Cerf", title="{Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems}", howpublished="RFC 157", series="Internet Request for Comments", type="RFC", number="157", pages="1--2", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc157.txt", key="RFC 157", doi="10.17487/RFC0157", } @misc{rfc158, author="T.C. O'Sullivan", title="{Telnet Protocol: A Proposed Document}", howpublished="RFC 158", series="Internet Request for Comments", type="RFC", number="158", pages="1--11", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 495, updated by RFC 318", url="https://www.rfc-editor.org/rfc/rfc158.txt", key="RFC 158", doi="10.17487/RFC0158", } @misc{rfc160, author="Network Information Center. Stanford Research Institute", title="{RFC brief list}", howpublished="RFC 160", series="Internet Request for Comments", type="RFC", number="160", pages="1--4", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 200, 999", url="https://www.rfc-editor.org/rfc/rfc160.txt", key="RFC 160", doi="10.17487/RFC0160", } @misc{rfc161, author="A. Shoshani", title="{Solution to the race condition in the ICP}", howpublished="RFC 161", series="Internet Request for Comments", type="RFC", number="161", pages="1--1", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc161.txt", key="RFC 161", doi="10.17487/RFC0161", } @misc{rfc162, author="M. Kampe", title="{NETBUGGER3}", howpublished="RFC 162", series="Internet Request for Comments", type="RFC", number="162", pages="1--2", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc162.txt", key="RFC 162", doi="10.17487/RFC0162", } @misc{rfc163, author="V.G. Cerf", title="{Data transfer protocols}", howpublished="RFC 163", series="Internet Request for Comments", type="RFC", number="163", pages="1--3", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc163.txt", key="RFC 163", keywords="FTP, DTP, data, manager", doi="10.17487/RFC0163", } @misc{rfc164, author="J.F. Heafner", title="{Minutes of Network Working Group meeting, 5/16 through 5/19/71}", howpublished="RFC 164", series="Internet Request for Comments", type="RFC", number="164", pages="1--32", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc164.txt", key="RFC 164", doi="10.17487/RFC0164", } @misc{rfc165, author="J. Postel", title="{Proffered Official Initial Connection Protocol}", howpublished="RFC 165", series="Internet Request for Comments", type="RFC", number="165", pages="1--5", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC NaN", url="https://www.rfc-editor.org/rfc/rfc165.txt", key="RFC 165", doi="10.17487/RFC0165", } @misc{rfc166, author="R.H. Anderson and V.G. Cerf and E. Harslem and J.F. Heafner and J. Madden and R.M. Metcalfe and A. Shoshani and J.E. White and D.C.M. Wood", title="{Data Reconfiguration Service: An implementation specification}", howpublished="RFC 166", series="Internet Request for Comments", type="RFC", number="166", pages="1--20", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc166.txt", key="RFC 166", doi="10.17487/RFC0166", } @misc{rfc167, author="A.K. Bhushan and R.M. Metcalfe and J.M. Winett", title="{Socket conventions reconsidered}", howpublished="RFC 167", series="Internet Request for Comments", type="RFC", number="167", pages="1--4", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc167.txt", key="RFC 167", doi="10.17487/RFC0167", } @misc{rfc168, author="J.B. North", title="{ARPA Network mailing lists}", howpublished="RFC 168", series="Internet Request for Comments", type="RFC", number="168", pages="1--7", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 211", url="https://www.rfc-editor.org/rfc/rfc168.txt", key="RFC 168", doi="10.17487/RFC0168", } @misc{rfc169, author="S.D. Crocker", title="{COMPUTER NETWORKS}", howpublished="RFC 169", series="Internet Request for Comments", type="RFC", number="169", pages="1--4", year=1971, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc169.txt", key="RFC 169", doi="10.17487/RFC0169", } @misc{rfc170, author="Network Information Center. Stanford Research Institute", title="{RFC List by Number}", howpublished="RFC 170", series="Internet Request for Comments", type="RFC", number="170", pages="1--6", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 200", url="https://www.rfc-editor.org/rfc/rfc170.txt", key="RFC 170", doi="10.17487/RFC0170", } @misc{rfc171, author="A. Bhushan and B. Braden and W. Crowther and E. Harslem and J. Heafner and A. McKenize and J. Melvin and B. Sundberg and D. Watson and J. White", title="{The Data Transfer Protocol}", howpublished="RFC 171", series="Internet Request for Comments", type="RFC", number="171", pages="1--9", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 264, updated by RFC 238", url="https://www.rfc-editor.org/rfc/rfc171.txt", key="RFC 171", keywords="FTP, DTP", doi="10.17487/RFC0171", } @misc{rfc172, author="A. Bhushan and B. Braden and W. Crowther and E. Harslem and J. Heafner and A. McKenzie and J. Melvin and B. Sundberg and D. Watson and J. White", title="{The File Transfer Protocol}", howpublished="RFC 172", series="Internet Request for Comments", type="RFC", number="172", pages="1--12", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 265, updated by RFC 238", url="https://www.rfc-editor.org/rfc/rfc172.txt", key="RFC 172", keywords="FTP", doi="10.17487/RFC0172", } @misc{rfc173, author="P.M. Karp and D.B. McKay", title="{Network Data Management Committee Meeting Announcement}", howpublished="RFC 173", series="Internet Request for Comments", type="RFC", number="173", pages="1--2", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc173.txt", key="RFC 173", doi="10.17487/RFC0173", } @misc{rfc174, author="J. Postel and V.G. Cerf", title="{UCLA - Computer Science Graphics Overview}", howpublished="RFC 174", series="Internet Request for Comments", type="RFC", number="174", pages="1--3", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc174.txt", key="RFC 174", doi="10.17487/RFC0174", } @misc{rfc175, author="E. Harslem and J.F. Heafner", title="{Comments on ``Socket Conventions Reconsidered''}", howpublished="RFC 175", series="Internet Request for Comments", type="RFC", number="175", pages="1--1", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc175.txt", key="RFC 175", doi="10.17487/RFC0175", } @misc{rfc176, author="A.K. Bhushan and R. Kanodia and R.M. Metcalfe and J. Postel", title="{Comments on ``Byte size for connections''}", howpublished="RFC 176", series="Internet Request for Comments", type="RFC", number="176", pages="1--5", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc176.txt", key="RFC 176", doi="10.17487/RFC0176", } @misc{rfc177, author="J. McConnell", title="{Device independent graphical display description}", howpublished="RFC 177", series="Internet Request for Comments", type="RFC", number="177", pages="1--9", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 181", url="https://www.rfc-editor.org/rfc/rfc177.txt", key="RFC 177", doi="10.17487/RFC0177", } @misc{rfc178, author="I.W. Cotton", title="{Network graphic attention handling}", howpublished="RFC 178", series="Internet Request for Comments", type="RFC", number="178", pages="1--11", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc178.txt", key="RFC 178", doi="10.17487/RFC0178", } @misc{rfc179, author="A.M. McKenzie", title="{Link Number Assignments}", howpublished="RFC 179", series="Internet Request for Comments", type="RFC", number="179", pages="1--1", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc179.txt", key="RFC 179", doi="10.17487/RFC0179", } @misc{rfc180, author="A.M. McKenzie", title="{File system questionnaire}", howpublished="RFC 180", series="Internet Request for Comments", type="RFC", number="180", pages="1--4", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc180.txt", key="RFC 180", doi="10.17487/RFC0180", } @misc{rfc181, author="J. McConnell", title="{Modifications to RFC 177}", howpublished="RFC 181", series="Internet Request for Comments", type="RFC", number="181", pages="1--3", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc181.txt", key="RFC 181", doi="10.17487/RFC0181", } @misc{rfc182, author="J.B. North", title="{Compilation of list of relevant site reports}", howpublished="RFC 182", series="Internet Request for Comments", type="RFC", number="182", pages="1--1", year=1971, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc182.txt", key="RFC 182", doi="10.17487/RFC0182", } @misc{rfc183, author="J.M. Winett", title="{EBCDIC Codes and Their Mapping to ASCII}", howpublished="RFC 183", series="Internet Request for Comments", type="RFC", number="183", pages="1--12", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc183.txt", key="RFC 183", doi="10.17487/RFC0183", } @misc{rfc184, author="K.C. Kelley", title="{Proposed graphic display modes}", howpublished="RFC 184", series="Internet Request for Comments", type="RFC", number="184", pages="1--7", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc184.txt", key="RFC 184", doi="10.17487/RFC0184", } @misc{rfc185, author="J.B. North", title="{NIC distribution of manuals and handbooks}", howpublished="RFC 185", series="Internet Request for Comments", type="RFC", number="185", pages="1--1", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc185.txt", key="RFC 185", doi="10.17487/RFC0185", } @misc{rfc186, author="J.C. Michener", title="{Network graphics loader}", howpublished="RFC 186", series="Internet Request for Comments", type="RFC", number="186", pages="1--17", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc186.txt", key="RFC 186", doi="10.17487/RFC0186", } @misc{rfc187, author="D.B. McKay and D.P. Karp", title="{Network/440 Protocol Concept}", howpublished="RFC 187", series="Internet Request for Comments", type="RFC", number="187", pages="1--11", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc187.txt", key="RFC 187", doi="10.17487/RFC0187", } @misc{rfc188, author="P.M. Karp and D.B. McKay", title="{Data management meeting announcement}", howpublished="RFC 188", series="Internet Request for Comments", type="RFC", number="188", pages="1--2", year=1971, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc188.txt", key="RFC 188", doi="10.17487/RFC0188", } @misc{rfc189, author="R.T. Braden", title="{Interim NETRJS specifications}", howpublished="RFC 189", series="Internet Request for Comments", type="RFC", number="189", pages="1--19", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 599, updated by RFC 283", url="https://www.rfc-editor.org/rfc/rfc189.txt", key="RFC 189", doi="10.17487/RFC0189", } @misc{rfc190, author="L.P. Deutsch", title="{DEC PDP-10-IMLAC communications system}", howpublished="RFC 190", series="Internet Request for Comments", type="RFC", number="190", pages="1--16", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc190.txt", key="RFC 190", doi="10.17487/RFC0190", } @misc{rfc191, author="C.H. Irby", title="{Graphics implementation and conceptualization at Augmentation Research Center}", howpublished="RFC 191", series="Internet Request for Comments", type="RFC", number="191", pages="1--4", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc191.txt", key="RFC 191", doi="10.17487/RFC0191", } @misc{rfc192, author="R.W. Watson", title="{Some factors which a Network Graphics Protocol must consider}", howpublished="RFC 192", series="Internet Request for Comments", type="RFC", number="192", pages="1--19", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc192.txt", key="RFC 192", doi="10.17487/RFC0192", } @misc{rfc193, author="E. Harslem and J.F. Heafner", title="{NETWORK CHECKOUT}", howpublished="RFC 193", series="Internet Request for Comments", type="RFC", number="193", pages="1--2", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 198, updated by RFC 198", url="https://www.rfc-editor.org/rfc/rfc193.txt", key="RFC 193", doi="10.17487/RFC0193", } @misc{rfc194, author="V. Cerf and E. Harslem and J. Heafner and B. Metcalfe and J. White", title="{The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes}", howpublished="RFC 194", series="Internet Request for Comments", type="RFC", number="194", pages="1--18", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc194.txt", key="RFC 194", doi="10.17487/RFC0194", } @misc{rfc195, author="G.H. Mealy", title="{Data computers-data descriptions and access language}", howpublished="RFC 195", series="Internet Request for Comments", type="RFC", number="195", pages="1--4", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc195.txt", key="RFC 195", doi="10.17487/RFC0195", } @misc{rfc196, author="R.W. Watson", title="{Mail Box Protocol}", howpublished="RFC 196", series="Internet Request for Comments", type="RFC", number="196", pages="1--4", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 221", url="https://www.rfc-editor.org/rfc/rfc196.txt", key="RFC 196", doi="10.17487/RFC0196", } @misc{rfc197, author="A. Shoshani and E. Harslem", title="{Initial Connection Protocol - Reviewed}", howpublished="RFC 197", series="Internet Request for Comments", type="RFC", number="197", pages="1--5", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc197.txt", key="RFC 197", doi="10.17487/RFC0197", } @misc{rfc198, author="J.F. Heafner", title="{Site Certification - Lincoln Labs 360/67}", howpublished="RFC 198", series="Internet Request for Comments", type="RFC", number="198", pages="1--1", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 214", url="https://www.rfc-editor.org/rfc/rfc198.txt", key="RFC 198", doi="10.17487/RFC0198", } @misc{rfc199, author="T. Williams", title="{Suggestions for a Network Data-Tablet Graphics Protocol}", howpublished="RFC 199", series="Internet Request for Comments", type="RFC", number="199", pages="1--10", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc199.txt", key="RFC 199", doi="10.17487/RFC0199", } @misc{rfc200, author="J.B. North", title="{RFC list by number}", howpublished="RFC 200", series="Internet Request for Comments", type="RFC", number="200", pages="1--7", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC NaN", url="https://www.rfc-editor.org/rfc/rfc200.txt", key="RFC 200", doi="10.17487/RFC0200", } @misc{rfc202, author="S.M. Wolfe and J. Postel", title="{Possible Deadlock in ICP}", howpublished="RFC 202", series="Internet Request for Comments", type="RFC", number="202", pages="1--2", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc202.txt", key="RFC 202", doi="10.17487/RFC0202", } @misc{rfc203, author="R.B. Kalin", title="{Achieving reliable communication}", howpublished="RFC 203", series="Internet Request for Comments", type="RFC", number="203", pages="1--4", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc203.txt", key="RFC 203", doi="10.17487/RFC0203", } @misc{rfc204, author="J. Postel", title="{Sockets in use}", howpublished="RFC 204", series="Internet Request for Comments", type="RFC", number="204", pages="1--1", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 234", url="https://www.rfc-editor.org/rfc/rfc204.txt", key="RFC 204", doi="10.17487/RFC0204", } @misc{rfc205, author="R.T. Braden", title="{NETCRT - a character display protocol}", howpublished="RFC 205", series="Internet Request for Comments", type="RFC", number="205", pages="1--13", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc205.txt", key="RFC 205", doi="10.17487/RFC0205", } @misc{rfc206, author="J. White", title="{A User TELNET Description of an Initial Implementation}", howpublished="RFC 206", series="Internet Request for Comments", type="RFC", number="206", pages="1--14", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc206.txt", key="RFC 206", doi="10.17487/RFC0206", } @misc{rfc207, author="A. Vezza", title="{September Network Working Group meeting}", howpublished="RFC 207", series="Internet Request for Comments", type="RFC", number="207", pages="1--2", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 212", url="https://www.rfc-editor.org/rfc/rfc207.txt", key="RFC 207", doi="10.17487/RFC0207", } @misc{rfc208, author="A.M. McKenzie", title="{Address tables}", howpublished="RFC 208", series="Internet Request for Comments", type="RFC", number="208", pages="1--3", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc208.txt", key="RFC 208", doi="10.17487/RFC0208", } @misc{rfc209, author="B. Cosell", title="{Host/IMP interface documentation}", howpublished="RFC 209", series="Internet Request for Comments", type="RFC", number="209", pages="1--1", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc209.txt", key="RFC 209", doi="10.17487/RFC0209", } @misc{rfc210, author="W. Conrad", title="{Improvement of Flow Control}", howpublished="RFC 210", series="Internet Request for Comments", type="RFC", number="210", pages="1--2", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc210.txt", key="RFC 210", doi="10.17487/RFC0210", } @misc{rfc211, author="J.B. North", title="{ARPA Network Mailing Lists}", howpublished="RFC 211", series="Internet Request for Comments", type="RFC", number="211", pages="1--13", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 300", url="https://www.rfc-editor.org/rfc/rfc211.txt", key="RFC 211", doi="10.17487/RFC0211", } @misc{rfc212, author="Information Sciences Institute University of Southern California", title="{NWG meeting on network usage}", howpublished="RFC 212", series="Internet Request for Comments", type="RFC", number="212", pages="1--2", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 222", url="https://www.rfc-editor.org/rfc/rfc212.txt", key="RFC 212", doi="10.17487/RFC0212", } @misc{rfc213, author="B. Cosell", title="{IMP System change notification}", howpublished="RFC 213", series="Internet Request for Comments", type="RFC", number="213", pages="1--1", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc213.txt", key="RFC 213", doi="10.17487/RFC0213", } @misc{rfc214, author="E. Harslem", title="{Network checkpoint}", howpublished="RFC 214", series="Internet Request for Comments", type="RFC", number="214", pages="1--2", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc214.txt", key="RFC 214", doi="10.17487/RFC0214", } @misc{rfc215, author="A.M. McKenzie", title="{NCP, ICP, and Telnet: The Terminal IMP implementation}", howpublished="RFC 215", series="Internet Request for Comments", type="RFC", number="215", pages="1--7", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc215.txt", key="RFC 215", doi="10.17487/RFC0215", } @misc{rfc216, author="J.E. White", title="{Telnet Access to UCSB's On-Line System}", howpublished="RFC 216", series="Internet Request for Comments", type="RFC", number="216", pages="1--16", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc216.txt", key="RFC 216", doi="10.17487/RFC0216", } @misc{rfc217, author="J.E. White", title="{Specifications changes for OLS, RJE/RJOR, and SMFS}", howpublished="RFC 217", series="Internet Request for Comments", type="RFC", number="217", pages="1--2", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc217.txt", key="RFC 217", doi="10.17487/RFC0217", } @misc{rfc218, author="B. Cosell", title="{Changing the IMP status reporting facility}", howpublished="RFC 218", series="Internet Request for Comments", type="RFC", number="218", pages="1--1", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc218.txt", key="RFC 218", doi="10.17487/RFC0218", } @misc{rfc219, author="R. Winter", title="{User's View of the Datacomputer}", howpublished="RFC 219", series="Internet Request for Comments", type="RFC", number="219", pages="1--7", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc219.txt", key="RFC 219", doi="10.17487/RFC0219", } @misc{rfc221, author="R.W. Watson", title="{Mail Box Protocol: Version 2}", howpublished="RFC 221", series="Internet Request for Comments", type="RFC", number="221", pages="1--5", year=1971, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 278", url="https://www.rfc-editor.org/rfc/rfc221.txt", key="RFC 221", doi="10.17487/RFC0221", } @misc{rfc222, author="R.M. Metcalfe", title="{Subject: System programmer's workshop}", howpublished="RFC 222", series="Internet Request for Comments", type="RFC", number="222", pages="1--2", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 234", url="https://www.rfc-editor.org/rfc/rfc222.txt", key="RFC 222", doi="10.17487/RFC0222", } @misc{rfc223, author="J.T. Melvin and R.W. Watson", title="{Network Information Center schedule for network users}", howpublished="RFC 223", series="Internet Request for Comments", type="RFC", number="223", pages="1--4", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc223.txt", key="RFC 223", doi="10.17487/RFC0223", } @misc{rfc224, author="A.M. McKenzie", title="{Comments on Mailbox Protocol}", howpublished="RFC 224", series="Internet Request for Comments", type="RFC", number="224", pages="1--2", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc224.txt", key="RFC 224", doi="10.17487/RFC0224", } @misc{rfc225, author="E. Harslem and R. Stoughton", title="{Rand/UCSB network graphics experiment}", howpublished="RFC 225", series="Internet Request for Comments", type="RFC", number="225", pages="1--5", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc225.txt", key="RFC 225", doi="10.17487/RFC0225", } @misc{rfc226, author="P.M. Karp", title="{Standardization of host mnemonics}", howpublished="RFC 226", series="Internet Request for Comments", type="RFC", number="226", pages="1--1", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 247", url="https://www.rfc-editor.org/rfc/rfc226.txt", key="RFC 226", doi="10.17487/RFC0226", } @misc{rfc227, author="J.F. Heafner and E. Harslem", title="{Data transfer rates (Rand/UCLA)}", howpublished="RFC 227", series="Internet Request for Comments", type="RFC", number="227", pages="1--2", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc227.txt", key="RFC 227", doi="10.17487/RFC0227", } @misc{rfc228, author="D.C. Walden", title="{Clarification}", howpublished="RFC 228", series="Internet Request for Comments", type="RFC", number="228", pages="1--1", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc228.txt", key="RFC 228", doi="10.17487/RFC0228", } @misc{rfc229, author="J. Postel", title="{Standard host names}", howpublished="RFC 229", series="Internet Request for Comments", type="RFC", number="229", pages="1--3", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 236", url="https://www.rfc-editor.org/rfc/rfc229.txt", key="RFC 229", doi="10.17487/RFC0229", } @misc{rfc230, author="T. Pyke", title="{Toward reliable operation of minicomputer-based terminals on a TIP}", howpublished="RFC 230", series="Internet Request for Comments", type="RFC", number="230", pages="1--3", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc230.txt", key="RFC 230", doi="10.17487/RFC0230", } @misc{rfc231, author="J.F. Heafner and E. Harslem", title="{Service center standards for remote usage: A user's view}", howpublished="RFC 231", series="Internet Request for Comments", type="RFC", number="231", pages="1--4", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc231.txt", key="RFC 231", doi="10.17487/RFC0231", } @misc{rfc232, author="A. Vezza", title="{Postponement of network graphics meeting}", howpublished="RFC 232", series="Internet Request for Comments", type="RFC", number="232", pages="1--1", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc232.txt", key="RFC 232", doi="10.17487/RFC0232", } @misc{rfc233, author="A. Bhushan and R. Metcalfe", title="{Standardization of host call letters}", howpublished="RFC 233", series="Internet Request for Comments", type="RFC", number="233", pages="1--2", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc233.txt", key="RFC 233", doi="10.17487/RFC0233", } @misc{rfc234, author="A. Vezza", title="{Network Working Group meeting schedule}", howpublished="RFC 234", series="Internet Request for Comments", type="RFC", number="234", pages="1--1", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc234.txt", key="RFC 234", doi="10.17487/RFC0234", } @misc{rfc235, author="E. Westheimer", title="{Site status}", howpublished="RFC 235", series="Internet Request for Comments", type="RFC", number="235", pages="1--5", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 240", url="https://www.rfc-editor.org/rfc/rfc235.txt", key="RFC 235", doi="10.17487/RFC0235", } @misc{rfc236, author="J. Postel", title="{Standard host names}", howpublished="RFC 236", series="Internet Request for Comments", type="RFC", number="236", pages="1--2", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc236.txt", key="RFC 236", doi="10.17487/RFC0236", } @misc{rfc237, author="R.W. Watson", title="{NIC view of standard host names}", howpublished="RFC 237", series="Internet Request for Comments", type="RFC", number="237", pages="1--1", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 273", url="https://www.rfc-editor.org/rfc/rfc237.txt", key="RFC 237", doi="10.17487/RFC0237", } @misc{rfc238, author="R.T. Braden", title="{Comments on DTP and FTP proposals}", howpublished="RFC 238", series="Internet Request for Comments", type="RFC", number="238", pages="1--2", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc238.txt", key="RFC 238", keywords="FTP", doi="10.17487/RFC0238", } @misc{rfc239, author="R.T. Braden", title="{Host mnemonics proposed in RFC 226 (NIC 7625)}", howpublished="RFC 239", series="Internet Request for Comments", type="RFC", number="239", pages="1--1", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc239.txt", key="RFC 239", doi="10.17487/RFC0239", } @misc{rfc240, author="A.M. McKenzie", title="{Site Status}", howpublished="RFC 240", series="Internet Request for Comments", type="RFC", number="240", pages="1--4", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 252", url="https://www.rfc-editor.org/rfc/rfc240.txt", key="RFC 240", doi="10.17487/RFC0240", } @misc{rfc241, author="A.M. McKenzie", title="{Connecting computers to MLC ports}", howpublished="RFC 241", series="Internet Request for Comments", type="RFC", number="241", pages="1--2", year=1971, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc241.txt", key="RFC 241", doi="10.17487/RFC0241", } @misc{rfc242, author="L. Haibt and A.P. Mullery", title="{Data Descriptive Language for Shared Data}", howpublished="RFC 242", series="Internet Request for Comments", type="RFC", number="242", pages="1--10", year=1971, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc242.txt", key="RFC 242", doi="10.17487/RFC0242", } @misc{rfc243, author="A.P. Mullery", title="{Network and data sharing bibliography}", howpublished="RFC 243", series="Internet Request for Comments", type="RFC", number="243", pages="1--7", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 290", url="https://www.rfc-editor.org/rfc/rfc243.txt", key="RFC 243", doi="10.17487/RFC0243", } @misc{rfc245, author="C. Falls", title="{Reservations for Network Group meeting}", howpublished="RFC 245", series="Internet Request for Comments", type="RFC", number="245", pages="1--1", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc245.txt", key="RFC 245", doi="10.17487/RFC0245", } @misc{rfc246, author="A. Vezza", title="{Network Graphics meeting}", howpublished="RFC 246", series="Internet Request for Comments", type="RFC", number="246", pages="1--1", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc246.txt", key="RFC 246", doi="10.17487/RFC0246", } @misc{rfc247, author="P.M. Karp", title="{Proffered set of standard host names}", howpublished="RFC 247", series="Internet Request for Comments", type="RFC", number="247", pages="1--4", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc247.txt", key="RFC 247", doi="10.17487/RFC0247", } @misc{rfc249, author="R.F. Borelli", title="{Coordination of equipment and supplies purchase}", howpublished="RFC 249", series="Internet Request for Comments", type="RFC", number="249", pages="1--2", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc249.txt", key="RFC 249", doi="10.17487/RFC0249", } @misc{rfc250, author="H. Brodie", title="{Some thoughts on file transfer}", howpublished="RFC 250", series="Internet Request for Comments", type="RFC", number="250", pages="1--1", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc250.txt", key="RFC 250", doi="10.17487/RFC0250", } @misc{rfc251, author="D. Stern", title="{Weather data}", howpublished="RFC 251", series="Internet Request for Comments", type="RFC", number="251", pages="1--2", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc251.txt", key="RFC 251", doi="10.17487/RFC0251", } @misc{rfc252, author="E. Westheimer", title="{Network host status}", howpublished="RFC 252", series="Internet Request for Comments", type="RFC", number="252", pages="1--3", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 255", url="https://www.rfc-editor.org/rfc/rfc252.txt", key="RFC 252", doi="10.17487/RFC0252", } @misc{rfc253, author="J.A. Moorer", title="{Second Network Graphics meeting details}", howpublished="RFC 253", series="Internet Request for Comments", type="RFC", number="253", pages="1--1", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc253.txt", key="RFC 253", doi="10.17487/RFC0253", } @misc{rfc254, author="A. Bhushan", title="{Scenarios for using ARPANET computers}", howpublished="RFC 254", series="Internet Request for Comments", type="RFC", number="254", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc254.txt", key="RFC 254", doi="10.17487/RFC0254", } @misc{rfc255, author="E. Westheimer", title="{Status of network hosts}", howpublished="RFC 255", series="Internet Request for Comments", type="RFC", number="255", pages="1--2", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 266", url="https://www.rfc-editor.org/rfc/rfc255.txt", key="RFC 255", doi="10.17487/RFC0255", } @misc{rfc256, author="B. Cosell", title="{IMPSYS change notification}", howpublished="RFC 256", series="Internet Request for Comments", type="RFC", number="256", pages="1--1", year=1971, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc256.txt", key="RFC 256", doi="10.17487/RFC0256", } @misc{rfc263, author="A.M. McKenzie", title="{``Very Distant'' Host interface}", howpublished="RFC 263", series="Internet Request for Comments", type="RFC", number="263", pages="1--2", year=1971, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc263.txt", key="RFC 263", doi="10.17487/RFC0263", } @misc{rfc264, author="A. Bhushan and B. Braden and W. Crowther and E. Harslem and J. Heafner and A. McKenize and B. Sundberg and D. Watson and J. White", title="{The Data Transfer Protocol}", howpublished="RFC 264", series="Internet Request for Comments", type="RFC", number="264", pages="1--9", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 354, updated by RFC 310", url="https://www.rfc-editor.org/rfc/rfc264.txt", key="RFC 264", keywords="FTP, DTP", doi="10.17487/RFC0264", } @misc{rfc265, author="A. Bhushan and B. Braden and W. Crowther and E. Harslem and J. Heafner and A. McKenzie and J. Melvin and B. Sundberg and D. Watson and J. White", title="{The File Transfer Protocol}", howpublished="RFC 265", series="Internet Request for Comments", type="RFC", number="265", pages="1--12", year=1971, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 354, updated by RFCs 281, 294, 310", url="https://www.rfc-editor.org/rfc/rfc265.txt", key="RFC 265", keywords="FTP", doi="10.17487/RFC0265", } @misc{rfc266, author="E. Westheimer", title="{Network host status}", howpublished="RFC 266", series="Internet Request for Comments", type="RFC", number="266", pages="1--2", year=1971, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 267", url="https://www.rfc-editor.org/rfc/rfc266.txt", key="RFC 266", doi="10.17487/RFC0266", } @misc{rfc267, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 267", series="Internet Request for Comments", type="RFC", number="267", pages="1--4", year=1971, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 287", url="https://www.rfc-editor.org/rfc/rfc267.txt", key="RFC 267", doi="10.17487/RFC0267", } @misc{rfc268, author="J. Postel", title="{Graphics facilities information}", howpublished="RFC 268", series="Internet Request for Comments", type="RFC", number="268", pages="1--1", year=1971, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc268.txt", key="RFC 268", doi="10.17487/RFC0268", } @misc{rfc269, author="H. Brodie", title="{Some Experience with File Transfer}", howpublished="RFC 269", series="Internet Request for Comments", type="RFC", number="269", pages="1--3", year=1971, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc269.txt", key="RFC 269", doi="10.17487/RFC0269", } @misc{rfc270, author="A.M. McKenzie", title="{Correction to BBN Report No. 1822 (NIC NO 7958)}", howpublished="RFC 270", series="Internet Request for Comments", type="RFC", number="270", pages="1--1", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc270.txt", key="RFC 270", doi="10.17487/RFC0270", } @misc{rfc271, author="B. Cosell", title="{IMP System change notifications}", howpublished="RFC 271", series="Internet Request for Comments", type="RFC", number="271", pages="1--2", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc271.txt", key="RFC 271", doi="10.17487/RFC0271", } @misc{rfc273, author="R.W. Watson", title="{More on standard host names}", howpublished="RFC 273", series="Internet Request for Comments", type="RFC", number="273", pages="1--3", year=1971, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc273.txt", key="RFC 273", doi="10.17487/RFC0273", } @misc{rfc274, author="E. Forman", title="{Establishing a local guide for network usage}", howpublished="RFC 274", series="Internet Request for Comments", type="RFC", number="274", pages="1--5", year=1971, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc274.txt", key="RFC 274", doi="10.17487/RFC0274", } @misc{rfc276, author="R.W. Watson", title="{NIC course}", howpublished="RFC 276", series="Internet Request for Comments", type="RFC", number="276", pages="1--1", year=1971, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc276.txt", key="RFC 276", doi="10.17487/RFC0276", } @misc{rfc278, author="A.K. Bhushan and R.T. Braden and E. Harslem and J.F. Heafner and A.M. McKenzie and J.T. Melvin and R.L. Sundberg and R.W. Watson and J.E. White", title="{Revision of the Mail Box Protocol}", howpublished="RFC 278", series="Internet Request for Comments", type="RFC", number="278", pages="1--4", year=1971, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc278.txt", key="RFC 278", doi="10.17487/RFC0278", } @misc{rfc280, author="R.W. Watson", title="{A Draft of Host Names}", howpublished="RFC 280", series="Internet Request for Comments", type="RFC", number="280", pages="1--3", year=1971, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc280.txt", key="RFC 280", doi="10.17487/RFC0280", } @misc{rfc281, author="A.M. McKenzie", title="{Suggested addition to File Transfer Protocol}", howpublished="RFC 281", series="Internet Request for Comments", type="RFC", number="281", pages="1--8", year=1971, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc281.txt", key="RFC 281", keywords="FTP", doi="10.17487/RFC0281", } @misc{rfc282, author="M.A. Padlipsky", title="{Graphics meeting report}", howpublished="RFC 282", series="Internet Request for Comments", type="RFC", number="282", pages="1--8", year=1971, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc282.txt", key="RFC 282", doi="10.17487/RFC0282", } @misc{rfc283, author="R.T. Braden", title="{NETRJT: Remote Job Service Protocol for TIPS}", howpublished="RFC 283", series="Internet Request for Comments", type="RFC", number="283", pages="1--9", year=1971, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc283.txt", key="RFC 283", doi="10.17487/RFC0283", } @misc{rfc285, author="D. Huff", title="{Network graphics}", howpublished="RFC 285", series="Internet Request for Comments", type="RFC", number="285", pages="1--8", year=1971, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc285.txt", key="RFC 285", doi="10.17487/RFC0285", } @misc{rfc286, author="E. Forman", title="{Network Library Information System}", howpublished="RFC 286", series="Internet Request for Comments", type="RFC", number="286", pages="1--1", year=1971, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc286.txt", key="RFC 286", doi="10.17487/RFC0286", } @misc{rfc287, author="E. Westheimer", title="{Status of Network Hosts}", howpublished="RFC 287", series="Internet Request for Comments", type="RFC", number="287", pages="1--5", year=1971, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 288", url="https://www.rfc-editor.org/rfc/rfc287.txt", key="RFC 287", doi="10.17487/RFC0287", } @misc{rfc288, author="E. Westheimer", title="{Network host status}", howpublished="RFC 288", series="Internet Request for Comments", type="RFC", number="288", pages="1--4", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 293, updated by RFC 293", url="https://www.rfc-editor.org/rfc/rfc288.txt", key="RFC 288", doi="10.17487/RFC0288", } @misc{rfc289, author="R.W. Watson", title="{What we hope is an official list of host names}", howpublished="RFC 289", series="Internet Request for Comments", type="RFC", number="289", pages="1--3", year=1971, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 384", url="https://www.rfc-editor.org/rfc/rfc289.txt", key="RFC 289", doi="10.17487/RFC0289", } @misc{rfc290, author="A.P. Mullery", title="{Computer networks and data sharing: A bibliography}", howpublished="RFC 290", series="Internet Request for Comments", type="RFC", number="290", pages="1--15", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc290.txt", key="RFC 290", doi="10.17487/RFC0290", } @misc{rfc291, author="D.B. McKay", title="{Data Management Meeting Announcement}", howpublished="RFC 291", series="Internet Request for Comments", type="RFC", number="291", pages="1--2", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc291.txt", key="RFC 291", doi="10.17487/RFC0291", } @misc{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}", howpublished="RFC 292", series="Internet Request for Comments", type="RFC", number="292", pages="1--10", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 493", url="https://www.rfc-editor.org/rfc/rfc292.txt", key="RFC 292", doi="10.17487/RFC0292", } @misc{rfc293, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 293", series="Internet Request for Comments", type="RFC", number="293", pages="1--4", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 298", url="https://www.rfc-editor.org/rfc/rfc293.txt", key="RFC 293", doi="10.17487/RFC0293", } @misc{rfc294, author="A.K. Bhushan", title="{The Use of ``Set Data Type'' Transaction in File Transfer Protocol}", howpublished="RFC 294", series="Internet Request for Comments", type="RFC", number="294", pages="1--2", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc294.txt", key="RFC 294", keywords="FTP", doi="10.17487/RFC0294", } @misc{rfc295, author="J. Postel", title="{Report of the Protocol Workshop, 12 October 1971}", howpublished="RFC 295", series="Internet Request for Comments", type="RFC", number="295", pages="1--4", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc295.txt", key="RFC 295", doi="10.17487/RFC0295", } @misc{rfc296, author="D.E. Liddle", title="{DS-1 Display System}", howpublished="RFC 296", series="Internet Request for Comments", type="RFC", number="296", pages="1--17", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc296.txt", key="RFC 296", doi="10.17487/RFC0296", } @misc{rfc297, author="D.C. Walden", title="{TIP Message Buffers}", howpublished="RFC 297", series="Internet Request for Comments", type="RFC", number="297", pages="1--2", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc297.txt", key="RFC 297", doi="10.17487/RFC0297", } @misc{rfc298, author="E. Westheimer", title="{Network host status}", howpublished="RFC 298", series="Internet Request for Comments", type="RFC", number="298", pages="1--4", year=1972, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 306", url="https://www.rfc-editor.org/rfc/rfc298.txt", key="RFC 298", doi="10.17487/RFC0298", } @misc{rfc299, author="D. Hopkin", title="{Information Management System}", howpublished="RFC 299", series="Internet Request for Comments", type="RFC", number="299", pages="1--1", year=1972, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc299.txt", key="RFC 299", doi="10.17487/RFC0299", } @misc{rfc300, author="J.B. North", title="{ARPA Network mailing lists}", howpublished="RFC 300", series="Internet Request for Comments", type="RFC", number="300", pages="1--9", year=1972, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 303", url="https://www.rfc-editor.org/rfc/rfc300.txt", key="RFC 300", doi="10.17487/RFC0300", } @misc{rfc301, author="R. Alter", title="{BBN IMP (\#5) and NCC Schedule March 4, 1971}", howpublished="RFC 301", series="Internet Request for Comments", type="RFC", number="301", pages="1--1", year=1972, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc301.txt", key="RFC 301", doi="10.17487/RFC0301", } @misc{rfc302, author="R.F. Bryan", title="{Exercising The ARPANET}", howpublished="RFC 302", series="Internet Request for Comments", type="RFC", number="302", pages="1--3", year=1972, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc302.txt", key="RFC 302", doi="10.17487/RFC0302", } @misc{rfc303, author="Network Information Center. Stanford Research Institute", title="{ARPA Network mailing lists}", howpublished="RFC 303", series="Internet Request for Comments", type="RFC", number="303", pages="1--11", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 329", url="https://www.rfc-editor.org/rfc/rfc303.txt", key="RFC 303", doi="10.17487/RFC0303", } @misc{rfc304, author="D.B. McKay", title="{Data Management System Proposal for the ARPA Network}", howpublished="RFC 304", series="Internet Request for Comments", type="RFC", number="304", pages="1--8", year=1972, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc304.txt", key="RFC 304", doi="10.17487/RFC0304", } @misc{rfc305, author="R. Alter", title="{Unknown Host Numbers}", howpublished="RFC 305", series="Internet Request for Comments", type="RFC", number="305", pages="1--1", year=1972, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc305.txt", key="RFC 305", doi="10.17487/RFC0305", } @misc{rfc306, author="E. Westheimer", title="{Network host status}", howpublished="RFC 306", series="Internet Request for Comments", type="RFC", number="306", pages="1--4", year=1972, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 315", url="https://www.rfc-editor.org/rfc/rfc306.txt", key="RFC 306", doi="10.17487/RFC0306", } @misc{rfc307, author="E. Harslem", title="{Using network Remote Job Entry}", howpublished="RFC 307", series="Internet Request for Comments", type="RFC", number="307", pages="1--6", year=1972, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc307.txt", key="RFC 307", doi="10.17487/RFC0307", } @misc{rfc308, author="M. Seriff", title="{ARPANET host availability data}", howpublished="RFC 308", series="Internet Request for Comments", type="RFC", number="308", pages="1--4", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc308.txt", key="RFC 308", doi="10.17487/RFC0308", } @misc{rfc309, author="A.K. Bhushan", title="{Data and File Transfer Workshop Announcement}", howpublished="RFC 309", series="Internet Request for Comments", type="RFC", number="309", pages="1--6", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc309.txt", key="RFC 309", keywords="FTP, DTP", doi="10.17487/RFC0309", } @misc{rfc310, author="A.K. Bhushan", title="{Another Look at Data and File Transfer Protocols}", howpublished="RFC 310", series="Internet Request for Comments", type="RFC", number="310", pages="1--7", year=1972, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc310.txt", key="RFC 310", keywords="FTP", doi="10.17487/RFC0310", } @misc{rfc311, author="R.F. Bryan", title="{New Console Attachments to the USCB Host}", howpublished="RFC 311", series="Internet Request for Comments", type="RFC", number="311", pages="1--2", year=1972, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc311.txt", key="RFC 311", doi="10.17487/RFC0311", } @misc{rfc312, author="A.M. McKenzie", title="{Proposed Change in IMP-to-Host Protocol}", howpublished="RFC 312", series="Internet Request for Comments", type="RFC", number="312", pages="1--2", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc312.txt", key="RFC 312", doi="10.17487/RFC0312", } @misc{rfc313, author="T.C. O'Sullivan", title="{Computer based instruction}", howpublished="RFC 313", series="Internet Request for Comments", type="RFC", number="313", pages="1--8", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc313.txt", key="RFC 313", doi="10.17487/RFC0313", } @misc{rfc314, author="I.W. Cotton", title="{Network Graphics Working Group Meeting}", howpublished="RFC 314", series="Internet Request for Comments", type="RFC", number="314", pages="1--1", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc314.txt", key="RFC 314", doi="10.17487/RFC0314", } @misc{rfc315, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 315", series="Internet Request for Comments", type="RFC", number="315", pages="1--4", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 319", url="https://www.rfc-editor.org/rfc/rfc315.txt", key="RFC 315", doi="10.17487/RFC0315", } @misc{rfc316, author="D.B. McKay and A.P. Mullery", title="{ARPA Network Data Management Working Group}", howpublished="RFC 316", series="Internet Request for Comments", type="RFC", number="316", pages="1--7", year=1972, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc316.txt", key="RFC 316", doi="10.17487/RFC0316", } @misc{rfc317, author="J. Postel", title="{Official Host-Host Protocol Modification: Assigned Link Numbers}", howpublished="RFC 317", series="Internet Request for Comments", type="RFC", number="317", pages="1--1", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 604", url="https://www.rfc-editor.org/rfc/rfc317.txt", key="RFC 317", doi="10.17487/RFC0317", } @misc{rfc318, author="J. Postel", title="{Telnet Protocols}", howpublished="RFC 318", series="Internet Request for Comments", type="RFC", number="318", pages="1--16", year=1972, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 435", url="https://www.rfc-editor.org/rfc/rfc318.txt", key="RFC 318", doi="10.17487/RFC0318", } @misc{rfc319, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 319", series="Internet Request for Comments", type="RFC", number="319", pages="1--4", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 326", url="https://www.rfc-editor.org/rfc/rfc319.txt", key="RFC 319", doi="10.17487/RFC0319", } @misc{rfc320, author="R. Reddy", title="{Workshop on Hard Copy Line Graphics}", howpublished="RFC 320", series="Internet Request for Comments", type="RFC", number="320", pages="1--3", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc320.txt", key="RFC 320", doi="10.17487/RFC0320", } @misc{rfc321, author="P.M. Karp", title="{CBI Networking Activity at MITRE}", howpublished="RFC 321", series="Internet Request for Comments", type="RFC", number="321", pages="1--13", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc321.txt", key="RFC 321", doi="10.17487/RFC0321", } @misc{rfc322, author="V. Cerf and J. Postel", title="{Well known socket numbers}", howpublished="RFC 322", series="Internet Request for Comments", type="RFC", number="322", pages="1--1", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc322.txt", key="RFC 322", doi="10.17487/RFC0322", } @misc{rfc323, author="V. Cerf", title="{Formation of Network Measurement Group (NMG)}", howpublished="RFC 323", series="Internet Request for Comments", type="RFC", number="323", pages="1--9", year=1972, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 388", url="https://www.rfc-editor.org/rfc/rfc323.txt", key="RFC 323", doi="10.17487/RFC0323", } @misc{rfc324, author="J. Postel", title="{RJE Protocol meeting}", howpublished="RFC 324", series="Internet Request for Comments", type="RFC", number="324", pages="1--1", year=1972, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc324.txt", key="RFC 324", doi="10.17487/RFC0324", } @misc{rfc325, author="G. Hicks", title="{Network Remote Job Entry program - NETRJS}", howpublished="RFC 325", series="Internet Request for Comments", type="RFC", number="325", pages="1--9", year=1972, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc325.txt", key="RFC 325", doi="10.17487/RFC0325", } @misc{rfc326, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 326", series="Internet Request for Comments", type="RFC", number="326", pages="1--4", year=1972, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 330", url="https://www.rfc-editor.org/rfc/rfc326.txt", key="RFC 326", doi="10.17487/RFC0326", } @misc{rfc327, author="A.K. Bhushan", title="{Data and File Transfer workshop notes}", howpublished="RFC 327", series="Internet Request for Comments", type="RFC", number="327", pages="1--5", year=1972, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc327.txt", key="RFC 327", doi="10.17487/RFC0327", } @misc{rfc328, author="J. Postel", title="{Suggested Telnet Protocol Changes}", howpublished="RFC 328", series="Internet Request for Comments", type="RFC", number="328", pages="1--2", year=1972, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc328.txt", key="RFC 328", doi="10.17487/RFC0328", } @misc{rfc329, author="Network Information Center. Stanford Research Institute", title="{ARPA Network Mailing Lists}", howpublished="RFC 329", series="Internet Request for Comments", type="RFC", number="329", pages="1--13", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 363", url="https://www.rfc-editor.org/rfc/rfc329.txt", key="RFC 329", doi="10.17487/RFC0329", } @misc{rfc330, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 330", series="Internet Request for Comments", type="RFC", number="330", pages="1--3", year=1972, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 332", url="https://www.rfc-editor.org/rfc/rfc330.txt", key="RFC 330", doi="10.17487/RFC0330", } @misc{rfc331, author="J.M. McQuillan", title="{IMP System Change Notification}", howpublished="RFC 331", series="Internet Request for Comments", type="RFC", number="331", pages="1--1", year=1972, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 343", url="https://www.rfc-editor.org/rfc/rfc331.txt", key="RFC 331", doi="10.17487/RFC0331", } @misc{rfc332, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 332", series="Internet Request for Comments", type="RFC", number="332", pages="1--4", year=1972, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 342", url="https://www.rfc-editor.org/rfc/rfc332.txt", key="RFC 332", doi="10.17487/RFC0332", } @misc{rfc333, author="R.D. Bressler and D. Murphy and D.C. Walden", title="{Proposed experiment with a Message Switching Protocol}", howpublished="RFC 333", series="Internet Request for Comments", type="RFC", number="333", pages="1--26", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc333.txt", key="RFC 333", doi="10.17487/RFC0333", } @misc{rfc334, author="A.M. McKenzie", title="{Network Use on May 8}", howpublished="RFC 334", series="Internet Request for Comments", type="RFC", number="334", pages="1--1", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc334.txt", key="RFC 334", doi="10.17487/RFC0334", } @misc{rfc335, author="R.F. Bryan", title="{New Interface - IMP/360}", howpublished="RFC 335", series="Internet Request for Comments", type="RFC", number="335", pages="1--1", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc335.txt", key="RFC 335", doi="10.17487/RFC0335", } @misc{rfc336, author="I.W. Cotton", title="{Level 0 Graphic Input Protocol}", howpublished="RFC 336", series="Internet Request for Comments", type="RFC", number="336", pages="1--2", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc336.txt", key="RFC 336", doi="10.17487/RFC0336", } @misc{rfc338, author="R.T. Braden", title="{EBCDIC/ASCII Mapping for Network RJE}", howpublished="RFC 338", series="Internet Request for Comments", type="RFC", number="338", pages="1--6", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc338.txt", key="RFC 338", doi="10.17487/RFC0338", } @misc{rfc339, author="R. Thomas", title="{MLTNET: A ``Multi Telnet'' Subsystem for Tenex}", howpublished="RFC 339", series="Internet Request for Comments", type="RFC", number="339", pages="1--4", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc339.txt", key="RFC 339", doi="10.17487/RFC0339", } @misc{rfc340, author="T.C. O'Sullivan", title="{Proposed Telnet Changes}", howpublished="RFC 340", series="Internet Request for Comments", type="RFC", number="340", pages="1--2", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc340.txt", key="RFC 340", doi="10.17487/RFC0340", } @misc{rfc342, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 342", series="Internet Request for Comments", type="RFC", number="342", pages="1--4", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 344", url="https://www.rfc-editor.org/rfc/rfc342.txt", key="RFC 342", doi="10.17487/RFC0342", } @misc{rfc343, author="A.M. McKenzie", title="{IMP System change notification}", howpublished="RFC 343", series="Internet Request for Comments", type="RFC", number="343", pages="1--2", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 359", url="https://www.rfc-editor.org/rfc/rfc343.txt", key="RFC 343", doi="10.17487/RFC0343", } @misc{rfc344, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 344", series="Internet Request for Comments", type="RFC", number="344", pages="1--4", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 353", url="https://www.rfc-editor.org/rfc/rfc344.txt", key="RFC 344", doi="10.17487/RFC0344", } @misc{rfc345, author="K.C. Kelley", title="{Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN)}", howpublished="RFC 345", series="Internet Request for Comments", type="RFC", number="345", pages="1--1", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc345.txt", key="RFC 345", keywords="MIP", doi="10.17487/RFC0345", } @misc{rfc346, author="J. Postel", title="{Satellite Considerations}", howpublished="RFC 346", series="Internet Request for Comments", type="RFC", number="346", pages="1--1", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc346.txt", key="RFC 346", doi="10.17487/RFC0346", } @misc{rfc347, author="J. Postel", title="{Echo process}", howpublished="RFC 347", series="Internet Request for Comments", type="RFC", number="347", pages="1--1", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc347.txt", key="RFC 347", doi="10.17487/RFC0347", } @misc{rfc348, author="J. Postel", title="{Discard Process}", howpublished="RFC 348", series="Internet Request for Comments", type="RFC", number="348", pages="1--1", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc348.txt", key="RFC 348", doi="10.17487/RFC0348", } @misc{rfc349, author="J. Postel", title="{Proposed Standard Socket Numbers}", howpublished="RFC 349", series="Internet Request for Comments", type="RFC", number="349", pages="1--1", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 433", url="https://www.rfc-editor.org/rfc/rfc349.txt", key="RFC 349", doi="10.17487/RFC0349", } @misc{rfc350, author="R. Stoughton", title="{User Accounts for UCSB On-Line System}", howpublished="RFC 350", series="Internet Request for Comments", type="RFC", number="350", pages="1--3", year=1972, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc350.txt", key="RFC 350", doi="10.17487/RFC0350", } @misc{rfc351, author="D. Crocker", title="{Graphics information form for the ARPANET graphics resources notebook}", howpublished="RFC 351", series="Internet Request for Comments", type="RFC", number="351", pages="1--2", year=1972, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc351.txt", key="RFC 351", doi="10.17487/RFC0351", } @misc{rfc352, author="D. Crocker", title="{TIP Site Information Form}", howpublished="RFC 352", series="Internet Request for Comments", type="RFC", number="352", pages="1--3", year=1972, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc352.txt", key="RFC 352", doi="10.17487/RFC0352", } @misc{rfc353, author="E. Westheimer", title="{Network host status}", howpublished="RFC 353", series="Internet Request for Comments", type="RFC", number="353", pages="1--5", year=1972, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 362", url="https://www.rfc-editor.org/rfc/rfc353.txt", key="RFC 353", doi="10.17487/RFC0353", } @misc{rfc354, author="A.K. Bhushan", title="{File Transfer Protocol}", howpublished="RFC 354", series="Internet Request for Comments", type="RFC", number="354", pages="1--25", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 542, updated by RFCs 385, 454, 683", url="https://www.rfc-editor.org/rfc/rfc354.txt", key="RFC 354", keywords="FTP", doi="10.17487/RFC0354", } @misc{rfc355, author="J. Davidson", title="{Response to NWG/RFC 346}", howpublished="RFC 355", series="Internet Request for Comments", type="RFC", number="355", pages="1--3", year=1972, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc355.txt", key="RFC 355", doi="10.17487/RFC0355", } @misc{rfc356, author="R. Alter", title="{ARPA Network Control Center}", howpublished="RFC 356", series="Internet Request for Comments", type="RFC", number="356", pages="1--1", year=1972, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc356.txt", key="RFC 356", doi="10.17487/RFC0356", } @misc{rfc357, author="J. Davidson", title="{Echoing strategy for satellite links}", howpublished="RFC 357", series="Internet Request for Comments", type="RFC", number="357", pages="1--13", year=1972, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc357.txt", key="RFC 357", doi="10.17487/RFC0357", } @misc{rfc359, author="D.C. Walden", title="{Status of the Release of the New IMP System (2600)}", howpublished="RFC 359", series="Internet Request for Comments", type="RFC", number="359", pages="1--1", year=1972, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc359.txt", key="RFC 359", doi="10.17487/RFC0359", } @misc{rfc360, author="C. Holland", title="{Proposed Remote Job Entry Protocol}", howpublished="RFC 360", series="Internet Request for Comments", type="RFC", number="360", pages="1--18", year=1972, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 407", url="https://www.rfc-editor.org/rfc/rfc360.txt", key="RFC 360", doi="10.17487/RFC0360", } @misc{rfc361, author="R.D. Bressler", title="{Deamon Processes on Host 106}", howpublished="RFC 361", series="Internet Request for Comments", type="RFC", number="361", pages="1--1", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc361.txt", key="RFC 361", doi="10.17487/RFC0361", } @misc{rfc362, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 362", series="Internet Request for Comments", type="RFC", number="362", pages="1--4", year=1972, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 366", url="https://www.rfc-editor.org/rfc/rfc362.txt", key="RFC 362", doi="10.17487/RFC0362", } @misc{rfc363, author="Network Information Center. Stanford Research Institute", title="{ARPA Network mailing lists}", howpublished="RFC 363", series="Internet Request for Comments", type="RFC", number="363", pages="1--13", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 402", url="https://www.rfc-editor.org/rfc/rfc363.txt", key="RFC 363", doi="10.17487/RFC0363", } @misc{rfc364, author="M.D. Abrams", title="{Serving remote users on the ARPANET}", howpublished="RFC 364", series="Internet Request for Comments", type="RFC", number="364", pages="1--6", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc364.txt", key="RFC 364", doi="10.17487/RFC0364", } @misc{rfc365, author="D.C. Walden", title="{Letter to All TIP Users}", howpublished="RFC 365", series="Internet Request for Comments", type="RFC", number="365", pages="1--5", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc365.txt", key="RFC 365", doi="10.17487/RFC0365", } @misc{rfc366, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 366", series="Internet Request for Comments", type="RFC", number="366", pages="1--4", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 367", url="https://www.rfc-editor.org/rfc/rfc366.txt", key="RFC 366", doi="10.17487/RFC0366", } @misc{rfc367, author="E. Westheimer", title="{Network host status}", howpublished="RFC 367", series="Internet Request for Comments", type="RFC", number="367", pages="1--4", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 370", url="https://www.rfc-editor.org/rfc/rfc367.txt", key="RFC 367", doi="10.17487/RFC0367", } @misc{rfc368, author="R.T. Braden", title="{Comments on ``Proposed Remote Job Entry Protocol''}", howpublished="RFC 368", series="Internet Request for Comments", type="RFC", number="368", pages="1--2", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc368.txt", key="RFC 368", doi="10.17487/RFC0368", } @misc{rfc369, author="J.R. Pickens", title="{Evaluation of ARPANET services January-March, 1972}", howpublished="RFC 369", series="Internet Request for Comments", type="RFC", number="369", pages="1--11", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc369.txt", key="RFC 369", doi="10.17487/RFC0369", } @misc{rfc370, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 370", series="Internet Request for Comments", type="RFC", number="370", pages="1--5", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 376", url="https://www.rfc-editor.org/rfc/rfc370.txt", key="RFC 370", doi="10.17487/RFC0370", } @misc{rfc371, author="R.E. Kahn", title="{Demonstration at International Computer Communications Conference}", howpublished="RFC 371", series="Internet Request for Comments", type="RFC", number="371", pages="1--2", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc371.txt", key="RFC 371", doi="10.17487/RFC0371", } @misc{rfc372, author="R.W. Watson", title="{Notes on a Conversation with Bob Kahn on the ICCC}", howpublished="RFC 372", series="Internet Request for Comments", type="RFC", number="372", pages="1--4", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc372.txt", key="RFC 372", doi="10.17487/RFC0372", } @misc{rfc373, author="J. McCarthy", title="{Arbitrary Character Sets}", howpublished="RFC 373", series="Internet Request for Comments", type="RFC", number="373", pages="1--4", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc373.txt", key="RFC 373", doi="10.17487/RFC0373", } @misc{rfc374, author="A.M. McKenzie", title="{IMP System Announcement}", howpublished="RFC 374", series="Internet Request for Comments", type="RFC", number="374", pages="1--2", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc374.txt", key="RFC 374", doi="10.17487/RFC0374", } @misc{rfc376, author="E. Westheimer", title="{Network Host Status}", howpublished="RFC 376", series="Internet Request for Comments", type="RFC", number="376", pages="1--5", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc376.txt", key="RFC 376", doi="10.17487/RFC0376", } @misc{rfc377, author="R.T. Braden", title="{Using TSO via ARPA Network Virtual Terminal}", howpublished="RFC 377", series="Internet Request for Comments", type="RFC", number="377", pages="1--4", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc377.txt", key="RFC 377", doi="10.17487/RFC0377", } @misc{rfc378, author="A.M. McKenzie", title="{Traffic statistics (July 1972)}", howpublished="RFC 378", series="Internet Request for Comments", type="RFC", number="378", pages="1--3", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 391", url="https://www.rfc-editor.org/rfc/rfc378.txt", key="RFC 378", doi="10.17487/RFC0378", } @misc{rfc379, author="R. Braden", title="{Using TSO at CCN}", howpublished="RFC 379", series="Internet Request for Comments", type="RFC", number="379", pages="1--5", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc379.txt", key="RFC 379", doi="10.17487/RFC0379", } @misc{rfc381, author="J.M. McQuillan", title="{Three aids to improved network operation}", howpublished="RFC 381", series="Internet Request for Comments", type="RFC", number="381", pages="1--4", year=1972, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 394", url="https://www.rfc-editor.org/rfc/rfc381.txt", key="RFC 381", doi="10.17487/RFC0381", } @misc{rfc382, author="L. McDaniel", title="{Mathematical Software on the ARPA Network}", howpublished="RFC 382", series="Internet Request for Comments", type="RFC", number="382", pages="1--1", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc382.txt", key="RFC 382", doi="10.17487/RFC0382", } @misc{rfc384, author="J.B. North", title="{Official site idents for organizations in the ARPA Network}", howpublished="RFC 384", series="Internet Request for Comments", type="RFC", number="384", pages="1--4", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc384.txt", key="RFC 384", doi="10.17487/RFC0384", } @misc{rfc385, author="A.K. Bhushan", title="{Comments on the File Transfer Protocol}", howpublished="RFC 385", series="Internet Request for Comments", type="RFC", number="385", pages="1--6", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 414", url="https://www.rfc-editor.org/rfc/rfc385.txt", key="RFC 385", keywords="FTP", doi="10.17487/RFC0385", } @misc{rfc386, author="B. Cosell and D.C. Walden", title="{Letter to TIP users-2}", howpublished="RFC 386", series="Internet Request for Comments", type="RFC", number="386", pages="1--5", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc386.txt", key="RFC 386", doi="10.17487/RFC0386", } @misc{rfc387, author="K.C. Kelley and J. Meir", title="{Some experiences in implementing Network Graphics Protocol Level 0}", howpublished="RFC 387", series="Internet Request for Comments", type="RFC", number="387", pages="1--5", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 401", url="https://www.rfc-editor.org/rfc/rfc387.txt", key="RFC 387", doi="10.17487/RFC0387", } @misc{rfc388, author="V. Cerf", title="{NCP statistics}", howpublished="RFC 388", series="Internet Request for Comments", type="RFC", number="388", pages="1--5", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc388.txt", key="RFC 388", doi="10.17487/RFC0388", } @misc{rfc389, author="B. Noble", title="{UCLA Campus Computing Network Liaison Staff for ARPA Network}", howpublished="RFC 389", series="Internet Request for Comments", type="RFC", number="389", pages="1--2", year=1972, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 423", url="https://www.rfc-editor.org/rfc/rfc389.txt", key="RFC 389", doi="10.17487/RFC0389", } @misc{rfc390, author="R.T. Braden", title="{TSO Scenario}", howpublished="RFC 390", series="Internet Request for Comments", type="RFC", number="390", pages="1--4", year=1972, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc390.txt", key="RFC 390", doi="10.17487/RFC0390", } @misc{rfc391, author="A.M. McKenzie", title="{Traffic statistics (August 1972)}", howpublished="RFC 391", series="Internet Request for Comments", type="RFC", number="391", pages="1--3", year=1972, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc391.txt", key="RFC 391", doi="10.17487/RFC0391", } @misc{rfc392, author="G. Hicks and B.D. Wessler", title="{Measurement of host costs for transmitting network data}", howpublished="RFC 392", series="Internet Request for Comments", type="RFC", number="392", pages="1--6", year=1972, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc392.txt", key="RFC 392", doi="10.17487/RFC0392", } @misc{rfc393, author="J.M. Winett", title="{Comments on Telnet Protocol Changes}", howpublished="RFC 393", series="Internet Request for Comments", type="RFC", number="393", pages="1--4", year=1972, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc393.txt", key="RFC 393", doi="10.17487/RFC0393", } @misc{rfc394, author="J.M. McQuillan", title="{Two Proposed Changes to the IMP-Host Protocol}", howpublished="RFC 394", series="Internet Request for Comments", type="RFC", number="394", pages="1--3", year=1972, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc394.txt", key="RFC 394", doi="10.17487/RFC0394", } @misc{rfc395, author="J.M. McQuillan", title="{Switch Settings on IMPs and TIPs}", howpublished="RFC 395", series="Internet Request for Comments", type="RFC", number="395", pages="1--1", year=1972, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc395.txt", key="RFC 395", doi="10.17487/RFC0395", } @misc{rfc396, author="S. Bunch", title="{Network Graphics Working Group Meeting - Second Iteration}", howpublished="RFC 396", series="Internet Request for Comments", type="RFC", number="396", pages="1--1", year=1972, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 474", url="https://www.rfc-editor.org/rfc/rfc396.txt", key="RFC 396", doi="10.17487/RFC0396", } @misc{rfc398, author="J.R. Pickens and E. Faeh", title="{UCSB Online Graphics}", howpublished="RFC 398", series="Internet Request for Comments", type="RFC", number="398", pages="1--2", year=1972, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc398.txt", key="RFC 398", doi="10.17487/RFC0398", } @misc{rfc399, author="M. Krilanovich", title="{SMFS Login and Logout}", howpublished="RFC 399", series="Internet Request for Comments", type="RFC", number="399", pages="1--2", year=1972, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 431", url="https://www.rfc-editor.org/rfc/rfc399.txt", key="RFC 399", doi="10.17487/RFC0399", } @misc{rfc400, author="A.M. McKenzie", title="{Traffic Statistics (September 1972)}", howpublished="RFC 400", series="Internet Request for Comments", type="RFC", number="400", pages="1--3", year=1972, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc400.txt", key="RFC 400", doi="10.17487/RFC0400", } @misc{rfc401, author="J. Hansen", title="{Conversion of NGP-0 Coordinates to Device Specific Coordinates}", howpublished="RFC 401", series="Internet Request for Comments", type="RFC", number="401", pages="1--2", year=1972, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc401.txt", key="RFC 401", doi="10.17487/RFC0401", } @misc{rfc402, author="J.B. North", title="{ARPA Network Mailing Lists}", howpublished="RFC 402", series="Internet Request for Comments", type="RFC", number="402", pages="1--16", year=1972, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc402.txt", key="RFC 402", doi="10.17487/RFC0402", } @misc{rfc403, author="G. Hicks", title="{Desirability of a Network 1108 Service}", howpublished="RFC 403", series="Internet Request for Comments", type="RFC", number="403", pages="1--5", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc403.txt", key="RFC 403", doi="10.17487/RFC0403", } @misc{rfc404, author="A.M. McKenzie", title="{Host Address Changes Involving Rand and ISI}", howpublished="RFC 404", series="Internet Request for Comments", type="RFC", number="404", pages="1--1", year=1972, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 405", url="https://www.rfc-editor.org/rfc/rfc404.txt", key="RFC 404", doi="10.17487/RFC0404", } @misc{rfc405, author="A.M. McKenzie", title="{Correction to RFC 404}", howpublished="RFC 405", series="Internet Request for Comments", type="RFC", number="405", pages="1--1", year=1972, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc405.txt", key="RFC 405", doi="10.17487/RFC0405", } @misc{rfc406, author="J.M. McQuillan", title="{Scheduled IMP Software Releases}", howpublished="RFC 406", series="Internet Request for Comments", type="RFC", number="406", pages="1--2", year=1972, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc406.txt", key="RFC 406", doi="10.17487/RFC0406", } @misc{rfc407, author="R.D. Bressler and R. Guida and A.M. McKenzie", title="{Remote Job Entry Protocol}", howpublished="RFC 407 (Historic)", series="Internet Request for Comments", type="RFC", number="407", pages="1--21", year=1972, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc407.txt", key="RFC 407", keywords="RJE", doi="10.17487/RFC0407", } @misc{rfc408, author="A.D. Owen and J. Postel", title="{NETBANK}", howpublished="RFC 408", series="Internet Request for Comments", type="RFC", number="408", pages="1--1", year=1972, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc408.txt", key="RFC 408", doi="10.17487/RFC0408", } @misc{rfc409, author="J.E. White", title="{Tenex interface to UCSB's Simple-Minded File System}", howpublished="RFC 409", series="Internet Request for Comments", type="RFC", number="409", pages="1--8", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc409.txt", key="RFC 409", doi="10.17487/RFC0409", } @misc{rfc410, author="J.M. McQuillan", title="{Removal of the 30-Second Delay When Hosts Come Up}", howpublished="RFC 410", series="Internet Request for Comments", type="RFC", number="410", pages="1--2", year=1972, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc410.txt", key="RFC 410", doi="10.17487/RFC0410", } @misc{rfc411, author="M.A. Padlipsky", title="{New MULTICS Network Software Features}", howpublished="RFC 411", series="Internet Request for Comments", type="RFC", number="411", pages="1--2", year=1972, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc411.txt", key="RFC 411", doi="10.17487/RFC0411", } @misc{rfc412, author="G. Hicks", title="{User FTP Documentation}", howpublished="RFC 412", series="Internet Request for Comments", type="RFC", number="412", pages="1--10", year=1972, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc412.txt", key="RFC 412", doi="10.17487/RFC0412", } @misc{rfc413, author="A.M. McKenzie", title="{Traffic statistics (October 1972)}", howpublished="RFC 413", series="Internet Request for Comments", type="RFC", number="413", pages="1--10", year=1972, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc413.txt", key="RFC 413", doi="10.17487/RFC0413", } @misc{rfc414, author="A.K. Bhushan", title="{File Transfer Protocol (FTP) status and further comments}", howpublished="RFC 414", series="Internet Request for Comments", type="RFC", number="414", pages="1--5", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc414.txt", key="RFC 414", doi="10.17487/RFC0414", } @misc{rfc415, author="H. Murray", title="{Tenex bandwidth}", howpublished="RFC 415", series="Internet Request for Comments", type="RFC", number="415", pages="1--2", year=1972, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc415.txt", key="RFC 415", doi="10.17487/RFC0415", } @misc{rfc416, author="J.C. Norton", title="{ARC System Will Be Unavailable for Use During Thanksgiving Week}", howpublished="RFC 416", series="Internet Request for Comments", type="RFC", number="416", pages="1--2", year=1972, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc416.txt", key="RFC 416", doi="10.17487/RFC0416", } @misc{rfc417, author="J. Postel and C. Kline", title="{Link usage violation}", howpublished="RFC 417", series="Internet Request for Comments", type="RFC", number="417", pages="1--1", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc417.txt", key="RFC 417", doi="10.17487/RFC0417", } @misc{rfc418, author="W. Hathaway", title="{Server File Transfer Under TSS/360 At NASA-Ames Research Center}", howpublished="RFC 418", series="Internet Request for Comments", type="RFC", number="418", year=1972, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc418.txt", key="RFC 418", doi="10.17487/RFC0418", } @misc{rfc419, author="A. Vezza", title="{To: Network liaisons and station agents}", howpublished="RFC 419", series="Internet Request for Comments", type="RFC", number="419", pages="1--1", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc419.txt", key="RFC 419", doi="10.17487/RFC0419", } @misc{rfc420, author="H. Murray", title="{CCA ICCC weather demo}", howpublished="RFC 420", series="Internet Request for Comments", type="RFC", number="420", pages="1--8", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc420.txt", key="RFC 420", doi="10.17487/RFC0420", } @misc{rfc421, author="A.M. McKenzie", title="{Software Consulting Service for Network Users}", howpublished="RFC 421", series="Internet Request for Comments", type="RFC", number="421", pages="1--2", year=1972, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc421.txt", key="RFC 421", doi="10.17487/RFC0421", } @misc{rfc422, author="A.M. McKenzie", title="{Traffic statistics (November 1972)}", howpublished="RFC 422", series="Internet Request for Comments", type="RFC", number="422", pages="1--4", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc422.txt", key="RFC 422", doi="10.17487/RFC0422", } @misc{rfc423, author="B. Noble", title="{UCLA Campus Computing Network Liaison Staff for ARPANET}", howpublished="RFC 423", series="Internet Request for Comments", type="RFC", number="423", pages="1--2", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc423.txt", key="RFC 423", doi="10.17487/RFC0423", } @misc{rfc425, author="R.D. Bressler", title="{``But my NCP costs \$500 a day''}", howpublished="RFC 425", series="Internet Request for Comments", type="RFC", number="425", pages="1--1", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc425.txt", key="RFC 425", doi="10.17487/RFC0425", } @misc{rfc426, author="R. Thomas", title="{Reconnection Protocol}", howpublished="RFC 426", series="Internet Request for Comments", type="RFC", number="426", pages="1--12", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc426.txt", key="RFC 426", doi="10.17487/RFC0426", } @misc{rfc429, author="J. Postel", title="{Character Generator Process}", howpublished="RFC 429", series="Internet Request for Comments", type="RFC", number="429", pages="1--1", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc429.txt", key="RFC 429", doi="10.17487/RFC0429", } @misc{rfc430, author="R.T. Braden", title="{Comments on File Transfer Protocol}", howpublished="RFC 430", series="Internet Request for Comments", type="RFC", number="430", pages="1--8", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc430.txt", key="RFC 430", doi="10.17487/RFC0430", } @misc{rfc431, author="M. Krilanovich", title="{Update on SMFS Login and Logout}", howpublished="RFC 431", series="Internet Request for Comments", type="RFC", number="431", pages="1--3", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc431.txt", key="RFC 431", doi="10.17487/RFC0431", } @misc{rfc432, author="N. Neigus", title="{Network logical map}", howpublished="RFC 432", series="Internet Request for Comments", type="RFC", number="432", pages="1--1", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc432.txt", key="RFC 432", doi="10.17487/RFC0432", } @misc{rfc433, author="J. Postel", title="{Socket number list}", howpublished="RFC 433", series="Internet Request for Comments", type="RFC", number="433", pages="1--5", year=1972, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 503", url="https://www.rfc-editor.org/rfc/rfc433.txt", key="RFC 433", doi="10.17487/RFC0433", } @misc{rfc434, author="A.M. McKenzie", title="{IMP/TIP memory retrofit schedule}", howpublished="RFC 434", series="Internet Request for Comments", type="RFC", number="434", pages="1--2", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 447", url="https://www.rfc-editor.org/rfc/rfc434.txt", key="RFC 434", doi="10.17487/RFC0434", } @misc{rfc435, author="B. Cosell and D.C. Walden", title="{Telnet issues}", howpublished="RFC 435", series="Internet Request for Comments", type="RFC", number="435", pages="1--10", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc435.txt", key="RFC 435", doi="10.17487/RFC0435", } @misc{rfc436, author="M. Krilanovich", title="{Announcement of RJS at UCSB}", howpublished="RFC 436", series="Internet Request for Comments", type="RFC", number="436", pages="1--1", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc436.txt", key="RFC 436", doi="10.17487/RFC0436", } @misc{rfc437, author="E. Faeh", title="{Data Reconfiguration Service at UCSB}", howpublished="RFC 437", series="Internet Request for Comments", type="RFC", number="437", pages="1--10", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc437.txt", key="RFC 437", doi="10.17487/RFC0437", } @misc{rfc438, author="R. Thomas and R. Clements", title="{FTP server-server interaction}", howpublished="RFC 438", series="Internet Request for Comments", type="RFC", number="438", pages="1--3", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc438.txt", key="RFC 438", doi="10.17487/RFC0438", } @misc{rfc439, author="V. Cerf", title="{PARRY encounters the DOCTOR}", howpublished="RFC 439", series="Internet Request for Comments", type="RFC", number="439", pages="1--7", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc439.txt", key="RFC 439", doi="10.17487/RFC0439", } @misc{rfc440, author="D.C. Walden", title="{Scheduled network software maintenance}", howpublished="RFC 440", series="Internet Request for Comments", type="RFC", number="440", pages="1--1", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc440.txt", key="RFC 440", doi="10.17487/RFC0440", } @misc{rfc441, author="R.D. Bressler and R. Thomas", title="{Inter-Entity Communication - an experiment}", howpublished="RFC 441", series="Internet Request for Comments", type="RFC", number="441", pages="1--7", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc441.txt", key="RFC 441", doi="10.17487/RFC0441", } @misc{rfc442, author="V. Cerf", title="{Current flow-control scheme for IMPSYS}", howpublished="RFC 442", series="Internet Request for Comments", type="RFC", number="442", pages="1--7", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 449", url="https://www.rfc-editor.org/rfc/rfc442.txt", key="RFC 442", doi="10.17487/RFC0442", } @misc{rfc443, author="A.M. McKenzie", title="{Traffic statistics (December 1972)}", howpublished="RFC 443", series="Internet Request for Comments", type="RFC", number="443", pages="1--3", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc443.txt", key="RFC 443", doi="10.17487/RFC0443", } @misc{rfc445, author="A.M. McKenzie", title="{IMP/TIP preventive maintenance schedule}", howpublished="RFC 445", series="Internet Request for Comments", type="RFC", number="445", pages="1--2", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc445.txt", key="RFC 445", doi="10.17487/RFC0445", } @misc{rfc446, author="L.P. Deutsch", title="{Proposal to consider a network program resource notebook}", howpublished="RFC 446", series="Internet Request for Comments", type="RFC", number="446", pages="1--2", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc446.txt", key="RFC 446", doi="10.17487/RFC0446", } @misc{rfc447, author="A.M. McKenzie", title="{IMP/TIP memory retrofit schedule}", howpublished="RFC 447", series="Internet Request for Comments", type="RFC", number="447", pages="1--2", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 476", url="https://www.rfc-editor.org/rfc/rfc447.txt", key="RFC 447", doi="10.17487/RFC0447", } @misc{rfc448, author="R.T. Braden", title="{Print files in FTP}", howpublished="RFC 448", series="Internet Request for Comments", type="RFC", number="448", pages="1--3", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc448.txt", key="RFC 448", doi="10.17487/RFC0448", } @misc{rfc449, author="D.C. Walden", title="{Current flow-control scheme for IMPSYS}", howpublished="RFC 449", series="Internet Request for Comments", type="RFC", number="449", pages="1--1", year=1973, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc449.txt", key="RFC 449", doi="10.17487/RFC0449", } @misc{rfc450, author="M.A. Padlipsky", title="{MULTICS sampling timeout change}", howpublished="RFC 450", series="Internet Request for Comments", type="RFC", number="450", pages="1--1", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc450.txt", key="RFC 450", doi="10.17487/RFC0450", } @misc{rfc451, author="M.A. Padlipsky", title="{Tentative proposal for a Unified User Level Protocol}", howpublished="RFC 451", series="Internet Request for Comments", type="RFC", number="451", pages="1--3", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc451.txt", key="RFC 451", doi="10.17487/RFC0451", } @misc{rfc452, author="J. Winett", title="{TELNET Command at Host LL}", howpublished="RFC 452", series="Internet Request for Comments", type="RFC", number="452", pages="1--14", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc452.txt", key="RFC 452", doi="10.17487/RFC0452", } @misc{rfc453, author="M.D. Kudlick", title="{Meeting announcement to discuss a network mail system}", howpublished="RFC 453", series="Internet Request for Comments", type="RFC", number="453", pages="1--3", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc453.txt", key="RFC 453", doi="10.17487/RFC0453", } @misc{rfc454, author="A.M. McKenzie", title="{File Transfer Protocol - meeting announcement and a new proposed document}", howpublished="RFC 454", series="Internet Request for Comments", type="RFC", number="454", pages="1--35", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc454.txt", key="RFC 454", keywords="FTP", doi="10.17487/RFC0454", } @misc{rfc455, author="A.M. McKenzie", title="{Traffic statistics (January 1973)}", howpublished="RFC 455", series="Internet Request for Comments", type="RFC", number="455", pages="1--3", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc455.txt", key="RFC 455", doi="10.17487/RFC0455", } @misc{rfc456, author="M.D. Kudlick", title="{Memorandum: Date change of mail meeting}", howpublished="RFC 456", series="Internet Request for Comments", type="RFC", number="456", pages="1--1", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc456.txt", key="RFC 456", doi="10.17487/RFC0456", } @misc{rfc457, author="D.C. Walden", title="{TIPUG}", howpublished="RFC 457", series="Internet Request for Comments", type="RFC", number="457", pages="1--1", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc457.txt", key="RFC 457", doi="10.17487/RFC0457", } @misc{rfc458, author="R.D. Bressler and R. Thomas", title="{Mail retrieval via FTP}", howpublished="RFC 458", series="Internet Request for Comments", type="RFC", number="458", pages="1--2", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc458.txt", key="RFC 458", doi="10.17487/RFC0458", } @misc{rfc459, author="W. Kantrowitz", title="{Network questionnaires}", howpublished="RFC 459", series="Internet Request for Comments", type="RFC", number="459", pages="1--1", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc459.txt", key="RFC 459", doi="10.17487/RFC0459", } @misc{rfc460, author="C. Kline", title="{NCP survey}", howpublished="RFC 460", series="Internet Request for Comments", type="RFC", number="460", pages="1--7", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc460.txt", key="RFC 460", doi="10.17487/RFC0460", } @misc{rfc461, author="A.M. McKenzie", title="{Telnet Protocol meeting announcement}", howpublished="RFC 461", series="Internet Request for Comments", type="RFC", number="461", pages="1--1", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc461.txt", key="RFC 461", doi="10.17487/RFC0461", } @misc{rfc462, author="J. Iseli and D. Crocker", title="{Responding to user needs}", howpublished="RFC 462", series="Internet Request for Comments", type="RFC", number="462", pages="1--2", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc462.txt", key="RFC 462", doi="10.17487/RFC0462", } @misc{rfc463, author="A.K. Bhushan", title="{FTP comments and response to RFC 430}", howpublished="RFC 463", series="Internet Request for Comments", type="RFC", number="463", pages="1--3", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc463.txt", key="RFC 463", doi="10.17487/RFC0463", } @misc{rfc464, author="M.D. Kudlick", title="{Resource notebook framework}", howpublished="RFC 464", series="Internet Request for Comments", type="RFC", number="464", pages="1--2", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc464.txt", key="RFC 464", doi="10.17487/RFC0464", } @misc{rfc466, author="J.M. Winett", title="{Telnet logger/server for host LL-67}", howpublished="RFC 466", series="Internet Request for Comments", type="RFC", number="466", pages="1--9", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc466.txt", key="RFC 466", doi="10.17487/RFC0466", } @misc{rfc467, author="J.D. Burchfiel and R.S. Tomlinson", title="{Proposed change to Host-Host Protocol: Resynchronization of connection status}", howpublished="RFC 467", series="Internet Request for Comments", type="RFC", number="467", pages="1--7", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 492", url="https://www.rfc-editor.org/rfc/rfc467.txt", key="RFC 467", doi="10.17487/RFC0467", } @misc{rfc468, author="R.T. Braden", title="{FTP data compression}", howpublished="RFC 468", series="Internet Request for Comments", type="RFC", number="468", pages="1--7", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc468.txt", key="RFC 468", doi="10.17487/RFC0468", } @misc{rfc469, author="M.D. Kudlick", title="{Network mail meeting summary}", howpublished="RFC 469", series="Internet Request for Comments", type="RFC", number="469", pages="1--10", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc469.txt", key="RFC 469", keywords="network, mail, meeting", doi="10.17487/RFC0469", } @misc{rfc470, author="R. Thomas", title="{Change in socket for TIP news facility}", howpublished="RFC 470", series="Internet Request for Comments", type="RFC", number="470", pages="1--1", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc470.txt", key="RFC 470", doi="10.17487/RFC0470", } @misc{rfc471, author="R. Thomas", title="{Workshop on multi-site executive programs}", howpublished="RFC 471", series="Internet Request for Comments", type="RFC", number="471", pages="1--2", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc471.txt", key="RFC 471", doi="10.17487/RFC0471", } @misc{rfc472, author="S. Bunch", title="{Illinois' reply to Maxwell's request for graphics information (NIC 14925)}", howpublished="RFC 472", series="Internet Request for Comments", type="RFC", number="472", pages="1--2", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc472.txt", key="RFC 472", doi="10.17487/RFC0472", } @misc{rfc473, author="D.C. Walden", title="{MIX and MIXAL?}", howpublished="RFC 473", series="Internet Request for Comments", type="RFC", number="473", pages="1--1", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc473.txt", key="RFC 473", doi="10.17487/RFC0473", } @misc{rfc474, author="S. Bunch", title="{Announcement of NGWG meeting: Call for papers}", howpublished="RFC 474", series="Internet Request for Comments", type="RFC", number="474", pages="1--2", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc474.txt", key="RFC 474", doi="10.17487/RFC0474", } @misc{rfc475, author="A.K. Bhushan", title="{FTP and Network Mail System}", howpublished="RFC 475", series="Internet Request for Comments", type="RFC", number="475", pages="1--5", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc475.txt", key="RFC 475", doi="10.17487/RFC0475", } @misc{rfc476, author="A.M. McKenzie", title="{IMP/TIP memory retrofit schedule (rev 2)}", howpublished="RFC 476", series="Internet Request for Comments", type="RFC", number="476", pages="1--2", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc476.txt", key="RFC 476", doi="10.17487/RFC0476", } @misc{rfc477, author="M. Krilanovich", title="{Remote Job Service at UCSB}", howpublished="RFC 477", series="Internet Request for Comments", type="RFC", number="477", pages="1--19", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc477.txt", key="RFC 477", doi="10.17487/RFC0477", } @misc{rfc478, author="R.D. Bressler and R. Thomas", title="{FTP server-server interaction - II}", howpublished="RFC 478", series="Internet Request for Comments", type="RFC", number="478", pages="1--2", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc478.txt", key="RFC 478", doi="10.17487/RFC0478", } @misc{rfc479, author="J.E. White", title="{Use of FTP by the NIC Journal}", howpublished="RFC 479", series="Internet Request for Comments", type="RFC", number="479", pages="1--5", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc479.txt", key="RFC 479", doi="10.17487/RFC0479", } @misc{rfc480, author="J.E. White", title="{Host-dependent FTP parameters}", howpublished="RFC 480", series="Internet Request for Comments", type="RFC", number="480", pages="1--1", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc480.txt", key="RFC 480", doi="10.17487/RFC0480", } @misc{rfc482, author="A.M. McKenzie", title="{Traffic statistics (February 1973)}", howpublished="RFC 482", series="Internet Request for Comments", type="RFC", number="482", pages="1--4", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 497", url="https://www.rfc-editor.org/rfc/rfc482.txt", key="RFC 482", doi="10.17487/RFC0482", } @misc{rfc483, author="M.D. Kudlick", title="{Cancellation of the resource notebook framework meeting}", howpublished="RFC 483", series="Internet Request for Comments", type="RFC", number="483", pages="1--1", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc483.txt", key="RFC 483", doi="10.17487/RFC0483", } @misc{rfc485, author="J.R. Pickens", title="{MIX and MIXAL at UCSB}", howpublished="RFC 485", series="Internet Request for Comments", type="RFC", number="485", pages="1--1", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc485.txt", key="RFC 485", doi="10.17487/RFC0485", } @misc{rfc486, author="R.D. Bressler", title="{Data transfer revisited}", howpublished="RFC 486", series="Internet Request for Comments", type="RFC", number="486", pages="1--2", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc486.txt", key="RFC 486", keywords="RJE, FTP", doi="10.17487/RFC0486", } @misc{rfc487, author="R.D. Bressler", title="{Free file transfer}", howpublished="RFC 487", series="Internet Request for Comments", type="RFC", number="487", pages="1--2", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc487.txt", key="RFC 487", keywords="FTP", doi="10.17487/RFC0487", } @misc{rfc488, author="M.F. Auerbach", title="{NLS classes at network sites}", howpublished="RFC 488", series="Internet Request for Comments", type="RFC", number="488", pages="1--2", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc488.txt", key="RFC 488", doi="10.17487/RFC0488", } @misc{rfc489, author="J. Postel", title="{Comment on resynchronization of connection status proposal}", howpublished="RFC 489", series="Internet Request for Comments", type="RFC", number="489", pages="1--1", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc489.txt", key="RFC 489", doi="10.17487/RFC0489", } @misc{rfc490, author="J.R. Pickens", title="{Surrogate RJS for UCLA-CCN}", howpublished="RFC 490", series="Internet Request for Comments", type="RFC", number="490", pages="1--6", year=1973, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc490.txt", key="RFC 490", doi="10.17487/RFC0490", } @misc{rfc491, author="M.A. Padlipsky", title="{What is ``Free''?}", howpublished="RFC 491", series="Internet Request for Comments", type="RFC", number="491", pages="1--2", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc491.txt", key="RFC 491", doi="10.17487/RFC0491", } @misc{rfc492, author="E. Meyer", title="{Response to RFC 467}", howpublished="RFC 492", series="Internet Request for Comments", type="RFC", number="492", pages="1--7", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc492.txt", key="RFC 492", doi="10.17487/RFC0492", } @misc{rfc493, author="J.C. Michener and I.W. Cotton and K.C. Kelley and D.E. Liddle and E. Meyer", title="{GRAPHICS PROTOCOL}", howpublished="RFC 493", series="Internet Request for Comments", type="RFC", number="493", pages="1--28", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc493.txt", key="RFC 493", doi="10.17487/RFC0493", } @misc{rfc494, author="D.C. Walden", title="{Availability of MIX and MIXAL in the Network}", howpublished="RFC 494", series="Internet Request for Comments", type="RFC", number="494", pages="1--1", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc494.txt", key="RFC 494", doi="10.17487/RFC0494", } @misc{rfc495, author="A.M. McKenzie", title="{Telnet Protocol specifications}", howpublished="RFC 495", series="Internet Request for Comments", type="RFC", number="495", pages="1--2", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 562", url="https://www.rfc-editor.org/rfc/rfc495.txt", key="RFC 495", doi="10.17487/RFC0495", } @misc{rfc496, author="M.F. Auerbach", title="{TNLS quick reference card is available}", howpublished="RFC 496", series="Internet Request for Comments", type="RFC", number="496", pages="1--1", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc496.txt", key="RFC 496", doi="10.17487/RFC0496", } @misc{rfc497, author="A.M. McKenzie", title="{Traffic Statistics (March 1973)}", howpublished="RFC 497", series="Internet Request for Comments", type="RFC", number="497", pages="1--4", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc497.txt", key="RFC 497", doi="10.17487/RFC0497", } @misc{rfc498, author="R.T. Braden", title="{On mail service to CCN}", howpublished="RFC 498", series="Internet Request for Comments", type="RFC", number="498", pages="1--3", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc498.txt", key="RFC 498", doi="10.17487/RFC0498", } @misc{rfc499, author="B.R. Reussow", title="{Harvard's network RJE}", howpublished="RFC 499", series="Internet Request for Comments", type="RFC", number="499", pages="1--6", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc499.txt", key="RFC 499", doi="10.17487/RFC0499", } @misc{rfc500, author="A. Shoshani and I. Spiegler", title="{Integration of data management systems on a computer network}", howpublished="RFC 500", series="Internet Request for Comments", type="RFC", number="500", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc500.txt", key="RFC 500", doi="10.17487/RFC0500", } @misc{rfc501, author="K.T. Pogran", title="{Un-muddling ``free file transfer''}", howpublished="RFC 501", series="Internet Request for Comments", type="RFC", number="501", pages="1--5", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc501.txt", key="RFC 501", keywords="FTP", doi="10.17487/RFC0501", } @misc{rfc503, author="N. Neigus and J. Postel", title="{Socket number list}", howpublished="RFC 503", series="Internet Request for Comments", type="RFC", number="503", pages="1--8", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 739", url="https://www.rfc-editor.org/rfc/rfc503.txt", key="RFC 503", doi="10.17487/RFC0503", } @misc{rfc504, author="R. Thomas", title="{Distributed resources workshop announcement}", howpublished="RFC 504", series="Internet Request for Comments", type="RFC", number="504", pages="1--5", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc504.txt", key="RFC 504", doi="10.17487/RFC0504", } @misc{rfc505, author="M.A. Padlipsky", title="{Two solutions to a file transfer access problem}", howpublished="RFC 505", series="Internet Request for Comments", type="RFC", number="505", pages="1--3", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc505.txt", key="RFC 505", keywords="FTP, free", doi="10.17487/RFC0505", } @misc{rfc506, author="M.A. Padlipsky", title="{FTP command naming problem}", howpublished="RFC 506", series="Internet Request for Comments", type="RFC", number="506", pages="1--1", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc506.txt", key="RFC 506", doi="10.17487/RFC0506", } @misc{rfc508, author="L. Pfeifer and J. McAfee", title="{Real-time data transmission on the ARPANET}", howpublished="RFC 508", series="Internet Request for Comments", type="RFC", number="508", pages="1--10", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc508.txt", key="RFC 508", doi="10.17487/RFC0508", } @misc{rfc509, author="A.M. McKenzie", title="{Traffic statistics (April 1973)}", howpublished="RFC 509", series="Internet Request for Comments", type="RFC", number="509", pages="1--4", year=1973, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc509.txt", key="RFC 509", doi="10.17487/RFC0509", } @misc{rfc510, author="J.E. White", title="{Request for network mailbox addresses}", howpublished="RFC 510", series="Internet Request for Comments", type="RFC", number="510", pages="1--2", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc510.txt", key="RFC 510", doi="10.17487/RFC0510", } @misc{rfc511, author="J.B. North", title="{Enterprise phone service to NIC from ARPANET sites}", howpublished="RFC 511", series="Internet Request for Comments", type="RFC", number="511", pages="1--4", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc511.txt", key="RFC 511", doi="10.17487/RFC0511", } @misc{rfc512, author="W. Hathaway", title="{More on lost message detection}", howpublished="RFC 512", series="Internet Request for Comments", type="RFC", number="512", pages="1--2", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc512.txt", key="RFC 512", doi="10.17487/RFC0512", } @misc{rfc513, author="W. Hathaway", title="{Comments on the new Telnet specifications}", howpublished="RFC 513", series="Internet Request for Comments", type="RFC", number="513", pages="1--3", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc513.txt", key="RFC 513", doi="10.17487/RFC0513", } @misc{rfc514, author="W. Kantrowitz", title="{Network make-work}", howpublished="RFC 514", series="Internet Request for Comments", type="RFC", number="514", pages="1--4", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc514.txt", key="RFC 514", doi="10.17487/RFC0514", } @misc{rfc515, author="R. Winter", title="{Specifications for Datalanguage, Version 0/9}", howpublished="RFC 515", series="Internet Request for Comments", type="RFC", number="515", pages="1--31", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc515.txt", key="RFC 515", doi="10.17487/RFC0515", } @misc{rfc516, author="J. Postel", title="{Lost message detection}", howpublished="RFC 516", series="Internet Request for Comments", type="RFC", number="516", pages="1--2", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc516.txt", key="RFC 516", doi="10.17487/RFC0516", } @misc{rfc518, author="N. Vaughan and E.J. Feinler", title="{ARPANET accounts}", howpublished="RFC 518", series="Internet Request for Comments", type="RFC", number="518", pages="1--9", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc518.txt", key="RFC 518", doi="10.17487/RFC0518", } @misc{rfc519, author="J.R. Pickens", title="{Resource Evaluation}", howpublished="RFC 519", series="Internet Request for Comments", type="RFC", number="519", pages="1--4", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc519.txt", key="RFC 519", doi="10.17487/RFC0519", } @misc{rfc520, author="J.D. Day", title="{Memo to FTP group: Proposal for File Access Protocol}", howpublished="RFC 520", series="Internet Request for Comments", type="RFC", number="520", pages="1--8", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc520.txt", key="RFC 520", doi="10.17487/RFC0520", } @misc{rfc521, author="A.M. McKenzie", title="{Restricted use of IMP DDT}", howpublished="RFC 521", series="Internet Request for Comments", type="RFC", number="521", pages="1--2", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc521.txt", key="RFC 521", doi="10.17487/RFC0521", } @misc{rfc522, author="A.M. McKenzie", title="{Traffic Statistics (May 1973)}", howpublished="RFC 522", series="Internet Request for Comments", type="RFC", number="522", pages="1--4", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc522.txt", key="RFC 522", doi="10.17487/RFC0522", } @misc{rfc523, author="A.K. Bhushan", title="{SURVEY is in operation again}", howpublished="RFC 523", series="Internet Request for Comments", type="RFC", number="523", pages="1--2", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc523.txt", key="RFC 523", doi="10.17487/RFC0523", } @misc{rfc524, author="J.E. White", title="{Proposed Mail Protocol}", howpublished="RFC 524", series="Internet Request for Comments", type="RFC", number="524", pages="1--40", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc524.txt", key="RFC 524", doi="10.17487/RFC0524", } @misc{rfc525, author="W. Parrish and J.R. Pickens", title="{MIT-MATHLAB meets UCSB-OLS -an example of resource sharing}", howpublished="RFC 525", series="Internet Request for Comments", type="RFC", number="525", pages="1--9", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc525.txt", key="RFC 525", doi="10.17487/RFC0525", } @misc{rfc526, author="W.K. Pratt", title="{Technical meeting: Digital image processing software systems}", howpublished="RFC 526", series="Internet Request for Comments", type="RFC", number="526", pages="1--3", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc526.txt", key="RFC 526", doi="10.17487/RFC0526", } @misc{rfc527, author="R. Merryman", title="{ARPAWOCKY}", howpublished="RFC 527", series="Internet Request for Comments", type="RFC", number="527", pages="1--1", year=1973, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc527.txt", key="RFC 527", doi="10.17487/RFC0527", } @misc{rfc528, author="J.M. McQuillan", title="{Software checksumming in the IMP and network reliability}", howpublished="RFC 528", series="Internet Request for Comments", type="RFC", number="528", pages="1--9", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc528.txt", key="RFC 528", doi="10.17487/RFC0528", } @misc{rfc529, author="A.M. McKenzie and R. Thomas and R.S. Tomlinson and K.T. Pogran", title="{Note on protocol synch sequences}", howpublished="RFC 529", series="Internet Request for Comments", type="RFC", number="529", pages="1--4", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc529.txt", key="RFC 529", doi="10.17487/RFC0529", } @misc{rfc530, author="A.K. Bhushan", title="{Report on the Survey Project}", howpublished="RFC 530", series="Internet Request for Comments", type="RFC", number="530", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc530.txt", key="RFC 530", doi="10.17487/RFC0530", } @misc{rfc531, author="M.A. Padlipsky", title="{Feast or famine? A response to two recent RFC's about network information}", howpublished="RFC 531", series="Internet Request for Comments", type="RFC", number="531", pages="1--2", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc531.txt", key="RFC 531", doi="10.17487/RFC0531", } @misc{rfc532, author="R.G. Merryman", title="{UCSD-CC Server-FTP facility}", howpublished="RFC 532", series="Internet Request for Comments", type="RFC", number="532", pages="1--4", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc532.txt", key="RFC 532", keywords="FTP, server", doi="10.17487/RFC0532", } @misc{rfc533, author="D.C. Walden", title="{Message-ID numbers}", howpublished="RFC 533", series="Internet Request for Comments", type="RFC", number="533", pages="1--1", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc533.txt", key="RFC 533", doi="10.17487/RFC0533", } @misc{rfc534, author="D.C. Walden", title="{Lost message detection}", howpublished="RFC 534", series="Internet Request for Comments", type="RFC", number="534", pages="1--2", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc534.txt", key="RFC 534", doi="10.17487/RFC0534", } @misc{rfc535, author="R. Thomas", title="{Comments on File Access Protocol}", howpublished="RFC 535", series="Internet Request for Comments", type="RFC", number="535", pages="1--4", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc535.txt", key="RFC 535", doi="10.17487/RFC0535", } @misc{rfc537, author="S. Bunch", title="{Announcement of NGG meeting July 16-17}", howpublished="RFC 537", series="Internet Request for Comments", type="RFC", number="537", pages="1--2", year=1973, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc537.txt", key="RFC 537", doi="10.17487/RFC0537", } @misc{rfc538, author="A.M. McKenzie", title="{Traffic statistics (June 1973)}", howpublished="RFC 538", series="Internet Request for Comments", type="RFC", number="538", pages="1--4", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 556", url="https://www.rfc-editor.org/rfc/rfc538.txt", key="RFC 538", doi="10.17487/RFC0538", } @misc{rfc539, author="D. Crocker and J. Postel", title="{Thoughts on the mail protocol proposed in RFC 524}", howpublished="RFC 539", series="Internet Request for Comments", type="RFC", number="539", pages="1--3", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc539.txt", key="RFC 539", doi="10.17487/RFC0539", } @misc{rfc542, author="N. Neigus", title="{File Transfer Protocol}", howpublished="RFC 542", series="Internet Request for Comments", type="RFC", number="542", pages="1--40", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 765, updated by RFCs 614, 640", url="https://www.rfc-editor.org/rfc/rfc542.txt", key="RFC 542", keywords="FTP", doi="10.17487/RFC0542", } @misc{rfc543, author="N.D. Meyer", title="{Network journal submission and delivery}", howpublished="RFC 543", series="Internet Request for Comments", type="RFC", number="543", pages="1--8", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc543.txt", key="RFC 543", doi="10.17487/RFC0543", } @misc{rfc544, author="N.D. Meyer and K. Kelley", title="{Locating on-line documentation at SRI-ARC}", howpublished="RFC 544", series="Internet Request for Comments", type="RFC", number="544", pages="1--1", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc544.txt", key="RFC 544", doi="10.17487/RFC0544", } @misc{rfc545, author="J.R. Pickens", title="{Of what quality be the UCSB resources evaluators?}", howpublished="RFC 545", series="Internet Request for Comments", type="RFC", number="545", pages="1--2", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc545.txt", key="RFC 545", doi="10.17487/RFC0545", } @misc{rfc546, author="R. Thomas", title="{Tenex load averages for July 1973}", howpublished="RFC 546", series="Internet Request for Comments", type="RFC", number="546", pages="1--4", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc546.txt", key="RFC 546", doi="10.17487/RFC0546", } @misc{rfc547, author="D.C. Walden", title="{Change to the Very Distant Host specification}", howpublished="RFC 547", series="Internet Request for Comments", type="RFC", number="547", pages="1--3", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc547.txt", key="RFC 547", doi="10.17487/RFC0547", } @misc{rfc548, author="D.C. Walden", title="{Hosts using the IMP Going Down message}", howpublished="RFC 548", series="Internet Request for Comments", type="RFC", number="548", pages="1--1", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc548.txt", key="RFC 548", doi="10.17487/RFC0548", } @misc{rfc549, author="J.C. Michener", title="{Minutes of Network Graphics Group meeting, 15-17 July 1973}", howpublished="RFC 549", series="Internet Request for Comments", type="RFC", number="549", pages="1--12", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc549.txt", key="RFC 549", doi="10.17487/RFC0549", } @misc{rfc550, author="L.P. Deutsch", title="{NIC NCP experiment}", howpublished="RFC 550", series="Internet Request for Comments", type="RFC", number="550", pages="1--2", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc550.txt", key="RFC 550", doi="10.17487/RFC0550", } @misc{rfc551, author="Y. Feinroth and R. Fink", title="{NYU, ANL, and LBL Joining the Net}", howpublished="RFC 551", series="Internet Request for Comments", type="RFC", number="551", pages="1--2", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc551.txt", key="RFC 551", doi="10.17487/RFC0551", } @misc{rfc552, author="A.D. Owen", title="{Single access to standard protocols}", howpublished="RFC 552", series="Internet Request for Comments", type="RFC", number="552", pages="1--1", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc552.txt", key="RFC 552", doi="10.17487/RFC0552", } @misc{rfc553, author="C.H. Irby and K. Victor", title="{Draft design for a text/graphics protocol}", howpublished="RFC 553", series="Internet Request for Comments", type="RFC", number="553", pages="1--19", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc553.txt", key="RFC 553", doi="10.17487/RFC0553", } @misc{rfc555, author="J.E. White", title="{Responses to critiques of the proposed mail protocol}", howpublished="RFC 555", series="Internet Request for Comments", type="RFC", number="555", pages="1--11", year=1973, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc555.txt", key="RFC 555", doi="10.17487/RFC0555", } @misc{rfc556, author="A.M. McKenzie", title="{Traffic Statistics (July 1973)}", howpublished="RFC 556", series="Internet Request for Comments", type="RFC", number="556", pages="1--4", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc556.txt", key="RFC 556", doi="10.17487/RFC0556", } @misc{rfc557, author="B.D. Wessler", title="{REVELATIONS IN NETWORK HOST MEASUREMENTS}", howpublished="RFC 557", series="Internet Request for Comments", type="RFC", number="557", pages="1--2", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc557.txt", key="RFC 557", doi="10.17487/RFC0557", } @misc{rfc559, author="A.K. Bushan", title="{Comments on The New Telnet Protocol and its Implementation}", howpublished="RFC 559", series="Internet Request for Comments", type="RFC", number="559", pages="1--5", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc559.txt", key="RFC 559", doi="10.17487/RFC0559", } @misc{rfc560, author="D. Crocker and J. Postel", title="{Remote Controlled Transmission and Echoing Telnet option}", howpublished="RFC 560", series="Internet Request for Comments", type="RFC", number="560", pages="1--12", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 581", url="https://www.rfc-editor.org/rfc/rfc560.txt", key="RFC 560", doi="10.17487/RFC0560", } @misc{rfc561, author="A.K. Bhushan and K.T. Pogran and R.S. Tomlinson and J.E. White", title="{Standardizing Network Mail Headers}", howpublished="RFC 561", series="Internet Request for Comments", type="RFC", number="561", pages="1--3", year=1973, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 680", url="https://www.rfc-editor.org/rfc/rfc561.txt", key="RFC 561", doi="10.17487/RFC0561", } @misc{rfc562, author="A.M. McKenzie", title="{Modifications to the TELNET Specification}", howpublished="RFC 562", series="Internet Request for Comments", type="RFC", number="562", pages="1--2", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc562.txt", key="RFC 562", doi="10.17487/RFC0562", } @misc{rfc563, author="J. Davidson", title="{Comments on the RCTE Telnet option}", howpublished="RFC 563", series="Internet Request for Comments", type="RFC", number="563", pages="1--5", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc563.txt", key="RFC 563", doi="10.17487/RFC0563", } @misc{rfc565, author="D. Cantor", title="{Storing network survey data at the datacomputer}", howpublished="RFC 565", series="Internet Request for Comments", type="RFC", number="565", pages="1--5", year=1973, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc565.txt", key="RFC 565", doi="10.17487/RFC0565", } @misc{rfc566, author="A.M. McKenzie", title="{Traffic statistics (August 1973)}", howpublished="RFC 566", series="Internet Request for Comments", type="RFC", number="566", pages="1--4", year=1973, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 579", url="https://www.rfc-editor.org/rfc/rfc566.txt", key="RFC 566", doi="10.17487/RFC0566", } @misc{rfc567, author="L.P. Deutsch", title="{Cross Country Network Bandwidth}", howpublished="RFC 567", series="Internet Request for Comments", type="RFC", number="567", pages="1--1", year=1973, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 568", url="https://www.rfc-editor.org/rfc/rfc567.txt", key="RFC 567", doi="10.17487/RFC0567", } @misc{rfc568, author="J.M. McQuillan", title="{Response to RFC 567 - cross country network bandwidth}", howpublished="RFC 568", series="Internet Request for Comments", type="RFC", number="568", pages="1--3", year=1973, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc568.txt", key="RFC 568", doi="10.17487/RFC0568", } @misc{rfc569, author="M.A. Padlipsky", title="{NETED: A Common Editor for the ARPA Network}", howpublished="RFC 569 (Historic)", series="Internet Request for Comments", type="RFC", number="569", pages="1--6", year=1973, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc569.txt", key="RFC 569", keywords="NETED", doi="10.17487/RFC0569", } @misc{rfc570, author="J.R. Pickens", title="{Experimental input mapping between NVT ASCII and UCSB On Line System}", howpublished="RFC 570", series="Internet Request for Comments", type="RFC", number="570", pages="1--1", year=1973, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc570.txt", key="RFC 570", doi="10.17487/RFC0570", } @misc{rfc571, author="R. Braden", title="{TENEX FTP PROBLEM}", howpublished="RFC 571", series="Internet Request for Comments", type="RFC", number="571", pages="1--1", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc571.txt", key="RFC 571", doi="10.17487/RFC0571", } @misc{rfc573, author="A. Bhushan", title="{DATA AND FILE TRANSFER - SOME MEASUREMENT RESULTS}", howpublished="RFC 573", series="Internet Request for Comments", type="RFC", number="573", pages="1--8", year=1973, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc573.txt", key="RFC 573", doi="10.17487/RFC0573", } @misc{rfc574, author="M. Krilanovich", title="{Announcement of a Mail Facility at UCSB}", howpublished="RFC 574", series="Internet Request for Comments", type="RFC", number="574", pages="1--1", year=1973, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc574.txt", key="RFC 574", doi="10.17487/RFC0574", } @misc{rfc576, author="K. Victor", title="{Proposal for modifying linking}", howpublished="RFC 576", series="Internet Request for Comments", type="RFC", number="576", pages="1--2", year=1973, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc576.txt", key="RFC 576", doi="10.17487/RFC0576", } @misc{rfc577, author="D. Crocker", title="{Mail priority}", howpublished="RFC 577", series="Internet Request for Comments", type="RFC", number="577", pages="1--2", year=1973, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc577.txt", key="RFC 577", doi="10.17487/RFC0577", } @misc{rfc578, author="A.K. Bhushan and N.D. Ryan", title="{Using MIT-Mathlab MACSYMA from MIT-DMS Muddle}", howpublished="RFC 578", series="Internet Request for Comments", type="RFC", number="578", pages="1--9", year=1973, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc578.txt", key="RFC 578", doi="10.17487/RFC0578", } @misc{rfc579, author="A.M. McKenzie", title="{Traffic statistics (September 1973)}", howpublished="RFC 579", series="Internet Request for Comments", type="RFC", number="579", pages="1--5", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 586", url="https://www.rfc-editor.org/rfc/rfc579.txt", key="RFC 579", doi="10.17487/RFC0579", } @misc{rfc580, author="J. Postel", title="{Note to Protocol Designers and Implementers}", howpublished="RFC 580", series="Internet Request for Comments", type="RFC", number="580", pages="1--1", year=1973, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 582", url="https://www.rfc-editor.org/rfc/rfc580.txt", key="RFC 580", doi="10.17487/RFC0580", } @misc{rfc581, author="D. Crocker and J. Postel", title="{Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet Option}", howpublished="RFC 581", series="Internet Request for Comments", type="RFC", number="581", pages="1--5", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc581.txt", key="RFC 581", doi="10.17487/RFC0581", } @misc{rfc582, author="R. Clements", title="{Comments on RFC 580: Machine readable protocols}", howpublished="RFC 582", series="Internet Request for Comments", type="RFC", number="582", pages="1--1", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc582.txt", key="RFC 582", doi="10.17487/RFC0582", } @misc{rfc584, author="J. Iseli and D. Crocker and N. Neigus", title="{Charter for ARPANET Users Interest Working Group}", howpublished="RFC 584", series="Internet Request for Comments", type="RFC", number="584", pages="1--3", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc584.txt", key="RFC 584", doi="10.17487/RFC0584", } @misc{rfc585, author="D. Crocker and N. Neigus and E.J. Feinler and J. Iseli", title="{ARPANET users interest working group meeting}", howpublished="RFC 585", series="Internet Request for Comments", type="RFC", number="585", pages="1--9", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc585.txt", key="RFC 585", doi="10.17487/RFC0585", } @misc{rfc586, author="A.M. McKenzie", title="{Traffic statistics (October 1973)}", howpublished="RFC 586", series="Internet Request for Comments", type="RFC", number="586", pages="1--5", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc586.txt", key="RFC 586", doi="10.17487/RFC0586", } @misc{rfc587, author="J. Postel", title="{Announcing New Telnet Options}", howpublished="RFC 587", series="Internet Request for Comments", type="RFC", number="587", pages="1--1", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc587.txt", key="RFC 587", doi="10.17487/RFC0587", } @misc{rfc588, author="A. Stokes", title="{London Node Is Now Up}", howpublished="RFC 588", series="Internet Request for Comments", type="RFC", number="588", pages="1--3", year=1973, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc588.txt", key="RFC 588", doi="10.17487/RFC0588", } @misc{rfc589, author="R.T. Braden", title="{CCN NETRJS server messages to remote user}", howpublished="RFC 589", series="Internet Request for Comments", type="RFC", number="589", pages="1--5", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc589.txt", key="RFC 589", doi="10.17487/RFC0589", } @misc{rfc590, author="M.A. Padlipsky", title="{MULTICS address change}", howpublished="RFC 590", series="Internet Request for Comments", type="RFC", number="590", pages="1--1", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc590.txt", key="RFC 590", doi="10.17487/RFC0590", } @misc{rfc591, author="D.C. Walden", title="{Addition to the Very Distant Host specifications}", howpublished="RFC 591", series="Internet Request for Comments", type="RFC", number="591", pages="1--1", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc591.txt", key="RFC 591", doi="10.17487/RFC0591", } @misc{rfc592, author="R.W. Watson", title="{Some thoughts on system design to facilitate resource sharing}", howpublished="RFC 592", series="Internet Request for Comments", type="RFC", number="592", pages="1--5", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc592.txt", key="RFC 592", doi="10.17487/RFC0592", } @misc{rfc593, author="A.M. McKenzie and J. Postel", title="{Telnet and FTP implementation schedule change}", howpublished="RFC 593", series="Internet Request for Comments", type="RFC", number="593", pages="1--1", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc593.txt", key="RFC 593", doi="10.17487/RFC0593", } @misc{rfc594, author="J.D. Burchfiel", title="{Speedup of Host-IMP interface}", howpublished="RFC 594", series="Internet Request for Comments", type="RFC", number="594", pages="1--3", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc594.txt", key="RFC 594", doi="10.17487/RFC0594", } @misc{rfc595, author="W. Hathaway", title="{Second thoughts in defense of the Telnet Go-Ahead}", howpublished="RFC 595", series="Internet Request for Comments", type="RFC", number="595", pages="1--5", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc595.txt", key="RFC 595", doi="10.17487/RFC0595", } @misc{rfc596, author="E.A. Taft", title="{Second thoughts on Telnet Go-Ahead}", howpublished="RFC 596", series="Internet Request for Comments", type="RFC", number="596", pages="1--5", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc596.txt", key="RFC 596", doi="10.17487/RFC0596", } @misc{rfc597, author="N. Neigus and E.J. Feinler", title="{Host status}", howpublished="RFC 597", series="Internet Request for Comments", type="RFC", number="597", pages="1--6", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 603", url="https://www.rfc-editor.org/rfc/rfc597.txt", key="RFC 597", doi="10.17487/RFC0597", } @misc{rfc598, author="Network Information Center. Stanford Research Institute", title="{RFC index - December 5, 1973}", howpublished="RFC 598", series="Internet Request for Comments", type="RFC", number="598", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc598.txt", key="RFC 598", doi="10.17487/RFC0598", } @misc{rfc599, author="R.T. Braden", title="{Update on NETRJS}", howpublished="RFC 599", series="Internet Request for Comments", type="RFC", number="599", pages="1--9", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 740", url="https://www.rfc-editor.org/rfc/rfc599.txt", key="RFC 599", doi="10.17487/RFC0599", } @misc{rfc600, author="A. Berggreen", title="{Interfacing an Illinois plasma terminal to the ARPANET}", howpublished="RFC 600", series="Internet Request for Comments", type="RFC", number="600", pages="1--3", year=1973, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc600.txt", key="RFC 600", abstract={Discusses some unusual interface issues for the Plato terminal.}, doi="10.17487/RFC0600", } @misc{rfc601, author="A.M. McKenzie", title="{Traffic statistics (November 1973)}", howpublished="RFC 601", series="Internet Request for Comments", type="RFC", number="601", pages="1--5", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc601.txt", key="RFC 601", doi="10.17487/RFC0601", } @misc{rfc602, author="R.M. Metcalfe", title="{``The stockings were hung by the chimney with care''}", howpublished="RFC 602", series="Internet Request for Comments", type="RFC", number="602", pages="1--1", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc602.txt", key="RFC 602", abstract={Susceptibility of ARPANET to security violations.}, keywords="security, violations, TIP, arpanet", doi="10.17487/RFC0602", } @misc{rfc603, author="J.D. Burchfiel", title="{Response to RFC 597: Host status}", howpublished="RFC 603", series="Internet Request for Comments", type="RFC", number="603", pages="1--1", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 613", url="https://www.rfc-editor.org/rfc/rfc603.txt", key="RFC 603", abstract={Questions about the ARPANET topology described in RFC 597.}, doi="10.17487/RFC0603", } @misc{rfc604, author="J. Postel", title="{Assigned link numbers}", howpublished="RFC 604", series="Internet Request for Comments", type="RFC", number="604", pages="1--2", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 739", url="https://www.rfc-editor.org/rfc/rfc604.txt", key="RFC 604", abstract={Modifies official host-host protocol. Replaces RFC 377.}, doi="10.17487/RFC0604", } @misc{rfc606, author="L.P. Deutsch", title="{Host names on-line}", howpublished="RFC 606", series="Internet Request for Comments", type="RFC", number="606", pages="1--3", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc606.txt", key="RFC 606", abstract={Resolving differences in hostname-address mappings; see also RFCs 627, 625, 623 and 608.}, keywords="lists, names, host, addresses", doi="10.17487/RFC0606", } @misc{rfc607, author="M. Krilanovich and G. Gregg", title="{Comments on the File Transfer Protocol}", howpublished="RFC 607", series="Internet Request for Comments", type="RFC", number="607", pages="1--3", year=1974, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 624, updated by RFC 614", url="https://www.rfc-editor.org/rfc/rfc607.txt", key="RFC 607", abstract={An old version; see RFC 624; see also RFCs 614, 542 and 640.}, keywords="solutions, weakness, ftp", doi="10.17487/RFC0607", } @misc{rfc608, author="M.D. Kudlick", title="{Host names on-line}", howpublished="RFC 608", series="Internet Request for Comments", type="RFC", number="608", pages="1--4", year=1974, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 810", url="https://www.rfc-editor.org/rfc/rfc608.txt", key="RFC 608", abstract={Response to RFC 606; see also RFCs 627, 625 and 623.}, doi="10.17487/RFC0608", } @misc{rfc609, author="B. Ferguson", title="{Statement of upcoming move of NIC/NLS service}", howpublished="RFC 609", series="Internet Request for Comments", type="RFC", number="609", pages="1--2", year=1974, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc609.txt", key="RFC 609", abstract={See also RFCs 621 and 620.}, doi="10.17487/RFC0609", } @misc{rfc610, author="R. Winter and J. Hill and W. Greiff", title="{Further datalanguage design concepts}", howpublished="RFC 610", series="Internet Request for Comments", type="RFC", number="610", pages="1--88", year=1973, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc610.txt", key="RFC 610", abstract={Preliminary results of the language design; a model for data languagea semantics; future considerations.}, doi="10.17487/RFC0610", } @misc{rfc611, author="D.C. Walden", title="{Two changes to the IMP/Host Protocol to improve user/network communications}", howpublished="RFC 611", series="Internet Request for Comments", type="RFC", number="611", pages="1--4", year=1974, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc611.txt", key="RFC 611", abstract={Expansion of Host-Going-Down and addition of Dead-Host-Status Message.}, doi="10.17487/RFC0611", } @misc{rfc612, author="A.M. McKenzie", title="{Traffic statistics (December 1973)}", howpublished="RFC 612", series="Internet Request for Comments", type="RFC", number="612", pages="1--6", year=1974, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc612.txt", key="RFC 612", doi="10.17487/RFC0612", } @misc{rfc613, author="A.M. McKenzie", title="{Network connectivity: A response to RFC 603}", howpublished="RFC 613", series="Internet Request for Comments", type="RFC", number="613", pages="1--1", year=1974, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc613.txt", key="RFC 613", doi="10.17487/RFC0613", } @misc{rfc614, author="K.T. Pogran and N. Neigus", title="{Response to RFC 607: ``Comments on the File Transfer Protocol''}", howpublished="RFC 614", series="Internet Request for Comments", type="RFC", number="614", pages="1--3", year=1974, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc614.txt", key="RFC 614", abstract={See also RFCs 624, 542 and 640.}, keywords="ftp, weakness, solutions", doi="10.17487/RFC0614", } @misc{rfc615, author="D. Crocker", title="{Proposed Network Standard Data Pathname syntax}", howpublished="RFC 615", series="Internet Request for Comments", type="RFC", number="615", pages="1--4", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 645", url="https://www.rfc-editor.org/rfc/rfc615.txt", key="RFC 615", doi="10.17487/RFC0615", } @misc{rfc616, author="D. Walden", title="{LATEST NETWORK MAPS}", howpublished="RFC 616", series="Internet Request for Comments", type="RFC", number="616", pages="1--1", year=1973, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc616.txt", key="RFC 616", keywords="Network, maps", doi="10.17487/RFC0616", } @misc{rfc617, author="E.A. Taft", title="{Note on socket number assignment}", howpublished="RFC 617", series="Internet Request for Comments", type="RFC", number="617", pages="1--3", year=1974, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc617.txt", key="RFC 617", abstract={Danger of imposing more fixed socket number requirements; see also RFCs 542, 503 and 451.}, keywords="telnet", doi="10.17487/RFC0617", } @misc{rfc618, author="E.A. Taft", title="{Few observations on NCP statistics}", howpublished="RFC 618", series="Internet Request for Comments", type="RFC", number="618", pages="1--3", year=1974, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc618.txt", key="RFC 618", abstract={Distribution of NCP and IMP message types by actual measurement.}, doi="10.17487/RFC0618", } @misc{rfc619, author="W. Naylor and H. Opderbeck", title="{Mean round-trip times in the ARPANET}", howpublished="RFC 619", series="Internet Request for Comments", type="RFC", number="619", pages="1--14", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc619.txt", key="RFC 619", abstract={Actual measurements of round-trip times.}, doi="10.17487/RFC0619", } @misc{rfc620, author="B. Ferguson", title="{Request for monitor host table updates}", howpublished="RFC 620", series="Internet Request for Comments", type="RFC", number="620", pages="1--1", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc620.txt", key="RFC 620", abstract={In conjunction with moving NIC users to OFFICE-1; see also RFCs 621 and 609.}, keywords="tenex", doi="10.17487/RFC0620", } @misc{rfc621, author="M.D. Kudlick", title="{NIC user directories at SRI ARC}", howpublished="RFC 621", series="Internet Request for Comments", type="RFC", number="621", pages="1--1", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc621.txt", key="RFC 621", abstract={See also RFCs 620 and 609.}, doi="10.17487/RFC0621", } @misc{rfc622, author="A.M. McKenzie", title="{Scheduling IMP/TIP down time}", howpublished="RFC 622", series="Internet Request for Comments", type="RFC", number="622", pages="1--3", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc622.txt", key="RFC 622", abstract={Modification of previous policy.}, doi="10.17487/RFC0622", } @misc{rfc623, author="M. Krilanovich", title="{Comments on on-line host name service}", howpublished="RFC 623", series="Internet Request for Comments", type="RFC", number="623", pages="1--2", year=1974, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc623.txt", key="RFC 623", abstract={See also RFCs 627, 625, 608 and 606.}, doi="10.17487/RFC0623", } @misc{rfc624, author="M. Krilanovich and G. Gregg and W. Hathaway and J.E. White", title="{Comments on the File Transfer Protocol}", howpublished="RFC 624", series="Internet Request for Comments", type="RFC", number="624", pages="1--3", year=1974, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc624.txt", key="RFC 624", abstract={Design changes and slight modifications. Replaces RFC 607; see also RFCs 614, 542 and 640.}, keywords="ftp, telnet", doi="10.17487/RFC0624", } @misc{rfc625, author="M.D. Kudlick and E.J. Feinler", title="{On-line hostnames service}", howpublished="RFC 625", series="Internet Request for Comments", type="RFC", number="625", pages="1--1", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc625.txt", key="RFC 625", abstract={See also RFCs 606, 608, 623 and 627.}, doi="10.17487/RFC0625", } @misc{rfc626, author="L. Kleinrock and H. Opderbeck", title="{On a possible lockup condition in IMP subnet due to message sequencing}", howpublished="RFC 626", series="Internet Request for Comments", type="RFC", number="626", pages="1--5", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc626.txt", key="RFC 626", doi="10.17487/RFC0626", } @misc{rfc627, author="M.D. Kudlick and E.J. Feinler", title="{ASCII text file of hostnames}", howpublished="RFC 627", series="Internet Request for Comments", type="RFC", number="627", pages="1--1", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc627.txt", key="RFC 627", abstract={See also RFCs 606, 608, 623 and 625.}, doi="10.17487/RFC0627", } @misc{rfc628, author="M.L. Keeney", title="{Status of RFC numbers and a note on pre-assigned journal numbers}", howpublished="RFC 628", series="Internet Request for Comments", type="RFC", number="628", pages="1--1", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc628.txt", key="RFC 628", doi="10.17487/RFC0628", } @misc{rfc629, author="J.B. North", title="{Scenario for using the Network Journal}", howpublished="RFC 629", series="Internet Request for Comments", type="RFC", number="629", pages="1--3", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc629.txt", key="RFC 629", doi="10.17487/RFC0629", } @misc{rfc630, author="J. Sussman", title="{FTP error code usage for more reliable mail service}", howpublished="RFC 630", series="Internet Request for Comments", type="RFC", number="630", pages="1--3", year=1974, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc630.txt", key="RFC 630", abstract={Describes FTP reply-code usage in TENEX mail processing.}, doi="10.17487/RFC0630", } @misc{rfc631, author="A. Danthine", title="{International meeting on minicomputers and data communication: Call for papers}", howpublished="RFC 631", series="Internet Request for Comments", type="RFC", number="631", pages="1--2", year=1974, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc631.txt", key="RFC 631", doi="10.17487/RFC0631", } @misc{rfc632, author="H. Opderbeck", title="{Throughput degradations for single packet messages}", howpublished="RFC 632", series="Internet Request for Comments", type="RFC", number="632", pages="1--6", year=1974, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc632.txt", key="RFC 632", doi="10.17487/RFC0632", } @misc{rfc633, author="A.M. McKenzie", title="{IMP/TIP preventive maintenance schedule}", howpublished="RFC 633", series="Internet Request for Comments", type="RFC", number="633", pages="1--4", year=1974, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 638", url="https://www.rfc-editor.org/rfc/rfc633.txt", key="RFC 633", abstract={An old version; see RFC 638.}, doi="10.17487/RFC0633", } @misc{rfc634, author="A.M. McKenzie", title="{Change in network address for Haskins Lab}", howpublished="RFC 634", series="Internet Request for Comments", type="RFC", number="634", pages="1--1", year=1974, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc634.txt", key="RFC 634", doi="10.17487/RFC0634", } @misc{rfc635, author="V. Cerf", title="{Assessment of ARPANET protocols}", howpublished="RFC 635", series="Internet Request for Comments", type="RFC", number="635", pages="1--1", year=1974, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc635.txt", key="RFC 635", abstract={Theoretical and practical motivation for redesign. Multipacket messages; host retransmission; duplicate detection; sequencing; acknowledgement.}, doi="10.17487/RFC0635", } @misc{rfc636, author="J.D. Burchfiel and B. Cosell and R.S. Tomlinson and D.C. Walden", title="{TIP/Tenex reliability improvements}", howpublished="RFC 636", series="Internet Request for Comments", type="RFC", number="636", pages="1--8", year=1974, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc636.txt", key="RFC 636", abstract={Obtaining/maintaining connections; recovery from lost connections; connection-state changes.}, doi="10.17487/RFC0636", } @misc{rfc637, author="A.M. McKenzie", title="{Change of network address for SU-DSL}", howpublished="RFC 637", series="Internet Request for Comments", type="RFC", number="637", pages="1--1", year=1974, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc637.txt", key="RFC 637", doi="10.17487/RFC0637", } @misc{rfc638, author="A.M. McKenzie", title="{IMP/TIP preventive maintenance schedule}", howpublished="RFC 638", series="Internet Request for Comments", type="RFC", number="638", pages="1--4", year=1974, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc638.txt", key="RFC 638", abstract={Corrects RFC 633.}, doi="10.17487/RFC0638", } @misc{rfc640, author="J. Postel", title="{Revised FTP reply codes}", howpublished="RFC 640", series="Internet Request for Comments", type="RFC", number="640", pages="1--17", year=1974, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc640.txt", key="RFC 640", abstract={Updates RFC 542.}, doi="10.17487/RFC0640", } @misc{rfc642, author="J.D. Burchfiel", title="{Ready line philosophy and implementation}", howpublished="RFC 642", series="Internet Request for Comments", type="RFC", number="642", pages="1--4", year=1974, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc642.txt", key="RFC 642", doi="10.17487/RFC0642", } @misc{rfc643, author="E. Mader", title="{Network Debugging Protocol}", howpublished="RFC 643", series="Internet Request for Comments", type="RFC", number="643", pages="1--7", year=1974, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc643.txt", key="RFC 643", abstract={To be used in an implementation of a PDP-11 network bootstrap device and a cross-network debugger.}, doi="10.17487/RFC0643", } @misc{rfc644, author="R. Thomas", title="{On the problem of signature authentication for network mail}", howpublished="RFC 644", series="Internet Request for Comments", type="RFC", number="644", pages="1--3", year=1974, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc644.txt", key="RFC 644", doi="10.17487/RFC0644", } @misc{rfc645, author="D. Crocker", title="{Network Standard Data Specification syntax}", howpublished="RFC 645", series="Internet Request for Comments", type="RFC", number="645", pages="1--9", year=1974, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc645.txt", key="RFC 645", abstract={Providing a mechanism for specifying all attributes of a collection of bits; see also RFC 615.}, doi="10.17487/RFC0645", } @misc{rfc647, author="M.A. Padlipsky", title="{Proposed protocol for connecting host computers to ARPA-like networks via front end processors}", howpublished="RFC 647", series="Internet Request for Comments", type="RFC", number="647", pages="1--20", year=1974, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc647.txt", key="RFC 647", abstract={Approaches to Front-End protocol processing using available hardware and software.}, doi="10.17487/RFC0647", } @misc{rfc651, author="D. Crocker", title="{Revised Telnet status option}", howpublished="RFC 651", series="Internet Request for Comments", type="RFC", number="651", pages="1--2", year=1974, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 859", url="https://www.rfc-editor.org/rfc/rfc651.txt", key="RFC 651", doi="10.17487/RFC0651", } @misc{rfc652, author="D. Crocker", title="{Telnet output carriage-return disposition option}", howpublished="RFC 652 (Historic)", series="Internet Request for Comments", type="RFC", number="652", pages="1--4", year=1974, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc652.txt", key="RFC 652", keywords="TOPT-OCRD", doi="10.17487/RFC0652", } @misc{rfc653, author="D. Crocker", title="{Telnet output horizontal tabstops option}", howpublished="RFC 653 (Historic)", series="Internet Request for Comments", type="RFC", number="653", pages="1--1", year=1974, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc653.txt", key="RFC 653", keywords="TOPT-OHT", doi="10.17487/RFC0653", } @misc{rfc654, author="D. Crocker", title="{Telnet output horizontal tab disposition option}", howpublished="RFC 654 (Historic)", series="Internet Request for Comments", type="RFC", number="654", pages="1--1", year=1974, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc654.txt", key="RFC 654", keywords="TOPT-OHTD", doi="10.17487/RFC0654", } @misc{rfc655, author="D. Crocker", title="{Telnet output formfeed disposition option}", howpublished="RFC 655 (Historic)", series="Internet Request for Comments", type="RFC", number="655", pages="1--1", year=1974, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc655.txt", key="RFC 655", keywords="TOPT-OFD", doi="10.17487/RFC0655", } @misc{rfc656, author="D. Crocker", title="{Telnet output vertical tabstops option}", howpublished="RFC 656 (Historic)", series="Internet Request for Comments", type="RFC", number="656", pages="1--1", year=1974, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc656.txt", key="RFC 656", keywords="TOPT-OVT", doi="10.17487/RFC0656", } @misc{rfc657, author="D. Crocker", title="{Telnet output vertical tab disposition option}", howpublished="RFC 657 (Historic)", series="Internet Request for Comments", type="RFC", number="657", pages="1--1", year=1974, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc657.txt", key="RFC 657", keywords="TOPT-OVTD", doi="10.17487/RFC0657", } @misc{rfc658, author="D. Crocker", title="{Telnet output linefeed disposition}", howpublished="RFC 658 (Historic)", series="Internet Request for Comments", type="RFC", number="658", pages="1--2", year=1974, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc658.txt", key="RFC 658", keywords="TOPT-OLD", doi="10.17487/RFC0658", } @misc{rfc659, author="J. Postel", title="{Announcing additional Telnet options}", howpublished="RFC 659", series="Internet Request for Comments", type="RFC", number="659", pages="1--1", year=1974, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc659.txt", key="RFC 659", abstract={Options defined in RFCs 651-658.}, doi="10.17487/RFC0659", } @misc{rfc660, author="D.C. Walden", title="{Some changes to the IMP and the IMP/Host interface}", howpublished="RFC 660", series="Internet Request for Comments", type="RFC", number="660", pages="1--1", year=1974, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc660.txt", key="RFC 660", abstract={Decoupling of message number sequences of hosts; host-host access control; message number window; messages outside normal mechanism; see also BBN 1822.}, doi="10.17487/RFC0660", } @misc{rfc661, author="J. Postel", title="{Protocol information}", howpublished="RFC 661", series="Internet Request for Comments", type="RFC", number="661", pages="1--21", year=1974, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 694", url="https://www.rfc-editor.org/rfc/rfc661.txt", key="RFC 661", abstract={An old version; see RFC 694.}, doi="10.17487/RFC0661", } @misc{rfc662, author="R. Kanodia", title="{Performance improvement in ARPANET file transfers from Multics}", howpublished="RFC 662", series="Internet Request for Comments", type="RFC", number="662", pages="1--2", year=1974, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc662.txt", key="RFC 662", abstract={Experimenting with host output buffers to improve throughput.}, doi="10.17487/RFC0662", } @misc{rfc663, author="R. Kanodia", title="{Lost message detection and recovery protocol}", howpublished="RFC 663", series="Internet Request for Comments", type="RFC", number="663", pages="1--22", year=1974, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc663.txt", key="RFC 663", abstract={Proposed extension of host-host protocol; see also RFCs 534, 516, 512, 492 and 467.}, keywords="ARPANET, Host", doi="10.17487/RFC0663", } @misc{rfc666, author="M.A. Padlipsky", title="{Specification of the Unified User-Level Protocol}", howpublished="RFC 666", series="Internet Request for Comments", type="RFC", number="666", pages="1--19", year=1974, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc666.txt", key="RFC 666", abstract={Discusses and proposes a common command language.}, doi="10.17487/RFC0666", } @misc{rfc667, author="S.G. Chipman", title="{Host Ports}", howpublished="RFC 667", series="Internet Request for Comments", type="RFC", number="667", pages="1--2", year=1974, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc667.txt", key="RFC 667", abstract={Approved scheme to connect host ports to the network.}, doi="10.17487/RFC0667", } @misc{rfc669, author="D.W. Dodds", title="{November, 1974, survey of New-Protocol Telnet servers}", howpublished="RFC 669", series="Internet Request for Comments", type="RFC", number="669", pages="1--3", year=1974, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 679", url="https://www.rfc-editor.org/rfc/rfc669.txt", key="RFC 669", abstract={An earlier poll of Telnet server implementation status. Updates RFC 702; see also RFCs 703 and 679.}, doi="10.17487/RFC0669", } @misc{rfc671, author="R. Schantz", title="{Note on Reconnection Protocol}", howpublished="RFC 671", series="Internet Request for Comments", type="RFC", number="671", pages="1--9", year=1974, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc671.txt", key="RFC 671", abstract={Experience with implementation in RSEXEC context.}, doi="10.17487/RFC0671", } @misc{rfc672, author="R. Schantz", title="{Multi-site data collection facility}", howpublished="RFC 672", series="Internet Request for Comments", type="RFC", number="672", pages="1--9", year=1974, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc672.txt", key="RFC 672", abstract={Applicability of TIP/TENEX protocols beyond TIP accounting.}, doi="10.17487/RFC0672", } @misc{rfc674, author="J. Postel and J.E. White", title="{Procedure call documents: Version 2}", howpublished="RFC 674", series="Internet Request for Comments", type="RFC", number="674", pages="1--6", year=1974, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc674.txt", key="RFC 674", abstract={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.}, doi="10.17487/RFC0674", } @misc{rfc675, author="V. Cerf and Y. Dalal and C. Sunshine", title="{Specification of Internet Transmission Control Program}", howpublished="RFC 675 (Historic)", series="Internet Request for Comments", type="RFC", number="675", pages="1--70", year=1974, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 7805", url="https://www.rfc-editor.org/rfc/rfc675.txt", key="RFC 675", abstract={The first detailed specification of TCP; see RFC 793.}, doi="10.17487/RFC0675", } @misc{rfc677, author="P.R. Johnson and R. Thomas", title="{Maintenance of duplicate databases}", howpublished="RFC 677", series="Internet Request for Comments", type="RFC", number="677", pages="1--10", year=1975, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc677.txt", key="RFC 677", doi="10.17487/RFC0677", } @misc{rfc678, author="J. Postel", title="{Standard file formats}", howpublished="RFC 678", series="Internet Request for Comments", type="RFC", number="678", pages="1--9", year=1974, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc678.txt", key="RFC 678", abstract={For transmission of documents across different environments.}, doi="10.17487/RFC0678", } @misc{rfc679, author="D.W. Dodds", title="{February, 1975, survey of New-Protocol Telnet servers}", howpublished="RFC 679", series="Internet Request for Comments", type="RFC", number="679", pages="1--3", year=1975, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 703", url="https://www.rfc-editor.org/rfc/rfc679.txt", key="RFC 679", abstract={An earlier poll of Telnet server implementation status. Updates RFCs 701, 702 and 669; see also RFC 703.}, doi="10.17487/RFC0679", } @misc{rfc680, author="T.H. Myer and D.A. Henderson", title="{Message Transmission Protocol}", howpublished="RFC 680", series="Internet Request for Comments", type="RFC", number="680", pages="1--6", year=1975, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc680.txt", key="RFC 680", abstract={Extends message field definition beyond RFC 561 attempts to establish syntactic and semantic standards for ARPANET; see also RFCs 733 and 822.}, doi="10.17487/RFC0680", } @misc{rfc681, author="S. Holmgren", title="{Network UNIX}", howpublished="RFC 681", series="Internet Request for Comments", type="RFC", number="681", pages="1--8", year=1975, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc681.txt", key="RFC 681", abstract={Capabilities as an ARPANET Mini-Host: standard I/O, Telnet, NCP, Hardware/Software requirements, reliability, availability.}, doi="10.17487/RFC0681", } @misc{rfc683, author="R. Clements", title="{FTPSRV - Tenex extension for paged files}", howpublished="RFC 683", series="Internet Request for Comments", type="RFC", number="683", pages="1--3", year=1975, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc683.txt", key="RFC 683", abstract={Defines an extension to FTP for page-mode transfers between TENEX systems; also discusses file transfer reliability.}, keywords="FTP, paged, file, transfer, Tenex", doi="10.17487/RFC0683", } @misc{rfc684, author="R. Schantz", title="{Commentary on procedure calling as a network protocol}", howpublished="RFC 684", series="Internet Request for Comments", type="RFC", number="684", pages="1--9", year=1975, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc684.txt", key="RFC 684", abstract={Issues in designing distributed computing systems. Shortcomings of RFC 674; see also RFCs 542 and 354.}, doi="10.17487/RFC0684", } @misc{rfc685, author="M. Beeler", title="{Response time in cross network debugging}", howpublished="RFC 685", series="Internet Request for Comments", type="RFC", number="685", pages="1--3", year=1975, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc685.txt", key="RFC 685", abstract={The contribution of ARPANET communication to response time.}, doi="10.17487/RFC0685", } @misc{rfc686, author="B. Harvey", title="{Leaving well enough alone}", howpublished="RFC 686", series="Internet Request for Comments", type="RFC", number="686", pages="1--9", year=1975, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc686.txt", key="RFC 686", abstract={Discusses difference between early and later versions of FTP; see also RFCs 691, 640, 630, 542, 454, 448, 414, 385 and 354.}, doi="10.17487/RFC0686", } @misc{rfc687, author="D.C. Walden", title="{IMP/Host and Host/IMP Protocol changes}", howpublished="RFC 687", series="Internet Request for Comments", type="RFC", number="687", pages="1--2", year=1975, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 704, updated by RFC 690", url="https://www.rfc-editor.org/rfc/rfc687.txt", key="RFC 687", abstract={Addressing hosts on more than 63 IMPs, and other backwards compatible expansions; see also RFCs 690 and 692.}, doi="10.17487/RFC0687", } @misc{rfc688, author="D.C. Walden", title="{Tentative schedule for the new Telnet implementation for the TIP}", howpublished="RFC 688", series="Internet Request for Comments", type="RFC", number="688", pages="1--1", year=1975, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc688.txt", key="RFC 688", doi="10.17487/RFC0688", } @misc{rfc689, author="R. Clements", title="{Tenex NCP finite state machine for connections}", howpublished="RFC 689", series="Internet Request for Comments", type="RFC", number="689", pages="1--5", year=1975, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc689.txt", key="RFC 689", abstract={Describes the internal states of an NCP connection in the TENEX implementation.}, doi="10.17487/RFC0689", } @misc{rfc690, author="J. Postel", title="{Comments on the proposed Host/IMP Protocol changes}", howpublished="RFC 690", series="Internet Request for Comments", type="RFC", number="690", pages="1--3", year=1975, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 692", url="https://www.rfc-editor.org/rfc/rfc690.txt", key="RFC 690", abstract={Comments on suggestions in RFC 687; see also RFCs 692 and 696.}, doi="10.17487/RFC0690", } @misc{rfc691, author="B. Harvey", title="{One more try on the FTP}", howpublished="RFC 691", series="Internet Request for Comments", type="RFC", number="691", pages="1--14", year=1975, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc691.txt", key="RFC 691", abstract={Slight revision of RFC 686, on the subject of print files; see also RFCs 640, 630, 542, 454, 448, 414, 385 and 354.}, doi="10.17487/RFC0691", } @misc{rfc692, author="S.M. Wolfe", title="{Comments on IMP/Host Protocol changes (RFCs 687 and 690)}", howpublished="RFC 692", series="Internet Request for Comments", type="RFC", number="692", pages="1--2", year=1975, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc692.txt", key="RFC 692", abstract={A proposed solution to the problem of combined length of IMP and Host leaders; see also RFCs 696, 690 and 687.}, doi="10.17487/RFC0692", } @misc{rfc694, author="J. Postel", title="{Protocol information}", howpublished="RFC 694", series="Internet Request for Comments", type="RFC", number="694", pages="1--36", year=1975, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc694.txt", key="RFC 694", abstract={References to documents and contacts concerning the various protocols used in the ARPANET, as well as recent developments; updates RFC 661.}, doi="10.17487/RFC0694", } @misc{rfc695, author="M. Krilanovich", title="{Official change in Host-Host Protocol}", howpublished="RFC 695", series="Internet Request for Comments", type="RFC", number="695", pages="1--3", year=1975, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc695.txt", key="RFC 695", abstract={Corrects ambiguity concerning the ERR command; changes NIC 8246 and NIC 7104.}, doi="10.17487/RFC0695", } @misc{rfc696, author="V.G. Cerf", title="{Comments on the IMP/Host and Host/IMP Protocol changes}", howpublished="RFC 696", series="Internet Request for Comments", type="RFC", number="696", pages="1--2", year=1975, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc696.txt", key="RFC 696", abstract={Observations on current international standards recommendations from IFIP working group 6.1; see also RFCs 692, 690, 687.}, doi="10.17487/RFC0696", } @misc{rfc697, author="J. Lieb", title="{CWD command of FTP}", howpublished="RFC 697", series="Internet Request for Comments", type="RFC", number="697", pages="1--2", year=1975, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc697.txt", key="RFC 697", abstract={Discusses FTP login access to ``files only'' directories.}, doi="10.17487/RFC0697", } @misc{rfc698, author="T. Mock", title="{Telnet extended ASCII option}", howpublished="RFC 698 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="698", pages="1--3", year=1975, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 5198", url="https://www.rfc-editor.org/rfc/rfc698.txt", key="RFC 698", abstract={Describes an option to allow transmission of a special kind of extended ASCII used at the Stanford AI and MIT AI Labs.}, keywords="TOPT-EXT", doi="10.17487/RFC0698", } @misc{rfc699, author="J. Postel and J. Vernon", title="{Request For Comments summary notes: 600-699}", howpublished="RFC 699 (Informational)", series="Internet Request for Comments", type="RFC", number="699", pages="1--9", year=1982, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc699.txt", key="RFC 699", doi="10.17487/RFC0699", } @misc{rfc700, author="E. Mader and W.W. Plummer and R.S. Tomlinson", title="{Protocol experiment}", howpublished="RFC 700 (Informational)", series="Internet Request for Comments", type="RFC", number="700", pages="1--7", year=1974, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc700.txt", key="RFC 700", doi="10.17487/RFC0700", } @misc{rfc701, author="D.W. Dodds", title="{August, 1974, survey of New-Protocol Telnet servers}", howpublished="RFC 701", series="Internet Request for Comments", type="RFC", number="701", pages="1--1", year=1974, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 702", url="https://www.rfc-editor.org/rfc/rfc701.txt", key="RFC 701", doi="10.17487/RFC0701", } @misc{rfc702, author="D.W. Dodds", title="{September, 1974, survey of New-Protocol Telnet servers}", howpublished="RFC 702", series="Internet Request for Comments", type="RFC", number="702", pages="1--3", year=1974, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 669", url="https://www.rfc-editor.org/rfc/rfc702.txt", key="RFC 702", doi="10.17487/RFC0702", } @misc{rfc703, author="D.W. Dodds", title="{July, 1975, survey of New-Protocol Telnet Servers}", howpublished="RFC 703", series="Internet Request for Comments", type="RFC", number="703", pages="1--3", year=1975, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc703.txt", key="RFC 703", doi="10.17487/RFC0703", } @misc{rfc704, author="P.J. Santos", title="{IMP/Host and Host/IMP Protocol change}", howpublished="RFC 704", series="Internet Request for Comments", type="RFC", number="704", pages="1--2", year=1975, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc704.txt", key="RFC 704", doi="10.17487/RFC0704", } @misc{rfc705, author="R.F. Bryan", title="{Front-end Protocol B6700 version}", howpublished="RFC 705", series="Internet Request for Comments", type="RFC", number="705", pages="1--39", year=1975, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc705.txt", key="RFC 705", doi="10.17487/RFC0705", } @misc{rfc706, author="J. Postel", title="{On the junk mail problem}", howpublished="RFC 706", series="Internet Request for Comments", type="RFC", number="706", pages="1--1", year=1975, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc706.txt", key="RFC 706", doi="10.17487/RFC0706", } @misc{rfc707, author="J.E. White", title="{High-level framework for network-based resource sharing}", howpublished="RFC 707", series="Internet Request for Comments", type="RFC", number="707", pages="1--29", year=1975, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc707.txt", key="RFC 707", doi="10.17487/RFC0707", } @misc{rfc708, author="J.E. White", title="{Elements of a Distributed Programming System}", howpublished="RFC 708", series="Internet Request for Comments", type="RFC", number="708", pages="1--30", year=1976, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc708.txt", key="RFC 708", doi="10.17487/RFC0708", } @misc{rfc712, author="J.E. Donnelley", title="{Distributed Capability Computing System (DCCS)}", howpublished="RFC 712", series="Internet Request for Comments", type="RFC", number="712", pages="1--17", year=1976, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc712.txt", key="RFC 712", doi="10.17487/RFC0712", } @misc{rfc713, author="J. Haverty", title="{MSDTP-Message Services Data Transmission Protocol}", howpublished="RFC 713", series="Internet Request for Comments", type="RFC", number="713", pages="1--21", year=1976, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc713.txt", key="RFC 713", doi="10.17487/RFC0713", } @misc{rfc714, author="A.M. McKenzie", title="{Host-Host Protocol for an ARPANET-Type Network}", howpublished="RFC 714", series="Internet Request for Comments", type="RFC", number="714", pages="1--22", year=1976, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc714.txt", key="RFC 714", doi="10.17487/RFC0714", } @misc{rfc716, author="D.C. Walden and J. Levin", title="{Interim Revision to Appendix F of BBN 1822}", howpublished="RFC 716", series="Internet Request for Comments", type="RFC", number="716", pages="1--1", year=1976, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc716.txt", key="RFC 716", doi="10.17487/RFC0716", } @misc{rfc717, author="J. Postel", title="{Assigned Network Numbers}", howpublished="RFC 717 (Historic)", series="Internet Request for Comments", type="RFC", number="717", pages="1--1", year=1976, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc717.txt", key="RFC 717", doi="10.17487/RFC0717", } @misc{rfc718, author="J. Postel", title="{Comments on RCTE from the Tenex Implementation Experience}", howpublished="RFC 718", series="Internet Request for Comments", type="RFC", number="718", pages="1--1", year=1976, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc718.txt", key="RFC 718", doi="10.17487/RFC0718", } @misc{rfc719, author="J. Postel", title="{Discussion on RCTE}", howpublished="RFC 719", series="Internet Request for Comments", type="RFC", number="719", pages="1--1", year=1976, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc719.txt", key="RFC 719", doi="10.17487/RFC0719", } @misc{rfc720, author="D. Crocker", title="{Address Specification Syntax for Network Mail}", howpublished="RFC 720", series="Internet Request for Comments", type="RFC", number="720", pages="1--3", year=1976, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc720.txt", key="RFC 720", doi="10.17487/RFC0720", } @misc{rfc721, author="L.L. Garlick", title="{Out-of-Band Control Signals in a Host-to-Host Protocol}", howpublished="RFC 721 (Historic)", series="Internet Request for Comments", type="RFC", number="721", pages="1--7", year=1976, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 7805", url="https://www.rfc-editor.org/rfc/rfc721.txt", key="RFC 721", doi="10.17487/RFC0721", } @misc{rfc722, author="J. Haverty", title="{Thoughts on Interactions in Distributed Services}", howpublished="RFC 722", series="Internet Request for Comments", type="RFC", number="722", pages="1--13", year=1976, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc722.txt", key="RFC 722", doi="10.17487/RFC0722", } @misc{rfc724, author="D. Crocker and K.T. Pogran and J. Vittal and D.A. Henderson", title="{Proposed official standard for the format of ARPA Network messages}", howpublished="RFC 724", series="Internet Request for Comments", type="RFC", number="724", pages="1--36", year=1977, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 733", url="https://www.rfc-editor.org/rfc/rfc724.txt", key="RFC 724", doi="10.17487/RFC0724", } @misc{rfc725, author="J.D. Day and G.R. Grossman", title="{RJE protocol for a resource sharing network}", howpublished="RFC 725", series="Internet Request for Comments", type="RFC", number="725", pages="1--27", year=1977, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc725.txt", key="RFC 725", doi="10.17487/RFC0725", } @misc{rfc726, author="J. Postel and D. Crocker", title="{Remote Controlled Transmission and Echoing Telnet option}", howpublished="RFC 726 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="726", pages="1--16", year=1977, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc726.txt", key="RFC 726", keywords="TOPT-REM", doi="10.17487/RFC0726", } @misc{rfc727, author="M.R. Crispin", title="{Telnet logout option}", howpublished="RFC 727 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="727", pages="1--3", year=1977, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc727.txt", key="RFC 727", keywords="TOPT-LOGO", doi="10.17487/RFC0727", } @misc{rfc728, author="J.D. Day", title="{Minor pitfall in the Telnet Protocol}", howpublished="RFC 728", series="Internet Request for Comments", type="RFC", number="728", pages="1--1", year=1977, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc728.txt", key="RFC 728", doi="10.17487/RFC0728", } @misc{rfc729, author="D. Crocker", title="{Telnet byte macro option}", howpublished="RFC 729", series="Internet Request for Comments", type="RFC", number="729", pages="1--3", year=1977, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 735", url="https://www.rfc-editor.org/rfc/rfc729.txt", key="RFC 729", doi="10.17487/RFC0729", } @misc{rfc730, author="J. Postel", title="{Extensible field addressing}", howpublished="RFC 730", series="Internet Request for Comments", type="RFC", number="730", pages="1--5", year=1977, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc730.txt", key="RFC 730", doi="10.17487/RFC0730", } @misc{rfc731, author="J.D. Day", title="{Telnet Data Entry Terminal option}", howpublished="RFC 731", series="Internet Request for Comments", type="RFC", number="731", pages="1--28", year=1977, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 732", url="https://www.rfc-editor.org/rfc/rfc731.txt", key="RFC 731", doi="10.17487/RFC0731", } @misc{rfc732, author="J.D. Day", title="{Telnet Data Entry Terminal option}", howpublished="RFC 732", series="Internet Request for Comments", type="RFC", number="732", pages="1--30", year=1977, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 1043", url="https://www.rfc-editor.org/rfc/rfc732.txt", key="RFC 732", doi="10.17487/RFC0732", } @misc{rfc733, author="D. Crocker and J. Vittal and K.T. Pogran and D.A. Henderson", title="{Standard for the format of ARPA network text messages}", howpublished="RFC 733", series="Internet Request for Comments", type="RFC", number="733", pages="1--38", year=1977, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 822", url="https://www.rfc-editor.org/rfc/rfc733.txt", key="RFC 733", doi="10.17487/RFC0733", } @misc{rfc734, author="M.R. Crispin", title="{SUPDUP Protocol}", howpublished="RFC 734 (Historic)", series="Internet Request for Comments", type="RFC", number="734", pages="1--13", year=1977, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc734.txt", key="RFC 734", keywords="SUPDUP", doi="10.17487/RFC0734", } @misc{rfc735, author="D. Crocker and R.H. Gumpertz", title="{Revised Telnet byte macro option}", howpublished="RFC 735 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="735", pages="1--5", year=1977, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc735.txt", key="RFC 735", keywords="TOPT-BYTE", doi="10.17487/RFC0735", } @misc{rfc736, author="M.R. Crispin", title="{Telnet SUPDUP option}", howpublished="RFC 736 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="736", pages="1--1", year=1977, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc736.txt", key="RFC 736", keywords="TOPT-SUP", doi="10.17487/RFC0736", } @misc{rfc737, author="K. Harrenstien", title="{FTP extension: XSEN}", howpublished="RFC 737", series="Internet Request for Comments", type="RFC", number="737", pages="1--1", year=1977, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc737.txt", key="RFC 737", doi="10.17487/RFC0737", } @misc{rfc738, author="K. Harrenstien", title="{Time server}", howpublished="RFC 738", series="Internet Request for Comments", type="RFC", number="738", pages="1--1", year=1977, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc738.txt", key="RFC 738", doi="10.17487/RFC0738", } @misc{rfc739, author="J. Postel", title="{Assigned numbers}", howpublished="RFC 739 (Historic)", series="Internet Request for Comments", type="RFC", number="739", pages="1--11", year=1977, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 750", url="https://www.rfc-editor.org/rfc/rfc739.txt", key="RFC 739", doi="10.17487/RFC0739", } @misc{rfc740, author="R.T. Braden", title="{NETRJS Protocol}", howpublished="RFC 740 (Historic)", series="Internet Request for Comments", type="RFC", number="740", pages="1--19", year=1977, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc740.txt", key="RFC 740", keywords="NETRJS", doi="10.17487/RFC0740", } @misc{rfc741, author="D. Cohen", title="{Specifications for the Network Voice Protocol (NVP)}", howpublished="RFC 741", series="Internet Request for Comments", type="RFC", number="741", pages="1--34", year=1977, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc741.txt", key="RFC 741", doi="10.17487/RFC0741", } @misc{rfc742, author="K. Harrenstien", title="{NAME/FINGER Protocol}", howpublished="RFC 742", series="Internet Request for Comments", type="RFC", number="742", pages="1--7", year=1977, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1288, 1196, 1194", url="https://www.rfc-editor.org/rfc/rfc742.txt", key="RFC 742", doi="10.17487/RFC0742", } @misc{rfc743, author="K. Harrenstien", title="{FTP extension: XRSQ/XRCP}", howpublished="RFC 743", series="Internet Request for Comments", type="RFC", number="743", pages="1--8", year=1977, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc743.txt", key="RFC 743", doi="10.17487/RFC0743", } @misc{rfc744, author="J. Sattley", title="{MARS - a Message Archiving and Retrieval Service}", howpublished="RFC 744", series="Internet Request for Comments", type="RFC", number="744", pages="1--6", year=1978, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc744.txt", key="RFC 744", doi="10.17487/RFC0744", } @misc{rfc745, author="M. Beeler", title="{JANUS interface specifications}", howpublished="RFC 745", series="Internet Request for Comments", type="RFC", number="745", pages="1--10", year=1978, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc745.txt", key="RFC 745", keywords="JANUS, interface, specifications", doi="10.17487/RFC0745", } @misc{rfc746, author="R. Stallman", title="{SUPDUP graphics extension}", howpublished="RFC 746", series="Internet Request for Comments", type="RFC", number="746", pages="1--15", year=1978, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc746.txt", key="RFC 746", doi="10.17487/RFC0746", } @misc{rfc747, author="M.R. Crispin", title="{Recent extensions to the SUPDUP Protocol}", howpublished="RFC 747", series="Internet Request for Comments", type="RFC", number="747", pages="1--1", year=1978, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc747.txt", key="RFC 747", doi="10.17487/RFC0747", } @misc{rfc748, author="M.R. Crispin", title="{Telnet randomly-lose option}", howpublished="RFC 748", series="Internet Request for Comments", type="RFC", number="748", pages="1--2", year=1978, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc748.txt", key="RFC 748", doi="10.17487/RFC0748", } @misc{rfc749, author="B. Greenberg", title="{Telnet SUPDUP-Output option}", howpublished="RFC 749 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="749", pages="1--4", year=1978, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc749.txt", key="RFC 749", keywords="TOPT-SUPO", doi="10.17487/RFC0749", } @misc{rfc750, author="J. Postel", title="{Assigned numbers}", howpublished="RFC 750 (Historic)", series="Internet Request for Comments", type="RFC", number="750", pages="1--12", year=1978, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 755", url="https://www.rfc-editor.org/rfc/rfc750.txt", key="RFC 750", doi="10.17487/RFC0750", } @misc{rfc751, author="P.D. Lebling", title="{Survey of FTP mail and MLFL}", howpublished="RFC 751", series="Internet Request for Comments", type="RFC", number="751", pages="1--5", year=1978, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc751.txt", key="RFC 751", doi="10.17487/RFC0751", } @misc{rfc752, author="M.R. Crispin", title="{Universal host table}", howpublished="RFC 752", series="Internet Request for Comments", type="RFC", number="752", pages="1--12", year=1979, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc752.txt", key="RFC 752", doi="10.17487/RFC0752", } @misc{rfc753, author="J. Postel", title="{Internet Message Protocol}", howpublished="RFC 753", series="Internet Request for Comments", type="RFC", number="753", pages="1--62", year=1979, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc753.txt", key="RFC 753", doi="10.17487/RFC0753", } @misc{rfc754, author="J. Postel", title="{Out-of-net host addresses for mail}", howpublished="RFC 754", series="Internet Request for Comments", type="RFC", number="754", pages="1--10", year=1979, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc754.txt", key="RFC 754", doi="10.17487/RFC0754", } @misc{rfc755, author="J. Postel", title="{Assigned numbers}", howpublished="RFC 755 (Historic)", series="Internet Request for Comments", type="RFC", number="755", pages="1--12", year=1979, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 758", url="https://www.rfc-editor.org/rfc/rfc755.txt", key="RFC 755", doi="10.17487/RFC0755", } @misc{rfc756, author="J.R. Pickens and E.J. Feinler and J.E. Mathis", title="{NIC name server - a datagram-based information utility}", howpublished="RFC 756", series="Internet Request for Comments", type="RFC", number="756", pages="1--12", year=1979, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc756.txt", key="RFC 756", doi="10.17487/RFC0756", } @misc{rfc757, author="D.P. Deutsch", title="{Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems}", howpublished="RFC 757", series="Internet Request for Comments", type="RFC", number="757", pages="1--19", year=1979, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc757.txt", key="RFC 757", doi="10.17487/RFC0757", } @misc{rfc758, author="J. Postel", title="{Assigned numbers}", howpublished="RFC 758 (Historic)", series="Internet Request for Comments", type="RFC", number="758", pages="1--12", year=1979, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 762", url="https://www.rfc-editor.org/rfc/rfc758.txt", key="RFC 758", doi="10.17487/RFC0758", } @misc{rfc759, author="J. Postel", title="{Internet Message Protocol}", howpublished="RFC 759 (Historic)", series="Internet Request for Comments", type="RFC", number="759", pages="1--77", year=1980, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc759.txt", key="RFC 759", keywords="MPM", doi="10.17487/RFC0759", } @misc{rfc760, author="J. Postel", title="{DoD standard Internet Protocol}", howpublished="RFC 760", series="Internet Request for Comments", type="RFC", number="760", pages="1--46", year=1980, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 791, updated by RFC 777", url="https://www.rfc-editor.org/rfc/rfc760.txt", key="RFC 760", doi="10.17487/RFC0760", } @misc{rfc761, author="J. Postel", title="{DoD standard Transmission Control Protocol}", howpublished="RFC 761 (Historic)", series="Internet Request for Comments", type="RFC", number="761", pages="1--88", year=1980, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 793, 7805", url="https://www.rfc-editor.org/rfc/rfc761.txt", key="RFC 761", keywords="TCP", doi="10.17487/RFC0761", } @misc{rfc762, author="J. Postel", title="{Assigned numbers}", howpublished="RFC 762 (Historic)", series="Internet Request for Comments", type="RFC", number="762", pages="1--13", year=1980, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 770", url="https://www.rfc-editor.org/rfc/rfc762.txt", key="RFC 762", doi="10.17487/RFC0762", } @misc{rfc763, author="M.D. Abrams", title="{Role mailboxes}", howpublished="RFC 763", series="Internet Request for Comments", type="RFC", number="763", pages="1--1", year=1980, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc763.txt", key="RFC 763", doi="10.17487/RFC0763", } @misc{rfc764, author="J. Postel", title="{Telnet Protocol specification}", howpublished="RFC 764", series="Internet Request for Comments", type="RFC", number="764", pages="1--15", year=1980, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 854", url="https://www.rfc-editor.org/rfc/rfc764.txt", key="RFC 764", doi="10.17487/RFC0764", } @misc{rfc765, author="J. Postel", title="{File Transfer Protocol specification}", howpublished="RFC 765", series="Internet Request for Comments", type="RFC", number="765", pages="1--70", year=1980, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 959", url="https://www.rfc-editor.org/rfc/rfc765.txt", key="RFC 765", doi="10.17487/RFC0765", } @misc{rfc766, author="J. Postel", title="{Internet Protocol Handbook: Table of contents}", howpublished="RFC 766", series="Internet Request for Comments", type="RFC", number="766", pages="1--2", year=1980, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 774", url="https://www.rfc-editor.org/rfc/rfc766.txt", key="RFC 766", doi="10.17487/RFC0766", } @misc{rfc767, author="J. Postel", title="{Structured format for transmission of multi-media documents}", howpublished="RFC 767", series="Internet Request for Comments", type="RFC", number="767", pages="1--40", year=1980, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc767.txt", key="RFC 767", doi="10.17487/RFC0767", } @misc{rfc768, author="J. Postel", title="{User Datagram Protocol}", howpublished="RFC 768 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="768", pages="1--3", year=1980, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc768.txt", key="RFC 768", keywords="UDP, UDP", doi="10.17487/RFC0768", } @misc{rfc769, author="J. Postel", title="{Rapicom 450 facsimile file format}", howpublished="RFC 769", series="Internet Request for Comments", type="RFC", number="769", pages="1--2", year=1980, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc769.txt", key="RFC 769", doi="10.17487/RFC0769", } @misc{rfc770, author="J. Postel", title="{Assigned numbers}", howpublished="RFC 770 (Historic)", series="Internet Request for Comments", type="RFC", number="770", pages="1--15", year=1980, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 776", url="https://www.rfc-editor.org/rfc/rfc770.txt", key="RFC 770", doi="10.17487/RFC0770", } @misc{rfc771, author="V.G. Cerf and J. Postel", title="{Mail transition plan}", howpublished="RFC 771", series="Internet Request for Comments", type="RFC", number="771", pages="1--9", year=1980, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc771.txt", key="RFC 771", doi="10.17487/RFC0771", } @misc{rfc772, author="S. Sluizer and J. Postel", title="{Mail Transfer Protocol}", howpublished="RFC 772", series="Internet Request for Comments", type="RFC", number="772", pages="1--31", year=1980, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 780", url="https://www.rfc-editor.org/rfc/rfc772.txt", key="RFC 772", keywords="MTP, email", doi="10.17487/RFC0772", } @misc{rfc773, author="V.G. Cerf", title="{Comments on NCP/TCP mail service transition strategy}", howpublished="RFC 773", series="Internet Request for Comments", type="RFC", number="773", pages="1--11", year=1980, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc773.txt", key="RFC 773", doi="10.17487/RFC0773", } @misc{rfc774, author="J. Postel", title="{Internet Protocol Handbook: Table of contents}", howpublished="RFC 774", series="Internet Request for Comments", type="RFC", number="774", pages="1--3", year=1980, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc774.txt", key="RFC 774", doi="10.17487/RFC0774", } @misc{rfc775, author="D. Mankins and D. Franklin and A.D. Owen", title="{Directory oriented FTP commands}", howpublished="RFC 775", series="Internet Request for Comments", type="RFC", number="775", pages="1--6", year=1980, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc775.txt", key="RFC 775", doi="10.17487/RFC0775", } @misc{rfc776, author="J. Postel", title="{Assigned numbers}", howpublished="RFC 776 (Historic)", series="Internet Request for Comments", type="RFC", number="776", pages="1--13", year=1981, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 790", url="https://www.rfc-editor.org/rfc/rfc776.txt", key="RFC 776", doi="10.17487/RFC0776", } @misc{rfc777, author="J. Postel", title="{Internet Control Message Protocol}", howpublished="RFC 777", series="Internet Request for Comments", type="RFC", number="777", pages="1--14", year=1981, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 792", url="https://www.rfc-editor.org/rfc/rfc777.txt", key="RFC 777", doi="10.17487/RFC0777", } @misc{rfc778, author="D.L. Mills", title="{DCNET Internet Clock Service}", howpublished="RFC 778 (Historic)", series="Internet Request for Comments", type="RFC", number="778", pages="1--4", year=1981, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc778.txt", key="RFC 778", keywords="CLOCK", doi="10.17487/RFC0778", } @misc{rfc779, author="E. Killian", title="{Telnet send-location option}", howpublished="RFC 779 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="779", pages="1--2", year=1981, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc779.txt", key="RFC 779", keywords="TOPT-SNDL", doi="10.17487/RFC0779", } @misc{rfc780, author="S. Sluizer and J. Postel", title="{Mail Transfer Protocol}", howpublished="RFC 780", series="Internet Request for Comments", type="RFC", number="780", pages="1--47", year=1981, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 788", url="https://www.rfc-editor.org/rfc/rfc780.txt", key="RFC 780", keywords="MTP, email", doi="10.17487/RFC0780", } @misc{rfc781, author="Z. Su", title="{Specification of the Internet Protocol (IP) timestamp option}", howpublished="RFC 781", series="Internet Request for Comments", type="RFC", number="781", pages="1--1", year=1981, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc781.txt", key="RFC 781", doi="10.17487/RFC0781", } @misc{rfc782, author="J. Nabielsky and A.P. Skelton", title="{Virtual Terminal management model}", howpublished="RFC 782", series="Internet Request for Comments", type="RFC", number="782", pages="1--23", year=1981, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc782.txt", key="RFC 782", doi="10.17487/RFC0782", } @misc{rfc783, author="K.R. Sollins", title="{TFTP Protocol (revision 2)}", howpublished="RFC 783", series="Internet Request for Comments", type="RFC", number="783", pages="1--18", year=1981, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1350", url="https://www.rfc-editor.org/rfc/rfc783.txt", key="RFC 783", doi="10.17487/RFC0783", } @misc{rfc784, author="S. Sluizer and J. Postel", title="{Mail Transfer Protocol: ISI TOPS20 implementation}", howpublished="RFC 784", series="Internet Request for Comments", type="RFC", number="784", pages="1--3", year=1981, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc784.txt", key="RFC 784", keywords="MTP, email", doi="10.17487/RFC0784", } @misc{rfc785, author="S. Sluizer and J. Postel", title="{Mail Transfer Protocol: ISI TOPS20 file definitions}", howpublished="RFC 785", series="Internet Request for Comments", type="RFC", number="785", pages="1--3", year=1981, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc785.txt", key="RFC 785", keywords="MTP, email", doi="10.17487/RFC0785", } @misc{rfc786, author="S. Sluizer and J. Postel", title="{Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface}", howpublished="RFC 786", series="Internet Request for Comments", type="RFC", number="786", pages="1--2", year=1981, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc786.txt", key="RFC 786", keywords="MTP, NIMAIL, TOPS20", doi="10.17487/RFC0786", } @misc{rfc787, author="A.L. Chapin", title="{Connectionless data transmission survey/tutorial}", howpublished="RFC 787", series="Internet Request for Comments", type="RFC", number="787", pages="1--40", year=1981, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc787.txt", key="RFC 787", doi="10.17487/RFC0787", } @misc{rfc788, author="J. Postel", title="{Simple Mail Transfer Protocol}", howpublished="RFC 788", series="Internet Request for Comments", type="RFC", number="788", pages="1--64", year=1981, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 821", url="https://www.rfc-editor.org/rfc/rfc788.txt", key="RFC 788", keywords="SMTP, email", doi="10.17487/RFC0788", } @misc{rfc789, author="E.C. Rosen", title="{Vulnerabilities of network control protocols: An example}", howpublished="RFC 789", series="Internet Request for Comments", type="RFC", number="789", pages="1--16", year=1981, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc789.txt", key="RFC 789", doi="10.17487/RFC0789", } @misc{rfc790, author="J. Postel", title="{Assigned numbers}", howpublished="RFC 790 (Historic)", series="Internet Request for Comments", type="RFC", number="790", pages="1--15", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 820", url="https://www.rfc-editor.org/rfc/rfc790.txt", key="RFC 790", doi="10.17487/RFC0790", } @misc{rfc791, author="J. Postel", title="{Internet Protocol}", howpublished="RFC 791 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="791", pages="1--51", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 1349, 2474, 6864", url="https://www.rfc-editor.org/rfc/rfc791.txt", key="RFC 791", keywords="IP, IPv4", doi="10.17487/RFC0791", } @misc{rfc792, author="J. Postel", title="{Internet Control Message Protocol}", howpublished="RFC 792 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="792", pages="1--21", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 950, 4884, 6633, 6918", url="https://www.rfc-editor.org/rfc/rfc792.txt", key="RFC 792", keywords="ICMP", doi="10.17487/RFC0792", } @misc{rfc793, author="J. Postel", title="{Transmission Control Protocol}", howpublished="RFC 793 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="793", pages="1--91", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 1122, 3168, 6093, 6528", url="https://www.rfc-editor.org/rfc/rfc793.txt", key="RFC 793", keywords="TCP, TCP", doi="10.17487/RFC0793", } @misc{rfc794, author="V.G. Cerf", title="{Pre-emption}", howpublished="RFC 794 (Informational)", series="Internet Request for Comments", type="RFC", number="794", pages="1--2", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc794.txt", key="RFC 794", doi="10.17487/RFC0794", } @misc{rfc795, author="J. Postel", title="{Service mappings}", howpublished="RFC 795", series="Internet Request for Comments", type="RFC", number="795", pages="1--4", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc795.txt", key="RFC 795", doi="10.17487/RFC0795", } @misc{rfc796, author="J. Postel", title="{Address mappings}", howpublished="RFC 796 (Historic)", series="Internet Request for Comments", type="RFC", number="796", pages="1--7", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc796.txt", key="RFC 796", doi="10.17487/RFC0796", } @misc{rfc797, author="A.R. Katz", title="{Format for Bitmap files}", howpublished="RFC 797", series="Internet Request for Comments", type="RFC", number="797", pages="1--2", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc797.txt", key="RFC 797", doi="10.17487/RFC0797", } @misc{rfc798, author="A.R. Katz", title="{Decoding facsimile data from the Rapicom 450}", howpublished="RFC 798", series="Internet Request for Comments", type="RFC", number="798", pages="1--17", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc798.txt", key="RFC 798", doi="10.17487/RFC0798", } @misc{rfc799, author="D.L. Mills", title="{Internet name domains}", howpublished="RFC 799", series="Internet Request for Comments", type="RFC", number="799", pages="1--5", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc799.txt", key="RFC 799", doi="10.17487/RFC0799", } @misc{rfc800, author="J. Postel and J. Vernon", title="{Request For Comments summary notes: 700-799}", howpublished="RFC 800 (Informational)", series="Internet Request for Comments", type="RFC", number="800", pages="1--10", year=1982, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc800.txt", key="RFC 800", 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.}, doi="10.17487/RFC0800", } @misc{rfc801, author="J. Postel", title="{NCP/TCP transition plan}", howpublished="RFC 801", series="Internet Request for Comments", type="RFC", number="801", pages="1--21", year=1981, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc801.txt", key="RFC 801", 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.}, doi="10.17487/RFC0801", } @misc{rfc802, author="A.G. Malis", title="{ARPANET 1822L Host Access Protocol}", howpublished="RFC 802", series="Internet Request for Comments", type="RFC", number="802", pages="1--45", year=1981, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 851", url="https://www.rfc-editor.org/rfc/rfc802.txt", key="RFC 802", 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.}, doi="10.17487/RFC0802", } @misc{rfc803, author="A. Agarwal and M.J. O'Connor and D.L. Mills", title="{Dacom 450/500 facsimile data transcoding}", howpublished="RFC 803", series="Internet Request for Comments", type="RFC", number="803", pages="1--14", year=1981, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc803.txt", key="RFC 803", 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.}, doi="10.17487/RFC0803", } @misc{rfc804, author="International Telegraph and Telephone Consultative Committee of the International Telecommunication Union", title="{CCITT draft recommendation T.4}", howpublished="RFC 804", series="Internet Request for Comments", type="RFC", number="804", pages="1--12", year=1981, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc804.txt", key="RFC 804", abstract={This is the CCITT standard for group 3 facsimile encoding. This is useful for data compression of bit map data.}, doi="10.17487/RFC0804", } @misc{rfc805, author="J. Postel", title="{Computer mail meeting notes}", howpublished="RFC 805", series="Internet Request for Comments", type="RFC", number="805", pages="1--6", year=1982, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc805.txt", key="RFC 805", 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@hostname'' mailbox format to ``username@host.domain'', where the domain itself can be further strutured.}, doi="10.17487/RFC0805", } @misc{rfc806, author="National Bureau of Standards", title="{Proposed Federal Information Processing Standard: Specification for message format for computer based message systems}", howpublished="RFC 806", series="Internet Request for Comments", type="RFC", number="806", pages="1--107", year=1981, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 841", url="https://www.rfc-editor.org/rfc/rfc806.txt", key="RFC 806", 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.}, doi="10.17487/RFC0806", } @misc{rfc807, author="J. Postel", title="{Multimedia mail meeting notes}", howpublished="RFC 807", series="Internet Request for Comments", type="RFC", number="807", pages="1--6", year=1982, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc807.txt", key="RFC 807", 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.}, doi="10.17487/RFC0807", } @misc{rfc808, author="J. Postel", title="{Summary of computer mail services meeting held at BBN on 10 January 1979}", howpublished="RFC 808", series="Internet Request for Comments", type="RFC", number="808", pages="1--8", year=1982, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc808.txt", key="RFC 808", 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.}, doi="10.17487/RFC0808", } @misc{rfc809, author="T. Chang", title="{UCL facsimile system}", howpublished="RFC 809", series="Internet Request for Comments", type="RFC", number="809", pages="1--99", year=1982, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc809.txt", key="RFC 809", 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.}, doi="10.17487/RFC0809", } @misc{rfc810, author="E.J. Feinler and K. Harrenstien and Z. Su and V. White", title="{DoD Internet host table specification}", howpublished="RFC 810", series="Internet Request for Comments", type="RFC", number="810", pages="1--8", year=1982, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 952", url="https://www.rfc-editor.org/rfc/rfc810.txt", key="RFC 810", 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.}, doi="10.17487/RFC0810", } @misc{rfc811, author="K. Harrenstien and V. White and E.J. Feinler", title="{Hostnames Server}", howpublished="RFC 811", series="Internet Request for Comments", type="RFC", number="811", pages="1--4", year=1982, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 953", url="https://www.rfc-editor.org/rfc/rfc811.txt", key="RFC 811", 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.}, doi="10.17487/RFC0811", } @misc{rfc812, author="K. Harrenstien and V. White", title="{NICNAME/WHOIS}", howpublished="RFC 812", series="Internet Request for Comments", type="RFC", number="812", pages="1--2", year=1982, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 954, 3912", url="https://www.rfc-editor.org/rfc/rfc812.txt", key="RFC 812", 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.}, doi="10.17487/RFC0812", } @misc{rfc813, author="D.D. Clark", title="{Window and Acknowledgement Strategy in TCP}", howpublished="RFC 813 (Historic)", series="Internet Request for Comments", type="RFC", number="813", pages="1--21", year=1982, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 7805", url="https://www.rfc-editor.org/rfc/rfc813.txt", key="RFC 813", 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.}, doi="10.17487/RFC0813", } @misc{rfc814, author="D.D. Clark", title="{Name, addresses, ports, and routes}", howpublished="RFC 814 (Informational)", series="Internet Request for Comments", type="RFC", number="814", pages="1--13", year=1982, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc814.txt", key="RFC 814", 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.}, doi="10.17487/RFC0814", } @misc{rfc815, author="D.D. Clark", title="{IP datagram reassembly algorithms}", howpublished="RFC 815", series="Internet Request for Comments", type="RFC", number="815", pages="1--8", year=1982, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc815.txt", key="RFC 815", 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.}, doi="10.17487/RFC0815", } @misc{rfc816, author="D.D. Clark", title="{Fault isolation and recovery}", howpublished="RFC 816 (Historic)", series="Internet Request for Comments", type="RFC", number="816", pages="1--11", year=1982, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 7805", url="https://www.rfc-editor.org/rfc/rfc816.txt", key="RFC 816", abstract={This RFC describes the portion of fault isolation and recovery which is the responsibility of the host.}, doi="10.17487/RFC0816", } @misc{rfc817, author="D.D. Clark", title="{Modularity and efficiency in protocol implementation}", howpublished="RFC 817 (Informational)", series="Internet Request for Comments", type="RFC", number="817", pages="1--25", year=1982, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc817.txt", key="RFC 817", abstract={This RFC will discuss some of the commonly encountered reasons why protocol implementations seem to run slowly.}, doi="10.17487/RFC0817", } @misc{rfc818, author="J. Postel", title="{Remote User Telnet service}", howpublished="RFC 818 (Historic)", series="Internet Request for Comments", type="RFC", number="818", pages="1--2", year=1982, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc818.txt", key="RFC 818", abstract={This RFC is the specification of an application protocol. Any host that implements this application level service must follow this protocol.}, keywords="RTELNET", doi="10.17487/RFC0818", } @misc{rfc819, author="Z. Su and J. Postel", title="{The Domain Naming Convention for Internet User Applications}", howpublished="RFC 819", series="Internet Request for Comments", type="RFC", number="819", pages="1--18", year=1982, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc819.txt", key="RFC 819", 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 Internet name service and user applications.}, doi="10.17487/RFC0819", } @misc{rfc820, author="J. Postel", title="{Assigned numbers}", howpublished="RFC 820 (Historic)", series="Internet Request for Comments", type="RFC", number="820", pages="1--22", year=1982, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 870", url="https://www.rfc-editor.org/rfc/rfc820.txt", key="RFC 820", abstract={This RFC is an old version, see RFC 870.}, doi="10.17487/RFC0820", } @misc{rfc821, author="J. Postel", title="{Simple Mail Transfer Protocol}", howpublished="RFC 821 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="821", pages="1--72", year=1982, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2821", url="https://www.rfc-editor.org/rfc/rfc821.txt", key="RFC 821", 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 RFC 788, 780, and 772.}, keywords="SMTP", doi="10.17487/RFC0821", } @misc{rfc822, author="D. Crocker", title="{STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES}", howpublished="RFC 822 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="822", pages="1--49", year=1982, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2822, updated by RFCs 1123, 2156, 1327, 1138, 1148", url="https://www.rfc-editor.org/rfc/rfc822.txt", key="RFC 822", 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.}, keywords="MAIL", doi="10.17487/RFC0822", } @misc{rfc823, author="R.M. Hinden and A. Sheltzer", title="{DARPA Internet gateway}", howpublished="RFC 823 (Historic)", series="Internet Request for Comments", type="RFC", number="823", pages="1--45", year=1982, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc823.txt", key="RFC 823", 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.}, keywords="GGP", doi="10.17487/RFC0823", } @misc{rfc824, author="W.I. MacGregor and D.C. Tappan", title="{CRONUS Virtual Local Network}", howpublished="RFC 824", series="Internet Request for Comments", type="RFC", number="824", pages="1--41", year=1982, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc824.txt", key="RFC 824", 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 Internet Standard.}, doi="10.17487/RFC0824", } @misc{rfc825, author="J. Postel", title="{Request for comments on Requests For Comments}", howpublished="RFC 825", series="Internet Request for Comments", type="RFC", number="825", pages="1--2", year=1982, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1111, 1543, 2223", url="https://www.rfc-editor.org/rfc/rfc825.txt", key="RFC 825", 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.}, doi="10.17487/RFC0825", } @misc{rfc826, author="D. Plummer", title="{Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware}", howpublished="RFC 826 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="826", pages="1--10", year=1982, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 5227, 5494", url="https://www.rfc-editor.org/rfc/rfc826.txt", key="RFC 826", 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 Internet Standard.}, keywords="ARP", doi="10.17487/RFC0826", } @misc{rfc827, author="E.C. Rosen", title="{Exterior Gateway Protocol (EGP)}", howpublished="RFC 827", series="Internet Request for Comments", type="RFC", number="827", pages="1--46", year=1982, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 904", url="https://www.rfc-editor.org/rfc/rfc827.txt", key="RFC 827", 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.}, doi="10.17487/RFC0827", } @misc{rfc828, author="K. Owen", title="{Data communications: IFIP's international ``network'' of experts}", howpublished="RFC 828", series="Internet Request for Comments", type="RFC", number="828", pages="1--11", year=1982, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc828.txt", key="RFC 828", 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.}, doi="10.17487/RFC0828", } @misc{rfc829, author="V.G. Cerf", title="{Packet satellite technology reference sources}", howpublished="RFC 829", series="Internet Request for Comments", type="RFC", number="829", pages="1--5", year=1982, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc829.txt", key="RFC 829", 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.}, doi="10.17487/RFC0829", } @misc{rfc830, author="Z. Su", title="{Distributed system for Internet name service}", howpublished="RFC 830", series="Internet Request for Comments", type="RFC", number="830", pages="1--18", year=1982, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc830.txt", key="RFC 830", abstract={This RFC proposes a distributed name service for DARPA 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.}, doi="10.17487/RFC0830", } @misc{rfc831, author="R.T. Braden", title="{Backup access to the European side of SATNET}", howpublished="RFC 831", series="Internet Request for Comments", type="RFC", number="831", pages="1--6", year=1982, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc831.txt", key="RFC 831", 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.}, doi="10.17487/RFC0831", } @misc{rfc832, author="D. Smallberg", title="{Who talks TCP?}", howpublished="RFC 832", series="Internet Request for Comments", type="RFC", number="832", pages="1--13", year=1982, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 833", url="https://www.rfc-editor.org/rfc/rfc832.txt", key="RFC 832", 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.}, doi="10.17487/RFC0832", } @misc{rfc833, author="D. Smallberg", title="{Who talks TCP?}", howpublished="RFC 833", series="Internet Request for Comments", type="RFC", number="833", pages="1--13", year=1982, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 834", url="https://www.rfc-editor.org/rfc/rfc833.txt", key="RFC 833", 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 14-Dec-82.}, doi="10.17487/RFC0833", } @misc{rfc834, author="D. Smallberg", title="{Who talks TCP?}", howpublished="RFC 834", series="Internet Request for Comments", type="RFC", number="834", pages="1--13", year=1982, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 835", url="https://www.rfc-editor.org/rfc/rfc834.txt", key="RFC 834", 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 22-Dec-82.}, doi="10.17487/RFC0834", } @misc{rfc835, author="D. Smallberg", title="{Who talks TCP?}", howpublished="RFC 835", series="Internet Request for Comments", type="RFC", number="835", pages="1--13", year=1982, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 836", url="https://www.rfc-editor.org/rfc/rfc835.txt", key="RFC 835", 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 28-Dec-82 through 5-Jan-83.}, doi="10.17487/RFC0835", } @misc{rfc836, author="D. Smallberg", title="{Who talks TCP?}", howpublished="RFC 836", series="Internet Request for Comments", type="RFC", number="836", pages="1--13", year=1983, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 837", url="https://www.rfc-editor.org/rfc/rfc836.txt", key="RFC 836", 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.}, doi="10.17487/RFC0836", } @misc{rfc837, author="D. Smallberg", title="{Who talks TCP?}", howpublished="RFC 837", series="Internet Request for Comments", type="RFC", number="837", pages="1--13", year=1983, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 838", url="https://www.rfc-editor.org/rfc/rfc837.txt", key="RFC 837", 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 31-Dec-82. The tests were run on 11-Jan-83.}, doi="10.17487/RFC0837", } @misc{rfc838, author="D. Smallberg", title="{Who talks TCP?}", howpublished="RFC 838", series="Internet Request for Comments", type="RFC", number="838", pages="1--13", year=1983, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 839", url="https://www.rfc-editor.org/rfc/rfc838.txt", key="RFC 838", 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 31-Dec-82. The tests were run on 18-Jan-83.}, doi="10.17487/RFC0838", } @misc{rfc839, author="D. Smallberg", title="{Who talks TCP?}", howpublished="RFC 839", series="Internet Request for Comments", type="RFC", number="839", pages="1--14", year=1983, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 842", url="https://www.rfc-editor.org/rfc/rfc839.txt", key="RFC 839", 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 31-Dec-82. The tests were run on 25-Jan-83.}, doi="10.17487/RFC0839", } @misc{rfc840, author="J. Postel", title="{Official protocols}", howpublished="RFC 840 (Historic)", series="Internet Request for Comments", type="RFC", number="840", pages="1--23", year=1983, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 880", url="https://www.rfc-editor.org/rfc/rfc840.txt", key="RFC 840", abstract={This RFC has been revised, see RFC 880.}, doi="10.17487/RFC0840", } @misc{rfc841, author="National Bureau of Standards", title="{Specification for message format for Computer Based Message Systems}", howpublished="RFC 841", series="Internet Request for Comments", type="RFC", number="841", pages="1--117", year=1983, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc841.txt", key="RFC 841", 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.}, doi="10.17487/RFC0841", } @misc{rfc842, author="D. Smallberg", title="{Who talks TCP? - survey of 1 February 83}", howpublished="RFC 842", series="Internet Request for Comments", type="RFC", number="842", pages="1--12", year=1983, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 843", url="https://www.rfc-editor.org/rfc/rfc842.txt", key="RFC 842", 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.}, doi="10.17487/RFC0842", } @misc{rfc843, author="D. Smallberg", title="{Who talks TCP? - survey of 8 February 83}", howpublished="RFC 843", series="Internet Request for Comments", type="RFC", number="843", pages="1--13", year=1983, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 845, updated by RFC 844", url="https://www.rfc-editor.org/rfc/rfc843.txt", key="RFC 843", 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.}, doi="10.17487/RFC0843", } @misc{rfc844, author="R. Clements", title="{Who talks ICMP, too? - Survey of 18 February 1983}", howpublished="RFC 844", series="Internet Request for Comments", type="RFC", number="844", pages="1--5", year=1983, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc844.txt", key="RFC 844", abstract={This survey determines how many hosts are able to respond to TELENET 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.}, doi="10.17487/RFC0844", } @misc{rfc845, author="D. Smallberg", title="{Who talks TCP? - survey of 15 February 1983}", howpublished="RFC 845", series="Internet Request for Comments", type="RFC", number="845", pages="1--14", year=1983, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 846", url="https://www.rfc-editor.org/rfc/rfc845.txt", key="RFC 845", 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.}, doi="10.17487/RFC0845", } @misc{rfc846, author="D. Smallberg", title="{Who talks TCP? - survey of 22 February 1983}", howpublished="RFC 846", series="Internet Request for Comments", type="RFC", number="846", pages="1--14", year=1983, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 847", url="https://www.rfc-editor.org/rfc/rfc846.txt", key="RFC 846", 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.}, doi="10.17487/RFC0846", } @misc{rfc847, author="A. Westine and D. Smallberg and J. Postel", title="{Summary of Smallberg surveys}", howpublished="RFC 847", series="Internet Request for Comments", type="RFC", number="847", pages="1--2", year=1983, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc847.txt", key="RFC 847", 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 Internet (not counting TACs or ECHOS).}, doi="10.17487/RFC0847", } @misc{rfc848, author="D. Smallberg", title="{Who provides the ``little'' TCP services?}", howpublished="RFC 848", series="Internet Request for Comments", type="RFC", number="848", pages="1--5", year=1983, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc848.txt", key="RFC 848", 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.}, doi="10.17487/RFC0848", } @misc{rfc849, author="M.R. Crispin", title="{Suggestions for improved host table distribution}", howpublished="RFC 849", series="Internet Request for Comments", type="RFC", number="849", pages="1--2", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc849.txt", key="RFC 849", 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.}, doi="10.17487/RFC0849", } @misc{rfc850, author="M.R. Horton", title="{Standard for interchange of USENET messages}", howpublished="RFC 850", series="Internet Request for Comments", type="RFC", number="850", pages="1--17", year=1983, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1036", url="https://www.rfc-editor.org/rfc/rfc850.txt", key="RFC 850", abstract={This memo is distributed as an RFC only to make this information easily accessible to researchers in the ARPA 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.}, doi="10.17487/RFC0850", } @misc{rfc851, author="A.G. Malis", title="{ARPANET 1822L Host Access Protocol}", howpublished="RFC 851", series="Internet Request for Comments", type="RFC", number="851", pages="1--47", year=1983, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 878", url="https://www.rfc-editor.org/rfc/rfc851.txt", key="RFC 851", 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.}, doi="10.17487/RFC0851", } @misc{rfc852, author="A.G. Malis", title="{ARPANET short blocking feature}", howpublished="RFC 852", series="Internet Request for Comments", type="RFC", number="852", pages="1--13", year=1983, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc852.txt", key="RFC 852", 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.}, doi="10.17487/RFC0852", } @misc{rfc854, author="J. Postel and J.K. Reynolds", title="{Telnet Protocol Specification}", howpublished="RFC 854 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="854", pages="1--15", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 5198", url="https://www.rfc-editor.org/rfc/rfc854.txt", key="RFC 854", 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.}, keywords="TELNET", doi="10.17487/RFC0854", } @misc{rfc855, author="J. Postel and J.K. Reynolds", title="{Telnet Option Specifications}", howpublished="RFC 855 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="855", pages="1--3", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc855.txt", key="RFC 855", 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.}, keywords="TELNET", doi="10.17487/RFC0855", } @misc{rfc856, author="J. Postel and J. Reynolds", title="{Telnet Binary Transmission}", howpublished="RFC 856 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="856", pages="1--4", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc856.txt", key="RFC 856", 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.}, keywords="TOPT-BIN", doi="10.17487/RFC0856", } @misc{rfc857, author="J. Postel and J. Reynolds", title="{Telnet Echo Option}", howpublished="RFC 857 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="857", pages="1--5", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc857.txt", key="RFC 857", 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.}, keywords="TOPT-ECHO", doi="10.17487/RFC0857", } @misc{rfc858, author="J. Postel and J. Reynolds", title="{Telnet Suppress Go Ahead Option}", howpublished="RFC 858 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="858", pages="1--2", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc858.txt", key="RFC 858", 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.}, keywords="TOPT-SUPP", doi="10.17487/RFC0858", } @misc{rfc859, author="J. Postel and J. Reynolds", title="{Telnet Status Option}", howpublished="RFC 859 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="859", pages="1--3", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc859.txt", key="RFC 859", 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).}, keywords="TOPT-STAT", doi="10.17487/RFC0859", } @misc{rfc860, author="J. Postel and J. Reynolds", title="{Telnet Timing Mark Option}", howpublished="RFC 860 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="860", pages="1--4", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc860.txt", key="RFC 860", 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.}, keywords="TOPT-TIM", doi="10.17487/RFC0860", } @misc{rfc861, author="J. Postel and J. Reynolds", title="{Telnet Extended Options: List Option}", howpublished="RFC 861 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="861", pages="1--2", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc861.txt", key="RFC 861", 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.}, keywords="TOPT-EXTOP", doi="10.17487/RFC0861", } @misc{rfc862, author="J. Postel", title="{Echo Protocol}", howpublished="RFC 862 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="862", pages="1--1", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc862.txt", key="RFC 862", 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.}, keywords="ECHO", doi="10.17487/RFC0862", } @misc{rfc863, author="J. Postel", title="{Discard Protocol}", howpublished="RFC 863 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="863", pages="1--1", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc863.txt", key="RFC 863", 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.}, keywords="DISCARD", doi="10.17487/RFC0863", } @misc{rfc864, author="J. Postel", title="{Character Generator Protocol}", howpublished="RFC 864 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="864", pages="1--3", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc864.txt", key="RFC 864", 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.}, keywords="CHARGEN", doi="10.17487/RFC0864", } @misc{rfc865, author="J. Postel", title="{Quote of the Day Protocol}", howpublished="RFC 865 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="865", pages="1--1", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc865.txt", key="RFC 865", 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.}, keywords="QUOTE", doi="10.17487/RFC0865", } @misc{rfc866, author="J. Postel", title="{Active users}", howpublished="RFC 866 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="866", pages="1--1", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc866.txt", key="RFC 866", 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.}, keywords="USERS", doi="10.17487/RFC0866", } @misc{rfc867, author="J. Postel", title="{Daytime Protocol}", howpublished="RFC 867 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="867", pages="1--2", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc867.txt", key="RFC 867", 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.}, keywords="DAYTIME", doi="10.17487/RFC0867", } @misc{rfc868, author="J. Postel and K. Harrenstien", title="{Time Protocol}", howpublished="RFC 868 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="868", pages="1--2", year=1983, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc868.txt", key="RFC 868", 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.}, keywords="TIME", doi="10.17487/RFC0868", } @misc{rfc869, author="R. Hinden", title="{Host Monitoring Protocol}", howpublished="RFC 869 (Historic)", series="Internet Request for Comments", type="RFC", number="869", pages="1--72", year=1983, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc869.txt", key="RFC 869", 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.}, keywords="HMP, HMP", doi="10.17487/RFC0869", } @misc{rfc870, author="J.K. Reynolds and J. Postel", title="{Assigned numbers}", howpublished="RFC 870 (Historic)", series="Internet Request for Comments", type="RFC", number="870", pages="1--26", year=1983, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 900", url="https://www.rfc-editor.org/rfc/rfc870.txt", key="RFC 870", abstract={This RFC documents the list of numbers assigned for networks, protocols, etc. Obsoletes RFCs 820, 790, 776, 770, 762, 758, 755, 750, 739, 604.}, doi="10.17487/RFC0870", } @misc{rfc871, author="M.A. Padlipsky", title="{Perspective on the ARPANET reference model}", howpublished="RFC 871", series="Internet Request for Comments", type="RFC", number="871", pages="1--29", year=1982, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc871.txt", key="RFC 871", 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.}, doi="10.17487/RFC0871", } @misc{rfc872, author="M.A. Padlipsky", title="{TCP-on-a-LAN}", howpublished="RFC 872 (Informational)", series="Internet Request for Comments", type="RFC", number="872", pages="1--10", year=1982, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc872.txt", key="RFC 872", 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.}, keywords="TCP LAN", doi="10.17487/RFC0872", } @misc{rfc873, author="M.A. Padlipsky", title="{Illusion of vendor support}", howpublished="RFC 873", series="Internet Request for Comments", type="RFC", number="873", pages="1--12", year=1982, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc873.txt", key="RFC 873", 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.}, doi="10.17487/RFC0873", } @misc{rfc874, author="M.A. Padlipsky", title="{Critique of X.25}", howpublished="RFC 874", series="Internet Request for Comments", type="RFC", number="874", pages="1--17", year=1982, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc874.txt", key="RFC 874", 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.}, doi="10.17487/RFC0874", } @misc{rfc875, author="M.A. Padlipsky", title="{Gateways, architectures, and heffalumps}", howpublished="RFC 875", series="Internet Request for Comments", type="RFC", number="875", pages="1--10", year=1982, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc875.txt", key="RFC 875", 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.}, doi="10.17487/RFC0875", } @misc{rfc876, author="D. Smallberg", title="{Survey of SMTP implementations}", howpublished="RFC 876", series="Internet Request for Comments", type="RFC", number="876", pages="1--13", year=1983, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc876.txt", key="RFC 876", 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.}, doi="10.17487/RFC0876", } @misc{rfc877, author="J.T. Korb", title="{Standard for the transmission of IP datagrams over public data networks}", howpublished="RFC 877", series="Internet Request for Comments", type="RFC", number="877", pages="1--2", year=1983, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1356", url="https://www.rfc-editor.org/rfc/rfc877.txt", key="RFC 877", 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.}, doi="10.17487/RFC0877", } @misc{rfc878, author="A.G. Malis", title="{ARPANET 1822L Host Access Protocol}", howpublished="RFC 878", series="Internet Request for Comments", type="RFC", number="878", pages="1--51", year=1983, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc878.txt", key="RFC 878", abstract={This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. The 1822L procedure allows ARPANET hosts to use logical identifiers as well as 1822 physical interface identifiers to address each other.}, doi="10.17487/RFC0878", } @misc{rfc879, author="J. Postel", title="{The TCP Maximum Segment Size and Related Topics}", howpublished="RFC 879 (Historic)", series="Internet Request for Comments", type="RFC", number="879", pages="1--11", year=1983, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 7805, updated by RFC 6691", url="https://www.rfc-editor.org/rfc/rfc879.txt", key="RFC 879", abstract={This RFC discusses the TCP Maximum Segment Size Option and related topics. The purposes 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''.}, doi="10.17487/RFC0879", } @misc{rfc880, author="J.K. Reynolds and J. Postel", title="{Official protocols}", howpublished="RFC 880 (Historic)", series="Internet Request for Comments", type="RFC", number="880", pages="1--26", year=1983, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 901", url="https://www.rfc-editor.org/rfc/rfc880.txt", key="RFC 880", abstract={This RFC identifies the documents specifying the official protocols used in the ARPA Internet. Annotations identify any revisions or changes planned. Obsoletes RFC 840.}, doi="10.17487/RFC0880", } @misc{rfc881, author="J. Postel", title="{Domain names plan and schedule}", howpublished="RFC 881", series="Internet Request for Comments", type="RFC", number="881", pages="1--10", year=1983, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 897", url="https://www.rfc-editor.org/rfc/rfc881.txt", key="RFC 881", 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.}, doi="10.17487/RFC0881", } @misc{rfc882, author="P.V. Mockapetris", title="{Domain names: Concepts and facilities}", howpublished="RFC 882", series="Internet Request for Comments", type="RFC", number="882", pages="1--31", year=1983, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1034, 1035, updated by RFC 973", url="https://www.rfc-editor.org/rfc/rfc882.txt", key="RFC 882", abstract={This RFC introduces domain style names, their use for ARPA Internet mail and host address support, and the protocol and servers used to implement domain name facilities.}, doi="10.17487/RFC0882", } @misc{rfc883, author="P.V. Mockapetris", title="{Domain names: Implementation specification}", howpublished="RFC 883", series="Internet Request for Comments", type="RFC", number="883", pages="1--74", year=1983, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1034, 1035, updated by RFC 973", url="https://www.rfc-editor.org/rfc/rfc883.txt", key="RFC 883", 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.}, doi="10.17487/RFC0883", } @misc{rfc884, author="M. Solomon and E. Wimmers", title="{Telnet terminal type option}", howpublished="RFC 884", series="Internet Request for Comments", type="RFC", number="884", pages="1--5", year=1983, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 930", url="https://www.rfc-editor.org/rfc/rfc884.txt", key="RFC 884", abstract={This RFC specifies a standard for the ARPA Internet community. It specifies a method for exchanging terminal type information in the Telnet protocol.}, doi="10.17487/RFC0884", } @misc{rfc885, author="J. Postel", title="{Telnet end of record option}", howpublished="RFC 885 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="885", pages="1--2", year=1983, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc885.txt", key="RFC 885", 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.}, keywords="TOPT-EOR", doi="10.17487/RFC0885", } @misc{rfc886, author="M.T. Rose", title="{Proposed standard for message header munging}", howpublished="RFC 886", series="Internet Request for Comments", type="RFC", number="886", pages="1--16", year=1983, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc886.txt", key="RFC 886", 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.}, doi="10.17487/RFC0886", } @misc{rfc887, author="M. Accetta", title="{Resource Location Protocol}", howpublished="RFC 887 (Experimental)", series="Internet Request for Comments", type="RFC", number="887", pages="1--16", year=1983, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc887.txt", key="RFC 887", 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 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 Internet.}, keywords="RLP", doi="10.17487/RFC0887", } @misc{rfc888, author="L. Seamonson and E.C. Rosen", title="{``STUB'' Exterior Gateway Protocol}", howpublished="RFC 888", series="Internet Request for Comments", type="RFC", number="888", pages="1--39", year=1984, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 904", url="https://www.rfc-editor.org/rfc/rfc888.txt", key="RFC 888", abstract={This RFC describes the Exterior Gateway Protocol 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.}, doi="10.17487/RFC0888", } @misc{rfc889, author="D.L. Mills", title="{Internet Delay Experiments}", howpublished="RFC 889 (Informational)", series="Internet Request for Comments", type="RFC", number="889", pages="1--12", year=1983, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc889.txt", key="RFC 889", 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 Internet and advice to TCP implementers.}, doi="10.17487/RFC0889", } @misc{rfc890, author="J. Postel", title="{Exterior Gateway Protocol implementation schedule}", howpublished="RFC 890", series="Internet Request for Comments", type="RFC", number="890", pages="1--3", year=1984, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc890.txt", key="RFC 890", abstract={This memo is a policy statement on the implementation of the Exterior Gateway Protocol in the 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.}, keywords="EGP", doi="10.17487/RFC0890", } @misc{rfc891, author="D.L. Mills", title="{DCN Local-Network Protocols}", howpublished="RFC 891 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="891", pages="1--26", year=1983, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc891.txt", key="RFC 891", 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.}, keywords="IP-DC", doi="10.17487/RFC0891", } @misc{rfc892, author="International Organization for Standardization", title="{ISO Transport Protocol specification}", howpublished="RFC 892", series="Internet Request for Comments", type="RFC", number="892", pages="1--82", year=1983, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 905", url="https://www.rfc-editor.org/rfc/rfc892.txt", key="RFC 892", 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.}, doi="10.17487/RFC0892", } @misc{rfc893, author="S. Leffler and M.J. Karels", title="{Trailer encapsulations}", howpublished="RFC 893", series="Internet Request for Comments", type="RFC", number="893", pages="1--6", year=1984, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc893.txt", key="RFC 893", 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.}, doi="10.17487/RFC0893", } @misc{rfc894, author="C. Hornig", title="{A Standard for the Transmission of IP Datagrams over Ethernet Networks}", howpublished="RFC 894 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="894", pages="1--3", year=1984, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc894.txt", key="RFC 894", 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.}, keywords="IP-E", doi="10.17487/RFC0894", } @misc{rfc895, author="J. Postel", title="{Standard for the transmission of IP datagrams over experimental Ethernet networks}", howpublished="RFC 895 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="895", pages="1--3", year=1984, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc895.txt", key="RFC 895", 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.}, keywords="IP-EE", doi="10.17487/RFC0895", } @misc{rfc896, author="J. Nagle", title="{Congestion Control in IP/TCP Internetworks}", howpublished="RFC 896 (Historic)", series="Internet Request for Comments", type="RFC", number="896", pages="1--9", year=1984, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 7805", url="https://www.rfc-editor.org/rfc/rfc896.txt", key="RFC 896", 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.}, doi="10.17487/RFC0896", } @misc{rfc897, author="J. Postel", title="{Domain name system implementation schedule}", howpublished="RFC 897", series="Internet Request for Comments", type="RFC", number="897", pages="1--8", year=1984, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 921", url="https://www.rfc-editor.org/rfc/rfc897.txt", key="RFC 897", abstract={This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is a partial update of RFC 881. The intent of this memo is to detail the schedule for the implementation for 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.}, doi="10.17487/RFC0897", } @misc{rfc898, author="R.M. Hinden and J. Postel and M. Muuss and J.K. Reynolds", title="{Gateway special interest group meeting notes}", howpublished="RFC 898", series="Internet Request for Comments", type="RFC", number="898", pages="1--24", year=1984, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc898.txt", key="RFC 898", 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 a meeting. No conclusions, decisions, or policy statements are documented in this note.}, doi="10.17487/RFC0898", } @misc{rfc899, author="J. Postel and A. Westine", title="{Request For Comments summary notes: 800-899}", howpublished="RFC 899 (Informational)", series="Internet Request for Comments", type="RFC", number="899", pages="1--18", year=1984, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc899.txt", key="RFC 899", doi="10.17487/RFC0899", } @misc{rfc900, author="J.K. Reynolds and J. Postel", title="{Assigned Numbers}", howpublished="RFC 900 (Historic)", series="Internet Request for Comments", type="RFC", number="900", pages="1--43", year=1984, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 923", url="https://www.rfc-editor.org/rfc/rfc900.txt", key="RFC 900", abstract={This RFC specifies parameter values use in the Internet family of protocols, such as network numbers, well known ports, protocol types, and version numbers. This memo is an official status report on the protocol parameters used in the Internet protocol system. See RFC-990 and 997.}, doi="10.17487/RFC0900", } @misc{rfc901, author="J.K. Reynolds and J. Postel", title="{Official ARPA-Internet protocols}", howpublished="RFC 901", series="Internet Request for Comments", type="RFC", number="901", pages="1--28", year=1984, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 924", url="https://www.rfc-editor.org/rfc/rfc901.txt", key="RFC 901", abstract={This RFC identifies the documents specifying the official protocols used in the ARPA-Internet. Annotations identify any revisions or changes planned. This memo is an official status report on the protocols used in the DARPA research community. See RFC-991.}, doi="10.17487/RFC0901", } @misc{rfc902, author="J.K. Reynolds and J. Postel", title="{ARPA Internet Protocol policy}", howpublished="RFC 902", series="Internet Request for Comments", type="RFC", number="902", pages="1--5", year=1984, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc902.txt", key="RFC 902", 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.}, doi="10.17487/RFC0902", } @misc{rfc903, author="R. Finlayson and T. Mann and J.C. Mogul and M. Theimer", title="{A Reverse Address Resolution Protocol}", howpublished="RFC 903 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="903", pages="1--4", year=1984, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc903.txt", key="RFC 903", 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 improvements.}, keywords="RARP", doi="10.17487/RFC0903", } @misc{rfc904, author="D.L. Mills", title="{Exterior Gateway Protocol formal specification}", howpublished="RFC 904 (Historic)", series="Internet Request for Comments", type="RFC", number="904", pages="1--30", year=1984, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc904.txt", key="RFC 904", abstract={RFC-904 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.}, keywords="EGP", doi="10.17487/RFC0904", } @misc{rfc905, author="ISO", title="{ISO Transport Protocol specification ISO DP 8073}", howpublished="RFC 905", series="Internet Request for Comments", type="RFC", number="905", pages="1--164", year=1984, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc905.txt", key="RFC 905", 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.}, doi="10.17487/RFC0905", } @misc{rfc906, author="R. Finlayson", title="{Bootstrap loading using TFTP}", howpublished="RFC 906", series="Internet Request for Comments", type="RFC", number="906", pages="1--4", year=1984, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc906.txt", key="RFC 906", 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.}, doi="10.17487/RFC0906", } @misc{rfc907, author="Bolt Beranek and Newman Laboratories", title="{Host Access Protocol specification}", howpublished="RFC 907 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="907", pages="1--75", year=1984, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 1221", url="https://www.rfc-editor.org/rfc/rfc907.txt", key="RFC 907", 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.}, keywords="IP-WB", doi="10.17487/RFC0907", } @misc{rfc908, author="D. Velten and R.M. Hinden and J. Sax", title="{Reliable Data Protocol}", howpublished="RFC 908 (Experimental)", series="Internet Request for Comments", type="RFC", number="908", pages="1--62", year=1984, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 1151", url="https://www.rfc-editor.org/rfc/rfc908.txt", key="RFC 908", 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.}, keywords="RDP", doi="10.17487/RFC0908", } @misc{rfc909, author="C. Welles and W. Milliken", title="{Loader Debugger Protocol}", howpublished="RFC 909 (Experimental)", series="Internet Request for Comments", type="RFC", number="909", pages="1--135", year=1984, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc909.txt", key="RFC 909", 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 improvemts.}, keywords="LDP", doi="10.17487/RFC0909", } @misc{rfc910, author="H.C. Forsdick", title="{Multimedia mail meeting notes}", howpublished="RFC 910", series="Internet Request for Comments", type="RFC", number="910", pages="1--11", year=1984, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc910.txt", key="RFC 910", 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.}, doi="10.17487/RFC0910", } @misc{rfc911, author="P. Kirton", title="{EGP Gateway under Berkeley UNIX 4.2}", howpublished="RFC 911", series="Internet Request for Comments", type="RFC", number="911", pages="1--23", year=1984, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc911.txt", key="RFC 911", 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).}, doi="10.17487/RFC0911", } @misc{rfc912, author="M. St. Johns", title="{Authentication service}", howpublished="RFC 912", series="Internet Request for Comments", type="RFC", number="912", pages="1--3", year=1984, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 931", url="https://www.rfc-editor.org/rfc/rfc912.txt", key="RFC 912", 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.}, doi="10.17487/RFC0912", } @misc{rfc913, author="M. Lottor", title="{Simple File Transfer Protocol}", howpublished="RFC 913 (Historic)", series="Internet Request for Comments", type="RFC", number="913", pages="1--15", year=1984, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc913.txt", key="RFC 913", 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.}, keywords="SFTP, FTP", doi="10.17487/RFC0913", } @misc{rfc914, author="D.J. Farber and G. Delp and T.M. Conte", title="{Thinwire protocol for connecting personal computers to the Internet}", howpublished="RFC 914 (Historic)", series="Internet Request for Comments", type="RFC", number="914", pages="1--22", year=1984, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc914.txt", key="RFC 914", abstract={This RFC 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.}, keywords="THINWIRE", doi="10.17487/RFC0914", } @misc{rfc915, author="M.A. Elvy and R. Nedved", title="{Network mail path service}", howpublished="RFC 915", series="Internet Request for Comments", type="RFC", number="915", pages="1--11", year=1984, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc915.txt", key="RFC 915", abstract={This RFC proposed a new service for the ARPA-Internet community and requests discussion and suggestions for improvements. 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.}, doi="10.17487/RFC0915", } @misc{rfc916, author="G.G. Finn", title="{Reliable Asynchronous Transfer Protocol (RATP)}", howpublished="RFC 916 (Historic)", series="Internet Request for Comments", type="RFC", number="916", pages="1--54", year=1984, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc916.txt", key="RFC 916", abstract={This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. 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.}, keywords="RATP", doi="10.17487/RFC0916", } @misc{rfc917, author="J.C. Mogul", title="{Internet subnets}", howpublished="RFC 917", series="Internet Request for Comments", type="RFC", number="917", pages="1--22", year=1984, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc917.txt", key="RFC 917", 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.}, doi="10.17487/RFC0917", } @misc{rfc918, author="J.K. Reynolds", title="{Post Office Protocol}", howpublished="RFC 918", series="Internet Request for Comments", type="RFC", number="918", pages="1--5", year=1984, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 937", url="https://www.rfc-editor.org/rfc/rfc918.txt", key="RFC 918", abstract={This RFC suggests a simple method for workstations to dynamically access mail from a mailbox server. The intent of the Post Office Protocol (POP) is to allow a user's workstation to access mail from a mailbox server. It is expected that mail will be posted from the workstation to the mailbox server via the Simple Mail Transfer Protocol (SMTP). This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. The status of this protocol is experimental, and this protocol is dependent upon TCP.}, doi="10.17487/RFC0918", } @misc{rfc919, author="J.C. Mogul", title="{Broadcasting Internet Datagrams}", howpublished="RFC 919 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="919", pages="1--8", year=1984, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc919.txt", key="RFC 919", 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.}, keywords="", doi="10.17487/RFC0919", } @misc{rfc920, author="J. Postel and J.K. Reynolds", title="{Domain requirements}", howpublished="RFC 920", series="Internet Request for Comments", type="RFC", number="920", pages="1--14", year=1984, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc920.txt", key="RFC 920", 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.}, doi="10.17487/RFC0920", } @misc{rfc921, author="J. Postel", title="{Domain name system implementation schedule - revised}", howpublished="RFC 921", series="Internet Request for Comments", type="RFC", number="921", pages="1--13", year=1984, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc921.txt", key="RFC 921", abstract={This memo is a policy statement on the implementation of the Domain Style Naming System in the 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.}, doi="10.17487/RFC0921", } @misc{rfc922, author="J.C. Mogul", title="{Broadcasting Internet datagrams in the presence of subnets}", howpublished="RFC 922 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="922", pages="1--12", year=1984, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc922.txt", key="RFC 922", 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.}, keywords="", doi="10.17487/RFC0922", } @misc{rfc923, author="J.K. Reynolds and J. Postel", title="{Assigned numbers}", howpublished="RFC 923 (Historic)", series="Internet Request for Comments", type="RFC", number="923", pages="1--47", year=1984, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 943", url="https://www.rfc-editor.org/rfc/rfc923.txt", key="RFC 923", abstract={This RFC documents the currently assigned values from several series of numbers used in network protocol implementations. This edition of Assigned Numbers obsoletes RFC-900 and earlier editions. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990, and 997.}, doi="10.17487/RFC0923", } @misc{rfc924, author="J.K. Reynolds and J. Postel", title="{Official ARPA-Internet protocols for connecting personal computers to the Internet}", howpublished="RFC 924", series="Internet Request for Comments", type="RFC", number="924", pages="1--35", year=1984, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 944", url="https://www.rfc-editor.org/rfc/rfc924.txt", key="RFC 924", abstract={This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-900 and earlier editions. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.}, doi="10.17487/RFC0924", } @misc{rfc925, author="J. Postel", title="{Multi-LAN address resolution}", howpublished="RFC 925", series="Internet Request for Comments", type="RFC", number="925", pages="1--15", year=1984, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc925.txt", key="RFC 925", 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 an site a distinct Internet network number. It is desirable to hide the details of the interconnections between the LANs within an 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 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.}, doi="10.17487/RFC0925", } @misc{rfc926, author="International Organization for Standardization", title="{Protocol for providing the connectionless mode network services}", howpublished="RFC 926", series="Internet Request for Comments", type="RFC", number="926", pages="1--107", year=1984, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 994", url="https://www.rfc-editor.org/rfc/rfc926.txt", key="RFC 926", 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 distributred as an RFC for information only. It does not specify a standard for the ARPA-Internet.}, doi="10.17487/RFC0926", } @misc{rfc927, author="B.A. Anderson", title="{TACACS user identification Telnet option}", howpublished="RFC 927 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="927", pages="1--4", year=1984, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc927.txt", key="RFC 927", 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.}, keywords="TOPT-TACACS", doi="10.17487/RFC0927", } @misc{rfc928, author="M.A. Padlipsky", title="{Introduction to proposed DoD standard H-FP}", howpublished="RFC 928", series="Internet Request for Comments", type="RFC", number="928", pages="1--21", year=1984, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc928.txt", key="RFC 928", 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.}, doi="10.17487/RFC0928", } @misc{rfc929, author="J. Lilienkamp and R. Mandell and M.A. Padlipsky", title="{Proposed Host-Front End Protocol}", howpublished="RFC 929 (Historic)", series="Internet Request for Comments", type="RFC", number="929", pages="1--56", year=1984, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc929.txt", key="RFC 929", 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.}, keywords="HFEP", doi="10.17487/RFC0929", } @misc{rfc930, author="M. Solomon and E. Wimmers", title="{Telnet terminal type option}", howpublished="RFC 930", series="Internet Request for Comments", type="RFC", number="930", pages="1--4", year=1985, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1091", url="https://www.rfc-editor.org/rfc/rfc930.txt", key="RFC 930", 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. 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.}, doi="10.17487/RFC0930", } @misc{rfc931, author="M. St. Johns", title="{Authentication server}", howpublished="RFC 931", series="Internet Request for Comments", type="RFC", number="931", pages="1--5", year=1985, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1413", url="https://www.rfc-editor.org/rfc/rfc931.txt", key="RFC 931", 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.}, doi="10.17487/RFC0931", } @misc{rfc932, author="D.D. Clark", title="{Subnetwork addressing scheme}", howpublished="RFC 932", series="Internet Request for Comments", type="RFC", number="932", pages="1--4", year=1985, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc932.txt", key="RFC 932", 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.}, doi="10.17487/RFC0932", } @misc{rfc933, author="S. Silverman", title="{Output marking Telnet option}", howpublished="RFC 933 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="933", pages="1--4", year=1985, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc933.txt", key="RFC 933", 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.}, keywords="TOPT-OM", doi="10.17487/RFC0933", } @misc{rfc934, author="M.T. Rose and E.A. Stefferud", title="{Proposed standard for message encapsulation}", howpublished="RFC 934", series="Internet Request for Comments", type="RFC", number="934", pages="1--10", year=1985, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc934.txt", key="RFC 934", 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.}, doi="10.17487/RFC0934", } @misc{rfc935, author="J.G. Robinson", title="{Reliable link layer protocols}", howpublished="RFC 935", series="Internet Request for Comments", type="RFC", number="935", pages="1--12", year=1985, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc935.txt", key="RFC 935", 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.}, doi="10.17487/RFC0935", } @misc{rfc936, author="M.J. Karels", title="{Another Internet subnet addressing scheme}", howpublished="RFC 936", series="Internet Request for Comments", type="RFC", number="936", pages="1--4", year=1985, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc936.txt", key="RFC 936", 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.}, doi="10.17487/RFC0936", } @misc{rfc937, author="M. Butler and J. Postel and D. Chase and J. Goldberger and J.K. Reynolds", title="{Post Office Protocol: Version 2}", howpublished="RFC 937 (Historic)", series="Internet Request for Comments", type="RFC", number="937", pages="1--24", year=1985, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc937.txt", key="RFC 937", 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.}, keywords="POP2, Post Office Protocol, Version 2", doi="10.17487/RFC0937", } @misc{rfc938, author="T. Miller", title="{Internet Reliable Transaction Protocol functional and interface specification}", howpublished="RFC 938 (Experimental)", series="Internet Request for Comments", type="RFC", number="938", pages="1--19", year=1985, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc938.txt", key="RFC 938", 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.}, keywords="IRTP", doi="10.17487/RFC0938", } @misc{rfc939, author="National Research Council", title="{Executive summary of the NRC report on transport protocols for Department of Defense data networks}", howpublished="RFC 939", series="Internet Request for Comments", type="RFC", number="939", pages="1--20", year=1985, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc939.txt", key="RFC 939", 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. This RFC is distributed for information only. This RFC does not establish any policy for the DARPA research community or the DDN operational community.}, doi="10.17487/RFC0939", } @misc{rfc940, author="Gateway Algorithms and Data Structures Task Force", title="{Toward an Internet standard scheme for subnetting}", howpublished="RFC 940", series="Internet Request for Comments", type="RFC", number="940", pages="1--3", year=1985, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc940.txt", key="RFC 940", 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.}, doi="10.17487/RFC0940", } @misc{rfc941, author="International Organization for Standardization", title="{Addendum to the network service definition covering network layer addressing}", howpublished="RFC 941", series="Internet Request for Comments", type="RFC", number="941", pages="1--34", year=1985, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc941.txt", key="RFC 941", 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.}, doi="10.17487/RFC0941", } @misc{rfc942, author="National Research Council", title="{Transport protocols for Department of Defense data networks}", howpublished="RFC 942", series="Internet Request for Comments", type="RFC", number="942", pages="1--88", year=1985, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc942.txt", key="RFC 942", 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).}, doi="10.17487/RFC0942", } @misc{rfc943, author="J.K. Reynolds and J. Postel", title="{Assigned numbers}", howpublished="RFC 943 (Historic)", series="Internet Request for Comments", type="RFC", number="943", pages="1--50", year=1985, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 960", url="https://www.rfc-editor.org/rfc/rfc943.txt", key="RFC 943", abstract={This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This RFC will be updated periodically, and in any case current information can be obtained from Joyce Reynolds. The assignment of numbers is also handled by Joyce. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, network number, etc., please contact Joyce to receive a number assignment. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997.}, doi="10.17487/RFC0943", } @misc{rfc944, author="J.K. Reynolds and J. Postel", title="{Official ARPA-Internet protocols}", howpublished="RFC 944", series="Internet Request for Comments", type="RFC", number="944", pages="1--40", year=1985, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 961", url="https://www.rfc-editor.org/rfc/rfc944.txt", key="RFC 944", abstract={This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-924 and earlier editions. This RFC will be updated periodically, and current information can be obtained from Joyce Reynolds. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.}, doi="10.17487/RFC0944", } @misc{rfc945, author="J. Postel", title="{DoD statement on the NRC report}", howpublished="RFC 945", series="Internet Request for Comments", type="RFC", number="945", pages="1--2", year=1985, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1039", url="https://www.rfc-editor.org/rfc/rfc945.txt", key="RFC 945", abstract={In May 1983 the National Research Council (NRC) was asked jointly by 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.}, doi="10.17487/RFC0945", } @misc{rfc946, author="R. Nedved", title="{Telnet terminal location number option}", howpublished="RFC 946 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="946", pages="1--4", year=1985, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc946.txt", key="RFC 946", 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.}, keywords="TOPT-TLN", doi="10.17487/RFC0946", } @misc{rfc947, author="K. Lebowitz and D. Mankins", title="{Multi-network broadcasting within the Internet}", howpublished="RFC 947", series="Internet Request for Comments", type="RFC", number="947", pages="1--5", year=1985, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc947.txt", key="RFC 947", 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.}, doi="10.17487/RFC0947", } @misc{rfc948, author="I. Winston", title="{Two methods for the transmission of IP datagrams over IEEE 802.3 networks}", howpublished="RFC 948", series="Internet Request for Comments", type="RFC", number="948", pages="1--7", year=1985, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1042", url="https://www.rfc-editor.org/rfc/rfc948.txt", key="RFC 948", abstract={This RFC describes two methods of encapsulating Internet Protocol (IP) datagrams on an IEEE 802.3 network. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.}, doi="10.17487/RFC0948", } @misc{rfc949, author="M.A. Padlipsky", title="{FTP unique-named store command}", howpublished="RFC 949", series="Internet Request for Comments", type="RFC", number="949", pages="1--2", year=1985, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc949.txt", key="RFC 949", 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. See RFC-959.}, doi="10.17487/RFC0949", } @misc{rfc950, author="J.C. Mogul and J. Postel", title="{Internet Standard Subnetting Procedure}", howpublished="RFC 950 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="950", pages="1--18", year=1985, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 6918", url="https://www.rfc-editor.org/rfc/rfc950.txt", key="RFC 950", 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.}, keywords="Address", doi="10.17487/RFC0950", } @misc{rfc951, author="W.J. Croft and J. Gilmore", title="{Bootstrap Protocol}", howpublished="RFC 951 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="951", pages="1--12", year=1985, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 1395, 1497, 1532, 1542, 5494", url="https://www.rfc-editor.org/rfc/rfc951.txt", key="RFC 951", 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.}, keywords="BOOTP", doi="10.17487/RFC0951", } @misc{rfc952, author="K. Harrenstien and M.K. Stahl and E.J. Feinler", title="{DoD Internet host table specification}", howpublished="RFC 952", series="Internet Request for Comments", type="RFC", number="952", pages="1--6", year=1985, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 1123", url="https://www.rfc-editor.org/rfc/rfc952.txt", key="RFC 952", 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.}, doi="10.17487/RFC0952", } @misc{rfc953, author="K. Harrenstien and M.K. Stahl and E.J. Feinler", title="{Hostname Server}", howpublished="RFC 953 (Historic)", series="Internet Request for Comments", type="RFC", number="953", pages="1--5", year=1985, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc953.txt", key="RFC 953", 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.}, keywords="HOSTNAME", doi="10.17487/RFC0953", } @misc{rfc954, author="K. Harrenstien and M.K. Stahl and E.J. Feinler", title="{NICNAME/WHOIS}", howpublished="RFC 954 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="954", pages="1--4", year=1985, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 3912", url="https://www.rfc-editor.org/rfc/rfc954.txt", key="RFC 954", 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.}, keywords="NICNAME", doi="10.17487/RFC0954", } @misc{rfc955, author="R.T. Braden", title="{Towards a transport service for transaction processing applications}", howpublished="RFC 955", series="Internet Request for Comments", type="RFC", number="955", pages="1--10", year=1985, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc955.txt", key="RFC 955", 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. This RFC is concerned with the possible design of one or more new protocols for the ARPA-Internet, to support kinds of applications which are not well supported at present. The RFC is intended to spur discussion in the Internet research community towards the development of new protocols and/or concepts, in order to meet these unmet application requirements. It does not represent a standard, nor even a concrete protocol proposal.}, doi="10.17487/RFC0955", } @misc{rfc956, author="D.L. Mills", title="{Algorithms for synchronizing network clocks}", howpublished="RFC 956", series="Internet Request for Comments", type="RFC", number="956", pages="1--26", year=1985, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc956.txt", key="RFC 956", 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.}, doi="10.17487/RFC0956", } @misc{rfc957, author="D.L. Mills", title="{Experiments in network clock synchronization}", howpublished="RFC 957", series="Internet Request for Comments", type="RFC", number="957", pages="1--27", year=1985, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc957.txt", key="RFC 957", 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.}, doi="10.17487/RFC0957", } @misc{rfc958, author="D.L. Mills", title="{Network Time Protocol (NTP)}", howpublished="RFC 958", series="Internet Request for Comments", type="RFC", number="958", pages="1--14", year=1985, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1059, 1119, 1305", url="https://www.rfc-editor.org/rfc/rfc958.txt", key="RFC 958", 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 is 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.}, keywords="NTP, time, clock, synchronization", doi="10.17487/RFC0958", } @misc{rfc959, author="J. Postel and J. Reynolds", title="{File Transfer Protocol}", howpublished="RFC 959 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="959", pages="1--69", year=1985, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 2228, 2640, 2773, 3659, 5797, 7151", url="https://www.rfc-editor.org/rfc/rfc959.txt", key="RFC 959", 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.}, keywords="FTP", doi="10.17487/RFC0959", } @misc{rfc960, author="J.K. Reynolds and J. Postel", title="{Assigned numbers}", howpublished="RFC 960 (Historic)", series="Internet Request for Comments", type="RFC", number="960", pages="1--60", year=1985, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 990", url="https://www.rfc-editor.org/rfc/rfc960.txt", key="RFC 960", abstract={This memo documents the currently assigned values from several series of numbers used in network protocol implementations. This edition of Assigned Numbers updates and obsoletes RFC-943. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997.}, doi="10.17487/RFC0960", } @misc{rfc961, author="J.K. Reynolds and J. Postel", title="{Official ARPA-Internet protocols}", howpublished="RFC 961", series="Internet Request for Comments", type="RFC", number="961", pages="1--38", year=1985, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 991", url="https://www.rfc-editor.org/rfc/rfc961.txt", key="RFC 961", abstract={This memo identifies the documents specifying the official protocols used in the Internet, and comments on any revisions or changes planned. This edition of the Official Protocols updates and obsoletes RFC-944. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991.}, doi="10.17487/RFC0961", } @misc{rfc962, author="M.A. Padlipsky", title="{TCP-4 prime}", howpublished="RFC 962", series="Internet Request for Comments", type="RFC", number="962", pages="1--2", year=1985, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc962.txt", key="RFC 962", 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.}, doi="10.17487/RFC0962", } @misc{rfc963, author="D.P. Sidhu", title="{Some problems with the specification of the Military Standard Internet Protocol}", howpublished="RFC 963", series="Internet Request for Comments", type="RFC", number="963", pages="1--19", year=1985, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc963.txt", key="RFC 963", 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.}, doi="10.17487/RFC0963", } @misc{rfc964, author="D.P. Sidhu and T. Blumer", title="{Some problems with the specification of the Military Standard Transmission Control Protocol}", howpublished="RFC 964 (Informational)", series="Internet Request for Comments", type="RFC", number="964", pages="1--10", year=1985, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc964.txt", key="RFC 964", 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.}, doi="10.17487/RFC0964", } @misc{rfc965, author="L. Aguilar", title="{Format for a graphical communication protocol}", howpublished="RFC 965", series="Internet Request for Comments", type="RFC", number="965", pages="1--51", year=1985, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc965.txt", key="RFC 965", 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.}, doi="10.17487/RFC0965", } @misc{rfc966, author="S.E. Deering and D.R. Cheriton", title="{Host groups: A multicast extension to the Internet Protocol}", howpublished="RFC 966", series="Internet Request for Comments", type="RFC", number="966", pages="1--27", year=1985, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 988", url="https://www.rfc-editor.org/rfc/rfc966.txt", key="RFC 966", 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. See RFC-988.}, doi="10.17487/RFC0966", } @misc{rfc967, author="M.A. Padlipsky", title="{All victims together}", howpublished="RFC 967", series="Internet Request for Comments", type="RFC", number="967", pages="1--2", year=1985, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc967.txt", key="RFC 967", 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.}, doi="10.17487/RFC0967", } @misc{rfc968, author="V.G. Cerf", title="{Twas the night before start-up}", howpublished="RFC 968", series="Internet Request for Comments", type="RFC", number="968", pages="1--2", year=1985, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc968.txt", key="RFC 968", abstract={This memo discusses problems that arise and debugging techniques used in bringing a new network into operation.}, doi="10.17487/RFC0968", } @misc{rfc969, author="D.D. Clark and M.L. Lambert and L. Zhang", title="{NETBLT: A bulk data transfer protocol}", howpublished="RFC 969", series="Internet Request for Comments", type="RFC", number="969", pages="1--15", year=1985, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 998", url="https://www.rfc-editor.org/rfc/rfc969.txt", key="RFC 969", abstract={This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. 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. See RFC-998.}, doi="10.17487/RFC0969", } @misc{rfc970, author="J. Nagle", title="{On Packet Switches With Infinite Storage}", howpublished="RFC 970", series="Internet Request for Comments", type="RFC", number="970", pages="1--9", year=1985, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc970.txt", key="RFC 970", 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.}, doi="10.17487/RFC0970", } @misc{rfc971, author="A.L. DeSchon", title="{Survey of data representation standards}", howpublished="RFC 971", series="Internet Request for Comments", type="RFC", number="971", pages="1--9", year=1986, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc971.txt", key="RFC 971", 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.}, doi="10.17487/RFC0971", } @misc{rfc972, author="F.J. Wancho", title="{Password Generator Protocol}", howpublished="RFC 972", series="Internet Request for Comments", type="RFC", number="972", pages="1--2", year=1986, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc972.txt", key="RFC 972", 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.}, doi="10.17487/RFC0972", } @misc{rfc973, author="P.V. Mockapetris", title="{Domain system changes and observations}", howpublished="RFC 973", series="Internet Request for Comments", type="RFC", number="973", pages="1--10", year=1986, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1034, 1035", url="https://www.rfc-editor.org/rfc/rfc973.txt", key="RFC 973", 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.}, doi="10.17487/RFC0973", } @misc{rfc974, author="C. Partridge", title="{Mail routing and the domain system}", howpublished="RFC 974 (Historic)", series="Internet Request for Comments", type="RFC", number="974", pages="1--7", year=1986, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2821", url="https://www.rfc-editor.org/rfc/rfc974.txt", key="RFC 974", 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.}, keywords="DNS-MX", doi="10.17487/RFC0974", } @misc{rfc975, author="D.L. Mills", title="{Autonomous confederations}", howpublished="RFC 975", series="Internet Request for Comments", type="RFC", number="975", pages="1--10", year=1986, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc975.txt", key="RFC 975", 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.}, doi="10.17487/RFC0975", } @misc{rfc976, author="M.R. Horton", title="{UUCP mail interchange format standard}", howpublished="RFC 976", series="Internet Request for Comments", type="RFC", number="976", pages="1--12", year=1986, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 1137", url="https://www.rfc-editor.org/rfc/rfc976.txt", key="RFC 976", 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.}, doi="10.17487/RFC0976", } @misc{rfc977, author="B. Kantor and P. Lapsley", title="{Network News Transfer Protocol}", howpublished="RFC 977 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="977", pages="1--27", year=1986, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 3977", url="https://www.rfc-editor.org/rfc/rfc977.txt", key="RFC 977", 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.}, keywords="NNTP]", doi="10.17487/RFC0977", } @misc{rfc978, author="J.K. Reynolds and R. Gillman and W.A. Brackenridge and A. Witkowski and J. Postel", title="{Voice File Interchange Protocol (VFIP)}", howpublished="RFC 978", series="Internet Request for Comments", type="RFC", number="978", pages="1--5", year=1986, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc978.txt", key="RFC 978", 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.}, doi="10.17487/RFC0978", } @misc{rfc979, author="A.G. Malis", title="{PSN End-to-End functional specification}", howpublished="RFC 979", series="Internet Request for Comments", type="RFC", number="979", pages="1--15", year=1986, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc979.txt", key="RFC 979", abstract={This memo is an updated version of BBN Report 5775, ``End-to-End Functional Specification and describes important changes to the functionality of the interface between a Host and the PSN, 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 EE, to improve its performance and overall throughput, and to better equip the Packet Switch Node (PSN, also known as the IMP) to support its current and anticipated host population.}, doi="10.17487/RFC0979", } @misc{rfc980, author="O.J. Jacobsen and J. Postel", title="{Protocol document order information}", howpublished="RFC 980", series="Internet Request for Comments", type="RFC", number="980", pages="1--12", year=1986, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc980.txt", key="RFC 980", 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).}, doi="10.17487/RFC0980", } @misc{rfc981, author="D.L. Mills", title="{Experimental multiple-path routing algorithm}", howpublished="RFC 981", series="Internet Request for Comments", type="RFC", number="981", pages="1--22", year=1986, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc981.txt", key="RFC 981", 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.}, doi="10.17487/RFC0981", } @misc{rfc982, author="H.W. Braun", title="{Guidelines for the specification of the structure of the Domain Specific Part (DSP) of the ISO standard NSAP address}", howpublished="RFC 982", series="Internet Request for Comments", type="RFC", number="982", pages="1--11", year=1986, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc982.txt", key="RFC 982", 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.}, doi="10.17487/RFC0982", } @misc{rfc983, author="D.E. Cass and M.T. Rose", title="{ISO transport arrives on top of the TCP}", howpublished="RFC 983", series="Internet Request for Comments", type="RFC", number="983", pages="1--27", year=1986, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1006", url="https://www.rfc-editor.org/rfc/rfc983.txt", key="RFC 983", 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 in 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 in 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.}, doi="10.17487/RFC0983", } @misc{rfc984, author="D.D. Clark and M.L. Lambert", title="{PCMAIL: A distributed mail system for personal computers}", howpublished="RFC 984", series="Internet Request for Comments", type="RFC", number="984", pages="1--31", year=1986, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 993", url="https://www.rfc-editor.org/rfc/rfc984.txt", key="RFC 984", 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. See RFC-993.}, doi="10.17487/RFC0984", } @misc{rfc985, author="National Science Foundation and Network Technical Advisory Group", title="{Requirements for Internet gateways - draft}", howpublished="RFC 985", series="Internet Request for Comments", type="RFC", number="985", pages="1--23", year=1986, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1009", url="https://www.rfc-editor.org/rfc/rfc985.txt", key="RFC 985", abstract={This RFC summarizes the requirements for gateways to be used on networks supporting the DARPA Internet protocols. While it applies specifically to 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.}, keywords="Requirements, Internet, gateways", doi="10.17487/RFC0985", } @misc{rfc986, author="R.W. Callon and H.W. Braun", title="{Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol}", howpublished="RFC 986", series="Internet Request for Comments", type="RFC", number="986", pages="1--7", year=1986, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1069", url="https://www.rfc-editor.org/rfc/rfc986.txt", key="RFC 986", 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.}, doi="10.17487/RFC0986", } @misc{rfc987, author="S.E. Kille", title="{Mapping between X.400 and RFC 822}", howpublished="RFC 987", series="Internet Request for Comments", type="RFC", number="987", pages="1--69", year=1986, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 2156, 1327, updated by RFCs 1026, 1138, 1148", url="https://www.rfc-editor.org/rfc/rfc987.txt", key="RFC 987", abstract={The X.400 series 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.}, doi="10.17487/RFC0987", } @misc{rfc988, author="S.E. Deering", title="{Host extensions for IP multicasting}", howpublished="RFC 988", series="Internet Request for Comments", type="RFC", number="988", pages="1--20", year=1986, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1054, 1112", url="https://www.rfc-editor.org/rfc/rfc988.txt", key="RFC 988", 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.}, keywords="multicast, Internet", doi="10.17487/RFC0988", } @misc{rfc989, author="J. Linn", title="{Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures}", howpublished="RFC 989", series="Internet Request for Comments", type="RFC", number="989", pages="1--23", year=1987, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1040, 1113", url="https://www.rfc-editor.org/rfc/rfc989.txt", key="RFC 989", 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.}, doi="10.17487/RFC0989", } @misc{rfc990, author="J.K. Reynolds and J. Postel", title="{Assigned numbers}", howpublished="RFC 990 (Historic)", series="Internet Request for Comments", type="RFC", number="990", pages="1--75", year=1986, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1010, updated by RFC 997", url="https://www.rfc-editor.org/rfc/rfc990.txt", key="RFC 990", 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. See RFC-997. Obsoletes RFC-960, 943, 923 and 900.}, doi="10.17487/RFC0990", } @misc{rfc991, author="J.K. Reynolds and J. Postel", title="{Official ARPA-Internet protocols}", howpublished="RFC 991", series="Internet Request for Comments", type="RFC", number="991", pages="1--46", year=1986, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1011", url="https://www.rfc-editor.org/rfc/rfc991.txt", key="RFC 991", 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. Obsoletes RFC-961, 944 and 924.}, doi="10.17487/RFC0991", } @misc{rfc992, author="K.P. Birman and T.A. Joseph", title="{On communication support for fault tolerant process groups}", howpublished="RFC 992", series="Internet Request for Comments", type="RFC", number="992", pages="1--18", year=1986, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc992.txt", key="RFC 992", 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.}, doi="10.17487/RFC0992", } @misc{rfc993, author="D.D. Clark and M.L. Lambert", title="{PCMAIL: A distributed mail system for personal computers}", howpublished="RFC 993", series="Internet Request for Comments", type="RFC", number="993", pages="1--28", year=1986, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1056", url="https://www.rfc-editor.org/rfc/rfc993.txt", key="RFC 993", abstract={This document is a discussion of the Pcmail workstation-based distributed mail system. It is a revision of the design published in NIC RFC-984. The revision is based on discussion and comment fromm a variety of sources, as well as further research into the design of interactive Pcmail clients and the use of client code on machines other than IBM PCs. As this design may change, implementation of this document is not advised. Obsoletes RFC-984.}, doi="10.17487/RFC0993", } @misc{rfc994, author="International Organization for Standardization", title="{Final text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service}", howpublished="RFC 994", series="Internet Request for Comments", type="RFC", number="994", pages="1--52", year=1986, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc994.txt", key="RFC 994", 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).}, doi="10.17487/RFC0994", } @misc{rfc995, author="International Organization for Standardization", title="{End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473}", howpublished="RFC 995", series="Internet Request for Comments", type="RFC", number="995", pages="1--41", year=1986, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc995.txt", key="RFC 995", 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.}, doi="10.17487/RFC0995", } @misc{rfc996, author="D.L. Mills", title="{Statistics server}", howpublished="RFC 996 (Historic)", series="Internet Request for Comments", type="RFC", number="996", pages="1--3", year=1987, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc996.txt", key="RFC 996", 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.}, keywords="STATSRV", doi="10.17487/RFC0996", } @misc{rfc997, author="J.K. Reynolds and J. Postel", title="{Internet numbers}", howpublished="RFC 997", series="Internet Request for Comments", type="RFC", number="997", pages="1--42", year=1987, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1020, 1117", url="https://www.rfc-editor.org/rfc/rfc997.txt", key="RFC 997", 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. Obsoletes RFC-990, 960, 943, 923 and 900.}, doi="10.17487/RFC0997", } @misc{rfc998, author="D.D. Clark and M.L. Lambert and L. Zhang", title="{NETBLT: A bulk data transfer protocol}", howpublished="RFC 998 (Experimental)", series="Internet Request for Comments", type="RFC", number="998", pages="1--21", year=1987, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc998.txt", key="RFC 998", 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. Obsoletes RFC-969.}, keywords="NETBLT", doi="10.17487/RFC0998", } @misc{rfc999, author="A. Westine and J. Postel", title="{Requests For Comments summary notes: 900-999}", howpublished="RFC 999", series="Internet Request for Comments", type="RFC", number="999", pages="1--22", year=1987, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1000", url="https://www.rfc-editor.org/rfc/rfc999.txt", key="RFC 999", doi="10.17487/RFC0999", } @misc{rfc1000, author="J.K. Reynolds and J. Postel", title="{Request For Comments reference guide}", howpublished="RFC 1000", series="Internet Request for Comments", type="RFC", number="1000", pages="1--149", year=1987, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1000.txt", key="RFC 1000", 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.}, doi="10.17487/RFC1000", } @misc{rfc1001, author="NetBIOS Working Group in the Defense Advanced Research Projects Agency and Internet Activities Board and End-to-End Services Task Force", title="{Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods}", howpublished="RFC 1001 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1001", pages="1--68", year=1987, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1001.txt", key="RFC 1001", 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''.}, keywords="NETBIOS", doi="10.17487/RFC1001", } @misc{rfc1002, author="NetBIOS Working Group in the Defense Advanced Research Projects Agency and Internet Activities Board and End-to-End Services Task Force", title="{Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications}", howpublished="RFC 1002 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1002", pages="1--84", year=1987, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1002.txt", key="RFC 1002", 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''.}, keywords="NETBIOS", doi="10.17487/RFC1002", } @misc{rfc1003, author="A.R. Katz", title="{Issues in defining an equations representation standard}", howpublished="RFC 1003", series="Internet Request for Comments", type="RFC", number="1003", pages="1--7", year=1987, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1003.txt", key="RFC 1003", 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.}, doi="10.17487/RFC1003", } @misc{rfc1004, author="D.L. Mills", title="{Distributed-protocol authentication scheme}", howpublished="RFC 1004 (Experimental)", series="Internet Request for Comments", type="RFC", number="1004", pages="1--8", year=1987, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1004.txt", key="RFC 1004", 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.}, keywords="COOKIE-JAR", doi="10.17487/RFC1004", } @misc{rfc1005, author="A. Khanna and A.G. Malis", title="{ARPANET AHIP-E Host Access Protocol (enhanced AHIP)}", howpublished="RFC 1005", series="Internet Request for Comments", type="RFC", number="1005", pages="1--34", year=1987, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1005.txt", key="RFC 1005", 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.}, doi="10.17487/RFC1005", } @misc{rfc1006, author="M.T. Rose and D.E. Cass", title="{ISO Transport Service on top of the TCP Version: 3}", howpublished="RFC 1006 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1006", pages="1--19", year=1987, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 2126", url="https://www.rfc-editor.org/rfc/rfc1006.txt", key="RFC 1006", 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.}, keywords="TP-TCP", doi="10.17487/RFC1006", } @misc{rfc1007, author="W. McCoy", title="{Military supplement to the ISO Transport Protocol}", howpublished="RFC 1007", series="Internet Request for Comments", type="RFC", number="1007", pages="1--23", year=1987, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1007.txt", key="RFC 1007", 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.}, doi="10.17487/RFC1007", } @misc{rfc1008, author="W. McCoy", title="{Implementation guide for the ISO Transport Protocol}", howpublished="RFC 1008", series="Internet Request for Comments", type="RFC", number="1008", pages="1--73", year=1987, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1008.txt", key="RFC 1008", 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.}, doi="10.17487/RFC1008", } @misc{rfc1009, author="R.T. Braden and J. Postel", title="{Requirements for Internet gateways}", howpublished="RFC 1009 (Historic)", series="Internet Request for Comments", type="RFC", number="1009", pages="1--54", year=1987, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1812", url="https://www.rfc-editor.org/rfc/rfc1009.txt", key="RFC 1009", 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.}, keywords="", doi="10.17487/RFC1009", } @misc{rfc1010, author="J.K. Reynolds and J. Postel", title="{Assigned numbers}", howpublished="RFC 1010 (Historic)", series="Internet Request for Comments", type="RFC", number="1010", pages="1--44", year=1987, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1060", url="https://www.rfc-editor.org/rfc/rfc1010.txt", key="RFC 1010", 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.}, doi="10.17487/RFC1010", } @misc{rfc1011, author="J.K. Reynolds and J. Postel", title="{Official Internet protocols}", howpublished="RFC 1011", series="Internet Request for Comments", type="RFC", number="1011", pages="1--52", year=1987, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 6093", url="https://www.rfc-editor.org/rfc/rfc1011.txt", key="RFC 1011", 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.}, doi="10.17487/RFC1011", } @misc{rfc1012, author="J.K. Reynolds and J. Postel", title="{Bibliography of Request For Comments 1 through 999}", howpublished="RFC 1012 (Informational)", series="Internet Request for Comments", type="RFC", number="1012", pages="1--64", year=1987, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1012.txt", key="RFC 1012", 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.}, doi="10.17487/RFC1012", } @misc{rfc1013, author="R.W. Scheifler", title="{X Window System Protocol, version 11: Alpha update April 1987}", howpublished="RFC 1013", series="Internet Request for Comments", type="RFC", number="1013", pages="1--101", year=1987, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1013.txt", key="RFC 1013", 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.}, doi="10.17487/RFC1013", } @misc{rfc1014, author="Sun Microsystems", title="{XDR: External Data Representation standard}", howpublished="RFC 1014", series="Internet Request for Comments", type="RFC", number="1014", pages="1--20", year=1987, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1014.txt", key="RFC 1014", 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.}, doi="10.17487/RFC1014", } @misc{rfc1015, author="B.M. Leiner", title="{Implementation plan for interagency research Internet}", howpublished="RFC 1015", series="Internet Request for Comments", type="RFC", number="1015", pages="1--24", year=1987, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1015.txt", key="RFC 1015", 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.}, doi="10.17487/RFC1015", } @misc{rfc1016, author="W. Prue and J. Postel", title="{Something a Host Could Do with Source Quench: The Source Quench Introduced Delay (SQuID)}", howpublished="RFC 1016", series="Internet Request for Comments", type="RFC", number="1016", pages="1--18", year=1987, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1016.txt", key="RFC 1016", 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.}, doi="10.17487/RFC1016", } @misc{rfc1017, author="B.M. Leiner", title="{Network requirements for scientific research: Internet task force on scientific computing}", howpublished="RFC 1017", series="Internet Request for Comments", type="RFC", number="1017", pages="1--19", year=1987, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1017.txt", key="RFC 1017", 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.}, doi="10.17487/RFC1017", } @misc{rfc1018, author="A.M. McKenzie", title="{Some comments on SQuID}", howpublished="RFC 1018", series="Internet Request for Comments", type="RFC", number="1018", pages="1--3", year=1987, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1018.txt", key="RFC 1018", 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. Distribution of this memo is unlimited.}, doi="10.17487/RFC1018", } @misc{rfc1019, author="D. Arnon", title="{Report of the Workshop on Environments for Computational Mathematics}", howpublished="RFC 1019", series="Internet Request for Comments", type="RFC", number="1019", pages="1--8", year=1987, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1019.txt", key="RFC 1019", 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.}, doi="10.17487/RFC1019", } @misc{rfc1020, author="S. Romano and M.K. Stahl", title="{Internet numbers}", howpublished="RFC 1020", series="Internet Request for Comments", type="RFC", number="1020", pages="1--51", year=1987, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1062, 1117, 1166", url="https://www.rfc-editor.org/rfc/rfc1020.txt", key="RFC 1020", abstract={This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous System Numbers. This RFC obsoletes RFC-997.}, doi="10.17487/RFC1020", } @misc{rfc1021, author="C. Partridge and G. Trewitt", title="{High-level Entity Management System (HEMS)}", howpublished="RFC 1021 (Historic)", series="Internet Request for Comments", type="RFC", number="1021", pages="1--5", year=1987, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1021.txt", key="RFC 1021", 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.}, keywords="HEMS", doi="10.17487/RFC1021", } @misc{rfc1022, author="C. Partridge and G. Trewitt", title="{High-level Entity Management Protocol (HEMP)}", howpublished="RFC 1022", series="Internet Request for Comments", type="RFC", number="1022", pages="1--12", year=1987, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1022.txt", key="RFC 1022", 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.}, doi="10.17487/RFC1022", } @misc{rfc1023, author="G. Trewitt and C. Partridge", title="{HEMS monitoring and control language}", howpublished="RFC 1023", series="Internet Request for Comments", type="RFC", number="1023", pages="1--17", year=1987, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1076", url="https://www.rfc-editor.org/rfc/rfc1023.txt", key="RFC 1023", 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.}, doi="10.17487/RFC1023", } @misc{rfc1024, author="C. Partridge and G. Trewitt", title="{HEMS variable definitions}", howpublished="RFC 1024", series="Internet Request for Comments", type="RFC", number="1024", pages="1--74", year=1987, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1024.txt", key="RFC 1024", 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.}, doi="10.17487/RFC1024", } @misc{rfc1025, author="J. Postel", title="{TCP and IP bake off}", howpublished="RFC 1025", series="Internet Request for Comments", type="RFC", number="1025", pages="1--6", year=1987, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1025.txt", key="RFC 1025", 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.}, doi="10.17487/RFC1025", } @misc{rfc1026, author="S.E. Kille", title="{Addendum to RFC 987: (Mapping between X.400 and RFC-822)}", howpublished="RFC 1026", series="Internet Request for Comments", type="RFC", number="1026", pages="1--4", year=1987, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 2156, 1327, updated by RFCs 1138, 1148", url="https://www.rfc-editor.org/rfc/rfc1026.txt", key="RFC 1026", abstract={This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements.}, doi="10.17487/RFC1026", } @misc{rfc1027, author="S. Carl-Mitchell and J.S. Quarterman", title="{Using ARP to implement transparent subnet gateways}", howpublished="RFC 1027", series="Internet Request for Comments", type="RFC", number="1027", pages="1--8", year=1987, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1027.txt", key="RFC 1027", 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''.}, doi="10.17487/RFC1027", } @misc{rfc1028, author="J. Davin and J.D. Case and M. Fedor and M.L. Schoffstall", title="{Simple Gateway Monitoring Protocol}", howpublished="RFC 1028 (Historic)", series="Internet Request for Comments", type="RFC", number="1028", pages="1--35", year=1987, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1028.txt", key="RFC 1028", 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.}, keywords="SGMP", doi="10.17487/RFC1028", } @misc{rfc1029, author="G. Parr", title="{More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets}", howpublished="RFC 1029", series="Internet Request for Comments", type="RFC", number="1029", pages="1--17", year=1988, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1029.txt", key="RFC 1029", 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.}, keywords="arp", doi="10.17487/RFC1029", } @misc{rfc1030, author="M.L. Lambert", title="{On testing the NETBLT Protocol over divers networks}", howpublished="RFC 1030", series="Internet Request for Comments", type="RFC", number="1030", pages="1--16", year=1987, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1030.txt", key="RFC 1030", 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.}, doi="10.17487/RFC1030", } @misc{rfc1031, author="W.D. Lazear", title="{MILNET name domain transition}", howpublished="RFC 1031", series="Internet Request for Comments", type="RFC", number="1031", pages="1--10", year=1987, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1031.txt", key="RFC 1031", 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.}, doi="10.17487/RFC1031", } @misc{rfc1032, author="M.K. Stahl", title="{Domain administrators guide}", howpublished="RFC 1032", series="Internet Request for Comments", type="RFC", number="1032", pages="1--14", year=1987, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1032.txt", key="RFC 1032", 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.}, doi="10.17487/RFC1032", } @misc{rfc1033, author="M. Lottor", title="{Domain Administrators Operations Guide}", howpublished="RFC 1033", series="Internet Request for Comments", type="RFC", number="1033", pages="1--22", year=1987, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1033.txt", key="RFC 1033", 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).}, doi="10.17487/RFC1033", } @misc{rfc1034, author="P.V. Mockapetris", title="{Domain names - concepts and facilities}", howpublished="RFC 1034 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1034", pages="1--55", year=1987, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 1101, 1183, 1348, 1876, 1982, 2065, 2181, 2308, 2535, 4033, 4034, 4035, 4343, 4035, 4592, 5936, 8020", url="https://www.rfc-editor.org/rfc/rfc1034.txt", key="RFC 1034", 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.}, keywords="DOMAIN", doi="10.17487/RFC1034", } @misc{rfc1035, author="P.V. Mockapetris", title="{Domain names - implementation and specification}", howpublished="RFC 1035 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1035", pages="1--55", year=1987, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 1101, 1183, 1348, 1876, 1982, 1995, 1996, 2065, 2136, 2181, 2137, 2308, 2535, 2673, 2845, 3425, 3658, 4033, 4034, 4035, 4343, 5936, 5966, 6604, 7766", url="https://www.rfc-editor.org/rfc/rfc1035.txt", key="RFC 1035", 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.}, keywords="DOMAIN, DNS", doi="10.17487/RFC1035", } @misc{rfc1036, author="M.R. Horton and R. Adams", title="{Standard for interchange of USENET messages}", howpublished="RFC 1036", series="Internet Request for Comments", type="RFC", number="1036", pages="1--19", year=1987, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 5536, 5537", url="https://www.rfc-editor.org/rfc/rfc1036.txt", key="RFC 1036", 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.}, doi="10.17487/RFC1036", } @misc{rfc1037, author="B. Greenberg and S. Keene", title="{NFILE - a file access protocol}", howpublished="RFC 1037 (Historic)", series="Internet Request for Comments", type="RFC", number="1037", pages="1--86", year=1987, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1037.txt", key="RFC 1037", 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.}, keywords="NFILE", doi="10.17487/RFC1037", } @misc{rfc1038, author="M. St. Johns", title="{Draft revised IP security option}", howpublished="RFC 1038", series="Internet Request for Comments", type="RFC", number="1038", pages="1--7", year=1988, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1108", url="https://www.rfc-editor.org/rfc/rfc1038.txt", key="RFC 1038", 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''.}, doi="10.17487/RFC1038", } @misc{rfc1039, author="D. Latham", title="{DoD statement on Open Systems Interconnection protocols}", howpublished="RFC 1039", series="Internet Request for Comments", type="RFC", number="1039", pages="1--3", year=1988, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1039.txt", key="RFC 1039", 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.}, doi="10.17487/RFC1039", } @misc{rfc1040, author="J. Linn", title="{Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures}", howpublished="RFC 1040", series="Internet Request for Comments", type="RFC", number="1040", pages="1--29", year=1988, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1113", url="https://www.rfc-editor.org/rfc/rfc1040.txt", key="RFC 1040", 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.}, doi="10.17487/RFC1040", } @misc{rfc1041, author="Y. Rekhter", title="{Telnet 3270 regime option}", howpublished="RFC 1041 (Historic)", series="Internet Request for Comments", type="RFC", number="1041", pages="1--6", year=1988, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 6270", url="https://www.rfc-editor.org/rfc/rfc1041.txt", key="RFC 1041", 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.}, keywords="TOPT-3270", doi="10.17487/RFC1041", } @misc{rfc1042, author="J. Postel and J.K. Reynolds", title="{Standard for the transmission of IP datagrams over IEEE 802 networks}", howpublished="RFC 1042 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1042", pages="1--15", year=1988, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1042.txt", key="RFC 1042", 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.}, keywords="IP-IEEE", doi="10.17487/RFC1042", } @misc{rfc1043, author="A. Yasuda and T. Thompson", title="{Telnet Data Entry Terminal option: DODIIS implementation}", howpublished="RFC 1043 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1043", pages="1--26", year=1988, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1043.txt", key="RFC 1043", 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.}, keywords="TOPT-DATA", doi="10.17487/RFC1043", } @misc{rfc1044, author="K. Hardwick and J. Lekashman", title="{Internet Protocol on Network System's HYPERchannel: Protocol Specification}", howpublished="RFC 1044 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1044", pages="1--43", year=1988, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 5494", url="https://www.rfc-editor.org/rfc/rfc1044.txt", key="RFC 1044", 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.}, keywords="IP-HC", doi="10.17487/RFC1044", } @misc{rfc1045, author="D.R. Cheriton", title="{VMTP: Versatile Message Transaction Protocol: Protocol specification}", howpublished="RFC 1045 (Experimental)", series="Internet Request for Comments", type="RFC", number="1045", pages="1--128", year=1988, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1045.txt", key="RFC 1045", 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.}, keywords="VMTP", doi="10.17487/RFC1045", } @misc{rfc1046, author="W. Prue and J. Postel", title="{Queuing algorithm to provide type-of-service for IP links}", howpublished="RFC 1046", series="Internet Request for Comments", type="RFC", number="1046", pages="1--11", year=1988, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1046.txt", key="RFC 1046", 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.}, doi="10.17487/RFC1046", } @misc{rfc1047, author="C. Partridge", title="{Duplicate messages and SMTP}", howpublished="RFC 1047", series="Internet Request for Comments", type="RFC", number="1047", pages="1--3", year=1988, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1047.txt", key="RFC 1047", 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.}, doi="10.17487/RFC1047", } @misc{rfc1048, author="P.A. Prindeville", title="{BOOTP vendor information extensions}", howpublished="RFC 1048", series="Internet Request for Comments", type="RFC", number="1048", pages="1--7", year=1988, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1084, 1395, 1497, 1533", url="https://www.rfc-editor.org/rfc/rfc1048.txt", key="RFC 1048", abstract={This memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought.}, doi="10.17487/RFC1048", } @misc{rfc1049, author="M.A. Sirbu", title="{Content-type header field for Internet messages}", howpublished="RFC 1049 (Historic)", series="Internet Request for Comments", type="RFC", number="1049", pages="1--8", year=1988, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1049.txt", key="RFC 1049", abstract={This memo suggests proposed additions to the Internet Mail Protocol, RFC-822, for the Internet community, and requests discussion and suggestions for improvements.}, keywords="CONTENT", doi="10.17487/RFC1049", } @misc{rfc1050, author="Sun Microsystems", title="{RPC: Remote Procedure Call Protocol specification}", howpublished="RFC 1050 (Historic)", series="Internet Request for Comments", type="RFC", number="1050", pages="1--24", year=1988, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1057", url="https://www.rfc-editor.org/rfc/rfc1050.txt", key="RFC 1050", 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.}, keywords="SUN-RPC", doi="10.17487/RFC1050", } @misc{rfc1051, author="P.A. Prindeville", title="{Standard for the transmission of IP datagrams and ARP packets over ARCNET networks}", howpublished="RFC 1051 (Historic)", series="Internet Request for Comments", type="RFC", number="1051", pages="1--4", year=1988, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1201", url="https://www.rfc-editor.org/rfc/rfc1051.txt", key="RFC 1051", 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.}, keywords="", doi="10.17487/RFC1051", } @misc{rfc1052, author="V.G. Cerf", title="{IAB recommendations for the development of Internet network management standards}", howpublished="RFC 1052", series="Internet Request for Comments", type="RFC", number="1052", pages="1--14", year=1988, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1052.txt", key="RFC 1052", 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.}, doi="10.17487/RFC1052", } @misc{rfc1053, author="S. Levy and T. Jacobson", title="{Telnet X.3 PAD option}", howpublished="RFC 1053 (Historic)", series="Internet Request for Comments", type="RFC", number="1053", pages="1--21", year=1988, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1053.txt", key="RFC 1053", abstract={This RFC proposes a new option to Telnet for the Internet community, and requests discussion and suggestions for improvements.}, keywords="TOPT-X.3", doi="10.17487/RFC1053", } @misc{rfc1054, author="S.E. Deering", title="{Host extensions for IP multicasting}", howpublished="RFC 1054", series="Internet Request for Comments", type="RFC", number="1054", pages="1--19", year=1988, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1112", url="https://www.rfc-editor.org/rfc/rfc1054.txt", key="RFC 1054", 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.}, doi="10.17487/RFC1054", } @misc{rfc1055, author="J.L. Romkey", title="{Nonstandard for transmission of IP datagrams over serial lines: SLIP}", howpublished="RFC 1055 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1055", pages="1--6", year=1988, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1055.txt", key="RFC 1055", 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.}, keywords="IP-SLIP", doi="10.17487/RFC1055", } @misc{rfc1056, author="M.L. Lambert", title="{PCMAIL: A distributed mail system for personal computers}", howpublished="RFC 1056 (Informational)", series="Internet Request for Comments", type="RFC", number="1056", pages="1--38", year=1988, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1056.txt", key="RFC 1056", 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.}, keywords="PCMAIL", doi="10.17487/RFC1056", } @misc{rfc1057, author="Sun Microsystems", title="{RPC: Remote Procedure Call Protocol specification: Version 2}", howpublished="RFC 1057 (Informational)", series="Internet Request for Comments", type="RFC", number="1057", pages="1--25", year=1988, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1057.txt", key="RFC 1057", 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.}, keywords="SUN-RPC", doi="10.17487/RFC1057", } @misc{rfc1058, author="C.L. Hedrick", title="{Routing Information Protocol}", howpublished="RFC 1058 (Historic)", series="Internet Request for Comments", type="RFC", number="1058", pages="1--33", year=1988, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 1388, 1723", url="https://www.rfc-editor.org/rfc/rfc1058.txt", key="RFC 1058", 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.}, keywords="RIP", doi="10.17487/RFC1058", } @misc{rfc1059, author="D.L. Mills", title="{Network Time Protocol (version 1) specification and implementation}", howpublished="RFC 1059", series="Internet Request for Comments", type="RFC", number="1059", pages="1--58", year=1988, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1119, 1305", url="https://www.rfc-editor.org/rfc/rfc1059.txt", key="RFC 1059", 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.}, keywords="NTP, NTPv1, time, clock, synchronization", doi="10.17487/RFC1059", } @misc{rfc1060, author="J.K. Reynolds and J. Postel", title="{Assigned numbers}", howpublished="RFC 1060 (Historic)", series="Internet Request for Comments", type="RFC", number="1060", pages="1--86", year=1990, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1340, updated by RFC 1349", url="https://www.rfc-editor.org/rfc/rfc1060.txt", key="RFC 1060", 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.}, doi="10.17487/RFC1060", } @misc{rfc1062, author="S. Romano and M.K. Stahl and M. Recker", title="{Internet numbers}", howpublished="RFC 1062", series="Internet Request for Comments", type="RFC", number="1062", pages="1--65", year=1988, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1117, 1166", url="https://www.rfc-editor.org/rfc/rfc1062.txt", key="RFC 1062", abstract={This memo is an official status report on the network numbers and gateway autonomous system numbers used in the Internet community.}, doi="10.17487/RFC1062", } @misc{rfc1063, author="J.C. Mogul and C.A. Kent and C. Partridge and K. McCloghrie", title="{IP MTU discovery options}", howpublished="RFC 1063", series="Internet Request for Comments", type="RFC", number="1063", pages="1--11", year=1988, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1191", url="https://www.rfc-editor.org/rfc/rfc1063.txt", key="RFC 1063", 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.}, doi="10.17487/RFC1063", } @misc{rfc1064, author="M.R. Crispin", title="{Interactive Mail Access Protocol: Version 2}", howpublished="RFC 1064", series="Internet Request for Comments", type="RFC", number="1064", pages="1--26", year=1988, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1176, 1203", url="https://www.rfc-editor.org/rfc/rfc1064.txt", key="RFC 1064", 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.}, doi="10.17487/RFC1064", } @misc{rfc1065, author="K. McCloghrie and M.T. Rose", title="{Structure and identification of management information for TCP/IP-based internets}", howpublished="RFC 1065 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1065", pages="1--21", year=1988, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1155", url="https://www.rfc-editor.org/rfc/rfc1065.txt", key="RFC 1065", 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.}, doi="10.17487/RFC1065", } @misc{rfc1066, author="K. McCloghrie and M.T. Rose", title="{Management Information Base for network management of TCP/IP-based internets}", howpublished="RFC 1066", series="Internet Request for Comments", type="RFC", number="1066", pages="1--90", year=1988, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1156", url="https://www.rfc-editor.org/rfc/rfc1066.txt", key="RFC 1066", 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.}, doi="10.17487/RFC1066", } @misc{rfc1067, author="J.D. Case and M. Fedor and M.L. Schoffstall and J. Davin", title="{Simple Network Management Protocol}", howpublished="RFC 1067", series="Internet Request for Comments", type="RFC", number="1067", pages="1--33", year=1988, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1098", url="https://www.rfc-editor.org/rfc/rfc1067.txt", key="RFC 1067", 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.}, doi="10.17487/RFC1067", } @misc{rfc1068, author="A.L. DeSchon and R.T. Braden", title="{Background File Transfer Program (BFTP)}", howpublished="RFC 1068", series="Internet Request for Comments", type="RFC", number="1068", pages="1--27", year=1988, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1068.txt", key="RFC 1068", 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.}, keywords="FTP", doi="10.17487/RFC1068", } @misc{rfc1069, author="R.W. Callon and H.W. Braun", title="{Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol}", howpublished="RFC 1069", series="Internet Request for Comments", type="RFC", number="1069", pages="1--10", year=1989, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1069.txt", key="RFC 1069", 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.}, doi="10.17487/RFC1069", } @misc{rfc1070, author="R.A. Hagens and N.E. Hall and M.T. Rose", title="{Use of the Internet as a subnetwork for experimentation with the OSI network layer}", howpublished="RFC 1070", series="Internet Request for Comments", type="RFC", number="1070", pages="1--17", year=1989, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1070.txt", key="RFC 1070", 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.}, doi="10.17487/RFC1070", } @misc{rfc1071, author="R.T. Braden and D.A. Borman and C. Partridge", title="{Computing the Internet checksum}", howpublished="RFC 1071 (Informational)", series="Internet Request for Comments", type="RFC", number="1071", pages="1--24", year=1988, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 1141", url="https://www.rfc-editor.org/rfc/rfc1071.txt", key="RFC 1071", 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.}, doi="10.17487/RFC1071", } @misc{rfc1072, author="V. Jacobson and R.T. Braden", title="{TCP extensions for long-delay paths}", howpublished="RFC 1072 (Historic)", series="Internet Request for Comments", type="RFC", number="1072", pages="1--16", year=1988, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1323, 2018, 6247", url="https://www.rfc-editor.org/rfc/rfc1072.txt", key="RFC 1072", 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.}, doi="10.17487/RFC1072", } @misc{rfc1073, author="D. Waitzman", title="{Telnet window size option}", howpublished="RFC 1073 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1073", pages="1--4", year=1988, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1073.txt", key="RFC 1073", abstract={This RFC describes a proposed Telnet option to allow a client to convey window size to a Telnet server.}, keywords="TOPT-NAWS", doi="10.17487/RFC1073", } @misc{rfc1074, author="J. Rekhter", title="{NSFNET backbone SPF based Interior Gateway Protocol}", howpublished="RFC 1074", series="Internet Request for Comments", type="RFC", number="1074", pages="1--5", year=1988, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1074.txt", key="RFC 1074", abstract={This RFC is an implementation description of the standard ANSI IS-IS and ISO ES-IS routing protocols within the NSFNET backbone network.}, doi="10.17487/RFC1074", } @misc{rfc1075, author="D. Waitzman and C. Partridge and S.E. Deering", title="{Distance Vector Multicast Routing Protocol}", howpublished="RFC 1075 (Experimental)", series="Internet Request for Comments", type="RFC", number="1075", pages="1--24", year=1988, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1075.txt", key="RFC 1075", 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.}, keywords="IP-DVMRP", doi="10.17487/RFC1075", } @misc{rfc1076, author="G. Trewitt and C. Partridge", title="{HEMS monitoring and control language}", howpublished="RFC 1076", series="Internet Request for Comments", type="RFC", number="1076", pages="1--42", year=1988, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1076.txt", key="RFC 1076", 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.}, doi="10.17487/RFC1076", } @misc{rfc1077, author="B.M. Leiner", title="{Critical issues in high bandwidth networking}", howpublished="RFC 1077", series="Internet Request for Comments", type="RFC", number="1077", pages="1--46", year=1988, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1077.txt", key="RFC 1077", 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.}, doi="10.17487/RFC1077", } @misc{rfc1078, author="M. Lottor", title="{TCP port service Multiplexer (TCPMUX)}", howpublished="RFC 1078 (Historic)", series="Internet Request for Comments", type="RFC", number="1078", pages="1--2", year=1988, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 7805", url="https://www.rfc-editor.org/rfc/rfc1078.txt", key="RFC 1078", abstract={This RFC proposes an Internet standard which can be used by future TCP services instead of using 'well-known ports'.}, doi="10.17487/RFC1078", } @misc{rfc1079, author="C.L. Hedrick", title="{Telnet terminal speed option}", howpublished="RFC 1079 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1079", pages="1--3", year=1988, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1079.txt", key="RFC 1079", 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.}, keywords="TOPT-TS", doi="10.17487/RFC1079", } @misc{rfc1080, author="C.L. Hedrick", title="{Telnet remote flow control option}", howpublished="RFC 1080", series="Internet Request for Comments", type="RFC", number="1080", pages="1--4", year=1988, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1372", url="https://www.rfc-editor.org/rfc/rfc1080.txt", key="RFC 1080", 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.}, doi="10.17487/RFC1080", } @misc{rfc1081, author="M.T. Rose", title="{Post Office Protocol: Version 3}", howpublished="RFC 1081", series="Internet Request for Comments", type="RFC", number="1081", pages="1--16", year=1988, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1225", url="https://www.rfc-editor.org/rfc/rfc1081.txt", key="RFC 1081", 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.}, doi="10.17487/RFC1081", } @misc{rfc1082, author="M.T. Rose", title="{Post Office Protocol: Version 3: Extended service offerings}", howpublished="RFC 1082", series="Internet Request for Comments", type="RFC", number="1082", pages="1--11", year=1988, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1082.txt", key="RFC 1082", 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.}, doi="10.17487/RFC1082", } @misc{rfc1083, author="Defense Advanced Research Projects Agency and Internet Activities Board", title="{IAB official protocol standards}", howpublished="RFC 1083 (Historic)", series="Internet Request for Comments", type="RFC", number="1083", pages="1--12", year=1988, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1100", url="https://www.rfc-editor.org/rfc/rfc1083.txt", key="RFC 1083", 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.}, keywords="IAB, official, protocol, standards", doi="10.17487/RFC1083", } @misc{rfc1084, author="J.K. Reynolds", title="{BOOTP vendor information extensions}", howpublished="RFC 1084", series="Internet Request for Comments", type="RFC", number="1084", pages="1--8", year=1988, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1395, 1497, 1533", url="https://www.rfc-editor.org/rfc/rfc1084.txt", key="RFC 1084", abstract={This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville. This memo will be updated as additional tags are are defined. This edition introduces Tag 13 for Boot File Size. Comments and suggestions for improvements are sought.}, doi="10.17487/RFC1084", } @misc{rfc1085, author="M.T. Rose", title="{ISO presentation services on top of TCP/IP based internets}", howpublished="RFC 1085", series="Internet Request for Comments", type="RFC", number="1085", pages="1--32", year=1988, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1085.txt", key="RFC 1085", 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.}, doi="10.17487/RFC1085", } @misc{rfc1086, author="J.P. Onions and M.T. Rose", title="{ISO-TP0 bridge between TCP and X.25}", howpublished="RFC 1086", series="Internet Request for Comments", type="RFC", number="1086", pages="1--9", year=1988, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1086.txt", key="RFC 1086", 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.}, doi="10.17487/RFC1086", } @misc{rfc1087, author="Defense Advanced Research Projects Agency and Internet Activities Board", title="{Ethics and the Internet}", howpublished="RFC 1087", series="Internet Request for Comments", type="RFC", number="1087", pages="1--2", year=1989, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1087.txt", key="RFC 1087", abstract={This memo is a statement of policy by the Internet Activities Board (IAB) concerning the proper use of the resources of the Internet.}, keywords="Ethics, Internet", doi="10.17487/RFC1087", } @misc{rfc1088, author="L.J. McLaughlin", title="{Standard for the transmission of IP datagrams over NetBIOS networks}", howpublished="RFC 1088 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1088", pages="1--3", year=1989, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1088.txt", key="RFC 1088", abstract={This document specifies a standard method of encapsulating the Internet Protocol (IP) datagrams on NetBIOS networks.}, keywords="IP-NETBIOS", doi="10.17487/RFC1088", } @misc{rfc1089, author="M. Schoffstall and C. Davin and M. Fedor and J. Case", title="{SNMP over Ethernet}", howpublished="RFC 1089", series="Internet Request for Comments", type="RFC", number="1089", pages="1--3", year=1989, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 4789", url="https://www.rfc-editor.org/rfc/rfc1089.txt", key="RFC 1089", 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.}, doi="10.17487/RFC1089", } @misc{rfc1090, author="R. Ullmann", title="{SMTP on X.25}", howpublished="RFC 1090", series="Internet Request for Comments", type="RFC", number="1090", pages="1--4", year=1989, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1090.txt", key="RFC 1090", abstract={This memo proposes a standard for SMTP on the virtual circuit facility provided by the X.25 standard of the CCITT.}, doi="10.17487/RFC1090", } @misc{rfc1091, author="J. VanBokkelen", title="{Telnet terminal-type option}", howpublished="RFC 1091 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1091", pages="1--7", year=1989, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1091.txt", key="RFC 1091", 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}, keywords="TOPT-TERM", doi="10.17487/RFC1091", } @misc{rfc1092, author="J. Rekhter", title="{EGP and policy based routing in the new NSFNET backbone}", howpublished="RFC 1092", series="Internet Request for Comments", type="RFC", number="1092", pages="1--5", year=1989, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1092.txt", key="RFC 1092", 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.}, doi="10.17487/RFC1092", } @misc{rfc1093, author="H.W. Braun", title="{NSFNET routing architecture}", howpublished="RFC 1093", series="Internet Request for Comments", type="RFC", number="1093", pages="1--9", year=1989, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1093.txt", key="RFC 1093", 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.}, doi="10.17487/RFC1093", } @misc{rfc1094, author="B. Nowicki", title="{NFS: Network File System Protocol specification}", howpublished="RFC 1094 (Informational)", series="Internet Request for Comments", type="RFC", number="1094", pages="1--27", year=1989, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1094.txt", key="RFC 1094", 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.}, keywords="SUN-NFS", doi="10.17487/RFC1094", } @misc{rfc1095, author="U.S. Warrier and L. Besaw", title="{Common Management Information Services and Protocol over TCP/IP (CMOT)}", howpublished="RFC 1095", series="Internet Request for Comments", type="RFC", number="1095", pages="1--67", year=1989, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1189", url="https://www.rfc-editor.org/rfc/rfc1095.txt", key="RFC 1095", 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.}, doi="10.17487/RFC1095", } @misc{rfc1096, author="G.A. Marcy", title="{Telnet X display location option}", howpublished="RFC 1096 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1096", pages="1--3", year=1989, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1096.txt", key="RFC 1096", 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.}, keywords="TOPT-XDL", doi="10.17487/RFC1096", } @misc{rfc1097, author="B. Miller", title="{Telnet subliminal-message option}", howpublished="RFC 1097", series="Internet Request for Comments", type="RFC", number="1097", pages="1--3", year=1989, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1097.txt", key="RFC 1097", 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.}, doi="10.17487/RFC1097", } @misc{rfc1098, author="J.D. Case and M. Fedor and M.L. Schoffstall and J. Davin", title="{Simple Network Management Protocol (SNMP)}", howpublished="RFC 1098", series="Internet Request for Comments", type="RFC", number="1098", pages="1--34", year=1989, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1157", url="https://www.rfc-editor.org/rfc/rfc1098.txt", key="RFC 1098", 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.}, doi="10.17487/RFC1098", } @misc{rfc1099, author="J. Reynolds", title="{Request for Comments Summary: RFC Numbers 1000-1099}", howpublished="RFC 1099 (Informational)", series="Internet Request for Comments", type="RFC", number="1099", pages="1--22", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1099.txt", key="RFC 1099", doi="10.17487/RFC1099", } @misc{rfc1100, author="Defense Advanced Research Projects Agency and Internet Activities Board", title="{IAB official protocol standards}", howpublished="RFC 1100 (Historic)", series="Internet Request for Comments", type="RFC", number="1100", pages="1--14", year=1989, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1130", url="https://www.rfc-editor.org/rfc/rfc1100.txt", key="RFC 1100", 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.}, keywords="IAB, official, protocol, standards", doi="10.17487/RFC1100", } @misc{rfc1101, author="P.V. Mockapetris", title="{DNS encoding of network names and other types}", howpublished="RFC 1101", series="Internet Request for Comments", type="RFC", number="1101", pages="1--14", year=1989, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1101.txt", key="RFC 1101", abstract={This RFC proposes two extensions to the Domain Name System: - A specific method for entering and retrieving RRs which map between network names and numbers. - 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.}, doi="10.17487/RFC1101", } @misc{rfc1102, author="D.D. Clark", title="{Policy routing in Internet protocols}", howpublished="RFC 1102", series="Internet Request for Comments", type="RFC", number="1102", pages="1--22", year=1989, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1102.txt", key="RFC 1102", 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.}, doi="10.17487/RFC1102", } @misc{rfc1103, author="D. Katz", title="{Proposed standard for the transmission of IP datagrams over FDDI Networks}", howpublished="RFC 1103", series="Internet Request for Comments", type="RFC", number="1103", pages="1--9", year=1989, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1188", url="https://www.rfc-editor.org/rfc/rfc1103.txt", key="RFC 1103", 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. [STANDARDS-TRACK]}, doi="10.17487/RFC1103", } @misc{rfc1104, author="H.W. Braun", title="{Models of policy based routing}", howpublished="RFC 1104", series="Internet Request for Comments", type="RFC", number="1104", pages="1--10", year=1989, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1104.txt", key="RFC 1104", 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.}, doi="10.17487/RFC1104", } @misc{rfc1105, author="K. Lougheed and Y. Rekhter", title="{Border Gateway Protocol (BGP)}", howpublished="RFC 1105 (Experimental)", series="Internet Request for Comments", type="RFC", number="1105", pages="1--17", year=1989, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1163", url="https://www.rfc-editor.org/rfc/rfc1105.txt", key="RFC 1105", abstract={This RFC outlines a specific approach for the exchange of network reachability information between Autonomous Systems. Updated by RFCs 1163 and 1164. [STANDARDS-TRACK]}, keywords="BGP", doi="10.17487/RFC1105", } @misc{rfc1106, author="R. Fox", title="{TCP big window and NAK options}", howpublished="RFC 1106 (Historic)", series="Internet Request for Comments", type="RFC", number="1106", pages="1--13", year=1989, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 6247", url="https://www.rfc-editor.org/rfc/rfc1106.txt", key="RFC 1106", 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.}, doi="10.17487/RFC1106", } @misc{rfc1107, author="K.R. Sollins", title="{Plan for Internet directory services}", howpublished="RFC 1107 (Informational)", series="Internet Request for Comments", type="RFC", number="1107", pages="1--19", year=1989, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1107.txt", key="RFC 1107", 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.}, doi="10.17487/RFC1107", } @misc{rfc1108, author="S. Kent", title="{U.S. Department of Defense Security Options for the Internet Protocol}", howpublished="RFC 1108 (Historic)", series="Internet Request for Comments", type="RFC", number="1108", pages="1--17", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1108.txt", key="RFC 1108", 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. [STANDARDS-TRACK]}, keywords="IPSO", doi="10.17487/RFC1108", } @misc{rfc1109, author="V.G. Cerf", title="{Report of the second Ad Hoc Network Management Review Group}", howpublished="RFC 1109", series="Internet Request for Comments", type="RFC", number="1109", pages="1--8", year=1989, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1109.txt", key="RFC 1109", 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.}, doi="10.17487/RFC1109", } @misc{rfc1110, author="A.M. McKenzie", title="{Problem with the TCP big window option}", howpublished="RFC 1110 (Historic)", series="Internet Request for Comments", type="RFC", number="1110", pages="1--3", year=1989, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 6247", url="https://www.rfc-editor.org/rfc/rfc1110.txt", key="RFC 1110", abstract={This memo comments on the TCP Big Window option described in RFC 1106.}, doi="10.17487/RFC1110", } @misc{rfc1111, author="J. Postel", title="{Request for comments on Request for Comments: Instructions to RFC authors}", howpublished="RFC 1111 (Informational)", series="Internet Request for Comments", type="RFC", number="1111", pages="1--6", year=1989, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1543, 2223", url="https://www.rfc-editor.org/rfc/rfc1111.txt", key="RFC 1111", abstract={This RFC specifies a standard for the Internet community. Authors of RFCs are expected to adopt and implement this standard.}, doi="10.17487/RFC1111", } @misc{rfc1112, author="S.E. Deering", title="{Host extensions for IP multicasting}", howpublished="RFC 1112 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1112", pages="1--17", year=1989, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 2236", url="https://www.rfc-editor.org/rfc/rfc1112.txt", key="RFC 1112", 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. [STANDARDS-TRACK]}, keywords="IGMP, multicast", doi="10.17487/RFC1112", } @misc{rfc1113, author="J. Linn", title="{Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures}", howpublished="RFC 1113 (Historic)", series="Internet Request for Comments", type="RFC", number="1113", pages="1--34", year=1989, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1421", url="https://www.rfc-editor.org/rfc/rfc1113.txt", key="RFC 1113", abstract={This RFC specifies features for private electronic mail based on encryption technology. [STANDARDS-TRACK]}, keywords="", doi="10.17487/RFC1113", } @misc{rfc1114, author="S.T. Kent and J. Linn", title="{Privacy enhancement for Internet electronic mail: Part II - certificate-based key management}", howpublished="RFC 1114 (Historic)", series="Internet Request for Comments", type="RFC", number="1114", pages="1--25", year=1989, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1422", url="https://www.rfc-editor.org/rfc/rfc1114.txt", key="RFC 1114", abstract={This RFC specifies the key management aspects of Privacy Enhanced Mail. [STANDARDS-TRACK]}, keywords="", doi="10.17487/RFC1114", } @misc{rfc1115, author="J. Linn", title="{Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers}", howpublished="RFC 1115 (Historic)", series="Internet Request for Comments", type="RFC", number="1115", pages="1--8", year=1989, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1423", url="https://www.rfc-editor.org/rfc/rfc1115.txt", key="RFC 1115", 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. [STANDARDS-TRACK]}, keywords="", doi="10.17487/RFC1115", } @misc{rfc1116, author="D.A. Borman", title="{Telnet Linemode option}", howpublished="RFC 1116 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1116", pages="1--21", year=1989, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1184", url="https://www.rfc-editor.org/rfc/rfc1116.txt", key="RFC 1116", abstract={Hosts on the Internet that support Linemode within the Telnet protocol are expected to adopt and implement this protocol. Obsoleted by RFC 1184. [STANDARDS-TRACK]}, doi="10.17487/RFC1116", } @misc{rfc1117, author="S. Romano and M.K. Stahl and M. Recker", title="{Internet numbers}", howpublished="RFC 1117 (Informational)", series="Internet Request for Comments", type="RFC", number="1117", pages="1--109", year=1989, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1166", url="https://www.rfc-editor.org/rfc/rfc1117.txt", key="RFC 1117", abstract={This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community.}, doi="10.17487/RFC1117", } @misc{rfc1118, author="E. Krol", title="{Hitchhikers guide to the Internet}", howpublished="RFC 1118 (Informational)", series="Internet Request for Comments", type="RFC", number="1118", pages="1--24", year=1989, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1118.txt", key="RFC 1118", 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.}, doi="10.17487/RFC1118", } @misc{rfc1119, author="D.L. Mills", title="{Network Time Protocol (version 2) specification and implementation}", howpublished="RFC 1119 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1119", pages="1--1", year=1989, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1305", url="https://www.rfc-editor.org/rfc/rfc1119.txt", key="RFC 1119", 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. [STANDARDS-TRACK]}, keywords="NTP, NTPv2, time, clock, synchronization", doi="10.17487/RFC1119", } @misc{rfc1120, author="V. Cerf", title="{Internet Activities Board}", howpublished="RFC 1120 (Informational)", series="Internet Request for Comments", type="RFC", number="1120", pages="1--11", year=1989, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1160", url="https://www.rfc-editor.org/rfc/rfc1120.txt", key="RFC 1120", 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.}, doi="10.17487/RFC1120", } @misc{rfc1121, author="J. Postel and L. Kleinrock and V.G. Cerf and B. Boehm", title="{Act one - the poems}", howpublished="RFC 1121 (Informational)", series="Internet Request for Comments", type="RFC", number="1121", pages="1--6", year=1989, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1121.txt", key="RFC 1121", 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.}, doi="10.17487/RFC1121", } @misc{rfc1122, author="R. Braden", title="{Requirements for Internet Hosts - Communication Layers}", howpublished="RFC 1122 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1122", pages="1--116", year=1989, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 1349, 4379, 5884, 6093, 6298, 6633, 6864, 8029", url="https://www.rfc-editor.org/rfc/rfc1122.txt", key="RFC 1122", 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. [STANDARDS-TRACK]}, keywords="applicability", doi="10.17487/RFC1122", } @misc{rfc1123, author="R. Braden", title="{Requirements for Internet Hosts - Application and Support}", howpublished="RFC 1123 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1123", pages="1--98", year=1989, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 1349, 2181, 5321, 5966, 7766", url="https://www.rfc-editor.org/rfc/rfc1123.txt", key="RFC 1123", 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. [STANDARDS-TRACK]}, keywords="applicability", doi="10.17487/RFC1123", } @misc{rfc1124, author="B.M. Leiner", title="{Policy issues in interconnecting networks}", howpublished="RFC 1124", series="Internet Request for Comments", type="RFC", number="1124", pages="1--1", year=1989, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1124.txt", key="RFC 1124", 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.}, doi="10.17487/RFC1124", } @misc{rfc1125, author="D. Estrin", title="{Policy requirements for inter Administrative Domain routing}", howpublished="RFC 1125", series="Internet Request for Comments", type="RFC", number="1125", pages="1--21", year=1989, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1125.txt", key="RFC 1125", 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.}, doi="10.17487/RFC1125", } @misc{rfc1126, author="M. Little", title="{Goals and functional requirements for inter-autonomous system routing}", howpublished="RFC 1126", series="Internet Request for Comments", type="RFC", number="1126", pages="1--25", year=1989, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1126.txt", key="RFC 1126", 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.}, doi="10.17487/RFC1126", } @misc{rfc1127, author="R.T. Braden", title="{Perspective on the Host Requirements RFCs}", howpublished="RFC 1127 (Informational)", series="Internet Request for Comments", type="RFC", number="1127", pages="1--20", year=1989, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1127.txt", key="RFC 1127", 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.}, doi="10.17487/RFC1127", } @misc{rfc1128, author="D.L. Mills", title="{Measured performance of the Network Time Protocol in the Internet system}", howpublished="RFC 1128", series="Internet Request for Comments", type="RFC", number="1128", pages="1--1", year=1989, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1128.txt", key="RFC 1128", 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.}, doi="10.17487/RFC1128", } @misc{rfc1129, author="D.L. Mills", title="{Internet Time Synchronization: The Network Time Protocol}", howpublished="RFC 1129 (Informational)", series="Internet Request for Comments", type="RFC", number="1129", pages="1--1", year=1989, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1129.txt", key="RFC 1129", 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.}, keywords="NTP", doi="10.17487/RFC1129", } @misc{rfc1130, author="Defense Advanced Research Projects Agency and Internet Activities Board", title="{IAB official protocol standards}", howpublished="RFC 1130 (Historic)", series="Internet Request for Comments", type="RFC", number="1130", pages="1--17", year=1989, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1140", url="https://www.rfc-editor.org/rfc/rfc1130.txt", key="RFC 1130", abstract={This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB).}, keywords="IAB, official, protocol, standards", doi="10.17487/RFC1130", } @misc{rfc1131, author="J. Moy", title="{OSPF specification}", howpublished="RFC 1131 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1131", pages="1--1", year=1989, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1247", url="https://www.rfc-editor.org/rfc/rfc1131.txt", key="RFC 1131", 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. [STANDARDS-TRACK]}, doi="10.17487/RFC1131", } @misc{rfc1132, author="L.J. McLaughlin", title="{Standard for the transmission of 802.2 packets over IPX networks}", howpublished="RFC 1132 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1132", pages="1--4", year=1989, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1132.txt", key="RFC 1132", 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.}, keywords="IP-IPX", doi="10.17487/RFC1132", } @misc{rfc1133, author="J.Y. Yu and H.W. Braun", title="{Routing between the NSFNET and the DDN}", howpublished="RFC 1133 (Informational)", series="Internet Request for Comments", type="RFC", number="1133", pages="1--10", year=1989, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1133.txt", key="RFC 1133", 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.}, doi="10.17487/RFC1133", } @misc{rfc1134, author="D. Perkins", title="{Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links}", howpublished="RFC 1134 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1134", pages="1--38", year=1989, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1171", url="https://www.rfc-editor.org/rfc/rfc1134.txt", key="RFC 1134", 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. [STANDARDS-TRACK]}, doi="10.17487/RFC1134", } @misc{rfc1135, author="J.K. Reynolds", title="{Helminthiasis of the Internet}", howpublished="RFC 1135 (Informational)", series="Internet Request for Comments", type="RFC", number="1135", pages="1--33", year=1989, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1135.txt", key="RFC 1135", 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.}, doi="10.17487/RFC1135", } @misc{rfc1136, author="S. Hares and D. Katz", title="{Administrative Domains and Routing Domains: A model for routing in the Internet}", howpublished="RFC 1136 (Informational)", series="Internet Request for Comments", type="RFC", number="1136", pages="1--10", year=1989, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1136.txt", key="RFC 1136", 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.}, doi="10.17487/RFC1136", } @misc{rfc1137, author="S. Kille", title="{Mapping between full RFC 822 and RFC 822 with restricted encoding}", howpublished="RFC 1137 (Historic)", series="Internet Request for Comments", type="RFC", number="1137", pages="1--3", year=1989, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1137.txt", key="RFC 1137", 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.}, keywords="", doi="10.17487/RFC1137", } @misc{rfc1138, author="S.E. Kille", title="{Mapping between X.400(1988) / ISO 10021 and RFC 822}", howpublished="RFC 1138 (Experimental)", series="Internet Request for Comments", type="RFC", number="1138", pages="1--92", year=1989, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 2156, 1327, updated by RFC 1148", url="https://www.rfc-editor.org/rfc/rfc1138.txt", key="RFC 1138", 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.}, doi="10.17487/RFC1138", } @misc{rfc1139, author="R.A. Hagens", title="{Echo function for ISO 8473}", howpublished="RFC 1139 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1139", pages="1--6", year=1990, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1574, 1575", url="https://www.rfc-editor.org/rfc/rfc1139.txt", key="RFC 1139", 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. [STANDARDS-TRACK]}, doi="10.17487/RFC1139", } @misc{rfc1140, author="Defense Advanced Research Projects Agency and Internet Activities Board", title="{IAB official protocol standards}", howpublished="RFC 1140 (Historic)", series="Internet Request for Comments", type="RFC", number="1140", pages="1--27", year=1990, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1200", url="https://www.rfc-editor.org/rfc/rfc1140.txt", key="RFC 1140", 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.}, keywords="IAB, official, protocol, standards", doi="10.17487/RFC1140", } @misc{rfc1141, author="T. Mallory and A. Kullberg", title="{Incremental updating of the Internet checksum}", howpublished="RFC 1141 (Informational)", series="Internet Request for Comments", type="RFC", number="1141", pages="1--2", year=1990, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 1624", url="https://www.rfc-editor.org/rfc/rfc1141.txt", key="RFC 1141", 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.}, doi="10.17487/RFC1141", } @misc{rfc1142, author="D. Oran", title="{OSI IS-IS Intra-domain Routing Protocol}", howpublished="RFC 1142 (Historic)", series="Internet Request for Comments", type="RFC", number="1142", pages="1--517", year=1990, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 7142", url="https://www.rfc-editor.org/rfc/rfc1142.txt", key="RFC 1142", abstract={This RFC is a republication of ISO DP 10589 as a service to the Internet community. This is not an Internet standard.}, keywords="Domain, Routing, ISO", doi="10.17487/RFC1142", } @misc{rfc1143, author="D.J. Bernstein", title="{The Q Method of Implementing TELNET Option Negotiation}", howpublished="RFC 1143 (Experimental)", series="Internet Request for Comments", type="RFC", number="1143", pages="1--10", year=1990, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1143.txt", key="RFC 1143", 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.}, keywords="", doi="10.17487/RFC1143", } @misc{rfc1144, author="V. Jacobson", title="{Compressing TCP/IP Headers for Low-Speed Serial Links}", howpublished="RFC 1144 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1144", pages="1--49", year=1990, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1144.txt", key="RFC 1144", 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. [STANDARDS-TRACK]}, keywords="IP-CMPRS", doi="10.17487/RFC1144", } @misc{rfc1145, author="J. Zweig and C. Partridge", title="{TCP alternate checksum options}", howpublished="RFC 1145 (Historic)", series="Internet Request for Comments", type="RFC", number="1145", pages="1--5", year=1990, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1146, 6247", url="https://www.rfc-editor.org/rfc/rfc1145.txt", key="RFC 1145", 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.}, doi="10.17487/RFC1145", } @misc{rfc1146, author="J. Zweig and C. Partridge", title="{TCP alternate checksum options}", howpublished="RFC 1146 (Historic)", series="Internet Request for Comments", type="RFC", number="1146", pages="1--5", year=1990, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 6247", url="https://www.rfc-editor.org/rfc/rfc1146.txt", key="RFC 1146", 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. Note: This RFC corrects errors introduced in the editing process in RFC 1145.}, keywords="TCP-ACO", doi="10.17487/RFC1146", } @misc{rfc1147, author="R.H. Stine", title="{FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices}", howpublished="RFC 1147 (Informational)", series="Internet Request for Comments", type="RFC", number="1147", pages="1--177", year=1990, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1470", url="https://www.rfc-editor.org/rfc/rfc1147.txt", key="RFC 1147", 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.}, doi="10.17487/RFC1147", } @misc{rfc1148, author="S.E. Kille", title="{Mapping between X.400(1988) / ISO 10021 and RFC 822}", howpublished="RFC 1148 (Experimental)", series="Internet Request for Comments", type="RFC", number="1148", pages="1--94", year=1990, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 2156, 1327", url="https://www.rfc-editor.org/rfc/rfc1148.txt", key="RFC 1148", 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.}, doi="10.17487/RFC1148", } @misc{rfc1149, author="D. Waitzman", title="{Standard for the transmission of IP datagrams on avian carriers}", howpublished="RFC 1149 (Experimental)", series="Internet Request for Comments", type="RFC", number="1149", pages="1--2", year=1990, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 2549, 6214", url="https://www.rfc-editor.org/rfc/rfc1149.txt", key="RFC 1149", 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.}, keywords="avian, carrier, april, fools", doi="10.17487/RFC1149", } @misc{rfc1150, author="G.S. Malkin and J.K. Reynolds", title="{FYI on FYI: Introduction to the FYI Notes}", howpublished="RFC 1150 (Historic)", series="Internet Request for Comments", type="RFC", number="1150", pages="1--4", year=1990, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 6360", url="https://www.rfc-editor.org/rfc/rfc1150.txt", key="RFC 1150", 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.]}, doi="10.17487/RFC1150", } @misc{rfc1151, author="C. Partridge and R.M. Hinden", title="{Version 2 of the Reliable Data Protocol (RDP)}", howpublished="RFC 1151 (Experimental)", series="Internet Request for Comments", type="RFC", number="1151", pages="1--4", year=1990, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1151.txt", key="RFC 1151", 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.}, keywords="RDP", doi="10.17487/RFC1151", } @misc{rfc1152, author="C. Partridge", title="{Workshop report: Internet research steering group workshop on very-high-speed networks}", howpublished="RFC 1152 (Informational)", series="Internet Request for Comments", type="RFC", number="1152", pages="1--23", year=1990, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1152.txt", key="RFC 1152", 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.}, doi="10.17487/RFC1152", } @misc{rfc1153, author="F.J. Wancho", title="{Digest message format}", howpublished="RFC 1153 (Experimental)", series="Internet Request for Comments", type="RFC", number="1153", pages="1--4", year=1990, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1153.txt", key="RFC 1153", abstract={This memo describes the de facto standard Digest Message Format. This is an elective experimental protocol.}, keywords="DMF-MAIL", doi="10.17487/RFC1153", } @misc{rfc1154, author="D. Robinson and R. Ullmann", title="{Encoding header field for internet messages}", howpublished="RFC 1154 (Experimental)", series="Internet Request for Comments", type="RFC", number="1154", pages="1--7", year=1990, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1505", url="https://www.rfc-editor.org/rfc/rfc1154.txt", key="RFC 1154", 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).}, doi="10.17487/RFC1154", } @misc{rfc1155, author="M.T. Rose and K. McCloghrie", title="{Structure and identification of management information for TCP/IP-based internets}", howpublished="RFC 1155 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1155", pages="1--22", year=1990, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1155.txt", key="RFC 1155", 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. [STANDARDS-TRACK]}, keywords="SMI", doi="10.17487/RFC1155", } @misc{rfc1156, author="K. McCloghrie and M.T. Rose", title="{Management Information Base for network management of TCP/IP-based internets}", howpublished="RFC 1156 (Historic)", series="Internet Request for Comments", type="RFC", number="1156", pages="1--91", year=1990, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1156.txt", key="RFC 1156", 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. [STANDARDS-TRACK]}, keywords="MIB-I", doi="10.17487/RFC1156", } @misc{rfc1157, author="J.D. Case and M. Fedor and M.L. Schoffstall and J. Davin", title="{Simple Network Management Protocol (SNMP)}", howpublished="RFC 1157 (Historic)", series="Internet Request for Comments", type="RFC", number="1157", pages="1--36", year=1990, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1157.txt", key="RFC 1157", 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. [STANDARDS-TRACK]}, keywords="SNMP", doi="10.17487/RFC1157", } @misc{rfc1158, author="M.T. Rose", title="{Management Information Base for network management of TCP/IP-based internets: MIB-II}", howpublished="RFC 1158 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1158", pages="1--133", year=1990, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1213", url="https://www.rfc-editor.org/rfc/rfc1158.txt", key="RFC 1158", 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. [STANDARDS-TRACK]}, doi="10.17487/RFC1158", } @misc{rfc1159, author="R. Nelson", title="{Message Send Protocol}", howpublished="RFC 1159 (Experimental)", series="Internet Request for Comments", type="RFC", number="1159", pages="1--2", year=1990, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1312", url="https://www.rfc-editor.org/rfc/rfc1159.txt", key="RFC 1159", 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.}, doi="10.17487/RFC1159", } @misc{rfc1160, author="V. Cerf", title="{Internet Activities Board}", howpublished="RFC 1160 (Informational)", series="Internet Request for Comments", type="RFC", number="1160", pages="1--11", year=1990, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1160.txt", key="RFC 1160", 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.}, doi="10.17487/RFC1160", } @misc{rfc1161, author="M.T. Rose", title="{SNMP over OSI}", howpublished="RFC 1161 (Experimental)", series="Internet Request for Comments", type="RFC", number="1161", pages="1--8", year=1990, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1418", url="https://www.rfc-editor.org/rfc/rfc1161.txt", key="RFC 1161", 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,}, doi="10.17487/RFC1161", } @misc{rfc1162, author="G. Satz", title="{Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base}", howpublished="RFC 1162 (Experimental)", series="Internet Request for Comments", type="RFC", number="1162", pages="1--70", year=1990, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1238", url="https://www.rfc-editor.org/rfc/rfc1162.txt", key="RFC 1162", 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.}, doi="10.17487/RFC1162", } @misc{rfc1163, author="K. Lougheed and Y. Rekhter", title="{Border Gateway Protocol (BGP)}", howpublished="RFC 1163 (Historic)", series="Internet Request for Comments", type="RFC", number="1163", pages="1--29", year=1990, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1267", url="https://www.rfc-editor.org/rfc/rfc1163.txt", key="RFC 1163", 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. [STANDARDS-TRACK]}, keywords="BGP", doi="10.17487/RFC1163", } @misc{rfc1164, author="J.C. Honig and D. Katz and M. Mathis and Y. Rekhter and J.Y. Yu", title="{Application of the Border Gateway Protocol in the Internet}", howpublished="RFC 1164 (Historic)", series="Internet Request for Comments", type="RFC", number="1164", pages="1--23", year=1990, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1268", url="https://www.rfc-editor.org/rfc/rfc1164.txt", key="RFC 1164", abstract={This RFC, together with its companion RFC-1163, ``A Border Gateway Protocol (BGP)'', specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]}, keywords="BGP", doi="10.17487/RFC1164", } @misc{rfc1165, author="J. Crowcroft and J.P. Onions", title="{Network Time Protocol (NTP) over the OSI Remote Operations Service}", howpublished="RFC 1165 (Experimental)", series="Internet Request for Comments", type="RFC", number="1165", pages="1--10", year=1990, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1165.txt", key="RFC 1165", 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.}, keywords="NTP-OSI", doi="10.17487/RFC1165", } @misc{rfc1166, author="S. Kirkpatrick and M.K. Stahl and M. Recker", title="{Internet numbers}", howpublished="RFC 1166 (Informational)", series="Internet Request for Comments", type="RFC", number="1166", pages="1--182", year=1990, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 5737", url="https://www.rfc-editor.org/rfc/rfc1166.txt", key="RFC 1166", abstract={This memo is a status report on the network numbers and autonomous system numbers used in the Internet community.}, doi="10.17487/RFC1166", } @misc{rfc1167, author="V.G. Cerf", title="{Thoughts on the National Research and Education Network}", howpublished="RFC 1167 (Informational)", series="Internet Request for Comments", type="RFC", number="1167", pages="1--8", year=1990, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1167.txt", key="RFC 1167", 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.}, doi="10.17487/RFC1167", } @misc{rfc1168, author="A. Westine and A.L. DeSchon and J. Postel and C.E. Ward", title="{Intermail and Commercial Mail Relay services}", howpublished="RFC 1168 (Informational)", series="Internet Request for Comments", type="RFC", number="1168", pages="1--18", year=1990, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1168.txt", key="RFC 1168", 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.}, doi="10.17487/RFC1168", } @misc{rfc1169, author="V.G. Cerf and K.L. Mills", title="{Explaining the role of GOSIP}", howpublished="RFC 1169 (Informational)", series="Internet Request for Comments", type="RFC", number="1169", pages="1--15", year=1990, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1169.txt", key="RFC 1169", 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.}, doi="10.17487/RFC1169", } @misc{rfc1170, author="R.B. Fougner", title="{Public key standards and licenses}", howpublished="RFC 1170 (Informational)", series="Internet Request for Comments", type="RFC", number="1170", pages="1--2", year=1991, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1170.txt", key="RFC 1170", 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.}, doi="10.17487/RFC1170", } @misc{rfc1171, author="D. Perkins", title="{Point-to-Point Protocol for the transmission of multi-protocol datagrams over Point-to-Point links}", howpublished="RFC 1171 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1171", pages="1--51", year=1990, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1331", url="https://www.rfc-editor.org/rfc/rfc1171.txt", key="RFC 1171", 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.}, doi="10.17487/RFC1171", } @misc{rfc1172, author="D. Perkins and R. Hobby", title="{Point-to-Point Protocol (PPP) initial configuration options}", howpublished="RFC 1172 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1172", pages="1--40", year=1990, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1331, 1332", url="https://www.rfc-editor.org/rfc/rfc1172.txt", key="RFC 1172", 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.}, doi="10.17487/RFC1172", } @misc{rfc1173, author="J. VanBokkelen", title="{Responsibilities of host and network managers: A summary of the ``oral tradition'' of the Internet}", howpublished="RFC 1173 (Informational)", series="Internet Request for Comments", type="RFC", number="1173", pages="1--5", year=1990, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1173.txt", key="RFC 1173", 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.}, doi="10.17487/RFC1173", } @misc{rfc1174, author="V.G. Cerf", title="{IAB recommended policy on distributing internet identifier assignment and IAB recommended policy change to internet ``connected'' status}", howpublished="RFC 1174 (Informational)", series="Internet Request for Comments", type="RFC", number="1174", pages="1--9", year=1990, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1174.txt", key="RFC 1174", 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.}, doi="10.17487/RFC1174", } @misc{rfc1175, author="K.L. Bowers and T.L. LaQuey and J.K. Reynolds and K. Roubicek and M.K. Stahl and A. Yuan", title="{FYI on where to start: A bibliography of internetworking information}", howpublished="RFC 1175 (Informational)", series="Internet Request for Comments", type="RFC", number="1175", pages="1--43", year=1990, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1175.txt", key="RFC 1175", 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.]}, doi="10.17487/RFC1175", } @misc{rfc1176, author="M.R. Crispin", title="{Interactive Mail Access Protocol: Version 2}", howpublished="RFC 1176 (Experimental)", series="Internet Request for Comments", type="RFC", number="1176", pages="1--30", year=1990, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1176.txt", key="RFC 1176", 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.}, keywords="IMAP2", doi="10.17487/RFC1176", } @misc{rfc1177, author="G.S. Malkin and A.N. Marine and J.K. Reynolds", title="{FYI on Questions and Answers: Answers to commonly asked ``new internet user'' questions}", howpublished="RFC 1177 (Informational)", series="Internet Request for Comments", type="RFC", number="1177", pages="1--24", year=1990, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1206", url="https://www.rfc-editor.org/rfc/rfc1177.txt", key="RFC 1177", 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.]}, doi="10.17487/RFC1177", } @misc{rfc1178, author="D. Libes", title="{Choosing a name for your computer}", howpublished="RFC 1178 (Informational)", series="Internet Request for Comments", type="RFC", number="1178", pages="1--8", year=1990, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1178.txt", key="RFC 1178", 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.]}, doi="10.17487/RFC1178", } @misc{rfc1179, author="L. McLaughlin", title="{Line printer daemon protocol}", howpublished="RFC 1179 (Informational)", series="Internet Request for Comments", type="RFC", number="1179", pages="1--14", year=1990, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1179.txt", key="RFC 1179", 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.}, keywords="LPDP", doi="10.17487/RFC1179", } @misc{rfc1180, author="T.J. Socolofsky and C.J. Kale", title="{TCP/IP tutorial}", howpublished="RFC 1180 (Informational)", series="Internet Request for Comments", type="RFC", number="1180", pages="1--28", year=1991, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1180.txt", key="RFC 1180", 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.}, doi="10.17487/RFC1180", } @misc{rfc1181, author="R. Blokzijl", title="{RIPE Terms of Reference}", howpublished="RFC 1181 (Informational)", series="Internet Request for Comments", type="RFC", number="1181", pages="1--2", year=1990, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1181.txt", key="RFC 1181", 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.}, doi="10.17487/RFC1181", } @misc{rfc1183, author="C.F. Everhart and L.A. Mamakos and R. Ullmann and P.V. Mockapetris", title="{New DNS RR Definitions}", howpublished="RFC 1183 (Experimental)", series="Internet Request for Comments", type="RFC", number="1183", pages="1--11", year=1990, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 5395, 5864, 6195, 6895", url="https://www.rfc-editor.org/rfc/rfc1183.txt", key="RFC 1183", 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.}, keywords="DNS-RR", doi="10.17487/RFC1183", } @misc{rfc1184, author="D.A. Borman", title="{Telnet Linemode Option}", howpublished="RFC 1184 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1184", pages="1--23", year=1990, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1184.txt", key="RFC 1184", abstract={This RFC specifies a procedure for line at a time terminal interaction based on the Telnet Protocol. It obsoletes RFC 1116. [STANDARDS-TRACK]}, keywords="TOPT-LINE", doi="10.17487/RFC1184", } @misc{rfc1185, author="V. Jacobson and R.T. Braden and L. Zhang", title="{TCP Extension for High-Speed Paths}", howpublished="RFC 1185 (Experimental)", series="Internet Request for Comments", type="RFC", number="1185", pages="1--21", year=1990, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1323", url="https://www.rfc-editor.org/rfc/rfc1185.txt", key="RFC 1185", 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.}, doi="10.17487/RFC1185", } @misc{rfc1186, author="R.L. Rivest", title="{MD4 Message Digest Algorithm}", howpublished="RFC 1186 (Informational)", series="Internet Request for Comments", type="RFC", number="1186", pages="1--18", year=1990, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1320", url="https://www.rfc-editor.org/rfc/rfc1186.txt", key="RFC 1186", 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.}, doi="10.17487/RFC1186", } @misc{rfc1187, author="M.T. Rose and K. McCloghrie and J.R. Davin", title="{Bulk Table Retrieval with the SNMP}", howpublished="RFC 1187 (Experimental)", series="Internet Request for Comments", type="RFC", number="1187", pages="1--12", year=1990, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1187.txt", key="RFC 1187", 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.}, keywords="SNMP-BULK", doi="10.17487/RFC1187", } @misc{rfc1188, author="D. Katz", title="{Proposed Standard for the Transmission of IP Datagrams over FDDI Networks}", howpublished="RFC 1188 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1188", pages="1--11", year=1990, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1188.txt", key="RFC 1188", 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. [STANDARDS-TRACK]}, keywords="", doi="10.17487/RFC1188", } @misc{rfc1189, author="U.S. Warrier and L. Besaw and L. LaBarre and B.D. Handspicker", title="{Common Management Information Services and Protocols for the Internet (CMOT and CMIP)}", howpublished="RFC 1189 (Historic)", series="Internet Request for Comments", type="RFC", number="1189", pages="1--15", year=1990, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1189.txt", key="RFC 1189", 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. [STANDARDS-TRACK]}, keywords="CMOT", doi="10.17487/RFC1189", } @misc{rfc1190, author="C. Topolcic", title="{Experimental Internet Stream Protocol: Version 2 (ST-II)}", howpublished="RFC 1190 (Experimental)", series="Internet Request for Comments", type="RFC", number="1190", pages="1--148", year=1990, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1819", url="https://www.rfc-editor.org/rfc/rfc1190.txt", key="RFC 1190", abstract={This memo defines a revised version of the Internet Stream Protocol, originally defined in IEN-119 [8], 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.}, doi="10.17487/RFC1190", } @misc{rfc1191, author="J.C. Mogul and S.E. Deering", title="{Path MTU discovery}", howpublished="RFC 1191 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1191", pages="1--19", year=1990, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1191.txt", key="RFC 1191", 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. [STANDARDS-TRACK]}, keywords="IP-MTU", doi="10.17487/RFC1191", } @misc{rfc1192, author="B. Kahin", title="{Commercialization of the Internet summary report}", howpublished="RFC 1192 (Informational)", series="Internet Request for Comments", type="RFC", number="1192", pages="1--13", year=1990, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1192.txt", key="RFC 1192", 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.}, doi="10.17487/RFC1192", } @misc{rfc1193, author="D. Ferrari", title="{Client requirements for real-time communication services}", howpublished="RFC 1193 (Informational)", series="Internet Request for Comments", type="RFC", number="1193", pages="1--24", year=1990, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1193.txt", key="RFC 1193", 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.}, doi="10.17487/RFC1193", } @misc{rfc1194, author="D.P. Zimmerman", title="{Finger User Information Protocol}", howpublished="RFC 1194 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1194", pages="1--12", year=1990, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1196, 1288", url="https://www.rfc-editor.org/rfc/rfc1194.txt", key="RFC 1194", 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. [STANDARDS-TRACK]}, doi="10.17487/RFC1194", } @misc{rfc1195, author="R.W. Callon", title="{Use of OSI IS-IS for routing in TCP/IP and dual environments}", howpublished="RFC 1195 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1195", pages="1--85", year=1990, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 1349, 5302, 5304", url="https://www.rfc-editor.org/rfc/rfc1195.txt", key="RFC 1195", 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. [STANDARDS-TRACK]}, keywords="IS-IS", doi="10.17487/RFC1195", } @misc{rfc1196, author="D.P. Zimmerman", title="{Finger User Information Protocol}", howpublished="RFC 1196 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1196", pages="1--12", year=1990, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1288", url="https://www.rfc-editor.org/rfc/rfc1196.txt", key="RFC 1196", 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. This edition corrects and clarifies in a minor way, RFC 1194. [STANDARDS-TRACK]}, doi="10.17487/RFC1196", } @misc{rfc1197, author="M. Sherman", title="{Using ODA for translating multimedia information}", howpublished="RFC 1197 (Informational)", series="Internet Request for Comments", type="RFC", number="1197", pages="1--2", year=1990, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1197.txt", key="RFC 1197", 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.}, doi="10.17487/RFC1197", } @misc{rfc1198, author="R.W. Scheifler", title="{FYI on the X window system}", howpublished="RFC 1198 (Informational)", series="Internet Request for Comments", type="RFC", number="1198", pages="1--3", year=1991, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1198.txt", key="RFC 1198", 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.}, doi="10.17487/RFC1198", } @misc{rfc1199, author="J. Reynolds", title="{Request for Comments Summary Notes: 1100-1199}", howpublished="RFC 1199 (Informational)", series="Internet Request for Comments", type="RFC", number="1199", pages="1--22", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1199.txt", key="RFC 1199", keywords="Summary, RFC", doi="10.17487/RFC1199", } @misc{rfc1200, author="Defense Advanced Research Projects Agency and Internet Activities Board", title="{IAB official protocol standards}", howpublished="RFC 1200 (Historic)", series="Internet Request for Comments", type="RFC", number="1200", pages="1--31", year=1991, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1250", url="https://www.rfc-editor.org/rfc/rfc1200.txt", key="RFC 1200", 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.}, keywords="IAB, official, protocol, standards", doi="10.17487/RFC1200", } @misc{rfc1201, author="D. Provan", title="{Transmitting IP traffic over ARCNET networks}", howpublished="RFC 1201 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1201", pages="1--7", year=1991, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1201.txt", key="RFC 1201", abstract={This memo defines a protocol for the transmission of IP and ARP packets over the ARCnet Local Area Network.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''. [STANDARDS-TRACK]}, keywords="IP-ARC", doi="10.17487/RFC1201", } @misc{rfc1202, author="M.T. Rose", title="{Directory Assistance service}", howpublished="RFC 1202 (Informational)", series="Internet Request for Comments", type="RFC", number="1202", pages="1--11", year=1991, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1202.txt", key="RFC 1202", abstract={This document defines a mechanism by which a user-interface may access a textual DAP-like interface over a TCP/IP connection. This is a local mechanism. This memo provides information for the Internet community. It does not specify any standard.}, keywords="DAS", doi="10.17487/RFC1202", } @misc{rfc1203, author="J. Rice", title="{Interactive Mail Access Protocol: Version 3}", howpublished="RFC 1203 (Historic)", series="Internet Request for Comments", type="RFC", number="1203", pages="1--49", year=1991, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1203.txt", key="RFC 1203", abstract={This RFC suggests a method for workstations to access mail dynamically from a mailbox server (``repository''). The following document is a modified version of RFC 1064, the definition of the IMAP2 protocol. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard.}, keywords="IMAP3", doi="10.17487/RFC1203", } @misc{rfc1204, author="S. Yeh and D. Lee", title="{Message Posting Protocol (MPP)}", howpublished="RFC 1204 (Experimental)", series="Internet Request for Comments", type="RFC", number="1204", pages="1--6", year=1991, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1204.txt", key="RFC 1204", abstract={This memo describes a protocol for posting messages from workstations (e.g., PCs) to a mail service host. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard.}, keywords="MPP", doi="10.17487/RFC1204", } @misc{rfc1205, author="P. Chmielewski", title="{5250 Telnet interface}", howpublished="RFC 1205 (Informational)", series="Internet Request for Comments", type="RFC", number="1205", pages="1--12", year=1991, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 2877", url="https://www.rfc-editor.org/rfc/rfc1205.txt", key="RFC 1205", abstract={This RFC is being distributed in order to document the interface to the IBM 5250 Telnet implementation. This memo provides information for the Internet community. It does not specify any standard.}, doi="10.17487/RFC1205", } @misc{rfc1206, author="G.S. Malkin and A.N. Marine", title="{FYI on Questions and Answers: Answers to commonly asked ``new Internet user'' questions}", howpublished="RFC 1206 (Informational)", series="Internet Request for Comments", type="RFC", number="1206", pages="1--32", year=1991, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1325", url="https://www.rfc-editor.org/rfc/rfc1206.txt", key="RFC 1206", abstract={This FYI RFC is one of two FYI's called, ``Questions and Answers'' (Q/A). 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. [FYI 4]}, doi="10.17487/RFC1206", } @misc{rfc1207, author="G.S. Malkin and A.N. Marine and J.K. Reynolds", title="{FYI on Questions and Answers: Answers to commonly asked ``experienced Internet user'' questions}", howpublished="RFC 1207 (Informational)", series="Internet Request for Comments", type="RFC", number="1207", pages="1--15", year=1991, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1207.txt", key="RFC 1207", abstract={This FYI RFC is one of two FYI's called, ``Questions and Answers'' (Q/A), produced by the User Services Working Group 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.}, doi="10.17487/RFC1207", } @misc{rfc1208, author="O.J. Jacobsen and D.C. Lynch", title="{A Glossary of Networking Terms}", howpublished="RFC 1208 (Informational)", series="Internet Request for Comments", type="RFC", number="1208", pages="1--18", year=1991, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1208.txt", key="RFC 1208", abstract={This RFC is a glossary adapted from ``The INTEROP Pocket Glossary of Networking Terms'' distributed at Interop '90. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1208", } @misc{rfc1209, author="D. Piscitello and J. Lawrence", title="{The Transmission of IP Datagrams over the SMDS Service}", howpublished="RFC 1209 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1209", pages="1--11", year=1991, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1209.txt", key="RFC 1209", abstract={This memo defines a protocol for the transmission of IP and ARP packets over a Switched Multi-megabit Data Service Network configured as a logical IP subnetwork. [STANDARDS-TRACK]}, keywords="IP-SMDS, Switched Multi-megabit Data Service", doi="10.17487/RFC1209", } @misc{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}", howpublished="RFC 1210 (Informational)", series="Internet Request for Comments", type="RFC", number="1210", pages="1--36", year=1991, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1210.txt", key="RFC 1210", abstract={This report complements a shorter printed version which appeared in a summary report of all the committees which met in Brussels and Washington last July, 1990. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1210", } @misc{rfc1211, author="A. Westine and J. Postel", title="{Problems with the maintenance of large mailing lists}", howpublished="RFC 1211 (Informational)", series="Internet Request for Comments", type="RFC", number="1211", pages="1--54", year=1991, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1211.txt", key="RFC 1211", abstract={This RFC discusses problems with maintaining large mailing lists, especially the processing of error reports. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1211", } @misc{rfc1212, author="M.T. Rose and K. McCloghrie", title="{Concise MIB definitions}", howpublished="RFC 1212 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1212", pages="1--19", year=1991, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1212.txt", key="RFC 1212", abstract={This memo describes a straight-forward approach toward producing concise, yet descriptive, MIB modules. This memo defines a format for producing MIB modules. [STANDARDS-TRACK]}, keywords="Concise-MIB", doi="10.17487/RFC1212", } @misc{rfc1213, author="K. McCloghrie and M. Rose", title="{Management Information Base for Network Management of TCP/IP-based internets: MIB-II}", howpublished="RFC 1213 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1213", pages="1--70", year=1991, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 2011, 2012, 2013", url="https://www.rfc-editor.org/rfc/rfc1213.txt", key="RFC 1213", 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. [STANDARDS-TRACK]}, keywords="MIB-II", doi="10.17487/RFC1213", } @misc{rfc1214, author="L. LaBarre", title="{OSI internet management: Management Information Base}", howpublished="RFC 1214 (Historic)", series="Internet Request for Comments", type="RFC", number="1214", pages="1--83", year=1991, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1214.txt", key="RFC 1214", 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. [STANDARDS-TRACK]}, keywords="OIM-MIB-II", doi="10.17487/RFC1214", } @misc{rfc1215, author="M.T. Rose", title="{Convention for defining traps for use with the SNMP}", howpublished="RFC 1215 (Informational)", series="Internet Request for Comments", type="RFC", number="1215", pages="1--9", year=1991, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1215.txt", key="RFC 1215", abstract={This memo suggests a straight-forward approach towards defining traps used with the SNMP. This memo provides information for the Internet community. It does not specify any standard.}, keywords="SNMP-TRAPS", doi="10.17487/RFC1215", } @misc{rfc1216, author="P. Richard and P. Kynikos", title="{Gigabit network economics and paradigm shifts}", howpublished="RFC 1216 (Informational)", series="Internet Request for Comments", type="RFC", number="1216", pages="1--4", year=1991, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1216.txt", key="RFC 1216", abstract={This memo proposes a new standard paradigm for the Internet Activities Board (IAB) standardization track. [STANDARDS-TRACK]}, doi="10.17487/RFC1216", } @misc{rfc1217, author="V.G. Cerf", title="{Memo from the Consortium for Slow Commotion Research (CSCR)}", howpublished="RFC 1217 (Informational)", series="Internet Request for Comments", type="RFC", number="1217", pages="1--5", year=1991, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1217.txt", key="RFC 1217", abstract={This RFC is in response to RFC 1216, ``Gigabit Network Economics and Paradigm Shifts''. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1217", } @misc{rfc1218, author="North American Directory Forum", title="{Naming scheme for c=US}", howpublished="RFC 1218 (Informational)", series="Internet Request for Comments", type="RFC", number="1218", pages="1--23", year=1991, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1255, 1417", url="https://www.rfc-editor.org/rfc/rfc1218.txt", key="RFC 1218", abstract={This RFC is a near-verbatim copy of a document, known as NADF-123, which has been produced by the North American Directory Forum (NADF). As a part of its charter, the NADF must reach agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1218", } @misc{rfc1219, author="P.F. Tsuchiya", title="{On the assignment of subnet numbers}", howpublished="RFC 1219 (Informational)", series="Internet Request for Comments", type="RFC", number="1219", pages="1--13", year=1991, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1219.txt", key="RFC 1219", abstract={This memo suggests a new procedure for assigning subnet numbers. Use of this assignment technique within a network would be a purely local matter, and would not effect other networks. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="SUBNETASGN", doi="10.17487/RFC1219", } @misc{rfc1220, author="F. Baker", title="{Point-to-Point Protocol extensions for bridging}", howpublished="RFC 1220 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1220", pages="1--18", year=1991, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1638", url="https://www.rfc-editor.org/rfc/rfc1220.txt", key="RFC 1220", 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. [STANDARDS-TRACK]}, doi="10.17487/RFC1220", } @misc{rfc1221, author="W. Edmond", title="{Host Access Protocol (HAP) specification: Version 2}", howpublished="RFC 1221 (Informational)", series="Internet Request for Comments", type="RFC", number="1221", pages="1--68", year=1991, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1221.txt", key="RFC 1221", abstract={This memo describes the Host Access Protocol implemented in the Terrestrial Wideband Network (TWBNET). This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="HAP2", doi="10.17487/RFC1221", } @misc{rfc1222, author="H.W. Braun and Y. Rekhter", title="{Advancing the NSFNET routing architecture}", howpublished="RFC 1222 (Informational)", series="Internet Request for Comments", type="RFC", number="1222", pages="1--6", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1222.txt", key="RFC 1222", abstract={This RFC suggests improvements in the NSFNET routing architecture to accommodate a more flexible interface to the Backbone clients. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1222", } @misc{rfc1223, author="J.M. Halpern", title="{OSI CLNS and LLC1 protocols on Network Systems HYPERchannel}", howpublished="RFC 1223 (Informational)", series="Internet Request for Comments", type="RFC", number="1223", pages="1--12", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1223.txt", key="RFC 1223", 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 memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="OSI-HYPER", doi="10.17487/RFC1223", } @misc{rfc1224, author="L. Steinberg", title="{Techniques for managing asynchronously generated alerts}", howpublished="RFC 1224 (Experimental)", series="Internet Request for Comments", type="RFC", number="1224", pages="1--22", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1224.txt", key="RFC 1224", abstract={This memo defines common mechanisms for managing asynchronously produced alerts in a manner consistent with current network management protocols. This memo specifies an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="ALERTS", doi="10.17487/RFC1224", } @misc{rfc1225, author="M.T. Rose", title="{Post Office Protocol: Version 3}", howpublished="RFC 1225 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1225", pages="1--16", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1460", url="https://www.rfc-editor.org/rfc/rfc1225.txt", key="RFC 1225", abstract={This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. [STANDARDS-TRACK]}, doi="10.17487/RFC1225", } @misc{rfc1226, author="B. Kantor", title="{Internet protocol encapsulation of AX.25 frames}", howpublished="RFC 1226 (Experimental)", series="Internet Request for Comments", type="RFC", number="1226", pages="1--2", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1226.txt", key="RFC 1226", 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. It does not specify an Internet standard.}, keywords="IP-AX.25", doi="10.17487/RFC1226", } @misc{rfc1227, author="M.T. Rose", title="{SNMP MUX protocol and MIB}", howpublished="RFC 1227 (Historic)", series="Internet Request for Comments", type="RFC", number="1227", pages="1--13", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1227.txt", key="RFC 1227", abstract={This memo suggests a mechanism by which a user process may associate itself with the local SNMP agent on a host, in order to implement portions of the MIB. This mechanism would be local to the host.This is an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="SNMP-MUX", doi="10.17487/RFC1227", } @misc{rfc1228, author="G. Carpenter and B. Wijnen", title="{SNMP-DPI: Simple Network Management Protocol Distributed Program Interface}", howpublished="RFC 1228 (Experimental)", series="Internet Request for Comments", type="RFC", number="1228", pages="1--50", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1592", url="https://www.rfc-editor.org/rfc/rfc1228.txt", key="RFC 1228", abstract={This RFC describes a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1228", } @misc{rfc1229, author="K. McCloghrie", title="{Extensions to the generic-interface MIB}", howpublished="RFC 1229 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1229", pages="1--16", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1573, updated by RFC 1239", url="https://www.rfc-editor.org/rfc/rfc1229.txt", key="RFC 1229", abstract={This RFC contains definitions of managed objects used as experimental extensions to the generic interfaces structure of MIB-II. [STANDARDS-TRACK]}, doi="10.17487/RFC1229", } @misc{rfc1230, author="K. McCloghrie and R. Fox", title="{IEEE 802.4 Token Bus MIB}", howpublished="RFC 1230 (Historic)", series="Internet Request for Comments", type="RFC", number="1230", pages="1--23", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 1239", url="https://www.rfc-editor.org/rfc/rfc1230.txt", key="RFC 1230", 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. [STANDARDS-TRACK]}, keywords="802.4-MIP", doi="10.17487/RFC1230", } @misc{rfc1231, author="K. McCloghrie and R. Fox and E. Decker", title="{IEEE 802.5 Token Ring MIB}", howpublished="RFC 1231 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1231", pages="1--23", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1743, 1748, updated by RFC 1239", url="https://www.rfc-editor.org/rfc/rfc1231.txt", key="RFC 1231", 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. [STANDARDS-TRACK]}, doi="10.17487/RFC1231", } @misc{rfc1232, author="F. Baker and C.P. Kolb", title="{Definitions of managed objects for the DS1 Interface type}", howpublished="RFC 1232 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1232", pages="1--28", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1406, updated by RFC 1239", url="https://www.rfc-editor.org/rfc/rfc1232.txt", key="RFC 1232", doi="10.17487/RFC1232", } @misc{rfc1233, author="T.A. Cox and K. Tesink", title="{Definitions of managed objects for the DS3 Interface type}", howpublished="RFC 1233 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1233", pages="1--23", year=1991, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1407, updated by RFC 1239", url="https://www.rfc-editor.org/rfc/rfc1233.txt", key="RFC 1233", abstract={This memo defines objects for managing DS3 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK]}, doi="10.17487/RFC1233", } @misc{rfc1234, author="D. Provan", title="{Tunneling IPX traffic through IP networks}", howpublished="RFC 1234 (Historic)", series="Internet Request for Comments", type="RFC", number="1234", pages="1--6", year=1991, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1234.txt", key="RFC 1234", abstract={This memo describes a method of encapsulating IPX datagrams within UDP packets so that IPX traffic can travel across an IP internet. [STANDARDS-TRACK] This memo defines objects for managing DS1 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK]}, keywords="IPX-IP", doi="10.17487/RFC1234", } @misc{rfc1235, author="J. Ioannidis and G. Maguire", title="{Coherent File Distribution Protocol}", howpublished="RFC 1235 (Experimental)", series="Internet Request for Comments", type="RFC", number="1235", pages="1--12", year=1991, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1235.txt", key="RFC 1235", abstract={This memo describes the Coherent File Distribution Protocol (CFDP). This is an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="CFDP", doi="10.17487/RFC1235", } @misc{rfc1236, author="L. Morales and P. Hasse", title="{IP to X.121 address mapping for DDN}", howpublished="RFC 1236 (Informational)", series="Internet Request for Comments", type="RFC", number="1236", pages="1--7", year=1991, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1236.txt", key="RFC 1236", 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). This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="IP-X.121", doi="10.17487/RFC1236", } @misc{rfc1237, author="R. Colella and E. Gardner and R. Callon", title="{Guidelines for OSI NSAP Allocation in the Internet}", howpublished="RFC 1237 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1237", pages="1--48", year=1991, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1629", url="https://www.rfc-editor.org/rfc/rfc1237.txt", key="RFC 1237", abstract={This paper provides guidelines for allocating NSAPs in the Internet.[STANDARDS-TRACK]}, doi="10.17487/RFC1237", } @misc{rfc1238, author="G. Satz", title="{CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542)}", howpublished="RFC 1238 (Experimental)", series="Internet Request for Comments", type="RFC", number="1238", pages="1--32", year=1991, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1238.txt", key="RFC 1238", 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 is an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="CLNS-MIB", doi="10.17487/RFC1238", } @misc{rfc1239, author="J.K. Reynolds", title="{Reassignment of experimental MIBs to standard MIBs}", howpublished="RFC 1239 (Historic)", series="Internet Request for Comments", type="RFC", number="1239", pages="1--2", year=1991, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1239.txt", key="RFC 1239", abstract={This memo specifically updates RFC 1229, RFC 1230, RFC 1231, RFC 1232 and RFC 1233 with new codes. [STANDARDS-TRACK]}, keywords="STD-MIBs", doi="10.17487/RFC1239", } @misc{rfc1240, author="C. Shue and W. Haggerty and K. Dobbins", title="{OSI connectionless transport services on top of UDP: Version 1}", howpublished="RFC 1240 (Historic)", series="Internet Request for Comments", type="RFC", number="1240", pages="1--8", year=1991, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1240.txt", key="RFC 1240", abstract={This document describes a protocol for running OSI Connectionless service on UDP. [STANDARDS-TRACK]}, keywords="OSI-UDP", doi="10.17487/RFC1240", } @misc{rfc1241, author="R.A. Woodburn and D.L. Mills", title="{Scheme for an internet encapsulation protocol: Version 1}", howpublished="RFC 1241 (Experimental)", series="Internet Request for Comments", type="RFC", number="1241", pages="1--17", year=1991, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1241.txt", key="RFC 1241", abstract={This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="IN-ENCAP", doi="10.17487/RFC1241", } @misc{rfc1242, author="S. Bradner", title="{Benchmarking Terminology for Network Interconnection Devices}", howpublished="RFC 1242 (Informational)", series="Internet Request for Comments", type="RFC", number="1242", pages="1--12", year=1991, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 6201", url="https://www.rfc-editor.org/rfc/rfc1242.txt", key="RFC 1242", abstract={This memo discusses and defines a number of terms that are used in describing performance benchmarking tests and the results of such tests. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1242", } @misc{rfc1243, author="S. Waldbusser", title="{AppleTalk Management Information Base}", howpublished="RFC 1243 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1243", pages="1--29", year=1991, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1742", url="https://www.rfc-editor.org/rfc/rfc1243.txt", key="RFC 1243", abstract={This memo defines objects for managing AppleTalk objects for use with the SNMP protocol. [STANDARDS-TRACK]}, doi="10.17487/RFC1243", } @misc{rfc1244, author="J.P. Holbrook and J.K. Reynolds", title="{Site Security Handbook}", howpublished="RFC 1244 (Informational)", series="Internet Request for Comments", type="RFC", number="1244", pages="1--101", year=1991, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2196", url="https://www.rfc-editor.org/rfc/rfc1244.txt", key="RFC 1244", abstract={This FYI RFC is a first attempt at providing Internet users guidance on how to deal with security issues in the Internet. This FYI RFC provides information for the Internet community. It does not specify an Internet standard. [FYI 8]}, doi="10.17487/RFC1244", } @misc{rfc1245, author="J. Moy", title="{OSPF Protocol Analysis}", howpublished="RFC 1245 (Informational)", series="Internet Request for Comments", type="RFC", number="1245", pages="1--12", year=1991, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1245.txt", key="RFC 1245", abstract={This report attempts to summarize the key features of OSPF V2. It also attempts to analyze how the protocol will perform and scale in the Internet. This memo provides information for the Internet community. It does not specify any Internet standard.}, keywords="OSPF, SPF, routing, TOS, LSA, flooding", doi="10.17487/RFC1245", } @misc{rfc1246, author="J. Moy", title="{Experience with the OSPF Protocol}", howpublished="RFC 1246 (Informational)", series="Internet Request for Comments", type="RFC", number="1246", pages="1--31", year=1991, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1246.txt", key="RFC 1246", abstract={This report documents experience with OSPF V2. This includes reports on interoperability testing, field experience, simulations and the current state of OSPF implementations. This memo provides information for the Internet community. It does not specify any Internet standard.}, keywords="OSPF, SPF, routing, MIB, experience, testing", doi="10.17487/RFC1246", } @misc{rfc1247, author="J. Moy", title="{OSPF Version 2}", howpublished="RFC 1247 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1247", pages="1--189", year=1991, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1583, updated by RFC 1349", url="https://www.rfc-editor.org/rfc/rfc1247.txt", key="RFC 1247", abstract={This memo documents version 2 of the OSPF protocol. OSPF is a link- state based routing protocol. [STANDARDS-TRACK]}, keywords="equal-cost, multipath, link state, LSA", doi="10.17487/RFC1247", } @misc{rfc1248, author="F. Baker and R. Coltun", title="{OSPF Version 2 Management Information Base}", howpublished="RFC 1248 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1248", pages="1--42", year=1991, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1252, updated by RFC 1349", url="https://www.rfc-editor.org/rfc/rfc1248.txt", key="RFC 1248", 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 objects for managing OSPF Version 2. [STANDARDS-TRACK]}, keywords="OSPF, SPF, MIB, routing, network management", doi="10.17487/RFC1248", } @misc{rfc1249, author="T. Howes and M. Smith and B. Beecher", title="{DIXIE Protocol Specification}", howpublished="RFC 1249 (Informational)", series="Internet Request for Comments", type="RFC", number="1249", pages="1--10", year=1991, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1249.txt", key="RFC 1249", abstract={This RFC defines a mechanism by which TCP/UDP based clients can access OSI Directory Service without the overhead of the ISO transport and presentation protocols required to implement full-blown DAP. This memo provides information for the Internet community. It does not specify any standard.}, keywords="DIXIE, DIXIE, protocol, directory services, X.500, DAP", doi="10.17487/RFC1249", } @misc{rfc1250, author="J. Postel", title="{IAB Official Protocol Standards}", howpublished="RFC 1250 (Historic)", series="Internet Request for Comments", type="RFC", number="1250", pages="1--28", year=1991, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 2200, 1280", url="https://www.rfc-editor.org/rfc/rfc1250.txt", key="RFC 1250", abstract={This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="standards, protocol, IAB", doi="10.17487/RFC1250", } @misc{rfc1251, author="G. Malkin", title="{Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members}", howpublished="RFC 1251 (Informational)", series="Internet Request for Comments", type="RFC", number="1251", pages="1--26", year=1991, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1336", url="https://www.rfc-editor.org/rfc/rfc1251.txt", key="RFC 1251", abstract={This FYI RFC contains biographical information about members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 9]}, keywords="IESG, IRSG, IAB", doi="10.17487/RFC1251", } @misc{rfc1252, author="F. Baker and R. Coltun", title="{OSPF Version 2 Management Information Base}", howpublished="RFC 1252 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1252", pages="1--42", year=1991, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1253", url="https://www.rfc-editor.org/rfc/rfc1252.txt", key="RFC 1252", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK]}, keywords="OSPF, SPF, MIB, routing, network management", doi="10.17487/RFC1252", } @misc{rfc1253, author="F. Baker and R. Coltun", title="{OSPF Version 2 Management Information Base}", howpublished="RFC 1253 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1253", pages="1--42", year=1991, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1850", url="https://www.rfc-editor.org/rfc/rfc1253.txt", key="RFC 1253", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK]}, doi="10.17487/RFC1253", } @misc{rfc1254, author="A. Mankin and K. Ramakrishnan", title="{Gateway Congestion Control Survey}", howpublished="RFC 1254 (Informational)", series="Internet Request for Comments", type="RFC", number="1254", pages="1--25", year=1991, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1254.txt", key="RFC 1254", abstract={The purpose of this paper is to present a review of the congestion control approaches, as a way of encouraging new discussion and experimentation. Included in the survey are Source Quench, Random Drop, Congestion Indication (DEC Bit), and Fair Queueing.}, keywords="gateway, congestion, SQ, source quench, fiar queueing, random drop", doi="10.17487/RFC1254", } @misc{rfc1255, author="The North American Directory Forum", title="{A Naming Scheme for c=US}", howpublished="RFC 1255 (Informational)", series="Internet Request for Comments", type="RFC", number="1255", pages="1--25", year=1991, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1417", url="https://www.rfc-editor.org/rfc/rfc1255.txt", key="RFC 1255", abstract={This memo documents the NADF's agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="naming, NADF, X.500, directory services, c=us", doi="10.17487/RFC1255", } @misc{rfc1256, author="S. Deering", title="{ICMP Router Discovery Messages}", howpublished="RFC 1256 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1256", pages="1--19", year=1991, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1256.txt", key="RFC 1256", abstract={This document specifies an extension of the Internet Control Message Protocol (ICMP) to enable hosts attached to multicast or broadcast networks to discover the IP addresses of their neighboring routers. [STANDARDS-TRACK]}, keywords="ICMP-ROUT, ICMP, router, gateway, discovery, standard, protocol", doi="10.17487/RFC1256", } @misc{rfc1257, author="C. Partridge", title="{Isochronous applications do not require jitter-controlled networks}", howpublished="RFC 1257 (Informational)", series="Internet Request for Comments", type="RFC", number="1257", pages="1--5", year=1991, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1257.txt", key="RFC 1257", abstract={This memo argues that jitter control is not required for networks to support isochronous applications. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1257", } @misc{rfc1258, author="B. Kantor", title="{BSD Rlogin}", howpublished="RFC 1258 (Informational)", series="Internet Request for Comments", type="RFC", number="1258", pages="1--5", year=1991, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1282", url="https://www.rfc-editor.org/rfc/rfc1258.txt", key="RFC 1258", abstract={The rlogin facility provides a remote-echoed, locally flow-controlled virtual terminal with proper flushing of output.This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1258", } @misc{rfc1259, author="M. Kapor", title="{Building the open road: The NREN as test-bed for the national public network}", howpublished="RFC 1259 (Informational)", series="Internet Request for Comments", type="RFC", number="1259", pages="1--23", year=1991, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1259.txt", key="RFC 1259", abstract={This memo discusses the background and importance of NREN. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="NREN, test-bed, network policy", doi="10.17487/RFC1259", } @misc{rfc1261, author="S. Williamson and L. Nobile", title="{Transition of Nic Services}", howpublished="RFC 1261 (Informational)", series="Internet Request for Comments", type="RFC", number="1261", pages="1--3", year=1991, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1261.txt", key="RFC 1261", abstract={This memo outlines the transition of NIC Services. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="NIC, transition", doi="10.17487/RFC1261", } @misc{rfc1262, author="V.G. Cerf", title="{Guidelines for Internet Measurement Activities}", howpublished="RFC 1262 (Informational)", series="Internet Request for Comments", type="RFC", number="1262", pages="1--3", year=1991, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1262.txt", key="RFC 1262", abstract={This RFC represents IAB guidance for researchers considering measurement experiments on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1262", } @misc{rfc1263, author="S. O'Malley and L.L. Peterson", title="{TCP Extensions Considered Harmful}", howpublished="RFC 1263 (Informational)", series="Internet Request for Comments", type="RFC", number="1263", pages="1--19", year=1991, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1263.txt", key="RFC 1263", abstract={This RFC comments on recent proposals to extend TCP. It argues that the backward compatible extensions proposed in RFC's 1072 and 1185 should not be pursued, and proposes an alternative way to evolve the Internet protocol suite. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1263", } @misc{rfc1264, author="R.M. Hinden", title="{Internet Engineering Task Force Internet Routing Protocol Standardization Criteria}", howpublished="RFC 1264 (Historic)", series="Internet Request for Comments", type="RFC", number="1264", pages="1--8", year=1991, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 4794", url="https://www.rfc-editor.org/rfc/rfc1264.txt", key="RFC 1264", abstract={This informational RFC presents procedures for creating and documenting Internet standards on routing protocols. These procedures have been established by the Internet Activities Board (IAB) in consultation with the Internet Engineering Steering Group (IESG). This memo provides information for the Internet community. It does not specifiy an Internet standard.}, doi="10.17487/RFC1264", } @misc{rfc1265, author="Y. Rekhter", title="{BGP Protocol Analysis}", howpublished="RFC 1265 (Informational)", series="Internet Request for Comments", type="RFC", number="1265", pages="1--8", year=1991, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1265.txt", key="RFC 1265", abstract={This report summarizes the key feature of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1265", } @misc{rfc1266, author="Y. Rekhter", title="{Experience with the BGP Protocol}", howpublished="RFC 1266 (Informational)", series="Internet Request for Comments", type="RFC", number="1266", pages="1--9", year=1991, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1266.txt", key="RFC 1266", abstract={The purpose of this memo is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by Border Gateway Protocol (BGP). This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1266", } @misc{rfc1267, author="K. Lougheed and Y. Rekhter", title="{Border Gateway Protocol 3 (BGP-3)}", howpublished="RFC 1267 (Historic)", series="Internet Request for Comments", type="RFC", number="1267", pages="1--35", year=1991, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1267.txt", key="RFC 1267", abstract={This memo, together with its companion document, ``Application of the Border Gateway Protocol in the Internet'', define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]}, keywords="BGP3", doi="10.17487/RFC1267", } @misc{rfc1268, author="Y. Rekhter and P. Gross", title="{Application of the Border Gateway Protocol in the Internet}", howpublished="RFC 1268 (Historic)", series="Internet Request for Comments", type="RFC", number="1268", pages="1--13", year=1991, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1655", url="https://www.rfc-editor.org/rfc/rfc1268.txt", key="RFC 1268", abstract={This document describes the usage of the BGP in the Internet. [STANDARDS-TRACK]}, keywords="BGP3", doi="10.17487/RFC1268", } @misc{rfc1269, author="S. Willis and J.W. Burruss", title="{Definitions of Managed Objects for the Border Gateway Protocol: Version 3}", howpublished="RFC 1269 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1269", pages="1--13", year=1991, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 4273", url="https://www.rfc-editor.org/rfc/rfc1269.txt", key="RFC 1269", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Border Gateway Protocol. [STANDARDS-TRACK]}, keywords="BGP-MIB", doi="10.17487/RFC1269", } @misc{rfc1270, author="F. Kastenholz", title="{SNMP Communications Services}", howpublished="RFC 1270 (Informational)", series="Internet Request for Comments", type="RFC", number="1270", pages="1--11", year=1991, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1270.txt", key="RFC 1270", abstract={This document discusses various issues to be considered when determining the underlying communications services to be used by an SNMP implementation. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1270", } @misc{rfc1271, author="S. Waldbusser", title="{Remote Network Monitoring Management Information Base}", howpublished="RFC 1271 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1271", pages="1--81", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1757, updated by RFC 1513", url="https://www.rfc-editor.org/rfc/rfc1271.txt", key="RFC 1271", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK]}, doi="10.17487/RFC1271", } @misc{rfc1272, author="C. Mills and D. Hirsh and G.R. Ruth", title="{Internet Accounting: Background}", howpublished="RFC 1272 (Informational)", series="Internet Request for Comments", type="RFC", number="1272", pages="1--19", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1272.txt", key="RFC 1272", abstract={This document provides background information for the ``Internet Accounting Architecture''. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1272", } @misc{rfc1273, author="M.F. Schwartz", title="{Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations}", howpublished="RFC 1273 (Informational)", series="Internet Request for Comments", type="RFC", number="1273", pages="1--8", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1273.txt", key="RFC 1273", abstract={This memo describes plans to carry out a longitudinal measurement study of changes in service-level reachability in the global TCP/IP Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1273", } @misc{rfc1274, author="P. Barker and S. Kille", title="{The COSINE and Internet X.500 Schema}", howpublished="RFC 1274 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1274", pages="1--60", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 4524", url="https://www.rfc-editor.org/rfc/rfc1274.txt", key="RFC 1274", abstract={This document suggests an X.500 Directory Schema, or Naming Architecture, for use in the COSINE and Internet X.500 pilots. [STANDARDS-TRACK]}, keywords="Naming", doi="10.17487/RFC1274", } @misc{rfc1275, author="S.E. Hardcastle-Kille", title="{Replication Requirements to provide an Internet Directory using X.500}", howpublished="RFC 1275 (Informational)", series="Internet Request for Comments", type="RFC", number="1275", pages="1--3", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1275.txt", key="RFC 1275", abstract={This RFC considers certain deficiencies of the 1988 X.500 standard, which need to be addressed before an effective open Internet Directory can be established using these protocols and services [CCI88]. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1275", } @misc{rfc1276, author="S.E. Hardcastle-Kille", title="{Replication and Distributed Operations extensions to provide an Internet Directory using X.500}", howpublished="RFC 1276 (Historic)", series="Internet Request for Comments", type="RFC", number="1276", pages="1--17", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1276.txt", key="RFC 1276", abstract={Some requirements on extensions to X.500 are described in the RFC[HK91b], in order to build an Internet Directory using X.500(1988). This document specifies a set of solutions to the problems raised. [STANDARDS-TRACK]}, keywords="", doi="10.17487/RFC1276", } @misc{rfc1277, author="S.E. Hardcastle-Kille", title="{Encoding Network Addresses to Support Operation over Non-OSI Lower Layers}", howpublished="RFC 1277 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1277", pages="1--12", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1277.txt", key="RFC 1277", abstract={This document defines a new network address format, and rules for using some existing network address formats. [STANDARDS-TRACK]}, keywords="address ISO OSI", doi="10.17487/RFC1277", } @misc{rfc1278, author="S.E. Hardcastle-Kille", title="{A string encoding of Presentation Address}", howpublished="RFC 1278 (Informational)", series="Internet Request for Comments", type="RFC", number="1278", pages="1--7", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1278.txt", key="RFC 1278", abstract={There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="OSI, ASN.1", doi="10.17487/RFC1278", } @misc{rfc1279, author="S.E. Hardcastle-Kille", title="{X.500 and Domains}", howpublished="RFC 1279 (Experimental)", series="Internet Request for Comments", type="RFC", number="1279", pages="1--15", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1279.txt", key="RFC 1279", abstract={This RFC considers X.500 in relation to Internet and UK Domains. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="Domain, Name, naming", doi="10.17487/RFC1279", } @misc{rfc1280, author="J. Postel", title="{IAB Official Protocol Standards}", howpublished="RFC 1280 (Historic)", series="Internet Request for Comments", type="RFC", number="1280", pages="1--32", year=1992, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1360", url="https://www.rfc-editor.org/rfc/rfc1280.txt", key="RFC 1280", abstract={This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1280", } @misc{rfc1281, author="R. Pethia and S. Crocker and B. Fraser", title="{Guidelines for the Secure Operation of the Internet}", howpublished="RFC 1281 (Informational)", series="Internet Request for Comments", type="RFC", number="1281", pages="1--10", year=1991, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1281.txt", key="RFC 1281", abstract={The purpose of this document is to provide a set of guidelines to aid in the secure operation of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="security, privacy, protection, guideline", doi="10.17487/RFC1281", } @misc{rfc1282, author="B. Kantor", title="{BSD Rlogin}", howpublished="RFC 1282 (Informational)", series="Internet Request for Comments", type="RFC", number="1282", pages="1--5", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1282.txt", key="RFC 1282", abstract={This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="BSD Login, Unix, remote-login, remote-logon", doi="10.17487/RFC1282", } @misc{rfc1283, author="M. Rose", title="{SNMP over OSI}", howpublished="RFC 1283 (Experimental)", series="Internet Request for Comments", type="RFC", number="1283", pages="1--8", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1418", url="https://www.rfc-editor.org/rfc/rfc1283.txt", key="RFC 1283", abstract={This memo describes mappings from the SNMP onto both the COTS and the CLTS. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet Standard.}, keywords="ISO, Management, MIB", doi="10.17487/RFC1283", } @misc{rfc1284, author="J. Cook", title="{Definitions of Managed Objects for the Ethernet-like Interface Types}", howpublished="RFC 1284 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1284", pages="1--21", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1398", url="https://www.rfc-editor.org/rfc/rfc1284.txt", key="RFC 1284", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK]}, keywords="SNMP, MIB, Management", doi="10.17487/RFC1284", } @misc{rfc1285, author="J. Case", title="{FDDI Management Information Base}", howpublished="RFC 1285 (Historic)", series="Internet Request for Comments", type="RFC", number="1285", pages="1--46", year=1992, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 1512", url="https://www.rfc-editor.org/rfc/rfc1285.txt", key="RFC 1285", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI. [STANDARDS-TRACK]}, keywords="FDDI-MIB, standard, standards, MIB, SNMP", doi="10.17487/RFC1285", } @misc{rfc1286, author="E. Decker and P. Langille and A. Rijsinghani and K. McCloghrie", title="{Definitions of Managed Objects for Bridges}", howpublished="RFC 1286 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1286", pages="1--40", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1493, 1525", url="https://www.rfc-editor.org/rfc/rfc1286.txt", key="RFC 1286", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing bridges based on the IEEE 802.1d draft standard between Local Area Network (LAN) segments. This memo is an extension to the SNMP MIB. [STANDARDS-TRACK]}, keywords="SNMP, MIB, standard, standards", doi="10.17487/RFC1286", } @misc{rfc1287, author="D. Clark and L. Chapin and V. Cerf and R. Braden and R. Hobby", title="{Towards the Future Internet Architecture}", howpublished="RFC 1287 (Informational)", series="Internet Request for Comments", type="RFC", number="1287", pages="1--29", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1287.txt", key="RFC 1287", abstract={This informational RFC discusses important directions for possible future evolution of the Internet architecture, and suggests steps towards the desired goals. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1287", } @misc{rfc1288, author="D. Zimmerman", title="{The Finger User Information Protocol}", howpublished="RFC 1288 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1288", pages="1--12", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1288.txt", key="RFC 1288", abstract={This memo describes the Finger user information protocol.This is a simple protocol which provides an interface to a remote user information program. [STANDARDS-TRACK]}, keywords="FINGER", doi="10.17487/RFC1288", } @misc{rfc1289, author="J. Saperia", title="{DECnet Phase IV MIB Extensions}", howpublished="RFC 1289 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1289", pages="1--64", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1559", url="https://www.rfc-editor.org/rfc/rfc1289.txt", key="RFC 1289", abstract={This memo is an extension to the SNMP MIB. This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. [STANDARDS-TRACK]}, keywords="SNMP, Management, protocol, standard, standards", doi="10.17487/RFC1289", } @misc{rfc1290, author="J. Martin", title="{There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places}", howpublished="RFC 1290 (Informational)", series="Internet Request for Comments", type="RFC", number="1290", pages="1--27", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1402", url="https://www.rfc-editor.org/rfc/rfc1290.txt", key="RFC 1290", abstract={This paper will present some of the ``gold nuggets'' of information and file repositories on the network that could be of use to end users. This RFC provides information for the Internet community. It does not specify an Internet standard.}, keywords="SIGUCCS, User Services, Help, Internet", doi="10.17487/RFC1290", } @misc{rfc1291, author="V. Aggarwal", title="{Mid-Level Networks Potential Technical Services}", howpublished="RFC 1291 (Informational)", series="Internet Request for Comments", type="RFC", number="1291", pages="1--10", year=1991, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1291.txt", key="RFC 1291", abstract={This document proposes a set of technical services that each Internet mid-level network can offer within the mid-level network itself and and to its peer networks. This RFC provides information for the Internet community. It does not specify an Internet standard.}, keywords="statistics, connectivity, management", doi="10.17487/RFC1291", } @misc{rfc1292, author="R. Lang and R. Wright", title="{A Catalog of Available X.500 Implementations}", howpublished="RFC 1292 (Informational)", series="Internet Request for Comments", type="RFC", number="1292", pages="1--103", year=1992, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1632", url="https://www.rfc-editor.org/rfc/rfc1292.txt", key="RFC 1292", abstract={The goal of this document is to provide information regarding the availability and capability of implementations of X.500. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1292", } @misc{rfc1293, author="T. Bradley and C. Brown", title="{Inverse Address Resolution Protocol}", howpublished="RFC 1293 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1293", pages="1--6", year=1992, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2390", url="https://www.rfc-editor.org/rfc/rfc1293.txt", key="RFC 1293", abstract={This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]}, keywords="standard, standards, ARP, DLCI", doi="10.17487/RFC1293", } @misc{rfc1294, author="T. Bradley and C. Brown and A. Malis", title="{Multiprotocol Interconnect over Frame Relay}", howpublished="RFC 1294 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1294", pages="1--28", year=1992, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1490, 2427", url="https://www.rfc-editor.org/rfc/rfc1294.txt", key="RFC 1294", abstract={This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK]}, keywords="standard, standards", doi="10.17487/RFC1294", } @misc{rfc1295, author="The North American Directory Forum", title="{User Bill of Rights for entries and listings in the Public Directory}", howpublished="RFC 1295 (Informational)", series="Internet Request for Comments", type="RFC", number="1295", pages="1--2", year=1992, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1417", url="https://www.rfc-editor.org/rfc/rfc1295.txt", key="RFC 1295", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) objects. This document is a companion document with Definitions of Managed Objects for the DS1/E1 and DS3/E3 Interface Types, RFC1406 and RFC1407. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="NADF-265, NADF, X.500", doi="10.17487/RFC1295", } @misc{rfc1296, author="M. Lottor", title="{Internet Growth (1981-1991)}", howpublished="RFC 1296 (Informational)", series="Internet Request for Comments", type="RFC", number="1296", pages="1--9", year=1992, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1296.txt", key="RFC 1296", abstract={This document illustrates the growth of the Internet by examination of entries in the Domain Name System (DNS) and pre-DNS host tables. This memo provides information for the Internet community. It does not specify an Internet standard. This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service. [STANDARDS-TRACK]}, keywords="statistics, ZONE", doi="10.17487/RFC1296", } @misc{rfc1297, author="D. Johnson", title="{NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist (``NOC TT REQUIREMENTS'')}", howpublished="RFC 1297 (Informational)", series="Internet Request for Comments", type="RFC", number="1297", pages="1--12", year=1992, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1297.txt", key="RFC 1297", abstract={This document explores competing uses, architectures, and desirable features of integrated internal trouble ticket systems for Network and other Operations Centers. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="problems, tracking, operations, NOC", doi="10.17487/RFC1297", } @misc{rfc1298, author="R. Wormley and S. Bostock", title="{SNMP over IPX}", howpublished="RFC 1298 (Informational)", series="Internet Request for Comments", type="RFC", number="1298", pages="1--5", year=1992, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1420", url="https://www.rfc-editor.org/rfc/rfc1298.txt", key="RFC 1298", abstract={This memo defines a convention for encapsulating Simple Network Management Protocol (SNMP) packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1298", } @misc{rfc1299, author="M. Kennedy", title="{Summary of 1200-1299}", howpublished="RFC 1299 (Informational)", series="Internet Request for Comments", type="RFC", number="1299", pages="1--20", year=1997, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1299.txt", key="RFC 1299", keywords="Index", doi="10.17487/RFC1299", } @misc{rfc1300, author="S. Greenfield", title="{Remembrances of Things Past}", howpublished="RFC 1300 (Informational)", series="Internet Request for Comments", type="RFC", number="1300", pages="1--4", year=1992, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1300.txt", key="RFC 1300", abstract={Poem. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="poem", doi="10.17487/RFC1300", } @misc{rfc1301, author="S. Armstrong and A. Freier and K. Marzullo", title="{Multicast Transport Protocol}", howpublished="RFC 1301 (Informational)", series="Internet Request for Comments", type="RFC", number="1301", pages="1--38", year=1992, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1301.txt", key="RFC 1301", abstract={This memo describes a protocol for reliable transport that utilizes the multicast capability of applicable lower layer networking architectures. The transport definition permits an arbitrary number of transport providers to perform realtime collaborations without requiring networking clients (aka, applications) to possess detailed knowledge of the population or geographical dispersion of the participating members. It is not network architectural specific, but does implicitly require some form of multicasting (or broadcasting) at the data link level, as well as some means of communicating that capability up through the layers to the transport. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="MTP, MTP, reliable transport, multicast, broadcast, collaboration, networking", doi="10.17487/RFC1301", } @misc{rfc1302, author="D. Sitzler and P. Smith and A. Marine", title="{Building a Network Information Services Infrastructure}", howpublished="RFC 1302 (Informational)", series="Internet Request for Comments", type="RFC", number="1302", pages="1--13", year=1992, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1302.txt", key="RFC 1302", abstract={This FYI RFC document is intended for existing Internet Network Information Center (NIC) personnel, people interested in establishing a new NIC, Internet Network Operations Centers (NOCs), and funding agencies interested in contributing to user support facilities. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="NISI, NIC, User Services", doi="10.17487/RFC1302", } @misc{rfc1303, author="K. McCloghrie and M. Rose", title="{A Convention for Describing SNMP-based Agents}", howpublished="RFC 1303 (Informational)", series="Internet Request for Comments", type="RFC", number="1303", pages="1--12", year=1992, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1303.txt", key="RFC 1303", abstract={This memo suggests a straight-forward approach towards describing SNMP- based agents. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="SNMP, MIB, Network Management,", doi="10.17487/RFC1303", } @misc{rfc1304, author="T. Cox and K. Tesink", title="{Definitions of Managed Objects for the SIP Interface Type}", howpublished="RFC 1304 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1304", pages="1--25", year=1992, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1694", url="https://www.rfc-editor.org/rfc/rfc1304.txt", key="RFC 1304", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing SIP (SMDS Interface Protocol) objects. [STANDARDS-TRACK]}, keywords="Standard, MIB, Network Management, SMDS", doi="10.17487/RFC1304", } @misc{rfc1305, author="D. Mills", title="{Network Time Protocol (Version 3) Specification, Implementation and Analysis}", howpublished="RFC 1305 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1305", pages="1--109", year=1992, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 5905", url="https://www.rfc-editor.org/rfc/rfc1305.txt", key="RFC 1305", abstract={This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. [STANDARDS-TRACK]}, keywords="NTPV3, NTP", doi="10.17487/RFC1305", } @misc{rfc1306, author="A. Nicholson and J. Young", title="{Experiences Supporting By-Request Circuit-Switched T3 Networks}", howpublished="RFC 1306 (Informational)", series="Internet Request for Comments", type="RFC", number="1306", pages="1--10", year=1992, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1306.txt", key="RFC 1306", abstract={This memo describes the experiences of a project team at Cray Research, Inc., in implementing support for circuit-switched T3 services. While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementers. This RFC provides information for the Internet community. It does not specify an Internet standard.}, keywords="WAN, Wide Area Net, FDDI", doi="10.17487/RFC1306", } @misc{rfc1307, author="J. Young and A. Nicholson", title="{Dynamically Switched Link Control Protocol}", howpublished="RFC 1307 (Experimental)", series="Internet Request for Comments", type="RFC", number="1307", pages="1--13", year=1992, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1307.txt", key="RFC 1307", abstract={This memo describes an experimental protocol developed by a project team at Cray Research, Inc., in implementing support for circuit-switched T3 services. The protocol is used for the control of network connections external to a host, but known to the host. This memo defines an Experimental Protocol for the Internet community.}, keywords="DSLCP, Experimental Protocol, T3, FDDI", doi="10.17487/RFC1307", } @misc{rfc1308, author="C. Weider and J. Reynolds", title="{Executive Introduction to Directory Services Using the X.500 Protocol}", howpublished="RFC 1308 (Informational)", series="Internet Request for Comments", type="RFC", number="1308", pages="1--4", year=1992, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1308.txt", key="RFC 1308", abstract={This document is an Executive Introduction to Directory Services using the X.500 protocol. It briefly discusses the deficiencies in currently deployed Internet Directory Services, and then illustrates the solutions provided by X.500. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1308", } @misc{rfc1309, author="C. Weider and J. Reynolds and S. Heker", title="{Technical Overview of Directory Services Using the X.500 Protocol}", howpublished="RFC 1309 (Informational)", series="Internet Request for Comments", type="RFC", number="1309", pages="1--16", year=1992, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1309.txt", key="RFC 1309", abstract={This document is an overview of the X.500 standard for people not familiar with the technology. It compares and contrasts Directory Services based on X.500 with several of the other Directory services currently in use in the Internet. This paper also describes the status of the standard and provides references for further information on X.500 implementations and technical information. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1309", } @misc{rfc1310, author="L. Chapin", title="{The Internet Standards Process}", howpublished="RFC 1310 (Informational)", series="Internet Request for Comments", type="RFC", number="1310", pages="1--23", year=1992, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1602", url="https://www.rfc-editor.org/rfc/rfc1310.txt", key="RFC 1310", abstract={This memo documents the process currently used for the standardization of Internet protocols and procedures. [STANDARDS-TRACK]}, doi="10.17487/RFC1310", } @misc{rfc1311, author="J. Postel", title="{Introduction to the STD Notes}", howpublished="RFC 1311 (Informational)", series="Internet Request for Comments", type="RFC", number="1311", pages="1--5", year=1992, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1311.txt", key="RFC 1311", abstract={The STDs are a subseries of notes within the RFC series that are the Internet standards. The intent is to identify clearly for the Internet community those RFCs which document Internet standards. [STANDARDS-TRACK]}, keywords="new, IAB", doi="10.17487/RFC1311", } @misc{rfc1312, author="R. Nelson and G. Arnold", title="{Message Send Protocol 2}", howpublished="RFC 1312 (Experimental)", series="Internet Request for Comments", type="RFC", number="1312", pages="1--8", year=1992, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1312.txt", key="RFC 1312", abstract={The Message Send Protocol is used to send a short message to a given user on a given terminal on a given host. This memo defines an Experimental Protocol for the Internet community.}, keywords="MSP2, MSP, talk", doi="10.17487/RFC1312", } @misc{rfc1313, author="C. Partridge", title="{Today's Programming for KRFC AM 1313 Internet Talk Radio}", howpublished="RFC 1313 (Informational)", series="Internet Request for Comments", type="RFC", number="1313", pages="1--3", year=1992, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1313.txt", key="RFC 1313", abstract={Hi and welcome to KRFC Internet Talk Radio, your place on the AM dial for lively talk and just-breaking news on internetworking. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1313", } @misc{rfc1314, author="A. Katz and D. Cohen", title="{A File Format for the Exchange of Images in the Internet}", howpublished="RFC 1314 (Historic)", series="Internet Request for Comments", type="RFC", number="1314", pages="1--23", year=1992, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1314.txt", key="RFC 1314", abstract={This document defines a standard file format for the exchange of fax- like black and white images within the Internet. [STANDARDS-TRACK]}, keywords="NETFAX, netfax, TIFF, facsimile", doi="10.17487/RFC1314", } @misc{rfc1315, author="C. Brown and F. Baker and C. Carvalho", title="{Management Information Base for Frame Relay DTEs}", howpublished="RFC 1315 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1315", pages="1--19", year=1992, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2115", url="https://www.rfc-editor.org/rfc/rfc1315.txt", key="RFC 1315", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Frame Relay. [STANDARDS-TRACK]}, keywords="MIB", doi="10.17487/RFC1315", } @misc{rfc1316, author="B. Stewart", title="{Definitions of Managed Objects for Character Stream Devices}", howpublished="RFC 1316 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1316", pages="1--17", year=1992, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1658", url="https://www.rfc-editor.org/rfc/rfc1316.txt", key="RFC 1316", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for the management of character stream devices. [STANDARDS-TRACK]}, keywords="MIB", doi="10.17487/RFC1316", } @misc{rfc1317, author="B. Stewart", title="{Definitions of Managed Objects for RS-232-like Hardware Devices}", howpublished="RFC 1317 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1317", pages="1--17", year=1992, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1659", url="https://www.rfc-editor.org/rfc/rfc1317.txt", key="RFC 1317", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of RS-232-like devices. [STANDARDS-TRACK]}, keywords="MIB", doi="10.17487/RFC1317", } @misc{rfc1318, author="B. Stewart", title="{Definitions of Managed Objects for Parallel-printer-like Hardware Devices}", howpublished="RFC 1318 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1318", pages="1--11", year=1992, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1660", url="https://www.rfc-editor.org/rfc/rfc1318.txt", key="RFC 1318", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of parallel-printer- like devices. [STANDARDS-TRACK]}, keywords="MIB", doi="10.17487/RFC1318", } @misc{rfc1319, author="B. Kaliski", title="{The MD2 Message-Digest Algorithm}", howpublished="RFC 1319 (Historic)", series="Internet Request for Comments", type="RFC", number="1319", pages="1--17", year=1992, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 6149", url="https://www.rfc-editor.org/rfc/rfc1319.txt", key="RFC 1319", abstract={This document describes the MD2 message-digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit ``fingerprint'' or ``message digest'' of the input. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="security, encryption, signature", doi="10.17487/RFC1319", } @misc{rfc1320, author="R. Rivest", title="{The MD4 Message-Digest Algorithm}", howpublished="RFC 1320 (Historic)", series="Internet Request for Comments", type="RFC", number="1320", pages="1--20", year=1992, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 6150", url="https://www.rfc-editor.org/rfc/rfc1320.txt", key="RFC 1320", abstract={This document describes the MD4 message-digest algorithm [1]. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit ``fingerprint'' or ``message digest'' of the input. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="MD4, security, encryption, signature", doi="10.17487/RFC1320", } @misc{rfc1321, author="R. Rivest", title="{The MD5 Message-Digest Algorithm}", howpublished="RFC 1321 (Informational)", series="Internet Request for Comments", type="RFC", number="1321", pages="1--21", year=1992, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 6151", url="https://www.rfc-editor.org/rfc/rfc1321.txt", key="RFC 1321", abstract={This document describes the MD5 message-digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit ``fingerprint'' or ``message digest'' of the input. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="security, signature, eneryption", doi="10.17487/RFC1321", } @misc{rfc1322, author="D. Estrin and Y. Rekhter and S. Hotz", title="{A Unified Approach to Inter-Domain Routing}", howpublished="RFC 1322 (Informational)", series="Internet Request for Comments", type="RFC", number="1322", pages="1--38", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1322.txt", key="RFC 1322", abstract={This memo is an informational RFC which outlines one potential approach for inter-domain routing in future global internets. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="path, vector, routing, source, demand, routing", doi="10.17487/RFC1322", } @misc{rfc1323, author="V. Jacobson and R. Braden and D. Borman", title="{TCP Extensions for High Performance}", howpublished="RFC 1323 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1323", pages="1--37", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 7323", url="https://www.rfc-editor.org/rfc/rfc1323.txt", key="RFC 1323", abstract={This memo presents a set of TCP extensions to improve performance over large bandwidth*delay product paths and to provide reliable operation over very high-speed paths. It defines new TCP options for scaled windows and timestamps, which are designed to provide compatible interworking with TCP's that do not implement the extensions. [STANDARDS-TRACK]}, keywords="TCP-EXT, options, PAWS, window, scale, window", doi="10.17487/RFC1323", } @misc{rfc1324, author="D. Reed", title="{A Discussion on Computer Network Conferencing}", howpublished="RFC 1324 (Informational)", series="Internet Request for Comments", type="RFC", number="1324", pages="1--11", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1324.txt", key="RFC 1324", abstract={This memo is intended to make more people aware of the present developments in the Computer Conferencing field as well as put forward ideas on what should be done to formalize this work so that there is a common standard for programmers and others who are involved in this field to work with. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="talk, real time, chat", doi="10.17487/RFC1324", } @misc{rfc1325, author="G. Malkin and A. Marine", title="{FYI on Questions and Answers Answers to Commonly asked ``New Internet User'' Questions}", howpublished="RFC 1325 (Informational)", series="Internet Request for Comments", type="RFC", number="1325", pages="1--42", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1594", url="https://www.rfc-editor.org/rfc/rfc1325.txt", key="RFC 1325", abstract={This FYI RFC is one of two FYI's called, ``Questions and Answers'' (Q/A), produced by the User Services Working Group 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 an Internet standard.}, keywords="documentation, help, information", doi="10.17487/RFC1325", } @misc{rfc1326, author="P. Tsuchiya", title="{Mutual Encapsulation Considered Dangerous}", howpublished="RFC 1326 (Informational)", series="Internet Request for Comments", type="RFC", number="1326", pages="1--5", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1326.txt", key="RFC 1326", abstract={This memo describes a packet explosion problem that can occur with mutual encapsulation of protocols (A encapsulates B and B encapsulates A). This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="protocol, layering, wrapping", doi="10.17487/RFC1326", } @misc{rfc1327, author="S. Hardcastle-Kille", title="{Mapping between X.400(1988) / ISO 10021 and RFC 822}", howpublished="RFC 1327 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1327", pages="1--113", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2156, updated by RFC 1495", url="https://www.rfc-editor.org/rfc/rfc1327.txt", key="RFC 1327", abstract={This document specifies a mapping between two protocols. This specification should be used when this mapping is performed on the DARPA Internet or in the UK Academic Community. This specification may be modified in the light of implementation experience, but no substantial changes are expected. [STANDARDS-TRACK]}, keywords="Electronic-mail,Message handling systems", doi="10.17487/RFC1327", } @misc{rfc1328, author="S. Hardcastle-Kille", title="{X.400 1988 to 1984 downgrading}", howpublished="RFC 1328 (Historic)", series="Internet Request for Comments", type="RFC", number="1328", pages="1--5", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1328.txt", key="RFC 1328", abstract={This document considers issues of downgrading from X.400(1988) to X.400(1984) [MHS88a, MHS84]. Annexe B of X.419 specifies some downgrading rules [MHS88b], but these are not sufficient for provision of service in an environment containing both 1984 and 1988 components. This document defines a number of extensions to this annexe. [STANDARDS-TRACK]}, keywords="Electronic-mail, message handling systems,mail", doi="10.17487/RFC1328", } @misc{rfc1329, author="P. Kuehn", title="{Thoughts on Address Resolution for Dual MAC FDDI Networks}", howpublished="RFC 1329 (Informational)", series="Internet Request for Comments", type="RFC", number="1329", pages="1--28", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 5494", url="https://www.rfc-editor.org/rfc/rfc1329.txt", key="RFC 1329", abstract={In this document an idea is submitted how IP and ARP can be used on inhomogeneous FDDI networks (FDDI networks with single MAC and dual MAC stations) by introducing a new protocol layer in the protocol suite of the dual MAC stations. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1329", } @misc{rfc1330, author="ESCC X.500/X.400 Task Force and ESnet Site Coordinating Comittee (ESCC) and Energy Sciences Network (ESnet)", title="{Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESNET Community}", howpublished="RFC 1330 (Informational)", series="Internet Request for Comments", type="RFC", number="1330", pages="1--87", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1330.txt", key="RFC 1330", abstract={This RFC is a near verbatim copy of the whitepaper produced by the ESnet Site Coordinating Committee's X.500/X.400 Task Force. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1330", } @misc{rfc1331, author="W. Simpson", title="{The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links}", howpublished="RFC 1331 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1331", pages="1--69", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1548", url="https://www.rfc-editor.org/rfc/rfc1331.txt", key="RFC 1331", abstract={This document defines the PPP encapsulation scheme, together with the PPP Link Control Protocol (LCP), an extensible option negotiation protocol which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS-TRACK]}, keywords="serial line, IP over serial, dial-up", doi="10.17487/RFC1331", } @misc{rfc1332, author="G. McGregor", title="{The PPP Internet Protocol Control Protocol (IPCP)}", howpublished="RFC 1332 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1332", pages="1--14", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 3241", url="https://www.rfc-editor.org/rfc/rfc1332.txt", key="RFC 1332", abstract={The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. [STANDARDS-TRACK]}, keywords="PPP-IPCP, serial line, IP over serial, dial-up", doi="10.17487/RFC1332", } @misc{rfc1333, author="W. Simpson", title="{PPP Link Quality Monitoring}", howpublished="RFC 1333 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1333", pages="1--17", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1989", url="https://www.rfc-editor.org/rfc/rfc1333.txt", key="RFC 1333", abstract={The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of a Quality Protocol for continuous monitoring of the viability of the link. [STANDARDS-TRACK]}, keywords="serial line, IP over serial, dial-up", doi="10.17487/RFC1333", } @misc{rfc1334, author="B. Lloyd and W. Simpson", title="{PPP Authentication Protocols}", howpublished="RFC 1334 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1334", pages="1--16", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1994", url="https://www.rfc-editor.org/rfc/rfc1334.txt", key="RFC 1334", abstract={This document defines two protocols for Authentication: the Password Authentication Protocol and the Challenge-Handshake Authentication Protocol. [STANDARDS-TRACK]}, keywords="point, serial, line, dial-up", doi="10.17487/RFC1334", } @misc{rfc1335, author="Z. Wang and J. Crowcroft", title="{A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion}", howpublished="RFC 1335 (Informational)", series="Internet Request for Comments", type="RFC", number="1335", pages="1--7", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1335.txt", key="RFC 1335", abstract={This RFC presents a solution to problem of address space exhaustion in the Internet. It proposes a two-tier address structure for the Internet. This is an ``idea'' paper and discussion is strongly encouraged. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="internet, protocol, IP", doi="10.17487/RFC1335", } @misc{rfc1336, author="G. Malkin", title="{Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members}", howpublished="RFC 1336 (Informational)", series="Internet Request for Comments", type="RFC", number="1336", pages="1--33", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1336.txt", key="RFC 1336", abstract={This FYI RFC contains biographical information about members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify any standard.}, keywords="Almquist, Braden, Braun, Callon, Cerf, Chiappa, Chapin, Clark, Crocker, Davin, Estrin, Hobby, Huitema, Huizer, Kent, Lauck, Leiner, Lynch, Piscitello, Postel, Reynolds, Schwartz, Stockman, Vaudreuil", doi="10.17487/RFC1336", } @misc{rfc1337, author="R. Braden", title="{TIME-WAIT Assassination Hazards in TCP}", howpublished="RFC 1337 (Informational)", series="Internet Request for Comments", type="RFC", number="1337", pages="1--11", year=1992, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1337.txt", key="RFC 1337", abstract={This note describes some theoretically-possible failure modes for TCP connections and discusses possible remedies. In particular, one very simple fix is identified. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="TCP protocol, protocol state, graceful close, reset", doi="10.17487/RFC1337", } @misc{rfc1338, author="V. Fuller and T. Li and J. Yu and K. Varadhan", title="{Supernetting: an Address Assignment and Aggregation Strategy}", howpublished="RFC 1338 (Informational)", series="Internet Request for Comments", type="RFC", number="1338", pages="1--20", year=1992, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1519", url="https://www.rfc-editor.org/rfc/rfc1338.txt", key="RFC 1338", abstract={This memo discusses strategies for address assignment of the existing IP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers run by transit routing domain providers. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="internet address, routing", doi="10.17487/RFC1338", } @misc{rfc1339, author="S. Dorner and P. Resnick", title="{Remote Mail Checking Protocol}", howpublished="RFC 1339 (Experimental)", series="Internet Request for Comments", type="RFC", number="1339", pages="1--6", year=1992, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1339.txt", key="RFC 1339", abstract={This RFC defines a protocol to provide a mail checking service to be used between a client and server pair. Typically, a small program on a client workstation would use the protocol to query a server in order to find out whether new mail has arrived for a specified user. This memo defines an Experimental Protocol for the Internet community.}, keywords="RMCP, email, remote mail", doi="10.17487/RFC1339", } @misc{rfc1340, author="J. Reynolds and J. Postel", title="{Assigned Numbers}", howpublished="RFC 1340 (Historic)", series="Internet Request for Comments", type="RFC", number="1340", pages="1--139", year=1992, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1700", url="https://www.rfc-editor.org/rfc/rfc1340.txt", key="RFC 1340", 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 a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community.}, doi="10.17487/RFC1340", } @misc{rfc1341, author="N. Borenstein and N. Freed", title="{MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies}", howpublished="RFC 1341 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1341", pages="1--80", year=1992, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1521", url="https://www.rfc-editor.org/rfc/rfc1341.txt", key="RFC 1341", abstract={This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. [STANDARDS-TRACK]}, keywords="EMail, Multimedia", doi="10.17487/RFC1341", } @misc{rfc1342, author="K. Moore", title="{Representation of Non-ASCII Text in Internet Message Headers}", howpublished="RFC 1342 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1342", pages="1--7", year=1992, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1522", url="https://www.rfc-editor.org/rfc/rfc1342.txt", key="RFC 1342", abstract={This memo describes an extension to the message format defined in [1] (known to the IETF Mail Extensions Working Group as ``RFC 1341''), to allow the representation of character sets other than ASCII in RFC 822 message headers. [STANDARDS-TRACK]}, keywords="EMail, Character Sets", doi="10.17487/RFC1342", } @misc{rfc1343, author="N. Borenstein", title="{A User Agent Configuration Mechanism for Multimedia Mail Format Information}", howpublished="RFC 1343 (Informational)", series="Internet Request for Comments", type="RFC", number="1343", pages="1--10", year=1992, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1343.txt", key="RFC 1343", abstract={This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="EMail, Multimedia", doi="10.17487/RFC1343", } @misc{rfc1344, author="N. Borenstein", title="{Implications of MIME for Internet Mail Gateways}", howpublished="RFC 1344 (Informational)", series="Internet Request for Comments", type="RFC", number="1344", pages="1--9", year=1992, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1344.txt", key="RFC 1344", abstract={While MIME was carefully designed so that it does not require any changes to Internet electronic message transport facilities, there are several ways in which message transport systems may want to take advantage of MIME. These opportunities are the subject of this memo. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="EMail, Forwarding, Relaying, Fragmentation, Multimedia", doi="10.17487/RFC1344", } @misc{rfc1345, author="K. Simonsen", title="{Character Mnemonics and Character Sets}", howpublished="RFC 1345 (Informational)", series="Internet Request for Comments", type="RFC", number="1345", pages="1--103", year=1992, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1345.txt", key="RFC 1345", abstract={This memo lists a selection of characters and their presence in some coded character sets. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1345", } @misc{rfc1346, author="P. Jones", title="{Resource Allocation, Control, and Accounting for the Use of Network Resources}", howpublished="RFC 1346 (Informational)", series="Internet Request for Comments", type="RFC", number="1346", pages="1--6", year=1992, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1346.txt", key="RFC 1346", abstract={The purpose of this RFC is to focus discussion on particular challenges in large service networks in general, and the International IP Internet in particular. No solution discussed in this document is intended as a standard. Rather, it is hoped that a general consensus will emerge as to the appropriate solutions, leading eventually to the adoption of standards. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1346", } @misc{rfc1347, author="R. Callon", title="{TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing}", howpublished="RFC 1347 (Informational)", series="Internet Request for Comments", type="RFC", number="1347", pages="1--8", year=1992, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1347.txt", key="RFC 1347", abstract={This paper describes a simple proposal which provides a long-term solution to Internet addressing, routing, and scaling. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1347", } @misc{rfc1348, author="B. Manning", title="{DNS NSAP RRs}", howpublished="RFC 1348 (Experimental)", series="Internet Request for Comments", type="RFC", number="1348", pages="1--4", year=1992, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1637", url="https://www.rfc-editor.org/rfc/rfc1348.txt", key="RFC 1348", abstract={This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and reserves corresponding DNS type mnemonic and numerical codes. This memo defines an Experimental Protocol for the Internet community.}, keywords="domain names, CLNP, resource records", doi="10.17487/RFC1348", } @misc{rfc1349, author="P. Almquist", title="{Type of Service in the Internet Protocol Suite}", howpublished="RFC 1349 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1349", pages="1--28", year=1992, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2474", url="https://www.rfc-editor.org/rfc/rfc1349.txt", key="RFC 1349", abstract={This memo changes and clarifies some aspects of the semantics of the Type of Service octet in the Internet Protocol (IP) header. [STANDARDS-TRACK]}, keywords="TOS, TOS, IP", doi="10.17487/RFC1349", } @misc{rfc1350, author="K. Sollins", title="{The TFTP Protocol (Revision 2)}", howpublished="RFC 1350 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1350", pages="1--11", year=1992, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 1782, 1783, 1784, 1785, 2347, 2348, 2349", url="https://www.rfc-editor.org/rfc/rfc1350.txt", key="RFC 1350", abstract={TFTP is a very simple protocol used to transfer files. It is from this that its name comes, Trivial File Transfer Protocol or TFTP. Each nonterminal packet is acknowledged separately. This document describes the protocol and its types of packets. The document also explains the reasons behind some of the design decisions. [STANDARDS-TRACK]}, keywords="TFTP, trivial, file, transfer, booting", doi="10.17487/RFC1350", } @misc{rfc1351, author="J. Davin and J. Galvin and K. McCloghrie", title="{SNMP Administrative Model}", howpublished="RFC 1351 (Historic)", series="Internet Request for Comments", type="RFC", number="1351", pages="1--35", year=1992, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1351.txt", key="RFC 1351", abstract={This memo presents an elaboration of the SNMP administrative model set forth in [1]. This model provides a unified conceptual basis for administering SNMP protocol entities to support: authenticaiton and integrity, privacy, access control, and cooperation of protocol entities. [STANDARDS-TRACK]}, keywords="SNMP-ADMIN, network, management, authentication", doi="10.17487/RFC1351", } @misc{rfc1352, author="J. Galvin and K. McCloghrie and J. Davin", title="{SNMP Security Protocols}", howpublished="RFC 1352 (Historic)", series="Internet Request for Comments", type="RFC", number="1352", pages="1--41", year=1992, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1352.txt", key="RFC 1352", abstract={The Simple Network Management Protocol (SNMP) specification [1] allows for the protection of network management operations by a variety of security protocols. The SNMP administrative model described in [2] provides a framework for securing SNMP network management. In the context of that framework, this memo defines protocols to support the following three security services: data integrity, data origin authentication and data confidentiality. [STANDARDS-TRACK]}, keywords="SNMP-SEC, network, management, authentication", doi="10.17487/RFC1352", } @misc{rfc1353, author="K. McCloghrie and J. Davin and J. Galvin", title="{Definitions of Managed Objects for Administration of SNMP Parties}", howpublished="RFC 1353 (Historic)", series="Internet Request for Comments", type="RFC", number="1353", pages="1--26", year=1992, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1353.txt", key="RFC 1353", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes a representation of the SNMP parties defined in [8] as objects defined according to the Internet Standard SMI [1]. [STANDARDS-TRACK]}, keywords="SNMP-PARTY-MIB, network, management, authentication", doi="10.17487/RFC1353", } @misc{rfc1354, author="F. Baker", title="{IP Forwarding Table MIB}", howpublished="RFC 1354 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1354", pages="1--12", year=1992, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2096", url="https://www.rfc-editor.org/rfc/rfc1354.txt", key="RFC 1354", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing routes in the IP Internet. [STANDARDS-TRACK]}, keywords="Network, Management, Route, Table", doi="10.17487/RFC1354", } @misc{rfc1355, author="J. Curran and A. Marine", title="{Privacy and Accuracy Issues in Network Information Center Databases}", howpublished="RFC 1355 (Informational)", series="Internet Request for Comments", type="RFC", number="1355", pages="1--4", year=1992, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1355.txt", key="RFC 1355", abstract={This document provides a set of guidelines for the administration and operation of public Network Information Center (NIC) databases. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="NIC, data, privacy, accuracy", doi="10.17487/RFC1355", } @misc{rfc1356, author="A. Malis and D. Robinson and R. Ullmann", title="{Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode}", howpublished="RFC 1356 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1356", pages="1--14", year=1992, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1356.txt", key="RFC 1356", abstract={This document specifies the encapsulation of IP and other network layer protocols over X.25 networks, in accordance and alignment with ISO/IEC and CCITT standards. It is a replacement for RFC 877, ``A Standard for the Transmission of IP Datagrams Over Public Data Networks'' [1]. [STANDARDS-TRACK]}, keywords="IP-X.25, IP, on, X.25", doi="10.17487/RFC1356", } @misc{rfc1357, author="D. Cohen", title="{A Format for E-mailing Bibliographic Records}", howpublished="RFC 1357 (Informational)", series="Internet Request for Comments", type="RFC", number="1357", pages="1--13", year=1992, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1807", url="https://www.rfc-editor.org/rfc/rfc1357.txt", key="RFC 1357", abstract={This memo defines a format for E-mailing bibliographic records of technical reports. It is intended to accelerate the dissemination of information about new Computer Science Technical Reports (CS-TR). This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="library, technical, reports, email, services", doi="10.17487/RFC1357", } @misc{rfc1358, author="L. Chapin", title="{Charter of the Internet Architecture Board (IAB)}", howpublished="RFC 1358 (Informational)", series="Internet Request for Comments", type="RFC", number="1358", pages="1--5", year=1992, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1601", url="https://www.rfc-editor.org/rfc/rfc1358.txt", key="RFC 1358", abstract={The Internet Architecture Board (IAB) shall be constituted and shall operate as a technical advisory group of the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="ISOC, Internet, Society, IETF, IRTF", doi="10.17487/RFC1358", } @misc{rfc1359, author="ACM SIGUCCS", title="{Connecting to the Internet - What Connecting Institutions Should Anticipate}", howpublished="RFC 1359 (Informational)", series="Internet Request for Comments", type="RFC", number="1359", pages="1--25", year=1992, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1359.txt", key="RFC 1359", abstract={This FYI RFC outlines the major issues an institution should consider in the decision and implementation of a campus connection to the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Internet, access", doi="10.17487/RFC1359", } @misc{rfc1360, author="J. Postel", title="{IAB Official Protocol Standards}", howpublished="RFC 1360 (Historic)", series="Internet Request for Comments", type="RFC", number="1360", pages="1--33", year=1992, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1410", url="https://www.rfc-editor.org/rfc/rfc1360.txt", key="RFC 1360", keywords="proposed, draft, experimental, informational, historic, full", doi="10.17487/RFC1360", } @misc{rfc1361, author="D. Mills", title="{Simple Network Time Protocol (SNTP)}", howpublished="RFC 1361 (Informational)", series="Internet Request for Comments", type="RFC", number="1361", pages="1--10", year=1992, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1769", url="https://www.rfc-editor.org/rfc/rfc1361.txt", key="RFC 1361", abstract={This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memorandum does not obsolete or update any RFC. This memo provides information for the Internet community. It does not specify an Internet standard. Discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.9 contain the lists of protocols in each stage of standardization. Finally come pointers to references and contacts for further information. [STANDARDS-TRACK]}, keywords="Clocks, Synchronization, NTP", doi="10.17487/RFC1361", } @misc{rfc1362, author="M. Allen", title="{Novell IPX over Various WAN Media (IPXWAN)}", howpublished="RFC 1362 (Informational)", series="Internet Request for Comments", type="RFC", number="1362", pages="1--13", year=1992, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1634", url="https://www.rfc-editor.org/rfc/rfc1362.txt", key="RFC 1362", abstract={This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common ``IPX WAN'' protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="IPX on X.25, IPX on PPP, IPX on Frame Relay", doi="10.17487/RFC1362", } @misc{rfc1363, author="C. Partridge", title="{A Proposed Flow Specification}", howpublished="RFC 1363 (Informational)", series="Internet Request for Comments", type="RFC", number="1363", pages="1--20", year=1992, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1363.txt", key="RFC 1363", keywords="flow, spec, resource, reservation, stream, type of service, quality of service", doi="10.17487/RFC1363", } @misc{rfc1364, author="K. Varadhan", title="{BGP OSPF Interaction}", howpublished="RFC 1364 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1364", pages="1--14", year=1992, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1403", url="https://www.rfc-editor.org/rfc/rfc1364.txt", key="RFC 1364", keywords="autonomous, system, border, router, open, shortest, path, first, routing, protocol, domain, route, exchange, exporting, importing", doi="10.17487/RFC1364", } @misc{rfc1365, author="K. Siyan", title="{An IP Address Extension Proposal}", howpublished="RFC 1365 (Informational)", series="Internet Request for Comments", type="RFC", number="1365", pages="1--6", year=1992, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1365.txt", key="RFC 1365", keywords="class F addresses", doi="10.17487/RFC1365", } @misc{rfc1366, author="E. Gerich", title="{Guidelines for Management of IP Address Space}", howpublished="RFC 1366 (Informational)", series="Internet Request for Comments", type="RFC", number="1366", pages="1--8", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1466", url="https://www.rfc-editor.org/rfc/rfc1366.txt", key="RFC 1366", abstract={This document has been reviewed by the Federal Engineering Task Force (FEPG) on behalf of the Federal Networking Council (FNC), the co-chairs of the International Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space. This memo provides information for the Internet community. It does not specify an Internet standard. This RFC suggests an extension to the IP protocol to solve the shortage of IP address problem, and requests discussion and suggestions for improvements. This memo provides information for the Internet community. It does not specify an Internet standard. This memo defines the various criteria to be used when designing Autonomous System Border Routers (ASBR) that will run BGP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK] 1363 Partridge Spt 92 A Proposed Flow Specification The flow specification defined in this memo is intended for information and possible experimentation (i.e., experimental use by consenting routers and applications only). This RFC is a product of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="routing, tables, allocation, registry, IR, IANA", doi="10.17487/RFC1366", } @misc{rfc1367, author="C. Topolcic", title="{Schedule for IP Address Space Management Guidelines}", howpublished="RFC 1367 (Informational)", series="Internet Request for Comments", type="RFC", number="1367", pages="1--3", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1467", url="https://www.rfc-editor.org/rfc/rfc1367.txt", key="RFC 1367", abstract={This memo suggests a schedule for the implementation of the IP network number allocation plan described in RFC 1366. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="routing, tables, allocation, registry, IR, IANA", doi="10.17487/RFC1367", } @misc{rfc1368, author="D. McMaster and K. McCloghrie", title="{Definition of Managed Objects for IEEE 802.3 Repeater Devices}", howpublished="RFC 1368 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1368", pages="1--40", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1516", url="https://www.rfc-editor.org/rfc/rfc1368.txt", key="RFC 1368", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing IEEE 802.3 10 Mb/second baseband repeaters, sometimes referred to as ``hubs''. [STANDARDS-TRACK]}, keywords="MIB, hub, management", doi="10.17487/RFC1368", } @misc{rfc1369, author="F. Kastenholz", title="{Implementation Notes and Experience for the Internet Ethernet MIB}", howpublished="RFC 1369 (Informational)", series="Internet Request for Comments", type="RFC", number="1369", pages="1--7", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1369.txt", key="RFC 1369", abstract={This document reflects the currently known status of 11 different implementations of the MIB by 7 different vendors on 7 different Ethernet interface chips. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="management", doi="10.17487/RFC1369", } @misc{rfc1370, author="Internet Architecture Board and L. Chapin", title="{Applicability Statement for OSPF}", howpublished="RFC 1370 (Historic)", series="Internet Request for Comments", type="RFC", number="1370", pages="1--2", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1370.txt", key="RFC 1370", abstract={This Applicability Statement places a requirement on vendors claiming conformance to this standard, in order to assure that users will have the option of deploying OSPF when they need a multivendor, interoperable IGP in their environment. [STANDARDS-TRACK]}, keywords="routing, open, shortest, path, first", doi="10.17487/RFC1370", } @misc{rfc1371, author="P. Gross", title="{Choosing a Common IGP for the IP Internet}", howpublished="RFC 1371 (Informational)", series="Internet Request for Comments", type="RFC", number="1371", pages="1--9", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1371.txt", key="RFC 1371", abstract={This memo presents motivation, rationale and other surrounding background information leading to the IESG's recommendation to the IAB for a single ``common IGP'' for the IP portions of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="routing, recommendation, interior, gateway, protocol", doi="10.17487/RFC1371", } @misc{rfc1372, author="C. Hedrick and D. Borman", title="{Telnet Remote Flow Control Option}", howpublished="RFC 1372 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1372", pages="1--6", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1372.txt", key="RFC 1372", abstract={This document specifies an extended version of the Telnet Remote Flow Control Option, RFC 1080, with the addition of the RESTART-ANY and RESTART-XON suboptions. [STANDARDS-TRACK]}, keywords="TOPT-RFC, terminal, access", doi="10.17487/RFC1372", } @misc{rfc1373, author="T. Tignor", title="{Portable DUAs}", howpublished="RFC 1373 (Informational)", series="Internet Request for Comments", type="RFC", number="1373", pages="1--12", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1373.txt", key="RFC 1373", abstract={This document comes in two parts. The first part is for regular people who wish to set up their own DUAs (Directory User Interfaces) to access the Directory. The second part is for ISODE-maintainers wishing to provide portable DUAs to users. This part gives instructions in a similar but longer, step-by-step format. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="directory, user, agents, whois, de, dixie, ud, doog, ISODE, X.500", doi="10.17487/RFC1373", } @misc{rfc1374, author="J. Renwick and A. Nicholson", title="{IP and ARP on HIPPI}", howpublished="RFC 1374 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1374", pages="1--43", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2834", url="https://www.rfc-editor.org/rfc/rfc1374.txt", key="RFC 1374", abstract={The ANSI X3T9.3 committee has drafted a proposal for the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. Another X3T9.3 draft describes the operation of HIPPI physical switches. X3T9.3 chose to leave HIPPI networking issues largely outside the scope of their standards; this document discusses methods of using of ANSI standard HIPPI hardware and protocols in the context of the Internet, including the use of HIPPI switches as LANs and interoperation with other networks. This memo is intended to become an Internet Standard. [STANDARDS-TRACK]}, doi="10.17487/RFC1374", } @misc{rfc1375, author="P. Robinson", title="{Suggestion for New Classes of IP Addresses}", howpublished="RFC 1375 (Informational)", series="Internet Request for Comments", type="RFC", number="1375", pages="1--7", year=1992, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1375.txt", key="RFC 1375", abstract={This RFC suggests a change in the method of specifying the IP address to add new classes of networks to be called F, G, H, and K, to reduce the amount of wasted address space, and to increase the available IP address number space, especially for smaller organizations or classes of connectors that do not need or do not want a full Class C IP address. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="network, numbers", doi="10.17487/RFC1375", } @misc{rfc1376, author="S. Senum", title="{The PPP DECnet Phase IV Control Protocol (DNCP)}", howpublished="RFC 1376 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1376", pages="1--6", year=1992, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1762", url="https://www.rfc-editor.org/rfc/rfc1376.txt", key="RFC 1376", abstract={This document defines the NCP for establishing and configuring Digital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP. This document applies only to DNA Phase IV Routing messages (both data and control), and not to other DNA Phase IV protocols (MOP, LAT, etc.). [STANDARDS-TRACK]}, keywords="point, DNA, DDCMP", doi="10.17487/RFC1376", } @misc{rfc1377, author="D. Katz", title="{The PPP OSI Network Layer Control Protocol (OSINLCP)}", howpublished="RFC 1377 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1377", pages="1--10", year=1992, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1377.txt", key="RFC 1377", abstract={This document defines the NCP for establishing and configuring OSI Network Layer Protocols. [STANDARDS-TRACK]}, keywords="PPP-OSINLCP, point, open, systems, interconnection", doi="10.17487/RFC1377", } @misc{rfc1378, author="B. Parker", title="{The PPP AppleTalk Control Protocol (ATCP)}", howpublished="RFC 1378 (Historic)", series="Internet Request for Comments", type="RFC", number="1378", pages="1--16", year=1992, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1378.txt", key="RFC 1378", abstract={This document defines the NCP for establishing and configuring the AppleTalk Protocol [3] over PPP. [STANDARDS-TRACK]}, keywords="PPP-ATCP, point", doi="10.17487/RFC1378", } @misc{rfc1379, author="R. Braden", title="{Extending TCP for Transactions -- Concepts}", howpublished="RFC 1379 (Historic)", series="Internet Request for Comments", type="RFC", number="1379", pages="1--38", year=1992, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 6247, updated by RFC 1644", url="https://www.rfc-editor.org/rfc/rfc1379.txt", key="RFC 1379", abstract={This memo discusses extension of TCP to provide transaction-oriented service, without altering its virtual-circuit operation. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="transmission, control, protocol", doi="10.17487/RFC1379", } @misc{rfc1380, author="P. Gross and P. Almquist", title="{IESG Deliberations on Routing and Addressing}", howpublished="RFC 1380 (Informational)", series="Internet Request for Comments", type="RFC", number="1380", pages="1--22", year=1992, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1380.txt", key="RFC 1380", abstract={This memo summarizes issues surrounding the routing and addressing scaling problems in the IP architecture, and it provides a brief background of the ROAD group and related activities in the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="ROAD", doi="10.17487/RFC1380", } @misc{rfc1381, author="D. Throop and F. Baker", title="{SNMP MIB Extension for X.25 LAPB}", howpublished="RFC 1381 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1381", pages="1--33", year=1992, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1381.txt", key="RFC 1381", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Link Layer of X.25, LAPB. [STANDARDS-TRACK]}, keywords="SNMP-LAPB, management", doi="10.17487/RFC1381", } @misc{rfc1382, author="D. Throop", title="{SNMP MIB Extension for the X.25 Packet Layer}", howpublished="RFC 1382 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1382", pages="1--69", year=1992, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1382.txt", key="RFC 1382", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK]}, keywords="SNMP-X.25, management", doi="10.17487/RFC1382", } @misc{rfc1383, author="C. Huitema", title="{An Experiment in DNS Based IP Routing}", howpublished="RFC 1383 (Experimental)", series="Internet Request for Comments", type="RFC", number="1383", pages="1--14", year=1992, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1383.txt", key="RFC 1383", abstract={Potential solutions to the routing explosion. This memo defines an Experimental Protocol for the Internet community.}, keywords="DNS-IP", doi="10.17487/RFC1383", } @misc{rfc1384, author="P. Barker and S.E. Hardcastle-Kille", title="{Naming Guidelines for Directory Pilots}", howpublished="RFC 1384 (Informational)", series="Internet Request for Comments", type="RFC", number="1384", pages="1--12", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1617, NaN", url="https://www.rfc-editor.org/rfc/rfc1384.txt", key="RFC 1384", abstract={This document defines a number of naming guidelines. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="X.500, Multinational", doi="10.17487/RFC1384", } @misc{rfc1385, author="Z. Wang", title="{EIP: The Extended Internet Protocol}", howpublished="RFC 1385 (Historic)", series="Internet Request for Comments", type="RFC", number="1385", pages="1--17", year=1992, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 6814", url="https://www.rfc-editor.org/rfc/rfc1385.txt", key="RFC 1385", abstract={EIP can substantially reduce the amount of modifications needed to the current Internet systems and greatly ease the difficulties of transition. This is an ``idea'' paper and discussion is strongly encouraged on Big-Internet@munnari.oz.au. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="addressing", doi="10.17487/RFC1385", } @misc{rfc1386, author="A. Cooper and J. Postel", title="{The US Domain}", howpublished="RFC 1386 (Informational)", series="Internet Request for Comments", type="RFC", number="1386", pages="1--31", year=1992, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1480", url="https://www.rfc-editor.org/rfc/rfc1386.txt", key="RFC 1386", abstract={This is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="DNS, top-level", doi="10.17487/RFC1386", } @misc{rfc1387, author="G. Malkin", title="{RIP Version 2 Protocol Analysis}", howpublished="RFC 1387 (Informational)", series="Internet Request for Comments", type="RFC", number="1387", pages="1--3", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1721", url="https://www.rfc-editor.org/rfc/rfc1387.txt", key="RFC 1387", abstract={As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="RIP-2", doi="10.17487/RFC1387", } @misc{rfc1388, author="G. Malkin", title="{RIP Version 2 Carrying Additional Information}", howpublished="RFC 1388 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1388", pages="1--7", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1723", url="https://www.rfc-editor.org/rfc/rfc1388.txt", key="RFC 1388", abstract={This document specifies an extension of the Routing Information Protocol (RIP), as defined in [STANDARDS-TRACK]}, keywords="RIP-2", doi="10.17487/RFC1388", } @misc{rfc1389, author="G. Malkin and F. Baker", title="{RIP Version 2 MIB Extensions}", howpublished="RFC 1389 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1389", pages="1--13", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1724", url="https://www.rfc-editor.org/rfc/rfc1389.txt", key="RFC 1389", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK]}, keywords="RIP-2, Management, Information, Base", doi="10.17487/RFC1389", } @misc{rfc1390, author="D. Katz", title="{Transmission of IP and ARP over FDDI Networks}", howpublished="RFC 1390 (Internet Standard)", series="Internet Request for Comments", type="RFC", number="1390", pages="1--11", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1390.txt", key="RFC 1390", 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. [STANDARDS-TRACK]}, keywords="IP-FDDI, IEEE, 802, MAC", doi="10.17487/RFC1390", } @misc{rfc1391, author="G. Malkin", title="{The Tao of the IETF: A Guide for New Attendees of the Internet Engineering Task Force}", howpublished="RFC 1391 (Informational)", series="Internet Request for Comments", type="RFC", number="1391", pages="1--19", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1539", url="https://www.rfc-editor.org/rfc/rfc1391.txt", key="RFC 1391", abstract={The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="meetings", doi="10.17487/RFC1391", } @misc{rfc1392, author="G. Malkin and T. LaQuey Parker", title="{Internet Users' Glossary}", howpublished="RFC 1392 (Informational)", series="Internet Request for Comments", type="RFC", number="1392", pages="1--53", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1983", url="https://www.rfc-editor.org/rfc/rfc1392.txt", key="RFC 1392", abstract={There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1392", } @misc{rfc1393, author="G. Malkin", title="{Traceroute Using an IP Option}", howpublished="RFC 1393 (Historic)", series="Internet Request for Comments", type="RFC", number="1393", pages="1--7", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 6814", url="https://www.rfc-editor.org/rfc/rfc1393.txt", key="RFC 1393", abstract={This document specifies a new IP option and ICMP message type which duplicates the functionality of the existing traceroute method while generating fewer packets and completing in a shorter time. This memo defines an Experimental Protocol for the Internet community.}, keywords="TRACE-IP, ICMP, MTU, Line, Speed", doi="10.17487/RFC1393", } @misc{rfc1394, author="P. Robinson", title="{Relationship of Telex Answerback Codes to Internet Domains}", howpublished="RFC 1394 (Informational)", series="Internet Request for Comments", type="RFC", number="1394", pages="1--15", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1394.txt", key="RFC 1394", abstract={This RFC gives the list, as best known, of all common Internet domains and the conversion between specific country telex answerback codes and Internet country domain identifiers. It also lists the telex code and international dialing code, wherever it is available. It will also list major Internet ``Public'' E-Mail addresses. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="DNS, Country", doi="10.17487/RFC1394", } @misc{rfc1395, author="J. Reynolds", title="{BOOTP Vendor Information Extensions}", howpublished="RFC 1395 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1395", pages="1--8", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1497, 1533", url="https://www.rfc-editor.org/rfc/rfc1395.txt", key="RFC 1395", abstract={This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo will be updated as additional tags are defined. This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16 for Swap Server and Tag 17 for Root Path. This memo is a status report on the vendor information extensions used int the Bootstrap Protocol (BOOTP).}, keywords="TAGS", doi="10.17487/RFC1395", } @misc{rfc1396, author="S. Crocker", title="{The Process for Organization of Internet Standards Working Group (POISED)}", howpublished="RFC 1396 (Informational)", series="Internet Request for Comments", type="RFC", number="1396", pages="1--10", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1396.txt", key="RFC 1396", abstract={This report provides a summary of the POISED Working Group (WG), starting from the events leading to the formation of the WG to the end of 1992. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="IAB, IESG, ISOC", doi="10.17487/RFC1396", } @misc{rfc1397, author="D. Haskin", title="{Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol}", howpublished="RFC 1397 (Historic)", series="Internet Request for Comments", type="RFC", number="1397", pages="1--2", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1397.txt", key="RFC 1397", abstract={This document speficies the recommendation of the BGP Working Group on default route advertisement support in BGP2 [1] and BGP3 [2] versions of the Border Gateway Protocol. [STANDARDS-TRACK]}, keywords="BGP", doi="10.17487/RFC1397", } @misc{rfc1398, author="F. Kastenholz", title="{Definitions of Managed Objects for the Ethernet-Like Interface Types}", howpublished="RFC 1398 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1398", pages="1--17", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1623", url="https://www.rfc-editor.org/rfc/rfc1398.txt", key="RFC 1398", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing ehternet-like objects. [STANDARDS-TRACK]}, keywords="MIB, Management", doi="10.17487/RFC1398", } @misc{rfc1399, author="J. Elliott", title="{Summary of 1300-1399}", howpublished="RFC 1399 (Informational)", series="Internet Request for Comments", type="RFC", number="1399", pages="1--22", year=1997, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1399.txt", key="RFC 1399", keywords="Index", doi="10.17487/RFC1399", } @misc{rfc1400, author="S. Williamson", title="{Transition and Modernization of the Internet Registration Service}", howpublished="RFC 1400 (Informational)", series="Internet Request for Comments", type="RFC", number="1400", pages="1--7", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1400.txt", key="RFC 1400", abstract={As a result of the NREN NIS award by National Science Foundation, non- DDN registration services will soon be transferred from the DDN NIC to the new Internet Registration Service, which is a part of an entity referred to as the InterNIC. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="INTERNIC IR", doi="10.17487/RFC1400", } @misc{rfc1401, author="Internet Architecture Board", title="{Correspondence between the IAB and DISA on the use of DNS}", howpublished="RFC 1401 (Informational)", series="Internet Request for Comments", type="RFC", number="1401", pages="1--8", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1401.txt", key="RFC 1401", abstract={This memo reproduces three letters exchanged between the Internet Activities Board (IAB) and the Defense Information Systems Agency (DISA) regarding the importance of using the Domain Name System (DNS) throughout the Internet, and phasing out the use of older host name to address tables, such as ``hosts.txt''. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Domain Name, Milnet", doi="10.17487/RFC1401", } @misc{rfc1402, author="J. Martin", title="{There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places}", howpublished="RFC 1402 (Informational)", series="Internet Request for Comments", type="RFC", number="1402", pages="1--39", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1402.txt", key="RFC 1402", abstract={The ultimate goal is to make the route to these sources of information invisible to you. At present, this is not easy to do. I will explain some of the techniques that can be used to make these nuggets easier to pick up so that we all can be richer. This RFC provides information for the Internet community. It does not specify an Internet standard.}, keywords="information, introduction, SIGUCCS, User Services, Help", doi="10.17487/RFC1402", } @misc{rfc1403, author="K. Varadhan", title="{BGP OSPF Interaction}", howpublished="RFC 1403 (Historic)", series="Internet Request for Comments", type="RFC", number="1403", pages="1--17", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1403.txt", key="RFC 1403", abstract={This memo defines the various criteria to be used when designing an Autonomous System Border Routers (ASBR) that will run BGP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK]}, keywords="BGP-OSPF, border gateway protocol, open shortest path first routing", doi="10.17487/RFC1403", } @misc{rfc1404, author="B. Stockman", title="{A Model for Common Operational Statistics}", howpublished="RFC 1404 (Informational)", series="Internet Request for Comments", type="RFC", number="1404", pages="1--27", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1857", url="https://www.rfc-editor.org/rfc/rfc1404.txt", key="RFC 1404", abstract={This memo describes a model for operational statistics in the Internet. It gives recommendations for metrics, measurements, polling periods, storage formats and presentation formats. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Management, Operations", doi="10.17487/RFC1404", } @misc{rfc1405, author="C. Allocchio", title="{Mapping between X.400(1984/1988) and Mail-11 (DECnet mail)}", howpublished="RFC 1405 (Experimental)", series="Internet Request for Comments", type="RFC", number="1405", pages="1--19", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2162", url="https://www.rfc-editor.org/rfc/rfc1405.txt", key="RFC 1405", abstract={This document describes a set of mappings which will enable inter working between systems operating the CCITT X.400 ( 1984 / 1988 ) Recommendations on Message Handling Systems, and systems running the Mail-11 (also known as DECnet mail) protocol. This memo defines an Experimental Protocol for the Internet community.}, keywords="SMTP, EMail, 822", doi="10.17487/RFC1405", } @misc{rfc1406, author="F. Baker and J. Watt", title="{Definitions of Managed Objects for the DS1 and E1 Interface Types}", howpublished="RFC 1406 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1406", pages="1--50", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2495", url="https://www.rfc-editor.org/rfc/rfc1406.txt", key="RFC 1406", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing DS1 Interfaces -- including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links. [STANDARDS-TRACK]}, keywords="DS1/E1-MIB, T1, MIB, Management, SNMP", doi="10.17487/RFC1406", } @misc{rfc1407, author="T. Cox and K. Tesink", title="{Definitions of Managed Objects for the DS3/E3 Interface Type}", howpublished="RFC 1407 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1407", pages="1--43", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2496", url="https://www.rfc-editor.org/rfc/rfc1407.txt", key="RFC 1407", abstract={This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing DS3 and E3 Interfaces. [STANDARDS-TRACK]}, keywords="DS3/E3-MIB, T3, MIB, Management, SNMP", doi="10.17487/RFC1407", } @misc{rfc1408, author="D. Borman", title="{Telnet Environment Option}", howpublished="RFC 1408 (Historic)", series="Internet Request for Comments", type="RFC", number="1408", pages="1--7", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 1571", url="https://www.rfc-editor.org/rfc/rfc1408.txt", key="RFC 1408", abstract={This document specifies a mechanism for passing environment information between a telnet client and server. [STANDARDS-TRACK]}, keywords="TOPT-ENVIR, Negotiation", doi="10.17487/RFC1408", } @misc{rfc1409, author="D. Borman", title="{Telnet Authentication Option}", howpublished="RFC 1409 (Experimental)", series="Internet Request for Comments", type="RFC", number="1409", pages="1--7", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1416", url="https://www.rfc-editor.org/rfc/rfc1409.txt", key="RFC 1409", abstract={This memo defines an Experimental Protocol for the Internet community.}, keywords="security", doi="10.17487/RFC1409", } @misc{rfc1410, author="J. Postel", title="{IAB Official Protocol Standards}", howpublished="RFC 1410 (Historic)", series="Internet Request for Comments", type="RFC", number="1410", pages="1--35", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1500", url="https://www.rfc-editor.org/rfc/rfc1410.txt", key="RFC 1410", abstract={This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB).}, keywords="proposed, draft, experimental, informational, historic, full", doi="10.17487/RFC1410", } @misc{rfc1411, author="D. Borman", title="{Telnet Authentication: Kerberos Version 4}", howpublished="RFC 1411 (Experimental)", series="Internet Request for Comments", type="RFC", number="1411", pages="1--4", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1411.txt", key="RFC 1411", abstract={This memo defines an Experimental Protocol for the Internet community.}, keywords="TEL-KER, Security, option", doi="10.17487/RFC1411", } @misc{rfc1412, author="K. Alagappan", title="{Telnet Authentication: SPX}", howpublished="RFC 1412 (Experimental)", series="Internet Request for Comments", type="RFC", number="1412", pages="1--4", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1412.txt", key="RFC 1412", abstract={This memo defines an Experimental Protocol for the Internet community.}, keywords="TEL-SPX, Security, option", doi="10.17487/RFC1412", } @misc{rfc1413, author="M. St. Johns", title="{Identification Protocol}", howpublished="RFC 1413 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1413", pages="1--8", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1413.txt", key="RFC 1413", abstract={The Identification Protocol was formerly called the Authentication Server Protocol. It has been renamed to better reflect its function. [STANDARDS-TRACK]}, keywords="IDENT, Authentication", doi="10.17487/RFC1413", } @misc{rfc1414, author="M. St. Johns and M. Rose", title="{Identification MIB}", howpublished="RFC 1414 (Historic)", series="Internet Request for Comments", type="RFC", number="1414", pages="1--7", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1414.txt", key="RFC 1414", abstract={This memo defines a MIB for use with identifying the users associated with TCP connections. It provides functionality approximately equivalent to that provided by the protocol defined in RFC 1413 [1]. [STANDARDS-TRACK]}, keywords="IDENT-MIB, Management, SNMP", doi="10.17487/RFC1414", } @misc{rfc1415, author="J. Mindel and R. Slaski", title="{FTP-FTAM Gateway Specification}", howpublished="RFC 1415 (Historic)", series="Internet Request for Comments", type="RFC", number="1415", pages="1--58", year=1993, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1415.txt", key="RFC 1415", abstract={This memo describes a dual protocol stack application layer gateway that performs protocol translation, in an interactive environment, between the FTP and FTAM file transfer protocols. [STANDARDS-TRACK]}, keywords="FTP, FTAM, transfer, ISO, OSI", doi="10.17487/RFC1415", } @misc{rfc1416, author="D. Borman", title="{Telnet Authentication Option}", howpublished="RFC 1416 (Experimental)", series="Internet Request for Comments", type="RFC", number="1416", pages="1--7", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2941", url="https://www.rfc-editor.org/rfc/rfc1416.txt", key="RFC 1416", abstract={This RFC 1416 replaces RFC 1409, which has an important typographical error in the example on page 6 (one occurance of ``REPLY'' should be ``IS''). This memo defines an Experimental Protocol for the Internet community.}, keywords="TOPT-AUTH, Security", doi="10.17487/RFC1416", } @misc{rfc1417, author="The North American Directory Forum", title="{NADF Standing Documents: A Brief Overview}", howpublished="RFC 1417 (Informational)", series="Internet Request for Comments", type="RFC", number="1417", pages="1--4", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1758", url="https://www.rfc-editor.org/rfc/rfc1417.txt", key="RFC 1417", abstract={The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="X.500, Directory", doi="10.17487/RFC1417", } @misc{rfc1418, author="M. Rose", title="{SNMP over OSI}", howpublished="RFC 1418 (Historic)", series="Internet Request for Comments", type="RFC", number="1418", pages="1--4", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1418.txt", key="RFC 1418", abstract={This memo addresses some concerns by defining a framework for running the SNMP in an environment which supports the OSI connectionless-mode transport service. [STANDARDS-TRACK]}, keywords="SNMP-OSI, Management", doi="10.17487/RFC1418", } @misc{rfc1419, author="G. Minshall and M. Ritter", title="{SNMP over AppleTalk}", howpublished="RFC 1419 (Historic)", series="Internet Request for Comments", type="RFC", number="1419", pages="1--7", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1419.txt", key="RFC 1419", abstract={This memo describes the method by which the Simple Network Management Protocol (SNMP) as specified in [1] can be used over AppleTalk protocols [2] instead of the Internet UDP/IP protocol stack. [STANDARDS-TRACK]}, keywords="SNMP-AT, Management", doi="10.17487/RFC1419", } @misc{rfc1420, author="S. Bostock", title="{SNMP over IPX}", howpublished="RFC 1420 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1420", pages="1--4", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1420.txt", key="RFC 1420", abstract={This document defines a convention for encapsulating Simple Network Management Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2]. [STANDARDS-TRACK]}, keywords="SNMP-IPX, Management", doi="10.17487/RFC1420", } @misc{rfc1421, author="J. Linn", title="{Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures}", howpublished="RFC 1421 (Historic)", series="Internet Request for Comments", type="RFC", number="1421", pages="1--42", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1421.txt", key="RFC 1421", abstract={This document defines message encryption and authentication procedures, in order to provide privacy-enhanced mail (PEM) services for electronic mail transfer in the Internet. [STANDARDS-TRACK]}, keywords="PEM-ENC, PEM", doi="10.17487/RFC1421", } @misc{rfc1422, author="S. Kent", title="{Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management}", howpublished="RFC 1422 (Historic)", series="Internet Request for Comments", type="RFC", number="1422", pages="1--32", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1422.txt", key="RFC 1422", abstract={This is one of a series of documents defining privacy enhancement mechanisms for electronic mail transferred using Internet mail protocols. [STANDARDS-TRACK]}, keywords="PEM-CKM, PEM", doi="10.17487/RFC1422", } @misc{rfc1423, author="D. Balenson", title="{Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers}", howpublished="RFC 1423 (Historic)", series="Internet Request for Comments", type="RFC", number="1423", pages="1--14", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1423.txt", key="RFC 1423", abstract={This document provides definitions, formats, references, and citations for cryptographic algorithms, usage modes, and associated identifiers and parameters used in support of Privacy Enhanced Mail (PEM) in the Internet community. [STANDARDS-TRACK]}, keywords="PEM-ALG, PEM", doi="10.17487/RFC1423", } @misc{rfc1424, author="B. Kaliski", title="{Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services}", howpublished="RFC 1424 (Historic)", series="Internet Request for Comments", type="RFC", number="1424", pages="1--9", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1424.txt", key="RFC 1424", abstract={This document describes three types of service in support of Internet Privacy-Enhanced Mail (PEM) [1-3]: key certification, certificate- revocation list (CRL) storage, and CRL retrieval. [STANDARDS-TRACK]}, keywords="PEM-KEY, PEM", doi="10.17487/RFC1424", } @misc{rfc1425, author="J. Klensin and N. Freed and M. Rose and E. Stefferud and D. Crocker", title="{SMTP Service Extensions}", howpublished="RFC 1425 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1425", pages="1--10", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1651", url="https://www.rfc-editor.org/rfc/rfc1425.txt", key="RFC 1425", abstract={This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK]}, keywords="Mail", doi="10.17487/RFC1425", } @misc{rfc1426, author="J. Klensin and N. Freed and M. Rose and E. Stefferud and D. Crocker", title="{SMTP Service Extension for 8bit-MIMEtransport}", howpublished="RFC 1426 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1426", pages="1--6", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1652", url="https://www.rfc-editor.org/rfc/rfc1426.txt", key="RFC 1426", abstract={This memo defines an extension to the SMTP service whereby an SMTP content body containing octets outside of the US ASCII octet range (hex}, keywords="Mail", doi="10.17487/RFC1426", } @misc{rfc1427, author="J. Klensin and N. Freed and K. Moore", title="{SMTP Service Extension for Message Size Declaration}", howpublished="RFC 1427 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1427", pages="1--8", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1653", url="https://www.rfc-editor.org/rfc/rfc1427.txt", key="RFC 1427", abstract={This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. [STANDARDS-TRACK]}, keywords="Mail", doi="10.17487/RFC1427", } @misc{rfc1428, author="G. Vaudreuil", title="{Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME}", howpublished="RFC 1428 (Informational)", series="Internet Request for Comments", type="RFC", number="1428", pages="1--6", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1428.txt", key="RFC 1428", abstract={This document outlines the problems in this environment and an approach to minimizing the cost of transition from current usage of non-MIME 8bit messages to MIME. This RFC provides information for the Internet community. It does not specify an Internet standard.}, keywords="Mail", doi="10.17487/RFC1428", } @misc{rfc1429, author="E. Thomas", title="{Listserv Distribute Protocol}", howpublished="RFC 1429 (Informational)", series="Internet Request for Comments", type="RFC", number="1429", pages="1--8", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1429.txt", key="RFC 1429", abstract={This memo specifies a subset of the distribution protocol used by the BITNET LISTSERV to deliver mail messages to large amounts of recipients. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="LISTSERV, Mail", doi="10.17487/RFC1429", } @misc{rfc1430, author="S. Hardcastle-Kille and E. Huizer and V. Cerf and R. Hobby and S. Kent", title="{A Strategic Plan for Deploying an Internet X.500 Directory Service}", howpublished="RFC 1430 (Informational)", series="Internet Request for Comments", type="RFC", number="1430", pages="1--20", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1430.txt", key="RFC 1430", abstract={This document describes an overall strategy for deploying a Directory Service on the Internet, based on the OSI X.500 Directory Service. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="X.500", doi="10.17487/RFC1430", } @misc{rfc1431, author="P. Barker", title="{DUA Metrics (OSI-DS 33 (v2))}", howpublished="RFC 1431 (Informational)", series="Internet Request for Comments", type="RFC", number="1431", pages="1--19", year=1993, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1431.txt", key="RFC 1431", abstract={This document defines a set of criteria by which a DUA implementation, or more precisely a Directory user interface, may be judged. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Directory User Agent, Measurement, Statistics, Survey, X.500", doi="10.17487/RFC1431", } @misc{rfc1432, author="J. Quarterman", title="{Recent Internet Books}", howpublished="RFC 1432 (Informational)", series="Internet Request for Comments", type="RFC", number="1432", pages="1--15", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1432.txt", key="RFC 1432", abstract={Here is a list of books related to using the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="bibiography", doi="10.17487/RFC1432", } @misc{rfc1433, author="J. Garrett and J. Hagan and J. Wong", title="{Directed ARP}", howpublished="RFC 1433 (Experimental)", series="Internet Request for Comments", type="RFC", number="1433", pages="1--18", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1433.txt", key="RFC 1433", abstract={Directed ARP is a dynamic address resolution procedure that enables hosts and routers to resolve advertised potential next-hop IP addresses on foreign IP networks to their associated link level addresses. This memo defines an Experimental Protocol for the Internet community.}, keywords="DIR-ARP, public networks, SMDS", doi="10.17487/RFC1433", } @misc{rfc1434, author="R. Dixon and D. Kushi", title="{Data Link Switching: Switch-to-Switch Protocol}", howpublished="RFC 1434 (Informational)", series="Internet Request for Comments", type="RFC", number="1434", pages="1--33", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1795", url="https://www.rfc-editor.org/rfc/rfc1434.txt", key="RFC 1434", abstract={This RFC describes IBM's support of Data Link Switching over TCP/IP. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="IBM, SNA, DLS, SSP, NetBIos", doi="10.17487/RFC1434", } @misc{rfc1435, author="S. Knowles", title="{IESG Advice from Experience with Path MTU Discovery}", howpublished="RFC 1435 (Informational)", series="Internet Request for Comments", type="RFC", number="1435", pages="1--2", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1435.txt", key="RFC 1435", abstract={In the course of reviewing the MTU Discovery protocol for possible elevation to Draft Standard, a specific operational problem was uncovered. The problem results from the optional suppression of ICMP messages implemented in some routers. This memo outlines a modification to this practice to allow the correct functioning of MTU Discovery. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Maximum, Transmission, Unit", doi="10.17487/RFC1435", } @misc{rfc1436, author="F. Anklesaria and M. McCahill and P. Lindner and D. Johnson and D. Torrey and B. Albert", title="{The Internet Gopher Protocol (a distributed document search and retrieval protocol)}", howpublished="RFC 1436 (Informational)", series="Internet Request for Comments", type="RFC", number="1436", pages="1--16", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1436.txt", key="RFC 1436", abstract={This document describes the protocol, lists some of the implementations currently available, and has an overview of how to implement new client and server applications. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="GOPHER, information, locating", doi="10.17487/RFC1436", } @misc{rfc1437, author="N. Borenstein and M. Linimon", title="{The Extension of MIME Content-Types to a New Medium}", howpublished="RFC 1437 (Informational)", series="Internet Request for Comments", type="RFC", number="1437", pages="1--6", year=1993, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1437.txt", key="RFC 1437", abstract={This document defines one particular type of MIME data, the matter- transport/sentient-life-form type. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="life form, Matter, transport, Sentient", doi="10.17487/RFC1437", } @misc{rfc1438, author="A. Lyman Chapin and C. Huitema", title="{Internet Engineering Task Force Statements Of Boredom (SOBs)}", howpublished="RFC 1438 (Informational)", series="Internet Request for Comments", type="RFC", number="1438", pages="1--2", year=1993, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1438.txt", key="RFC 1438", abstract={This document creates a new subseries of RFCs, entitled, IETF Statements Of Boredom (SOBs). This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="process, policy", doi="10.17487/RFC1438", } @misc{rfc1439, author="C. Finseth", title="{The Uniqueness of Unique Identifiers}", howpublished="RFC 1439 (Informational)", series="Internet Request for Comments", type="RFC", number="1439", pages="1--11", year=1993, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1439.txt", key="RFC 1439", abstract={This RFC provides information that may be useful when selecting a method to use for assigning unique identifiers to people. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="names", doi="10.17487/RFC1439", } @misc{rfc1440, author="R. Troth", title="{SIFT/UFT: Sender-Initiated/Unsolicited File Transfer}", howpublished="RFC 1440 (Experimental)", series="Internet Request for Comments", type="RFC", number="1440", pages="1--9", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1440.txt", key="RFC 1440", abstract={This document describes a Sender-Initiated File Transfer (SIFT) protocol, also commonly called Unsolicited File Transfer (UFT) protocol. This memo defines an Experimental Protocol for the Internet community.}, keywords="SIFT, UFT, Send, FTP", doi="10.17487/RFC1440", } @misc{rfc1441, author="J. Case and K. McCloghrie and M. Rose and S. Waldbusser", title="{Introduction to version 2 of the Internet-standard Network Management Framework}", howpublished="RFC 1441 (Historic)", series="Internet Request for Comments", type="RFC", number="1441", pages="1--13", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1441.txt", key="RFC 1441", abstract={The purpose of this document is to provide an overview of version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2). [STANDARDS-TRACK]}, keywords="SNMPv2, SNMP, Management, Framework", doi="10.17487/RFC1441", } @misc{rfc1442, author="J. Case and K. McCloghrie and M. Rose and S. Waldbusser", title="{Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)}", howpublished="RFC 1442 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1442", pages="1--56", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1902", url="https://www.rfc-editor.org/rfc/rfc1442.txt", key="RFC 1442", abstract={Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using a subset of OSI's Abstract Syntax Notation One (ASN.1) [1]. It is the purpose of this document, the Structure of Management Information (SMI), to define that subset. [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework, SMI", doi="10.17487/RFC1442", } @misc{rfc1443, author="J. Case and K. McCloghrie and M. Rose and S. Waldbusser", title="{Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)}", howpublished="RFC 1443 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1443", pages="1--31", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1903", url="https://www.rfc-editor.org/rfc/rfc1443.txt", key="RFC 1443", abstract={It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework", doi="10.17487/RFC1443", } @misc{rfc1444, author="J. Case and K. McCloghrie and M. Rose and S. Waldbusser", title="{Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2)}", howpublished="RFC 1444 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1444", pages="1--33", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1904", url="https://www.rfc-editor.org/rfc/rfc1444.txt", key="RFC 1444", abstract={It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes. [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework", doi="10.17487/RFC1444", } @misc{rfc1445, author="J. Galvin and K. McCloghrie", title="{Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)}", howpublished="RFC 1445 (Historic)", series="Internet Request for Comments", type="RFC", number="1445", pages="1--48", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1445.txt", key="RFC 1445", abstract={It is the purpose of this document, the Administrative Model for SNMPv2, to define how the administrative framework is applied to realize effective network management in a variety of configurations and environments. [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework", doi="10.17487/RFC1445", } @misc{rfc1446, author="J. Galvin and K. McCloghrie", title="{Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2)}", howpublished="RFC 1446 (Historic)", series="Internet Request for Comments", type="RFC", number="1446", pages="1--52", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1446.txt", key="RFC 1446", abstract={It is the purpose of this document, Security Protocols for SNMPv2, to define one such authentication and one such privacy protocol. [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework", doi="10.17487/RFC1446", } @misc{rfc1447, author="K. McCloghrie and J. Galvin", title="{Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2)}", howpublished="RFC 1447 (Historic)", series="Internet Request for Comments", type="RFC", number="1447", pages="1--50", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1447.txt", key="RFC 1447", abstract={The Administrative Model for SNMPv2 document [3] defines the properties associated with SNMPv2 parties, SNMPv2 contexts, and access control policies. It is the purpose of this document, the Party MIB for SNMPv2, to define managed objects which correspond to these properties. [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework", doi="10.17487/RFC1447", } @misc{rfc1448, author="J. Case and K. McCloghrie and M. Rose and S. Waldbusser", title="{Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)}", howpublished="RFC 1448 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1448", pages="1--36", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1905", url="https://www.rfc-editor.org/rfc/rfc1448.txt", key="RFC 1448", abstract={It is the purpose of this document, Protocol Operations for SNMPv2, to define the operations of the protocol with respect to the sending and receiving of the PDUs. [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework", doi="10.17487/RFC1448", } @misc{rfc1449, author="J. Case and K. McCloghrie and M. Rose and S. Waldbusser", title="{Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)}", howpublished="RFC 1449 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1449", pages="1--25", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1906", url="https://www.rfc-editor.org/rfc/rfc1449.txt", key="RFC 1449", abstract={It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework", doi="10.17487/RFC1449", } @misc{rfc1450, author="J. Case and K. McCloghrie and M. Rose and S. Waldbusser", title="{Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)}", howpublished="RFC 1450 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1450", pages="1--27", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1907", url="https://www.rfc-editor.org/rfc/rfc1450.txt", key="RFC 1450", abstract={It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework", doi="10.17487/RFC1450", } @misc{rfc1451, author="J. Case and K. McCloghrie and M. Rose and S. Waldbusser", title="{Manager-to-Manager Management Information Base}", howpublished="RFC 1451 (Historic)", series="Internet Request for Comments", type="RFC", number="1451", pages="1--36", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1451.txt", key="RFC 1451", abstract={It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity acting in both a manager role and an agent role. [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework", doi="10.17487/RFC1451", } @misc{rfc1452, author="J. Case and K. McCloghrie and M. Rose and S. Waldbusser", title="{Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework}", howpublished="RFC 1452 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1452", pages="1--17", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1908", url="https://www.rfc-editor.org/rfc/rfc1452.txt", key="RFC 1452", abstract={The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2) [1], and the original Internet-standard Network Management Framework (SNMPv1). [STANDARDS-TRACK]}, keywords="SNMP, Management, Framework", doi="10.17487/RFC1452", } @misc{rfc1453, author="W. Chimiak", title="{A Comment on Packet Video Remote Conferencing and the Transport/Network Layers}", howpublished="RFC 1453 (Informational)", series="Internet Request for Comments", type="RFC", number="1453", pages="1--10", year=1993, month=apr, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1453.txt", key="RFC 1453", abstract={This RFC is a vehicle to inform the Internet community about XTP as it benefits from past Internet activity and targets general-purpose applications and multimedia applications with the emerging ATM networks in mind. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="XTP", doi="10.17487/RFC1453", } @misc{rfc1454, author="T. Dixon", title="{Comparison of Proposals for Next Version of IP}", howpublished="RFC 1454 (Informational)", series="Internet Request for Comments", type="RFC", number="1454", pages="1--15", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1454.txt", key="RFC 1454", abstract={This is a slightly edited reprint of RARE Technical Report (RTC(93)004). This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="IPng, PIP, TUBA, SIP", doi="10.17487/RFC1454", } @misc{rfc1455, author="D. {Eastlake 3rd}", title="{Physical Link Security Type of Service}", howpublished="RFC 1455 (Experimental)", series="Internet Request for Comments", type="RFC", number="1455", pages="1--6", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2474", url="https://www.rfc-editor.org/rfc/rfc1455.txt", key="RFC 1455", abstract={This RFC documents an experimental protocol providing a Type of Service (TOS) to request maximum physical link security. This is an addition to the types of service enumerated in RFC 1349: Type of Service in the Internet Protocol Suite. This memo defines an Experimental Protocol for the Internet community.}, keywords="TOS-LS, TOS", doi="10.17487/RFC1455", } @misc{rfc1456, author="Vietnamese Standardization Working Group", title="{Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification}", howpublished="RFC 1456 (Informational)", series="Internet Request for Comments", type="RFC", number="1456", pages="1--7", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1456.txt", key="RFC 1456", abstract={This document provides information to the Internet community on the currently used conventions for encoding Vietnamese characters into 7-bit US ASCII and in an 8-bit form. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Character, Set", doi="10.17487/RFC1456", } @misc{rfc1457, author="R. Housley", title="{Security Label Framework for the Internet}", howpublished="RFC 1457 (Informational)", series="Internet Request for Comments", type="RFC", number="1457", pages="1--14", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1457.txt", key="RFC 1457", abstract={This memo presents a security labeling framework for the Internet. The framework is intended to help protocol designers determine what, if any, security labeling should be supported by their protocols. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1457", } @misc{rfc1458, author="R. Braudes and S. Zabele", title="{Requirements for Multicast Protocols}", howpublished="RFC 1458 (Informational)", series="Internet Request for Comments", type="RFC", number="1458", pages="1--19", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1458.txt", key="RFC 1458", abstract={This memo discusses some of these unresolved issues, and provides a high-level design for a new multicast transport protocol, group address and membership authority, and modifications to existing routing protocols. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Real-Time", doi="10.17487/RFC1458", } @misc{rfc1459, author="J. Oikarinen and D. Reed", title="{Internet Relay Chat Protocol}", howpublished="RFC 1459 (Experimental)", series="Internet Request for Comments", type="RFC", number="1459", pages="1--65", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFCs 2810, 2811, 2812, 2813, 7194", url="https://www.rfc-editor.org/rfc/rfc1459.txt", key="RFC 1459", abstract={The IRC protocol is a text-based protocol, with the simplest client being any socket program capable of connecting to the server. This memo defines an Experimental Protocol for the Internet community.}, keywords="IRCP, IRC", doi="10.17487/RFC1459", } @misc{rfc1460, author="M. Rose", title="{Post Office Protocol - Version 3}", howpublished="RFC 1460 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1460", pages="1--17", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1725", url="https://www.rfc-editor.org/rfc/rfc1460.txt", key="RFC 1460", abstract={This memo is a revision to RFC 1225, a Draft Standard. [STANDARDS-TRACK]}, keywords="Email", doi="10.17487/RFC1460", } @misc{rfc1461, author="D. Throop", title="{SNMP MIB extension for Multiprotocol Interconnect over X.25}", howpublished="RFC 1461 (Historic)", series="Internet Request for Comments", type="RFC", number="1461", pages="1--21", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1461.txt", key="RFC 1461", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Multiprotocol Interconnect (including IP) traffic carried over X.25. [STANDARDS-TRACK]}, keywords="X25-MIB", doi="10.17487/RFC1461", } @misc{rfc1462, author="E. Krol and E. Hoffman", title="{FYI on ``What is the Internet?''}", howpublished="RFC 1462 (Informational)", series="Internet Request for Comments", type="RFC", number="1462", pages="1--11", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1462.txt", key="RFC 1462", abstract={This FYI RFC answers the question, ``What is the Internet?'' and is produced by the User Services Working Group of the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Introduction", doi="10.17487/RFC1462", } @misc{rfc1463, author="E. Hoffman and L. Jackson", title="{FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings}", howpublished="RFC 1463 (Informational)", series="Internet Request for Comments", type="RFC", number="1463", pages="1--4", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1463.txt", key="RFC 1463", abstract={This bibliography offers a short list of recent information resources that will help the network novice become familiar with the Internet, including its associated networks, resources, protocols, and history. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1463", } @misc{rfc1464, author="R. Rosenbaum", title="{Using the Domain Name System To Store Arbitrary String Attributes}", howpublished="RFC 1464 (Experimental)", series="Internet Request for Comments", type="RFC", number="1464", pages="1--4", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1464.txt", key="RFC 1464", abstract={This paper describes a simple means to associate arbitrary string information (ASCII text) with attributes that have not been defined by the DNS. This memo defines an Experimental Protocol for the Internet community.}, keywords="DNS, TXT", doi="10.17487/RFC1464", } @misc{rfc1465, author="D. Eppenberger", title="{Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing}", howpublished="RFC 1465 (Experimental)", series="Internet Request for Comments", type="RFC", number="1465", pages="1--31", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1465.txt", key="RFC 1465", abstract={This document proposes short term solutions for maintaining and distributing routing information and shows how messages can travel over different networks by using multi stack MTAs as relays. This memo defines an Experimental Protocol for the Internet community.}, keywords="X400", doi="10.17487/RFC1465", } @misc{rfc1466, author="E. Gerich", title="{Guidelines for Management of IP Address Space}", howpublished="RFC 1466 (Informational)", series="Internet Request for Comments", type="RFC", number="1466", pages="1--10", year=1993, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2050", url="https://www.rfc-editor.org/rfc/rfc1466.txt", key="RFC 1466", abstract={This document proposes a plan which will forward the implementation of RFC 1174 and which defines the allocation and assignment of the network number space. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="CIDR", doi="10.17487/RFC1466", } @misc{rfc1467, author="C. Topolcic", title="{Status of CIDR Deployment in the Internet}", howpublished="RFC 1467 (Historic)", series="Internet Request for Comments", type="RFC", number="1467", pages="1--9", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1467.txt", key="RFC 1467", abstract={This document describes the current status of the development and deployment of CIDR technology into the Internet. This document replaces RFC 1367, which was a schedule for the deployment of IP address space management procedures to support route aggregation. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="routing, tables, allocation, registry, IR, IANA, classless", doi="10.17487/RFC1467", } @misc{rfc1468, author="J. Murai and M. Crispin and E. van der Poel", title="{Japanese Character Encoding for Internet Messages}", howpublished="RFC 1468 (Informational)", series="Internet Request for Comments", type="RFC", number="1468", pages="1--6", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1468.txt", key="RFC 1468", abstract={This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Set", doi="10.17487/RFC1468", } @misc{rfc1469, author="T. Pusateri", title="{IP Multicast over Token-Ring Local Area Networks}", howpublished="RFC 1469 (Historic)", series="Internet Request for Comments", type="RFC", number="1469", pages="1--4", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1469.txt", key="RFC 1469", abstract={This document specifies a method for the transmission of IP multicast datagrams over Token-Ring Local Area Networks. [STANDARDS-TRACK]}, keywords="IP-TR-MC, 802.2, 802.5", doi="10.17487/RFC1469", } @misc{rfc1470, author="R. Enger and J. Reynolds", title="{FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices}", howpublished="RFC 1470 (Informational)", series="Internet Request for Comments", type="RFC", number="1470", pages="1--192", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1470.txt", key="RFC 1470", abstract={The goal of this FYI memo is to provide an update to FYI 2, RFC 1147 [1], which provided practical information to site administrators and network managers. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="NOCTOOLS", doi="10.17487/RFC1470", } @misc{rfc1471, author="F. Kastenholz", title="{The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol}", howpublished="RFC 1471 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1471", pages="1--25", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1471.txt", key="RFC 1471", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Link Control Protocol and Link Quality Monitoring on subnetwork interfaces that use the family of Point-to-Point Protocols [8, 9, 10, 11, \& 12]. [STANDARDS-TRACK]}, keywords="PPP/LCP MIB, Management, Framework, PPP", doi="10.17487/RFC1471", } @misc{rfc1472, author="F. Kastenholz", title="{The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol}", howpublished="RFC 1472 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1472", pages="1--13", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1472.txt", key="RFC 1472", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Security Protocols on subnetwork interfaces using the family of Point-to-Point Protocols [8, 9, 10, 11, \& 12]. [STANDARDS-TRACK]}, keywords="PPP/SEC MIB, Management, Framework, PPP", doi="10.17487/RFC1472", } @misc{rfc1473, author="F. Kastenholz", title="{The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol}", howpublished="RFC 1473 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1473", pages="1--10", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1473.txt", key="RFC 1473", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the IP Network Control Protocol on subnetwork interfaces using the family of Point-to-Point Protocols [8, 9, 10, 11, \& 12]. [STANDARDS-TRACK]}, keywords="PPP/IP MIB, Management, Framework, PPP", doi="10.17487/RFC1473", } @misc{rfc1474, author="F. Kastenholz", title="{The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol}", howpublished="RFC 1474 (Historic)", series="Internet Request for Comments", type="RFC", number="1474", pages="1--15", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1474.txt", key="RFC 1474", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the bridge Network Control Protocol [10] on subnetwork interfaces using the family of Point-to-Point Protocols. [STANDARDS-TRACK]}, keywords="PPP/Bridge, Management, Framework, PPP", doi="10.17487/RFC1474", } @misc{rfc1475, author="R. Ullmann", title="{TP/IX: The Next Internet}", howpublished="RFC 1475 (Historic)", series="Internet Request for Comments", type="RFC", number="1475", pages="1--35", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 6814", url="https://www.rfc-editor.org/rfc/rfc1475.txt", key="RFC 1475", abstract={This memo presents the specification for version 7 of the Internet Protocol, as well as version 7 of the TCP and the user datagram protocol. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="TP-IX, IPv7, IPng", doi="10.17487/RFC1475", } @misc{rfc1476, author="R. Ullmann", title="{RAP: Internet Route Access Protocol}", howpublished="RFC 1476 (Experimental)", series="Internet Request for Comments", type="RFC", number="1476", pages="1--20", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1476.txt", key="RFC 1476", abstract={This RFC describes an open distance vector routing protocol for use at all levels of the internet, from isolated LANs to the major routers of an international commercial network provider. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="RAP, Routing", doi="10.17487/RFC1476", } @misc{rfc1477, author="M. Steenstrup", title="{IDPR as a Proposed Standard}", howpublished="RFC 1477 (Informational)", series="Internet Request for Comments", type="RFC", number="1477", pages="1--13", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1477.txt", key="RFC 1477", abstract={This document contains a discussion of inter-domain policy routing (IDPR), including an overview of functionality and a discussion of experiments. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Routing, Policy", doi="10.17487/RFC1477", } @misc{rfc1478, author="M. Steenstrup", title="{An Architecture for Inter-Domain Policy Routing}", howpublished="RFC 1478 (Historic)", series="Internet Request for Comments", type="RFC", number="1478", pages="1--35", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1478.txt", key="RFC 1478", abstract={We present an architecture for inter-domain policy routing (IDPR). [STANDARDS-TRACK]}, keywords="IDPR-ARCH, IDPR", doi="10.17487/RFC1478", } @misc{rfc1479, author="M. Steenstrup", title="{Inter-Domain Policy Routing Protocol Specification: Version 1}", howpublished="RFC 1479 (Historic)", series="Internet Request for Comments", type="RFC", number="1479", pages="1--108", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1479.txt", key="RFC 1479", abstract={We present the set of protocols and procedures that constitute Inter- Domain Policy Routing (IDPR). [STANDARDS-TRACK]}, keywords="IDPR, IDPR", doi="10.17487/RFC1479", } @misc{rfc1480, author="A. Cooper and J. Postel", title="{The US Domain}", howpublished="RFC 1480 (Informational)", series="Internet Request for Comments", type="RFC", number="1480", pages="1--47", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1480.txt", key="RFC 1480", abstract={This is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="DNS, top-level", doi="10.17487/RFC1480", } @misc{rfc1481, author="C. Huitema", title="{IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling}", howpublished="RFC 1481 (Historic)", series="Internet Request for Comments", type="RFC", number="1481", pages="1--2", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1481.txt", key="RFC 1481", abstract={CIDR is proposed as an immediate term strategy to extend the life of the current 32 bit IP address space. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="CIDR", doi="10.17487/RFC1481", } @misc{rfc1482, author="M. Knopper and S. Richardson", title="{Aggregation Support in the NSFNET Policy-Based Routing Database}", howpublished="RFC 1482 (Historic)", series="Internet Request for Comments", type="RFC", number="1482", pages="1--11", year=1993, month=jun, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1482.txt", key="RFC 1482", abstract={This document describes plans for support of route aggregation, as specified in the descriptions of Classless Inter-Domain Routing (CIDR) [1] and the BGP-4 protocol [2], by the NSFNET Backbone Network Service. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="CIDR", doi="10.17487/RFC1482", } @misc{rfc1483, author="Juha Heinanen", title="{Multiprotocol Encapsulation over ATM Adaptation Layer 5}", howpublished="RFC 1483 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1483", pages="1--16", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2684", url="https://www.rfc-editor.org/rfc/rfc1483.txt", key="RFC 1483", abstract={This memo describes two encapsulations methods for carrying network interconnect traffic over ATM AAL5. [STANDARDS-TRACK]}, keywords="ATM-ENCAP, IP, AAL5, over", doi="10.17487/RFC1483", } @misc{rfc1484, author="S. Hardcastle-Kille", title="{Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2))}", howpublished="RFC 1484 (Historic)", series="Internet Request for Comments", type="RFC", number="1484", pages="1--25", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1781, 3494", url="https://www.rfc-editor.org/rfc/rfc1484.txt", key="RFC 1484", abstract={This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="X.500, directory names, representing names", doi="10.17487/RFC1484", } @misc{rfc1485, author="S. Hardcastle-Kille", title="{A String Representation of Distinguished Names (OSI-DS 23 (v5))}", howpublished="RFC 1485 (Historic)", series="Internet Request for Comments", type="RFC", number="1485", pages="1--7", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1779, 3494", url="https://www.rfc-editor.org/rfc/rfc1485.txt", key="RFC 1485", abstract={When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. [STANDARDS-TRACK]}, keywords="X.500, directory names, representing names", doi="10.17487/RFC1485", } @misc{rfc1486, author="M. Rose and C. Malamud", title="{An Experiment in Remote Printing}", howpublished="RFC 1486 (Experimental)", series="Internet Request for Comments", type="RFC", number="1486", pages="1--14", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1528, 1529", url="https://www.rfc-editor.org/rfc/rfc1486.txt", key="RFC 1486", abstract={This memo describes a technique for ``remote printing'' using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="electronic mail, facsimile", doi="10.17487/RFC1486", } @misc{rfc1487, author="W. Yeong and T. Howes and S. Kille", title="{X.500 Lightweight Directory Access Protocol}", howpublished="RFC 1487 (Historic)", series="Internet Request for Comments", type="RFC", number="1487", pages="1--21", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1777, 3494", url="https://www.rfc-editor.org/rfc/rfc1487.txt", key="RFC 1487", abstract={The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). [STANDARDS-TRACK]}, keywords="X.500, DAP, interactive access", doi="10.17487/RFC1487", } @misc{rfc1488, author="T. Howes and S. Kille and W. Yeong and C. Robbins", title="{The X.500 String Representation of Standard Attribute Syntaxes}", howpublished="RFC 1488 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1488", pages="1--11", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1778", url="https://www.rfc-editor.org/rfc/rfc1488.txt", key="RFC 1488", abstract={This document defines the requirements that must be satisfied by encoding rules used to render Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3]. [STANDARDS-TRACK]}, keywords="X.500, LDAP, lightweight directory protocol", doi="10.17487/RFC1488", } @misc{rfc1489, author="A. Chernov", title="{Registration of a Cyrillic Character Set}", howpublished="RFC 1489 (Informational)", series="Internet Request for Comments", type="RFC", number="1489", pages="1--5", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1489.txt", key="RFC 1489", abstract={Though the proposed character set ``koi8-r'' is not currently an international standard, there is very large user community (including Relcom Net) supporting it. Factually, ``koi8-r'' is de-facto standard for Unix and global network applications in the former Soviet Union. This is the reason the Society of Unix User Groups (SUUG) believes ``koi8-r'' should be registered. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1489", } @misc{rfc1490, author="T. Bradley and C. Brown and A. Malis", title="{Multiprotocol Interconnect over Frame Relay}", howpublished="RFC 1490 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1490", pages="1--35", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2427", url="https://www.rfc-editor.org/rfc/rfc1490.txt", key="RFC 1490", abstract={This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. Additionally, it describes a simple fragmentation procedure for carrying large frames over a frame relay network with a smaller MTU. [STANDARDS-TRACK]}, keywords="standard, standards, IP, over", doi="10.17487/RFC1490", } @misc{rfc1491, author="C. Weider and R. Wright", title="{A Survey of Advanced Usages of X.500}", howpublished="RFC 1491 (Informational)", series="Internet Request for Comments", type="RFC", number="1491", pages="1--18", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1491.txt", key="RFC 1491", abstract={This document is the result of a survey asking people to detail their advanced usages of X.500. It is intended to show how various organizations are using X.500 in ways which extend the view of X.500 as a ``White Pages'' service. This RFC is a product of the Integrated Directory Services Working Group of the Application and User Services Areas of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="directory", doi="10.17487/RFC1491", } @misc{rfc1492, author="C. Finseth", title="{An Access Control Protocol, Sometimes Called TACACS}", howpublished="RFC 1492 (Informational)", series="Internet Request for Comments", type="RFC", number="1492", pages="1--21", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1492.txt", key="RFC 1492", abstract={This RFC documents the extended TACACS protocol use by the Cisco Systems terminal servers. This same protocol is used by the University of Minnesota's distributed authentication system. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="TACACS, Terminal, Server, TAC", doi="10.17487/RFC1492", } @misc{rfc1493, author="E. Decker and P. Langille and A. Rijsinghani and K. McCloghrie", title="{Definitions of Managed Objects for Bridges}", howpublished="RFC 1493 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1493", pages="1--34", year=1993, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 4188", url="https://www.rfc-editor.org/rfc/rfc1493.txt", key="RFC 1493", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network (LAN) segments. [STANDARDS-TRACK]}, keywords="BRIDGE-MIB, SNMP, MIB, standard, standards", doi="10.17487/RFC1493", } @misc{rfc1494, author="H. Alvestrand and S. Thompson", title="{Equivalences between 1988 X.400 and RFC-822 Message Bodies}", howpublished="RFC 1494 (Historic)", series="Internet Request for Comments", type="RFC", number="1494", pages="1--19", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1494.txt", key="RFC 1494", abstract={This document describes the content of the ``IANA MHS/MIME Equivalence table'', and defines the initial configuration of this table. Mappings for new MIME content-types and/or X.400 body part types should be registered with the IANA to minimize redundancy and promote interoperability. [STANDARDS-TRACK]}, keywords="Equiv, Mail", doi="10.17487/RFC1494", } @misc{rfc1495, author="H. Alvestrand and S. Kille and R. Miles and M. Rose and S. Thompson", title="{Mapping between X.400 and RFC-822 Message Bodies}", howpublished="RFC 1495 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1495", pages="1--11", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2156", url="https://www.rfc-editor.org/rfc/rfc1495.txt", key="RFC 1495", abstract={Since the introduction of X.400(84), there has been work ongoing for defining mappings between MHS and RFC-822. The most recent work in this area is RFC-1327 [3], which focuses primarily on translation of envelope and headers. This document is complimentary to RFC-1327 as it focuses on translation of the message body. [STANDARDS-TRACK]}, keywords="Mail", doi="10.17487/RFC1495", } @misc{rfc1496, author="H. Alvestrand and J. Romaguera and K. Jordan", title="{Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages}", howpublished="RFC 1496 (Historic)", series="Internet Request for Comments", type="RFC", number="1496", pages="1--5", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1496.txt", key="RFC 1496", abstract={This document describes how RFC-1328 must be modified in order to provide adequate support for the scenarios: It replaces chapter 6 of RFC-1328. The rest of RFC-1328 is NOT obsoleted. [STANDARDS-TRACK]}, keywords="HARPOON, Mail", doi="10.17487/RFC1496", } @misc{rfc1497, author="J. Reynolds", title="{BOOTP Vendor Information Extensions}", howpublished="RFC 1497 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1497", pages="1--8", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1533", url="https://www.rfc-editor.org/rfc/rfc1497.txt", key="RFC 1497", abstract={This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo is a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP).}, keywords="TAGS, Boot", doi="10.17487/RFC1497", } @misc{rfc1498, author="J. Saltzer", title="{On the Naming and Binding of Network Destinations}", howpublished="RFC 1498 (Informational)", series="Internet Request for Comments", type="RFC", number="1498", pages="1--10", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1498.txt", key="RFC 1498", abstract={This brief paper offers a perspective on the subject of names of destinations in data communication networks. It suggests two ideas: First, it is helpful to distinguish among four different kinds of objects that may be named as the destination of a packet in a network. Second, the operating system concept of binding is a useful way to describe the relations among the four kinds of objects. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="NAMES, Addresses, Routes, Objects, Nodes, Paths", doi="10.17487/RFC1498", } @misc{rfc1499, author="J. Elliott", title="{Summary of 1400-1499}", howpublished="RFC 1499 (Informational)", series="Internet Request for Comments", type="RFC", number="1499", pages="1--21", year=1997, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1499.txt", key="RFC 1499", keywords="Index", doi="10.17487/RFC1499", } @misc{rfc1500, author="J. Postel", title="{Internet Official Protocol Standards}", howpublished="RFC 1500 (Historic)", series="Internet Request for Comments", type="RFC", number="1500", pages="1--36", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1540", url="https://www.rfc-editor.org/rfc/rfc1500.txt", key="RFC 1500", abstract={This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK]}, keywords="IAB", doi="10.17487/RFC1500", } @misc{rfc1501, author="E. Brunsen", title="{OS/2 User Group}", howpublished="RFC 1501 (Informational)", series="Internet Request for Comments", type="RFC", number="1501", pages="1--2", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1501.txt", key="RFC 1501", abstract={Memo soliciting reactions to the proposal of a OS/2 User Group. This memo provides information for the Internet community. This memo does not specify an IAB standard of any kind.}, doi="10.17487/RFC1501", } @misc{rfc1502, author="H. Alvestrand", title="{X.400 Use of Extended Character Sets}", howpublished="RFC 1502 (Historic)", series="Internet Request for Comments", type="RFC", number="1502", pages="1--14", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1502.txt", key="RFC 1502", abstract={This RFC defines a suggested method of using ``GeneralText'' in order to harmonize as much as possible the usage of this body part. [STANDARDS-TRACK]}, keywords="Mail", doi="10.17487/RFC1502", } @misc{rfc1503, author="K. McCloghrie and M. Rose", title="{Algorithms for Automating Administration in SNMPv2 Managers}", howpublished="RFC 1503 (Informational)", series="Internet Request for Comments", type="RFC", number="1503", pages="1--14", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1503.txt", key="RFC 1503", abstract={When a user invokes an SNMPv2 management application, it may be desirable for the user to specify the minimum amount of information necessary to establish and maintain SNMPv2 communications. This memo suggests an approach to achieve this goal. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Management, SNMP", doi="10.17487/RFC1503", } @misc{rfc1504, author="A. Oppenheimer", title="{Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing}", howpublished="RFC 1504 (Informational)", series="Internet Request for Comments", type="RFC", number="1504", pages="1--82", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1504.txt", key="RFC 1504", abstract={This document provides detailed information about the AppleTalk Update- based Routing Protocol (AURP) and wide area routing. AURP provides wide area routing enhancements to the AppleTalk routing protocols and is fully compatible with AppleTalk Phase 2. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="AVRP", doi="10.17487/RFC1504", } @misc{rfc1505, author="A. Costanzo and D. Robinson and R. Ullmann", title="{Encoding Header Field for Internet Messages}", howpublished="RFC 1505 (Experimental)", series="Internet Request for Comments", type="RFC", number="1505", pages="1--36", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1505.txt", key="RFC 1505", abstract={This document expands upon the elective experimental Encoding header field which permits the mailing of multi-part, multi-structured messages. It replaces RFC 1154. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="EHF-MAIL, Mail", doi="10.17487/RFC1505", } @misc{rfc1506, author="J. Houttuin", title="{A Tutorial on Gatewaying between X.400 and Internet Mail}", howpublished="RFC 1506 (Informational)", series="Internet Request for Comments", type="RFC", number="1506", pages="1--39", year=1993, month=aug, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1506.txt", key="RFC 1506", abstract={This tutorial was produced especially to help new gateway managers find their way into the complicated subject of mail gatewaying according to RFC 1327. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="822, email, RTR", doi="10.17487/RFC1506", } @misc{rfc1507, author="C. Kaufman", title="{DASS - Distributed Authentication Security Service}", howpublished="RFC 1507 (Experimental)", series="Internet Request for Comments", type="RFC", number="1507", pages="1--119", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1507.txt", key="RFC 1507", abstract={The goal of DASS is to provide authentication services in a distributed environment which are both more secure and easier to use than existing mechanisms. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="DASS, CAT", doi="10.17487/RFC1507", } @misc{rfc1508, author="J. Linn", title="{Generic Security Service Application Program Interface}", howpublished="RFC 1508 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1508", pages="1--49", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2078", url="https://www.rfc-editor.org/rfc/rfc1508.txt", key="RFC 1508", abstract={This Generic Security Service Application Program Interface (GSS-API) definition provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments. [STANDARDS-TRACK]}, keywords="CAT,GSS,API", doi="10.17487/RFC1508", } @misc{rfc1509, author="J. Wray", title="{Generic Security Service API : C-bindings}", howpublished="RFC 1509 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1509", pages="1--48", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2744", url="https://www.rfc-editor.org/rfc/rfc1509.txt", key="RFC 1509", abstract={This document specifies C language bindings for the Generic Security Service Application Program Interface (GSS-API), which is described at a language-independent conceptual level in other documents. [STANDARDS-TRACK]}, keywords="GSSAPI, CAT,GSS", doi="10.17487/RFC1509", } @misc{rfc1510, author="J. Kohl and C. Neuman", title="{The Kerberos Network Authentication Service (V5)}", howpublished="RFC 1510 (Historic)", series="Internet Request for Comments", type="RFC", number="1510", pages="1--112", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 4120, 6649", url="https://www.rfc-editor.org/rfc/rfc1510.txt", key="RFC 1510", abstract={This document gives an overview and specification of Version 5 of the protocol for the Kerberos network authentication system. [STANDARDS-TRACK]}, keywords="KERBEROS, CAT,Security", doi="10.17487/RFC1510", } @misc{rfc1511, author="J. Linn", title="{Common Authentication Technology Overview}", howpublished="RFC 1511 (Informational)", series="Internet Request for Comments", type="RFC", number="1511", pages="1--2", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1511.txt", key="RFC 1511", abstract={This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="CAT,Security", doi="10.17487/RFC1511", } @misc{rfc1512, author="J. Case and A. Rijsinghani", title="{FDDI Management Information Base}", howpublished="RFC 1512 (Historic)", series="Internet Request for Comments", type="RFC", number="1512", pages="1--51", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1512.txt", key="RFC 1512", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI based on the ANSI FDDI SMT 7.3 draft standard, which has been forwarded for publication by the X3T9.5 committee.}, keywords="FDDI-MIB , MIB, SNMP", doi="10.17487/RFC1512", } @misc{rfc1513, author="S. Waldbusser", title="{Token Ring Extensions to the Remote Network Monitoring MIB}", howpublished="RFC 1513 (Historic)", series="Internet Request for Comments", type="RFC", number="1513", pages="1--55", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1513.txt", key="RFC 1513", abstract={This memo defines extensions to the Remote Network Monitoring MIB for managing 802.5 Token Ring networks. [STANDARDS-TRACK]}, keywords="Monitoring, SNMP", doi="10.17487/RFC1513", } @misc{rfc1514, author="P. Grillo and S. Waldbusser", title="{Host Resources MIB}", howpublished="RFC 1514 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1514", pages="1--33", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2790", url="https://www.rfc-editor.org/rfc/rfc1514.txt", key="RFC 1514", abstract={This memo defines a MIB for use with managing host systems. [STANDARDS-TRACK]}, keywords="HOST-MIB, Management, SNMP", doi="10.17487/RFC1514", } @misc{rfc1515, author="D. McMaster and K. McCloghrie and S. Roberts", title="{Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)}", howpublished="RFC 1515 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1515", pages="1--25", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 3636", url="https://www.rfc-editor.org/rfc/rfc1515.txt", key="RFC 1515", abstract={This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). [STANDARDS-TRACK]}, keywords="MIB, Management, SNMP", doi="10.17487/RFC1515", } @misc{rfc1516, author="D. McMaster and K. McCloghrie", title="{Definitions of Managed Objects for IEEE 802.3 Repeater Devices}", howpublished="RFC 1516 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1516", pages="1--40", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2108", url="https://www.rfc-editor.org/rfc/rfc1516.txt", key="RFC 1516", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 10 Mb/second baseband repeaters, sometimes referred to as ``hubs.'' [STANDARDS-TRACK]}, keywords="Management, SNMP", doi="10.17487/RFC1516", } @misc{rfc1517, author="Internet Engineering Steering Group and R. Hinden", title="{Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR)}", howpublished="RFC 1517 (Historic)", series="Internet Request for Comments", type="RFC", number="1517", pages="1--4", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1517.txt", key="RFC 1517", abstract={Classless Inter-Domain Routing (CIDR) defines a mechanism to slow the growth of routing tables and reduce the need to allocate new IP network numbers. [STANDARDS-TRACK]}, keywords="CIDR, Address", doi="10.17487/RFC1517", } @misc{rfc1518, author="Y. Rekhter and T. Li", title="{An Architecture for IP Address Allocation with CIDR}", howpublished="RFC 1518 (Historic)", series="Internet Request for Comments", type="RFC", number="1518", pages="1--27", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1518.txt", key="RFC 1518", abstract={This paper provides an architecture and a plan for allocating IP addresses in the Internet. This architecture and the plan are intended to play an important role in steering the Internet towards the Address Assignment and Aggregating Strategy. [STANDARDS-TRACK]}, keywords="CIDR-ARCH, Classless, Routing", doi="10.17487/RFC1518", } @misc{rfc1519, author="V. Fuller and T. Li and J. Yu and K. Varadhan", title="{Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy}", howpublished="RFC 1519 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1519", pages="1--24", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 4632", url="https://www.rfc-editor.org/rfc/rfc1519.txt", key="RFC 1519", abstract={This memo discusses strategies for address assignment of the existing IP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers. [STANDARDS-TRACK]}, keywords="CIDR-STRA]", doi="10.17487/RFC1519", } @misc{rfc1520, author="Y. Rekhter and C. Topolcic", title="{Exchanging Routing Information Across Provider Boundaries in the CIDR Environment}", howpublished="RFC 1520 (Historic)", series="Internet Request for Comments", type="RFC", number="1520", pages="1--9", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1520.txt", key="RFC 1520", abstract={The purpose of this document is twofold. First, it describes various alternatives for exchanging inter-domain routing information across domain boundaries, where one of the peering domain is CIDR-capable and another is not. Second, it addresses the implications of running CIDR- capable inter-domain routing protocols (e.g., BGP-4, IDRP) on intra- domain routing. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Classless, Routing", doi="10.17487/RFC1520", } @misc{rfc1521, author="N. Borenstein and N. Freed", title="{MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies}", howpublished="RFC 1521 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1521", pages="1--81", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 2045, 2046, 2047, 2048, 2049, updated by RFC 1590", url="https://www.rfc-editor.org/rfc/rfc1521.txt", key="RFC 1521", abstract={This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. This is based on earlier work documented in RFC 934 and STD 11, RFC 1049, but extends and revises that work. [STANDARDS-TRACK]}, keywords="email, multimedia", doi="10.17487/RFC1521", } @misc{rfc1522, author="K. Moore", title="{MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text}", howpublished="RFC 1522 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1522", pages="1--10", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 2045, 2046, 2047, 2048, 2049", url="https://www.rfc-editor.org/rfc/rfc1522.txt", key="RFC 1522", abstract={This memo describes an extension to the message format defined in RFC 1521, to allow the representation of character sets other than ASCII in RFC 822 (STD 11) message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1521.}, keywords="email, character", doi="10.17487/RFC1522", } @misc{rfc1523, author="N. Borenstein", title="{The text/enriched MIME Content-type}", howpublished="RFC 1523 (Informational)", series="Internet Request for Comments", type="RFC", number="1523", pages="1--15", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 1563, 1896", url="https://www.rfc-editor.org/rfc/rfc1523.txt", key="RFC 1523", abstract={MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail. This document defines one particular type of MIME data, the text/enriched type, a refinement of the ``text/richtext'' type defined in RFC 1341. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="email, mail, richtext", doi="10.17487/RFC1523", } @misc{rfc1524, author="N. Borenstein", title="{A User Agent Configuration Mechanism For Multimedia Mail Format Information}", howpublished="RFC 1524 (Informational)", series="Internet Request for Comments", type="RFC", number="1524", pages="1--12", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1524.txt", key="RFC 1524", abstract={This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="MIME, email, mailcap", doi="10.17487/RFC1524", } @misc{rfc1525, author="E. Decker and K. McCloghrie and P. Langille and A. Rijsinghani", title="{Definitions of Managed Objects for Source Routing Bridges}", howpublished="RFC 1525 (Historic)", series="Internet Request for Comments", type="RFC", number="1525", pages="1--18", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1525.txt", key="RFC 1525", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for managing source routing and source routing transparent bridges. These bridges are also required to implement relevant groups in the Bridge MIB. [STANDARDS-TRACK]}, keywords="SRB-MIB, MIB, Management, SNMP", doi="10.17487/RFC1525", } @misc{rfc1526, author="D. Piscitello", title="{Assignment of System Identifiers for TUBA/CLNP Hosts}", howpublished="RFC 1526 (Informational)", series="Internet Request for Comments", type="RFC", number="1526", pages="1--8", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1526.txt", key="RFC 1526", abstract={This document describes conventions whereby the system identifier portion of an RFC 1237 style NSAP address may be guaranteed uniqueness within a routing domain for the purpose of autoconfiguration in TUBA/CLNP internets. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="NSAP, Address", doi="10.17487/RFC1526", } @misc{rfc1527, author="G. Cook", title="{What Should We Plan Given the Dilemma of the Network?}", howpublished="RFC 1527 (Informational)", series="Internet Request for Comments", type="RFC", number="1527", pages="1--17", year=1993, month=sep, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1527.txt", key="RFC 1527", abstract={The Internet community needs to be asking what the most important policy issues facing the network are. And given agreement on any particular set of policy issues, the next thing we should be asking is, what would be some of the political choices that would follow for Congress to make? This memo is a shortened version of the suggested policy draft. This memo provides information for the Internet community. It does not specify an Internet standard.}, doi="10.17487/RFC1527", } @misc{rfc1528, author="C. Malamud and M. Rose", title="{Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures}", howpublished="RFC 1528 (Experimental)", series="Internet Request for Comments", type="RFC", number="1528", pages="1--12", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1528.txt", key="RFC 1528", abstract={This memo describes a technique for ``remote printing'' using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.}, keywords="REM-PRINT, FAX, Facsimile", doi="10.17487/RFC1528", } @misc{rfc1529, author="C. Malamud and M. Rose", title="{Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies}", howpublished="RFC 1529 (Informational)", series="Internet Request for Comments", type="RFC", number="1529", pages="1--5", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1529.txt", key="RFC 1529", abstract={This document defines the administrative policies for the operation of remote printer facilities within the context of the tpc.int subdomain. The document describes different approaches to resource recovery for remote printer server sites and includes discussions of issues pertaining to auditing, security, and denial of access. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="FAX, Facsimile", doi="10.17487/RFC1529", } @misc{rfc1530, author="C. Malamud and M. Rose", title="{Principles of Operation for the TPC.INT Subdomain: General Principles and Policy}", howpublished="RFC 1530 (Informational)", series="Internet Request for Comments", type="RFC", number="1530", pages="1--7", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1530.txt", key="RFC 1530", abstract={This document defines the initial principles of operation for the tpc.int subdomain, a collection of service listings accessible over the Internet infrastructure through an administered namespace contained within the Domain Name System. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="FAX, Facsimile", doi="10.17487/RFC1530", } @misc{rfc1531, author="R. Droms", title="{Dynamic Host Configuration Protocol}", howpublished="RFC 1531 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1531", pages="1--39", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1541", url="https://www.rfc-editor.org/rfc/rfc1531.txt", key="RFC 1531", abstract={The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. [STANDARDS-TRACK]}, keywords="DHCP", doi="10.17487/RFC1531", } @misc{rfc1532, author="W. Wimer", title="{Clarifications and Extensions for the Bootstrap Protocol}", howpublished="RFC 1532 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1532", pages="1--22", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1542", url="https://www.rfc-editor.org/rfc/rfc1532.txt", key="RFC 1532", abstract={Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of ``BOOTP relay agents'' (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. [STANDARDS-TRACK]}, keywords="BOOTP", doi="10.17487/RFC1532", } @misc{rfc1533, author="S. Alexander and R. Droms", title="{DHCP Options and BOOTP Vendor Extensions}", howpublished="RFC 1533 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1533", pages="1--30", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2132", url="https://www.rfc-editor.org/rfc/rfc1533.txt", key="RFC 1533", abstract={This document specifies the current set of DHCP options. [STANDARDS-TRACK]}, keywords="Dynamic, Host, Configuration, Bootstrap", doi="10.17487/RFC1533", } @misc{rfc1534, author="R. Droms", title="{Interoperation Between DHCP and BOOTP}", howpublished="RFC 1534 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1534", pages="1--4", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1534.txt", key="RFC 1534", abstract={DHCP provides a superset of the functions provided by BOOTP. This document describes the interactions between DHCP and BOOTP network participants. [STANDARDS-TRACK]}, keywords="DHCP-BOOTP, Dynamic, Host, Configuration, Bootstrap", doi="10.17487/RFC1534", } @misc{rfc1535, author="E. Gavron", title="{A Security Problem and Proposed Correction With Widely Deployed DNS Software}", howpublished="RFC 1535 (Informational)", series="Internet Request for Comments", type="RFC", number="1535", pages="1--5", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1535.txt", key="RFC 1535", abstract={This document discusses a flaw in some of the currently distributed name resolver clients. The flaw exposes a security weakness related to the search heuristic invoked by these same resolvers when users provide a partial domain name, and which is easy to exploit. This document points out the flaw, a case in point, and a solution. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Domain, Name, System", doi="10.17487/RFC1535", } @misc{rfc1536, author="A. Kumar and J. Postel and C. Neuman and P. Danzig and S. Miller", title="{Common DNS Implementation Errors and Suggested Fixes}", howpublished="RFC 1536 (Informational)", series="Internet Request for Comments", type="RFC", number="1536", pages="1--12", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1536.txt", key="RFC 1536", abstract={This memo describes common errors seen in DNS implementations and suggests some fixes. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Domain, Name, System", doi="10.17487/RFC1536", } @misc{rfc1537, author="P. Beertema", title="{Common DNS Data File Configuration Errors}", howpublished="RFC 1537 (Informational)", series="Internet Request for Comments", type="RFC", number="1537", pages="1--9", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1912", url="https://www.rfc-editor.org/rfc/rfc1537.txt", key="RFC 1537", abstract={This memo describes errors often found in DNS data files. It points out common mistakes system administrators tend to make and why they often go unnoticed for long periods of time. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="Domain, Name, System", doi="10.17487/RFC1537", } @misc{rfc1538, author="W. Behl and B. Sterling and W. Teskey", title="{Advanced SNA/IP : A Simple SNA Transport Protocol}", howpublished="RFC 1538 (Informational)", series="Internet Request for Comments", type="RFC", number="1538", pages="1--10", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1538.txt", key="RFC 1538", abstract={This RFC provides information for the Internet community about a method for establishing and maintaining SNA sessions over an IP internet. This memo provides information for the Internet community. It does not specify an Internet standard.}, keywords="ADSNA-IP, Domain, Name, System", doi="10.17487/RFC1538", } @misc{rfc1539, author="G. Malkin", title="{The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force}", howpublished="RFC 1539 (Informational)", series="Internet Request for Comments", type="RFC", number="1539", pages="1--22", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1718", url="https://www.rfc-editor.org/rfc/rfc1539.txt", key="RFC 1539", abstract={The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 17]}, keywords="Introduction", doi="10.17487/RFC1539", } @misc{rfc1540, author="J. Postel", title="{Internet Official Protocol Standards}", howpublished="RFC 1540 (Historic)", series="Internet Request for Comments", type="RFC", number="1540", pages="1--34", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1600", url="https://www.rfc-editor.org/rfc/rfc1540.txt", key="RFC 1540", abstract={This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK]}, keywords="status, procedure, index", doi="10.17487/RFC1540", } @misc{rfc1541, author="R. Droms", title="{Dynamic Host Configuration Protocol}", howpublished="RFC 1541 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1541", pages="1--39", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2131", url="https://www.rfc-editor.org/rfc/rfc1541.txt", key="RFC 1541", abstract={The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. DHCP is based on the Bootstrap Protocol (BOOTP) adding the capability of automatic allocation of reusable network addresses and additional configuration options. [STANDARDS-TRACK]}, keywords="DHCP", doi="10.17487/RFC1541", } @misc{rfc1542, author="W. Wimer", title="{Clarifications and Extensions for the Bootstrap Protocol}", howpublished="RFC 1542 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1542", pages="1--23", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1542.txt", key="RFC 1542", abstract={Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of ``BOOTP relay agents'' (originally called ``BOOTP forwarding agents''). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. [STANDARDS-TRACK]}, keywords="BOOTP", doi="10.17487/RFC1542", } @misc{rfc1543, author="J. Postel", title="{Instructions to RFC Authors}", howpublished="RFC 1543 (Informational)", series="Internet Request for Comments", type="RFC", number="1543", pages="1--16", year=1993, month=oct, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2223", url="https://www.rfc-editor.org/rfc/rfc1543.txt", key="RFC 1543", abstract={This Request for Comments (RFC) provides information about the preparation of RFCs, and certain policies relating to the publication of RFCs. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Request, For, Comment", doi="10.17487/RFC1543", } @misc{rfc1544, author="M. Rose", title="{The Content-MD5 Header Field}", howpublished="RFC 1544 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1544", pages="1--3", year=1993, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1864", url="https://www.rfc-editor.org/rfc/rfc1544.txt", key="RFC 1544", abstract={This memo defines the use of an optional header field, Content-MD5, which may be used as a message integrity check (MIC), to verify that the decoded data are the same data that were initially sent. [STANDARDS-TRACK]}, keywords="MIME, EMail, Integrity, MIC, Digest", doi="10.17487/RFC1544", } @misc{rfc1545, author="D. Piscitello", title="{FTP Operation Over Big Address Records (FOOBAR)}", howpublished="RFC 1545 (Experimental)", series="Internet Request for Comments", type="RFC", number="1545", pages="1--5", year=1993, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1639", url="https://www.rfc-editor.org/rfc/rfc1545.txt", key="RFC 1545", abstract={This RFC specifies a method for assigning long addresses in the HOST- PORT specification for the data port to be used in establishing a data connection for File Transfer Protocol, FTP (STD 9, RFC 959). This is a general solution, applicable for all ``next generation'' IP alternatives, and can also be extended to allow FTP operation over transport interfaces other than TCP. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="FTP, File Transfer, PORT, PASV, LPRT, LPSV", doi="10.17487/RFC1545", } @misc{rfc1546, author="C. Partridge and T. Mendez and W. Milliken", title="{Host Anycasting Service}", howpublished="RFC 1546 (Informational)", series="Internet Request for Comments", type="RFC", number="1546", pages="1--9", year=1993, month=nov, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1546.txt", key="RFC 1546", abstract={This RFC describes an internet anycasting service for IP. The primary purpose of this memo is to establish the semantics of an anycasting service within an IP internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Resource Location, Multicasting", doi="10.17487/RFC1546", } @misc{rfc1547, author="D. Perkins", title="{Requirements for an Internet Standard Point-to-Point Protocol}", howpublished="RFC 1547 (Informational)", series="Internet Request for Comments", type="RFC", number="1547", pages="1--21", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1547.txt", key="RFC 1547", abstract={This document discusses the evaluation criteria for an Internet Standard Data Link Layer protocol to be used with point-to-point links. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="PPP, link, serial, line", doi="10.17487/RFC1547", } @misc{rfc1548, author="W. Simpson", title="{The Point-to-Point Protocol (PPP)}", howpublished="RFC 1548 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1548", pages="1--53", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1661, updated by RFC 1570", url="https://www.rfc-editor.org/rfc/rfc1548.txt", key="RFC 1548", abstract={This document defines the PPP organization and methodology, and the PPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS-TRACK]}, keywords="link, serial, line", doi="10.17487/RFC1548", } @misc{rfc1549, author="W. Simpson", title="{PPP in HDLC Framing}", howpublished="RFC 1549 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1549", pages="1--18", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1662", url="https://www.rfc-editor.org/rfc/rfc1549.txt", key="RFC 1549", abstract={This document describes the use of HDLC for framing PPP encapsulated packets. [STANDARDS-TRACK]}, keywords="point, link, serial, line", doi="10.17487/RFC1549", } @misc{rfc1550, author="S. Bradner and A. Mankin", title="{IP: Next Generation (IPng) White Paper Solicitation}", howpublished="RFC 1550 (Informational)", series="Internet Request for Comments", type="RFC", number="1550", pages="1--6", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1550.txt", key="RFC 1550", abstract={This memo solicits white papers on topics related to the IPng requirements and selection criteria. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, doi="10.17487/RFC1550", } @misc{rfc1551, author="M. Allen", title="{Novell IPX Over Various WAN Media (IPXWAN)}", howpublished="RFC 1551 (Informational)", series="Internet Request for Comments", type="RFC", number="1551", pages="1--22", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1634", url="https://www.rfc-editor.org/rfc/rfc1551.txt", key="RFC 1551", abstract={This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common ``IPX WAN'' protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Internetworking, Packet, Exchange", doi="10.17487/RFC1551", } @misc{rfc1552, author="W. Simpson", title="{The PPP Internetworking Packet Exchange Control Protocol (IPXCP)}", howpublished="RFC 1552 (Historic)", series="Internet Request for Comments", type="RFC", number="1552", pages="1--16", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1552.txt", key="RFC 1552", abstract={This document defines the Network Control Protocol for establishing and configuring the IPX protocol over PPP. [STANDARDS-TRACK]}, keywords="IPXCP, IPX, point, serial, line, link", doi="10.17487/RFC1552", } @misc{rfc1553, author="S. Mathur and M. Lewis", title="{Compressing IPX Headers Over WAN Media (CIPX)}", howpublished="RFC 1553 (Historic)", series="Internet Request for Comments", type="RFC", number="1553", pages="1--23", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1553.txt", key="RFC 1553", abstract={This document describes a method for compressing the headers of IPX datagrams (CIPX). [STANDARDS-TRACK]}, keywords="CIPX, Internetworking, Packet, Exchange", doi="10.17487/RFC1553", } @misc{rfc1554, author="M. Ohta and K. Handa", title="{ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP}", howpublished="RFC 1554 (Informational)", series="Internet Request for Comments", type="RFC", number="1554", pages="1--6", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1554.txt", key="RFC 1554", abstract={This memo describes a text encoding scheme: ``ISO-2022-JP-2'', which is used experimentally for electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. The encoding is a multilingual extension of ``ISO-2022-JP'', the existing encoding for Japanese [2022JP]. The encoding is supported by an Emacs based multilingual text editor: MULE [MULE]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Character Set, Japanese", doi="10.17487/RFC1554", } @misc{rfc1555, author="H. Nussbacher and Y. Bourvine", title="{Hebrew Character Encoding for Internet Messages}", howpublished="RFC 1555 (Informational)", series="Internet Request for Comments", type="RFC", number="1555", pages="1--5", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1555.txt", key="RFC 1555", abstract={This document describes the encoding used in electronic mail [RFC822] for transferring Hebrew. The standard devised makes use of MIME [RFC1521] and ISO-8859-8. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Character Set", doi="10.17487/RFC1555", } @misc{rfc1556, author="H. Nussbacher", title="{Handling of Bi-directional Texts in MIME}", howpublished="RFC 1556 (Informational)", series="Internet Request for Comments", type="RFC", number="1556", pages="1--3", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1556.txt", key="RFC 1556", abstract={This document describes the format and syntax of the ``direction'' keyword to be used with bi-directional texts in MIME. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Character Set", doi="10.17487/RFC1556", } @misc{rfc1557, author="U. Choi and K. Chon and H. Park", title="{Korean Character Encoding for Internet Messages}", howpublished="RFC 1557 (Informational)", series="Internet Request for Comments", type="RFC", number="1557", pages="1--5", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1557.txt", key="RFC 1557", abstract={This document describes the encoding method being used to represent Korean characters in both header and body part of the Internet mail messages [RFC822]. This encoding method was specified in 1991, and has since then been used. It has now widely being used in Korean IP networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Character Set", doi="10.17487/RFC1557", } @misc{rfc1558, author="T. Howes", title="{A String Representation of LDAP Search Filters}", howpublished="RFC 1558 (Informational)", series="Internet Request for Comments", type="RFC", number="1558", pages="1--3", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1960", url="https://www.rfc-editor.org/rfc/rfc1558.txt", key="RFC 1558", abstract={The Lightweight Directory Access Protocol (LDAP) defines a network representation of a search filter transmitted to an LDAP server. Some applications may find it useful to have a common way of representing these search filters in a human-readable form. This document defines a human-readable string format for representing LDAP search filters. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="X.500, Directory", doi="10.17487/RFC1558", } @misc{rfc1559, author="J. Saperia", title="{DECnet Phase IV MIB Extensions}", howpublished="RFC 1559 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1559", pages="1--69", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1559.txt", key="RFC 1559", abstract={This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. It reflects changes which are the result of operational experience based on RFC 1289. [STANDARDS-TRACK]}, keywords="DECNET-MIB, Management, SNMP", doi="10.17487/RFC1559", } @misc{rfc1560, author="B. Leiner and Y. Rekhter", title="{The MultiProtocol Internet}", howpublished="RFC 1560 (Informational)", series="Internet Request for Comments", type="RFC", number="1560", pages="1--7", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1560.txt", key="RFC 1560", abstract={There has recently been considerable discussion on two topics: MultiProtocol approaches in the Internet and the selection of a next generation Internet Protocol. This document suggests a strawman position for goals and approaches for the IETF/IESG/IAB in these areas. It takes the view that these two topics are related, and proposes directions for the IETF/IESG/IAB to pursue. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Architecture, Protocol", doi="10.17487/RFC1560", } @misc{rfc1561, author="D. Piscitello", title="{Use of ISO CLNP in TUBA Environments}", howpublished="RFC 1561 (Experimental)", series="Internet Request for Comments", type="RFC", number="1561", pages="1--25", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1561.txt", key="RFC 1561", abstract={This memo specifies a profile of the ISO/IEC 8473 Connectionless-mode Network Layer Protocol for use in conjunction with RFC 1347, TCP/UDP over Bigger Addresses. It describes the use of CLNP to provide the lower-level service expected by Transmission Control Protocol and User Datagram Protocol. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="CLNP-TUBA, OSI, IP, Internet, Protocol", doi="10.17487/RFC1561", } @misc{rfc1562, author="G. Michaelson and M. Prior", title="{Naming Guidelines for the AARNet X.500 Directory Service}", howpublished="RFC 1562 (Informational)", series="Internet Request for Comments", type="RFC", number="1562", pages="1--4", year=1993, month=dec, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1562.txt", key="RFC 1562", abstract={This document is an AARNet (Australian Academic and Research Network) Engineering Note (AEN-001). AARNet Engineering Notes are engineering documents of the AARNet Engineering Working Group, and record current or proposed operational practices related to the provision of Internetworking services within Australia, and AARNet in particular. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Australia", doi="10.17487/RFC1562", } @misc{rfc1563, author="N. Borenstein", title="{The text/enriched MIME Content-type}", howpublished="RFC 1563 (Informational)", series="Internet Request for Comments", type="RFC", number="1563", pages="1--16", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1896", url="https://www.rfc-editor.org/rfc/rfc1563.txt", key="RFC 1563", abstract={MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail. This document defines one particular type of MIME data, the text/enriched type, a refinement of the ``text/richtext'' type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="email, mail, richtext", doi="10.17487/RFC1563", } @misc{rfc1564, author="P. Barker and R. Hedberg", title="{DSA Metrics (OSI-DS 34 (v3))}", howpublished="RFC 1564 (Informational)", series="Internet Request for Comments", type="RFC", number="1564", pages="1--21", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1564.txt", key="RFC 1564", abstract={This document defines a set of criteria by which a DSA implementation may be judged. Particular issues covered include conformance to standards; performance; demonstrated interoperability. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="x.500, Directory, Service, Agent", doi="10.17487/RFC1564", } @misc{rfc1565, author="S. Kille and N. Freed", title="{Network Services Monitoring MIB}", howpublished="RFC 1565 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1565", pages="1--17", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2248", url="https://www.rfc-editor.org/rfc/rfc1565.txt", key="RFC 1565", abstract={This document defines a MIB which contains the elements common to the monitoring of any network service application. This information includes a table of all monitorable network service applications, a count of the associations (connections) to each application, and basic information about the parameters and status of each application-related association. [STANDARDS-TRACK]}, keywords="Management, Information, Base", doi="10.17487/RFC1565", } @misc{rfc1566, author="S. Kille and N. Freed", title="{Mail Monitoring MIB}", howpublished="RFC 1566 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1566", pages="1--20", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 2249, 2789", url="https://www.rfc-editor.org/rfc/rfc1566.txt", key="RFC 1566", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, this memo extends the basic Network Services Monitoring MIB to allow monitoring of Message Transfer Agents (MTAs). It may also be used to monitor MTA components within gateways. [STANDARDS-TRACK]}, keywords="Management, Information, Base", doi="10.17487/RFC1566", } @misc{rfc1567, author="G. Mansfield and S. Kille", title="{X.500 Directory Monitoring MIB}", howpublished="RFC 1567 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1567", pages="1--18", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2605", url="https://www.rfc-editor.org/rfc/rfc1567.txt", key="RFC 1567", abstract={This document defines a portion of the Management Information Base (MIB). It defines the MIB for monitoring Directory System Agents (DSA), a component of the OSI Directory. This MIB will be used in conjunction with the APPLICATION-MIB for monitoring DSAs. [STANDARDS-TRACK]}, keywords="X500-MIB, Management, Information, Base", doi="10.17487/RFC1567", } @misc{rfc1568, author="A. Gwinn", title="{Simple Network Paging Protocol - Version 1(b)}", howpublished="RFC 1568 (Informational)", series="Internet Request for Comments", type="RFC", number="1568", pages="1--8", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1645", url="https://www.rfc-editor.org/rfc/rfc1568.txt", key="RFC 1568", abstract={This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Beeper", doi="10.17487/RFC1568", } @misc{rfc1569, author="M. Rose", title="{Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures}", howpublished="RFC 1569 (Informational)", series="Internet Request for Comments", type="RFC", number="1569", pages="1--6", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1703", url="https://www.rfc-editor.org/rfc/rfc1569.txt", key="RFC 1569", abstract={This memo describes a technique for radio paging using the Internet mail infrastructure. In particular, this memo focuses on the case in which radio pagers are identified via the international telephone network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Beeper", doi="10.17487/RFC1569", } @misc{rfc1570, author="W. Simpson", title="{PPP LCP Extensions}", howpublished="RFC 1570 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1570", pages="1--19", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Updated by RFC 2484", url="https://www.rfc-editor.org/rfc/rfc1570.txt", key="RFC 1570", abstract={The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection. This document defines several additional LCP features which have been suggested over the past few years. [STANDARDS-TRACK]}, keywords="PPP-LCP, Point-to Point, Link, Control, Protocol, serial, line", doi="10.17487/RFC1570", } @misc{rfc1571, author="D. Borman", title="{Telnet Environment Option Interoperability Issues}", howpublished="RFC 1571 (Informational)", series="Internet Request for Comments", type="RFC", number="1571", pages="1--4", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1571.txt", key="RFC 1571", abstract={This document describes a method for allowing implementors to ensure that their implementation of the Environment option will be interoperable with as many other implementations as possible, by providing a set of heuristics that can be used to help identify which definitions for VAR and VALUE are being used by the other side of the connection. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, doi="10.17487/RFC1571", } @misc{rfc1572, author="S. Alexander", title="{Telnet Environment Option}", howpublished="RFC 1572 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1572", pages="1--7", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1572.txt", key="RFC 1572", abstract={This document specifies a mechanism for passing environment information between a telnet client and server. Use of this mechanism enables a telnet user to propagate configuration information to a remote host when connecting. [STANDARDS-TRACK]}, keywords="TOPT-ENVIR", doi="10.17487/RFC1572", } @misc{rfc1573, author="K. McCloghrie and F. Kastenholz", title="{Evolution of the Interfaces Group of MIB-II}", howpublished="RFC 1573 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1573", pages="1--55", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2233", url="https://www.rfc-editor.org/rfc/rfc1573.txt", key="RFC 1573", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing Network Interfaces. [STANARDS-TRACK]}, keywords="Management, Information, Base", doi="10.17487/RFC1573", } @misc{rfc1574, author="S. Hares and C. Wittbrodt", title="{Essential Tools for the OSI Internet}", howpublished="RFC 1574 (Informational)", series="Internet Request for Comments", type="RFC", number="1574", pages="1--13", year=1994, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1574.txt", key="RFC 1574", abstract={This document specifies the following three necessary tools to debug problems in the deployment and maintenance of networks using ISO 8473 (CLNP): ping or OSI Echo function, traceroute function which uses the OSI Echo function, and routing table dump function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Echo, Traceroute, Routing Table, CLNP", doi="10.17487/RFC1574", } @misc{rfc1575, author="S. Hares and C. Wittbrodt", title="{An Echo Function for CLNP (ISO 8473)}", howpublished="RFC 1575 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1575", pages="1--9", year=1994, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1575.txt", key="RFC 1575", abstract={This memo defines an echo function for the connection-less network layer protocol. The mechanism that is mandated here is in the final process of being standardized by ISO as ``Amendment X: Addition of an Echo function to ISO 8473'' an integral part of Version 2 of ISO 8473. [STANDARDS-TRACK]}, keywords="ISO-TS-ECHO", doi="10.17487/RFC1575", } @misc{rfc1576, author="J. Penner", title="{TN3270 Current Practices}", howpublished="RFC 1576 (Informational)", series="Internet Request for Comments", type="RFC", number="1576", pages="1--12", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1576.txt", key="RFC 1576", abstract={This document describes the existing implementation of transferring 3270 display terminal data using currently available telnet capabilities. The name traditionally associated with this implementation is TN3270. This memo provides information for the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Telnet Option Terminal Type EOR Binary", doi="10.17487/RFC1576", } @misc{rfc1577, author="M. Laubach", title="{Classical IP and ARP over ATM}", howpublished="RFC 1577 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1577", pages="1--17", year=1994, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2225", url="https://www.rfc-editor.org/rfc/rfc1577.txt", key="RFC 1577", abstract={This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS). [STANDARDS-TRACK]}, keywords="Internet, Protocol, Address, Resolution, Asynchronous, Transmission, Mode", doi="10.17487/RFC1577", } @misc{rfc1578, author="J. Sellers", title="{FYI on Questions and Answers - Answers to Commonly Asked ``Primary and Secondary School Internet User'' Questions}", howpublished="RFC 1578 (Informational)", series="Internet Request for Comments", type="RFC", number="1578", pages="1--53", year=1994, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1941", url="https://www.rfc-editor.org/rfc/rfc1578.txt", key="RFC 1578", abstract={The goal of this FYI RFC is to document the questions most commonly asked about the Internet by those in the primary and secondary school community, and to provide pointers to sources which answer those questions. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 22]}, keywords="K12", doi="10.17487/RFC1578", } @misc{rfc1579, author="S. Bellovin", title="{Firewall-Friendly FTP}", howpublished="RFC 1579 (Informational)", series="Internet Request for Comments", type="RFC", number="1579", pages="1--4", year=1994, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1579.txt", key="RFC 1579", abstract={This memo describes a suggested change to the behavior of FTP client programs. This document provides information for the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="file, transfer, PORT, PASV, Security", doi="10.17487/RFC1579", } @misc{rfc1580, author="EARN Staff", title="{Guide to Network Resource Tools}", howpublished="RFC 1580 (Informational)", series="Internet Request for Comments", type="RFC", number="1580", pages="1--107", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1580.txt", key="RFC 1580", abstract={The purpose of this guide is to supply the basic information that anyone on the network needs to try out and begin using tools. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 23]}, keywords="EARN, BITNET, Gopher, World-Wide Web, WWW, WAIS, Archie, Whois, X.500, Netfind, Trickle, BIFTP, Listserv, Netnews, Astra, NetServ, Mail Base, Prospero, IRC, Relay", doi="10.17487/RFC1580", } @misc{rfc1581, author="G. Meyer", title="{Protocol Analysis for Extensions to RIP to Support Demand Circuits}", howpublished="RFC 1581 (Informational)", series="Internet Request for Comments", type="RFC", number="1581", pages="1--4", year=1994, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1581.txt", key="RFC 1581", abstract={As required by Routing Protocol Criteria, this report documents the key features of Routing over Demand Circuits on Wide Area Networks - RIP and the current implementation experience. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="routing, Protocol", doi="10.17487/RFC1581", } @misc{rfc1582, author="G. Meyer", title="{Extensions to RIP to Support Demand Circuits}", howpublished="RFC 1582 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1582", pages="1--29", year=1994, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1582.txt", key="RFC 1582", abstract={This memo defines a generalized modification which can be applied to Bellman-Ford (or distance vector) algorithm information broadcasting protocols. [STANDARDS-TRACK]}, keywords="RIP-DC, routing, Protocol", doi="10.17487/RFC1582", } @misc{rfc1583, author="J. Moy", title="{OSPF Version 2}", howpublished="RFC 1583 (Draft Standard)", series="Internet Request for Comments", type="RFC", number="1583", pages="1--216", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2178", url="https://www.rfc-editor.org/rfc/rfc1583.txt", key="RFC 1583", abstract={This memo documents version 2 of the OSPF protocol. OSPF is a link- state routing protocol. [STANDARDS-TRACK]}, keywords="equal-cost, multipath, link state, LSA", doi="10.17487/RFC1583", } @misc{rfc1584, author="J. Moy", title="{Multicast Extensions to OSPF}", howpublished="RFC 1584 (Historic)", series="Internet Request for Comments", type="RFC", number="1584", pages="1--102", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1584.txt", key="RFC 1584", abstract={This memo documents enhancements to the OSPF protocol enabling the routing of IP multicast datagrams. [STANDARDS-TRACK]}, keywords="OSPF-Multi, Open, Shortest, Path, First", doi="10.17487/RFC1584", } @misc{rfc1585, author="J. Moy", title="{MOSPF: Analysis and Experience}", howpublished="RFC 1585 (Informational)", series="Internet Request for Comments", type="RFC", number="1585", pages="1--13", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1585.txt", key="RFC 1585", abstract={This memo documents how the MOSPF protocol satisfies the requirements imposed on Internet routing protocols by ``Internet Engineering Task Force internet routing protocol standardization criteria'' ([RFC 1264]). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Multicast, Open, Shortest, Path, First, OSPF", doi="10.17487/RFC1585", } @misc{rfc1586, author="O. deSouza and M. Rodrigues", title="{Guidelines for Running OSPF Over Frame Relay Networks}", howpublished="RFC 1586 (Informational)", series="Internet Request for Comments", type="RFC", number="1586", pages="1--6", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1586.txt", key="RFC 1586", abstract={This memo specifies guidelines for implementors and users of the Open Shortest Path First (OSPF) routing protocol to bring about improvements in how the protocol runs over frame relay networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="FR, Open, Shortest, Path, First", doi="10.17487/RFC1586", } @misc{rfc1587, author="R. Coltun and V. Fuller", title="{The OSPF NSSA Option}", howpublished="RFC 1587 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1587", pages="1--17", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 3101", url="https://www.rfc-editor.org/rfc/rfc1587.txt", key="RFC 1587", abstract={This document describes a new optional type of OSPF area, somewhat humorously referred to as a ``not-so-stubby'' area (or NSSA). NSSAs are similar to the existing OSPF stub area configuration option but have the additional capability of importing AS external routes in a limited fashion. [STANDARDS-TRACK]}, keywords="OSPF-NSSA, Open, Shortest, Path, First, not so stubby, area, routing, protocol", doi="10.17487/RFC1587", } @misc{rfc1588, author="J. Postel and C. Anderson", title="{White Pages Meeting Report}", howpublished="RFC 1588 (Informational)", series="Internet Request for Comments", type="RFC", number="1588", pages="1--35", year=1994, month=feb, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1588.txt", key="RFC 1588", abstract={This report describes the results of a meeting held at the November IETF (Internet Engineering Task Force) in Houston, TX, on November 2, 1993, to discuss the future of and approaches to a white pages directory services for the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="X-500 directory", doi="10.17487/RFC1588", } @misc{rfc1589, author="D. Mills", title="{A Kernel Model for Precision Timekeeping}", howpublished="RFC 1589 (Informational)", series="Internet Request for Comments", type="RFC", number="1589", pages="1--37", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1589.txt", key="RFC 1589", abstract={This memorandum describes an engineering model which implements a precision time-of-day function for a generic operating system. The model is based on the principles of disciplined oscillators and phase-lock loops (PLL) often found in the engineering literature. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Time, NTP, Clock", doi="10.17487/RFC1589", } @misc{rfc1590, author="J. Postel", title="{Media Type Registration Procedure}", howpublished="RFC 1590 (Informational)", series="Internet Request for Comments", type="RFC", number="1590", pages="1--7", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFCs 2045, 2046, 2047, 2048, 2049", url="https://www.rfc-editor.org/rfc/rfc1590.txt", key="RFC 1590", abstract={Several questions have been raised about the requirements and administrative procedure for registering MIME content-type and subtypes, and the use of these Media Types for other applications. This document addresses these issues and specifies a procedure for the registration of new Media Types (content-type/subtypes). It also generalizes the scope of use of these Media Types to make it appropriate to use the same registrations and specifications with other applications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="email, multimedia", doi="10.17487/RFC1590", } @misc{rfc1591, author="J. Postel", title="{Domain Name System Structure and Delegation}", howpublished="RFC 1591 (Informational)", series="Internet Request for Comments", type="RFC", number="1591", pages="1--7", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1591.txt", key="RFC 1591", abstract={This memo provides some information on the structure of the names in the Domain Name System (DNS), specifically the top-level domain names; and on the administration of domains. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="DNS, Policy, Top-Level, TLD", doi="10.17487/RFC1591", } @misc{rfc1592, author="B. Wijnen and G. Carpenter and K. Curran and A. Sehgal and G. Waters", title="{Simple Network Management Protocol Distributed Protocol Interface Version 2.0}", howpublished="RFC 1592 (Experimental)", series="Internet Request for Comments", type="RFC", number="1592", pages="1--54", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1592.txt", key="RFC 1592", abstract={This RFC describes version 2.0 of a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="SNMP-DPI, SNMP, DPT, IBM", doi="10.17487/RFC1592", } @misc{rfc1593, author="W. McKenzie and J. Cheng", title="{SNA APPN Node MIB}", howpublished="RFC 1593 (Informational)", series="Internet Request for Comments", type="RFC", number="1593", pages="1--120", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1593.txt", key="RFC 1593", abstract={This RFC describes IBM's SNMP support for SNA Advanced Peer-to-Peer Networking (APPN) nodes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="IBM, Management", doi="10.17487/RFC1593", } @misc{rfc1594, author="A. Marine and J. Reynolds and G. Malkin", title="{FYI on Questions and Answers - Answers to Commonly asked ``New Internet User'' Questions}", howpublished="RFC 1594 (Informational)", series="Internet Request for Comments", type="RFC", number="1594", pages="1--44", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2664", url="https://www.rfc-editor.org/rfc/rfc1594.txt", key="RFC 1594", abstract={This FYI RFC is one of two FYI's called, ``Questions and Answers'' (Q/A). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 4]}, keywords="documentation, help, information, FAQ", doi="10.17487/RFC1594", } @misc{rfc1595, author="T. Brown and K. Tesink", title="{Definitions of Managed Objects for the SONET/SDH Interface Type}", howpublished="RFC 1595 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1595", pages="1--59", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2558", url="https://www.rfc-editor.org/rfc/rfc1595.txt", key="RFC 1595", keywords="SONET-MIB, MIB, Management, SNMP", doi="10.17487/RFC1595", } @misc{rfc1596, author="T. Brown", title="{Definitions of Managed Objects for Frame Relay Service}", howpublished="RFC 1596 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1596", pages="1--46", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1604", url="https://www.rfc-editor.org/rfc/rfc1596.txt", key="RFC 1596", keywords="FR, MIB, Management, SNMP", doi="10.17487/RFC1596", } @misc{rfc1597, author="Y. Rekhter and B. Moskowitz and D. Karrenberg and G. de Groot", title="{Address Allocation for Private Internets}", howpublished="RFC 1597 (Informational)", series="Internet Request for Comments", type="RFC", number="1597", pages="1--8", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1918", url="https://www.rfc-editor.org/rfc/rfc1597.txt", key="RFC 1597", abstract={This RFC describes methods to preserve IP address space by not allocating globally unique IP addresses to hosts private to an enterprise while still permitting full network layer connectivity between all hosts inside an enterprise as well as between all public hosts of different enterprises. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="IP, Network, Number, Local", doi="10.17487/RFC1597", } @misc{rfc1598, author="W. Simpson", title="{PPP in X.25}", howpublished="RFC 1598 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1598", pages="1--8", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1598.txt", key="RFC 1598", abstract={The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes the use of X.25 for framing PPP encapsulated packets. [STANDARDS-TRACK]}, keywords="PPP-X25, point", doi="10.17487/RFC1598", } @misc{rfc1599, author="M. Kennedy", title="{Summary of 1500-1599}", howpublished="RFC 1599 (Informational)", series="Internet Request for Comments", type="RFC", number="1599", pages="1--22", year=1997, month=jan, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1599.txt", key="RFC 1599", keywords="Index", doi="10.17487/RFC1599", } @misc{rfc1600, author="J. Postel", title="{Internet Official Protocol Standards}", howpublished="RFC 1600 (Historic)", series="Internet Request for Comments", type="RFC", number="1600", pages="1--36", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1610", url="https://www.rfc-editor.org/rfc/rfc1600.txt", key="RFC 1600", abstract={This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]}, keywords="status, procedure, index", doi="10.17487/RFC1600", } @misc{rfc1601, author="C. Huitema", title="{Charter of the Internet Architecture Board (IAB)}", howpublished="RFC 1601 (Informational)", series="Internet Request for Comments", type="RFC", number="1601", pages="1--6", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2850", url="https://www.rfc-editor.org/rfc/rfc1601.txt", key="RFC 1601", abstract={This memo documents the composition, selection, roles, and organization of the Internet Architecture Board and its subsidiary organizations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="ISOC, Internet Society, IETF, IRTF", doi="10.17487/RFC1601", } @misc{rfc1602, author="Internet Architecture Board and Internet Engineering Steering Group", title="{The Internet Standards Process -- Revision 2}", howpublished="RFC 1602 (Informational)", series="Internet Request for Comments", type="RFC", number="1602", pages="1--37", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2026, updated by RFC 1871", url="https://www.rfc-editor.org/rfc/rfc1602.txt", key="RFC 1602", abstract={This document is a revision of RFC 1310, which defined the official procedures for creating and documenting Internet Standards. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, doi="10.17487/RFC1602", } @misc{rfc1603, author="E. Huizer and D. Crocker", title="{IETF Working Group Guidelines and Procedures}", howpublished="RFC 1603 (Informational)", series="Internet Request for Comments", type="RFC", number="1603", pages="1--29", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2418, updated by RFC 1871", url="https://www.rfc-editor.org/rfc/rfc1603.txt", key="RFC 1603", abstract={This document describes the guidelines and procedures for formation and operation of IETF working groups. It describes the formal relationship between IETF participants WG and the Internet Engineering Steering Group (IESG). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="WG", doi="10.17487/RFC1603", } @misc{rfc1604, author="T. Brown", title="{Definitions of Managed Objects for Frame Relay Service}", howpublished="RFC 1604 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1604", pages="1--46", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2954", url="https://www.rfc-editor.org/rfc/rfc1604.txt", key="RFC 1604", abstract={This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service. [STANDARDS-TRACK]}, keywords="FR-MIB, MIB, Management, SNMP, Network", doi="10.17487/RFC1604", } @misc{rfc1605, author="W. Shakespeare", title="{SONET to Sonnet Translation}", howpublished="RFC 1605 (Informational)", series="Internet Request for Comments", type="RFC", number="1605", pages="1--3", year=1994, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1605.txt", key="RFC 1605", abstract={Because Synchronous Optical Network (SONET) transmits data in frames of bytes, it is fairly easy to envision ways to compress SONET frames to yield higher bandwidth over a given fiber optic link. This memo describes a particular method, SONET Over Novel English Translation (SONNET). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Humor", doi="10.17487/RFC1605", } @misc{rfc1606, author="J. Onions", title="{A Historical Perspective On The Usage Of IP Version 9}", howpublished="RFC 1606 (Informational)", series="Internet Request for Comments", type="RFC", number="1606", pages="1--4", year=1994, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1606.txt", key="RFC 1606", abstract={This paper reviews the usages of the old IP version protocol. It considers some of its successes and its failures. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Humor", doi="10.17487/RFC1606", } @misc{rfc1607, author="V. Cerf", title="{A VIEW FROM THE 21ST CENTURY}", howpublished="RFC 1607 (Informational)", series="Internet Request for Comments", type="RFC", number="1607", pages="1--14", year=1994, month=apr, day="1", issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1607.txt", key="RFC 1607", abstract={This document is a composition of letters discussing a possible future. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="V. Cerf", doi="10.17487/RFC1607", } @misc{rfc1608, author="T. Johannsen and G. Mansfield and M. Kosters and S. Sataluri", title="{Representing IP Information in the X.500 Directory}", howpublished="RFC 1608 (Experimental)", series="Internet Request for Comments", type="RFC", number="1608", pages="1--20", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1608.txt", key="RFC 1608", abstract={This document describes the objects necessary to include information about IP networks and IP numbers in the X.500 Directory. It extends the work ``Charting networks in the X.500 Directory'' [1] where a general framework is presented for representing networks in the Directory by applying it to IP networks. This memo defines an Experimental Protocol for the Internet community.}, keywords="X500-DIR, Data, Structure, Schemo", doi="10.17487/RFC1608", } @misc{rfc1609, author="G. Mansfield and T. Johannsen and M. Knopper", title="{Charting Networks in the X.500 Directory}", howpublished="RFC 1609 (Experimental)", series="Internet Request for Comments", type="RFC", number="1609", pages="1--15", year=1994, month=mar, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1609.txt", key="RFC 1609", abstract={This document presents a model in which a communication network with all its related details and descriptions can be represented in the X.500 Directory. This memo defines an Experimental Protocol for the Internet community.}, keywords="X500-CHART, Data, Structure, Schemo", doi="10.17487/RFC1609", } @misc{rfc1610, author="J. Postel", title="{Internet Official Protocol Standards}", howpublished="RFC 1610 (Historic)", series="Internet Request for Comments", type="RFC", number="1610", pages="1--36", year=1994, month=jul, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 1720", url="https://www.rfc-editor.org/rfc/rfc1610.txt", key="RFC 1610", abstract={This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]}, keywords="status, procedure, index", doi="10.17487/RFC1610", } @misc{rfc1611, author="R. Austein and J. Saperia", title="{DNS Server MIB Extensions}", howpublished="RFC 1611 (Historic)", series="Internet Request for Comments", type="RFC", number="1611", pages="1--30", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1611.txt", key="RFC 1611", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of extensions which instrument DNS name server functions. This memo was produced by the DNS working group. [STANDARDS-TRACK]}, keywords="DNS-S-MIB, Domain, Name, System, Management, Information, Base", doi="10.17487/RFC1611", } @misc{rfc1612, author="R. Austein and J. Saperia", title="{DNS Resolver MIB Extensions}", howpublished="RFC 1612 (Historic)", series="Internet Request for Comments", type="RFC", number="1612", pages="1--32", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1612.txt", key="RFC 1612", abstract={This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of extensions which instrument DNS resolver functions. This memo was produced by the DNS working group. [STANDARDS-TRACK]}, keywords="DNS-R-MIB, Domain, Name, System, Management, Information, Base", doi="10.17487/RFC1612", } @misc{rfc1613, author="J. Forster and G. Satz and G. Glick and R. Day", title="{cisco Systems X.25 over TCP (XOT)}", howpublished="RFC 1613 (Informational)", series="Internet Request for Comments", type="RFC", number="1613", pages="1--13", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1613.txt", key="RFC 1613", abstract={This memo documents a method of sending X.25 packets over IP internets by encapsulating the X.25 Packet Level in TCP packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Transmission, Control, Protocol", doi="10.17487/RFC1613", } @misc{rfc1614, author="C. Adie", title="{Network Access to Multimedia Information}", howpublished="RFC 1614 (Informational)", series="Internet Request for Comments", type="RFC", number="1614", pages="1--79", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1614.txt", key="RFC 1614", abstract={This report summarises the requirements of research and academic network users for network access to multimedia information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="RARE, Technical, Report", doi="10.17487/RFC1614", } @misc{rfc1615, author="J. Houttuin and J. Craigie", title="{Migrating from X.400(84) to X.400(88)}", howpublished="RFC 1615 (Informational)", series="Internet Request for Comments", type="RFC", number="1615", pages="1--17", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1615.txt", key="RFC 1615", abstract={This document compares X.400(88) to X.400(84) and describes what problems can be anticipated in the migration, especially considering the migration from the existing X.400(84) infrastructure created by the COSINE MHS project to an X.400(88) infrastructure. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="RARE, Technical, Report, email", doi="10.17487/RFC1615", } @misc{rfc1616, author="RARE WG-MSG Task Force 88 and E. Huizer and J. Romaguera", title="{X.400(1988) for the Academic and Research Community in Europe}", howpublished="RFC 1616 (Informational)", series="Internet Request for Comments", type="RFC", number="1616", pages="1--44", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1616.txt", key="RFC 1616", abstract={The report documents the results of a task force on X.400(1988) deployment of the RARE Mails and Messaging Work Group during the period from November 1992 until October 1993. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="RARE, Technical, Report, email", doi="10.17487/RFC1616", } @misc{rfc1617, author="P. Barker and S. Kille and T. Lenggenhager", title="{Naming and Structuring Guidelines for X.500 Directory Pilots}", howpublished="RFC 1617 (Informational)", series="Internet Request for Comments", type="RFC", number="1617", pages="1--28", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1617.txt", key="RFC 1617", abstract={This document defines a number of naming and structuring guidelines focused on White Pages usage. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="RARE, Technical, Report, White Pages", doi="10.17487/RFC1617", } @misc{rfc1618, author="W. Simpson", title="{PPP over ISDN}", howpublished="RFC 1618 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1618", pages="1--7", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1618.txt", key="RFC 1618", abstract={This document describes the use of PPP over Integrated Services Digital Network (ISDN) switched circuits. [STANDARDS-TRACK]}, keywords="PPP-ISDN, Point, Integrated Services Digital Network", doi="10.17487/RFC1618", } @misc{rfc1619, author="W. Simpson", title="{PPP over SONET/SDH}", howpublished="RFC 1619 (Proposed Standard)", series="Internet Request for Comments", type="RFC", number="1619", pages="1--5", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", note="Obsoleted by RFC 2615", url="https://www.rfc-editor.org/rfc/rfc1619.txt", key="RFC 1619", abstract={This document describes the use of PPP over Synchronous Optical Network (SONET) and Synchronous Digital Heirarchy (SDH) circuits. [STANDARDS-TRACK]}, keywords="PPP-SONET, Point, Synchronous Optical Network Digital Heirarchy", doi="10.17487/RFC1619", } @misc{rfc1620, author="B. Braden and J. Postel and Y. Rekhter", title="{Internet Architecture Extensions for Shared Media}", howpublished="RFC 1620 (Informational)", series="Internet Request for Comments", type="RFC", number="1620", pages="1--19", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1620.txt", key="RFC 1620", abstract={This memo discusses alternative approaches to extending the Internet architecture to eliminate some or all unnecessary hops. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.}, keywords="Public, data, networks, ARP, address, resolution, protocol", doi="10.17487/RFC1620", } @misc{rfc1621, author="P. Francis", title="{Pip Near-term Architecture}", howpublished="RFC 1621 (Informational)", series="Internet Request for Comments", type="RFC", number="1621", pages="1--51", year=1994, month=may, issn="2070-1721", publisher="RFC Editor", institution="RFC Editor", organization="RFC Editor", address="Fremont, CA, USA", url="https://www.rfc-editor.org/rfc/rfc1621.txt", key="RFC 1621", abstract={The