From: kuznet@ms2.inr.ac.ru
To: pekkas@netcore.fi (Pekka Savola)
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 03:32:03 +0400 (MSD) [thread overview]
Message-ID: <200307152332.DAA09710@dub.inr.ac.ru> (raw)
In-Reply-To: <Pine.LNX.4.44.0307152029580.14070-100000@netcore.fi> from "Pekka Savola" at éÀÌ 15, 2003 10:26:21
Hello!
> 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? OK. But I remember you have spoken something quite
opposite yesterday.
> Please describe what you mean by "real IPv6 6to4 addresses".
...
> If the node processing those as a next-hop supports 6to4 and has the sit0
> pseudointerface configured, the address will be but through the special
> handling.
>
> If the node doesn't support 6to4 or doesn't have the sit0 pseudointerface
> configured, the address will be processed as normal, as any other IPv6
> nexthop.
>
> Right?
I do not understand why did you ask previous question. You answered to
this.
> 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. :-)
Just to complete discussion, let's stay on format fe80::A.B.C.D, for example.
Unlike anothers it is 100% logically clean. :-)
Alexey
next prev parent reply other threads:[~2003-07-15 23:32 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 [this message]
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=200307152332.DAA09710@dub.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=davem@redhat.com \
--cc=jmorris@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).