draft-ietf-idr-bgp4-cap-neg-04.txt		draft-ietf-idr-bgp4-cap-neg-05.txt
	Network Working Group Ravi Chandra		Network Working Group Ravi Chandra
	Internet Draft Cisco Systems		Internet Draft Siara Systems
	Expiration Date: March 2000 John G. Scudder		Expiration Date: August 2000 John G. Scudder
	Internet Engineering Group, LLC		cisco Systems
	Capabilities Negotiation with BGP-4		Capabilities Negotiation with BGP-4
	draft-ietf-idr-bgp4-cap-neg-04.txt		draft-ietf-idr-bgp4-cap-neg-05.txt
	1. Status of this Memo		1. Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026 except that the right to		all provisions of Section 10 of RFC2026 except that the right to
	produce derivative works is not granted.		produce derivative works is not granted.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	skipping to change at page 3, line 30		skipping to change at page 3, line 30
	of the Capability Value field in octets.		of the Capability Value field in octets.
	Capability Value:		Capability Value:
	Capability Value is a variable length field that is interpreted		Capability Value is a variable length field that is interpreted
	according to the value of the Capability Code field.		according to the value of the Capability Code field.
	A particular capability, as identified by its Capability Code, may		A particular capability, as identified by its Capability Code, may
	occur more than once within the Optional Parameter.		occur more than once within the Optional Parameter.
	This document reserves Capability Codes 128-255 for vendor-specific
	applications.
	This document reserves value 0.
	Capability Codes (other than those reserved for vendor specific use)
	are assigned only by the IETF consensus process and IESG approval.
	5. Extensions to Error Handling		5. Extensions to Error Handling
	This document defines new Error Subcode - Unsupported Capability.		This document defines new Error Subcode - Unsupported Capability.
	The value of this Subcode is 7. The Data field in the NOTIFICATION		The value of this Subcode is 7. The Data field in the NOTIFICATION
	message lists the set of capabilities that cause the speaker to send		message lists the set of capabilities that cause the speaker to send
	the message. Each such capability is encoded the same way as it was		the message. Each such capability is encoded the same way as it was
	encoded in the received OPEN message.		encoded in the received OPEN message.
	6. Security Considerations		6. IANA Considerations
	This extension to BGP does not change the underlying security issues.		As specified in this document, the Capability optional parameter
			contains the Capability Code field. Capability Code value 0 is
			reserved. Capability Code values 1 through 63 are to be assigned by
			IANA using the "IETF Consensus" policy defined in RFC2434. Capability
			Code values 64 through 127 are to be assigned by IANA, using the
			"First Come First Served" policy defined in RFC2434. Capability Code
			values 128 through 255 are vendor-specific, and values in this range
			are not to be assigned by IANA.
	7. Acknowledgements		7. Security Considerations
			This extension to BGP does not change the underlying security issues
			inherent in the existing BGP [Heffernan].
			8. Acknowledgements
	The authors would like to thank members of the IDR Working Group for		The authors would like to thank members of the IDR Working Group for
	their review and comments.		their review and comments.
	8. References		9. References
	[BGP-4] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 (BGP-		[BGP-4] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 (BGP-
	4)", RFC 1771, March 1995.		4)", RFC 1771, March 1995.
	9. Author Information		[Heffernan] Heffernan, A., "Protection of BGP Sessions via the TCP
			MD5 Signature Option", RFC2385, August 1998.
			10. Author Information
	Ravi Chandra		Ravi Chandra
			Siara Systems Incorporated
			1195 Borregas Avenue
			Sunnyvale, CA 94089
			e-mail: rchandra@siara.com
			John G. Scudder
	Cisco Systems, Inc.		Cisco Systems, Inc.
	170 West Tasman Drive		170 West Tasman Drive
	San Jose, CA 95134		San Jose, CA 95134
	e-mail: rchandra@cisco.com		e-mail: jgs@cisco.com
	John G. Scudder
	Internet Engineering Group, LLC
	122 S. Main, Suite 280
	Ann Arbor, MI 48104
	e-mail: jgs@ieng.com
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/