
From schmidt@informatik.haw-hamburg.de  Tue May  3 05:57:11 2011
Return-Path: <schmidt@informatik.haw-hamburg.de>
X-Original-To: sam@ietfa.amsl.com
Delivered-To: sam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60134E0813 for <sam@ietfa.amsl.com>; Tue,  3 May 2011 05:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.864
X-Spam-Level: 
X-Spam-Status: No, score=-101.864 tagged_above=-999 required=5 tests=[AWL=1.474, BAYES_00=-2.599, GB_I_INVITATION=-2, HELO_EQ_DE=0.35, SARE_NETPROD=0.111, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UlZiDZyaUqNF for <sam@ietfa.amsl.com>; Tue,  3 May 2011 05:57:10 -0700 (PDT)
Received: from mail2.rz.htw-berlin.de (mail2.rz.htw-berlin.de [141.45.10.102]) by ietfa.amsl.com (Postfix) with ESMTP id 6E8A1E0808 for <sam@irtf.org>; Tue,  3 May 2011 05:57:09 -0700 (PDT)
Envelope-to: sam@irtf.org
Received: from [141.22.26.184] by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1QHF8I-000EVB-QF for sam@irtf.org; Tue, 03 May 2011 14:55:18 +0200
Message-ID: <4DBFFBA4.7010000@informatik.haw-hamburg.de>
Date: Tue, 03 May 2011 14:57:08 +0200
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: sam <sam@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: sam@irtf.org
Subject: [SAM] Fwd: [IRTF-Announce] FIVE DAYS REMAINING: Call for Nominations: Applied Networking Research Prize (ANRP)
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG" <sam.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/sam>, <mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/sam>, <mailto:sam-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2011 12:57:11 -0000

Dear all,

as you might have seen on the announcement list, there is a very 
interesting call for the "Applied Networking Research Prize (ANRP)".

Please distribute to your colleagues and consider applications / 
nominations of candidates with suitable contributions!

Best regards,

Thomas
-------- Original Message --------
Subject: [IRTF-Announce] FIVE DAYS REMAINING: Call for Nominations: 
Applied	Networking Research Prize (ANRP)
Date: Tue, 3 May 2011 15:27:39 +0300
From: Lars Eggert <lars.eggert@nokia.com>
Reply-To: anrp@isoc.org
To: irtf-announce@irtf.org


                    CALL FOR NOMINATIONS:

           APPLIED NETWORKING RESEARCH PRIZE (ANRP)


*** Apply until May 8, 2011 for the ANR Prize for IETF-81,
*** July 24-29, 2011 in Quebec City, Canada!

The Applied Networking Research Prize (ANRP) is awarded for
recent results in applied networking research that are relevant
for transitioning into shipping Internet products and related
standardization efforts. Researchers with relevant, recently
published results are encouraged to apply for this prize, which
will offer them the opportunity to present and discuss their work
with the engineers, network operators, policy makers and
scientists that participate in the Internet Engineering Task
Force (IETF) and its research arm, the Internet Research Task
Force (IRTF). Third-party nominations for this prize are also
encouraged. The goal of the Applied Networking Research Prize
(ANRP) is to recognize the best new ideas in networking, and
bring them to the IETF and IRTF especially in cases where they
would not otherwise see much exposure or discussion.

The Applied Networking Research Prize (ANRP) consists of:

   * cash prize of $500 (USD)

   * invited talk at the IRTF Open Meeting

   * travel grant to attend the week-long IETF meeting
     (airfare, hotel, registration, stipend)

   * recognition at the IETF plenary

   * invitation to related social activities

   * potential for additional travel grants to future IETF
     meetings, based on community feedback

The Applied Networking Research Prize (ANRP) will be awarded
three times per year, in conjunction with the three annual IETF
meetings.


HOW TO APPLY

Applicants must nominate a peer-reviewed, recently-published,
original journal, conference or workshop paper. Both self
nominations (nominating one's own paper) and third-party
nominations (nominating someone else's paper) are encouraged. The
nominee must be one of the main authors of the nominated paper.

The nominated paper should provide a scientific foundation for
possible future IETF engineering work or IRTF experimentation,
analyze the behavior of Internet protocols in operational
deployments or realistic testbeds, make an important contribution
to the understanding of Internet scalability, performance,
reliability, security or capability, or otherwise be of relevance
to ongoing or future IETF or IRTF activities.

Applicants must briefly describe how the nominated paper relates
to these goals, and are encouraged to describe how presentation
of these research results will foster their transition into new
IETF engineering or IRTF experimentation, or otherwise seed new
activities that will have an impact on the real-world Internet.

The goal of the Applied Networking Research Prize (ANRP) is to
foster the transitioning of research results into real-world
benefits for the Internet. Therefore, applicants must indicate
that they (or the nominee, in case of third-party applications)
are available to attend the respective IETF meeting in person and
in its entirety.

Applications must include:

   * the name and email address of the nominee

   * a reference to the published nominated paper

   * a PDF copy of the nominated paper

   * a statement that describes how the nominated paper
     fulfills the goals of the award

   * a statement that the nominee is available to attend the
     respective IETF meeting in person and in its entirety

   * a brief biography or CV of the nominee

   * optionally, any other supporting information (link to
     nominee's web site, etc.)

*** Applications are submitted by email to anrp@isoc.org. ***


SELECTION PROCESS

A small selection committee comprised of individuals
knowledgeable about the IRTF, IETF and the broader networking
research community will evaluate the submissions against these
selection criteria. The goal is to select 1-2 submissions for the
Applied Networking Research Prize (ANRP) during each application
period. All applicants will be notified by email.


IMPORTANT DATES

Applications open:      April 11, 2011
Applications close:     May 8, 2011
Notifications:          May 31, 2011
IETF-81 Meeting:        July 24-29, 2011


SPONSORS

The Applied Networking Research Prize (ANRP) is supported by the
Internet Society (ISOC), as part of its Internet Research Award
Programme, in coordination with the Internet Research Task Force
(IRTF).


From mko@cs.stir.ac.uk  Mon May 16 04:21:34 2011
Return-Path: <mko@cs.stir.ac.uk>
X-Original-To: sam@ietfa.amsl.com
Delivered-To: sam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE8FE0751 for <sam@ietfa.amsl.com>; Mon, 16 May 2011 04:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_28=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TFbg8PBn2Abi for <sam@ietfa.amsl.com>; Mon, 16 May 2011 04:21:33 -0700 (PDT)
Received: from clyde.stir.ac.uk (clyde.stir.ac.uk [139.153.13.35]) by ietfa.amsl.com (Postfix) with ESMTP id 32EB9E074C for <sam@irtf.org>; Mon, 16 May 2011 04:21:32 -0700 (PDT)
Received: from [139.153.13.214] (helo=smtp.stir.ac.uk) by clyde.stir.ac.uk with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <mko@cs.stir.ac.uk>) id 1QLvrR-0007fq-NV for sam@irtf.org; Mon, 16 May 2011 12:21:17 +0100
Received: from d253090.cs.stir.ac.uk ([139.153.253.90]) by smtp.stir.ac.uk with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <mko@cs.stir.ac.uk>) id 1QLvrR-0000jq-GJ for sam@irtf.org; Mon, 16 May 2011 12:21:17 +0100
Message-ID: <4DD108A5.3040007@cs.stir.ac.uk>
Date: Mon, 16 May 2011 12:21:09 +0100
From: Dr Mario Kolberg <mko@cs.stir.ac.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: sam <sam@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-stir.ac.uk-MailScanner-ID: 1QLvrR-0007fq-NV
X-stir.ac.uk-MailScanner: Found to be clean
Subject: [SAM] CFP: IMSAA-2011 - 5th International Conference on, Internet Multimedia System Architectures and Applications
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG" <sam.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/sam>, <mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/sam>, <mailto:sam-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2011 11:21:34 -0000

Call for Papers: IMSAA-2011

5th International Conference on
Internet Multimedia System Architectures and Applications
Bangalore, India, 12-14 December 2011
www.imsaa.org

Mobile broadband, convergence of data and communication networks, and
proliferation of smart end-user devices and terminals have sparked
many new architectures enabling internet multimedia applications.
However, "Any Information, Any Device, Any Location" networked
systems still face significant technical challenges including issues
related to performance, privacy,  security, reliability, scalability,
mobility, interoperability, and deployment. IMSAA-11 is endorsed
by the IEEE Communications Society Bangalore Chapter and the
IEEE Communications Society Technical Committees on Communications
and Information Security (CISTC), Network Operation and Management 
(CNOM), and Multimedia Communications (MMTC).

IMSAA-11 is intended to tackle these challenges and will bring together
researchers, engineers and practitioners working on the latest issues in
internet multimedia systems, architectures and applications. The
conference will include a peer reviewed program of technical
sessions, workshops, tutorials, and demonstration sessions.

We welcome submissions for IMSAA's Technical Program under the following
tracks and topics:

Track I. Services
- Mobile Applications and Application Stores
- Crowdsourcing and New Business Models
- Social Networking and Communication services
- Context and Content Aware Services
- Service Lifecycle Management
- Service Delivery Platforms, Virtualization, and Cloud Computing
- Service Composition and Feature Interaction Handling
- P2P Communication and Gaming Services
- VoIP Services
- Benchmarking Services and Application

Track II. Next Generation Communication Systems
- M2M Communications and Internet of Things
- P2P Communication Architectures
- IMS Control and Application Network
- Smart Handheld, Settop, and Home Networking Equipment
- Traffic Optimization and Performance
- IPv6 Migration
- Testing, Simulation, and Validation Platforms
- Policy Management and Charging Gateways and Systems
- Green Systems and Smart Grids

Track III. Multimedia Streaming and Communication
- Multicast, Broadcast, and IPTV
- Media Streaming
- Cross-layer Optimization for Multimedia Service Support
- Video Quality Assessment
- QoS for Voice and Video

Track IV. Security
- Privacy and Information Sharing
- User Data Security and Privacy
- End-to-end Security
- Security and Privacy in P2P Networks
- Authentication, Authorization, and Access Control

In addition to the technical tracks, IMSAA-11 will host a range of
workshops, tutorials and demos. Please check the conference website
for details.

Information for authors: All submissions via EDAS. All papers
submitted in scope to conference tracks and topics will
receive at least 3 reviews.

Dates:
Paper submission deadline    15 July 2011
Author notification        1 September 2011
Final camera ready        10 November 2011

TPC Chairs
Ashish Jain, Telecordia, USA
Mohan Kankanhalli, National University of Singapore
Mario Kolberg, University of Stirling, UK

General Chair
John Buford, Avaya Labs Research, USA


-- 
The Sunday Times Scottish University of the Year 2009/2010
The University of Stirling is a charity registered in Scotland, number 
SC 011159.


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1321 / Virus Database: 1500/3582 - Release Date: 04/18/11



-- 
The Sunday Times Scottish University of the Year 2009/2010
The University of Stirling is a charity registered in Scotland, 
 number SC 011159.


From prvs=1148fbf0b=Sebastian.Woelke@haw-hamburg.de  Fri May 20 04:36:22 2011
Return-Path: <prvs=1148fbf0b=Sebastian.Woelke@haw-hamburg.de>
X-Original-To: sam@ietfa.amsl.com
Delivered-To: sam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DA63E072F for <sam@ietfa.amsl.com>; Fri, 20 May 2011 04:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.327
X-Spam-Level: 
X-Spam-Status: No, score=-1.327 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6EwQ3ny1yPQ for <sam@ietfa.amsl.com>; Fri, 20 May 2011 04:36:21 -0700 (PDT)
Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) by ietfa.amsl.com (Postfix) with ESMTP id 771F6E06BF for <sam@irtf.org>; Fri, 20 May 2011 04:36:20 -0700 (PDT)
Received: from dehawshub02.mailcluster.haw-hamburg.de ([141.22.200.52]) by mail6.is.haw-hamburg.de with ESMTP/TLS/RC4-MD5; 20 May 2011 13:36:19 +0200
Received: from dehawscas03.mailcluster.haw-hamburg.de (141.22.200.53) by DEHAWSHUB02.mailcluster.haw-hamburg.de (141.22.200.52) with Microsoft SMTP Server (TLS) id 8.1.358.0; Fri, 20 May 2011 13:36:19 +0200
Received: from mail-px0-f176.google.com (141.22.200.35) by haw-mailer.haw-hamburg.de (141.22.200.80) with Microsoft SMTP Server (TLS) id 8.1.358.0; Fri, 20 May 2011 13:36:18 +0200
Received: by pxi11 with SMTP id 11so2953535pxi.7        for <sam@irtf.org>; Fri, 20 May 2011 04:36:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.126.18 with SMTP id y18mr2542082wfc.361.1305891376170; Fri, 20 May 2011 04:36:16 -0700 (PDT)
Received: by 10.142.89.15 with HTTP; Fri, 20 May 2011 04:36:16 -0700 (PDT)
Date: Fri, 20 May 2011 13:36:16 +0200
Message-ID: <BANLkTiktFHMCiPVzApKWuXCG9o_4Z0y0_w@mail.gmail.com>
From: =?ISO-8859-1?Q?Sebastian_W=F6lke?= <Sebastian.Woelke@haw-hamburg.de>
To: <sam@irtf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [SAM] detect the presence of an IGMPv3 querier
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sebastian.Woelke@haw-hamburg.de
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG" <sam.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/sam>, <mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/sam>, <mailto:sam-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2011 12:13:34 -0000

Hi all,

I'm working on a system software that automatically detects the presence
of a multicast querier in the current subnet based on passively
monitoring Linux kernel states.

This works fine for IPv6/MLD by looking into the /proc/net/SNMP6 table.
For IPv4/IGMP, the SNMP approach does not work. I can detect an IGMPv2
querier by monitoring 'Timer' in the /proc/net/igmp table: this counts
down the [Unsolicited Report Interval]. However, this does not exist for
IGMPv3, as reports are not suppressed.

My question is about IGMPv3. Does anybody know how to detect the
presence of an IGMPv3 querier based on the kernel states of a multicast
client?

Thanks for your support,

Sebastian

From stig@venaas.com  Fri May 20 10:45:43 2011
Return-Path: <stig@venaas.com>
X-Original-To: sam@ietfa.amsl.com
Delivered-To: sam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C61EE0700 for <sam@ietfa.amsl.com>; Fri, 20 May 2011 10:45:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DHQ2xA7RSEY for <sam@ietfa.amsl.com>; Fri, 20 May 2011 10:45:43 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id ACA09E069B for <sam@irtf.org>; Fri, 20 May 2011 10:45:42 -0700 (PDT)
Received: from [IPv6:2001:420:4:ea0c:7455:bffc:3b49:6e8e] (unknown [IPv6:2001:420:4:ea0c:7455:bffc:3b49:6e8e]) by ufisa.uninett.no (Postfix) with ESMTPSA id 8D9FF7FE6; Fri, 20 May 2011 19:45:39 +0200 (CEST)
Message-ID: <4DD6A8C0.1000501@venaas.com>
Date: Fri, 20 May 2011 10:45:36 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Sebastian.Woelke@haw-hamburg.de
References: <BANLkTiktFHMCiPVzApKWuXCG9o_4Z0y0_w@mail.gmail.com>
In-Reply-To: <BANLkTiktFHMCiPVzApKWuXCG9o_4Z0y0_w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: sam@irtf.org
Subject: Re: [SAM] detect the presence of an IGMPv3 querier
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG" <sam.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/sam>, <mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/sam>, <mailto:sam-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2011 17:45:43 -0000

On 5/20/2011 4:36 AM, Sebastian Wölke wrote:
> Hi all,
>
> I'm working on a system software that automatically detects the presence
> of a multicast querier in the current subnet based on passively
> monitoring Linux kernel states.
>
> This works fine for IPv6/MLD by looking into the /proc/net/SNMP6 table.
> For IPv4/IGMP, the SNMP approach does not work. I can detect an IGMPv2
> querier by monitoring 'Timer' in the /proc/net/igmp table: this counts
> down the [Unsolicited Report Interval]. However, this does not exist for
> IGMPv3, as reports are not suppressed.
>
> My question is about IGMPv3. Does anybody know how to detect the
> presence of an IGMPv3 querier based on the kernel states of a multicast
> client?

If you look at "/proc/net/igmp" it should give you the querier version.
I see e.g.:

Idx     Device    : Count Querier       Group    Users Timer    Reporter
1       lo        :     0      V3
                                 010000E0     1 0:00000000               0
2       eth0      :     3      V3
                                 010000E0     1 0:00000000               0

Doesn't this work?

Stig

>
> Thanks for your support,
>
> Sebastian
> _______________________________________________
> SAM mailing list
> SAM@irtf.org
> http://www.irtf.org/mailman/listinfo/sam


From prvs=1176289b4=Sebastian.Woelke@haw-hamburg.de  Mon May 23 00:51:27 2011
Return-Path: <prvs=1176289b4=Sebastian.Woelke@haw-hamburg.de>
X-Original-To: sam@ietfa.amsl.com
Delivered-To: sam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE56E0726 for <sam@ietfa.amsl.com>; Mon, 23 May 2011 00:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.88
X-Spam-Level: 
X-Spam-Status: No, score=-0.88 tagged_above=-999 required=5 tests=[AWL=0.447,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9PpcCM3UJYw for <sam@ietfa.amsl.com>; Mon, 23 May 2011 00:51:24 -0700 (PDT)
Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) by ietfa.amsl.com (Postfix) with ESMTP id 89220E075F for <sam@irtf.org>; Mon, 23 May 2011 00:51:23 -0700 (PDT)
Received: from dehawshub01.mailcluster.haw-hamburg.de ([141.22.200.36]) by mail6.is.haw-hamburg.de with ESMTP/TLS/RC4-MD5; 23 May 2011 09:48:03 +0200
Received: from dehawscas03.mailcluster.haw-hamburg.de (141.22.200.53) by DEHAWSHUB01.mailcluster.haw-hamburg.de (141.22.200.36) with Microsoft SMTP Server (TLS) id 8.1.358.0; Mon, 23 May 2011 09:48:02 +0200
Received: from mail-px0-f176.google.com (141.22.200.35) by haw-mailer.haw-hamburg.de (141.22.200.80) with Microsoft SMTP Server (TLS) id 8.1.358.0; Mon, 23 May 2011 09:48:02 +0200
Received: by pxi11 with SMTP id 11so4448933pxi.7        for <sam@irtf.org>; Mon, 23 May 2011 00:48:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.126.18 with SMTP id y18mr777896wfc.361.1306136880000; Mon, 23 May 2011 00:48:00 -0700 (PDT)
Received: by 10.142.89.15 with HTTP; Mon, 23 May 2011 00:47:59 -0700 (PDT)
In-Reply-To: <4DD6A8C0.1000501@venaas.com>
References: <BANLkTiktFHMCiPVzApKWuXCG9o_4Z0y0_w@mail.gmail.com> <4DD6A8C0.1000501@venaas.com>
Date: Mon, 23 May 2011 09:47:59 +0200
Message-ID: <BANLkTikARxgDQfcbbCtsNpnBU2eeNX9oWQ@mail.gmail.com>
From: =?ISO-8859-1?Q?Sebastian_W=F6lke?= <Sebastian.Woelke@haw-hamburg.de>
To: Stig Venaas <stig@venaas.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: sam@irtf.org
Subject: Re: [SAM] detect the presence of an IGMPv3 querier
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sebastian.Woelke@haw-hamburg.de
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG" <sam.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/sam>, <mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/sam>, <mailto:sam-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2011 07:51:27 -0000

This dosen't work. The default Querier version is V3. If no Querier
present the version is set to V3.

Sebastian

2011/5/20 Stig Venaas <stig@venaas.com>:
> On 5/20/2011 4:36 AM, Sebastian W=F6lke wrote:
>> Hi all,
>>
>> I'm working on a system software that automatically detects the presence
>> of a multicast querier in the current subnet based on passively
>> monitoring Linux kernel states.
>>
>> This works fine for IPv6/MLD by looking into the /proc/net/SNMP6 table.
>> For IPv4/IGMP, the SNMP approach does not work. I can detect an IGMPv2
>> querier by monitoring 'Timer' in the /proc/net/igmp table: this counts
>> down the [Unsolicited Report Interval]. However, this does not exist for
>> IGMPv3, as reports are not suppressed.
>>
>> My question is about IGMPv3. Does anybody know how to detect the
>> presence of an IGMPv3 querier based on the kernel states of a multicast
>> client?
>
> If you look at "/proc/net/igmp" it should give you the querier version.
> I see e.g.:
>
> Idx =A0 =A0 Device =A0 =A0: Count Querier =A0 =A0 =A0 Group =A0 =A0Users =
Timer =A0 =A0Reporter
> 1 =A0 =A0 =A0 lo =A0 =A0 =A0 =A0: =A0 =A0 0 =A0 =A0 =A0V3
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 010000E0 =
=A0 =A0 1 0:00000000 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0
> 2 =A0 =A0 =A0 eth0 =A0 =A0 =A0: =A0 =A0 3 =A0 =A0 =A0V3
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 010000E0 =
=A0 =A0 1 0:00000000 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0
>
> Doesn't this work?
>
> Stig
>
>>
>> Thanks for your support,
>>
>> Sebastian
>> _______________________________________________
>> SAM mailing list
>> SAM@irtf.org
>> http://www.irtf.org/mailman/listinfo/sam
>
>

From schmidt@informatik.haw-hamburg.de  Sun May 29 09:11:58 2011
Return-Path: <schmidt@informatik.haw-hamburg.de>
X-Original-To: sam@ietfa.amsl.com
Delivered-To: sam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F23E073D for <sam@ietfa.amsl.com>; Sun, 29 May 2011 09:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hs5njdGzYlQs for <sam@ietfa.amsl.com>; Sun, 29 May 2011 09:11:57 -0700 (PDT)
Received: from mail2.rz.htw-berlin.de (mail2.rz.htw-berlin.de [141.45.10.102]) by ietfa.amsl.com (Postfix) with ESMTP id 0152EE066A for <sam@irtf.org>; Sun, 29 May 2011 09:11:56 -0700 (PDT)
Envelope-to: sam@irtf.org
Received: from e178059249.adsl.alicedsl.de ([85.178.59.249] helo=[192.168.178.36]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1QQiap-000P5L-Cx; Sun, 29 May 2011 18:11:55 +0200
Message-ID: <4DE27052.1000302@informatik.haw-hamburg.de>
Date: Sun, 29 May 2011 18:12:02 +0200
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Stig Venaas <stig@venaas.com>
References: <BANLkTiktFHMCiPVzApKWuXCG9o_4Z0y0_w@mail.gmail.com>	<4DD6A8C0.1000501@venaas.com> <BANLkTikARxgDQfcbbCtsNpnBU2eeNX9oWQ@mail.gmail.com>
In-Reply-To: <BANLkTikARxgDQfcbbCtsNpnBU2eeNX9oWQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: sam@irtf.org
Cc: sam <sam@irtf.org>
Subject: Re: [SAM] detect the presence of an IGMPv3 querier
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG" <sam.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/sam>, <mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/sam>, <mailto:sam-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 May 2011 16:11:58 -0000

Hi Stig et al.,

do you (or anybody else) have an idea where to look for traces of IGMPv3 
queriers in the linux kernel tables otherwise?

Thanks,

Thomas

On 23.05.2011 09:47, Sebastian Wölke wrote:
> This dosen't work. The default Querier version is V3. If no Querier
> present the version is set to V3.
>
> Sebastian
>
> 2011/5/20 Stig Venaas<stig@venaas.com>:
>> On 5/20/2011 4:36 AM, Sebastian Wölke wrote:
>>> Hi all,
>>>
>>> I'm working on a system software that automatically detects the presence
>>> of a multicast querier in the current subnet based on passively
>>> monitoring Linux kernel states.
>>>
>>> This works fine for IPv6/MLD by looking into the /proc/net/SNMP6 table.
>>> For IPv4/IGMP, the SNMP approach does not work. I can detect an IGMPv2
>>> querier by monitoring 'Timer' in the /proc/net/igmp table: this counts
>>> down the [Unsolicited Report Interval]. However, this does not exist for
>>> IGMPv3, as reports are not suppressed.
>>>
>>> My question is about IGMPv3. Does anybody know how to detect the
>>> presence of an IGMPv3 querier based on the kernel states of a multicast
>>> client?
>>
>> If you look at "/proc/net/igmp" it should give you the querier version.
>> I see e.g.:
>>
>> Idx     Device    : Count Querier       Group    Users Timer    Reporter
>> 1       lo        :     0      V3
>>                                  010000E0     1 0:00000000               0
>> 2       eth0      :     3      V3
>>                                  010000E0     1 0:00000000               0
>>
>> Doesn't this work?
>>
>> Stig
>>
>>>
>>> Thanks for your support,
>>>
>>> Sebastian
>>> _______________________________________________
>>> SAM mailing list
>>> SAM@irtf.org
>>> http://www.irtf.org/mailman/listinfo/sam
>>
>>
> _______________________________________________
> SAM mailing list
> SAM@irtf.org
> http://www.irtf.org/mailman/listinfo/sam

-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °
