public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@sun.com>
To: "Matthew G. Marsh" <mgm@paktronix.com>
Cc: David Ford <david@blue-labs.org>,
	Christopher Friesen <cfriesen@nortelnetworks.com>,
	kuznet@ms2.inr.ac.ru, Julian Anastasov <ja@ssi.bg>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: issue: deleting one IP alias deletes all
Date: Thu, 25 Oct 2001 13:01:45 -0700	[thread overview]
Message-ID: <3BD86FA9.A992FE96@sun.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0110251234430.32029-100000@netmonster.pakint.net>

"Matthew G. Marsh" wrote:

> The original thought refers to the old concept of address "class" where is
> a "class" (think subnet) went away then there was no need (and indeed
> incorrect) behaviour to still be able to have addresses on it. Thus when
> the primary address is deleted you should clear all addresses within that

I don't really think the original thought matters.  What matters is that
the behavior is 
a) non-obvious - you don't expect it
b) undetectable - you can't find out which alias is "primary"
c) inconsistent - some aliases act differently that other aliases

All of these violate the principle of least surprise.  Whether it was
intentional or not, it behaves like a nasty hack, or worse, a bug.  It is
easily fixed, and should be.

> Again - if you do not like this behaviour do not use the primary/secondary
> addressing scopes. Use /32.

Why should user-land be forced to work around what is obviously (to the
vast majority of people in this discussion) a mis-feature?

-- 
Tim Hockin
Systems Software Engineer
Sun Microsystems, Cobalt Server Appliances
thockin@sun.com

  reply	other threads:[~2001-10-25 19:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-24  1:01 issue: deleting one IP alias deletes all Julian Anastasov
2001-10-24  5:28 ` David Ford
2001-10-24  6:18   ` Petr Titera
2001-10-24  6:52     ` David Ford
2001-10-24 12:48     ` Wilson
2001-10-25 16:34     ` Matthew G. Marsh
2001-10-24  8:19   ` Julian Anastasov
2001-10-24 14:02   ` Christopher Friesen
2001-10-24 15:34     ` Tim Hockin
2001-10-24 17:14       ` Christopher Friesen
2001-10-24 20:36     ` David Ford
2001-10-24 20:54       ` Tim Hockin
2001-10-27 17:26         ` kuznet
2001-10-25 17:40       ` Matthew G. Marsh
2001-10-25 20:01         ` Tim Hockin [this message]
2001-10-25 19:56           ` David S. Miller
2001-10-25 20:29           ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2001-10-23 17:54 Tim Hockin
2001-10-24 11:36 ` Kurt Roeckx
2001-10-24 12:00   ` Kurt Roeckx
2001-10-25 16:30 ` Matthew G. Marsh
2001-10-26 19:51   ` Michal Jaegermann

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=3BD86FA9.A992FE96@sun.com \
    --to=thockin@sun.com \
    --cc=cfriesen@nortelnetworks.com \
    --cc=david@blue-labs.org \
    --cc=ja@ssi.bg \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgm@paktronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox