All of lore.kernel.org
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: davem@redhat.com (David S. Miller)
Cc: jmorris@redhat.com, netdev@oss.sgi.com
Subject: Re: Fw: [PATCH] IPv6: Allow 6to4 routes with SIT
Date: Tue, 15 Jul 2003 03:29:12 +0400 (MSD)	[thread overview]
Message-ID: <200307142329.DAA06071@dub.inr.ac.ru> (raw)
In-Reply-To: <20030713005345.1fea1092.davem@redhat.com> from "David S. Miller" at éÀÌ 13, 2003 12:53:45

Hello!

> Hey guys, even though yoshfuji is away I don't see any
> reason why I shouldn't apply the patch below to both
> 2.4.x and 2.5.x.  It looks very uncontroversial to me.
> 
> Any objections?

I would wait for experts.

Technically IPv6 does not allow use of non-link-local address
as nexthop address, because nexthop address is expected to be unique
for router.

Use of IPv4-COMPAT format for tunnels was a hack to make use of tunnel more
handly, it just a tricky way to encapsulate an IPv4 address inside
IPv6 one, it has nothing to do with _real_ IPv4-COMPAT addresses,
(though logically IPv4-COMPAT addresses _are_ really link-local
for 6over4 "network") it is just an element of our API. Use of 6of4 address
is very strange idea in this context, it does not contradict to anything,
of course, but it looks utterly stupid: 6to4 is a complicated format, where
information about nexthop is encoded in an inapproriate way.
The questions sort of: "What the hell? I do a route with nexthop
2002:x:y::a:b and a:b disappears somewhere." And the question is right,
because plain logic requires to use a:b as meaningful part of nexthop,
it is the part which provides node _identity_, x:y is just routing information,
identifying particullar "6to4" network, it is meaningless when used
as a nexthop address.

Shortly, this is mess. Technically, it is just one more trick and useless one,
logically... mess.

Alexey

       reply	other threads:[~2003-07-14 23:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030713005345.1fea1092.davem@redhat.com>
2003-07-14 23:29 ` kuznet [this message]
2003-07-15  6:28   ` Fw: [PATCH] IPv6: Allow 6to4 routes with SIT Pekka Savola
2003-07-15 14:28     ` kuznet
2003-07-15 19:26       ` Pekka Savola
2003-07-15 23:32         ` kuznet
2003-07-16  6:12           ` Pekka Savola
2003-07-17  0:20             ` kuznet
2003-07-17  7:04               ` Pekka Savola
2003-07-17 11:16                 ` Mika Liljeberg
2003-07-17 11:54                   ` Mika Liljeberg
2003-07-17 13:55                     ` Pekka Savola
2003-07-17 14:35                       ` Mika Liljeberg
2003-07-16 22:28       ` Mika Liljeberg
2003-07-16 23:28         ` kuznet
2003-07-16 23:39           ` Mika Liljeberg
2003-07-16 23:58             ` kuznet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200307142329.DAA06071@dub.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=davem@redhat.com \
    --cc=jmorris@redhat.com \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.