< draft-bjh21-ssh-transport-extension-01.txt		draft-bjh21-ssh-transport-extension-02.txt >
	Network Working Group B. Harris		Network Working Group B. Harris
	Internet-Draft February 21, 2007		Internet-Draft February 2007
	Intended status: Standards Track		Intended status: Standards Track
	Expires: August 25, 2007		Expires: August 5, 2007
	Extended packet types for the Secure Shell (SSH) Transport Layer		Extended packet types for the Secure Shell (SSH) Transport Layer
	Protocol		Protocol
	draft-bjh21-ssh-transport-extension-01		draft-bjh21-ssh-transport-extension-02
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	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
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on August 25, 2007.		This Internet-Draft will expire on August 5, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	This memo introduces a new message type into the Secure Shell (SSH)		This memo introduces a new message type into the Secure Shell (SSH)
	Transport Layer Protocol whose meaning and contents are defined by a		Transport Layer Protocol whose meaning and contents are defined by a
	name at the start of the message, thus allowing for further		name at the start of the message, thus allowing for further
	skipping to change at page 3, line 12 ¶		skipping to change at page 3, line 12 ¶
	The meaning of the message and the contents of 'extension-specific		The meaning of the message and the contents of 'extension-specific
	fields' are determined by 'extension name', which follows the		fields' are determined by 'extension name', which follows the
	conventions described in section 4.6.1 of [RFC4250].		conventions described in section 4.6.1 of [RFC4250].
	If an implementation receives an SSH_MSG_TRANSPORT_EXTENSION whose		If an implementation receives an SSH_MSG_TRANSPORT_EXTENSION whose
	'extension name' it does not recognise, it MUST treat it as if the		'extension name' it does not recognise, it MUST treat it as if the
	message number were unrecognised and return SSH_MSG_UNIMPLEMENTED as		message number were unrecognised and return SSH_MSG_UNIMPLEMENTED as
	specified in section 11.4 of [RFC4253].		specified in section 11.4 of [RFC4253].
	4. Security Considerations		4. Message Number
			The following message number is defined:
			SSH_MSG_TRANSPORT_EXTENSION XXX
			5. Security Considerations
	The security considerations in [RFC4251] apply.		The security considerations in [RFC4251] apply.
	5. IANA Considerations		6. IANA Considerations
	IANA should assign a Message Number in the range 1 to 19 for		IANA should assign a Message Number in the range 1 to 19 for
	SSH_MSG_TRANSPORT_EXTENSION in accordance with section 4.1 of		SSH_MSG_TRANSPORT_EXTENSION in accordance with section 4.1 of
	[RFC4250].		[RFC4250].
	IANA should maintain a register of Transport Layer Extension Packet		IANA should maintain a register of Transport Layer Extension Packet
	Names following the conventions and instructions in section 4.6 of		Names following the conventions and instructions in section 4.6 of
	[RFC4250].		[RFC4250].
	6. Normative References		7. Normative References
	[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.
	[RFC4250] Lehtinen, S. and C. Lonvick, "The Secure Shell (SSH)		[RFC4250] Lehtinen, S. and C. Lonvick, "The Secure Shell (SSH)
	Protocol Assigned Numbers", RFC 4250, January 2006.		Protocol Assigned Numbers", RFC 4250, January 2006.
	[RFC4251] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)		[RFC4251] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)
	Protocol Architecture", RFC 4251, January 2006.		Protocol Architecture", RFC 4251, January 2006.
End of changes. 7 change blocks.
	7 lines changed or deleted		13 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/