From owner-idmr@cs.ucl.ac.uk  Sun Sep  2 11:22:05 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11515
	for <idmr-archive@lists.ietf.org>; Sun, 2 Sep 2001 11:22:04 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.17886-0@pan2.cs.ucl.ac.uk>;
          Sun, 2 Sep 2001 15:30:24 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.17809-0@pan2.cs.ucl.ac.uk>; Sun, 2 Sep 2001 09:30:00 +0100
Received: from smtp-rt-2.wanadoo.fr by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.03179-0@bells.cs.ucl.ac.uk>; Sun, 2 Sep 2001 09:30:02 +0100
Received: from andira.wanadoo.fr (193.252.19.152) by apeiba.wanadoo.fr;
          2 Sep 2001 10:30:01 +0200
Received: from gtrpc19 (193.249.112.119) by andira.wanadoo.fr;
          2 Sep 2001 10:29:59 +0200
Message-Id: <3.0.1.32.20010902102048.0069b774@pop.mail.yahoo.com>
X-Sender: g2rtc@pop.mail.yahoo.com
X-Mailer: Windows Eudora Pro Version 3.0.1 (32) [F]
Date: Sun, 02 Sep 2001 10:20:48 +0200
To: conf@uha.fr
From: conf <conf@uha.fr>
Subject: CfP of HSNMC'02
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA11515

Dear Sir,

Could you find attached the CfP of HSNMC'02.
See also http://iutsun1.colmar.uha.fr/HSNMC02.html

Regards,
-----------------------------------------------------------------------
 
 CALL FOR PAPERS
5th International Conference on
 High-Speed Networks and Multimedia Communications
HSNMC'02
July 3-5, 2002 – Jeju Island, Korea
 

 GENERAL INFORMATION 

The 2002 IEEE International Conference on High-Speed Networks and
Multimedia Communications is sponsored by the IEEE, IEE and WSES. ICHSN'02
is organized by academic, research and industrial societies will be held at
Jeju, Korea, from Wednesday July 3, 2002 to Friday July 5, 2002 (just after
the soccer World Cup).

Cheju (Jeju) island known as a place of fantasy or mystery is most
beautiful island in Korea and is located in the southwest sea of the Korean
peninsula and is highlighted for its uniqueness.

In order to encourage closer interaction between academic and industrial
networking research communities, we solicit both academic research papers
and industrial contributions. 

TOPICS OF SPECIAL INTEREST 

Topics of interest include, but are not limited to the following: 
  

Traffic models

LAN Emulation

IP over ATM, IPv6 over ATM 

VLANs 

High-Speed Routing 

I-PNNI, NHRP 

Java, Tina, Corba architectures 

Interconnection 

Network Management, performance 

CTI (Computer Telephony Integration) 

Multicast ATM and Internet/Intranet
 IP and ATM over xDSL
Security

IP and ATM Telephony 

Practical experiences results 

User applications 

Video (Davic, ...) 

QoS 

WDM 

Optical Switching 

Scheduling & Resource allocation 

Services over ATM
 
MPOA, IP Switching, MPLS, Tag Switching, Fast IP, Aris ...

Wireless ATM (LEO,MEO GEO, from GSM to UMTS and IMT2000 Hyperlan2, ...)
 

These topics can be discussed in term of concepts, state of the art,
standards, implementations, performance, security and confidentiality,
traffic management, running experiments, QoS (Quality of Service) and
applications. 
  

INSTRUCTIONS FOR AUTHORS 

Mail four copies of a full paper, which should be no longer than 10 pages
or an extended abstract summarizing an original work. All the manuscripts
must be written in English. The top of the first page of each paper should
include the title of the paper, authors' name, position, address, telephone
and fax numbers, e-mail of the author responsible for correspondence and a
list of four keywords. Electronic submissions are strongly encouraged.
Acceptable formats are PDF, Postscript, RTF, and Word 97. Please use A4
paper format when formatting your submission! Authors of accepted papers
will later be required to submit a IEEE copyright form, please assure that
you have all necessary authorizations in place.

Authors of accepted papers will be invited to submit full-length
manuscripts for inclusion in the proceedings. 

All submitted papers should be sent to the following address: 

For the worldwide: 

Mike Myung-Ok LEE 

IDEC 

Dongshin University 

252 Daeho-Dong, Naju 

Chonnam, 520-714 Korea 

Phone:82(0)613-330-3195 Fax:82(0)613-330-2911 Mobile:82(0)16-612-2925 

E-mail: mykelee@kornet.net

  

For Europe : 

Pascal LORENZ 

University of Haute Alsace 

IUT - Department GTR 

34 rue du Grillenbreit 

68008 Colmar, France 

Phone: 33 (0)389202366 Fax: 33 (0)389202359 Mobile: 33 (0)603658042 

E-mail: lorenzp@computer.org

Check our Web page at http://iutsun1.colmar.uha.fr/HSNMC02.html for the
latest information concerning the conference. Best papers will be forwarded
for consideration in a special issue of the journal Telecommunication
Systems published by Baltzer Science Publishers. 

TUTORIALS AND WORKSHOPS 

Tutorials and workshops provide overviews of current high interest topics.
Proposals for half of full day tutorials are due by December 10, 2001. 

INTERNATIONAL ADVISORY COMMITTEE 

R. Addie (Australia) - University of Southern Queensland 

K. Begain (Jordan) - Mu'tah University 

A. Benslimane (France) - University of Belfort 

B. Bing (Singapore) - Ngee Ann Polytechnic 

D. Bonjour (France) - CNET 

A. Brandwajn (USA) - University of California Santa Cruz 

J.P. Coudreuse (France) - Mitsubishi 

J. Crowcroft (UK) - University College London 

B. Gavish (USA) - Vanderbilt University 

J. Halpern (USA) - Newbridge 

Z. Hulicki (Poland) - University of Cracow 

R. Israel (France) - IEEE 

S. Komandur (USA) - Ascend Communications 

D. Kouvatsos (UK) - University of Bradford 

S. Kumar (USA) - Ericsson 

G.S. Kuo (Taiwan) - National Central University 

F. Le Faucheur (France) - Cisco 

M. Lee (Korea) - Dongshin University 

P. Lorenz (France) - University of Haute Alsace 

G. Omidyar (USA) - Computer Sciences Corp. 

J.J. Pansiot (France) - University of Strasbourg 

M. Potts (Switzerland) - Martel 

Z. Mammeri (France) - University of Toulouse 

N. Mastorakis (Greece) - Military Institutions of University Education 

S. Moyer (USA) - Bellcore 

R. Muraine (France) - Newbridge 

G. Pujolle (France) - University of Versailles-Saint-Quentin 

S. Rao (Switzerland) - Ascom 

A. Reid (UK) - British Telecom 

S. Ritzenthaler (France) - Newbridge 

P. Rolin (France) - ENST Bretagne 

R. Saracco (Italy) - CSELT 

G. Swallow (USA) - Cisco 

H. Tobiet (France) - Clemessy 

V.A. Villagra (Spain) - University of Madrid 

E. Vazquez Gallo (Spain) - University of Madrid 

IMPORTANT DATES 

Extended Abstract due: January 20, 2002 

Notification of acceptance: February 28, 2002

Deadline for full-length camera-ready manuscript: March 30, 2002




From owner-idmr@cs.ucl.ac.uk  Wed Sep  5 05:18:24 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA21967
	for <idmr-archive@lists.ietf.org>; Wed, 5 Sep 2001 05:18:24 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.18883-0@pan2.cs.ucl.ac.uk>;
          Wed, 5 Sep 2001 09:30:07 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.18876-0@pan2.cs.ucl.ac.uk>; Wed, 5 Sep 2001 09:30:01 +0100
Received: from london.cisco.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.06507-0@bells.cs.ucl.ac.uk>; Wed, 5 Sep 2001 09:30:02 +0100
Received: from BRMCLAUG-W2K1.cisco.com (brmclaug-isdn-home.cisco.com [10.49.128.246]) 
          by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id JAA17879;
          Wed, 5 Sep 2001 09:28:45 +0100 (BST)
Message-Id: <4.3.2.7.2.20010905091527.01ddd2c8@london.cisco.com>
X-Sender: brmclaug@london.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 05 Sep 2001 09:28:49 +0100
To: "hitesh rupare;" <catchhitesh@hotmail.com>
From: Bryan Mclaughlin <brmclaug@cisco.com>
Subject: Re: question
Cc: bwilliam@cisco.com, John.Zwiebel@procket.com, brmclaug@cisco.com,
        pim@catarina.usc.edu, magma@innovationslab.net, idmr@cs.ucl.ac.uk,
        tme@multicasttech.com
In-Reply-To: <F226E8pnCI4hwZN7O6i00005295@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Hitesh,

"the mac addr is hard-coded on to the card " this is the address used  as a 
source or as a destination in unicast communication.

Remeber the destination in IPmulticast is not a physical device but a 
virtual group.

The destination MAc address of an IP Multicast frame is set as follows:

Organisational Unit Identifier; 00.00.5E  as you say the least significant 
bit of the most significant byte is set to 1 to indicate 
Broadcast/Multicast so the OUI becomes 01.00.5E:

To have a 1-1 mapping would have required 16 OUI's only 1 was made 
available to Steve Deering. In fact he was only given 1/2 of the above 
OUI.  So a possible 24 bits to map from IP add to MAC address became only 
23 bits.
You will notice there are now 32 possible address that map to the each MAC 
address.

01.00.5E.01.01.01

224.1.1.1
224.129.1.1
.
.
239.129.1.1

Hope this helps





At 20:44 04/09/2001 -0500, hitesh rupare; wrote:
>hi,
>
>the mac addr is hard-coded on to the card ... how then can one map the 28 
>bits of the ip addr onto 23 bits of the mac addr ?
>
>also bit 0 in octet 7 has to be set to 1 for broadcast/multicast ... how 
>is this bit set ?
>
>rgds
>hitesh
>
>
>
>>From: Beau Williamson <bwilliam@cisco.com>
>>To: John Zwiebel <John.Zwiebel@procket.com>,        Bryan Mclaughlin 
>><brmclaug@cisco.com>, pim@catarina.usc.edu,        MAGMA Mailing List 
>><magma@innovationslab.net>, idmr@cs.ucl.ac.uk
>>Subject: Re: draft-ietf-pim-dm-new-v2-04.txt
>>Date: Wed, 01 Aug 2001 16:37:59 -0500
>>
>>John,
>>
>>Once again I think you and I are on the same wavelength.  I'd like to see 
>>MSNIP evolve into something more like the RTS/CTS mechanism that you 
>>describe with sufficient specifications as to how the first hop device 
>>(maybe a router or maybe a layer-3 aware switch) should handle this.
>>
>>In addition, I'd like to see "receiver" admission control added if at all 
>>possible.  I'm not convinced that this would require a extension to IGMP 
>>or a new protocol and may actual fall into vendor specific features.
>>
>>In any case, the worries over DoS Attacks due to random sourcing and 
>>random joining (especially if SSM takes off) are real and are quickly 
>>becoming a barrier to multicast deployment.
>>
>>Maybe this can be discussed at the MAGMA WG in London.  Unfortunately, I 
>>won't be there so I'm hoping you or someone else will carry the 
>>flag.  (At least initially.)
>>
>>Beau
>>At 01:26 PM 7/31/2001, John Zwiebel wrote:
>> >Bryan Mclaughlin wrote:
>> >>
>> >> This issue is addressed by Multicast Source Notification of Interest
>> >> Protocol (MSNIP)  for SM protocols,  isn't it ? What would need to be 
>> added
>> >> to make it work for DM?
>> >>
>> >
>> >MSNIP does not do admission control.  It "kind of" does it, but
>> >there's nothing that prevents a source from dumping mpackets on to the
>> >LAN.
>> >And MSNIP does not specifically address what a router should do if
>> >it sees packets from a source that hasn't registered via MSNIP.
>> >(one could make the leap that in such a case the router could just
>> >bit bucket the data stream)
>> >
>> >The host (source) is still "in charge" and the network has to muddle
>> >through the best it can.  If a host is sending and there is no MSNIP
>> >available, there's nothing to stop it.
>> >
>> >The RTS/CTS process I'd like to see would make the network more
>> >"superior" to the host and is quite a bit more complicated than what
>> >MSNIP is trying to provide.
>> >
>> >I guess this sentence from the MSNIP draft makes my point:
>> >
>> >     Hosts that wish to be managed by MSNIP periodically transmit an
>> >     Interest Solicitation message. This message is multicast with a
>> >group
>> >     destination address of ALL_IGMPv3_ROUTERS (224.0.0.22) and is
>> >     transmitted every [Interest Solicitation Interval] seconds.
>> >
>> >  -- MSNIP is IGMPv3 only
>> >  -- Hosts can arbitrarily decide to not be managed by MSNIP
>> >  -- MSNIP does not describe how to signal the "network" that the
>> >        source is about to send.
>> >
>> >This shouldn't be taken as a condemnation of MSNIP.  Its quite
>> >possible my imagination just isn't strong enough to grasp the
>> >capabilities.  And what I think is needed may be way too complicated
>> >and contrary to the "spirit of the internet".
>
>
>_________________________________________________________________
>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp



Bryan Mclaughlin
Technical Marketing Engineer	            Telephone :+44 (0)20 8756 8811
IOS Technology Division 		Email        :brmclaug@cisco.com
Cisco Systems			Mobile       :+44 (0)7710 164487



From owner-idmr@cs.ucl.ac.uk  Wed Sep  5 07:31:33 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA24494
	for <idmr-archive@lists.ietf.org>; Wed, 5 Sep 2001 07:31:32 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.18932-0@pan2.cs.ucl.ac.uk>;
          Wed, 5 Sep 2001 11:54:02 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.18752-0@pan2.cs.ucl.ac.uk>; Wed, 5 Sep 2001 02:44:18 +0100
Received: from f226.law14.hotmail.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.15831-0@bells.cs.ucl.ac.uk>; Wed, 5 Sep 2001 02:44:21 +0100
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
          Tue, 4 Sep 2001 18:44:19 -0700
Received: from 134.193.128.191 by lw14fd.law14.hotmail.msn.com with HTTP;
          Wed, 05 Sep 2001 01:44:19 GMT
X-Originating-IP: [134.193.128.191]
From: "hitesh rupare;" <catchhitesh@hotmail.com>
To: bwilliam@cisco.com, John.Zwiebel@procket.com, brmclaug@cisco.com,
        pim@catarina.usc.edu, magma@innovationslab.net, idmr@cs.ucl.ac.uk
Cc: tme@multicasttech.com
Subject: question
Date: Tue, 04 Sep 2001 20:44:19 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F226E8pnCI4hwZN7O6i00005295@hotmail.com>
X-OriginalArrivalTime: 05 Sep 2001 01:44:19.0769 (UTC) 
                       FILETIME=[47C2F290:01C135AC]
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

hi,

the mac addr is hard-coded on to the card ... how then can one map the 28 
bits of the ip addr onto 23 bits of the mac addr ?

also bit 0 in octet 7 has to be set to 1 for broadcast/multicast ... how is 
this bit set ?

rgds
hitesh



>From: Beau Williamson <bwilliam@cisco.com>
>To: John Zwiebel <John.Zwiebel@procket.com>,        Bryan Mclaughlin 
><brmclaug@cisco.com>, pim@catarina.usc.edu,        MAGMA Mailing List 
><magma@innovationslab.net>, idmr@cs.ucl.ac.uk
>Subject: Re: draft-ietf-pim-dm-new-v2-04.txt
>Date: Wed, 01 Aug 2001 16:37:59 -0500
>
>John,
>
>Once again I think you and I are on the same wavelength.  I'd like to see 
>MSNIP evolve into something more like the RTS/CTS mechanism that you 
>describe with sufficient specifications as to how the first hop device 
>(maybe a router or maybe a layer-3 aware switch) should handle this.
>
>In addition, I'd like to see "receiver" admission control added if at all 
>possible.  I'm not convinced that this would require a extension to IGMP or 
>a new protocol and may actual fall into vendor specific features.
>
>In any case, the worries over DoS Attacks due to random sourcing and random 
>joining (especially if SSM takes off) are real and are quickly becoming a 
>barrier to multicast deployment.
>
>Maybe this can be discussed at the MAGMA WG in London.  Unfortunately, I 
>won't be there so I'm hoping you or someone else will carry the flag.  (At 
>least initially.)
>
>Beau
>At 01:26 PM 7/31/2001, John Zwiebel wrote:
> >Bryan Mclaughlin wrote:
> >>
> >> This issue is addressed by Multicast Source Notification of Interest
> >> Protocol (MSNIP)  for SM protocols,  isn't it ? What would need to be 
>added
> >> to make it work for DM?
> >>
> >
> >MSNIP does not do admission control.  It "kind of" does it, but
> >there's nothing that prevents a source from dumping mpackets on to the
> >LAN.
> >And MSNIP does not specifically address what a router should do if
> >it sees packets from a source that hasn't registered via MSNIP.
> >(one could make the leap that in such a case the router could just
> >bit bucket the data stream)
> >
> >The host (source) is still "in charge" and the network has to muddle
> >through the best it can.  If a host is sending and there is no MSNIP
> >available, there's nothing to stop it.
> >
> >The RTS/CTS process I'd like to see would make the network more
> >"superior" to the host and is quite a bit more complicated than what
> >MSNIP is trying to provide.
> >
> >I guess this sentence from the MSNIP draft makes my point:
> >
> >     Hosts that wish to be managed by MSNIP periodically transmit an
> >     Interest Solicitation message. This message is multicast with a
> >group
> >     destination address of ALL_IGMPv3_ROUTERS (224.0.0.22) and is
> >     transmitted every [Interest Solicitation Interval] seconds.
> >
> >  -- MSNIP is IGMPv3 only
> >  -- Hosts can arbitrarily decide to not be managed by MSNIP
> >  -- MSNIP does not describe how to signal the "network" that the
> >        source is about to send.
> >
> >This shouldn't be taken as a condemnation of MSNIP.  Its quite
> >possible my imagination just isn't strong enough to grasp the
> >capabilities.  And what I think is needed may be way too complicated
> >and contrary to the "spirit of the internet".
>


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp



From owner-idmr@cs.ucl.ac.uk  Wed Sep  5 07:31:45 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA24524
	for <idmr-archive@lists.ietf.org>; Wed, 5 Sep 2001 07:31:44 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.18968-0@pan2.cs.ucl.ac.uk>;
          Wed, 5 Sep 2001 11:55:21 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.18897-0@pan2.cs.ucl.ac.uk>; Wed, 5 Sep 2001 09:46:02 +0100
Received: from oak.fernuni-hagen.de by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.07382-0@bells.cs.ucl.ac.uk>; Wed, 5 Sep 2001 09:45:59 +0100
Received: from lgks2.fernuni-hagen.de by oak.fernuni-hagen.de via local-channel 
          with ESMTP; Wed, 5 Sep 2001 10:45:06 +0200
Received: from LGKS2/SpoolDir by lgks2.fernuni-hagen.de (Mercury 1.48);
          5 Sep 01 10:44:57 +0200
Received: from SpoolDir by LGKS2 (Mercury 1.48); 5 Sep 01 10:44:26 +0200
Received: from brinkhoffs (132.176.12.154) 
          by lgks2.fernuni-hagen.de (Mercury 1.48); 5 Sep 01 10:44:20 +0200
From: "Stepping, Michael" <michael.stepping@FernUni-Hagen.de>
To: "hitesh rupare;" <catchhitesh@hotmail.com>, pim <pim@catarina.usc.edu>,
        magma <magma@innovationslab.net>, idmr <idmr@cs.ucl.ac.uk>
Cc: tme <tme@multicasttech.com>
Subject: RE: question
Date: Wed, 5 Sep 2001 10:44:18 +0200
Message-ID: <NCBBKPDPCLFPBJHIIIBKCEBLFOAA.michael.stepping@fernuni-hagen.de>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <F226E8pnCI4hwZN7O6i00005295@hotmail.com>
Disposition-Notification-To: "Stepping, Michael" 
                             <michael.stepping@fernuni-hagen.de>
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Hitesh,

I am jumping in this thread and therefor I assume, you are talking about
IGMP,
which is the location where a mapping of IP-Adresses (IPv4 32 Bit) to
Mac-Adresses
(Ethernet MAC 48 Bits) happens.

First of all: Ethernet Cards have a register which proposes a
world-wide unique MAC Address, which consists of first three bytes are
manufacturer,
last three bytes are serial number. (This explains the cry of using this
number
in the Microsoft Word Documents.)
This MAC Address (48bit) can be reconfigured with standard mechanisms like
NDIS or ODI interface programming (on Windows and Novell machines).
DecNet reconfigured always this adress.

Second:
IP-Class D adresses are IP-Multicast adresses and therefore the last 28 bit
(out
of 32 bit) are significant.
Ethernet adresses have a tag for Ethernet-Multicast MAC Address (currently
not in my mind) and therefore the last 23 bits are significant.

Third: Mapping:
Take the last 23 bits of the IPv4-Multicast adress and fill these to the
Ethernet MAC Adress. That is all.

Question: But there are multiple IP-Multicast adresses mappable on
one Ethernet-MAC-Multicast Adress?

That is true, but a) that happens not that often in real and
b) the upper IP-Multicast layer can decide if this IPv4-Multicast traffic
is required.

Keep in mind: There are other topologies than Ethernet underlying IP layer.
(Token Ring, Fiber, etc.)


Michael


>
>
> hi,
>
> the mac addr is hard-coded on to the card ... how then can one map the 28
> bits of the ip addr onto 23 bits of the mac addr ?
>
> also bit 0 in octet 7 has to be set to 1 for broadcast/multicast
> ... how is
> this bit set ?
>

For Ethernet there are only 6 octets. Did I mis the point?

Michael



From owner-idmr@cs.ucl.ac.uk  Wed Sep  5 09:50:29 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA01834
	for <idmr-archive@lists.ietf.org>; Wed, 5 Sep 2001 09:50:29 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.19090-0@pan2.cs.ucl.ac.uk>;
          Wed, 5 Sep 2001 13:59:57 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.19013-0@pan2.cs.ucl.ac.uk>; Wed, 5 Sep 2001 12:17:30 +0100
Received: from ids2.idsonline.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.18314-0@bells.cs.ucl.ac.uk>; Wed, 5 Sep 2001 12:17:20 +0100
Received: from idsonline.com (nobody@ids2.idsonline.com [205.177.236.32]) 
          by ids2.idsonline.com (8.11.1/8.11.1) with SMTP id f85BLT802557;
          Wed, 5 Sep 2001 07:21:29 -0400
From: Marshall Eubanks <tme@21rst-century.com>
Reply-to: tme@21rst-century.com
To: "hitesh rupare;" <catchhitesh@hotmail.com>, bwilliam@cisco.com,
        John.Zwiebel@procket.com, brmclaug@cisco.com, pim@catarina.usc.edu,
        magma@innovationslab.net, idmr@cs.ucl.ac.uk, tme@multicasttech.com
Date: Wed, 5 Sep 2001 07:21:30 -0400
Subject: Re: [Magma] question
X-Mailer: DMailWeb Web to Mail Gateway 2.6k, http://netwinsite.com/top_mail.htm
Message-id: <3b960aba.9f7.0@idsonline.com>
X-User-Info: 63.23.125.116
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

>hi,
>
>the mac addr is hard-coded on to the card ... how then can one map the 28 

>bits of the ip addr onto 23 bits of the mac addr ?

Hello Hitesh;

   I hope things are well. The Class D to Ethernet MAC mapping
is described in 
http://www.multicasttech.com/faq/multicast_faq.html
amoung many other places. Collisions are indeed possible.

>
>also bit 0 in octet 7 has to be set to 1 for broadcast/multicast ... how is

>this bit set ?
>
Bit zero of Octet zero of any MAC address is zero for Layer 2
unicast, one for layer two multicast. (Every OUI thus contains
lots of multicast addresses!) The 23 bit for multicast is
for the mapping of Internet group addresses to MAC, and
is a historical accident.

Note that Ethernet MACs are big-endian, and so bit 0 of 
octet 0 is actually the 8th bit encountered.

Marshall

>rgds
>hitesh
>
>
Marshall Eubanks

tme@21rst-century.com


From owner-idmr@cs.ucl.ac.uk  Wed Sep  5 19:42:13 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA24970
	for <idmr-archive@lists.ietf.org>; Wed, 5 Sep 2001 19:42:10 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.19505-0@pan2.cs.ucl.ac.uk>;
          Thu, 6 Sep 2001 00:01:28 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.19499-0@pan2.cs.ucl.ac.uk>; Thu, 6 Sep 2001 00:01:22 +0100
Received: from london.cisco.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.04289-0@bells.cs.ucl.ac.uk>; Thu, 6 Sep 2001 00:01:19 +0100
Received: from BRMCLAUG-W2K1.cisco.com (brmclaug-isdn-home.cisco.com [10.49.128.246]) 
          by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id XAA01365;
          Wed, 5 Sep 2001 23:59:59 +0100 (BST)
Message-Id: <4.3.2.7.2.20010905235015.01f82cd0@london.cisco.com>
X-Sender: brmclaug@london.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 05 Sep 2001 23:59:59 +0100
To: "hitesh rupare;" <catchhitesh@hotmail.com>
From: Bryan Mclaughlin <brmclaug@cisco.com>
Subject: Re: question
Cc: brmclaug@cisco.com, bwilliam@cisco.com, John.Zwiebel@procket.com,
        pim@catarina.usc.edu, magma@innovationslab.net, idmr@cs.ucl.ac.uk,
        tme@multicasttech.com
In-Reply-To: <F49a3rFAFl5pVVc4t3x00007d0a@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

At 16:35 05/09/2001 -0500, hitesh rupare; wrote:
>hi,
>
>
>>"the mac addr is hard-coded on to the card " this is the address used  as a
>>source or as a destination in unicast communication.
>
>do you mean that the actual hard coded mac address is used only for 
>unicast and has nothing to do with multicast ?


Yes



>>Remeber the destination in IPmulticast is not a physical device but a
>>virtual group.
>
>
>i can understand that  this is how it works at the network layer ( ip ) 
>but i cant visualise this happening on mac layer or for physical 
>addresses...when they talk about mapping the last 28 bits of the group
>address to 23 bits of mac adddr what are they talking about ?


How can a Network layer Multicast address meant for *many* destinations use 
a real MAc address?

Answer by having the NIC listen not only to its *real* MAC address but also 
to other MAC address that correspond to the "virtual" address of the 
IPmulticast group.



>it seems ridiculous to me that if  the mac address of my card begins with 
>01-00-5e only then i can get multicast ...



You still have your regular MAC address but the NIC is also listening to 
the frames with the oui above




>i understand that this is not how it works but i have no explanation here 
>.... there has to be some way ( i know there is but i havent found this 
>anywhere ) that my mac address is overridden somehow by the last 23 bits 
>of the group address... i dont understand how and when this happens...

try

ftp://ftpeng.cisco.com/ipmulticast/whitepapers/technology_overview/index.html#xtocid51123


>rgds
>hitesh
>
>
>
>
>>
>>The destination MAc address of an IP Multicast frame is set as follows:
>>
>>Organisational Unit Identifier; 00.00.5E  as you say the least significant
>>bit of the most significant byte is set to 1 to indicate
>>Broadcast/Multicast so the OUI becomes 01.00.5E:
>>
>>To have a 1-1 mapping would have required 16 OUI's only 1 was made
>>available to Steve Deering. In fact he was only given 1/2 of the above
>>OUI.  So a possible 24 bits to map from IP add to MAC address became only
>>23 bits.
>>You will notice there are now 32 possible address that map to the each MAC
>>address.
>>
>>01.00.5E.01.01.01
>>
>>224.1.1.1
>>224.129.1.1
>>.
>>.
>>239.129.1.1
>>
>>Hope this helps
>>
>>
>>
>>
>>
>>At 20:44 04/09/2001 -0500, hitesh rupare; wrote:
>>>hi,
>>>
>>>the mac addr is hard-coded on to the card ... how then can one map the 28
>>>bits of the ip addr onto 23 bits of the mac addr ?
>>>
>>>also bit 0 in octet 7 has to be set to 1 for broadcast/multicast ... how
>>>is this bit set ?
>>>
>>>rgds
>>>hitesh
>>>
>>>
>>>
>>>>From: Beau Williamson <bwilliam@cisco.com>
>>>>To: John Zwiebel <John.Zwiebel@procket.com>,        Bryan Mclaughlin
>>>><brmclaug@cisco.com>, pim@catarina.usc.edu,        MAGMA Mailing List
>>>><magma@innovationslab.net>, idmr@cs.ucl.ac.uk
>>>>Subject: Re: draft-ietf-pim-dm-new-v2-04.txt
>>>>Date: Wed, 01 Aug 2001 16:37:59 -0500
>>>>
>>>>John,
>>>>
>>>>Once again I think you and I are on the same wavelength.  I'd like to see
>>>>MSNIP evolve into something more like the RTS/CTS mechanism that you
>>>>describe with sufficient specifications as to how the first hop device
>>>>(maybe a router or maybe a layer-3 aware switch) should handle this.
>>>>
>>>>In addition, I'd like to see "receiver" admission control added if at all
>>>>possible.  I'm not convinced that this would require a extension to IGMP
>>>>or a new protocol and may actual fall into vendor specific features.
>>>>
>>>>In any case, the worries over DoS Attacks due to random sourcing and
>>>>random joining (especially if SSM takes off) are real and are quickly
>>>>becoming a barrier to multicast deployment.
>>>>
>>>>Maybe this can be discussed at the MAGMA WG in London.  Unfortunately, I
>>>>won't be there so I'm hoping you or someone else will carry the
>>>>flag.  (At least initially.)
>>>>
>>>>Beau
>>>>At 01:26 PM 7/31/2001, John Zwiebel wrote:
>>>> >Bryan Mclaughlin wrote:
>>>> >>
>>>> >> This issue is addressed by Multicast Source Notification of Interest
>>>> >> Protocol (MSNIP)  for SM protocols,  isn't it ? What would need to be
>>>>added
>>>> >> to make it work for DM?
>>>> >>
>>>> >
>>>> >MSNIP does not do admission control.  It "kind of" does it, but
>>>> >there's nothing that prevents a source from dumping mpackets on to the
>>>> >LAN.
>>>> >And MSNIP does not specifically address what a router should do if
>>>> >it sees packets from a source that hasn't registered via MSNIP.
>>>> >(one could make the leap that in such a case the router could just
>>>> >bit bucket the data stream)
>>>> >
>>>> >The host (source) is still "in charge" and the network has to muddle
>>>> >through the best it can.  If a host is sending and there is no MSNIP
>>>> >available, there's nothing to stop it.
>>>> >
>>>> >The RTS/CTS process I'd like to see would make the network more
>>>> >"superior" to the host and is quite a bit more complicated than what
>>>> >MSNIP is trying to provide.
>>>> >
>>>> >I guess this sentence from the MSNIP draft makes my point:
>>>> >
>>>> >     Hosts that wish to be managed by MSNIP periodically transmit an
>>>> >     Interest Solicitation message. This message is multicast with a
>>>> >group
>>>> >     destination address of ALL_IGMPv3_ROUTERS (224.0.0.22) and is
>>>> >     transmitted every [Interest Solicitation Interval] seconds.
>>>> >
>>>> >  -- MSNIP is IGMPv3 only
>>>> >  -- Hosts can arbitrarily decide to not be managed by MSNIP
>>>> >  -- MSNIP does not describe how to signal the "network" that the
>>>> >        source is about to send.
>>>> >
>>>> >This shouldn't be taken as a condemnation of MSNIP.  Its quite
>>>> >possible my imagination just isn't strong enough to grasp the
>>>> >capabilities.  And what I think is needed may be way too complicated
>>>> >and contrary to the "spirit of the internet".
>>>
>>>
>>>_________________________________________________________________
>>>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>>
>>
>>
>>Bryan Mclaughlin
>>Technical Marketing Engineer                Telephone :+44 (0)20 8756 8811
>>IOS Technology Division                 Email        :brmclaug@cisco.com
>>Cisco Systems                   Mobile       :+44 (0)7710 164487
>
>
>_________________________________________________________________
>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp



Bryan Mclaughlin
Technical Marketing Engineer	            Telephone :+44 (0)20 8756 8811
IOS Technology Division 		Email        :brmclaug@cisco.com
Cisco Systems			Mobile       :+44 (0)7710 164487



From owner-idmr@cs.ucl.ac.uk  Wed Sep  5 19:42:21 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA24982
	for <idmr-archive@lists.ietf.org>; Wed, 5 Sep 2001 19:42:21 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.19545-0@pan2.cs.ucl.ac.uk>;
          Thu, 6 Sep 2001 00:16:55 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.19454-0@pan2.cs.ucl.ac.uk>; Wed, 5 Sep 2001 22:55:59 +0100
Received: from lennon.multicasttech.com by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.00433-0@bells.cs.ucl.ac.uk>;
          Wed, 5 Sep 2001 22:55:49 +0100
Received: from [63.105.122.193] (account marshall_eubanks HELO 21rst-century.com) 
          by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP 
          id 1075393; Wed, 05 Sep 2001 17:49:36 -0400
Message-ID: <3B969F66.4EB2BEF2@21rst-century.com>
Date: Wed, 05 Sep 2001 17:55:49 -0400
From: Marshall Eubanks <tme@21rst-century.com>
Reply-To: tme@21rst-century.com
Organization: Multicast Technologies
X-Mailer: Mozilla 4.7C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; I; PPC)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "hitesh rupare;" <catchhitesh@hotmail.com>
CC: brmclaug@cisco.com, bwilliam@cisco.com, John.Zwiebel@procket.com,
        pim@catarina.usc.edu, magma@innovationslab.net, idmr@cs.ucl.ac.uk,
        tme@multicasttech.com
Subject: Re: [Magma] Re: question
References: <F49a3rFAFl5pVVc4t3x00007d0a@hotmail.com>
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; 
              x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

"hitesh rupare;" wrote:

> hi,
>
> >"the mac addr is hard-coded on to the card " this is the address used  as a
> >source or as a destination in unicast communication.
>
> do you mean that the actual hard coded mac address is used only for unicast
> and has nothing to do with multicast ?

Yes.

>
>
> >
> >Remeber the destination in IPmulticast is not a physical device but a
> >virtual group.
>
> i can understand that  this is how it works at the network layer ( ip ) but
> i cant visualise this happening on mac layer or for physical
> addresses...when they talk about mapping the last 28 bits of the group
> address to 23 bits of mac adddr what are they talking about ?
>
> it seems ridiculous to me that if  the mac address of my card begins with
> 01-00-5e only then i can get multicast ... i understand that this is not how
> it works but i have no explanation here .... there has to be some way ( i
> know there is but i havent found this anywhere ) that my mac address is
> overridden somehow by the last 23 bits of the group address... i dont
> understand how and when this happens...

Dear Hitesh;

When you start to send an IP multicast packet, or when a router or a switch receives a
multicast IP packet to go onto the LAN, it is supposed to encapsulate it in an ethernet packet
with the 01-00-5e-XYZ MAC address.

When you receive, the NIC card of your ethernet device is supposed to recognize the
01-00-5e-XYZ address and pass it up to the CPU for processing.
This is true REGARDLESS of the actual hard coded MAC addess of your device, which will
not have the 00-00-5e prefix.

The cool thing is that every device on the LAN can get the same multicast packet.

As you know, this actually works in practice - it's how all of our multicasts
come in and go out (as they have to traverse an Ethernet).

Marshall


>
> rgds
> hitesh

T.M. Eubanks
Multicast Technologies, Inc
10301 Democracy Lane, Suite 410
Fairfax, Virginia 22030
Phone : 703-293-9624       Fax     : 703-293-9609
e-mail : tme@multicasttech.com
http://www.on-the-i.com

Test your network for multicast : http://www.multicasttech.com/mt/
 Check the status of multicast in real time :
 http://www.multicasttech.com/status/index.html




From owner-idmr@cs.ucl.ac.uk  Wed Sep  5 19:42:32 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA24997
	for <idmr-archive@lists.ietf.org>; Wed, 5 Sep 2001 19:42:32 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.19565-0@pan2.cs.ucl.ac.uk>;
          Thu, 6 Sep 2001 00:17:40 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.19468-0@pan2.cs.ucl.ac.uk>; Wed, 5 Sep 2001 23:04:11 +0100
Received: from miata.procket.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.01002-0@bells.cs.ucl.ac.uk>; Wed, 5 Sep 2001 23:04:12 +0100
Received: from procket.com (miata.procket.com [10.1.1.1]) 
          by miata.procket.com (8.11.1/8.11.1) with ESMTP id f85M3CH25506;
          Wed, 5 Sep 2001 15:03:12 -0700 (PDT)
Message-ID: <3B96A11F.5FCA28D2@procket.com>
Date: Wed, 05 Sep 2001 15:03:12 -0700
From: John Zwiebel <john.zwiebel@Procket.com>
Reply-To: john.zwiebel@Procket.com
Organization: Procket Networks
X-Mailer: Mozilla 4.73 (Macintosh; I; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: tme@21rst-century.com
CC: "hitesh rupare;" <catchhitesh@hotmail.com>, brmclaug@cisco.com,
        bwilliam@cisco.com, pim@catarina.usc.edu, magma@innovationslab.net,
        idmr@cs.ucl.ac.uk, tme@multicasttech.com
Subject: Re: [Magma] Re: question
References: <F49a3rFAFl5pVVc4t3x00007d0a@hotmail.com> <3B969F66.4EB2BEF2@21rst-century.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Let me put in my 2cents:  "Destination Address"
                           ^^^^^^^^^^^

I could be mistaken, but somehow I get the feeling that this was lost
somewhere.

Thanks for your tolerance of my input.

:-)

Marshall Eubanks wrote:
> 
> "hitesh rupare;" wrote:
> 
> > hi,
> >
> > >"the mac addr is hard-coded on to the card " this is the address used  as a
> > >source or as a destination in unicast communication.
> >
> > do you mean that the actual hard coded mac address is used only for unicast
> > and has nothing to do with multicast ?
> 
> Yes.
> 
> >
> >
> > >
> > >Remeber the destination in IPmulticast is not a physical device but a
> > >virtual group.
> >
> > i can understand that  this is how it works at the network layer ( ip ) but
> > i cant visualise this happening on mac layer or for physical
> > addresses...when they talk about mapping the last 28 bits of the group
> > address to 23 bits of mac adddr what are they talking about ?
> >
> > it seems ridiculous to me that if  the mac address of my card begins with
> > 01-00-5e only then i can get multicast ... i understand that this is not how
> > it works but i have no explanation here .... there has to be some way ( i
> > know there is but i havent found this anywhere ) that my mac address is
> > overridden somehow by the last 23 bits of the group address... i dont
> > understand how and when this happens...
> 
> Dear Hitesh;
> 
> When you start to send an IP multicast packet, or when a router or a switch receives a
> multicast IP packet to go onto the LAN, it is supposed to encapsulate it in an ethernet packet
> with the 01-00-5e-XYZ MAC address.
> 
> When you receive, the NIC card of your ethernet device is supposed to recognize the
> 01-00-5e-XYZ address and pass it up to the CPU for processing.
> This is true REGARDLESS of the actual hard coded MAC addess of your device, which will
> not have the 00-00-5e prefix.
> 
> The cool thing is that every device on the LAN can get the same multicast packet.
> 
> As you know, this actually works in practice - it's how all of our multicasts
> come in and go out (as they have to traverse an Ethernet).
> 
> Marshall
> 
> >
> > rgds
> > hitesh
> 
> T.M. Eubanks
> Multicast Technologies, Inc
> 10301 Democracy Lane, Suite 410
> Fairfax, Virginia 22030
> Phone : 703-293-9624       Fax     : 703-293-9609
> e-mail : tme@multicasttech.com
> http://www.on-the-i.com
> 
> Test your network for multicast : http://www.multicasttech.com/mt/
>  Check the status of multicast in real time :
>  http://www.multicasttech.com/status/index.html


From owner-idmr@cs.ucl.ac.uk  Wed Sep  5 19:48:41 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA25065
	for <idmr-archive@lists.ietf.org>; Wed, 5 Sep 2001 19:48:40 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.19525-0@pan2.cs.ucl.ac.uk>;
          Thu, 6 Sep 2001 00:15:25 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.19426-0@pan2.cs.ucl.ac.uk>; Wed, 5 Sep 2001 22:36:16 +0100
Received: from f49.law14.hotmail.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.28931-0@bells.cs.ucl.ac.uk>; Wed, 5 Sep 2001 22:36:04 +0100
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
          Wed, 5 Sep 2001 14:36:03 -0700
Received: from 134.193.128.232 by lw14fd.law14.hotmail.msn.com with HTTP;
          Wed, 05 Sep 2001 21:35:59 GMT
X-Originating-IP: [134.193.128.232]
From: "hitesh rupare;" <catchhitesh@hotmail.com>
To: brmclaug@cisco.com
Cc: bwilliam@cisco.com, John.Zwiebel@procket.com, pim@catarina.usc.edu,
        magma@innovationslab.net, idmr@cs.ucl.ac.uk, tme@multicasttech.com
Subject: Re: question
Date: Wed, 05 Sep 2001 16:35:59 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F49a3rFAFl5pVVc4t3x00007d0a@hotmail.com>
X-OriginalArrivalTime: 05 Sep 2001 21:36:03.0120 (UTC) 
                       FILETIME=[C3147300:01C13652]
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

hi,


>"the mac addr is hard-coded on to the card " this is the address used  as a
>source or as a destination in unicast communication.

do you mean that the actual hard coded mac address is used only for unicast 
and has nothing to do with multicast ?

>
>Remeber the destination in IPmulticast is not a physical device but a
>virtual group.


i can understand that  this is how it works at the network layer ( ip ) but 
i cant visualise this happening on mac layer or for physical 
addresses...when they talk about mapping the last 28 bits of the group
address to 23 bits of mac adddr what are they talking about ?


it seems ridiculous to me that if  the mac address of my card begins with 
01-00-5e only then i can get multicast ... i understand that this is not how 
it works but i have no explanation here .... there has to be some way ( i 
know there is but i havent found this anywhere ) that my mac address is 
overridden somehow by the last 23 bits of the group address... i dont 
understand how and when this happens...

rgds
hitesh




>
>The destination MAc address of an IP Multicast frame is set as follows:
>
>Organisational Unit Identifier; 00.00.5E  as you say the least significant
>bit of the most significant byte is set to 1 to indicate
>Broadcast/Multicast so the OUI becomes 01.00.5E:
>
>To have a 1-1 mapping would have required 16 OUI's only 1 was made
>available to Steve Deering. In fact he was only given 1/2 of the above
>OUI.  So a possible 24 bits to map from IP add to MAC address became only
>23 bits.
>You will notice there are now 32 possible address that map to the each MAC
>address.
>
>01.00.5E.01.01.01
>
>224.1.1.1
>224.129.1.1
>.
>.
>239.129.1.1
>
>Hope this helps
>
>
>
>
>
>At 20:44 04/09/2001 -0500, hitesh rupare; wrote:
>>hi,
>>
>>the mac addr is hard-coded on to the card ... how then can one map the 28
>>bits of the ip addr onto 23 bits of the mac addr ?
>>
>>also bit 0 in octet 7 has to be set to 1 for broadcast/multicast ... how
>>is this bit set ?
>>
>>rgds
>>hitesh
>>
>>
>>
>>>From: Beau Williamson <bwilliam@cisco.com>
>>>To: John Zwiebel <John.Zwiebel@procket.com>,        Bryan Mclaughlin
>>><brmclaug@cisco.com>, pim@catarina.usc.edu,        MAGMA Mailing List
>>><magma@innovationslab.net>, idmr@cs.ucl.ac.uk
>>>Subject: Re: draft-ietf-pim-dm-new-v2-04.txt
>>>Date: Wed, 01 Aug 2001 16:37:59 -0500
>>>
>>>John,
>>>
>>>Once again I think you and I are on the same wavelength.  I'd like to see
>>>MSNIP evolve into something more like the RTS/CTS mechanism that you
>>>describe with sufficient specifications as to how the first hop device
>>>(maybe a router or maybe a layer-3 aware switch) should handle this.
>>>
>>>In addition, I'd like to see "receiver" admission control added if at all
>>>possible.  I'm not convinced that this would require a extension to IGMP
>>>or a new protocol and may actual fall into vendor specific features.
>>>
>>>In any case, the worries over DoS Attacks due to random sourcing and
>>>random joining (especially if SSM takes off) are real and are quickly
>>>becoming a barrier to multicast deployment.
>>>
>>>Maybe this can be discussed at the MAGMA WG in London.  Unfortunately, I
>>>won't be there so I'm hoping you or someone else will carry the
>>>flag.  (At least initially.)
>>>
>>>Beau
>>>At 01:26 PM 7/31/2001, John Zwiebel wrote:
>>> >Bryan Mclaughlin wrote:
>>> >>
>>> >> This issue is addressed by Multicast Source Notification of Interest
>>> >> Protocol (MSNIP)  for SM protocols,  isn't it ? What would need to be
>>>added
>>> >> to make it work for DM?
>>> >>
>>> >
>>> >MSNIP does not do admission control.  It "kind of" does it, but
>>> >there's nothing that prevents a source from dumping mpackets on to the
>>> >LAN.
>>> >And MSNIP does not specifically address what a router should do if
>>> >it sees packets from a source that hasn't registered via MSNIP.
>>> >(one could make the leap that in such a case the router could just
>>> >bit bucket the data stream)
>>> >
>>> >The host (source) is still "in charge" and the network has to muddle
>>> >through the best it can.  If a host is sending and there is no MSNIP
>>> >available, there's nothing to stop it.
>>> >
>>> >The RTS/CTS process I'd like to see would make the network more
>>> >"superior" to the host and is quite a bit more complicated than what
>>> >MSNIP is trying to provide.
>>> >
>>> >I guess this sentence from the MSNIP draft makes my point:
>>> >
>>> >     Hosts that wish to be managed by MSNIP periodically transmit an
>>> >     Interest Solicitation message. This message is multicast with a
>>> >group
>>> >     destination address of ALL_IGMPv3_ROUTERS (224.0.0.22) and is
>>> >     transmitted every [Interest Solicitation Interval] seconds.
>>> >
>>> >  -- MSNIP is IGMPv3 only
>>> >  -- Hosts can arbitrarily decide to not be managed by MSNIP
>>> >  -- MSNIP does not describe how to signal the "network" that the
>>> >        source is about to send.
>>> >
>>> >This shouldn't be taken as a condemnation of MSNIP.  Its quite
>>> >possible my imagination just isn't strong enough to grasp the
>>> >capabilities.  And what I think is needed may be way too complicated
>>> >and contrary to the "spirit of the internet".
>>
>>
>>_________________________________________________________________
>>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>
>
>Bryan Mclaughlin
>Technical Marketing Engineer	            Telephone :+44 (0)20 8756 8811
>IOS Technology Division 		Email        :brmclaug@cisco.com
>Cisco Systems			Mobile       :+44 (0)7710 164487
>


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp



From owner-idmr@cs.ucl.ac.uk  Thu Sep  6 06:10:29 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA18884
	for <idmr-archive@lists.ietf.org>; Thu, 6 Sep 2001 06:10:28 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.19733-0@pan2.cs.ucl.ac.uk>;
          Thu, 6 Sep 2001 10:23:51 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.19724-0@pan2.cs.ucl.ac.uk>; Thu, 6 Sep 2001 10:23:43 +0100
Received: from 203.197.141.34 by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.09040-0@bells.cs.ucl.ac.uk>; Thu, 6 Sep 2001 10:23:45 +0100
Received: from cdc2vwall.wipro.com (cdc2vwall.wipro.com [10.145.0.23]) 
          by raksha.wipro.com (8.11.3/8.11.3) with SMTP id f869O5I11987 
          for <idmr@cs.ucl.ac.uk>; Thu, 6 Sep 2001 14:54:06 +0530 (IST)
Received: from Vinod ([10.145.2.225]) 
          by arabhi.mail.wipro.com (Netscape Messaging Server 4.15) with ESMTP 
          id GJ8I5600.NBG for <idmr@cs.ucl.ac.uk>;
          Thu, 6 Sep 2001 14:54:42 +0530
Message-ID: <007401c136b6$88d9afc0$e102910a@wipro.com>
From: Vinodkumar Parasmal <vinodkumar.paras@wipro.com>
To: IDMR <idmr@cs.ucl.ac.uk>
Subject: Query On Building and Sending (G,S) Queries
Date: Thu, 6 Sep 2001 15:00:14 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------InterScan_NT_MIME_Boundary"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi All,
I have a Query on Building and Sending Group and Source
Specific Queries according to
draft-ietf-idmr-igmp-v3-07.txt Sec:6.6.3.2 P.n:35

The calculation of the contents of Query says that :
two separate query messages are sent for the group ---

one with "Suppress Router-Side Processing" bit set and contains
all the sources with retransmission state and timers greater than LMQI.

and another one has the Suppress Router-Side Processing" bit clear
and contains all the sources with retransmission state and timers lower
or equal to LMQI .

Why is that we require to send two such queries instead of only the second
one ?
How do we compare the timers , is that the remaining time we have to compare
?

Thanks in advance
Vinod



--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit


----------------------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers
and is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
---------------------------------------------------------------------------------------------------------------------------------

--------------InterScan_NT_MIME_Boundary--


From owner-idmr@cs.ucl.ac.uk  Wed Sep 12 10:31:54 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA23001
	for <idmr-archive@lists.ietf.org>; Wed, 12 Sep 2001 10:31:53 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.00178-0@pan2.cs.ucl.ac.uk>;
          Wed, 12 Sep 2001 14:30:40 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.00138-1@pan2.cs.ucl.ac.uk>; Wed, 12 Sep 2001 14:30:08 +0100
Received: from emerson.torrentnet.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.25558-0@bells.cs.ucl.ac.uk>; Wed, 12 Sep 2001 14:29:47 +0100
Received: from imperial.torrentnet.com (imperial.torrentnet.com [198.78.51.109]) 
          by emerson.torrentnet.com (8.11.2/8.11.2) with ESMTP id f8CDTks95365;
          Wed, 12 Sep 2001 09:29:46 -0400 (EDT)
Received: from malibu.torrentnet.com (malibu.torrentnet.com [198.78.51.100]) 
          by imperial.torrentnet.com (8.11.2/8.11.2) with ESMTP 
          id f8CDTkn26864; Wed, 12 Sep 2001 09:29:46 -0400 (EDT)
Received: from malibu.torrentnet.com (malibu.torrentnet.com [198.78.51.100]) 
          by malibu.torrentnet.com (8.11.2/8.11.2) with ESMTP id f8CDTjI05939;
          Wed, 12 Sep 2001 09:29:46 -0400 (EDT)
Date: Wed, 12 Sep 2001 09:29:45 -0400 (EDT)
From: Todd Hayton <thayton@torrentnet.com>
To: IDMR <idmr@cs.ucl.ac.uk>
cc: fenner <fenner@research.att.com>
Subject: Group Source Queries
Message-ID: <Pine.GSO.4.33.0109120925340.4415-100000@malibu.torrentnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Hello,

When sending IGMPv3 Group-and-Source-Specific Queries, are multiple
queries sent if the source list is so large that not all sources may be
sent in a single query (because of the limits of the networks MTU)? Or,
should only a single query be sent with as many sources as can fit (given
the constraints of the MTU) be sent?

Todd H



From owner-idmr@cs.ucl.ac.uk  Fri Sep 14 06:23:58 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA14115
	for <idmr-archive@lists.ietf.org>; Fri, 14 Sep 2001 06:23:58 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.00784-0@pan2.cs.ucl.ac.uk>;
          Fri, 14 Sep 2001 10:24:38 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.00778-0@pan2.cs.ucl.ac.uk>; Fri, 14 Sep 2001 10:24:32 +0100
Received: from lorraine.loria.fr by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.14210-0@bells.cs.ucl.ac.uk>; Fri, 14 Sep 2001 10:24:17 +0100
Received: from dargneuilles.loria.fr (IDENT:lahmadi@dargneuilles.loria.fr [152.81.11.183]) 
          by lorraine.loria.fr (8.9.3/8.9.3/8.9.3/JCG-DG) with SMTP 
          id LAA14402; Fri, 14 Sep 2001 11:24:08 +0200 (MET DST)
From: Abdelkader Lahmadi <Abdelkader.Lahmadi@loria.fr>
Organization: LORIA
To: Vinodkumar Parasmal <vinodkumar.paras@wipro.com>
Subject: the router side if IGMPv3
Date: Fri, 14 Sep 2001 11:21:06 +0200
X-Mailer: KMail [version 1.0.20]
Content-Type: text/plain
Cc: idmr@cs.ucl.ac.uk
MIME-Version: 1.0
Message-Id: <01091411240701.09184@dargneuilles.loria.fr>
Content-Transfer-Encoding: 8bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 8bit

hi, 
an implementation of the router side of IGMPv3 is on : www.loria.fr/~lahmadi

regards,
---------------------------------------------
  Lahmadi Abdelkader
  LORIA - UHP NANCY I
  CAMPUS SCIENTIFIQUE B.P.239
  54506 VANDOEUVRE-LES-NANCY CEDEX
  E-mail : lahmadi@loria.fr
---------------------------------------------


From owner-idmr@cs.ucl.ac.uk  Thu Sep 20 06:02:36 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA04602
	for <idmr-archive@lists.ietf.org>; Thu, 20 Sep 2001 06:02:36 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.02669-0@pan2.cs.ucl.ac.uk>;
          Thu, 20 Sep 2001 10:00:37 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.02663-0@pan2.cs.ucl.ac.uk>; Thu, 20 Sep 2001 10:00:31 +0100
Received: from isis.lip6.fr by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.06880-0@bells.cs.ucl.ac.uk>; Thu, 20 Sep 2001 10:00:26 +0100
Received: from tibre.lip6.fr (tibre.lip6.fr [132.227.74.2]) 
          by isis.lip6.fr (8.12.0.Beta19/jtpda-5.3.2+victor) with ESMTP 
          id f8K90MeZ020438 ; Thu, 20 Sep 2001 11:00:22 +0200
X-pt: isis.lip6.fr
Received: from lip6.fr (otos.lip6.fr [132.227.61.47]) 
          by tibre.lip6.fr (8.11.3/8.11.3) with ESMTP id f8K90DW09154;
          Thu, 20 Sep 2001 11:00:14 +0200 (CEST)
Message-ID: <3BA9B023.F43BDE71@lip6.fr>
Date: Thu, 20 Sep 2001 11:00:20 +0200
From: Rolland Vida <Rolland.Vida@lip6.fr>
Organization: Laboratoire Lip6
X-Mailer: Mozilla 4.75 [fr] (WinNT; U)
X-Accept-Language: fr
MIME-Version: 1.0
To: magma@innovationslab.net, idmr@cs.ucl.ac.uk, ipng@sunroof.eng.sun.com,
        ssm-interest@external.cisco.com, wg-multicast@internet2.edu
Subject: MLDv2 implementation
Content-Type: multipart/alternative; 
              boundary="------------CEC8BFA98A27BF2765E316CA"
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


--------------CEC8BFA98A27BF2765E316CA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear all,

We would like to announce the first implementation of the
MLDv2(Multicast Listener Discovery version 2) protocol, jointly
developed at LIP6 - Universite Pierre et Maris Curie, Paris and LSIIT -
Universite Louis Pasteur, Strasbourg.

The development was done on FreeBSD 4.3, using the integrated KAME code
for IPv6.

MLDv2 Host Implementation was done by Konstantin Kabassanov at LIP6. It
is a kernel implementation based on Wilbert de Graaf's IGMPv3 Host
Implementation for IPv4.

MLDv2 Enabled PIM-SSM Router Implementation was done by Mickael Hoerdt
at LSIIT. MLDv2 Router is not a kernel code, but implemented as a user
process, fully integrated to PIM-SSM routing daemon.

The MLDv2 Host implementation follows the MLDv2 Internet Draft
(draft-vida-mld-v2-01.txt). The MLDv2 Router part is not fully compliant
with the internet draft, as it fulfils Source Specific Multicast Routing
requirements, limited to INCLUDE messages.

All the information related to our MLDv2 Implementation can be found at:
http://mldv2.lip6.fr.
Please send comments, or report bugs to:
  - mldv2@lip6.fr (host part)
  - ssm@www-r2.u-strasbg.fr  (router part)

Best regards,

LIP6 Team                         LSIIT Team
   Konstantin Kabassanov            Mickael Hoerdt
   Rolland Vida                     Dominique Grad
   Luis Costa                       Jean-Jacques Pansiot
   Serge Fdida


--------------CEC8BFA98A27BF2765E316CA
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<tt>Dear all,</tt><tt></tt>
<p><tt>We would like to announce the first implementation of the MLDv2(Multicast
Listener Discovery version 2) protocol, jointly developed at LIP6 - Universite
Pierre et Maris Curie, Paris and LSIIT - Universite Louis Pasteur, Strasbourg.</tt><tt></tt>
<p><tt>The development was done on FreeBSD 4.3, using the integrated KAME
code for IPv6.</tt><tt></tt>
<p><tt>MLDv2 Host Implementation was done by Konstantin Kabassanov at LIP6.
It is a kernel implementation based on Wilbert de Graaf's IGMPv3 Host Implementation
for IPv4.</tt><tt></tt>
<p><tt>MLDv2 Enabled PIM-SSM Router Implementation was done by Mickael
Hoerdt at LSIIT. MLDv2 Router is not a kernel code, but implemented as
a user process, fully integrated to PIM-SSM routing daemon.</tt><tt></tt>
<p><tt>The MLDv2 Host implementation follows the MLDv2 Internet Draft (draft-vida-mld-v2-01.txt).
The MLDv2 Router part is not fully compliant with the internet draft, as
it fulfils Source Specific Multicast Routing requirements, limited to INCLUDE
messages.</tt><tt></tt>
<p><tt>All the information related to our MLDv2 Implementation can be found
at: <A HREF="http://mldv2.lip6.fr">http://mldv2.lip6.fr</A>.</tt>
<br><tt>Please send comments, or report bugs to:</tt>
<br><tt>&nbsp; - mldv2@lip6.fr (host part)</tt>
<br><tt>&nbsp; - ssm@www-r2.u-strasbg.fr&nbsp; (router part)</tt><tt></tt>
<p><tt>Best regards,</tt><tt></tt>
<p><tt>LIP6 Team&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LSIIT Team</tt>
<br><tt>&nbsp;&nbsp; Konstantin Kabassanov&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Mickael Hoerdt</tt>
<br><tt>&nbsp;&nbsp; Rolland Vida&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Dominique Grad</tt>
<br><tt>&nbsp;&nbsp; Luis Costa&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Jean-Jacques Pansiot</tt>
<br><tt>&nbsp;&nbsp; Serge Fdida</tt>
<br><tt></tt>&nbsp;</html>

--------------CEC8BFA98A27BF2765E316CA--



From owner-idmr@cs.ucl.ac.uk  Fri Sep 21 12:31:14 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA00481
	for <idmr-archive@lists.ietf.org>; Fri, 21 Sep 2001 12:31:14 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.03620-0@pan2.cs.ucl.ac.uk>;
          Fri, 21 Sep 2001 16:32:06 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.03614-0@pan2.cs.ucl.ac.uk>; Fri, 21 Sep 2001 16:32:00 +0100
Received: from H-135-207-30-103.research.att.com by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.16160-0@bells.cs.ucl.ac.uk>;
          Fri, 21 Sep 2001 16:31:59 +0100
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) 
          by mail-green.research.att.com (Postfix) with ESMTP id 5C8181E007;
          Fri, 21 Sep 2001 11:31:53 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) 
          by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id LAA10664;
          Fri, 21 Sep 2001 11:31:47 -0400 (EDT)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) 
          id IAA29767; Fri, 21 Sep 2001 08:31:47 -0700 (PDT)
Message-Id: <200109211531.IAA29767@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: magma@innovationslab.net
Subject: IANA considerations for IPv4 IGMP
Date: Fri, 21 Sep 2001 08:31:47 -0700
Versions: dmail (solaris) 2.2j/makemail 2.9b
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


MAGMA WG,

  I'd like the working group to consider this short document, which
requests the IANA to create a registry for IPv4 IGMP Type and Code
numbers, similar to the existing registry for IPv4 ICMP.  Some IDMR
drafts are blocked on the existence of this registry.

  This seems to fall smack dab in the middle of the MAGMA charter,
so unless there are objections from the WG I'd like to adopt this draft
as a WG document, and do a last call real soon.  Let's say one week to
discuss the document on the magma mailing list; on October 1st, barring
significant problems, we will adopt the document as a WG document and
start the WG last call.

  What follows is the Internet-Draft announcement for the current draft.

Thanks,
  Bill

----- Begin forwarded message:

From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-fenner-igmp-iana-01.txt,.ps
Date: Fri, 21 Sep 2001 07:04:08 -0400
To: IETF-Announce: ;
Reply-to: Internet-Drafts@ietf.org


	Title		: IANA Considerations for IGMP
	Author(s)	: B. Fenner
	Filename	: draft-fenner-igmp-iana-01.txt,.ps
	Pages		: 7
	Date		: 20-Sep-01
	
This memo requests that the IANA create a registry for fields in the
IGMP protocol header, and provides guidance for the IANA to use in
assigning parameters for those fields.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-fenner-igmp-iana-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-fenner-igmp-iana-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-fenner-igmp-iana-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

[anon-ftp unfetched: draft-fenner-igmp-iana-01.txt]

----- End forwarded message:


From owner-idmr@cs.ucl.ac.uk  Fri Sep 21 12:37:52 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA00664
	for <idmr-archive@lists.ietf.org>; Fri, 21 Sep 2001 12:37:51 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.03643-0@pan2.cs.ucl.ac.uk>;
          Fri, 21 Sep 2001 16:50:09 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.03637-0@pan2.cs.ucl.ac.uk>; Fri, 21 Sep 2001 16:50:03 +0100
Received: from lorraine.loria.fr by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.18000-0@bells.cs.ucl.ac.uk>; Fri, 21 Sep 2001 16:50:01 +0100
Received: from dargneuilles.loria.fr (IDENT:lahmadi@dargneuilles.loria.fr [152.81.11.183]) 
          by lorraine.loria.fr (8.9.3/8.9.3/8.9.3/JCG-DG) with SMTP 
          id RAA09260 for <idmr@cs.ucl.ac.uk>;
          Fri, 21 Sep 2001 17:49:59 +0200 (MET DST)
From: Abdelkader Lahmadi <Abdelkader.Lahmadi@loria.fr>
Organization: LORIA
To: idmr@cs.ucl.ac.uk
Subject: IGMPv3:Max resp code
Date: Fri, 21 Sep 2001 17:47:14 +0200
X-Mailer: KMail [version 1.0.20]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <01092117495800.15493@dargneuilles.loria.fr>
Content-Transfer-Encoding: 8bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 8bit

hi,
on the IGMPv3 internet draft section 4.1.1, i would to know the reasons for
choosing the value 128, to determinate the Max resp Time ?

regards,

---------------------------------------------
  Lahmadi Abdelkader
  LORIA - UHP NANCY I
  CAMPUS SCIENTIFIQUE B.P.239
  54506 VANDOEUVRE-LES-NANCY CEDEX
  E-mail : lahmadi@loria.fr
---------------------------------------------


From owner-idmr@cs.ucl.ac.uk  Fri Sep 21 15:55:23 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA05602
	for <idmr-archive@lists.ietf.org>; Fri, 21 Sep 2001 15:55:21 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.03715-0@pan2.cs.ucl.ac.uk>;
          Fri, 21 Sep 2001 19:54:46 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.03709-0@pan2.cs.ucl.ac.uk>; Fri, 21 Sep 2001 19:54:40 +0100
Received: from net015s.hetnet.nl by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.04063-0@bells.cs.ucl.ac.uk>; Fri, 21 Sep 2001 19:54:38 +0100
Received: from wdegraafdp866 ([209.131.52.217]) by hetnet.nl 
          with Microsoft SMTPSVC(5.5.1877.757.75);
          Fri, 21 Sep 2001 20:52:43 +0200
Message-ID: <00b401c142ce$d99f8190$d93483d1@inktomi.com>
From: Wilbert de Graaf <wilbertdg@hetnet.nl>
To: Abdelkader Lahmadi <Abdelkader.Lahmadi@loria.fr>
Cc: idmr <idmr@cs.ucl.ac.uk>
References: <01092117495800.15493@dargneuilles.loria.fr>
Subject: Re: IGMPv3:Max resp code
Date: Fri, 21 Sep 2001 11:54:30 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit


> on the IGMPv3 internet draft section 4.1.1, i would to know the reasons
for
> choosing the value 128, to determinate the Max resp Time ?

First of all I wasn't there but this is what I was told. Some people with
thousands of hosts on a single router (I believe cable operators) argued the
need for a max response time of more than one hour. This value of 128 has
been picked because it was found to be the best to:

1) express any value below 128 with precision
2) although losing precision, good enough to express those hours

I remember once seeing a plot of those values on a webpage.

Wilbert




From owner-idmr@cs.ucl.ac.uk  Mon Sep 24 18:42:17 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA02745
	for <idmr-archive@lists.ietf.org>; Mon, 24 Sep 2001 18:42:16 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.05143-0@pan2.cs.ucl.ac.uk>;
          Mon, 24 Sep 2001 22:45:52 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.05137-0@pan2.cs.ucl.ac.uk>; Mon, 24 Sep 2001 22:45:47 +0100
Received: from mail-blue.research.att.com by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.05106-0@bells.cs.ucl.ac.uk>;
          Mon, 24 Sep 2001 22:45:45 +0100
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) 
          by mail-blue.research.att.com (Postfix) with ESMTP id 31CB44CE02;
          Mon, 24 Sep 2001 17:45:45 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) 
          by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id RAA27657;
          Mon, 24 Sep 2001 17:45:43 -0400 (EDT)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) 
          id OAA03623; Mon, 24 Sep 2001 14:45:43 -0700 (PDT)
Message-Id: <200109242145.OAA03623@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: wilbertdg@hetnet.nl
Subject: Re: IGMPv3:Max resp code
Cc: abdelkader.lahmadi@loria.fr, idmr@cs.ucl.ac.uk
References: <01092117495800.15493@dargneuilles.loria.fr> <00b401c142ce$d99f8190$d93483d1@inktomi.com>
Date: Mon, 24 Sep 2001 14:45:43 -0700
Versions: dmail (solaris) 2.2j/makemail 2.9b
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


See http://www.research.att.com/~fenner/mcast/igmpv3/ for the
graphs and charts.  We chose the green line (4-bit mantissa,
3-bit exponent) to give a max value of just over 52 minutes;
the 9 days possible using the blue line seemed like overkill.

  Bill


From owner-idmr@cs.ucl.ac.uk  Fri Sep 28 09:42:48 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA14936
	for <idmr-archive@lists.ietf.org>; Fri, 28 Sep 2001 09:42:47 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.07294-0@pan2.cs.ucl.ac.uk>;
          Fri, 28 Sep 2001 14:30:37 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.07288-0@pan2.cs.ucl.ac.uk>; Fri, 28 Sep 2001 14:30:32 +0100
Received: from cmr2.ash.ops.us.uu.net by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.00621-0@bells.cs.ucl.ac.uk>; Fri, 28 Sep 2001 14:30:30 +0100
Received: from neserve0.corp.us.uu.net by cmr2.ash.ops.us.uu.net 
          with ESMTP (peer crosschecked as: neserve0.corp.us.uu.net [153.39.92.148]) 
          id QQlila24495; Fri, 28 Sep 2001 13:30:40 GMT
Received: by neserve0.corp.us.uu.net id QQlikz27011;
          Fri, 28 Sep 2001 09:29:45 -0400 (EDT)
From: jhall@UU.NET (Jeremy Hall)
Message-Id: <QQlikz27011.200109281329@neserve0.corp.us.uu.net>
Subject: Re: Multicast and partitioned links?
In-Reply-To: <Roam.SIMC.2.0.6.1001662967.18435.nordmark@bebop.france> from Erik Nordmark at "Sep 28, 2001 09:42:47 am"
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Date: Fri, 28 Sep 2001 09:29:45 -0400 (EDT)
CC: idmr@cs.ucl.ac.uk
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

If the two routers cannot hear eachother's pim messages on the lan, they
will work correctly with the caveat that upstream routers may not know to
which router to RPF for the hosts.  It is better to subnet differently
based on topological boundaries.

_J

In the new year, Erik Nordmark wrote:
> 
> I'm trying to figure out the detailed impact on multicast routing
> when e.g. a Ethernet link is partitioned so that some hosts can communicate
> with one multicast router and other hosts can communicate with
> another multicast router. (See pictures below.)
> 
> Is this behavior deterministic? Is it a function of what multicast routing
> protocol is used? Is it a function of different implementations of
> multicast routing protocols?
> RTFMs are welcome.
> 
> 
> 		Rest of Internet
> 		|		|
> 		|		|
> 		R1		R2		Multicast routers
> 		|		|
> 		X---------------X		Ethernet hubs/switches
> 		|		|
> 		H1		H2
> 
> Assume that a single IP subnet prefix is assigned to the link.
> What happens when the link partitions due to the horizontal link
> between the two switches fail?
> 
> Clearly both multicast routers continue to adverise the subnet prefix
> using the routing protocol, since they have an interface with that subnet
> prefix assigned to it.
> But they loose any routing protocol adjacency between each other on that link.
> 
> I assume this means that they will both become IGMP/MLD queriers on the link.
> Does it also mean that they will forward multicast packets from the link
> (with source addresses in the subnet prefix) towards the rest of
> the Internet? As far as I can tell they should, but this perhaps depends
> on the multicast routing protocol?
> What about groups in which H1 and H2 are members? Will multicast packets
> from the "outside" reach them?
> 
> My guesses so far are:
>  - The routers (due the the partition) are no longer aware of each other.
>  - Each router becomes an IGMP/MLD querier on the link hence
>    they discover which groups H1 and H2 are part of.
>  - They both forward packets from the link towards the rest of the Internet.
>    Thus when H1 sends multicasts R1 will forward it; when H2 sends R2 will 
>    forward.
>  - Some packets sent by H1 and H2 will not reach all receivers due to
>    RPF checks further away from R1 and R2. This is caused by the RPF
>    check operating what is believes is the shortest path to the subnet prefix
>    which implicitly assumes that e.g. both R1 and R2 would forward packets sent
>    by H1.
>  - Multicast groups with senders in the Internet (i.e. outside the partitioned
>    links) will(?) be received by both H1 and H2 - both R1 and R2 will forward
>    multicast packets onto the partitioned link.
>    (When the link is not partitioned R1 and R2 will elect one of them as
>    a forwarder onto the link. But at least for some multicast routing
>    protocols (all of them?) the election of a forwarder will elect
>    both when there is a partition - caused by R1 and R2 not being able to
>    communicate with each other over the link.)
> 
> Greateful for any information, clues, or RTFMs.
> 
>   Erik
> 
>    
>    
> 



From owner-idmr@cs.ucl.ac.uk  Fri Sep 28 09:43:24 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA14983
	for <idmr-archive@lists.ietf.org>; Fri, 28 Sep 2001 09:43:24 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.07261-0@pan2.cs.ucl.ac.uk>;
          Fri, 28 Sep 2001 13:52:41 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.07104-0@pan2.cs.ucl.ac.uk>; Fri, 28 Sep 2001 08:47:25 +0100
Received: from mercury.Sun.COM by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.04084-0@bells.cs.ucl.ac.uk>; Fri, 28 Sep 2001 08:47:23 +0100
Received: from bebop.France.Sun.COM ([129.157.174.15]) 
          by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA27154 
          for <idmr@cs.ucl.ac.uk>; Fri, 28 Sep 2001 00:47:22 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23]) 
          by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP 
          id f8S7lKv12992; Fri, 28 Sep 2001 09:47:20 +0200 (MET DST)
Date: Fri, 28 Sep 2001 09:42:47 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Multicast and partitioned links?
To: idmr@cs.ucl.ac.uk
Cc: Erik.Nordmark@eng.sun.com
Message-ID: <Roam.SIMC.2.0.6.1001662967.18435.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


I'm trying to figure out the detailed impact on multicast routing
when e.g. a Ethernet link is partitioned so that some hosts can communicate
with one multicast router and other hosts can communicate with
another multicast router. (See pictures below.)

Is this behavior deterministic? Is it a function of what multicast routing
protocol is used? Is it a function of different implementations of
multicast routing protocols?
RTFMs are welcome.


		Rest of Internet
		|		|
		|		|
		R1		R2		Multicast routers
		|		|
		X---------------X		Ethernet hubs/switches
		|		|
		H1		H2

Assume that a single IP subnet prefix is assigned to the link.
What happens when the link partitions due to the horizontal link
between the two switches fail?

Clearly both multicast routers continue to adverise the subnet prefix
using the routing protocol, since they have an interface with that subnet
prefix assigned to it.
But they loose any routing protocol adjacency between each other on that link.

I assume this means that they will both become IGMP/MLD queriers on the link.
Does it also mean that they will forward multicast packets from the link
(with source addresses in the subnet prefix) towards the rest of
the Internet? As far as I can tell they should, but this perhaps depends
on the multicast routing protocol?
What about groups in which H1 and H2 are members? Will multicast packets
from the "outside" reach them?

My guesses so far are:
 - The routers (due the the partition) are no longer aware of each other.
 - Each router becomes an IGMP/MLD querier on the link hence
   they discover which groups H1 and H2 are part of.
 - They both forward packets from the link towards the rest of the Internet.
   Thus when H1 sends multicasts R1 will forward it; when H2 sends R2 will 
   forward.
 - Some packets sent by H1 and H2 will not reach all receivers due to
   RPF checks further away from R1 and R2. This is caused by the RPF
   check operating what is believes is the shortest path to the subnet prefix
   which implicitly assumes that e.g. both R1 and R2 would forward packets sent
   by H1.
 - Multicast groups with senders in the Internet (i.e. outside the partitioned
   links) will(?) be received by both H1 and H2 - both R1 and R2 will forward
   multicast packets onto the partitioned link.
   (When the link is not partitioned R1 and R2 will elect one of them as
   a forwarder onto the link. But at least for some multicast routing
   protocols (all of them?) the election of a forwarder will elect
   both when there is a partition - caused by R1 and R2 not being able to
   communicate with each other over the link.)

Greateful for any information, clues, or RTFMs.

  Erik

   
   



From owner-idmr@cs.ucl.ac.uk  Fri Sep 28 14:02:09 2001
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA21326
	for <idmr-archive@lists.ietf.org>; Fri, 28 Sep 2001 14:02:09 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.07420-0@pan2.cs.ucl.ac.uk>;
          Fri, 28 Sep 2001 18:02:43 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.07414-0@pan2.cs.ucl.ac.uk>; Fri, 28 Sep 2001 18:02:37 +0100
Received: from alpo.casc.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.17208-0@bells.cs.ucl.ac.uk>; Fri, 28 Sep 2001 18:02:23 +0100
Received: from sunce (sunce.uk.lucent.com [135.86.22.59]) 
          by alpo.casc.com (8.9.1a/8.9.1) with SMTP id NAA02818 
          for <idmr@cs.ucl.ac.uk>; Fri, 28 Sep 2001 13:02:41 -0400 (EDT)
Message-ID: <013f01c1483e$6a596420$3b165687@uk.lucent.com>
From: Mladen Sablic <Mladen.Sablic@lucent.com>
To: idmr <idmr@cs.ucl.ac.uk>
Subject: What do you set Max Resp Time field in IGMPv3 G & G-S queries?
Date: Fri, 28 Sep 2001 17:55:43 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

From draft-ietf-idmr-igmp-v3-07.txt

[LMQI] = Last Member Query Interval
[LMQI] = Last Member Query Count
[MRT]  = Maximum Response Time in Memb. Query Message.
[QRV]  = Querier Robustness Variable in Memb. Query Messsages.

Section 6.6.3 IGMPv3-07 draft specifies that:
   - the group or source timer is lowered by [LMQI].
   - queries are retransmitted [LMQC-1] times WITHIN the
     [LMQI] period.

Period between retransmissions is left unspecified...
is there a reason?

Hence, I also have following questions:-

1. What do you set the [MRT] in the group & group-source
   specific V3 query messages?

    Assuming retransmission period [LMQI]/[LMQC],
    should [MRT] = [LMQI]/[LMQC==QRV].
  
2. In 6.6.1 How does the non-querier calculate LMQI when
it receives a query with Suppress Router-Side Processing
flag not set?

Is it:
   if (QRV==0)
        lower timer to own configured LMQI 
   else
        lower timer to [QRV]*[MRT]
        (both values from the packet).

Regards,

Mladen

<Mladen.Sablic@lucent.com> UK IP Development





