<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.boucadair-sfc-design-analysis" target="https://datatracker.ietf.org/doc/html/draft-boucadair-sfc-design-analysis-03">
   <front>
      <title>Service Function Chaining: Design Considerations, Analysis &amp; Recommendations</title>
      <author initials="M." surname="Boucadair" fullname="Mohamed Boucadair">
         <organization>France Telecom</organization>
      </author>
      <author initials="C." surname="Jacquenet" fullname="Christian Jacquenet">
         <organization>France Telecom</organization>
      </author>
      <author initials="R." surname="Parker" fullname="Ron Parker">
         <organization>Affirmed Networks</organization>
      </author>
      <author initials="L." surname="Dunbar" fullname="Linda Dunbar">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="October" day="22" year="2014" />
      <abstract>
	 <t>   This document aims at analyzing the various design options and
   providing a set of recommendations for the design of Service Function
   Chaining solution(s).  Note:

   o  The analysis does not claim to be exhaustive.  The list includes a
      preliminary set of potential solutions; other proposals can be
      added to the analysis if required.

   o  The analysis is still ongoing.  The analysis text will be updated
      to integrate received comments and inputs.

   o  Sketched recommendations are not frozen.  These recommendations
      are provided as proposals to kick-off the discussion and to
      challenge them.

   o  The analysis does not cover any application-specific solution
      (e.g., HTTP header) because of the potential issues inherent to
      (TLS) encrypted traffic.

   o  The analysis will be updated to take into account the full set of
      SFC requirements.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-boucadair-sfc-design-analysis-03" />
   
</reference>
