[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [magma] Question about Building and Sending Group and Source Specific Queries ( RFC 3376, section 6.6.3.2)
Sorry, I still have some questions about it.
The RFC 3376 says that "The first one has the "Suppress Router-Side
Processing" bit set and contains all the
sources with retransmission state and timers greater than LMQT."
So I guess that the first query's S bit will always be set.
But I think that the first query's S bit should not be set, and the
second query's S bit should be set, and I think it's more reasonable.
Any response will be highly appreciated
kuzi
>>First group and source specific query's S bit will never be set. This is mentioned for the subsequent queries where a response might have been received. In that case, it generates >>two >queries, one with the sources fFrom magma-bounces at ietf.org Thu Jul 3 09:32:39 2008
Return-Path: <magma-bounces at ietf.org>
X-Original-To: magma-archive at megatron.ietf.org
Delivered-To: ietfarch-magma-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 533A23A6D29;
Thu, 3 Jul 2008 09:32:39 -0700 (PDT)
X-Original-To: magma at core3.amsl.com
Delivered-To: magma at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 9FEBE3A69C0
for <magma at core3.amsl.com>; Mon, 30 Jun 2008 19:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.901
X-Spam-Level:
X-Spam-Status: No, score=0.901 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2,
MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 7VGi4hhQbpvA for <magma at core3.amsl.com>;
Mon, 30 Jun 2008 19:35:53 -0700 (PDT)
Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190])
by core3.amsl.com (Postfix) with ESMTP id 9BE0A3A67F2
for <magma at ietf.org>; Mon, 30 Jun 2008 19:35:53 -0700 (PDT)
Received: by mu-out-0910.google.com with SMTP id g7so761356muf.9
for <magma at ietf.org>; Mon, 30 Jun 2008 19:36:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:mime-version:content-type:content-transfer-encoding
:content-disposition;
bh=AEajsE6EfLnjUrFh25/pwVxumrkE4Ipe0QMnvD3zY0A=;
b=wgPpfiEFcYoR4in9gQ6swZA7ThhBgbUv9E3Ye3w3UYh1runZRwYVf+DJEmmxvEHKfG
UUv9Z4nDuXeuGNXmY4mBD01RdWtULrGMQwYm0uL18SSNoJvktk4+F3Hmnl+nj+LVgbTO
2mXn34EHeqyBWNO2TVr+JixIej1rNJojuuzJA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:mime-version:content-type
:content-transfer-encoding:content-disposition;
b=SUJ8AH4AO2av3X/smW/qFBWiXDcCZKWokxleMyAxdkQzZoej6ouiBVpAN9sEpYI23Y
X15yoxKX+YoByWJbs637HPDz0TOAR0GOdoJaxxLYJyE0Nur7ffapnlryMf1r6EAzpUm0
8/8Hd/pQCZ83VWosAHuiX81yObmQCLnYOD160=
Received: by 10.103.243.9 with SMTP id v9mr2639897mur.44.1214879764117;
Mon, 30 Jun 2008 19:36:04 -0700 (PDT)
Received: by 10.103.16.2 with HTTP; Mon, 30 Jun 2008 19:36:04 -0700 (PDT)
Message-ID: <7e901fff0806301936tfd98eabnb94646ae10fbf8b9 at mail.gmail.com>
Date: Tue, 1 Jul 2008 10:36:04 +0800
From: "=?BIG5?B?p/Wpvs1R?=" <izukizuk at gmail.com>
To: magma at ietf.org
MIME-Version: 1.0
Content-Disposition: inline
X-Mailman-Approved-At: Thu, 03 Jul 2008 09:32:38 -0700
Subject: Re: [magma] Question about Building and Sending Group and Source
Specific Queries ( RFC 3376, section 6.6.3.2)
X-BeenThere: magma at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast and Anycast Group Membership <magma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/magma>,
<mailto:magma-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/magma>
List-Post: <mailto:magma at ietf.org>
List-Help: <mailto:magma-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/magma>,
<mailto:magma-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: magma-bounces at ietf.org
Errors-To: magma-bounces at ietf.org
Sorry, I still have some questions about it.
The RFC 3376 says that "The first one has the "Suppress Router-Side
Processing" bit set and contains all the
sources with retransmission state and timers greater than LMQT."
So I guess that the first query's S bit will always be set.
But I think that the first query's S bit should not be set, and the
second query's S bit should be set, and I think it's more reasonable.
Any response will be highly appreciated
kuzi
>>First group and source specific query's S bit will never be set. This is mentioned for the subsequent queries where a response might have been received. In that case, it generates >>two >queries, one with the sources for whichor which it does not want non-querier to reduce its timers and another with those for which it wants the non-querier to reduce their timers.
>>This is done for those sources for which are heard in the responses.
>>Thanks,
>>Bharat
_______________________________________________
magma mailing list
magma at ietf.org
https://www.ietf.org/mailman/listinfo/magma
it does not want non-querier to reduce its timers and another with those for which it wants the non-querier to reduce their timers.
>>This is done for those sources for which are heard in the responses.
>>Thanks,
>>Bharat
_______________________________________________
magma mailing list
magma at ietf.org
https://www.ietf.org/mailman/listinfo/magma