< draft-ietf-isis-3way-04.txt		draft-ietf-isis-3way-05.txt >
	Network Working Group Dave Katz		Network Working Group Dave Katz
	INTERNET DRAFT Juniper Networks, Inc.		INTERNET DRAFT Juniper Networks, Inc.
	Expiration Date: July 2002 Rajesh Saluja		Expiration Date: August 2002 Rajesh Saluja
	Nortel Networks, Inc.		Nortel Networks, Inc.
	January 2002		February 2002
	Three-Way Handshake for IS-IS Point-to-Point Adjacencies		Three-Way Handshake for IS-IS Point-to-Point Adjacencies
	draft-ietf-isis-3way-04.txt		draft-ietf-isis-3way-05.txt
	Status of this Memo		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. Internet-Drafts are working		all provisions of Section 10 of RFC2026. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas,		documents of the Internet Engineering Task Force (IETF), its areas,
	and its working groups. Note that other groups may also distribute		and its working groups. Note that other groups may also distribute
	working documents as Internet-Drafts.		working documents as Internet-Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	skipping to change at page 4, line 39 ¶		skipping to change at page 4, line 39 ¶
	Type = 0xF0 (decimal 240)		Type = 0xF0 (decimal 240)
	Length = 1 to 17 octets		Length = 1 to 17 octets
	Value:		Value:
	Adjacency Three-Way State (one octet):		Adjacency Three-Way State (one octet):
	0 = Up		0 = Up
	1 = Initializing		1 = Initializing
	2 = Down		2 = Down
	Extended Local Circuit ID (four octets)		Extended Local Circuit ID (four octets)
	Neighbor System ID if known (zero to eight octets)		Neighbor System ID if known (zero to eight octets)
	Neighbor Extended Local Circuit ID (four octets, if Neighbor		Neighbor Extended Local Circuit ID if known (four octets)
	System ID is present)
	Any system that supports this mechanism shall include this option in		Any system that supports this mechanism shall include this option in
	its Point-to-Point IIH packets.		its Point-to-Point IIH packets.
	Any system that does not understand this option will ignore it, and		Any system that does not understand this option will ignore it, and
	(of course) will not include it in its own IIH packets.		(of course) will not include it in its own IIH packets.
	Any system that supports this mechanism MUST include Adjacency		Any system that supports this mechanism MUST include Adjacency
	Three-Way State field in this option. The other fields in this option		Three-Way State field in this option. The other fields in this option
	should be included as explained below in section 3.2.		should be included as explained below in section 3.2.
	skipping to change at page 5, line 25 ¶		skipping to change at page 5, line 25 ¶
	Although the extended circuit ID is only used in the context of the		Although the extended circuit ID is only used in the context of the
	three-way handshake, it is worth noting that it effectively protects		three-way handshake, it is worth noting that it effectively protects
	against the unlikely event where a link is moved to another interface		against the unlikely event where a link is moved to another interface
	on a system that has the same local circuit ID, as the received PDUs		on a system that has the same local circuit ID, as the received PDUs
	will be ignored (via the checks defined below) and the existing		will be ignored (via the checks defined below) and the existing
	adjacency will fail.		adjacency will fail.
	Add a clause e) to the end of section 8.2.2 of [1]:		Add a clause e) to the end of section 8.2.2 of [1]:
	Set the state to be reported in the Adjacency Three-Way State field		Set the state to be reported in the Adjacency Three-Way State field
	of the Point-to-Point Three-Way Adjacency option to Down."		of the Point-to-Point Three-Way Adjacency option to Down.
	Add a clause e) to the end of section 8.2.3 of [1]:		Add a clause e) to the end of section 8.2.3 of [1]:
	The IS shall include the Point-to-Point Three-Way Adjacency option		The IS shall include the Point-to-Point Three-Way Adjacency option
	in the transmitted Point-to-Point IIH PDU. The current three-way		in the transmitted Point-to-Point IIH PDU. The current three-way
	state of the adjacency with its neighbor on the link (as defined in		state of the adjacency with its neighbor on the link (as defined in
	new section 8.2.4.1.1) shall be reported in the Adjacency Three-Way		new section 8.2.4.1.1) shall be reported in the Adjacency Three-Way
	State field. If no adjacency exists, the state shall be reported as		State field. If no adjacency exists, the state shall be reported as
	Down.		Down.
	skipping to change at page 7, line 44 ¶		skipping to change at page 7, line 44 ¶
	Protocol for providing the Connectionless-mode Network Service		Protocol for providing the Connectionless-mode Network Service
	(ISO 8473)", ISO/IEC 10589:1992.		(ISO 8473)", ISO/IEC 10589:1992.
	[2] "Netware Link Services Protocol Specification, Version 1.0",		[2] "Netware Link Services Protocol Specification, Version 1.0",
	Novell, Inc., February 1994.		Novell, Inc., February 1994.
	[3] Callon, R., "OSI IS-IS for IP and Dual Environment", RFC 1195,		[3] Callon, R., "OSI IS-IS for IP and Dual Environment", RFC 1195,
	December 1990.		December 1990.
	[4] Tony Przygienda, "Reserved TLV Codepoints in ISIS", Work in		[4] Tony Przygienda, "Reserved TLV Codepoints in ISIS", Work in
	Progress, July 2001		Progress, January 2002
	Acknowledgements		Acknowledgements
	The authors would like to thank Tony Li, Henk Smit, Naiming Shen,		The authors would like to thank Tony Li, Henk Smit, Naiming Shen,
	Dave Ward, Jeff Learman, Les Ginsberg and Philip Christian for their		Dave Ward, Jeff Learman, Les Ginsberg and Philip Christian for their
	contributions to this document.		contributions to this document.
	Author's Addresses:		Author's Addresses:
	Dave Katz		Dave Katz
End of changes. 6 change blocks.
	7 lines changed or deleted		6 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/