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

From: "Purkayastha, Debashish" <[email-masked]>
Date: Tue, 31 Jul 2018 18:41:15 +0000

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