draft-ietf-grow-mrt-12.txt		draft-ietf-grow-mrt-13.txt
	Network Working Group L. Blunk		Network Working Group L. Blunk
	Internet-Draft M. Karir		Internet-Draft M. Karir
	Intended status: Standards Track Merit Network		Intended status: Standards Track Merit Network
	Expires: March 13, 2011 C. Labovitz		Expires: March 13, 2011 C. Labovitz
	Arbor Networks		Arbor Networks
	September 9, 2010		September 9, 2010
	MRT routing information export format		MRT routing information export format
	draft-ietf-grow-mrt-12.txt		draft-ietf-grow-mrt-13.txt
	Abstract		Abstract
	This document describes the MRT format for routing information		This document describes the MRT format for routing information
	export. This format was developed in concert with the Multi-threaded		export. This format was developed in concert with the Multi-threaded
	Routing Toolkit (MRT) from whence the format takes it name. The		Routing Toolkit (MRT) from whence the format takes it name. The
	format can be used to export routing protocol messages, state		format can be used to export routing protocol messages, state
	changes, and routing information base contents.		changes, and routing information base contents.
	Status of this Memo		Status of this Memo
	skipping to change at page 24, line 12		skipping to change at page 24, line 12
	create additional security risks, since the fields are not used to		create additional security risks, since the fields are not used to
	induce any particular behavior by the recipient application.		induce any particular behavior by the recipient application.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and		[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
	dual environments", RFC 1195, December 1990.		dual environments", RFC 1195, December 1990.
	[RFC1723] Malkin, G., "RIP Version 2 - Carrying Additional
	Information", STD 56, RFC 1723, November 1994.
	[RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080,		[RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080,
	January 1997.		January 1997.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.		[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
			[RFC2453] Malkin, G., "RIP Version 2", STD 56, RFC 2453,
			November 1998.
	[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway		[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
	Protocol 4 (BGP-4)", RFC 4271, January 2006.		Protocol 4 (BGP-4)", RFC 4271, January 2006.
	[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,		[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
	"Multiprotocol Extensions for BGP-4", RFC 4760,		"Multiprotocol Extensions for BGP-4", RFC 4760,
	January 2007.		January 2007.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	May 2008.		May 2008.
	skipping to change at page 28, line 30		skipping to change at page 28, line 30
	A.2.1.8. BGP_KEEPALIVE Subtype		A.2.1.8. BGP_KEEPALIVE Subtype
	The BGP_KEEPALIVE Subtype is used to encode BGP KEEPALIVE messages.		The BGP_KEEPALIVE Subtype is used to encode BGP KEEPALIVE messages.
	The format of the MRT Message field for this Subtype is the same as		The format of the MRT Message field for this Subtype is the same as
	the BGP_UPDATE, however, the last field contains no information.		the BGP_UPDATE, however, the last field contains no information.
	A.2.2. RIP Type		A.2.2. RIP Type
	The RIP Type is used to export RIP protocol packets as defined in RFC		The RIP Type is used to export RIP protocol packets as defined in RFC
	1723 [RFC1723]. The Subtype field is currently reserved for this		2453 [RFC2453]. The Subtype field is currently reserved for this
	Type and SHOULD be set to 0.		Type and SHOULD be set to 0.
	The format of the MRT Message field for the RIP Type is as follows:		The format of the MRT Message field for the RIP Type is as follows:
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Peer IP address |		| Peer IP address |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Local IP address |		| Local IP address |
End of changes. 4 change blocks.
	5 lines changed or deleted		5 lines changed or added
This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/