From: Pekka Savola <pekkas@netcore.fi>
To: kuznet@ms2.inr.ac.ru
Cc: davem@redhat.com, <jmorris@redhat.com>, <netdev@oss.sgi.com>
Subject: Re: Fw: [PATCH] IPv6: Allow 6to4 routes with SIT
Date: Wed, 16 Jul 2003 09:12:04 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0307160905330.20100-100000@netcore.fi> (raw)
In-Reply-To: <200307152332.DAA09710@dub.inr.ac.ru>
On Wed, 16 Jul 2003 kuznet@ms2.inr.ac.ru wrote:
> > Such addresses are link-locals, of link local scope only. A link-local
> > IPv6 address is awfully difficult to remember and type for all of your
> > possible links.
> >
> > The only reasonable value user could supply is a global address.
>
> So what? I do not see connection to previous. You want to live with global
> addresses as nexthop?
Yes, I dare to say that they're a requirement.
(But to be clear, when I talk about "global nexthop", I'm only interested
in nexthops which are on-link. That is, if you have prefix
3FFF:FFFF:A:B::/64, setting 3FFE:FFFF:A:B::1 would be ok, but
3FFE:FFFF:F00:BA::1 would not *have* to work.)
> OK. But I remember you have spoken something quite
> opposite yesterday.
I don't recall that. I think I was only suggesting that ONE possible way
of implementing it (which I wouldn't think is the best one) is make that
the user space tools' problem: i.e. make them resolve a globally addressed
nexthop to a link-local nexthop.
> > Redundant information can be ignored. This is not computer science
> > theory, removing everything which is not directly relevant. The use of
> > the same representation for the next-hop (2002:F00:BA::x) as an address
> > (2002:BA:F00:y) is the only logical, user-friendly way.
>
> What a bullshit... The second is address of host "x". The first is supposed
> to be address of host F00:BA, whatever it is. Probably, you can decrypt
> this only because poisoned by computer science. :-)
You read too much to in what I wrote (or maybe I wrote too much :-) --
what I mean is that 6to4 addresses have a very specific format. It's
completely illogical and unfriendly to the users to require use different
formats when they use 6to4 addresses as nexthops and "normal" addresses.
> Just to complete discussion, let's stay on format fe80::A.B.C.D, for example.
> Unlike anothers it is 100% logically clean. :-)
I can't disagree with you there; it's simple, but it's NOT what
specifications use and the *users* want and need to use.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
next prev parent reply other threads:[~2003-07-16 6:12 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 ` Fw: [PATCH] IPv6: Allow 6to4 routes with SIT kuznet
2003-07-15 6:28 ` 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 [this message]
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=Pine.LNX.4.44.0307160905330.20100-100000@netcore.fi \
--to=pekkas@netcore.fi \
--cc=davem@redhat.com \
--cc=jmorris@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--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.