< draft-ietf-secsh-publickeyfile-12.txt		draft-ietf-secsh-publickeyfile-13.txt >
	Secure Shell Working Group J. Galbraith		Secure Shell Working Group J. Galbraith
	Internet-Draft VanDyke Software		Internet-Draft VanDyke Software
	Expires: September 2, 2006 R. Thayer		Expires: September 23, 2006 R. Thayer
	The Tillerman Group		The Tillerman Group
	March 1, 2006		March 22, 2006
	SSH Public Key File Format		SSH Public Key File Format
	draft-ietf-secsh-publickeyfile-12.txt		draft-ietf-secsh-publickeyfile-13.txt
	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 September 2, 2006.		This Internet-Draft will expire on September 23, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This document formally documents an existing public key file format		This document formally documents an existing public key file format
	in use for exchanging public keys between different SSH		in use for exchanging public keys between different SSH
	implementations.		implementations.
	skipping to change at page 10, line 11 ¶		skipping to change at page 10, line 11 ¶
	by colons.		by colons.
	For example: "c1:b1:30:29:d7:b8:de:6c:97:77:10:d7:46:41:63:87"		For example: "c1:b1:30:29:d7:b8:de:6c:97:77:10:d7:46:41:63:87"
	5. IANA Considerations		5. IANA Considerations
	Section 3.3 defines a new namespace of "Header-tags". These are US-		Section 3.3 defines a new namespace of "Header-tags". These are US-
	ASCII strings of maximum length 64 characters, and are case-		ASCII strings of maximum length 64 characters, and are case-
	insensitive.		insensitive.
	The following header-tags are defined by this document:		IANA is requested to create and maintain a registry of these header-
			tags. The registry will map each header-tag to a reference defining
			the header.
	subject		The initial contents of the registry are as follows:
	comment		subject defined in Section 3.3.1
	In addition, all header-tags beginning with "x-" are reserved for		comment defined in Section 3.3.2
	Private Use, as defined in [RFC2434].
	Further allocations are to be made by IETF Consensus, as defined in		Header-tags beginning with "x-" are reserved for Private Use, as
			defined in [RFC2434].
			All other allocations are to be made by IETF Consensus, as defined in
	[RFC2434].		[RFC2434].
	6. Security Considerations		6. Security Considerations
	The file format described by this document provides no mechanism to		The file format described by this document provides no mechanism to
	verify the integrity or otherwise detect tampering with the data		verify the integrity or otherwise detect tampering with the data
	stored in such files. Given the potential of an adversarial		stored in such files. Given the potential of an adversarial
	tampering with this data, system-specific measures (e.g. Access		tampering with this data, system-specific measures (e.g. Access
	Control Lists, UNIX permissions, other Discretionary and/or Mandatory		Control Lists, UNIX permissions, other Discretionary and/or Mandatory
	Access Controls) SHOULD be used to protect these files. Also, if the		Access Controls) SHOULD be used to protect these files. Also, if the
	skipping to change at page 12, line 25 ¶		skipping to change at page 12, line 25 ¶
	[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.
	[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO		[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
	10646", STD 63, RFC 3629, November 2003.		10646", STD 63, RFC 3629, November 2003.
	[RFC4253] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)		[RFC4253] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)
	Transport Layer Protocol", RFC 4253, January 2006.		Transport Layer Protocol", RFC 4253, January 2006.
			[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
			IANA Considerations Section in RFCs", BCP 26, RFC 2434,
			October 1998.
	7.2. Informative References		7.2. Informative References
	[RFC1421] Linn, J., "Privacy Enhancement for Internet Electronic		[RFC1421] Linn, J., "Privacy Enhancement for Internet Electronic
	Mail: Part I: Message Encryption and Authentication		Mail: Part I: Message Encryption and Authentication
	Procedures", RFC 1421, February 1993.		Procedures", RFC 1421, February 1993.
	[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 2434,
	October 1998.
	[RFC2440] Callas, J., Donnerhacke, L., Finney, H., and R. Thayer,		[RFC2440] Callas, J., Donnerhacke, L., Finney, H., and R. Thayer,
	"OpenPGP Message Format", RFC 2440, November 1998.		"OpenPGP Message Format", RFC 2440, November 1998.
	Authors' Addresses		Authors' Addresses
	Joseph Galbraith		Joseph Galbraith
	VanDyke Software		VanDyke Software
	4848 Tramway Ridge Blvd		4848 Tramway Ridge Blvd
	Suite 101		Suite 101
	Albuquerque, NM 87111		Albuquerque, NM 87111
End of changes. 11 change blocks.
	14 lines changed or deleted		18 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/