Dear Spring,
Softbank and Cisco have announced the deployment of SRv6:
https://newsroom.cisco.com/press-release-content?type=webcontent&articleId=1969030
Another deployment is ongoing and several others are in preparation.
All these design and deployments extensively leverage the mature content
of the SRv6 network programmability document and its various
implementations:
.. Cisco: 4 different hardware and 3 OS
.. Linux: Kernal and srext module
.. FD.io: VPP
.. Apps: Snort, Wireshark, tcpdump, iptables and nftables
.. Other vendor as previously reported on the list
Multiple interoperable verifications took place.
The maturity of the draft since March 2017 coupled with the large number
of implementations, their interoperability and their concrete deployment
on several networks indicate that the drafts are ready for adoption by
the working group.
Cheers,
Clarence Filsfils
On 01-03-19 04:30, Lizhenbin wrote:
SRv6 network programming is an important work for the network evolution.
After refining many times the draft is already stable.
Besides the implementation and inter-op test info proposed, this week it
was published that there was already the commercial deployment of SRv6.
Hope the draft can be adopted by the working group as the co-author.
Best Regards,
Zhenbin (Robin)
*From:*spring [mailto:[email protected]] *On Behalf Of *Pablo
Camarillo (pcamaril)
*Sent:* Thursday, February 14, 2019 4:56 PM
*To:* [email protected]
*Subject:* [spring] draft-filsfils-spring-srv6-network-programming
Dear Spring,
We have submitted a new revision of
draft-filsfils-spring-srv6-network-programming. There are several minor
updates to the document, mainly addressing ICMP and having better
alignment with SRH draft. Also, based on WG feedback, we have split the
document moving the illustrations into a new informational draft.
As always, any feedback or question is more than welcome.
https://datatracker.ietf.org/doc/draft-filsfils-spring-srv6-network-programming/
https://datatracker.ietf.org/doc/draft-filsfils-spring-srv6-net-pgm-illustration/
We believe that the content of both drafts is mature and has been stable
since the first revision in March 2017. We are tracking several
opensource and vendor proprietary implementations. Some of these have
actually participated in a public interop more than a year ago.
For these reasons we believe that both documents are ready to progress
and be adopted by the working group.
Thanks,
Pablo (on behalf of authors&contributors)
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
