< draft-ietf-sigtran-sctp-12.txt		draft-ietf-sigtran-sctp-13.txt >
	skipping to change at page 1, line 21 ¶		skipping to change at page 1, line 21 ¶
	Nortel Networks		Nortel Networks
	I. Rytina		I. Rytina
	Ericsson		Ericsson
	M. Kalla		M. Kalla
	Telcordia		Telcordia
	L. Zhang		L. Zhang
	UCLA		UCLA
	V. Paxson		V. Paxson
	ACIRI		ACIRI
	expires in six months July 10,2000		expires in six months July 11,2000
	Stream Control Transmission Protocol		Stream Control Transmission Protocol
	<draft-ietf-sigtran-sctp-12.txt>		<draft-ietf-sigtran-sctp-13.txt>
	Status of This Memo		Status of This Memo
	This document is an Internet-Draft and is in full conformance with all		This document is an Internet-Draft and is in full conformance with all
	provisions of Section 10 of [RFC2026]. Internet-Drafts are working		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.
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	skipping to change at page 53, line 28 ¶		skipping to change at page 53, line 28 ¶
	The endpoint also MUST transmit an ERROR chunk with a "Stale Cookie"		The endpoint also MUST transmit an ERROR chunk with a "Stale Cookie"
	error cause to the peer endpoint (this is case C or D above).		error cause to the peer endpoint (this is case C or D above).
	If both Verification Tags in the State Cookie match the Verification		If both Verification Tags in the State Cookie match the Verification
	Tags of the current association, consider the State Cookie valid		Tags of the current association, consider the State Cookie valid
	(this is case E) even if the lifespan is exceeded.		(this is case E) even if the lifespan is exceeded.
	4) If the State Cookie proves to be valid, unpack the TCB into a		4) If the State Cookie proves to be valid, unpack the TCB into a
	temporary TCB.		temporary TCB.
	5) If the Verification Tags in the Temporary TCB match the		5) Refer to Table 2 to determine the correct action to be taken.
	Verification Tags in the existing TCB, the State Cookie is a
	duplicate cookie. A COOKIE ACK should be sent to the peer
	endpoint but no update should be made to the existing
	TCB (only the local Verification Tag needs to be compared if
	the peer's Verification Tag is not yet available).
	The endpoint doesn't leave the current state and all timers
	remain running.
	6) If either of the Verification Tags do NOT match, refer to the following
	table to determine the correct action to be taken.
	+------------+------------+---------------+--------------+-------------+		+------------+------------+---------------+--------------+-------------+
	| Local Tag | Peers Tag | Local-Tie-Tag | Peers-Tie-Tag| Action/ |		| Local Tag | Peers Tag | Local-Tie-Tag | Peers-Tie-Tag| Action/ |
	| | | | | Description |		| | | | | Description |
	+------------+------------+---------------+--------------+-------------+		+------------+------------+---------------+--------------+-------------+
	| X | X | M | M | (A) |		| X | X | M | M | (A) |
	+------------+------------+---------------+--------------+-------------+		+------------+------------+---------------+--------------+-------------+
	| M | A | A | A | (B) |		| M | A | A | A | (B) |
	+------------+------------+---------------+--------------+-------------+		+------------+------------+---------------+--------------+-------------+
	| X | M | 0 | 0 | (C) |		| X | M | 0 | 0 | (C) |
	skipping to change at page 54, line 8 ¶		skipping to change at page 54, line 8 ¶
	| M | M | A | A | (D) |		| M | M | A | A | (D) |
	+======================================================================+		+======================================================================+
	| Table 2: Handling of a Cookie when a TCB exists |		| Table 2: Handling of a Cookie when a TCB exists |
	+======================================================================+		+======================================================================+
	Legend:		Legend:
	X - Tag does not match the existing TCB		X - Tag does not match the existing TCB
	M - Tag matches the existing TCB.		M - Tag matches the existing TCB.
	0 - No Tie-Tag in Cookie (unknown).		0 - No Tie-Tag in Cookie (unknown).
	A - All cases match, no-match or unknown.		A - All cases, i.e. M, X or 0.
	Note: For any case not shown in Table 2, the cookie should be		Note: For any case not shown in Table 2, the cookie should be
	silently discarded.		silently discarded.
	Action		Action
	(A)In this case, the peer may have restarted. When the endpoint		(A)In this case, the peer may have restarted. When the endpoint
	recognizes this potential 'restart', the existing session is		recognizes this potential 'restart', the existing session is
	treated the same as if it received an ABORT followed by a new		treated the same as if it received an ABORT followed by a new
	Cookie Echo with the following exceptions:		Cookie Echo with the following exceptions:
End of changes. 4 change blocks.
	15 lines changed or deleted		4 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/