As per Relevance of the word research, we have this rfc below:
Network Working Group D.
Request for Comments: 1397 Bolt Beranek and Newman, Inc
January 1993
Default Route Advertisement
BGP2 And BGP3 Versions Of The Border Gateway
Status of this
This RFC specifies an IAB standards track protocol for the
community, and requests discussion and suggestions for improvements
Please refer to the current edition of the "IAB Official
Standards" for the standardization state and status of this protocol
Distribution of this memo is unlimited
This document specifies the recommendation of the BGP Working
on default route advertisement support in BGP2 [1] and BGP3 [2]
versions of the Border Gateway Protocol
This recommendation only applies to BGP2 and BGP3 versions of
Border Gateway Protocol since starting with the BGP4 [3] version
default route advertisement capability is built in the protocol
1.
The purpose of the default route advertisement capability is
advertise the IP address of a border gateway which can be used as
default next hop to destinations that are not listed explicitly
the BGP peer's routing table
This capability will allow routers, that are unable to maintain
complete routing table (e.g., due to its size) to learn a
gateway that is ready to handle the default traffic. Also,
contrast to static defaults, if there is more than one
gateway, this would make it possible for a BGP speaker to express
preference for one over the other. It also reduces the need
configure default routes in routers
2. Default Route
A default route is advertised in an UPDATE message that
reachability information for network 0.0.0.0. A Network field
such an UPDATE message must contain the IP address 0.0.0.0 as
indication that it carries a default route. The NEXT_HOP
attribute of such a message provides the IP address of a
Haskin [Page 1]
RFC 1397 Default Routes in Old BGPs January 1993
gateway that can be used as a default next hop to destinations
are not listed in the BGP peer's routing table. The value of
ORIGIN attribute should be 2 (INCOMPLETE). The AS_PATH
should be constructed according to the same rules that apply to
conventional network advertisement
If multiple default routes are advertised by a BGP speaker,
INTER-AS-METRIC path attribute can be included in the
UPDATE messages to express preference levels for entry points to
same AS
The UNREACHABLE path attribute is used to indicate that a
advertised default route has become unreachable
UPDATE messages containing the default route advertisements should
handled according to the rules that apply to all other
messages. If multiple default route are acquired by a BGP speaker,
route is selected according to the local policies adopted by this
speaker
[1] Lougheed, K., and Y. Rekhter, "A Border Gateway Protocol (BGP)",
RFC 1163, cisco Systems, T.J. Watson Research Center, IBM Corp.,
June 1990.
[2] Lougheed, K., and Y. Rekhter, "A Border Gateway Protocol 3 (BGP
3)", RFC 1267, cisco Systems, T.J. Watson Research Center,
Corp., October 1991.
[3] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 (BGP-4)",
Work in Progress, T.J. Watson Research Center, IBM Corp.,
Systems, December 1992.
Security
Security issues are not discussed in this memo
Author's
Dimitry
Bolt, Beranek &
150 Cambridge Park
Cambridge, MA 02140
Phone: 617-873-8609
Email: dhaskin@bbn.
Haskin [Page 2]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
