Path segment has multiple useful use cases. I support the WG adoption of this draft.
Few comments 1. The fact that service labels appear below path-segment should be clearly mentioned. At the egress, multiple labels may have to be looked-up and popped for UHP cases. This may need special hardware capability. This egress processing needs to be explained in the draft. 2. The ability to have a globally significant path-ID representation is very useful for various accounting purposes. I believe, we should continue to have globally scoped path-segment. 3. The path-segment should be pushed in a packet only when egress is capable of processing the path-segment. This aspect needs to be explained in this draft. Rgds Shraddha -----Original Message----- From: spring <[email protected]> On Behalf Of [email protected] Sent: Wednesday, February 20, 2019 2:34 PM To: SPRING WG <[email protected]> Cc: [email protected] Subject: [spring] Working Group Adoption Call for draft-cheng-spring-mpls-path-segment Hi SPRING WG, This email initiates a two week call for working group adoption for draft-cheng-spring-mpls-path-segment. Please indicate your support, comments, or objection, for adopting this draft as a working group item by March 6th 2019. We are particularly interested in hearing from working group members that are not co-authors of this draft. We are also looking for volunteers who would be ready to perform a technical review of this work at some later stage, such as before or during WG the last call. Additionally, there are currently 7 authors listed on this document. Please trim this to <= 5 front-page authors, utilising a "Contributors" section if required for the others. An approach to achieving this would be to list ~2 editors as the front-page authors. In parallel to this adoption call, I will send an IPR call for this document. We will need all authors and contributors to confirm their IPR position on this document. (1) https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dcheng-2Dspring-2Dmpls-2Dpath-2Dsegment&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=NyjLsr7JA7mvpCJa0YmPdVKcmMXJ31bpbBaNqzCNrng&m=fghPD_5Ecs8TYVskFZ0y6Npv0QXqX0-pLlGysClTjls&s=z8A_nYKmKXm0-42sVmn6BDxD3rSl6dJUudnCulEvofk&e= Thanks, --Bruno & Rob. _________________________________________________________________________________________________________________________ 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 [email protected] https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_spring&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=NyjLsr7JA7mvpCJa0YmPdVKcmMXJ31bpbBaNqzCNrng&m=fghPD_5Ecs8TYVskFZ0y6Npv0QXqX0-pLlGysClTjls&s=lf5L9lWYG4dgqnmDcTGYmbZd8iu-r73dEq-0IOsnaq8&e= _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
