draft-ietf-curdle-rc4-die-die-die-09.txt		draft-ietf-curdle-rc4-die-die-die-10.txt
	Internet Engineering Task Force L. Camara		Internet Engineering Task Force L. Camara
	Internet-Draft		Internet-Draft
	Obsoletes: 4325 (if approved) L. Velvindron		Obsoletes: 4325 (if approved) L. Velvindron
	Updates: 4253 (if approved) September 3, 2018		Updates: 4253 (if approved) cyberstorm.mu
	Intended status: Best Current Practice		Intended status: Best Current Practice September 24, 2018
	Expires: March 7, 2019		Expires: March 28, 2019
	Deprecating RC4 in Secure Shell (SSH)		Deprecating RC4 in Secure Shell (SSH)
	draft-ietf-curdle-rc4-die-die-die-09		draft-ietf-curdle-rc4-die-die-die-10
	Abstract		Abstract
	This document deprecates RC4 in Secure Shell (SSH). Therefore, this		This document deprecates RC4 in Secure Shell (SSH). Therefore, this
	document updates [RFC4253], and formally obsoletes and moves to		document updates [RFC4253], and formally obsoletes and moves to
	Historic [RFC4345].		Historic [RFC4345].
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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."
	This Internet-Draft will expire on March 7, 2019.		This Internet-Draft will expire on March 28, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 4, line 7 ¶		skipping to change at page 4, line 7 ¶
	All drafts are required to have an IANA considerations section (see		All drafts are required to have an IANA considerations section (see
	Guidelines for Writing an IANA Considerations Section in RFCs		Guidelines for Writing an IANA Considerations Section in RFCs
	[RFC5226] for a guide). If the draft does not require IANA to do		[RFC5226] for a guide). If the draft does not require IANA to do
	anything, the section contains an explicit statement that this is the		anything, the section contains an explicit statement that this is the
	case (as above). If there are no requirements for IANA, the section		case (as above). If there are no requirements for IANA, the section
	will be removed during conversion into an RFC by the RFC Editor.		will be removed during conversion into an RFC by the RFC Editor.
	4. Acknowledgements		4. Acknowledgements
	The authors would like to thank Daniel Migault		The authors would like to thank Daniel Migault and Rich Salz.
	5. Security Considerations		5. Security Considerations
	This document only prohibits the use of RC4 in SSH, and introduces no		This document only prohibits the use of RC4 in SSH, and introduces no
	new security considerations.		new security considerations.
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	skipping to change at page 5, line 12 ¶		skipping to change at page 5, line 12 ¶
	DOI 10.17487/RFC7465, February 2015,		DOI 10.17487/RFC7465, February 2015,
	<https://www.rfc-editor.org/info/rfc7465>.		<https://www.rfc-editor.org/info/rfc7465>.
	Authors' Addresses		Authors' Addresses
	Luis Camara		Luis Camara
	Email: luis.camara@live.com.pt		Email: luis.camara@live.com.pt
	Loganaden Velvindron		Loganaden Velvindron
			cyberstorm.mu
	Mauritius		Mauritius
	Email: loganaden@gmail.com		Email: loganaden@gmail.com
End of changes. 5 change blocks.
	6 lines changed or deleted		7 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/