RE: [ssm] Igmpv3 - Experiment-1

"Stepping, Michael" <michael.stepping@fernuni-hagen.de> Tue, 19 August 2003 07:53 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00883 for <ssm-archive@lists.ietf.org>; Tue, 19 Aug 2003 03:53:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19p1Ic-00028N-5r; Tue, 19 Aug 2003 03:53:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19p1IQ-00027x-C6 for ssm@optimus.ietf.org; Tue, 19 Aug 2003 03:52:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00845 for <ssm@ietf.org>; Tue, 19 Aug 2003 03:52:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19p1IN-0005hn-00 for ssm@ietf.org; Tue, 19 Aug 2003 03:52:47 -0400
Received: from oak.fernuni-hagen.de ([132.176.114.41]) by ietf-mx with esmtp (Exim 4.12) id 19p1IN-0005hX-00 for ssm@ietf.org; Tue, 19 Aug 2003 03:52:47 -0400
Received: from amavis by oak.FernUni-Hagen.de with scanned-ok (Exim 4.04) id 19p1Ht-00025A-00; Tue, 19 Aug 2003 09:52:17 +0200
Received: from lgks2.fernuni-hagen.de ([132.176.12.66]) by oak.FernUni-Hagen.de with esmtp (Exim 4.04) id 19p1Hl-00024a-00; Tue, 19 Aug 2003 09:52:09 +0200
Received: from LGKS2/SpoolDir by lgks2.fernuni-hagen.de (Mercury 1.48); 19 Aug 03 09:52:10 +0200
Received: from SpoolDir by LGKS2 (Mercury 1.48); 19 Aug 03 09:52:01 +0200
Received: from notebookms (132.176.12.154) by lgks2.fernuni-hagen.de (Mercury 1.48); 19 Aug 03 09:51:55 +0200
From: "Stepping, Michael" <michael.stepping@fernuni-hagen.de>
To: <srinivask@future.futsoft.com>, <ssm@ietf.org>
Subject: RE: [ssm] Igmpv3 - Experiment-1
Date: Tue, 19 Aug 2003 09:51:54 +0200
Message-ID: <NHBBIKJKCDACDGJNEKHPKEOPDKAA.michael.stepping@fernuni-hagen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 5 (Lowest)
X-MSMail-Priority: Low
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Low
In-Reply-To: <004d01c3660f$965807c0$7904060a@future.futsoft.com>
X-Virus-Scanned: by AMaViS perl-11
Content-Transfer-Encoding: 7bit
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

> - I want to know also whether this full state igmpv3  support is ethernet
> card
> vendor specific,means some vendor cards have this support and
> some may not.
> like 3c59x driver may have and 8139too realtek driver .does not have.
>

In modern up-to-date Operating Systems usually the Ethernet-Frame
is built in Software, means by a loadable driver. Therefore (Ethernet)
Hardware provides only a MAC-Interface (Medium Access Control).

Example:
You want to transmit a frame, let us say an RTP/UDP/IP frame.
Usually you built an application where it is your task to build
an RTP frame including RTP header. Then you ask the socket
to establish an UDP (Datagram) Socket and put this self-built frame
to the socket (so far nothing new, I assume).
Then usually the TCP/IP Kernel Driver catches this frame and adds
in this case the UDP header. After that the IP header is built in front.
Now nearly all Operating Systems have built-in a tool with the meaning
"Protocol Manager".
This Protocol Manager manages now that your IP frame is
diverted to the correct netcard. The netcard provides access by the MAC
interface.
(In MS Windows OS this is a part of the NDIS (Network Describing
Interface Specification) interface, in Novell this interface is called ODI,
for Linux
I need a hint.)
Usually the netcard driver adds the protocol specific headers and the
netcard hardware adds the necessary checksums and introductions (PLLs...).

That was a long story. The result: In the last 15 years the netcards
provided more or less a raw access. It is easier to exchange a piece of
software
than exchanging a monolithic netcard.
So, IGMP is a topic of the IP stack and is not influenced by your netcard.
(Of course there could be bugs in the software that do not initialize the
netcard correct or set filters for the several frames wrong or ....)

If I am wrong, please correct me.

Michael


_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm