Hi all,
As I had pointed out at the last IETF meeting, section 6 of this draft has an
serious overlap with
https://tools.ietf.org/html/draft-xu-mpls-service-chaining-03 that has now been
updated by
https://tools.ietf.org/html/draft-xuclad-spring-sr-service-chaining-01 with a
merge with draft-clad-spring-segment-routing-service-chaining.
Hence, I'm very interesting to know the intention of such rewritting of a given
mechanism that has been described in another draft. Is there any special
nutrition?
Best
regards,Xiaohu------------------------------------------------------------------发件人：IETF
Secretariat <ietf-secretariat-re...@ietf.org>发送时间：2018年3月6日(星期二)
22:09收件人：draft-farrel-mpls-sfc <draft-farrel-mpls-...@ietf.org>; mpls
<m...@ietf.org>; mpls-chairs <mpls-cha...@ietf.org>主 题：[mpls] The MPLS WG has
placed draft-farrel-mpls-sfc in state "Call For Adoption By WG Issued"
The MPLS WG has placed draft-farrel-mpls-sfc in state
Call For Adoption By WG Issued (entered by Loa Andersson)
The document is available at
https://datatracker.ietf.org/doc/draft-farrel-mpls-sfc/
_______________________________________________
mpls mailing list
m...@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring
