Hi Adrian, that's a fair proposal, I think. In addition, it may help to avoid the term "Traffic Engineering" when rechartering Spring. Spring needs to recharter now. I didn't see any emails on the list which advised against Spring policy routing and the related OAM mechanisms as future work items.
Regards, Ruediger -----Ursprüngliche Nachricht----- Von: spring [mailto:[email protected]] Im Auftrag von Adrian Farrel Gesendet: Donnerstag, 22. März 2018 14:08 An: [email protected] Betreff: [spring] What is "TE" and the rechartering discussion There *might* be some disconnect between: - What TEAS means by "TE" - What TEAS is perceived to mean by "TE" - What Spring means by "TE" - What Spring is perceived to mean by "TE" An option (although it would slow the discussion a bit - it might speed it in the long term) would be to try to clarify these points with a draft or a joint discussion session. Of course, that MUST NOT delay or derail the development of protocol specifications, but I think the discussion about where work should be done is a distraction: until that decision has been made (by the chairs and ADs) we should write drafts and we should discuss them on any and all mailing lists where people lurk who could help us get the work right. Adrian _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
