Chris M. Lonvick wrote:
> >My take is that for a multihomed host, the FQDN/IP to use is the one
> >belonging to the interface over which the session is being carried. (This
> >assumes, of course, that each channel is carried over at most one
> >interface.) What problems might be caused by making this otherwise?
>
> If the original interface were to die, then the sender shouldn't be able
> to carry on the same session with the receiver. The sender would then
> have to start a new session with the receiver with a new IP address.
Practically speaking, we're running over TCP here. I don't think you can
switch source addresses for a TCP connection and still maintain the same
connection.
> ((There are some funky resiliency techniques that could continue the
> session on a different interface with the same address but I don't think
> that we need to address those scenarios.))
A different physical interface with the same IP address isn't a problem,
really, since the XML in the syslog-reliable stuff is just talking about the
IP address. If the IP address doesn't change, no problem. If the IP address
*does* change, you'd lose the TCP connection anyway, unless there's some
*really* funky stuff out there I don't know about.
> >> COOKED <received> :
> I'll agree with Darren's comment.
Cool. I'll get out another draft by EOW.
--
Darren New / Senior MTS & Free Radical / Invisible Worlds Inc.
San Diego, CA, USA (PST). Cryptokeys on demand.
