Re: [BEHAVE] proprietary implementation v.s standardisedprotocols//re: draft-xu-behave-nat-state-sync-00

["Dan Wing" <[e-mail]>]

 

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] 
> Sent: Tuesday, December 01, 2009 9:55 PM
> To: Dan Wing
> Cc: 'Xu Xiaohu'; 'Simon Perreault'; [e-mail]
> Subject: Re: [BEHAVE] proprietary implementation v.s 
> standardisedprotocols//re: draft-xu-behave-nat-state-sync-00 
> 
> 
> In message <005301ca730e$5e44bd20$[e-mail]>, "Dan 
> Wing" writes:
> >  
> > 
> > > -----Original Message-----
> > > From: [e-mail] [mailto:[e-mail]] 
> > > Sent: Tuesday, December 01, 2009 8:51 PM
> > > To: Dan Wing
> > > Cc: 'Xu Xiaohu'; 'Simon Perreault'; [e-mail]
> > > Subject: Re: [BEHAVE] proprietary implementation v.s 
> > > standardisedprotocols//re: draft-xu-behave-nat-state-sync-00 
> > > 
> > > 
> > > In message <002201ca7301$5db9a710$[e-mail]>, "Dan 
> > > Wing" writes:
> > > >  
> > > > 
> > > > > -----Original Message-----
> > > > > From: [e-mail] [mailto:[e-mail]] 
> > > > > Sent: Tuesday, December 01, 2009 6:38 PM
> > > > > To: Dan Wing
> > > > > Cc: 'Xu Xiaohu'; 'Simon Perreault'; [e-mail]
> > > > > Subject: Re: [BEHAVE] proprietary implementation v.s 
> > > > > standardisedprotocols//re: draft-xu-behave-nat-state-sync-00 
> > > > > 
> > > > > 
> > > > > In message <000001ca72f4$1e1a30a0$[e-mail]>, "Dan 
> > > > > Wing" writes:
> > > > > > To my knowledge, sites do not run two different 
> > > > > implementations of DNS server
> > > > > > s
> > > > > > (e.g., ISC BIND and InfoBlox, or Microsoft and Unbound) 
> > > > > where both DNSs back
> > > > > > up each other.  Like NAT, DNS needs to be rock-solid 
> > > > > reliable, and a single
> > > > > > packet could take out a DNS server.
> > > > > 
> > > > > Actually lots of sites use multiple vendors for DNS.  
>  That being
> > > > > said there is not of lot of state to share between 
> DNS servers.
> > > > 
> > > > So they would update each other when one receives, say, a 
> > > DNS UPDATE?
> > > 
> > > UPDATEs are forwarded to the master server 
> > 
> > They're both master servers; you can't invoke DNS's master/secondary
> > concept here.  :-)
> 
> UPDATE doesn't support multi-master, it hasn't been specified.

I know.

Then the multi-vendor mixed DNS environment you had described
earlier isn't happening:  one DNS is master, the others are
secondary.  That's different from the active/standby of NAT64
being proposed, where the standby NAT64 takes over completely and
fully for the now-deceased (e.g., crashed) NAT64, and is now
a fully-functioning node.

With a secondary taking over for a master, it is not a fully
funtional node (it can't accept UPDATEs, for example, and 
changing its serial number on a zone file will be forgotten
when the master comes back alive).  Only the master is fully 
functional.

Seems different to me.

-d


> > > that then applies the
> > > update and sends out NOTIFY messages to say the zone contents have
> > > changed.  The slaves then do a IXFR request triggered by 
> the NOFIFY.
> > > 
> > > 		             serial 1		           serial 1
> > > client ->    UPDATE       -> slave -> FORWARED UPDATE    
> -> master 
> > > 							   serial 2
> > > client <- UPDATE RESPONSE <- slave <- UPDATE RESPONSE    <- master
> > > 			     slaves <- NOTIFY (serial 2) <- master
> > > 			     slaves -> NOTIFY RESPONSE   -> master
> > > 			     slaves -> IXFR (serial 1)   -> master
> > > 			     slaves <- IXFR RESPONSE     <- master
> > > 			     serial 2
> > > 
> > > > -d
> > > > 
> > > > > DHCP servers on the other had need to share lots of 
> > > state.  I don't
> > > > > believe the failover draft 
> (draft-ietf-dhc-failover-12) reached a
> > > > > conclusion even though we implement most (all?) of it 
> in our DHCP
> > > > > servers.
> > > > > 
> > > > > Mark
> > > > > -- 
> > > > > Mark Andrews, ISC
> > > > > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > > > > PHONE: [phone]                 INTERNET: [e-mail]
> > > > 
> > > -- 
> > > Mark Andrews, ISC
> > > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > > PHONE: [phone]                 INTERNET: [e-mail]
> > 
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: [phone]                 INTERNET: [e-mail]