Subject: Re: [sfc] The SFC WG has placed draft-sarikaya-sfc-hostid-serviceheader in state "Call For Adoption By WG Issued"

From: <[email-masked]>
Date: Wed, 1 Aug 2018 10:40:01 +0000

Hello Debashish,
thanks for the comments and suggestions.
We will address the dynamic SFP configuration in more detail in the next update (i.e. when we re-submit as WG draft).
Of course the NSH context header should allow for standardized interoperability  - we will point on this specifically in that next version, since it seems not to be enough reflected in the current text.
Thanks again!
Any other views towards adoption on the mailing list?
Of course more comments are equally welcome after adoption ;-)

Best Regards
Dirk 
-----Original Message-----
From: Purkayastha, Debashish [mailto:[email-masked]] 
Sent: Dienstag, 31. Juli 2018 20:41
To: [email-masked]; [email-masked]; [email-masked]
Cc: von Hugo, Dirk <[email-masked]>; [email-masked]
Subject: RE: [sfc] The SFC WG has placed draft-sarikaya-sfc-hostid-serviceheader in state "Call For Adoption By WG Issued"

Hello,

I have read the draft and support it's adoption.

This will be useful to allow SFs take different actions based on the information.

The use cases are interesting. For some of the use cases, e.g. low latency and high reliability, SF may need to get feedback from the network. How does the author visualizes that to happen? These two use cases may need the SFP to be dynamically configured as network condition, user load changes.

W.r.t section 4, how does authors view the SFs from different vendor to be interoperable. Will there be a common way to interpret the NSH Context header? How does this mechanism scale?

Thanks
Debashish.

> > On Tue, 2018-02-13 at 05:19 -0800, IETF Secretariat wrote:
> > > The SFC WG has placed draft-sarikaya-sfc-hostid-serviceheader in 
> > > state Call For Adoption By WG Issued (entered by Joel Halpern)
> > >
> > > The document is available at
> > > https://datatracker.ietf.org/doc/draft-sarikaya-sfc-hostid-servic
> > > eh
> > > ea
> > > der/
> > >
> > > _______________________________________________
> > > sfc mailing list
> > > [email-masked]
> > > https://www.ietf.org/mailman/listinfo/sfc

_______________________________________________
sfc mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/sfc
[Banner]
This e-mail is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and/or otherwise protected from disclosure to anyone other than its intended recipient. Unintended transmission shall not constitute waiver of any privilege or confidentiality obligation. If you received this communication in error, please do not review, copy or distribute it, notify me immediately by email, and delete the original message and any attachments. Unless expressly stated in this e-mail, nothing in this message or any attachment should be construed as a digital or electronic signature.