Subject: [sfc] Legacy SF

From: Youjianjie <[email-masked]>
Date: Wed, 6 Apr 2016 01:43:46 +0000

Hi all,

Would you like to review legacy-SF draft?

Thanks,
Jianjie

A new version of I-D, draft-song-sfc-legacy-sf-mapping-07.txt

has been successfully submitted by Jianjie You and posted to the IETF repository.

Name:               draft-song-sfc-legacy-sf-mapping

Revision:  07

Title:                  SFC Header Mapping for Legacy SF

Document date:       2016-04-05

Group:               Individual Submission

Pages:               17

URL:            https://www.ietf.org/internet-drafts/draft-song-sfc-legacy-sf-mapping-07.txt

Status:         https://datatracker.ietf.org/doc/draft-song-sfc-legacy-sf-mapping/

Htmlized:       https://tools.ietf.org/html/draft-song-sfc-legacy-sf-mapping-07

Diff:           https://www.ietf.org/rfcdiff?url2=draft-song-sfc-legacy-sf-mapping-07

Abstract:

   A Service Function Chain (SFC) defines a set of abstract Service

   Functions (SF) and ordering constraints that must be applied to

   packets and/or frames selected as a result of classification.  One

   assumption of this document is that legacy service functions can

   participate in service function chains without having support for the

   SFC header, or even being aware of it.  This document provides a

   mechanism between an SFC proxy and an SFC-unaware service function

   (herein termed "legacy SF"), to identify the SFC header associated

   with a packet that is returned from a legacy SF, without an SFC

   header being explicitly carried in the wired protocol between SFC

   proxy and legacy SF.

发件人: sfc [mailto:[email-masked]] 代表 Songhaibin (A)
发送时间: 2015年7月6日 17:24
收件人: Jim Guichard (jguichar); [email-masked]
主题: Re: [sfc] SFC WG agenda slots - Prague

Hi Jim,

I would like to request a very short slot presentation for draft-song-sfc-legacy-sf-mapping-05. This document serves the purpose how legacy service functions can participate in the service function chaining. There are some updates. We make it informational and remove RFC 2119 language, and add a little more deployment considerations, and also clarify on the meta data problem.

Best Regards!
-Haibin

From: sfc [mailto:[email-masked]] On Behalf Of Jim Guichard (jguichar)
Sent: Saturday, June 27, 2015 10:58 PM
To: [email-masked]<mailto:[email-masked]>
Subject: [sfc] SFC WG agenda slots - Prague

Greetings WG:

Our meeting in Prague is fast approaching. As always the goal of the meeting will be to make the best use of our limited face-to-face time. With that in mind we welcome requests for agenda time.

As we build the meeting agenda our goal will be to select presentations that best further the work of the WG, and that generally means focusing on key charter deliverables and topics with important open issues to resolve. When making a request please consider what you think the WG should do with its content – for example:

  *   Does the document have useful content that should be moved into another WG document or progress on its own merit
  *   Does the content have a good basis for one of the WG documents per the charter
  *   Should the document content be merged with one or more other documents, so that a combined document could become a WG document
Jim & Thomas