[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: misconfiguring the tunnel source address [mech-v2-04]

To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: misconfiguring the tunnel source address [mech-v2-04]
From: Erik Nordmark <Erik.Nordmark@sun.com>
Date: Tue, 24 Aug 2004 09:37:07 -0700 (PDT)
Cc: Erik Nordmark <Erik.Nordmark@sun.com>, Alex Conta <aconta@txc.com>, v6ops@ops.ietf.org
In-reply-to: "Your message with ID" <Pine.LNX.4.44.0408201528210.12557-100000@netcore.fi>
Reply-to: Erik Nordmark <Erik.Nordmark@sun.com>

> Without any description, it is obvious that the administrator who 
> wishes to set up a tunnel from node A must configure the source 
> address from node A as a source address, or just leave it empty -- and 
> then it's automatically determined.

Why is that obvious for the case of configured tunneling?
Especially given that we have other IETF specifications
that talk explicitly about using an IPv4 anycast
address as the source address of IPv6-in-IPv4 packets.

   Erik

References:
- Re: misconfiguring the tunnel source address [mech-v2-04]
  - From: Pekka Savola <pekkas@netcore.fi>

Prev by Date: RE: zeroconf draft
Next by Date: Re: mech-v2-05pre
Previous by thread: Re: misconfiguring the tunnel source address [mech-v2-04]
Next by thread: Re: misconfiguring the tunnel source address [mech-v2-04]
Index(es):
- Date
- Thread