IETF Logo Mail Archive

Re: [magma] Question about IGMP host implementation

"V, Magesh (Magesh)" <magesh.v@alcatel-lucent.com> Wed, 12 October 2011 05:23 UTC

Return-Path: <magesh.v@alcatel-lucent.com>
X-Original-To: magma@ietfa.amsl.com
Delivered-To: magma@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 362CD21F8BF8 for <magma@ietfa.amsl.com>; Tue, 11 Oct 2011 22:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I1qS+tbSEIy0 for <magma@ietfa.amsl.com>; Tue, 11 Oct 2011 22:23:09 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2F521F8B34 for <magma@ietf.org>; Tue, 11 Oct 2011 22:23:08 -0700 (PDT)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p9C5MxdG025748 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 12 Oct 2011 00:23:02 -0500 (CDT)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p9C5Mxsx009498 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 12 Oct 2011 10:52:59 +0530
Received: from INBANSXCHMBSA2.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Wed, 12 Oct 2011 10:52:58 +0530
From: "V, Magesh (Magesh)" <magesh.v@alcatel-lucent.com>
To: Kunal Shah <kunal.shah@ericsson.com>, "magma@ietf.org" <magma@ietf.org>
Date: Wed, 12 Oct 2011 10:52:58 +0530
Thread-Topic: Question about IGMP host implementation
Thread-Index: AcyId0SCeinZjfcnSnCOOiiZpocqFgAJwdKw
Message-ID: <05D3B4AA7527D74EBF4921238463575321641601BA@INBANSXCHMBSA2.in.alcatel-lucent.com>
References: <4FD1E7CD248BF84F86BD4814EDDDBCC151401F3936@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <4FD1E7CD248BF84F86BD4814EDDDBCC151401F3936@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_05D3B4AA7527D74EBF4921238463575321641601BAINBANSXCHMBSA_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Mailman-Approved-At: Fri, 14 Oct 2011 07:27:27 -0700
Subject: Re: [magma] Question about IGMP host implementation
X-BeenThere: magma@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast and Anycast Group Membership <magma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/magma>, <mailto:magma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/magma>
List-Post: <mailto:magma@ietf.org>
List-Help: <mailto:magma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Oct 2011 05:23:10 -0000

To the best of my knowledge the host does not care about the source-ip of the query for it to respond. I've seen this work always.
OTOH, the igmp router needs to do this check for the reports received because they come from the untrusted side of the n/w.

Thanks,
Magesh.

________________________________
From: magma-bounces@ietf.org [mailto:magma-bounces@ietf.org] On Behalf Of Kunal Shah
Sent: Wednesday, October 12, 2011 6:09 AM
To: magma@ietf.org
Subject: [magma] Question about IGMP host implementation

Hi all,

Can an IGMPv2 host respond to a general query originated from a subnet other then its own?? RFC 2236 states:

""query received" occurs when the host receives either a valid
     General Membership Query message, or a valid Group-Specific
     Membership Query message.  To be valid, the Query message must be
     at least 8 octets long, and have a correct IGMP checksum.  The
     group address in the IGMP header must either be zero (a General
     Query) or a valid multicast group address (a Group-Specific Query)"

There is no requirement for the source address to be on the same subnet as the host.

Thanks,
Kunal

v2.23.0 | Report a Bug | By Email