Dear All, I have several questions about the draft: - When using the approach described in Section 4, i.e., SR-based SFC with the integrated NSH, how does a re-Classifier scenario be handled? If I understand it correctly, a re-Classifier can change the SPI of the NSH coming back from the SF. If that is the case, the SFF will not match it to the saved SR information because the SPI had changed. How would SFF forward the NSH and the payload? - Related to the scenario from the above. The stored SR information that is not being used appears to become stale. It seems that it creates a leak of resources in a system that should be controlled somehow.
Regards, Greg On Tue, Feb 9, 2021 at 10:31 AM <bruno.decra...@orange.com> wrote: > Dear WG, > > > > This message starts a 2 weeks WG last call for draft-ietf-spring-nsh-sr > [1]. > > After review of the document please indicate whether you believe this > document should be progressed to the IESG. > > > > In addition to yes/no, please consider providing a technical review of > this document; in particular if you care for this document. > > Indeed, since WG adoption, this document had benefited from little reviews > from the WG, so we need more review from the SPRING WG. > > > > If you are aware of an implementation of this document, please report the > implementation either on the list or to the chairs so that the shepherd can > report implementations in the writeup. > > > > Note that I’ll forward that call to the SFC WG. > > > > Thanks! > > > > [1] https://tools.ietf.org/html/draft-ietf-spring-nsh-sr > > > > --Bruno > > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring >
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
