Support Not aware of any IPR
From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Rob Shakir Sent: Wednesday, May 16, 2018 17:20 To: SPRING WG List Subject: [spring] Working Group Adoption Call for draft-filsfils-spring-segment-routing-policy Hi SPRING WG, This email initiates a two week call for working group adoption for draft-filsfils-spring-segment-routing-policy. Please indicate your support, or otherwise, for adopting this draft as a working group item by 30th May 2018. We are particularly interested in hearing from working group members that are not co-authors of this draft. As part of the discussions of adopting this draft into SPRING with the ADs and chairs of other WGs, there are a number of requests to the authors. 1. Please clarify in the text traffic steering with "SR policy" and its relationship to other traffic engineering functions. It seems to me that this work is generally describing how one selects and steers traffic into policies, rather than path calculation. Additional clarification of whether this is the case (or not), would be welcome to ensure that the relationship with other work is clear. We would ask the authors to consider whether sections 14.1-14.4 are required scope of this document. 2.. Consider what the core content of this document is, and how it can be make as concise and clear as possible. There are some specific suggestions that can be made here, but we would like to see this discussed with the working group. Additionally, there are currently 17 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 17 authors to confirm their IPR position on this document. 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 spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
