IETF Logo Mail Archive

Re: [magma] Querier transition based on Group Specific Query?

"Kudachi, Deepak S" <deepak.kudachi@hp.com> Tue, 31 January 2012 05:16 UTC

Return-Path: <deepak.kudachi@hp.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 9630721F8782 for <magma@ietfa.amsl.com>; Mon, 30 Jan 2012 21:16:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level:
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 Kg3mWqpfTz4g for <magma@ietfa.amsl.com>; Mon, 30 Jan 2012 21:16:09 -0800 (PST)
Received: from g1t0027.austin.hp.com (g1t0027.austin.hp.com [15.216.28.34]) by ietfa.amsl.com (Postfix) with ESMTP id DC80021F8780 for <magma@ietf.org>; Mon, 30 Jan 2012 21:16:08 -0800 (PST)
Received: from G9W0369G.americas.hpqcorp.net (g9w0369g.houston.hp.com [16.216.193.232]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g1t0027.austin.hp.com (Postfix) with ESMTPS id F296438171; Tue, 31 Jan 2012 05:16:07 +0000 (UTC)
Received: from G4W3007G.americas.hpqcorp.net (16.234.25.123) by G9W0369G.americas.hpqcorp.net (16.216.193.232) with Microsoft SMTP Server (TLS) id 14.1.289.1; Tue, 31 Jan 2012 05:14:45 +0000
Received: from G4W3219.americas.hpqcorp.net ([169.254.8.91]) by G4W3007G.americas.hpqcorp.net ([16.234.25.123]) with mapi id 14.01.0289.001; Tue, 31 Jan 2012 05:14:45 +0000
From: "Kudachi, Deepak S" <deepak.kudachi@hp.com>
To: Indranil Bhattacharya <myselfindranil@gmail.com>, "magma@ietf.org" <magma@ietf.org>
Thread-Topic: [magma] Querier transition based on Group Specific Query?
Thread-Index: AQHM38g3KfPuVF0jl0m5m3lCe7QS7JYl7HVQ
Date: Tue, 31 Jan 2012 05:14:44 +0000
Message-ID: <A73087BEA2747741B7965ACF956E50042E4F1D20@G4W3219.americas.hpqcorp.net>
References: <CAAaur95C6wF7FmQhyPhd-bZKU7VGK5oozbLwkZxC8Mx89Qq9-A@mail.gmail.com>
In-Reply-To: <CAAaur95C6wF7FmQhyPhd-bZKU7VGK5oozbLwkZxC8Mx89Qq9-A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [16.216.12.12]
Content-Type: multipart/alternative; boundary="_000_A73087BEA2747741B7965ACF956E50042E4F1D20G4W3219americas_"
MIME-Version: 1.0
Subject: Re: [magma] Querier transition based on Group Specific Query?
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: Tue, 31 Jan 2012 05:16:09 -0000

Hi,

I guess it should be All host Query which needs to be considered for querier election and not group specific query
Some vendors may support their own proprietary  features like forced fast leave in this case non querier may send  single
GSQ on specific port to find any host interested for that group this should not be considered for querier election.

RFC does not mention any thing about this AHQ/GSQ/GSSQ.(let me know if you find anything related to this).

Rgds
Deepak

From: magma-bounces@ietf.org [mailto:magma-bounces@ietf.org] On Behalf Of Indranil Bhattacharya
Sent: Tuesday, January 31, 2012 8:57 AM
To: magma@ietf.org
Subject: [magma] Querier transition based on Group Specific Query?

Hi,

   In the querier transition state machine, RFC 2236 only mentions 'Query' and does not specify GQ or GSQ. Can a querier transition take place based on GSQ? Or is it okay to for a querier to ignore GSQ? Can anyone please help me with this?

Thanks,
Indranil

v2.23.0 | Report a Bug | By Email