Erik Kline has entered the following ballot position for draft-ietf-spring-nsh-sr-12: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-spring-nsh-sr/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # Internet AD comments for draft-ietf-spring-nsh-sr-12 CC @ekline ## Comments ### S5.1, S5.2 * I am not very familiar with the SFC paradigm, so please do correct me or ignore me. Does this "service-index - 1" cache end up imposing too tight a restriction on the SF handling of the NSH, limiting processing to only a single function (decrementing the service index by only 1)? I naively expected that the SR segment list could move a packet through a network of endpoints, but that each endpoint could perhaps trigger multiple functions acting on the packet without incurring extra, duplicative segments to indicate additional processing on the same node. ### S11.1 * Should the document reference actually RFC 8300 (NSH)? "This document" defines where the IANA allocation comes from but that doesn't really help a possible implementer get directly to the required spec. _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
