mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Myrddin Ambrosius <imipak@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: IGMPv3 (and the network code in general)
Date: Fri, 28 Dec 2001 12:27:24 -0800 (PST)	[thread overview]
Message-ID: <20011228202724.99671.qmail@web12303.mail.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2202 bytes --]

Hi,

   Well, I finally got to work on IGMPv3 for Linux.
Bad
Mistake! This looks like it'll be some seriously heavy
work,
if I'm going to do this properly, and not just make
some
half-hearted effort.

   First, IGMPv3 starts off apparently trivial - an
extended
IGMP header, a few #defines, one function, and a
couple
of structures. No biggie. But then it starts to get
fun.....

   Auxiliary data structures are the next layer in
IGMPv3.
The draft IGMPv3 document doesn't define any, but
there
is one for authentication, also in draft form, which
begins
to make things complicated.

   Parallel to all of this (and part of IGMPv3) is SSM
(Source Specific Multicast). Built around that, is
MSNIP
(Multicast Source Notification of Interest Protocol),
which
then has extensions for proxying. There's an RTCP
extension for SSM, but I'm going to ignore that. MSNIP
looks like it is going to be the biggest chunk of the
code.
The bulk of the API extensions, structures, etc, are
all
MSNIP stuff.

   I've included a diff for igmp.h, which inserts my
(shaky)
interpretation of the relevent draft documents' specs
for the
required structures, defines and functions. I've
backetted
the new code with #if define's. That way, it's visible
as to
what bit of code is intended for what, and the
extensions
can be selectively compiled in. (I've a nasty
suspicion that
there's going to be a fair amount of overhead involved
in
all this.)

   I want to get my interpretation of the API out
-now-,
because if I'm incorrect, I'd rather know about it
sooner,
rather than later. I'll get the back-end code out,
eventually,
but I'm sure you don't want to see a bunch of stubs
and
half-chewed code. (My hamster got into the computer.)

   I might miss a reply on the list, so if anyone is
interested
in the IGMPv3 stuff, I'd be grateful if you could CC
the
reply to imipak@yahoo.com. Also, if anyone else is
working on Linux IGMPv3 code, if they could drop me a
note, it would be helpful. Diversity is a good thing,
but
too much causes migranes in 8 out of 10 cats.

Thanks,

Jonathan Day


__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

[-- Attachment #2: igmp-patch.gz --]
[-- Type: application/x-gzip, Size: 3400 bytes --]

                 reply	other threads:[~2001-12-28 20:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20011228202724.99671.qmail@web12303.mail.yahoo.com \
    --to=imipak@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®