draft-ietf-opsec-lla-only-06.txt		draft-ietf-opsec-lla-only-07.txt
	OPsec Working Group M. Behringer		OPsec Working Group M. Behringer
	Internet-Draft E. Vyncke		Internet-Draft E. Vyncke
	Intended status: Informational Cisco		Intended status: Informational Cisco
	Expires: July 10, 2014 January 6, 2014		Expires: August 17, 2014 February 13, 2014
	Using Only Link-Local Addressing Inside an IPv6 Network		Using Only Link-Local Addressing Inside an IPv6 Network
	draft-ietf-opsec-lla-only-06		draft-ietf-opsec-lla-only-07
	Abstract		Abstract
	In an IPv6 network it is possible to use only link-local addresses on		In an IPv6 network it is possible to use only link-local addresses on
	infrastructure links between routers. This document discusses the		infrastructure links between routers. This document discusses the
	advantages and disadvantages of this approach to help the decision		advantages and disadvantages of this approach to help the decision
	process for a given network.		process for a given network.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 33		skipping to change at page 1, line 33
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 July 10, 2014.		This Internet-Draft will expire on August 17, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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 8, line 17		skipping to change at page 8, line 17
	The authors would like to thank Salman Asadullah, Brian Carpenter,		The authors would like to thank Salman Asadullah, Brian Carpenter,
	Bill Cerveny, Benoit Claise, Rama Darbha, Simon Eng, Wes George,		Bill Cerveny, Benoit Claise, Rama Darbha, Simon Eng, Wes George,
	Fernando Gont, Jen Linkova, Harald Michl, Janos Mohacsi, Ivan		Fernando Gont, Jen Linkova, Harald Michl, Janos Mohacsi, Ivan
	Pepelnjak, and Alvaro Retana for their useful comments about this		Pepelnjak, and Alvaro Retana for their useful comments about this
	work.		work.
	6. Informative References		6. Informative References
	[I-D.ietf-opsec-bgp-security]		[I-D.ietf-opsec-bgp-security]
	Durand, J., Pepelnjak, I., and G. Doering, "BGP operations		Durand, J., Pepelnjak, I., and G. Doering, "BGP operations
	and security", draft-ietf-opsec-bgp-security-01 (work in		and security", draft-ietf-opsec-bgp-security-02 (work in
	progress), July 2013.		progress), January 2014.
	[IS-IS] ISO/IEC 10589, , "Intermediate System to Intermediate		[IS-IS] ISO/IEC 10589, , "Intermediate System to Intermediate
	System Intra-Domain Routing Exchange Protocol for use in		System Intra-Domain Routing Exchange Protocol for use in
	Conjunction with the Protocol for Providing the		Conjunction with the Protocol for Providing the
	Connectionless-mode Network Service (ISO 8473)", June		Connectionless-mode Network Service (ISO 8473)", June
	1992.		1992.
	[RFC0495] McKenzie, A., "Telnet Protocol specifications", RFC 495,		[RFC0495] McKenzie, A., "Telnet Protocol specifications", RFC 495,
	May 1973.		May 1973.
	[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,
	RFC 792, September 1981.
	[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,		[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
	"Simple Network Management Protocol (SNMP)", STD 15, RFC		"Simple Network Management Protocol (SNMP)", STD 15, RFC
	1157, May 1990.		1157, May 1990.
	[RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080,		[RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080,
	January 1997.		January 1997.
	[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,		[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
	and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP		and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
	Tunnels", RFC 3209, December 2001.		Tunnels", RFC 3209, December 2001.
End of changes. 5 change blocks.
	8 lines changed or deleted		5 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/