< draft-sb-nvo3-sdn-federation-01.txt		draft-sb-nvo3-sdn-federation-02.txt >
	Internet Engineering Task Force Florin Balus		Internet Engineering Task Force Florin Balus
	Internet Draft Dimitri Stiliadis		Internet Draft Dimitri Stiliadis
	Intended status: standards track Nuage Networks		Intended status: standards track Nuage Networks
	Expires: April 2013		Expires: May 2014
	Nabil Bitar		Nabil Bitar
	Wim Henderickx Verizon		Wim Henderickx Verizon
	Marc Lasserre		Marc Lasserre
	Alcatel-Lucent Kenichi Ogaki		Alcatel-Lucent Kenichi Ogaki
	KDDI		KDDI
	October 22, 2012		November 22, 2013
	Federated SDN-based Controllers for NVO3		Federated SDN-based Controllers for NVO3
	draft-sb-nvo3-sdn-federation-01.txt		draft-sb-nvo3-sdn-federation-02.txt
	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
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and 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 Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	months and may be updated, replaced, or obsoleted by other documents		months and may be updated, replaced, or obsoleted by other documents
	at any time. It is inappropriate to use Internet-Drafts as		at any time. It is inappropriate to use Internet-Drafts as
	reference material or to cite them other than as "work in progress."		reference 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 April 22, 2013.		This Internet-Draft will expire on April 21, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2013 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
	carefully, as they describe your rights and restrictions with		carefully, as they describe your rights and restrictions with
	respect to this document.		respect to this document.
	Abstract		Abstract
	skipping to change at page 7, line 47 ¶		skipping to change at page 7, line 47 ¶
	shutdown is not known though, and it will depend on the		shutdown is not known though, and it will depend on the
	capabilities of the TS. Traffic from/to the TS must be		capabilities of the TS. Traffic from/to the TS must be
	forwarded.		forwarded.
	- Shut off: TS is in the power-off mode and not attached to the		- Shut off: TS is in the power-off mode and not attached to the
	NVE. This is similar to the suspend state. Traffic from/to the		NVE. This is similar to the suspend state. Traffic from/to the
	TS can be ignored. Routes corresponding to the TS must be		TS can be ignored. Routes corresponding to the TS must be
	withdrawn from corresponding tenant VN and the forwarding state		withdrawn from corresponding tenant VN and the forwarding state
	at the local NVE must be removed.		at the local NVE must be removed.
	- Moving: TS is active but a TS Move command was originated. The		- Moving: TS is active but a TS Move command was originated. The
	Controller must participate in any state transfer functions.		Controller must participate in any state transfer functions.
	The goal is to directly forward traffic to the TS at the new		The goal is to directly forward traffic to the TS at the new
	location and possibly tunnel traffic in transit to the old		location and possibly tunnel traffic in transit to the old
	location from the old location to the new one.		location from the old location to the new one.
	- Other: Opaque state that refers to additional states defined by		- Other: Opaque state that refers to additional states defined by
	a specialized TS.		a specialized TS.
	Even though, the states above are often related to virtual machines,		Even though, the states above are often related to virtual machines,
	the model or a subset can cover the physical appliance states as		the model or a subset can cover the physical appliance states as
	well. Depending on the TS, some of these states might not be easily		well. Depending on the TS, some of these states might not be easily
	identifiable (additional mechanisms, liveliness check, are required		identifiable (additional mechanisms, liveliness check, are required
	skipping to change at page 9, line 14 ¶		skipping to change at page 9, line 14 ¶
	as it does not contain parts of a TS packet, but information of a TS		as it does not contain parts of a TS packet, but information of a TS
	event. Alternatively a new request type can be defined. Details of		event. Alternatively a new request type can be defined. Details of
	this procedure will be added in a future revision.		this procedure will be added in a future revision.
	4.2. Address advertisement and FIB population		4.2. Address advertisement and FIB population
	Once the controller learns about the TS state event from North bound		Once the controller learns about the TS state event from North bound
	API or from the NVE it performs the following actions:		API or from the NVE it performs the following actions:
	- Identify the required NVO3 service attributes. Service		- Identify the required NVO3 service attributes. Service
	attributes could include acces lists and policies for certain		attributes could include access lists and policies for certain
	actions.		actions.
	- Populate the VN routing and FIB tables with the TS address(es).		- Populate the VN routing and FIB tables with the TS address(es).
	- If a push-model is used, it downloads the required FIB updates		- If a push-model is used, it downloads the required FIB updates
	and service attributes to the NVEs that participate in the		and service attributes to the NVEs that participate in the
	related VN (pre-population).		related VN (pre-population).
	- If a pull-model is selected, it waits for the first packets of		- If a pull-model is selected, it waits for the first packets of
	the corresponding flows or potentially other requests triggered		the corresponding flows or potentially other requests triggered
	by some events before establishing flow state, as per the		by some events before establishing flow state, as per the
	Openflow specification, or some FIB state in the NVE		Openflow specification, or some FIB state in the NVE
	- A combination of push and pull models may be beneficial. For		- A combination of push and pull models may be beneficial. For
End of changes. 7 change blocks.
	7 lines changed or deleted		7 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/