< draft-bryant-ipfrr-tunnels-01.txt		draft-bryant-ipfrr-tunnels-02.txt >
	Network Working Group S. Bryant		Network Working Group S. Bryant
	Internet Draft C. Filsfils		Internet Draft C. Filsfils
	Expiration Date: Apr 2005 S. Previdi		Expiration Date: Oct 2005 S. Previdi
	M. Shand		M. Shand
	Cisco Systems		Cisco Systems
	Oct 2004		Apr 2005
	IP Fast Reroute using tunnels		IP Fast Reroute using tunnels
	draft-bryant-ipfrr-tunnels-01.txt		draft-bryant-ipfrr-tunnels-02.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, we certify that any applicable		By submitting this Internet-Draft, each author represents that any
	patent or other IPR claims of which we are aware have been		applicable patent or other IPR claims of which he or she is aware
	disclosed, or will be disclosed, and any of which we become aware		have been or will be disclosed, and any of which he or she becomes
	will be disclosed, in accordance with RFC 3668.		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
	other groups may also distribute working documents as		other groups may also distribute working documents as Internet-
	Internet-Drafts.		Drafts.
	Internet-Drafts are draft documents valid for a maximum of six		Internet-Drafts are draft documents valid for a maximum of six
	months and may be updated, replaced, or obsoleted by other		months and may be updated, replaced, or obsoleted by other
	documents at any time. It is inappropriate to use Internet-Drafts		documents at any time. It is inappropriate to use Internet-Drafts
	as reference material or to cite them other than a "work in		as reference material or to cite them other than as "work in
	progress."		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/1id-abstracts.html		http://www.ietf.org/1id-abstracts.html
	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
	Abstract		Abstract
	skipping to change at page 2, line 48 ¶		skipping to change at page 2, line 48 ¶
	4.6.3. A LAN between E and its neighbors........................20		4.6.3. A LAN between E and its neighbors........................20
	4.6.4. The LAN is a Transit Subnet..............................21		4.6.4. The LAN is a Transit Subnet..............................21
	5. Failure Detection and Repair Path Activation.....................21		5. Failure Detection and Repair Path Activation.....................21
	5.1. Failure Detection............................................21		5.1. Failure Detection............................................21
	5.2. Repair Path Activation.......................................21		5.2. Repair Path Activation.......................................21
	5.3. Node Failure Detection Mechanism.............................21		5.3. Node Failure Detection Mechanism.............................21
	6. Loop Free Transition.............................................22		6. Loop Free Transition.............................................22
	7. IPFRR Capability.................................................22		7. IPFRR Capability.................................................22
	8. Enhancements to routing protocols................................23		8. Enhancements to routing protocols................................23
	9. IANA considerations..............................................23		9. IANA considerations..............................................23
	10. Security Considerations.........................................23		10. Security Considerations...............Error! Bookmark not defined.
	Terminology		Terminology
	This draft uses the terms defined in [FRMWK]. This section defines		This draft uses the terms defined in [FRMWK]. This section defines
	additional words, acronyms, and actions used in this draft.		additional words, acronyms, and actions used in this draft.
	Directed The ability of the repairing router (S) to		Directed The ability of the repairing router (S) to
	forwarding specify the next hop (G) on exit from a		forwarding specify the next hop (G) on exit from a
	tunnel end-point (F)		tunnel end-point (F)
	skipping to change at page 23, line 36 ¶		skipping to change at page 23, line 36 ¶
	o The ability to signal transition completion status to		o The ability to signal transition completion status to
	neighbors.		neighbors.
	o The ability to advertise that a link is protected.		o The ability to advertise that a link is protected.
	Capability advertisement should make use of existing capability		Capability advertisement should make use of existing capability
	mechanisms in the routing protocols. The exact set of enhancements		mechanisms in the routing protocols. The exact set of enhancements
	will depend on specific IPFRR design choices.		will depend on specific IPFRR design choices.
	9. IANA considerations		9. IANA Considerations
	There are no IANA considerations that arise from this architectural		There are no IANA considerations that arise from this architectural
	description of IPFRR. However there will be changes to the IGPs to		description of IPFRR. However there will be changes to the IGPs to
	support IPFRR in which there will be IANA considerations.		support IPFRR in which there will be IANA considerations.
	10. Security Considerations		10. Security Considerations
	Changes to the IGPs to support IPFRR do not introduce any		Changes to the IGPs to support IPFRR do not introduce any
	additional security risks.		additional security risks.
End of changes. 8 change blocks.
	12 lines changed or deleted		12 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/