Clear draft-ietf-vrrp-unified-spec 4
Stephen Nadas <[email protected]> Fri, 2 Oct 2009 11:40:45 -0400
| Newsgroups | gmane.ietf.vrrp |
|---|---|
| Message-ID | <450AE4BEC513614F96969DDA34F3593497639B99@EUSAACMS0701.eamcs.ericsson.se> |
Hi Dan, Will the approaches described below suffice to clear the draft for the comment? (there's a separate email coming for the discuss) Thanks, Steve 1. Appendix B and part of Appendix C excepting the part refering to changes from RFC 3768 should be dropped at publication. Will do 2. Another feature that at least one vendor implements is so-called Backup VRRP router passive ARP learning. This is very useful, because otherwise when you switch from active to backup, the backup doesn't know ARP bindings for IP addresses and this increases the time needed to converge. (The same feature should apply to ND I think) This would seem to be something that could be worth adding or at least discussing in the spec. We (VRRP wg chairs & I) would like to ship this document soon and part of the thinking all along with this draft was to avoid feature creep. Thus we are not thinking of adding this new feature- it is not required for interoperability. It could, however, be covered in a new separate draft. _______________________________________________ vrrp mailing list [email protected] https://www.ietf.org/mailman/listinfo/vrrp