IETF conflict review for draft-nachum-sarp
|draft-nachum-sarp-11 ISE stream
|Approved No Problem - announcement sent
|Send notices to
|"Nevil Brownlee" <email@example.com>, firstname.lastname@example.org
The IESG has concluded that this work is related to IETF work done in the NVO3 and PALS working groups, but this relationship does not prevent publishing. This work, like RFC 7342, has its origins in the ARMD working group. That working group closed down, having produced just one RFC, for lack of consensus on the need for or direction of any solutions work. Since the IETF has no active work in this area, it cannot be claimed that this draft conflicts with any IETF efforts. Furthermore, the IETF has published no work on solutions for scaling ARP. However, there are existing techniques using IETF protocols that address the problem that this document seeks to solve and that do not require this approach. Indeed, an existing deployed solution places each data center in a separate L2 domain and connects them with IP. This, in itself, does not predicate against an experiment with SARP, but the IESG needs to give clear guidance that other solutions from within the IETF stable already exist. Therefore, the IESG requests the ISE to include the following IESG note in this document if it is published as an RFC. The IESG notes that the problems described in RFC 6820 can already be addressed through the simple combination of existing standardized or other published techniques including Layer 2 VPN (RFC 4664), proxy ARP (RFC 925), proxy Neighbor Discovery (RFC 4389), IGMP and MLD snooping (RFC 4541), and ARP mediation for IP interworking of Layer 2 VPNs (RFC 6575).