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

Dear Dan,

Please see inline.

Cheers,
Med 

-----Message d'origine-----
De : behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la part de Dan Wing
Envoyé : mercredi 2 décembre 2009 03:07
À : 'Xu Xiaohu'; 'Simon Perreault'
Cc : behave@ietf.org
Objet : Re: [BEHAVE] proprietary implementation v.s standardisedprotocols//re: draft-xu-behave-nat-state-sync-00

... 
> > * Cluster = A set of synchronized NAT64 boxes sharing a 
> > single Pref64::/n.
> 
> Does that mean a set of NAT64 boxes within a cluster should 
> be from a single
> vendor? If so, how to deal with the case that some abnormal 
> packets cause
> NAT boxes (using the same OS) within a cluster to crash 
> simultaneously due to a bug with that OS?

The vendor fixes the bug.

The operational complexity of running two NATs, from two different vendors, is
very high:  different CLIs, different alarming/alerting (e.g., SYSLOG, SNMP,
per-session NAT logging), different features (e.g., IPsec Passthru, SCTP),
different implementation of features (e.g., TCP MSS adjustment, fragmentation
[timeouts?  how much memory dedicated to reassembly?  out-of-order packets
supported?]), bandwidth and throughput (Mbps, pps),  make it too hard to
operate both NATs.

Med: Except for the configuration operations, the remaining features should be the same, since both implementations should met the SP's requirement.
Furthermore, having both the primary and that backup nodes from the same vendor induces other unpredictable problems (and therefore long unavailability period). We experienced that kind of problems/behaviour with L2 nodes, it may be the case for NATxy boxes too.

To my knowledge, sites do not run two different implementations of DNS servers
(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.

-d

_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************