Subject: Re: [sfc] Comments on draft-sarikaya-sfc-hostid-serviceheader-07

From: <[email-masked]>
Date: Fri, 14 Sep 2018 10:58:30 +0000

Dear SFC chairs,

We meanwhile have received several reviews and opinions in favor of adoption of the draft having been in this state for 7 months.
What will be your decision?
Shall we post the revised version before officially ending this call or can we expect any other advice from your side?

Thanks!
Best Regards
Dirk 

-----Original Message-----
From: sfc [mailto:[email-masked]] On Behalf Of von Hugo, Dirk
Sent: Mittwoch, 15. August 2018 10:01
To: [email-masked]; [email-masked]; [email-masked]; [email-masked]
Cc: [email-masked]; [email-masked]; [email-masked]; [email-masked]; [email-masked]
Subject: Re: [sfc] Comments on draft-sarikaya-sfc-hostid-serviceheader-07

Dear Christian and Danny,

thanks a lot for your very detailed review and for suggesting editorial corrections and detecting some typos in the draft.
Very much appreciated!
We will revise the draft and submit the new version as WG draft once the adoption call is ended by the chairs.

Best Regards
Dirk

-----Original Message-----
From: Christian Esteve Rothenberg [mailto:[email-masked]] 
Sent: Dienstag, 14. August 2018 15:28
To: von Hugo, Dirk <[email-masked]>; [email-masked]; [email-masked]
Cc: [email-masked]; LUIS MIGUEL CONTRERAS MURILLO <[email-masked]>; David Moura <[email-masked]>; Marcelo Ribeiro Nascimento <[email-masked]>; Douglas Salles Viroel <[email-masked]>
Subject: Comments on draft-sarikaya-sfc-hostid-serviceheader-07

Dear authors,

Danny Lachos (cc:) and I have reviewed
draft-sarikaya-sfc-hostid-serviceheader-07 which proposes a valuable method to add user/service/slice information into the SFC meeting the needs of diverse use cases.

The initial Conventions and Terminology section assumes the reader is familiar with RFC7665, as usual. Nevertheless, to strengthen the description of the motivating use cases, I would consider recapping some key terms (e.g., SFF, SFC-aware SFs, SFC Proxy, SFC
Encapsulation) and have them appear in the use case description, which currently focuses on the problem but could provide a further technical glimpse on potential solutions unlocked through the proposed Identifiers {Subscriber, Slice and Service}. It would help to read in each use case a concrete example of a specific network element performing SFC Encapsulation and including one of the proposed Identifiers later used by other specific elements in the SFC.

In the context of the NECOS project [1], we have identified some network slicing scenarios [2] that I believe could be nicely realized with SFC featuring the proposed Slice Identifiers, offering a candidate realization strategy for some slicing modes of operation to which we do not have an actual technical solution yet. Maybe we can propose a specific scenario description for another sample use case 3.X. to be included in a future revision of the draft. I am copying some project colleagues who may also be interested in the SFC Slice Identifiers.

In addition to the suggestions above, in the attached file you can find further comments marked with [DANNY].

Thanks,
Christian and Danny

[1] NECOS - Novel Enablers for Cloud Slicing, available online:
http://www.h2020-necos.eu/

[2] NECOS Deliverable D2.1: Initial definition of use cases, available
online: http://www.maps.upc.edu/public/Deliverable%20D2.1%20final.pdf

=======================================================

[email-masked] Thu, 21 June 2018 17:16 UTCShow header

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Service Function Chaining WG of the IETF.

        Title           : Service Function Chaining: Subscriber and
Service Identification Use Cases and Variable-Length NSH Context Headers
        Authors         : Behcet Sarikaya
                          Mohamed Boucadair
                          Dirk von Hugo
Filename        : draft-sarikaya-sfc-hostid-serviceheader-07.txt
Pages           : 15
Date            : 2018-06-21

Abstract:
   This document discusses how to inform Service Functions about
   service- and subscriber-related information for the sake of policy
   enforcement and appropriate SFC-inferred forwarding.  Once the
   information is consumed by SFC-aware elements of an SFC-enabled
   domain, it is stripped from packets when they leave the SFC-enabled
   domain.  Thus privacy-sensitive information is not leaked outside the
   domain.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-sarikaya-sfc-hostid-serviceheader/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-sarikaya-sfc-hostid-serviceheader-07
https://datatracker.ietf.org/doc/html/draft-sarikaya-sfc-hostid-serviceheader-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-sarikaya-sfc-hostid-serviceheader-07

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
_______________________________________________
sfc mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/sfc