draft-ietf-idr-bgp4-multiprotocol-01.txt		rfc2283.txt
	Network Working Group Tony Bates		Network Working Group T. Bates
	Internet Draft Cisco Systems		Request for Comments: 2283 Cisco Systems
	Expiration Date: March 1998 Ravi Chandra		Category: Standards Track R. Chandra
	Cisco Systems		Cisco Systems
	Dave Katz		D. Katz
	Juniper Networks		Juniper Networks
	Yakov Rekhter		Y. Rekhter
	Cisco Systems		Cisco Systems
			February 1998
	Multiprotocol Extensions for BGP-4		Multiprotocol Extensions for BGP-4
	draft-ietf-idr-bgp4-multiprotocol-01.txt		Status of this Memo
	1. Status of this Memo
	This document is an Internet-Draft. Internet-Drafts are working		This document specifies an Internet standards track protocol for the
	documents of the Internet Engineering Task Force (IETF), its areas,		Internet community, and requests discussion and suggestions for
	and its working groups. Note that other groups may also distribute		improvements. Please refer to the current edition of the "Internet
	working documents as Internet-Drafts.		Official Protocol Standards" (STD 1) for the standardization state
			and status of this protocol. Distribution of this memo is unlimited.
	Internet-Drafts are draft documents valid for a maximum of six months		Copyright Notice
	and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as ``work in progress.''
	To learn the current status of any Internet-Draft, please check the		Copyright (C) The Internet Society (1998). All Rights Reserved.
	``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
	Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
	munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
	ftp.isi.edu (US West Coast).
	2. Abstract		2. Abstract
	Currently BGP-4 [BGP-4] is capable of carrying routing information		Currently BGP-4 [BGP-4] is capable of carrying routing information
	only for IPv4 [IPv4]. This document defines extensions to BGP-4 to		only for IPv4 [IPv4]. This document defines extensions to BGP-4 to
	enable it to carry routing information for multiple Network Layer		enable it to carry routing information for multiple Network Layer
	protocols (e.g., IPv6, IPX, etc...). The extensions are backward		protocols (e.g., IPv6, IPX, etc...). The extensions are backward
	compatible - a router that supports the extensions can interoperate		compatible - a router that supports the extensions can interoperate
	with a router that doesn't support the extensions.		with a router that doesn't support the extensions.
	skipping to change at page 7, line 42		skipping to change at page 7, line 18
	trailing bits to make the end of the field fall on an octet		trailing bits to make the end of the field fall on an octet
	boundary. Note that the value of trailing bits is irrelevant.		boundary. Note that the value of trailing bits is irrelevant.
	7. Subsequent Address Family Identifier		7. Subsequent Address Family Identifier
	This document defines the following values for the Subsequent Address		This document defines the following values for the Subsequent Address
	Family Identifier field carried in the MP_REACH_NLRI and		Family Identifier field carried in the MP_REACH_NLRI and
	MP_UNREACH_NLRI attributes:		MP_UNREACH_NLRI attributes:
	1 - Network Layer Reachability Information used for unicast		1 - Network Layer Reachability Information used for unicast
	forwarding		forwarding
	2 - Network Layer Reachability Information used for multicast		2 - Network Layer Reachability Information used for multicast
	forwarding		forwarding
	3 - Network Layer Reachability Information used for both unicast		3 - Network Layer Reachability Information used for both unicast
	and multicast forwarding		and multicast forwarding
	This document reserves values 128-255 for vendor-specific		This document reserves values 128-255 for vendor-specific
	applications.		applications.
	This document reserves value 0.		This document reserves value 0.
			Subsequent Address Family Identifiers (other than those reserved for
			vendor specific use) are assigned only by the IETF consensus process
			and IESG approval.
	8. Security Considerations		8. Security Considerations
	Security issues are not discussed in this document.		This extension to BGP does not change the underlying security issues.
	9. Acknowledgements		9. Acknowledgements
	To be supplied.		The authors would like to thank members of the IDR Working Group for
			their review and comments.
	10. References		10. References
	[BGP-4]		[BGP-4] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4
			(BGP-4)", RFC 1771, March 1995.
	[IPv4]
	[IPv6]		[IPv4] Postel, J., "Internet Protocol", STD 5, RFC 791,
			September 1981.
	[RFC1700]		[RFC1700] Reynolds, J., and J. Postel, "Assigned Numbers," STD 2,
			RFC 1700, October 1994. (see also
			http://www.iana.org/iana/assignments.html)
	11. Author Information		11. Author Information
	Tony Bates		Tony Bates
	Cisco Systems, Inc.		Cisco Systems, Inc.
	170 West Tasman Drive		170 West Tasman Drive
	San Jose, CA 95134		San Jose, CA 95134
	email: tbates@cisco.com
			EMail: tbates@cisco.com
	Ravi Chandra		Ravi Chandra
	Cisco Systems, Inc.		Cisco Systems, Inc.
	170 West Tasman Drive		170 West Tasman Drive
	San Jose, CA 95134		San Jose, CA 95134
	email: rchandra@cisco.com
			EMail: rchandra@cisco.com
	Dave Katz		Dave Katz
	Juniper Networks, Inc.		Juniper Networks, Inc.
	3260 Jay St.		3260 Jay St.
	Santa Clara, CA 95054		Santa Clara, CA 95054
	email: dkatz@jnx.com
			EMail: dkatz@jnx.com
	Yakov Rekhter		Yakov Rekhter
	Cisco Systems, Inc.		Cisco Systems, Inc.
	170 West Tasman Drive		170 West Tasman Drive
	San Jose, CA 95134		San Jose, CA 95134
	email: yakov@cisco.com
			EMail: yakov@cisco.com
			12. Full Copyright Statement
			Copyright (C) The Internet Society (1998). All Rights Reserved.
			This document and translations of it may be copied and furnished to
			others, and derivative works that comment on or otherwise explain it
			or assist in its implementation may be prepared, copied, published
			and distributed, in whole or in part, without restriction of any
			kind, provided that the above copyright notice and this paragraph are
			included on all such copies and derivative works. However, this
			document itself may not be modified in any way, such as by removing
			the copyright notice or references to the Internet Society or other
			Internet organizations, except as needed for the purpose of
			developing Internet standards in which case the procedures for
			copyrights defined in the Internet Standards process must be
			followed, or as required to translate it into languages other than
			English.
			The limited permissions granted above are perpetual and will not be
			revoked by the Internet Society or its successors or assigns.
			This document and the information contained herein is provided on an
			"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
			TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
			BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
			HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
			MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
End of changes. 19 change blocks.
	38 lines changed or deleted		41 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/