From owner-freebsd-current@FreeBSD.ORG  Fri Oct  2 12:22:09 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B8114106566B
	for <freebsd-current@freebsd.org>; Fri,  2 Oct 2009 12:22:09 +0000 (UTC)
	(envelope-from bms@FreeBSD.org)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com
	[66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 87E4A8FC08
	for <freebsd-current@freebsd.org>; Fri,  2 Oct 2009 12:22:09 +0000 (UTC)
Received: from compute1.internal (compute1.internal [10.202.2.41])
	by gateway1.messagingengine.com (Postfix) with ESMTP id C55B87F32E;
	Fri,  2 Oct 2009 08:22:08 -0400 (EDT)
Received: from heartbeat2.messagingengine.com ([10.202.2.161])
	by compute1.internal (MEProxy); Fri, 02 Oct 2009 08:22:08 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com;
	h=message-id:date:from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	s=smtpout; bh=pAneWRS5GVZuKQ/8sMsPYRpF8CU=;
	b=dWtMSJMIbWJp2CCmeeoQ137ofwCxe0cQaQvMAFRV9Jb+UM3pUNZnP1o+fUg2rwBXyglsfpvNzkeb/cxC/86nLr6ZQTSA6G27Dnf105oBiDkoKhpqyebs1hkEctnScEGU/sSzSSZjz5zJLcRafItp/FfZESfQOeZm1QsojojNbHg=
X-Sasl-enc: jENJ7n4HwHUOprQABr62OPSzA0GbQtalJHuGvfT6k0Lq 1254486128
Received: from empiric.lon.incunabulum.net
	(82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254])
	by mail.messagingengine.com (Postfix) with ESMTPSA id 493B61AC27;
	Fri,  2 Oct 2009 08:22:08 -0400 (EDT)
Message-ID: <4AC5F06F.9020807@FreeBSD.org>
Date: Fri, 02 Oct 2009 13:22:07 +0100
From: Bruce Simpson <bms@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.23 (X11/20091001)
MIME-Version: 1.0
To: Philip Romanov <philip_romanov@yahoo.com>
References: <951619.7835.qm@web52307.mail.re2.yahoo.com>
In-Reply-To: <951619.7835.qm@web52307.mail.re2.yahoo.com>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: IGMPv3 implementation
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2009 12:22:09 -0000

Philip Romanov wrote:
> Hello, 
>
> Does the current implement IGMPv3 state machine when it comes to merging interface state changes during retransmissions as per 5.1 of RFC3376:
>   

Yes, the IGMPv3 implementation merges state changes per interface.

A per source counter is not used for doing this, rather, if there is a 
pending state change for the interface, the merge is performed at the 
level of the outgoing mbuf queue.

> Can somebody shed any light on it? What is the compliance of interface state "merge" during report retransmits? 
>   

As far as I know, it works. I had a regression test framework for this, 
but due to some problems with the serial driver in 8.x, I was unable to 
fully run this test framework.

thanks,
BMS