Permalink
Cannot retrieve contributors at this time
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
20 lines (13 sloc)
1.03 KB
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| L3NM: | |
| Juniper Networks has a prototype implementation of the IETF L3NM model. | |
| It takes as its input an instance of the L3SM (RFC8299) and from that populates an L3NM instance, taking diversity requirements into account. | |
| Alternatively an instance of the L3NM can be provided as input. Transformation from the L3NM instance to device configuration then occurs. | |
| Capabilities supported include any-to-any and hub-and-spoke VPNs, with a choice of BGP, OSPF or static as the PE-CE protocol. | |
| Contact information: Julian Lucek, jlucek@juniper.net | |
| -- | |
| L2NM: | |
| Juniper Networks has a prototype implementation of the IETF L2NM model. | |
| It takes as its input an instance of the L2SM (RFC8466) and from that populates an L2NM instance, taking diversity requirements into account. | |
| Alternatively an instance of the L2NM can be provided as input. Transformation from the L2NM instance to device configuration then occurs. | |
| Capabilities supported include EVPN, with single-active or all-active multihoming. | |
| Contact information: Julian Lucek, jlucek@juniper.net |