<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Scribd Feed for NickyNET</title>
    <link>http://www.scribd.com/people/view/269166-nickynet</link>
    <description>This a feed for documents on Scribd written by NickyNET</description>
    <ttl>30</ttl>
    <pubDate>Fri, 06 Jun 2008 20:15:30 GMT</pubDate>
    <lastBuildDate>Fri, 06 Jun 2008 20:15:30 GMT</lastBuildDate>
    <item>
      <title>infII</title>
      <link>http://www.scribd.com/doc/3263283/infII</link>
      <description>&#1048;&#1085;&#1092;&#1086;&#1088;&#1084;&#1072;&#1090;&#1080;&#1082;&#1072; II &#1052;&#1086;&#1076;&#1091;&#1083; &#8222;&#1040;&#1083;&#1075;&#1086;&#1088;&#1080;&#1090;&#1084;&#1080; &#1080; &#1087;&#1086;&#1076;&#1093;&#1086;&#1076;&#1080; &#1079;&#1072; &#1087;&#1086;&#1089;&#1090;&#1088;&#1086;&#1103;&#1074;&#1072;&#1085;&#1077; &#1085;&#1072; &#1072;&#1083;&#1075;&#1086;&#1088;&#1080;&#1090;&#1084;&#1080;&#8221; 1. &#1042;&#1098;&#1074;&#1077;&#1076;&#1077;&#1085;&#1080;&#1077;. &#1055;&#1088;&#1077;&#1076;&#1084;&#1077;&#1090; &#1085;&#1072; &#1080;&#1085;&#1092;&#1086;&#1088;&#1084;&#1072;&#1090;&#1080;&#1082;&#1072;&#1090;&#1072;. &#1042;&#1088;&#1098;&#1079;&#1082;&#1072; &#1089; &#1084;&#1072;&#1090;&#1077;&#1084;&#1072;&#1090;&#1080;&#1082;&#1072;&#1090;&#1072; &#8211; &#1080;&#1085;&#1074;&#1072;&#1088;&#1080;&#1072;&#1085;&#1090;&#1085;&#1080; &#1084;&#1077;&#1090;&#1086;&#1076;&#1080; &#1079;&#1072; &#1087;&#1088;&#1077;&#1076;&#1089;&#1090;&#1072;&#1074;&#1103;&#1085;&#1077; &#1085;&#1072; &#1076;&#1072;&#1085;&#1085;&#1080; &#1080; &#1086;&#1073;&#1088;&#1072;&#1073;&#1086;&#1090;&#1082;&#1072;&#1090;&#1072; &#1080;&#1084;. &#1048;&#1079;&#1080;&#1089;&#1082;&#1074;&#1072;&#1085;&#1080;&#1103; &#1082;&#1098;&#1084; &#1072;&#1083;&#1075;&#1086;&#1088;&#1080;&#1090;&#1098;&#1084; &#8211; &#1087;&#1088;&#1072;&#1074;&#1080;&#1083;&#1085;&#1086;&#1089;&#1090;, &#1083;&#1077;&#1082;&#1086;&#1090;&#1072; &#1079;&#1072; &#1095;&#1077;&#1090;&#1077;&#1085;&#1077; &#1080; &#1084;&#1086;&#1076;&#1080;&#1092;&#1080;&#1082;&#1072;&#1094;&#1080;&#1103;, &#1077;&#1092;&#1077;&#1082;&#1090;&#1080;&#1074;&#1085;&#1086;&#1089;&#1090;. &#1053;&#1080;&#1079;&#1093;&#1086;&#1076;&#1103;&#1097;&#1086; &#1089;&#1090;&#1088;&#1091;&#1082;&#1090;&#1091;&#1088;&#1085;&#1086; &#1087;&#1088;&#1086;&#1075;&#1088;&#1072;&#1084;&#1080;&#1088;&#1072;&#1085;&#1077;. &#1054;&#1089;&#1085;&#1086;&#1074;&#1085;&#1080; &#1072;&#1083;&#1075;&#1086;&#1088;&#1080;&#1090;&#1084;&#1080;&#1095;&#1085;&#1080; &#1089;&#1090;&#1088;&#1091;&#1082;&#1090;&#1091;&#1088;&#1080;; &#1089;&#1090;&#1088;&#1091;&#1082;&#1090;&#1091;&#1088;&#1085;&#1080; &#1073;&#1083;&#1086;&#1082; &#1089;&#1093;&#1077;&#1084;&#1080; &#8211; &#1077;&#1076;&#1080;&#1085; &#1074;&#1093;&#1086;&#1076; &#1080; &#1077;&#1076;&#1080;&#1085; &#1080;&#1079;&#1093;&#1086;&#1076;. &#1055;&#1086;&#1089;&#1090;&#1098;&#1087;&#1082;&#1086;&#1074;&#1072; &#1076;&#1077;&#1082;&#1086;&#1084;&#1087;&#1086;&#1079;&#1080;&#1094;&#1080;&#1103;. 2. &#1048;&#1079;&#1095;&#1080;&#1089;&#1083;&#1080;&#1090;&#1077;&#1083;&#1085;&#1072; &#1089;&#1083;&#1086;&#1078;&#1085;&#1086;&#1089;&#1090; &#1085;&#1072; &#1072;&#1083;&#1075;&#1086;&#1088;&#1080;&#1090;&#1098;&#1084;. &#1053;&#1077;&#1086;&#1073;&#1093;&#1086;&#1076;&#1080;&#1084;&#1086;&#1089;&#1090; &#1086;&#1090; &#1086;&#1094;&#1077;&#1085;&#1082;&#1072; &#1085;&#1072; &#1089;&#1083;&#1086;&#1078;&#1085;&#1086;&#1089;&#1090;, &#1079;&#1072;&#1076;&#1072;&#1095;&#1072; &#1079;&#1072; &#1090;&#1098;&#1088;&#1075;&#1086;&#1074;&#1089;&#1082;&#1080;&#1103; &#1087;&#1098;&#1090;&#1085;&#1080;&#1082;. &#1054;&#1089;&#1085;&#1086;&#1074;&#1085;&#1080; &#1090;&#1077;&#1093;&#1085;&#1080;&#1082;&#1080; &#1079;&#1072; &#1087;&#1088;&#1077;&#1089;&#1084;&#1103;&#1090;&#1072;&#1085;&#1077; &#1085;&#1072; &#1089;&#1083;&#1086;&#1078;&#1085;&#1086;&#1089;&#1090;. &#1054;&#1087;&#1088;&#1077;&#1076;&#1077;&#1083;&#1103;&#1085;&#1077; &#1089;&#1083;&#1086;&#1078;&#1085;&#1086;&#1089;&#1090;&#1090;&#1072; &#1085;&#1072; &#1073;&#1072;&#1079;&#1086;&#1074;&#1080;&#1090;&#1077;</description>
      <pubDate>Fri, 06 Jun 2008 20:15:30 GMT</pubDate>
      <guid>http://www.scribd.com/doc/3263283/infII</guid>
    </item>
    <item>
      <title>&#1055;&#1088;&#1086;&#1090;&#1086;&#1082;&#1086;&#1083; &#1087;&#1086; &#1060;&#1080;&#1079;&#1080;&#1082;&#1072; - 92/&#1040;</title>
      <link>http://www.scribd.com/doc/2164764/-92</link>
      <description>&#1058;&#1045;&#1061;&#1053;&#1048;&#1063;&#1045;&#1057;&#1050;&#1048; &#1059;&#1053;&#1048;&#1042;&#1045;&#1056;&#1057;&#1048;&#1058;&#1045;&#1058; - &#1057;&#1054;&#1060;&#1048;&#1071;
&#1044; &#1045; &#1055; &#1040;&#1056; &#1058;&#1040; &#1052; &#1045; &#1053; &#1058; &#1055; &#1054; &#1055; &#1056; &#1048; &#1051; &#1054;&#1046; &#1053; &#1040; &#1060; &#1048; &#1047; &#1048; &#1050; &#1040;

&#1055;&#1088;&#1086;&#1090;&#1086;&#1082;&#1086;&#1083; &#8470;.......... &#1057;&#1087;&#1077;&#1094;&#1080;&#1072;&#1083;&#1085;&#1086;&#1089;&#1090;................................... &#1057;&#1090;&#1091;&#1076;&#1077;&#1085;&#1090;:..............................................................................&#1060;&#1072;&#1082; &#8470;.............................................. &#1043;&#1088;&#1091;&#1087;&#1072;.................... &#1047;&#1072;&#1076;&#1072;&#1095;&#1072; &#8470; &#1054;&#1087;&#1088;&#1077;&#1076;&#1077;&#1083;&#1103;&#1085;&#1077; &#1096;&#1080;&#1088;&#1080;&#1085;&#1072;&#1090;&#1072; &#1085;&#1072; &#1079;&#1072;&#1073;&#1088;&#1072;&#1085;&#1077;&#1085;&#1072;&#1090;&#1072; &#1079;&#1086;&#1085;&#1072; &#1085;&#1072; &#1087;&#1086;&#1083;&#1091;&#1087;&#1088;&#1086;&#1074;&#1086;&#1076;&#1085;&#1080;&#1082; &#1087;&#1086; &#1090;&#1077;&#1084;&#1087;&#1077;&#1088;&#1072;&#1090;&#1091;&#1088;&#1085;&#1080;&#1103; &#1093;&#1086;&#1076; &#1085;&#1072; &#1077;&#1083;&#1077;&#1082;&#1090;&#1088;&#1080;&#1095;&#1085;&#1072;&#1090;&#1072; </description>
      <pubDate>Sun, 24 Feb 2008 18:36:45 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2164764/-92</guid>
    </item>
    <item>
      <title>rfc1560</title>
      <link>http://www.scribd.com/doc/2042306/rfc1560</link>
      <description>Network Working Group Request for Comments: 1560 Category: Informational

B. Leiner USRA Y. Rekhter IBM December 1993

The MultiProtocol Internet Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract This document was prepared by the authors on behalf of the Internet Architecture Board (IAB). It is offered by the IAB to stimulate discussion. There has recently been considerable discussion on two topics: MultiProtocol approaches in the Internet and the selection</description>
      <pubDate>Mon, 04 Feb 2008 23:03:25 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042306/rfc1560</guid>
    </item>
    <item>
      <title>rfc1559</title>
      <link>http://www.scribd.com/doc/2042305/rfc1559</link>
      <description>Network Working Group Request for Comments: 1559 Obsoletes: 1289 Category: Standards Track

J. Saperia Digital Equipment Corporation December 1993

DECnet Phase IV MIB Extensions Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Table of Contents 1. Introduction ...............................</description>
      <pubDate>Mon, 04 Feb 2008 23:03:24 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042305/rfc1559</guid>
    </item>
    <item>
      <title>rfc1557</title>
      <link>http://www.scribd.com/doc/2042303/rfc1557</link>
      <description>





Network Working Group                                            U. Choi
Request for Comments: 1557                                       K. Chon
Category: Informational                                            KAIST
                                                                 H. Park
                                                     Solvit Chosun Media
                                                           December 1993


            Korean Character Encoding for Internet Messages

Status of this Memo

   This memo provides information for the Internet com</description>
      <pubDate>Mon, 04 Feb 2008 23:03:21 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042303/rfc1557</guid>
    </item>
    <item>
      <title>rfc1558</title>
      <link>http://www.scribd.com/doc/2042304/rfc1558</link>
      <description>Network Working Group Request for Comments: 1558 Category: Informational

T. Howes University of Michigan December 1993

A String Representation of LDAP Search Filters Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract The Lightweight Directory Access Protocol (LDAP) [1] 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-r</description>
      <pubDate>Mon, 04 Feb 2008 23:03:21 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042304/rfc1558</guid>
    </item>
    <item>
      <title>rfc1555</title>
      <link>http://www.scribd.com/doc/2042300/rfc1555</link>
      <description>Network Working Group Request for Comments: 1555 Category: Informational

H. Nussbacher Israeli Inter-University Computer Center Y. Bourvine Hebrew University December 1993

Hebrew Character Encoding for Internet Messages Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. 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. Description All Hebrew text w</description>
      <pubDate>Mon, 04 Feb 2008 23:03:20 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042300/rfc1555</guid>
    </item>
    <item>
      <title>rfc1556</title>
      <link>http://www.scribd.com/doc/2042302/rfc1556</link>
      <description>Network Working Group Request for Comments: 1556 Category: Informational

H. Nussbacher Israeli Inter-University Computer Center December 1993

Handling of Bi-directional Texts in MIME Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract This document describes the format and syntax of the "direction" keyword to be used with bi-directional texts in MIME. Description The MIME standards (RFC 1521 and 1522) defined methods for transporting non-ASCII data via a st</description>
      <pubDate>Mon, 04 Feb 2008 23:03:20 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042302/rfc1556</guid>
    </item>
    <item>
      <title>rfc1554</title>
      <link>http://www.scribd.com/doc/2042298/rfc1554</link>
      <description>Network Working Group Request for Comments: 1554 Category: Informational

M. Ohta Tokyo Institute of Technology K. Handa ETL December 1993

ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Introduction 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 multilingua</description>
      <pubDate>Mon, 04 Feb 2008 23:03:18 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042298/rfc1554</guid>
    </item>
    <item>
      <title>rfc1553</title>
      <link>http://www.scribd.com/doc/2042296/rfc1553</link>
      <description>Network Working Group Request for Comments: 1553 Category: Standards Track

S. Mathur M. Lewis Telebit Corporation December 1993

Compressing IPX Headers Over WAN Media (CIPX) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This document describes a method for compressing the header</description>
      <pubDate>Mon, 04 Feb 2008 23:03:17 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042296/rfc1553</guid>
    </item>
    <item>
      <title>rfc1552</title>
      <link>http://www.scribd.com/doc/2042292/rfc1552</link>
      <description>Network Working Group Request for Comments: 1552 Category: Standards Track

W. Simpson Daydreamer December 1993

The PPP Internetwork Packet Exchange Control Protocol (IPXCP) Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract The Point-to-Point Protocol (PPP) [1] provides a method for </description>
      <pubDate>Mon, 04 Feb 2008 23:03:15 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042292/rfc1552</guid>
    </item>
    <item>
      <title>rfc1551</title>
      <link>http://www.scribd.com/doc/2042290/rfc1551</link>
      <description>Network Working Group Request For Comments: 1551 Obsoletes: RFC 1362 Category: Informational Novell IPX Over Various WAN Media (IPXWAN) Status of this Memo

M. Allen Novell, Inc. December 1993

This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. 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 info</description>
      <pubDate>Mon, 04 Feb 2008 23:03:14 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042290/rfc1551</guid>
    </item>
    <item>
      <title>rfc1550</title>
      <link>http://www.scribd.com/doc/2042288/rfc1550</link>
      <description>Network Working Group Request for Comments: 1550 Category: Informational

S. Bradner Harvard University A. Mankin NRL December 1993

IP: Next Generation (IPng) White Paper Solicitation Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Table of Contents 1. Introduction . . . . . . . . . . . . . . . 2. Document Review Process . . . . . . . . . 3. Document Format Requirement . . . . . . . 4. Outline for IPng Requirements and Concerns 5. Engineering considerations . . .</description>
      <pubDate>Mon, 04 Feb 2008 23:03:13 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042288/rfc1550</guid>
    </item>
    <item>
      <title>rfc1549</title>
      <link>http://www.scribd.com/doc/2042286/rfc1549</link>
      <description>Network Working Group Request for Comments: 1549 Category: Standards Track PPP in HDLC Framing Status of this Memo

W. Simpson, Editor Daydreamer December 1993

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protoc</description>
      <pubDate>Mon, 04 Feb 2008 23:03:12 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042286/rfc1549</guid>
    </item>
    <item>
      <title>rfc1548</title>
      <link>http://www.scribd.com/doc/2042285/rfc1548</link>
      <description>Network Working Group Request for Comments: 1548 Obsoletes: RFC 1331 Category: Standards Track The Point-to-Point Protocol (PPP) Status of this Memo

W. Simpson Daydreamer December 1993

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract The Point-to-Point Protocol (PPP) provides a standard method for tra</description>
      <pubDate>Mon, 04 Feb 2008 23:03:11 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042285/rfc1548</guid>
    </item>
    <item>
      <title>rfc1547</title>
      <link>http://www.scribd.com/doc/2042284/rfc1547</link>
      <description>Network Working Group Request for Comments: 1547 Category: Informational

D. Perkins Carnegie Mellon University December 1993

Requirements for an Internet Standard Point-to-Point Protocol Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract This document discusses the evaluation criteria for an Internet Standard Data Link Layer protocol to be used with point-to-point links. Although many industry standard protocols and ad hoc protocols already exist for the d</description>
      <pubDate>Mon, 04 Feb 2008 23:03:09 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042284/rfc1547</guid>
    </item>
    <item>
      <title>rfc1545</title>
      <link>http://www.scribd.com/doc/2042282/rfc1545</link>
      <description>Network Working Group Request for Comments: 1545 Category: Experimental FTP Operation Over Big Address Records (FOOBAR) Status of this Memo

D. Piscitello Bellcore November 1993

This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. Abstract This paper describes a convention for specifying longer addresses in the PORT command. Introduction This RFC specifies a method for assigning long addresses in the HOST-PORT specific</description>
      <pubDate>Mon, 04 Feb 2008 23:03:07 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042282/rfc1545</guid>
    </item>
    <item>
      <title>rfc1546</title>
      <link>http://www.scribd.com/doc/2042283/rfc1546</link>
      <description>Network Working Group Request for Comments: 1546 Category: Informational

C. Partridge T. Mendez W. Milliken BBN November 1993

Host Anycasting Service Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. 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. Insofar as is possible, this memo tries to be agnostic about how the service is actually p</description>
      <pubDate>Mon, 04 Feb 2008 23:03:07 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042283/rfc1546</guid>
    </item>
    <item>
      <title>rfc1543</title>
      <link>http://www.scribd.com/doc/2042279/rfc1543</link>
      <description>Network Working Group Request for Comments: 1543 Obsoletes: RFCs 1111, 825 Category: Informational Instructions to RFC Authors Status of this Memo

J. Postel ISI October 1993

This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Table of Contents 1. 2. 3. 3a. 3b. 4. 4a. 4b. 4c. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 1. Introduction . . . . . . . . . . Editorial Policy . . . . . . . . Format Rules . . . . . . . . . . ASCII Format Rules . . . . . . PostScript Format Rules . . . </description>
      <pubDate>Mon, 04 Feb 2008 23:03:06 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042279/rfc1543</guid>
    </item>
    <item>
      <title>rfc1544</title>
      <link>http://www.scribd.com/doc/2042281/rfc1544</link>
      <description>Network Working Group Request for Comments: 1544 Category: Standards Track

M. Rose Dover Beach Consulting, Inc. November 1993

The Content-MD5 Header Field Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This memo specifies an optional header field, Content-MD5, for use with MIME-c</description>
      <pubDate>Mon, 04 Feb 2008 23:03:06 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042281/rfc1544</guid>
    </item>
    <item>
      <title>rfc1542</title>
      <link>http://www.scribd.com/doc/2042278/rfc1542</link>
      <description>Network Working Group Request for Comments: 1542 Updates: 951 Obsoletes: 1532 Category: Standards Track

W. Wimer Carnegie Mellon University October 1993

Clarifications and Extensions for the Bootstrap Protocol Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract Some aspects of the BOOTP protocol w</description>
      <pubDate>Mon, 04 Feb 2008 23:03:05 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042278/rfc1542</guid>
    </item>
    <item>
      <title>rfc1541</title>
      <link>http://www.scribd.com/doc/2042276/rfc1541</link>
      <description>Network Working Group Request for Comments: 1541 Obsoletes: 1531 Category: Standards Track Dynamic Host Configuration Protocol Status of this memo

R. Droms Bucknell University October 1993

This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract The Dynamic Host Configuration Protocol (DHCP) provides a framework for passi</description>
      <pubDate>Mon, 04 Feb 2008 23:03:03 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042276/rfc1541</guid>
    </item>
    <item>
      <title>rfc1540</title>
      <link>http://www.scribd.com/doc/2042275/rfc1540</link>
      <description>Network Working Group Request for Comments: 1540 Obsoletes: RFCs 1500, 1410, 1360, 1280, 1250, 1100, 1083, 1130, 1140, 1200 STD: 1 Category: Standards Track

Internet Architecture Board J. Postel, Editor October 1993

INTERNET OFFICIAL PROTOCOL STANDARDS Status of this Memo This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). Distribution of this memo is unlimited. Table of Contents Introduction . . . . . . . . . . . . . . . . . . . . . . 1. The Standardization Process . . . . . . . . . . . . 2. The Request f</description>
      <pubDate>Mon, 04 Feb 2008 23:03:01 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042275/rfc1540</guid>
    </item>
    <item>
      <title>rfc1539</title>
      <link>http://www.scribd.com/doc/2042272/rfc1539</link>
      <description>Network Working Group Request for Comments: 1539 Obsoletes: 1391 FYI: 17 Category: Informational

G. Malkin Xylogics, Inc. October 1993

The Tao of IETF A Guide for New Attendees of the Internet Engineering Task Force Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Abstract Over the last two years, the attendance at Internet Engineering Task Force (IETF) Plenary meetings has grown phenomenally. Approximately 38% of the attendees are new to the IETF at each meeting. About 33% of thos</description>
      <pubDate>Mon, 04 Feb 2008 23:02:56 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042272/rfc1539</guid>
    </item>
    <item>
      <title>rfc1538</title>
      <link>http://www.scribd.com/doc/2042271/rfc1538</link>
      <description>Network Working Group Request for Comments: 1538 Category: Informational

W. Behl McDATA Corporation B. Sterling McDATA Corporation W. Teskey I/O Concepts October 1993

Advanced SNA/IP : A Simple SNA Transport Protocol Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Abstract This RFC provides information for the Internet community about a method for establishing and maintaining SNA sessions over an IP internet. While the issues discussed may not be directly relevant to the research </description>
      <pubDate>Mon, 04 Feb 2008 23:02:55 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042271/rfc1538</guid>
    </item>
    <item>
      <title>rfc1537</title>
      <link>http://www.scribd.com/doc/2042270/rfc1537</link>
      <description>Network Working Group Request for Comments: 1537 Category: Informational Common DNS Data File Configuration Errors Status of this Memo

P. Beertema CWI October 1993

This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 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. Introduction Due to the lack of extensive documentation and automated tools, DNS zone files have mostly</description>
      <pubDate>Mon, 04 Feb 2008 23:02:54 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042270/rfc1537</guid>
    </item>
    <item>
      <title>rfc1536</title>
      <link>http://www.scribd.com/doc/2042268/rfc1536</link>
      <description>Network Working Group Request for Comments: 1536 Category: Informational

A. Kumar J. Postel C. Neuman ISI P. Danzig S. Miller USC October 1993

Common DNS Implementation Errors and Suggested Fixes Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Abstract This memo describes common errors seen in DNS implementations and suggests some fixes. Where applicable, violations of recommendations from STD 13, RFC 1034 and STD 13, RFC 1035 are mentioned. The memo also describes, where relevant</description>
      <pubDate>Mon, 04 Feb 2008 23:02:53 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042268/rfc1536</guid>
    </item>
    <item>
      <title>rfc1535</title>
      <link>http://www.scribd.com/doc/2042266/rfc1535</link>
      <description>





Network Working Group                                          E. Gavron
Request for Comments: 1535                            ACES Research Inc.
Category: Informational                                     October 1993


              A Security Problem and Proposed Correction
                   With Widely Deployed DNS Software

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard.  Distribution of this memo is
   unlimited.

Abstract

   This document discusses a flaw in some of the current</description>
      <pubDate>Mon, 04 Feb 2008 23:02:52 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042266/rfc1535</guid>
    </item>
    <item>
      <title>rfc1533</title>
      <link>http://www.scribd.com/doc/2042264/rfc1533</link>
      <description>Network Working Group Request for Comments: 1533 Obsoletes: 1497, 1395, 1084, 1048 Category: Standards Track

S. Alexander Lachman Technology, Inc. R. Droms Bucknell University October 1993

DHCP Options and BOOTP Vendor Extensions Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract The Dynamic Host</description>
      <pubDate>Mon, 04 Feb 2008 23:02:51 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042264/rfc1533</guid>
    </item>
    <item>
      <title>rfc1534</title>
      <link>http://www.scribd.com/doc/2042265/rfc1534</link>
      <description>Network Working Group Request for Comments: 1534 Category: Standards Track

R. Droms Bucknell University October 1993

Interoperation Between DHCP and BOOTP Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract DHCP provides a superset of the functions provided by BOOTP. This document describes the in</description>
      <pubDate>Mon, 04 Feb 2008 23:02:51 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042265/rfc1534</guid>
    </item>
    <item>
      <title>rfc1532</title>
      <link>http://www.scribd.com/doc/2042262/rfc1532</link>
      <description>Network Working Group Request for Comments: 1532 Updates: 951 Category: Standards Track

W. Wimer Carnegie Mellon University October 1993

Clarifications and Extensions for the Bootstrap Protocol Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract Some aspects of the BOOTP protocol were rather loose</description>
      <pubDate>Mon, 04 Feb 2008 23:02:50 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042262/rfc1532</guid>
    </item>
    <item>
      <title>rfc1531</title>
      <link>http://www.scribd.com/doc/2042261/rfc1531</link>
      <description>Network Working Group Request for Comments: 1531 Category: Standards Track Dynamic Host Configuration Protocol Status of this memo

R. Droms Bucknell University October 1993

This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration</description>
      <pubDate>Mon, 04 Feb 2008 23:02:48 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042261/rfc1531</guid>
    </item>
    <item>
      <title>rfc1530</title>
      <link>http://www.scribd.com/doc/2042259/rfc1530</link>
      <description>Network Working Group Request for Comments: 1530 Category: Informational

C. Malamud Internet Multicasting Service M. Rose Dover Beach Consulting, Inc. October 1993

Principles of Operation for the TPC.INT Subdomain: General Principles and Policy Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 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 administer</description>
      <pubDate>Mon, 04 Feb 2008 23:02:47 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042259/rfc1530</guid>
    </item>
    <item>
      <title>rfc1529</title>
      <link>http://www.scribd.com/doc/2042258/rfc1529</link>
      <description>Network Working Group Request for Comments: 1529 Obsoletes: 1486 Category: Informational

C. Malamud Internet Multicasting Service M. Rose Dover Beach Consulting, Inc. October 1993

Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Introduction This document defines the administrative policies for the operation of remote printer facilities within the context of the tpc.int subdomain. The docu</description>
      <pubDate>Mon, 04 Feb 2008 23:02:46 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042258/rfc1529</guid>
    </item>
    <item>
      <title>rfc1528</title>
      <link>http://www.scribd.com/doc/2042257/rfc1528</link>
      <description>Network Working Group Request for Comments: 1528 Obsoletes: 1486 Category: Experimental

C. Malamud Internet Multicasting Service M. Rose Dover Beach Consulting, Inc. October 1993

Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protoc</description>
      <pubDate>Mon, 04 Feb 2008 23:02:45 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042257/rfc1528</guid>
    </item>
    <item>
      <title>rfc1527</title>
      <link>http://www.scribd.com/doc/2042256/rfc1527</link>
      <description>Network Working Group Request for Comments: 1527 Category: Informational

G. Cook Cook Report September 1993

What Should We Plan Given the Dilemma of the Network? Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Abstract Early last year, as the concluding effort of an 18 month appointment at the US Congress Office of Technology Assessment (OTA), I drafted a potential policy framework for Congressional action on the National Research and Education Network (NREN). The Internet communi</description>
      <pubDate>Mon, 04 Feb 2008 23:02:44 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042256/rfc1527</guid>
    </item>
    <item>
      <title>rfc1525</title>
      <link>http://www.scribd.com/doc/2042254/rfc1525</link>
      <description>Network Working Group Request for Comments: 1525 Obsoletes: 1286 Category: Standards Track

E. Decker cisco Systems, Inc. K. McCloghrie Hughes LAN Systems, Inc. P. Langille DEC A. Rijsinghani DEC September 1993

Definitions of Managed Objects for Source Routing Bridges Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo i</description>
      <pubDate>Mon, 04 Feb 2008 23:02:43 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042254/rfc1525</guid>
    </item>
    <item>
      <title>rfc1526</title>
      <link>http://www.scribd.com/doc/2042255/rfc1526</link>
      <description>Network Working Group Request for Comments: 1526 Category: Informational

D. Piscitello Bellcore September 1993

Assignment of System Identifiers for TUBA/CLNP Hosts Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 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. The mechanism is extensible and can provid</description>
      <pubDate>Mon, 04 Feb 2008 23:02:43 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042255/rfc1526</guid>
    </item>
    <item>
      <title>rfc1524</title>
      <link>http://www.scribd.com/doc/2042253/rfc1524</link>
      <description>Network Working Group Request for Comments: 1524 Category: Informational A User Agent Configuration Mechanism For Multimedia Mail Format Information Status of This Memo

N. Borenstein Bellcore September 1993

This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 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. The mechanism is explicitly designed to work with mail systems based</description>
      <pubDate>Mon, 04 Feb 2008 23:02:41 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042253/rfc1524</guid>
    </item>
    <item>
      <title>rfc1523</title>
      <link>http://www.scribd.com/doc/2042252/rfc1523</link>
      <description>Network Working Group Request for Comments: 1523 Category: Informational The text/enriched MIME Content-type Status of this Memo

N. Borenstein Bellcore September 1993

This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 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. T</description>
      <pubDate>Mon, 04 Feb 2008 23:02:40 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042252/rfc1523</guid>
    </item>
    <item>
      <title>rfc1522</title>
      <link>http://www.scribd.com/doc/2042250/rfc1522</link>
      <description>Network Working Group Request for Comments: 1522 Obsoletes: 1342 Category: Standards Track

K. Moore University of Tennessee September 1993

MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This me</description>
      <pubDate>Mon, 04 Feb 2008 23:02:37 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042250/rfc1522</guid>
    </item>
    <item>
      <title>rfc1521</title>
      <link>http://www.scribd.com/doc/2042249/rfc1521</link>
      <description>Network Working Group Request for Comments: 1521 Obsoletes: 1341 Category: Standards Track

N. Borenstein Bellcore N. Freed Innosoft September 1993

MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution o</description>
      <pubDate>Mon, 04 Feb 2008 23:02:36 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042249/rfc1521</guid>
    </item>
    <item>
      <title>rfc1521</title>
      <link>http://www.scribd.com/doc/2042247/rfc1521</link>
      <description>Network Working Group Request for Comments: 1521 Obsoletes: 1341 Category: Standards Track

N. Borenstein Bellcore N. Freed September 1993

MIME (Multipurpose Internet Mail Extensions) Part One:
Mechanisms for Specifying and Describing the Format of Internet Message Bodies
Status of this Memo
This RFC speci&#64257;es an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Of&#64257;cial Protocol Standards" for the standardization state and status of this protocol. Distribution of this </description>
      <pubDate>Mon, 04 Feb 2008 23:02:32 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042247/rfc1521</guid>
    </item>
    <item>
      <title>rfc1521</title>
      <link>http://www.scribd.com/doc/2042245/rfc1521</link>
      <description>Network Working Group Request for Comments: 1521 Obsoletes: 1341 Category: Standards Track

N. Borenstein Bellcore N. Freed September 1993

MIME (Multipurpose Internet Mail Extensions) Part One:
Mechanisms for Specifying and Describing the Format of Internet Message Bodies
Status of this Memo
This RFC speci&#64257;es an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Of&#64257;cial Protocol Standards" for the standardization state and status of this protocol. Distribution of this </description>
      <pubDate>Mon, 04 Feb 2008 23:02:27 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042245/rfc1521</guid>
    </item>
    <item>
      <title>rfc1519</title>
      <link>http://www.scribd.com/doc/2042242/rfc1519</link>
      <description>Network Working Group Request for Comments: 1519 Obsoletes: 1338 Category: Standards Track

V. Fuller BARRNet T. Li cisco J. Yu MERIT K. Varadhan OARnet September 1993

Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Ab</description>
      <pubDate>Mon, 04 Feb 2008 23:02:23 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042242/rfc1519</guid>
    </item>
    <item>
      <title>rfc1520</title>
      <link>http://www.scribd.com/doc/2042244/rfc1520</link>
      <description>Network Working Group Request for Comments: 1520 Category: Informational

Y. Rekhter T.J. Watson Research Center, IBM Corp. C. Topolcic CNRI September 1993

Exchanging Routing Information Across Provider Boundaries in the CIDR Environment Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 1. Introduction Classless Inter-Domain Routing (CIDR) has been adopted as a solution to the scaling problem in the Internet. The overall CIDR architecture is described in [1]. The architecture for IP </description>
      <pubDate>Mon, 04 Feb 2008 23:02:23 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042244/rfc1520</guid>
    </item>
    <item>
      <title>rfc1518</title>
      <link>http://www.scribd.com/doc/2042239/rfc1518</link>
      <description>Network Working Group Request for Comments: 1518 Category: Standards Track

Y. Rekhter T.J. Watson Research Center, IBM Corp. T. Li cisco Systems Editors September 1993

An Architecture for IP Address Allocation with CIDR Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. 1. Introduction This paper provides</description>
      <pubDate>Mon, 04 Feb 2008 23:02:21 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042239/rfc1518</guid>
    </item>
    <item>
      <title>rfc1517</title>
      <link>http://www.scribd.com/doc/2042235/rfc1517</link>
      <description>Network Working Group Request for Comments: 1517 Category: Standards Track

Internet Engineering Steering Group R. Hinden, Editor September 1993

Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR) Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. 1. Introduction As the </description>
      <pubDate>Mon, 04 Feb 2008 23:02:19 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042235/rfc1517</guid>
    </item>
    <item>
      <title>rfc1516</title>
      <link>http://www.scribd.com/doc/2042234/rfc1516</link>
      <description>Network Working Group Request for Comments: 1516 Obsoletes: 1368

D. McMaster SynOptics Communications, Inc. K. McCloghrie Hughes LAN Systems, Inc. September 1993

Definitions of Managed Objects for IEEE 802.3 Repeater Devices Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This memo defines a p</description>
      <pubDate>Mon, 04 Feb 2008 23:02:18 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042234/rfc1516</guid>
    </item>
    <item>
      <title>rfc1515</title>
      <link>http://www.scribd.com/doc/2042233/rfc1515</link>
      <description>Network Working Group Request for Comments: 1515

D. McMaster SynOptics Communications, Inc. K. McCloghrie Hughes LAN Systems, Inc. S. Roberts Farallon Computing, Inc. September 1993

Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimit</description>
      <pubDate>Mon, 04 Feb 2008 23:02:16 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042233/rfc1515</guid>
    </item>
    <item>
      <title>rfc1514</title>
      <link>http://www.scribd.com/doc/2042232/rfc1514</link>
      <description>Network Working Group Request for Comments: 1514

P. Grillo Network Innovations Intel Corporation S. Waldbusser Carnegie Mellon University September 1993 Host Resources MIB

Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This memo defines a MIB for use with managing host systems. The term "host</description>
      <pubDate>Mon, 04 Feb 2008 23:02:14 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042232/rfc1514</guid>
    </item>
    <item>
      <title>rfc1513</title>
      <link>http://www.scribd.com/doc/2042231/rfc1513</link>
      <description>Network Working Group Request for Comments: 1513 Updates: 1271

S. Waldbusser Carnegie Mellon University September 1993

Token Ring Extensions to the Remote Network Monitoring MIB Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This memo defines extensions to the Remote Network Monitoring MIB fo</description>
      <pubDate>Mon, 04 Feb 2008 23:02:11 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042231/rfc1513</guid>
    </item>
    <item>
      <title>rfc1512</title>
      <link>http://www.scribd.com/doc/2042228/rfc1512</link>
      <description>Network Working Group Request for Comments: 1512 Updates: 1285

J. Case The University of Tennesse and SNMP Research, Incorporated A. Rijsinghani Digital Equipment Corporation September 1993

FDDI Management Information Base Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This memo defines a por</description>
      <pubDate>Mon, 04 Feb 2008 23:02:09 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042228/rfc1512</guid>
    </item>
    <item>
      <title>rfc1510</title>
      <link>http://www.scribd.com/doc/2042224/rfc1510</link>
      <description>Network Working Group Request for Comments: 1510

J. Kohl Digital Equipment Corporation C. Neuman ISI September 1993

The Kerberos Network Authentication Service (V5) Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This document gives an overview and specification of Version 5 of the protocol fo</description>
      <pubDate>Mon, 04 Feb 2008 23:02:06 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042224/rfc1510</guid>
    </item>
    <item>
      <title>rfc1511</title>
      <link>http://www.scribd.com/doc/2042226/rfc1511</link>
      <description>Network Working Group Request for Comments: 1511

J. Linn Geer Zolot Associates September 1993

Common Authentication Technology Overview Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Overview The IETF's Common Authentication Technology (CAT) working group has pursued, and continues to pursue, several interrelated activities, involving definition of service interfaces as well as protocols. As a goal, it has sought to separate security implementation tasks from integration of secur</description>
      <pubDate>Mon, 04 Feb 2008 23:02:06 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042226/rfc1511</guid>
    </item>
    <item>
      <title>rfc1509</title>
      <link>http://www.scribd.com/doc/2042219/rfc1509</link>
      <description>Network Working Group Request for Comments: 1509

J. Wray Digital Equipment Corporation September 1993

Generic Security Service API : C-bindings Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This document specifies C language bindings for the Generic Security Service Application Program Inter</description>
      <pubDate>Mon, 04 Feb 2008 23:01:59 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042219/rfc1509</guid>
    </item>
    <item>
      <title>rfc1508</title>
      <link>http://www.scribd.com/doc/2042216/rfc1508</link>
      <description>Network Working Group Request for Comments: 1508

J. Linn Geer Zolot Associates September 1993

Generic Security Service Application Program Interface Status of this Memo This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This Generic Security Service Application Program Interface (GSS-API) definition provides securit</description>
      <pubDate>Mon, 04 Feb 2008 23:01:52 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042216/rfc1508</guid>
    </item>
    <item>
      <title>rfc1507</title>
      <link>http://www.scribd.com/doc/2042214/rfc1507</link>
      <description>Network Working Group Request for Comments: 1507

C. Kaufman Digital Equipment Corporation September 1993

DASS Distributed Authentication Security Service Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Table of Contents 1. Introduction ......................................</description>
      <pubDate>Mon, 04 Feb 2008 23:01:49 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042214/rfc1507</guid>
    </item>
    <item>
      <title>rfc1506</title>
      <link>http://www.scribd.com/doc/2042210/rfc1506</link>
      <description>Network Working Group Request for Comments: 1506 RARE Technical Report: 6

J. Houttuin RARE Secretariat August 1993

A Tutorial on Gatewaying between X.400 and Internet Mail Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Introduction There are many ways in which X.400 and Internet (STD 11, RFC 822) mail systems can be interconnected. Addresses and service elements can be mapped onto each other in different ways. From the early available gateway implementations, one was not necessar</description>
      <pubDate>Mon, 04 Feb 2008 23:01:43 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042210/rfc1506</guid>
    </item>
    <item>
      <title>rfc1505</title>
      <link>http://www.scribd.com/doc/2042208/rfc1505</link>
      <description>Network Working Group Request for Comments: 1505 Obsoletes: 1154

A. Costanzo AKC Consulting D. Robinson Computervision Corporation R. Ullmann August 1993

Encoding Header Field for Internet Messages Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. 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. Distribution of this memo is unlimited. IESG Note Note that a standards-t</description>
      <pubDate>Mon, 04 Feb 2008 23:01:41 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042208/rfc1505</guid>
    </item>
    <item>
      <title>rfc1504</title>
      <link>http://www.scribd.com/doc/2042206/rfc1504</link>
      <description>Network Working Group Request for Comments: 1504

A. Oppenheimer Apple Computer August 1993

Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing Status of This Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Introduction This memo is being distributed to members of the Internet community to fully document an Apple protocol that may be running over the Internet. While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting </description>
      <pubDate>Mon, 04 Feb 2008 23:01:40 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042206/rfc1504</guid>
    </item>
    <item>
      <title>rfc1503</title>
      <link>http://www.scribd.com/doc/2042200/rfc1503</link>
      <description>Network Working Group Request for Comments: 1503

K. McCloghrie Hughes LAN Systems M. Rose Dover Beach Consulting, Inc. August 1993

Algorithms for Automating Administration in SNMPv2 Managers Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Table of Contents 1. Introduction .......................................... 2. Implementation Model .................................. 3. Configuration Assumptions ............................. 4. Normal Operations ..............................</description>
      <pubDate>Mon, 04 Feb 2008 23:01:34 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042200/rfc1503</guid>
    </item>
    <item>
      <title>rfc1502</title>
      <link>http://www.scribd.com/doc/2042199/rfc1502</link>
      <description>Network Working Group Request for Comments: 1502

H. Alvestrand SINTEF DELAB August 1993

X.400 Use of Extended Character Sets Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. 1. Introduction Since 1988, X.400 has had the capacity for carrying a large number of different character sets in a message by using the bod</description>
      <pubDate>Mon, 04 Feb 2008 23:01:33 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042199/rfc1502</guid>
    </item>
    <item>
      <title>rfc1500</title>
      <link>http://www.scribd.com/doc/2042195/rfc1500</link>
      <description>Network Working Group Request for Comments: 1500 Obsoletes: RFCs 1410, 1360, 1280, 1250, 1100, 1083, 1130, 1140, 1200 STD: 1

Internet Architecture Board J. Postel, Editor August 1993

INTERNET OFFICIAL PROTOCOL STANDARDS Status of this Memo This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). Distribution of this memo is unlimited. Table of Contents Introduction . . . . . . . . . . . . . . . . . . . . . . 1. The Standardization Process . . . . . . . . . . . . 2. The Request for Comments Documents . . . . . .</description>
      <pubDate>Mon, 04 Feb 2008 23:01:32 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042195/rfc1500</guid>
    </item>
    <item>
      <title>rfc1501</title>
      <link>http://www.scribd.com/doc/2042196/rfc1501</link>
      <description>Network Working Group Request for Comments: 1501

E. Brunsen Eastern New Mexico University August 1993 OS/2 User Group

Status of this Memo This memo provides information for the Internet community. This memo does not specify an IAB standard of any kind. Distribution of this memo is unlimited. Introduction This RFC is being distributed to members of the Internet 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 Internet, they may be interesting to a number of researchers and im</description>
      <pubDate>Mon, 04 Feb 2008 23:01:32 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042196/rfc1501</guid>
    </item>
    <item>
      <title>rfc1499</title>
      <link>http://www.scribd.com/doc/2042193/rfc1499</link>
      <description>Network Working Group Request for Comments: 1499 Category: Informational Request for Comments Summary RFC Numbers 1400-1499 Status of This Memo

J. Elliott ISI January 1997

This RFC is a slightly annotated list of the 100 RFCs from RFC 1400 through RFCs 1499. This is a status report on these RFCs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Note Many RFCs, but not all, are Proposed Standards, Draft Standards, or Standards. Since the status of these RFCs may change during the standards </description>
      <pubDate>Mon, 04 Feb 2008 23:01:29 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042193/rfc1499</guid>
    </item>
    <item>
      <title>rfc1498</title>
      <link>http://www.scribd.com/doc/2042191/rfc1498</link>
      <description>Network Working Group Request for Comments: 1498

J. Saltzer M.I.T. Laboratory for Computer Science August 1993

On the Naming and Binding of Network Destinations Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 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 networ</description>
      <pubDate>Mon, 04 Feb 2008 23:01:28 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042191/rfc1498</guid>
    </item>
    <item>
      <title>rfc1496</title>
      <link>http://www.scribd.com/doc/2042189/rfc1496</link>
      <description>Network Working Group Request for Comments: 1496 Updates: 1328

H. Alvestrand SINTEF DELAB J. Romaguera NetConsult AG K. Jordan Control Data Systems, Inc. August 1993

Rules for Downgrading Messages from X.400/88 to X.400/84 When MIME Content-Types are Present in the Messages Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is u</description>
      <pubDate>Mon, 04 Feb 2008 23:01:27 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042189/rfc1496</guid>
    </item>
    <item>
      <title>rfc1497</title>
      <link>http://www.scribd.com/doc/2042190/rfc1497</link>
      <description>Network Working Group Request for Comments: 1497 Obsoletes: 1395, 1084, 1048 Updates: 951 BOOTP Vendor Information Extensions Status of this Memo

J. Reynolds ISI August 1993

This memo is a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP). Distribution of this memo is unlimited. Introduction 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 are defined. This edition introduces Tag 18 for Extension Path. As workstatio</description>
      <pubDate>Mon, 04 Feb 2008 23:01:27 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042190/rfc1497</guid>
    </item>
    <item>
      <title>rfc1495</title>
      <link>http://www.scribd.com/doc/2042187/rfc1495</link>
      <description>Network Working Group Request for Comments: 1495 Updates: 1327

H. Alvestrand SINTEF DELAB S. Kille ISODE Consortium R. Miles Soft*Switch, Inc. M. Rose Dover Beach Consulting, Inc. S. Thompson Soft*Switch, Inc. August 1993

Mapping between X.400 and RFC-822 Message Bodies Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlim</description>
      <pubDate>Mon, 04 Feb 2008 23:01:26 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042187/rfc1495</guid>
    </item>
    <item>
      <title>rfc1494</title>
      <link>http://www.scribd.com/doc/2042186/rfc1494</link>
      <description>Network Working Group Request for Comments: 1494

H. Alvestrand SINTEF DELAB S. Thompson Soft*Switch, Inc. August 1993

Equivalences between 1988 X.400 and RFC-822 Message Bodies Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Table of Contents 1. Introduction ............................................. 2. Equiv</description>
      <pubDate>Mon, 04 Feb 2008 23:01:25 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042186/rfc1494</guid>
    </item>
    <item>
      <title>rfc1493</title>
      <link>http://www.scribd.com/doc/2042184/rfc1493</link>
      <description>Network Working Group Request for Comments: 1493 Obsoletes: 1286

E. Decker cisco Systems, Inc. P. Langille Digital Equipment Corporation A. Rijsinghani Digital Equipment Corporation K. McCloghrie Hughes LAN Systems, Inc. July 1993

Definitions of Managed Objects for Bridges Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is un</description>
      <pubDate>Mon, 04 Feb 2008 23:01:24 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042184/rfc1493</guid>
    </item>
    <item>
      <title>rfc1492</title>
      <link>http://www.scribd.com/doc/2042180/rfc1492</link>
      <description>Network Working Group Request for Comments: 1492

C. Finseth University of Minnesota July 1993

An Access Control Protocol, Sometimes Called TACACS Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Background There used to be a network called ARPANET. This network consisted of end nodes (hosts), routing nodes (IMPs) and links. There were (at least) two types of IMPs: those that connected dedicated lines only and those that could accept dial up lines. The latter were called "TIPs." Peo</description>
      <pubDate>Mon, 04 Feb 2008 23:01:22 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042180/rfc1492</guid>
    </item>
    <item>
      <title>rfc1491</title>
      <link>http://www.scribd.com/doc/2042178/rfc1491</link>
      <description>Network Working Group Request for Comments: 1491 FYI: 21

C. Weider Merit Network, Inc. R. Wright Lawrence Berkeley Laboratory July 1993

A Survey of Advanced Usages of X.500 Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 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 th</description>
      <pubDate>Mon, 04 Feb 2008 23:01:21 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042178/rfc1491</guid>
    </item>
    <item>
      <title>rfc1490</title>
      <link>http://www.scribd.com/doc/2042174/rfc1490</link>
      <description>Network Working Group Request for Comments: 1490 Obsoletes: 1294

T. Bradley Wellfleet Communications, Inc. C. Brown Wellfleet Communications, Inc. A. Malis Ascom Timeplex, Inc. July 1993

Multiprotocol Interconnect over Frame Relay Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract This memo describes an en</description>
      <pubDate>Mon, 04 Feb 2008 23:01:20 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042174/rfc1490</guid>
    </item>
    <item>
      <title>rfc1489</title>
      <link>http://www.scribd.com/doc/2042170/rfc1489</link>
      <description>Network Working Group Request for Comments: 1489

A. Chernov RELCOM Development Team July 1993

Registration of a Cyrillic Character Set Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Introduction 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 </description>
      <pubDate>Mon, 04 Feb 2008 23:01:18 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042170/rfc1489</guid>
    </item>
    <item>
      <title>rfc1487</title>
      <link>http://www.scribd.com/doc/2042167/rfc1487</link>
      <description>Network Working Group Request for Comments: 1487

W. Yeong Performance Systems International T. Howes University of Michigan S. Kille ISODE Consortium July 1993

X.500 Lightweight Directory Access Protocol Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract The protocol described in this document is designed </description>
      <pubDate>Mon, 04 Feb 2008 23:01:17 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042167/rfc1487</guid>
    </item>
    <item>
      <title>rfc1488</title>
      <link>http://www.scribd.com/doc/2042169/rfc1488</link>
      <description>





Network Working Group                                         T. Howes
Request for Comments: 1488                      University of Michigan
                                                              S. Kille
                                                      ISODE Consortium
                                                              W. Yeong
                                     Performance Systems International
                                                            C. Robbins
                                                            NeXor Ltd.
            </description>
      <pubDate>Mon, 04 Feb 2008 23:01:17 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042169/rfc1488</guid>
    </item>
    <item>
      <title>rfc1486</title>
      <link>http://www.scribd.com/doc/2042164/rfc1486</link>
      <description>Network Working Group Request for Comments: 1486

M. Rose Dover Beach Consulting, Inc. C. Malamud Internet Multicasting Service July 1993

An Experiment in Remote Printing Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. 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. Distribution of this memo is unlimited. Table of Contents 1. Introduction ...........................</description>
      <pubDate>Mon, 04 Feb 2008 23:01:15 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042164/rfc1486</guid>
    </item>
    <item>
      <title>rfc1484</title>
      <link>http://www.scribd.com/doc/2042159/rfc1484</link>
      <description>Network Working Group Request for Comments: 1484

S. Hardcastle-Kille ISODE Consortium July 1993

Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2)) Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. 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. Distribution of this memo is unlimited. Abstract The OSI Directory has user friendly naming as a goa</description>
      <pubDate>Mon, 04 Feb 2008 23:01:14 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042159/rfc1484</guid>
    </item>
    <item>
      <title>rfc1485</title>
      <link>http://www.scribd.com/doc/2042161/rfc1485</link>
      <description>Network Working Group Request for Comments: 1485

S. Hardcastle-Kille ISODE Consortium July 1993

A String Representation of Distinguished Names (OSI-DS 23 (v5)) Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract The OSI Directory uses distinguished names as the primary keys to entries in the directory. Dist</description>
      <pubDate>Mon, 04 Feb 2008 23:01:14 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042161/rfc1485</guid>
    </item>
    <item>
      <title>rfc1483</title>
      <link>http://www.scribd.com/doc/2042156/rfc1483</link>
      <description>Network Working Group Reguest for Comments: 1483

Juha Heinanen Telecom Finland July 1993

Multiprotocol Encapsulation over ATM Adaptation Layer 5 Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract This memo describes two encapsulations methods for carrying network interconnect traffic over ATM AAL5. The fir</description>
      <pubDate>Mon, 04 Feb 2008 23:01:12 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042156/rfc1483</guid>
    </item>
    <item>
      <title>rfc1482</title>
      <link>http://www.scribd.com/doc/2042154/rfc1482</link>
      <description>Network Working Group Request for Comments: 1482

Mark Knopper Steven J. Richardson Merit/NSFNET June 1993

Aggregation Support in the NSFNET Policy-Based Routing Database Status of this memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 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. Mechanisms for exchange of route aggregates betw</description>
      <pubDate>Mon, 04 Feb 2008 23:01:11 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042154/rfc1482</guid>
    </item>
    <item>
      <title>rfc1481</title>
      <link>http://www.scribd.com/doc/2042151/rfc1481</link>
      <description>Network Working Group Request for Comments: 1481

C. Huitema, Chair Internet Architecture Board July 1993

IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Recommendation Classless Inter-Domain Routing (CIDR) proposes 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</description>
      <pubDate>Mon, 04 Feb 2008 23:01:10 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042151/rfc1481</guid>
    </item>
    <item>
      <title>rfc1480</title>
      <link>http://www.scribd.com/doc/2042150/rfc1480</link>
      <description>Network Working Group Request for Comments: 1480 Obsoletes: 1386 The US Domain Status of this Memo

A. Cooper J. Postel June 1993

This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Table of Contents 1. Introduction ................................................ 1.1 The Internet Domain Name System......................... 1.2 Top-Level Domains....................................... 1.3 The US Domain .......................................... Naming Structure ............................................ </description>
      <pubDate>Mon, 04 Feb 2008 23:01:09 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042150/rfc1480</guid>
    </item>
    <item>
      <title>rfc1479</title>
      <link>http://www.scribd.com/doc/2042147/rfc1479</link>
      <description>Network Working Group Request for Comments: 1479

M. Steenstrup BBN Systems and Technologies July 1993

Inter-Domain Policy Routing Protocol Specification: Version 1 Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract We present the set of protocols and procedures that constitute Inter-Domain Policy Routing (</description>
      <pubDate>Mon, 04 Feb 2008 23:01:06 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042147/rfc1479</guid>
    </item>
    <item>
      <title>rfc1478</title>
      <link>http://www.scribd.com/doc/2042145/rfc1478</link>
      <description>Network Working Group Request for Comments: 1478

M. Steenstrup BBN Systems and Technologies June 1993

An Architecture for Inter-Domain Policy Routing Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract We present an architecture for inter-domain policy routing (IDPR). The objective of IDPR is to construct a</description>
      <pubDate>Mon, 04 Feb 2008 23:01:03 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042145/rfc1478</guid>
    </item>
    <item>
      <title>rfc1477</title>
      <link>http://www.scribd.com/doc/2042144/rfc1477</link>
      <description>Network Working Group Request for Comments: 1477

M. Steenstrup BBN Systems and Technologies July 1993

IDPR as a Proposed Standard Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 1. Introduction This document contains a discussion of inter-domain policy routing (IDPR), including an overview of functionality and a discussion of experiments. The objective of IDPR is to construct and maintain routes between source and destination administrative domains, that provide user traffic with </description>
      <pubDate>Mon, 04 Feb 2008 23:01:01 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042144/rfc1477</guid>
    </item>
    <item>
      <title>rfc1476</title>
      <link>http://www.scribd.com/doc/2042143/rfc1476</link>
      <description>Network Working Group Request for Comments: 1476

R. Ullmann Process Software Corporation June 1993

RAP: Internet Route Access Protocol Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. 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. Distribution of this memo is unlimited. Abstract This RFC describes an open distance vector routing protocol for use at all levels of th</description>
      <pubDate>Mon, 04 Feb 2008 23:01:00 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042143/rfc1476</guid>
    </item>
    <item>
      <title>rfc1475</title>
      <link>http://www.scribd.com/doc/2042142/rfc1475</link>
      <description>Network Working Group Request for Comments: 1475

R. Ullmann Process Software Corporation June 1993

TP/IX: The Next Internet Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. 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. Distribution of this memo is unlimited. Abstract The first version of this memo, describing a possible next generation of Internet protocols, was w</description>
      <pubDate>Mon, 04 Feb 2008 23:00:59 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042142/rfc1475</guid>
    </item>
    <item>
      <title>rfc1474</title>
      <link>http://www.scribd.com/doc/2042140/rfc1474</link>
      <description>Network Working Group Request for Comments: 1474

F. Kastenholz FTP Software, Inc. June 1993

The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract This memo defines a portion of the Management Information </description>
      <pubDate>Mon, 04 Feb 2008 23:00:57 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042140/rfc1474</guid>
    </item>
    <item>
      <title>rfc1473</title>
      <link>http://www.scribd.com/doc/2042139/rfc1473</link>
      <description>Network Working Group Request for Comments: 1473

F. Kastenholz FTP Software, Inc. June 1993

The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract This memo defines a portion of the Management Information Base</description>
      <pubDate>Mon, 04 Feb 2008 23:00:56 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042139/rfc1473</guid>
    </item>
    <item>
      <title>rfc1472</title>
      <link>http://www.scribd.com/doc/2042138/rfc1472</link>
      <description>Network Working Group Request for Comments: 1472

F. Kastenholz FTP Software, Inc. June 1993

The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract This memo defines a portion of the Management Information Base (MIB) fo</description>
      <pubDate>Mon, 04 Feb 2008 23:00:55 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042138/rfc1472</guid>
    </item>
    <item>
      <title>rfc1471</title>
      <link>http://www.scribd.com/doc/2042136/rfc1471</link>
      <description>Network Working Group Request for Comments: 1471

F. Kastenholz FTP Software, Inc. June 1993

The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract This memo defines a portion of the Management Information Base (MIB)</description>
      <pubDate>Mon, 04 Feb 2008 23:00:54 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042136/rfc1471</guid>
    </item>
    <item>
      <title>rfc1470</title>
      <link>http://www.scribd.com/doc/2042135/rfc1470</link>
      <description>Network Working Group Request for Comments: 1470 FYI: 2 Obsoletes: 1147

R. Enger ANS J. Reynolds ISI Editors June 1993

FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 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. New and/or updated tools are lis</description>
      <pubDate>Mon, 04 Feb 2008 23:00:52 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042135/rfc1470</guid>
    </item>
    <item>
      <title>rfc1469</title>
      <link>http://www.scribd.com/doc/2042132/rfc1469</link>
      <description>Network Working Group Request for Comments: 1469

T. Pusateri Consultant June 1993

IP Multicast over Token-Ring Local Area Networks Status of this Memo This RFC specifies an IAB standards track protocol 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. Distribution of this memo is unlimited. Abstract This document specifies a method for the transmission of IP multicast datagrams over Token-Ring Local Area Networks. Although</description>
      <pubDate>Mon, 04 Feb 2008 23:00:46 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042132/rfc1469</guid>
    </item>
    <item>
      <title>rfc1467</title>
      <link>http://www.scribd.com/doc/2042130/rfc1467</link>
      <description>Network Working Group Request for Comments: 1467 Obsoletes: 1367 Status of CIDR Deployment in the Internet Status of this Memo

C. Topolcic CNRI August 1993

This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 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. Since all the milestones propose</description>
      <pubDate>Mon, 04 Feb 2008 23:00:45 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042130/rfc1467</guid>
    </item>
    <item>
      <title>rfc1468</title>
      <link>http://www.scribd.com/doc/2042131/rfc1468</link>
      <description>Network Working Group Request for Comments: 1468

J. Murai Keio University M. Crispin Panda Programming E. van der Poel June 1993

Japanese Character Encoding for Internet Messages Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Introduction This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. It was first specified by and used in JUNET [JUNET]. The encoding is now also widely used in Japanese IP comm</description>
      <pubDate>Mon, 04 Feb 2008 23:00:45 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042131/rfc1468</guid>
    </item>
    <item>
      <title>rfc1466</title>
      <link>http://www.scribd.com/doc/2042129/rfc1466</link>
      <description>Network Working Group Request for Comments: 1466 Obsoletes: 1366 Guidelines for Management of IP Address Space Status of this Memo

E. Gerich Merit May 1993

This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Abstract This document has been reviewed by the Federal Engineering Planning Group (FEPG) on behalf of the Federal Networking Council (FNC), the co-chairs of the Intercontinental Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to sup</description>
      <pubDate>Mon, 04 Feb 2008 23:00:44 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042129/rfc1466</guid>
    </item>
    <item>
      <title>rfc1465</title>
      <link>http://www.scribd.com/doc/2042127/rfc1465</link>
      <description>Network Working Group Request for Comments: 1465

U. Eppenberger SWITCH May 1993

Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing Status of this Memo This memo defines 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. Distribution of this memo is unlimited. 1. Introduction The usage of the X.400 Message Handling System</description>
      <pubDate>Mon, 04 Feb 2008 23:00:43 GMT</pubDate>
      <guid>http://www.scribd.com/doc/2042127/rfc1465</guid>
    </item>
  </channel>
</rss>
