Re: VRRPv3 Implementation Report
"Mukesh Gupta" <[email protected]> Tue, 14 Oct 2008 22:42:55 -0700
| Newsgroups | gmane.ietf.vrrp |
|---|---|
| Message-ID | <FF22D8DA3CC478438280A45A7CFAD27A068092A9@ca-bay-exch-01.tropos.com> |
[Copying the WG] Lin, It's good to hear about your implementation and your comments. I will let Steve, the author/editor of the unified VRRP draft, respond to your technical comments. It would be good to receive information about the implementation of the unified draft (draft- ietf-vrrp-unified-spec-02.txt). When do you think you would be implementing the new draft? Steve, have you guys implemented the unified draft? Regards Mukesh > -----Original Message----- > From: Lin Tao [mailto:[email protected]] > Sent: Tuesday, October 14, 2008 2:23 AM > To: Mukesh Gupta; [email protected] > Cc: [email protected] > Subject: Re: [VRRP] VRRPv3 Implementation Report > > Dear Mukesh Gupta: > I'm a developer in H3C. We have implemented draft-ietf-vrrp-ipv6-spec-08 in our > Comware, and have paid attention to draft-ietf-vrrp-unified-spec-02. There are some > improvement, we shall develope it. > There is a new concept "Accept_Mode" in 6.1. In our opinion, the Default would be True. > Though the address is not its own, but there is requirement that the operator can manage the > router by connecting to this vrrp address when a virtual router in Master, i.e. this address > can be thought as the virtual route's own address. > Furthermore, we could think about wiping this mode away, and it will bring benifit in > implementation because of Simple design. > Sincerely look forward to your reply. > > Accept_Mode Controls whether a virtual router in Master > state will accept packets addressed to the > address owner's IPvX address as its own if it > is not the IPvX address owner. Default is > False. > > Note: IPv6 Neighbor Solicitations and > Neighbor Advertisements should not be dropped > when Accept_Mode is False. > > FYI: This is our implementation. > ======================================== > Name of Implementation: VRRP in Comware > Platform: Comware > Organization: H3C Technologies Co. > Origin of Code: Internal development > Information supplied by: Lin Tao [email protected] > Tested Interoperability: None yet. > ======================================== > > > > ----- Original Message ----- > From: Mukesh Gupta > To: [email protected] > Cc: Ross Callon > Sent: Saturday, October 11, 2008 8:40 AM > Subject: [VRRP] VRRPv3 Implementation Report > > > Hi All, > > The chairs are putting together an implementation report for VRRPv3 unified draft (draft- > ietf-vrrp-unified-spec-02.txt). If you have one or if you know of any, please let us know > before 10/31/08. > > Here is the information that is required. > > ======================================== > Name of Implementation: > Platform: > Organization: > Origin of Code: > Information supplied by: > Tested Interoperability: > ======================================== > > You can take a look at http://www.ietf.org/IESG/Implementations/rfc-2338- > implementation.txt for examples. > > Regards > Mukesh > > > > > > _______________________________________________ > vrrp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/vrrp _______________________________________________ vrrp mailing list [email protected] https://www.ietf.org/mailman/listinfo/vrrp