Прошел экстерном экзамен по курсу перепордготовки "Информационная безопасность". Хочу получить диплом, но не вижу где оплатить? Ну и соответственно , как с получением бумажного документа? |
Протоколы и алгоритмы маршрутизации в Интернет
:Протоколы и алгоритмы маршрутизации в Интернет
: Литература по курсу
Опубликован: 28.09.2007 | Уровень: специалист | Доступ: платный
- 1.Domain Names — Concepts and Facilities, STD13, RFC-1034USC/Information Sciences Institute, November 1987
- 2.Domain Names — Implementation and Specification, STD 13, RFC-1035USC/Information Sciences Institute, November 1987
- 3.IP Version 6 Addressing Architecture, RFC-1884, Ipsilon NetworksXerox PARC, December 1995
- 4.Transition Mechanisms for IPv6 Hosts and RoutersWork in Progress
- 6.“The MD5 Message Digest Algorithm”April 1992
- 7.“TCP Performance”The Internet Protocol Journal, Vol. 3, No. 2, Cisco Systems, June 2000
- 8.Infocom ’97, апрель, 1997, IEEE/ACM Trans. Networking, V5, N3, p.336-350, June 1997
- 9.Университет Осаки, Япония
- 10.“Fundamentals of Telecommunication Networks”Wiley-Interscience Publication, Jhon Wiley & sons, inc. 1995
- 11.ATM Forum Trac Management Specication Version 4.0, Draft Specification ATM Forum/95-0013R11ATM Forum, March 1996.
- 12.“Dynamical behavior of rate based flow control mechanisms”Computer Communication Review pp. 35-49, April 1990
- 13.“End-to-end packet delay and loss behavior in the Internet”Proc. ACM SIGCOMM ’93
- 14.“On the Design of Interfaces for TCP/IP over Wireless”Proceedings of IEEE Milcom ‘96
- 15.“Analysis and simulation of affair queueing algorithm”Proc. ACM SIGCOMM ‘89
- 16.“An approach to high performance high speed data networks”IEEE Communications Magazine, pp. 74-82, October 1991
- 17.“Connections with Multiple Congested Gateways in Packet Switched Networks Part 1: One-way Traffic”Computer Communications Review, vol. 21 no.5 pp. 30-47,October 1991
- 18.“Random Early Detection gateways for congestion avoidance”IEEE/ACM Transactions of Networking vol. 1, no. 4, pp. 397-413, August 1993. . http://www-nrg.ee.lbl.gov/nrg-paper.html
- 19.Proc. ACM SIGCOMM ’88, pp. 314-329
- 20.message to end2end-interest mailing list, April 1990, URL
- 21.“Berkeley TCP evolution from 4.3-tahoe to 4.3-reno”Proc. of the 18th Internet Engineering Task Force, Vancouver, August, 1990
- 22.“Improving Round Trip Time Estimates in Reliable Transport Protocols”ACM Trans. on Computer Systems, vol. 9no. 4, pp. 364-373, November 1991
- 23.“Window-based error recovery and flow control with a slow acknowledgement channel: a study of TCP/IP performance”Proceedings of IEEE Infocom 1997
- 24.“On the performance of Submitting Excess Traffic to ATM Networks”Proc. of Globecom 1991 pp. 281-288, December 1991
- 25.“Asymptotically optimal design of congestion control for high speed data networks”IEEE Trans. Commun., vol. 40, no. 2, pp. 301-311, February 1992
- 26.“Dynamic adaptive windows for high speed data networks with multiple paths and propagation delays”Computer Networks and ISDN Systems, vol. 25, pp. 663-679, 1993
- 27.“Analysis of dynamic congestion control protocols — a Fokker-Planck approximation”Proc. ACM SIGCOMM ‘91, pp. 159-169
- 28.“A generalized processor sharing approach to flow control in integrated services networks — the multiple node case”Proc. IEEE Infocom ‘93
- 29.“A binary feedback scheme for congestion avoidance in computer networks with a connectionless network layer”Proc. ACM SIGCOMM ’88, pp. 303-313
- 30.“A theoretical analysis of feedback flow control”Proc. ACM SIGCOMM ’90, pp. 156-165
- 31.“Some observations on the dynamics of a congestion control algorithm”Computer Communication Review, pp. 30-39, October 1990
- 32.“A new architecture for packet switching network protocols”Ph. D. dissertation, M.I.T. Lab. Comput. Sci. ,Cambridge, MA., 1989
- 33.“Observations on the dynamics of a congestion control algorithm the effects of two-way traffic”Proc. ACM SIGCOMM ’91, pp. 133-147
- 34.“The Macroscopic Behavior of the TCP Congestion Avoidance Algorithm”ACM SIGCOMM, v27, N3, July 1997. Computer Communication Review, Vol.27, No.3, 1997
- 35.“Simulation-based Comparisons of Tahoe, Reno, and SACK TCP”
- 36.IEEE GLOBECOM’01, San Antonio, TX, USA
- 38.“Promoting the Use of End-to-End Congestion Control in the Internet”IEEE/ACM Transactions on Internetworking, V7, N4. August 1999
- 39.“A Packet Selection Algorithm for Adaptive Transmission of Smoothed Video Over a Wireless Channel”
- 40.“Modeling TCP Throughput: A Simple Model and Its Empirical Validation”UMASS CMPSCI Tech. Report TR98-008, Feb.1998
- 44.February 1995
- 45.February 1995
- 46.October 1996
- 48.
- 52.IEEE J. Select. Areas Commun. V13, pp. 633-641, 1995
- 54.Proc. SIGCOMM Symp. Communications Architectures and Protocols, Aug. 1998, pp.303-314
- 55.Proc. Conf. Computer Communications. (IEEE INFOCOM) Mar. 1998
- 56.An Integrated Congestion Management Architecture for Internet HostsProc. ACM SIGCOMM, Cambridge, MA, September 1999
- 57.EquationBased Congestion Control for Unicast ApplicationsAugust 2000, Proc. ACM SIGCOMM 2000
- 58.EquationBased Congestion Control for Unicast Applications: the Extended VersionICSI tech report TR0003, March 2000
- 59.Modeling TCP Throughput: A Simple Model and its Empirical ValidationProc. ACM SIGCOMM 1998
- 60.Computing TCP's Retransmission Timer, RFC-2988November 2000
- 61.The Addition of Explicit Congestion Notification (ECN) to IP, RFC-3168September 2001
- 62.RTP: A Transport Protocol for RealTime Applications, RFC-1889January 1996
- 63.Robust Congestion SignalingIEEE International Conference on Network Protocols, November 2001
- 64.Diploma Thesis, University of Mannheim, February 2000
- 65.Resource Location Protocol, RFC-887, CMUDecember 1983
- 66.DHCP Options and BOOTP Vendor Extensions, RFC-1533Lachman Technology, Inc., Bucknell University, October 1993
- 67.Requirements for Internet Hosts — Communication Layers, STD 3, RFC-1122USC/Information Sciences Institute, October 1989
- 68.Requirements for Internet Hosts — Application and Support, STD 3, RFC-1123USC/Information Sciences Institute, October 1989
- 69.Dynamic Reverse Address Resolution Protocol (DRARP)Work in Progress
- 70.Uniform Access to Internet Directory ServicesProc. of ACM SIGCOMM' 90 (Special issue of Computer Communications Review), 20(4):5059, 1990
- 71.Bootstrap Protocol (BOOTP), RFC-951Stanford and SUN Microsystems, September 1985
- 72.Interoperation between DHCP and BOOTP, RFC-1534Bucknell University, October 1993
- 73.A Reverse Address Resolution Protocol, RFC-903Stanford, June 1984
- 74.On Traffic Phase Effects in Packet Switched GatewaysInternetworking: Research and Experience vol.3 no.3 pp. 115-156, September 1992. (An earlier version of this paper appeared in Computer Communication Review, vol. 21 no.2 April 1991)
- 75.Domain Names — Implementation and Specification, STD 13, RFC-1035USC/Information Sciences Institute, November 1987
- 76.Dynamic IP-адрес Assignment for Ethernet Attached HostsWork in Progress
- 77.BOOTP Vendor Information Extensions, RFC-1497USC/Information Sciences Institute, August 1993
- 78.A Protocol for the Dynamic Assignment of IP-адресes for use on an EthernetAvailable from the Athena Project, MIT, 1989
- 79.Clarifications and Extensions for the Bootstrap Protocol, RFC-1542Carnegie Mellon University, October 1993
- 80.The User Class Option for DHCP, RFC-3004November 2000
- 81.DHCP Relay Agent Information Option. RFC-3046January 2001
- 82.
- 83.DHCP Options and BOOTP Vendor Extensions, RFC-2132March 1997
- 84.Dynamic Host Configuration Protocol, RFC-2131March 1997
- 85.Uniform Resource Locators (URL), RFC-1738December 1994
- 86.DHCP Options and BOOTP Vendor Extensions, RFC-2132March 1997
- 87.Tags for the identification of languages, RFC-1766UNINETT, March 1995
- 88.The Internet Gopher Protocol: (a distributed document search and retrieval protocol), RFC-1436University of Minnesota, March 1993
- 89.Universal Resource Identifiers in WWW, A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the WorldWide Web", RFC-1630CERN, June 1994
- 90.Uniform Resource Locators (URL), RFC-1738CERN, Xerox PARC, University of Minnesota, December 1994
- 91.HyperText Markup Language Specification — 2.0, RFC-1866MIT/LCS, November 1995
- 92.Hypertext Transfer Protocol — HTTP/1.0., RFC-1945 MIT/LCSUC Irvine, May 1996
- 93.Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies, RFC-2045Innosoft, First Virtual, November 1996
- 94.Requirements for Internet hosts — application and support, STD3, RFC-1123IETF, October 1989
- 95.Standard for the Format of ARPA Internet Text Messages, STD 11, RFC-822UDEL, August 1982
- 96.WAIS Interface Protocol Prototype Functional Specification, (v1.5)Thinking Machines Corporation, April 1990
- 97.Relative Uniform Resource Locators, RFC-1808UC Irvine, June 1995
- 98.Standard for interchange of USENET messages, RFC-1036AT&T Bell Laboratories, Center for Seismic Studies, December 1987
- 99.Network News Transfer Protocol. A Proposed Standard for the StreamBased Transmission of News", RFC-977UC San Diego, UC Berkeley, February 1986
- 100.MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for NonASCII Text, RFC-2047University of Tennessee, November 1996
- 101.Formbased File Upload in HTML, RFC-1867Xerox Corporation, November 1995
- 102.Simple Mail Transfer Protocol, STD 10, RFC-821USC/ISI, August 1982
- 103.Media Type Registration Procedure, RFC-2048USC/ISI, November 1996
- 104.File Transfer Protocol (FTP), STD 9, RFC-959USC/ISI, October 1985
- 105.Assigned Numbers, STD 2, RFC-1700USC/ISI, October 1994
- 106.Functional Requirements for Uniform Resource Names, RFC-1737, MIT/LCSXerox Corporation, December 1994
- 107.USASCII. Coded Character Set — 7Bit American Standard Code for Information InterchangeStandard ANSI X3.41986, ANSI, 1986
- 108.ISO8859. International Standard — Information Processing — 8-bit SingleByte Coded Graphic Character Sets1987-1990
- 109.The ContentMD5 Header Field, RFC-1864Carnegie Mellon, Dover Beach Consulting, October, 1995
- 110.Renumbering Needs Work, RFC-1900IAB, February 1996
- 111.GZIP file format specification version 4.3. RFC-1952Aladdin Enterprises, May 1996
- 112.Computer Networks and ISDN Systems, v. 28, pp. 2535, Dec. 1995
- 113.Analysis of HTTP PerformanceUSC/Information Sciences Institute, June 1996
- 114.Network Time Protocol, Version 3, Specification, Implementation and Analysis, RFC- 1305University of Delaware, March 1992
- 115.DEFLATE Compressed Data Format Specification version 1.3. RFC 1951Aladdin Enterprises, May 1996
- 116.Analysis of HTTP Performance Problems
- 117.ZLIB Compressed Data Format Specification version 3.3, RFC-1950Aladdin Enterprises, InfoZIP, May 1996
- 118.An Extension to HTTP : Digest Access Authentication, RFC-2069янв.97
- 119."Architectural considerations for a new generation of protocols," in SIGCOMM Symposium on Communications Architectures и ProtocolsPhiladelphia, Pennsylvania, pp. 200208, IEEE, Sept. 1990. Computer Communications Review, Vol. 20(4), Sept. 1990
- 120.Internetworking with TCP/IP , vol. 1. Englewood CliffsNew Jersey: Prentice Hall, 1991
- 121."Internet Protocol", STD 5, RFC-791USC/Information Sciences Institute, September 1981
- 122."Network Time Protocol Version 3", RFC-1305UDEL, March 1992
- 123."Assigned Numbers", STD 2, RFC-1700USC/Information Sciences Institute, October 1994
- 124."Randomness Recommendations for Security", RFC-1750DEC, Cybercash, MIT, December 1994
- 125."Scalable feedback control for multicast video distribution in the internet" in SIGCOMM Symposium on Communications Architectures и ProtocolsLondon, England, pp. 5867, ACM, Aug. 1994
- 126."Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, и Identifiers", RFC-1423TIS, IAB IRTF PSRG, IETF PEM WG, February 1993
- 127."Security mechanisms in highlevel network protocols"ACM Computing Surveys, vol. 15, pp. 135171, June 1983
- 128."The MD5 MessageDigest Algorithm", RFC-1321MIT Laboratory for Computer Science и RSA Data Security, Inc., April 1992
- 129."Security services for multimedia conferencing," in 16-th National Computer Security ConferenceBaltimore, Maryland, pp. 391395, Sept. 1993
- 130."The synchronization of periodic routing messages"IEEE/ACM Transactions on Networking , vol. 2, pp. 122136, April 1994
- 131."Dynamic QoS control of multimedia applications based on RTP"Computer Communications , Jan. 1996
- 132."The synchronization of periodic routing messages" in SIGCOMM Symposium on Communications Architectures and ProtocolsSan Francisco, California, pp. 3344, ACM, Sept. 1993. also in [24]
- 133.Foundations of digital signal processing and data analysis New YorkNew York: Macmillan, 1987
- 134.Unicode Consortium, The Unicode Standard New YorkNew York: AddisonWesley, 1991
- 135."Domain Names — Concepts and Facilities", STD13, RFC-1034USC/Information Sciences Institute, November 1987
- 136."Domain Names — Implementation and Specification", STD 13, RFC-1035USC/Information Sciences Institute, November 1987
- 137."Requirements for Internet Hosts — Application and Support", STD 3, RFC-1123Internet Engineering Task Force, October 1989
- 138."Address Allocation for Private Internets", RFC-1597T.J. Watson Research Center, IBM Corp., Chrysler Corp., RIPE NCC, March 1994
- 139."Network 10 Considered Harmful (Some Practices Shouldn't be Codified)", RFC1627Silicon Graphics, Inc., Apple Computer, Inc., Silicon Graphics, Inc., July 1994
- 140."Standard for the Format of ARPA Internet Text Messages", STD 11, RFC-822UDEL, August 1982
- 141.An Introduction to Probability Theory and its Applications, Volume 1 , vol. 1. New YorkNew York: John Wiley and Sons, third ed., 1968
- 142.“Uniform Resource Identifiers (URI): Generic Syntax,” RFC 2396August 1998
- 143.“SIP Services: Slowly Rolling Forward”Business Communications Review, June 2002
- 144.“SIP for the Enterprise: Work in Progress”Business Communications Review, February 2003
- 145.“SDP: Session Description Protocol” RFC 2327April 1998
- 146.“The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services” RFC 2848June 2000
- 147.“SIP: Session Initiation Protocol” RFC 3261June 2002
- 148.“An Offer/Answer Model with the Session Description Protocol” RFC 3264June 2002
- 149.“The Session Initiation Protocol: Providing Advanced Telephony Access Across the Internet”Bell Labs Technical Journal, OctoberDecember 1998
- 150.Figures 2 through 4 are adapted from ones developed by Professor H. Charles Baker of Southern Methodist University
- 151.RFC2386A Framework for QoSbased Routing in the Internet. August 1998
- 152.RFC1633. Integrated Services in the Internet Architecture: an OverviewJune 1994
- 153.RFC2547. BGP/MPLS VPNsMarch 1999
- 154.RFC2702, Requirements for Traffic Engineering Over MPLSSeptember 1999
- 155.RFC2917, A Core MPLS IP VPN ArchitectureSeptember 2000
- 156.RFC3031, Multiprotocol Label Switching ArchitectureJanuary 2001
- 157.RFC3032, MPLS Label Stack EncodingJanuary 2001
- 158.RFC3035, MPLS using LDP and ATM VC SwitchingJanuary 2001
- 159.RFC3063, MPLS Loop Prevention MechanismFebruary 2001
- 160.Искусство оптимизации трафикаЖурнал сетевых решений LAN, декабрь 2001, стр. 38-47
- 161.Виртуальные частные сети на основе MPLSЖурнал сетевых решений LAN, январь 2002, стр. 58-63
- 162.Глобальная служба MPLS: опережая времяЖурнал сетевых решений LAN, март 2002, стр. 32-38
- 163.MPLS на службе VPNЖурнал сетевых решений LAN, март 2002, стр. 40-47
- 164.RFC3270, MultiProtocol Label Switching (MPLS) Support of Differentiated ServicesMay 2002.
- 165.
- 166.
- 167.MPLS and VPN Architectures. A Practical Guide to Understanding, Designing and Deploying MPLS and MPLSEnabled VPNsCisco Press, 2000
- 168.The MPLS Primer. An Introduction to Multiprotocol Label SwitchingPrentice Hall, 2001
- 169.MPLS. Implementing the Technology. With CDROMAddison Wesley, 2001
- 170.
- 171.RFC2430, Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)October 1998
- 172.RFC2210, The Use of RSVP with IETF Integrated ServicesSeptember 1997.
- 173."Resource ReSerVation Protocol", RFC2205September 1997
- 174.Multiprotocol Extensions for BGP4. RFC2858June 2000
- 175.RFC2212. Specification of the ControlledLoad Network Element ServiceSeptember 1997.
- 176.RFC2212. Specification of Guaranteed Quality of ServiceSeptember 1997.
- 177.RFC2748. The COPS (Common Open Policy Service) ProtocolJanuary 2000
- 178.“A Framework for PolicyBased Admission Control”, RFC2753January 2000
- 179.RFC2379. RSVP over ATM Implementation GuidelinesAugust 1998
- 180.RFC2380. RSVP over ATM Implementation RequirementsAugust 1998
- 181.RFC2382. A Framework for Integrated Services and RSVP over ATMAugust 1998
- 182.RFC2749 COPS usage for RSVPJanuary 2000
- 183.RFC2750. RSVP Extensions for Policy ControlJanuary 2000
- 184.RFC2814. SBM (Subnet Bandwidth Manager): A Protocol for RSVPbased Admission Control over IEEE 802style networksMay 2000
- 185.RFC3175. Aggregation of RSVP for IPv4 and IPv6 ReservationsSeptember 2001
- 186.RFC3209. RSVPTE: Extensions to RSVP for LSP TunnelsDecember 2001
- 187.RFC2940. Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol ClientsOctober 2000
- 188.RFC3084. COPS Usage for Policy Provisioning (COPSPR)March 2001
- 189.Контроль трафика в сетях ATMLAN/Журнал Сетевых решений №12/98
- 190.
- 191.
- 195.IPDatentransport ist nur der Anfang. Wilhelm GreinerLANline 10/2002, стр. 110-115; MPLS als Hoffnungstraeger. Gerhard Kafka, LANline 10/2002, стр. 122-125. Keine Zeit fuer Auszeigen. Markus Heis, LANline 10/2002, стр. 126129;
- 196.Overview of IP Multicast in a MultiProtocol Label Switching (MPLS) Environment; RFC3353August 2002
- 197.Time To Live (TTL) Processing in MultiProtocol Label Switching (MPLS) Networks; RFC3443January 2003
- 198.Framework for MultiProtocol Label Switching (MPLS)based Recovery; RFC3469February 2003
- 199.Generalized MultiProtocol Label Switching (GMPLS)Signaling Functional Description; RFC3471January 2003
- 200.Generalized MultiProtocol Label Switching (GMPLS) Signaling Constraintbased Routed Label Distribution Protocol (CRLDP) Extensions; RFC3472January 2003
- 201.Generalized MultiProtocol Label Switching (GMPLS) Signaling Resource ReserVation ProtocolTraffic Engineering (RSVPTE) Extensions; RFC3473January 2003
- 202.Graceful Restart Mechanism for Label Distribution Protocol; RFC3478February 2003
- 203.Fault Tolerance for the Label Distribution Protocol (LDP); RFC3479February 2003
- 204.“Качество обслуживания в сетях IP”Cisco Press, 2003
- 205.Definition of the Differentiated Services Field (DS Field)in the IPv4 and IPv6 Headers; RFC2474December 1998
- 206.Assured Forwarding PHB Group; RFC2597June 1999
- 208.“MPLS and VPN Architectures”Cisco Press, 2001
- 209.RFC3812. Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) ManagementJune 2004
- 210.RFC3812. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)June 2004
- 211.RFC3813. Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)June 2004
- 212.RFC3814. Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FECToNHLFE) Management Information Base (MIB)June 2004
- 213.RFC3815. Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)June 2004
- 214.RFC3919. Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and Multi Protocol Label Switching (MPLS)October 2004
- 215.RFC4023. Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)March 2005
- 216.“Multiprotocol Label Switching Architecture” RFC 3031January 2001
- 217.“Key words for use in RFCs to Indicate Requirement Levels”. BCP 14, RFC 2119March 1997
- 218.“Internet Control Message Protocol”, STD 5, RFC 792September 1981
- 219.“Path MTU Discovery”, RFC 1191November 1990
- 220.“IP Router Alert Option”, RFC 2113February 1997
- 221.“The PointtoPoint Protocol (PPP)”, STD 51, RFC1661July 1994
- 222.“Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification”, RFC 1885December 1995
- 223.“Path MTU Discovery for IP version 6”, RFC 1981August 1996
- 224.“MPLS Using LDP и ATM VC Switching”, RFC 3035January 2001
- 225.“A Proposed Architecture for MPLS”Work in Progress.
- 226.“A Framework for Multiprotocol Label Switching”Work in Progress
- 227.“Provider Architecture for Differentiated Services и Traffic Engineering (PASTE)”, RFC 2430October 1998
- 228.“Cisco Systems’ Tag Switching Architecture — Overview”, RFC 2105February 1997
- 229.“Quality of Service Extensions to OSPF”Work in Progress
- 230.“A Framework for QoS Based Routing in the Интернет”, RFC 2386August 1998
- 231.“QoS Routing Mechanisms и OSPF Extensions”, RFC 2676August 1999
- 232.“A Taxonomy for Congestion Control Algorithms in Packet Switching Networks”IEEE Network Magazine, Volume 9, Number 5, July/August 1995
- 233.“Routing Subject to Quality of Service Constraints in Integrated Communication Networks“IEEE Network, July 1995, pp 46-55
- 234.“Traffic Management Specification: Version 4.0”ATM Forum, April 1996
- 235.“Resource ReSerVation Protocol (RSVP) — Version 1, Functional Specification”, RFC 2205September 1997
- 236.“Multiprotocol Label Switching Architecture”, RFC 3031January 2001
- 237.“Requirements for Traffic Engineering over MPLS”, RFC 2702September 1999
- 238.“Specification of the ControlledLoad Network Element Service”, RFC 2211September 1997
- 239.“MPLS Label Stack Encoding”, RFC 3032January 2001
- 240.“Key words for use in RFCs to Indicate Requirement Levels”, BCP 14, RFC2119,March 1997
- 241.“Type of Service in the Internet Protocol Suite”, RFC 1349July 1992
- 242.“Definition of the Differentiated Services Field (DS Field) in the IPv4 и IPv6 Headers”, RFC 2474December 1998
- 243.“Signaled Preemption Priority Policy Element”, RFC 2751January 2000
- 244.“Applicability Statement for Extensions to RSVP for LSPTunnels”, RFC 3210December 2001
- 245.“The Use of RSVP with IETF Integrated Services”, RFC 2210September 1997
- 246.“Internet Control Message Protocol”, STD 5, RFC 792September 1981
- 247.“Path MTU Discovery”, RFC 1191November 1990
- 248.“Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6)”, RFC 2463December 1998
- 249.“Guidelines for Writing an IANA Considerations Section in RFCs”, BCP 26, RFC 2434October 1998
- 250.“Specification of the Null Service Type”, RFC 2997November 2000
- 251."An Architecture for IPv6 Unicast Address Allocation", RFC-1887cisco Systems, December 1995
- 252."Generalized MultiProtocol Label Switching (GMPLS) Architecture"October 2004
- 253."IP Encapsulating Security Payload (ESP)", RFC-2401November 1998
- 254."The Internet Key Exchange (IKE)", RFC-2409November 1998
- 255.TCP Friendly Rate Control (TFRC): Protocol Specification, RFC-3448Proposed Standard, January 2003
- 256."RSVP Refresh Overhead Reduction Extensions", RFC-2961April 2001
- 257."Generalized MultiProtocol Label Switching (GMPLS) Signaling Functional Description", RFC-3471January 2003
- 258."Signalling Unnumbered Links in Resource Reservation Protocol — Traffic Engineering (RSVPTE)", RFC-3477January 2003
- 259."IP Authentication Header", RFC-2401November 1998
- 260."Guidelines for Writing an IANA Considerations Section in RFC-s", BCP 26, RFC-2434October 1998.
- 261.Stream Control Transmission Protocol. RFC-2960RFC-2119, March 1997
- 262.The Internet Standards ProcessRevision 3. RFC-2026September 1997
- 263.Datagram Congestion Control Protocoldraftietfdccpspec04.txt, работа продолжается, июнь 2003
- 264."GMPLS SONET/SDH Specifics"Work in Progress
- 265."Routing Extensions in Support of Generalized MPLS"Work in Progress
- 266."GMPLS Signaling Procedure for Egress Control."February 2005
- 267."The MD5 MessageDigest Algorithm," RFC-1321April 1992
- 268."Generalized MultiProtocol Label Switching (GMPLS) Signaling Resource ReserVation ProtocolTraffic Engineering (RSVPTE) Extensions"January 2003
- 269."A Border Gateway Protocol 4 (BGP4)", RFC-1771March 1995
- 270."Link Management Protocol"Work in Progress
- 271."Link Bundling in MPLS Traffic Engineering"Work in Progress
- 272."LSP Hierarchy with MPLS TE"Work in Progress
- 273."The Internet Standards Process — Revision 3" BCP 9, RFC-2026ctober 1996
- 274."RSVP Cryptographic Authentication",RFC-2747January 2000
- 275."ConstraintBased LSP Setup using LDP", RFC-3212January 2002
- 276."RSVPTE: Extensions to RSVP for LSP Tunnels", RFC-3209December 2001
- 277."LDP Specification", RFC-3036January 2001
- 278."LDP Applicability", RFC-3037January 2001
- 279."MPLS using LDP and ATM VC Switching", RFC-3035January 2001
- 280."Use of Label Switching on Frame Relay Networks Specification", RFC-3034January 2001
- 281."MPLS Label Stack Encoding", RFC-3032January 2001
- 282."OSPF Version 2", STD 54, RFC-2328April 1998.
- 283."Multiprotocol Encapsulation over ATM Adaptation Layer 5"RFC-1483, July 1993
- 284."Generalized MultiProtocol Label Switching (GMPLS) Signaling Constraintbased Routed Label Distribution Protocol (CRLDP) Extensions", RFC-3472January 2003
- 285."Carrying Label Information in BGP4"Rekhter, Rosen, Work in Progress
- 286."Guidelines for Writing an IANA Considerations Section in RFC-s", BCP 26, RFC-2434October 1998
- 287."Host Extensions for IP multicasting", STD 5, RFC-1112Stanford University, August 1989
- 288."Multiprotocol Label Switching Architecture", RFC-3031January 2001
- 289.“Two Issues in Reservation Establishment”Proc. ACM SIGCOMM ‘95, Cambridge, MA, August 1995
- 290.“Policy Control for RSVP: Architectural Overview”Work in Progress
- 291.“Specification of Guarantied Quality of Service”February 2005
- 292.“Specification of the ControlledLoad Network Element Service”Work in Progress
- 293.“The Use of RSVP with Integrated Services”, RFC 2210September 1997
- 294."Requirements for Traffic Engineering over MPLS", RFC-2702September 1999
- 295."Protection of BGP Sessions via the TCP MD5 Signature Option", RFC-2385August 1998
- 296."Resource ReSerVation Protocol (RSVP) — Version 1 Functional Specification", RFC-2205September 1997
- 297."Key words for use in RFC-s to Indicate Requirement Levels", BCP 14RFC-2119, March 1997
- 298.“Integrated Services in the Internet Architecture: an Overview”, RFC 1633ISI, MIT, and PARC, June 1994
- 299.“Synchronization of Periodic Routing Messages”IEEE/ACM Transactions on Networking, Vol. 2, No. 2, April, 1994
- 300.“RSVP Extensions for IPSEC Data Flows”, RFC 2207September 1997
- 301.“Resource Reservation Protocol (RSVP) — Version 1. Applicability Statement”.November 1998
- 302."MPLS Label Stack Encoding", RFC-3032January 2001
- 303."ASSIGNED NUMBERS", STD 2, RFC-1700October 1994
- 304."MPLS using ATM VP Switching"Work in Progress
- 305.“IP Router Alert Option”, RFC 2113cisco Systems, February 1997
- 306."LDP Specification", RFC-3036January 2001
- 307."Use of Label Switching on Frame Relay Networks Specification", RFC-3034January 2001
- 308."ConstraintBased LSP Setup using LDP"Jamoussi, Editor, Work in Progress
- 309."MPLS using LDP and ATM VC Switching", RFC-3035January 2001
- 310.An EndtoEnd Approach to Host MobilityProc. 6th Annual ACM/IEEE International Conference on Mobile Computing and Networking (MOBICOM '00), August 2000
- 311."Neighbor Discovery for IP Version 6 (IPv6)"Work in Progress
- 312."IP Version 6 Addressing Architecture", RFC-1884Ipsilon Networks, Xerox PARC, December 1995
- 313."Internet Protocol, Version 6 (IPv6) Specification", RFC 1883Xerox PARC, Ipsilon Networks, December 1995
- 314."Supernetting: an Address Assignment and Aggregation Strategy", RFC 1338BARRNet, cisco, Merit, OARnet, June 1992
- 315."Extensions to RSVP for LSP Tunnels"Awduche, Berger, Gan, Li, Swallow, Srinvasan, Work in Progress
- 316."An Architecture for Differentiated Services", RFC-2475December 1998
- 317."ConstraintBased LSP Setup using LDP"Work in Progress
- 318.“RSVP Cryptographic Authentication”Work in Progress
- 319."Requirements for Traffic Engineering Over MPLS", RFC-2702September 1999
- 320.“Resource Reservation Protocol (RSVP) — Version 1.Message Processing Rules”Work in Progress
- 321."Host Anycasting Service", RFC-1546BBN, November 1993