< draft-bernardos-sfc-discovery-04.txt		draft-bernardos-sfc-discovery-05.txt >
	SFC WG CJ. Bernardos		SFC WG CJ. Bernardos
	Internet-Draft UC3M		Internet-Draft UC3M
	Intended status: Experimental A. Mourad		Intended status: Experimental A. Mourad
	Expires: September 12, 2020 InterDigital		Expires: March 21, 2021 InterDigital
	March 11, 2020		September 17, 2020
	Service Function discovery in fog environments		Service Function discovery in fog environments
	draft-bernardos-sfc-discovery-04		draft-bernardos-sfc-discovery-05
	Abstract		Abstract
	Service function chaining (SFC) allows the instantiation of an		Service function chaining (SFC) allows the instantiation of an
	ordered set of service functions and subsequent "steering" of traffic		ordered set of service functions and subsequent "steering" of traffic
	through them. Service functions provide an specific treatment of		through them. Service functions provide an specific treatment of
	received packets, therefore they need to be known so they can be used		received packets, therefore they need to be known so they can be used
	in a given service composition via SFC. This document discusses the		in a given service composition via SFC. This document discusses the
	need for service function discovery mechanisms and propose some		need for service function discovery mechanisms and propose some
	solutions for sfc-aware nodes to discover available service functions		solutions for sfc-aware nodes to discover available service functions
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 September 12, 2020.		This Internet-Draft will expire on March 21, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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 2, line 21 ¶		skipping to change at page 2, line 21 ¶
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Problem statement . . . . . . . . . . . . . . . . . . . . . . 4		3. Problem statement . . . . . . . . . . . . . . . . . . . . . . 4
	3.1. Discovery of SF in a multi-provider fog/edge environment 4		3.1. Discovery of SF in a multi-provider fog/edge environment 4
	4. Network-based SF discovery . . . . . . . . . . . . . . . . . 6		4. Network-based SF discovery . . . . . . . . . . . . . . . . . 6
	4.1. ICMPv6-based SF discovery . . . . . . . . . . . . . . . . 8		4.1. ICMPv6-based SF discovery . . . . . . . . . . . . . . . . 8
	4.2. DHCPv6-based SF discovery . . . . . . . . . . . . . . . . 8		4.2. DHCPv6-based SF discovery . . . . . . . . . . . . . . . . 8
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 8		6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8		7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9		8. Informative References . . . . . . . . . . . . . . . . . . . 8
	8.1. Normative References . . . . . . . . . . . . . . . . . . 9
	8.2. Informative References . . . . . . . . . . . . . . . . . 9
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
	1. Introduction		1. Introduction
	Virtualization of functions provides operators with tools to deploy		Virtualization of functions provides operators with tools to deploy
	new services much faster, as compared to the traditional use of		new services much faster, as compared to the traditional use of
	monolithic and tightly integrated dedicated machinery. As a natural		monolithic and tightly integrated dedicated machinery. As a natural
	next step, mobile network operators need to re-think how to evolve		next step, mobile network operators need to re-think how to evolve
	their existing network infrastructures and how to deploy new ones to		their existing network infrastructures and how to deploy new ones to
	address the challenges posed by the increasing customers' demands, as		address the challenges posed by the increasing customers' demands, as
	skipping to change at page 3, line 32 ¶		skipping to change at page 3, line 31 ¶
	may be applied at any layer within the network protocol stack		may be applied at any layer within the network protocol stack
	(network layer, transport layer, application layer, etc.).		(network layer, transport layer, application layer, etc.).
	A mobile terminal can benefit from using service function chaining at		A mobile terminal can benefit from using service function chaining at
	the edge/fog to enhance existing applications or to enable new ones.		the edge/fog to enhance existing applications or to enable new ones.
	In order to do so, discovery of available service functions is		In order to do so, discovery of available service functions is
	required. This document focuses on this aspect.		required. This document focuses on this aspect.
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].
	While [RFC2119] describes interpretations of these key words in terms
	of protocol specifications and implementations, they are used in this
	document to describe requirements for the SFC mechanisms to
	efficiently enable fog RAN.
	The following terms used in this document are defined by the IETF in		The following terms used in this document are defined by the IETF in
	[RFC7665] and [I-D.ietf-bess-nsh-bgp-control-plane]:		[RFC7665] and [I-D.ietf-bess-nsh-bgp-control-plane]:
	Service Function (SF): a function that is responsible for specific		Service Function (SF): a function that is responsible for specific
	treatment of received packets (e.g., firewall, load balancer).		treatment of received packets (e.g., firewall, load balancer).
	Service Function Chain (SFC): for a given service, the abstracted		Service Function Chain (SFC): for a given service, the abstracted
	view of the required service functions and the order in which they		view of the required service functions and the order in which they
	are to be applied. This is somehow equivalent to the Network		are to be applied. This is somehow equivalent to the Network
	Function Forwarding Graph (NF-FG) at ETSI.		Function Forwarding Graph (NF-FG) at ETSI.
	skipping to change at page 9, line 5 ¶		skipping to change at page 8, line 35 ¶
	6. Security Considerations		6. Security Considerations
	TBD.		TBD.
	7. Acknowledgments		7. Acknowledgments
	The work in this draft will be further developed and explored under		The work in this draft will be further developed and explored under
	the framework of the H2020 5G-DIVE project (Grant 859881).		the framework of the H2020 5G-DIVE project (Grant 859881).
	8. References		8. Informative References
	8.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.
	8.2. Informative References
	[I-D.bernardos-sfc-fog-ran]		[I-D.bernardos-sfc-fog-ran]
	Bernardos, C., Rahman, A., and A. Mourad, "Service		Bernardos, C., Rahman, A., and A. Mourad, "Service
	Function Chaining Use Cases in Fog RAN", draft-bernardos-		Function Chaining Use Cases in Fog RAN", draft-bernardos-
	sfc-fog-ran-06 (work in progress), September 2019.		sfc-fog-ran-07 (work in progress), March 2020.
	[I-D.ietf-bess-nsh-bgp-control-plane]		[I-D.ietf-bess-nsh-bgp-control-plane]
	Farrel, A., Drake, J., Rosen, E., Uttaro, J., and L.		Farrel, A., Drake, J., Rosen, E., Uttaro, J., and L.
	Jalil, "BGP Control Plane for NSH SFC", draft-ietf-bess-		Jalil, "BGP Control Plane for the Network Service Header
	nsh-bgp-control-plane-13 (work in progress), December		in Service Function Chaining", draft-ietf-bess-nsh-bgp-
	2019.		control-plane-18 (work in progress), August 2020.
	[RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function		[RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function
	Chaining (SFC) Architecture", RFC 7665,		Chaining (SFC) Architecture", RFC 7665,
	DOI 10.17487/RFC7665, October 2015,		DOI 10.17487/RFC7665, October 2015,
	<https://www.rfc-editor.org/info/rfc7665>.		<https://www.rfc-editor.org/info/rfc7665>.
	Authors' Addresses		Authors' Addresses
	Carlos J. Bernardos		Carlos J. Bernardos
	Universidad Carlos III de Madrid		Universidad Carlos III de Madrid
End of changes. 8 change blocks.
	30 lines changed or deleted		10 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/