Re: NAT Not Needed To Make Renumbering Easy

From: Sam Hartman <hartmans-ietf at mit.edu>
To: Phillip Hallam-Baker <hallam at gmail.com>
Cc: Sam Hartman <hartmans-ietf at mit.edu>, Christian Vogt <christian.vogt at ericsson.com>, IETF Discussion Mailing List <ietf at ietf.org>
Date: Thu, 05 Nov 2009 09:55:02 -0500
In-reply-to: <a123a5d60911042039k1d79ef73uce76c5cbbdf64e98 at mail.gmail.com> (Phillip Hallam-Baker's message of "Wed\, 4 Nov 2009 23\:39\:05 -0500")
References: <4D618E2F-A606-4CD5-9782-C07801F725D8 at sabahattin-gucukoglu.com> <8c99930d0910251441s3c2f5775sffa387017bac0df5 at mail.gmail.com> <55A9AFD6-35E2-4BBB-9F11-AD7FAE3DE3EC at ericsson.com> <tslljiml0vh.fsf at mit.edu> <6AC1DDB8-1FB2-4785-8622-8579D54D4376 at ericsson.com> <a123a5d60911042039k1d79ef73uce76c5cbbdf64e98 at mail.gmail.com>

>>>>> "Phillip" == Phillip Hallam-Baker <hallam at gmail.com> writes:

    Phillip> I am not sure I want failover to be handled at the IP
    Phillip> transport level.  Failover is something I would see as
    Phillip> part of 'robust service connectivity' which would include
    Phillip> what to do if one or both endpoint hosts failed. 

I think I agree.

References:
- NAT Not Needed To Make Renumbering Easy
  - From: Sabahattin Gucukoglu
- Re: NAT Not Needed To Make Renumbering Easy
  - From: Andrew G. Malis
- Re: NAT Not Needed To Make Renumbering Easy
  - From: Christian Vogt
- Re: NAT Not Needed To Make Renumbering Easy
  - From: Sam Hartman
- Re: NAT Not Needed To Make Renumbering Easy
  - From: Christian Vogt
- Re: NAT Not Needed To Make Renumbering Easy
  - From: Phillip Hallam-Baker

Prev by Date: Re: NAT Not Needed To Make Renumbering Easy
Next by Date: Re: NAT Not Needed To Make Renumbering Easy
Previous by thread: Re: NAT Not Needed To Make Renumbering Easy
Next by thread: Re: NAT Not Needed To Make Renumbering Easy
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: NAT Not Needed To Make Renumbering Easy

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.