Authors of draft-ietf-spring-sr-service-programming-01: "draft-ietf-spring-sr-service-programming" specifies Service SIDs to be embedded into the SID list. Does it make the SID list even longer? For example, if a packet needs to be steered through the network by 3 SIDs (S1, S2, S3), Service SIDs will be the additional SIDs to be added to the packet header?
It seems straight forward for draft-ietf-spring-srv6-network-programming to add an instruction to forward the packet to a specific service Function. Why not using draft-ietf-spring-srv6-network-programming to steer packets to specific service functions? What features specified by draft-ietf-spring-sr-service-programming that can't be achieved by draft-ietf-spring-srv6-network-programming? Some minor questions: What is the ENH in Section 6.1.2? You have ENH = 59, ENH = 4, Are you talking the Ethernet frames being encapsulated by SRH header? The inner payload are IP frames, aren't they? Thank you very much, Linda Dunbar
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
