|
|
| About site: Internet/RFCs/1701 - 1800 - RFC 1721 |
Return to Computers also Computers |
| About site: http://www.faqs.org/rfcs/rfc1721.html |
Title: Internet/RFCs/1701 - 1800 - RFC 1721 RIP Version 2 Protocol Analysis. G. Malkin. November 1994. |
|
|
|
|
AbaSioux_HTTP_Server The server supports virtual servers, CGI, SSL, and can easily be extended by writing plugins. The server binaries, documentation, and header files are freely available.
| The_Operating_System_Developers_Homepage Index of operating systems and links to resources for programmers.
| ImageGlue A set of active server page extensions for professional quality still image manipulation. Read and write BMP, PNG, TIFF, JPEG/JFIF, GIF, Photoshop, QuickDraw PICT, Targa, QuickTime Image, Silicon Grap
| Sun_Java_4_U Links and resources useful for SCJP aspirants includes exam simulators, mock exams, study guides.
| FTPFAST_com FTP Site Hosting service. Allows multiple account setup for sharing files with different people.
| PageBlockers Features Flash and classic HTML design services, custom graphic design and desktop publishing. Located in Sioux Falls, South Dakota.
|
|
| Alexa statistic for http://www.faqs.org/rfcs/rfc1721.html |
Please visit: http://www.faqs.org/rfcs/rfc1721.html
|
| Related sites for http://www.faqs.org/rfcs/rfc1721.html |
| ClearInternet Web Hosting and Web Design. PHP, CGI, ASP, And Perl solutions. | | developWorks__Wireless Provides educational articles, news, and access to the most useful tools involved in wireless technology. | | Rodney_Knaap__Build_your_own_ZX81 ZX81 hardware website featuring a project for building your own ZX81 with discrete components as well as Wilf Rigter's ZX97. In English, Dutch and German. | | DMC_Inc_ Develops and implements software to automate and control industrial machines, business processes, and test/measurement systems. Offers controls engineering and consulting to the industrial automation | | RAGE3D Site dedicated to Rage Pro\Rage 128\Rage 128 Pro owners. | | Quickbuild PMEase - Commercial version of Luntbuild, a Java web application for build automation and management. Features various CM adapters, build promotion, user-defined build steps, concurrent execution of s | | Crypto_CD A comprehensive archive of cryptography programs. Includes a lot of filesystems. (Available on CD or their ftp site) | | Smalltalk_Best_Practice_Patterns By Kent Beck; Prentice Hall, 1997, ISBN 013476904X. Real world style guide for better programming; gives set of patterns that organize informal experience successful Smalltalk programmers learned the | | Learn_to_Program_Using_Python__A_Tutorial_for_Hobbyists,_Self-Starters,_and_All_Who_Want_to_Learn_the_Art_of_Computer_Programmin By Alan Gauld; Addison Wesley Professional, 2001, ISBN 0201709384, has CD-ROM. Introduction for those learning programming basics: terminology, concepts, methods to write code. Assumes no prior knowle | | Quality_Link_Software Quality management software manages any quality system. | | Qtopia An application environment designed to make mobile computing simple, powerful, intuitive, and flexible. Provided by Trolltech, the creators of Qt. Information and SDK-Download. | | Count_Me_In,_LLC_ Time and attendance tracking and door access control software. [Windows] | | Xellsoft Specialize in Python programming technology and object oriented databases, develop custom software and offer consulting in the area of internet, data communication, technical and scientific programmin | | RFC_2695 Authentication Mechanisms for ONC RPC. A. Chiu. September 1999. | | RFC_2960 Stream Control Transmission Protocol. R. Stewart, Q. Xie, K. Morneault, C. Sharp, H. Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V. Paxson. October 2000. | | Workplace_Multimedia Offers design, flash, and graphics services. | | Wired_Media_Ltd Details of web design, e-commerce, content management, branding and digital marketing solutions. | | 9th_Street_Creative Offers web design, hosting, branding, and promotion. Located in Tuscaloosa, Alabama, USA. | | Esultants_com Offering hosting, web design, Flash design, e-commerce solutions, search engine optimization, advertising, and corporate image development. | | NMS A collection of programs intended as secure and robustly written drop in replacements for those provided by Matt's Script Archive - an ongoing project of The London Perl Mongers. |
|
This is websites2007.org cache of m/ as retrieved on 2008.09.07 websites2007.org's cache is the snapshot that we took of the page as we crawled the web. The page may have changed since that time.
|
RFC 1721 (rfc1721) - RIP Version 2 Protocol Analysis@import 'http://faqs.org/abstracts/css/default.css';@import 'http://faqs.org/search.css';function erfc(s){document.write("[ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ]Alternate Formats: rfc1721.txt | rfc1721.txt.pdfRFC 1721 - RIP Version 2 Protocol AnalysisSearch the Archives Display RFC by number RFC1721 - RIP Version 2 Protocol AnalysisNetwork Working Group G. MalkinRequest for Comments: 1721 Xylogics, Inc.Obsoletes: 1387 November 1994Category: Informational RIP Version 2 Protocol AnalysisStatus 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 As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This report is a prerequisite to advancing RIP-2 on the standards track.Acknowledgements The RIP-2 protocol owes much to those who participated in the RIP-2 working group. A special thanks goes to Fred Baker, for his help on the MIB, and to Jeffrey Honig, for all his comments.1. Protocol Documents The RIP-2 applicability statement is defined in RFC 1722 [1]. The RIP-2 protocol description is defined in RFC 1723 [2]. This memo obsoletes RFC 1388, which specifies an update to the "Routing Information Protocol" RFC 1058 (STD 34). The RIP-2 MIB description is defined in RFC 1724 [3]. This memo obsoletes RFC 1389.2. Key Features While RIP-2 shares the same basic algorithms as RIP-1, it supports several new features. They are: external route tags, subnet masks, next hop addresses, and authentication. The significant change from RFC 1388 is the removal of the domain field. There was no clear agreement as to how the field would be used, so it was determined to leave the field reserved for future expansion.2.1 External Route Tags The route tag field may be used to propagate information acquired from an EGP. The definition of the contents of this field are beyond the scope of this protocol. However, it may be used, for example, to propagate an EGP AS number.2.2 Subnet Masks Inclusion of subnet masks was the original intent of opening the RIP protocol for improvement. Subnet mask information makes RIP more useful in a variety of environments and allows the use of variable subnet masks on the network. Subnet masks are also necessary for implementation of "classless" addressing, as the CIDR work proposes.2.3 Next Hop Addresses Support for next hop addresses allows for optimization of routes in an environment which uses multiple routing protocols. For example, if RIP-2 were being run on a network along with another IGP, and one router ran both protocols, then that router could indicate to the other RIP-2 routers that a better next hop than itself exists for a given destination.2.4 Authentication One significant improvement RIP-2 offers over RIP-1, is the addition of an authentication mechanism. Essentially, it is the same extensible mechanism provided by OSPF. Currently, only a plain-text password is defined for authentication. However, more sophisticated authentication schemes can easily be incorporated as they are defined.2.5 Multicasting RIP-2 packets may be multicast instead of being broadcast. The use of an IP multicast address reduces the load on hosts which do not support routing protocols. It also allows RIP-2 routers to share information which RIP-1 routers cannot hear. This is useful since a RIP-1 router may misinterpret route information because it cannot apply the supplied subnet mask.3. RIP-2 MIB The MIB for RIP-2 allows for monitoring and control of RIP's operation within the router. In addition to global and per-interface counters and controls, there are per-peer counters which provide the status of RIP-2 "neighbors". The MIB was modified to deprecate the domain, which was removed from the protocol. It has also been converted into version 2 format.4. Implementations Currently, there are three complete implementations of RIP-2: GATED, written by Jeffrey Honig at Cornell University; Xylogics's Annex Communication server; and an implementation for NOS, written by Jeff White. The GATED implementation is available by anonymous FTP from gated.cornell.edu as pub/gated/gated-alpha.tar.Z. The implementation for NOS is available by anonymous FTP from ucsd.edu as /hamradio/packet/tcpip/incoming/rip2.zip. Additionally, Midnight Networks has produced a test suite which verifies an implementation's conformance to RFC 1388 implemented over RFC 1058. The author has conducted interoperability testing between the GATED and Xylogics implementations and found no incompatibilities. This testing includes verification of protection provided by the authentication mechanism described in section 2.4.5. Operational experience Xylogics has been running RIP-2 on its production systems for five months. The topology includes seven subnets in a class B address and various, unregistered class C addresses used for dial-up access. Six systems, in conjunction with three routers from other vendors and dozens of host systems, operate on those subnets. The only problem which has appeared is the reaction of some routers to Version 2 RIP packets. Contrary to RFC 1058, these routers discard Version 2 packets rather than ignoring the fields not defined for Version 1.6. References [1] Malkin, G., "RIP Version 2 Protocol Applicability Statement", RFC 1722, Xylogics, Inc., November 1994. [2] Malkin, G., "RIP Version 2 - Carrying Additional Information", RFC 1723, Xylogics, Inc., November 1994. [3] Malkin, G., and F. Baker, "RIP Version 2 MIB Extension", RFC 1724, Xylogics, Inc., Cisco Systems, November 1994.7. Security Considerations Security issues are discussed in sections 2.4 and 4.8. Author's Address Gary Scott Malkin Xylogics, Inc. 53 Third Avenue Burlington, MA 01803 Phone: (617) 272-8140 EMail: gmalkin@Xylogics.COM Previous: RFC 1720 - Internet Official Protocol Standards Next: RFC 1722 - RIP Version 2 Protocol Applicability Statement [ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ] © 2008 FAQS.ORG. All rights reserved. |
|
| |
RIP | Version | 2 | Protocol | Analysis. | G. | Malkin. | November | 1994. |
|
http://www.faqs.org/rfcs/rfc1721.html
RFC 1721 2008 September
dvd rental
dvd
RIP Version 2 Protocol Analysis. G. Malkin. November 1994.
Rules
|
© 2008 Internet Explorer 5+ or Netscape 6+
|
|
Recommended Sites: 1.
Arts -
Business -
Computers -
Games -
Health -
Home -
Kids and Teens -
News -
Recreation -
Reference -
Regional -
Science -
Shopping -
Society -
Sports -
World
Miss Gallery
- Top Anime Hentai
- DVD rental by mail
- Anaheim CA Hotels - Retro Air Jordans - Remortgage - Bad Credit Mortgages - Online Loans
|