[magma] draft-ietf-magma-mrdisc-04.txt

Margaret Wasserman <margaret@thingmagic.com> Fri, 04 March 2005 20:40 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01453; Fri, 4 Mar 2005 15:40:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D7Jcz-0005Oe-KV; Fri, 04 Mar 2005 15:42:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D7Jax-0005mT-7d; Fri, 04 Mar 2005 15:40:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D7Jav-0005mO-Ce for magma@megatron.ietf.org; Fri, 04 Mar 2005 15:40:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01410 for <magma@ietf.org>; Fri, 4 Mar 2005 15:40:19 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D7JcX-0005Na-TP for magma@ietf.org; Fri, 04 Mar 2005 15:42:03 -0500
Received: from [10.0.0.171] (account margaret HELO [10.0.0.171]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 300302; Fri, 04 Mar 2005 15:38:04 -0500
Mime-Version: 1.0
Message-Id: <p0620070ebe4e75d1be3b@[10.0.0.171]>
In-Reply-To: <fa7556132cc76c56f3e954c68a834d2b@innovationslab.net>
References: <fa7556132cc76c56f3e954c68a834d2b@innovationslab.net>
Date: Fri, 04 Mar 2005 15:38:08 -0500
To: Brian Haberman <brian@innovationslab.net>, kouvelas@cisco.com, jim@netzwert.ag
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: MAGMA WG <magma@ietf.org>
Subject: [magma] draft-ietf-magma-mrdisc-04.txt
X-BeenThere: magma@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multicast and Anycast Group Membership <magma.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:magma@ietf.org>
List-Help: <mailto:magma-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=subscribe>
Sender: magma-bounces@ietf.org
Errors-To: magma-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da

Hi All,

The MAGMA WG agenda includes a discussion of 
draft-ietf-magma-mrdisc-04.txt, and I just wanted to make sure that 
we are all on the same page going into Minneapolis.

The IESG still has two open blocking issues (discusses) with this 
document, one from Thomas Narten and one from Alex Zinin (see below).

Thomas' discuss was updated after the -04 draft was published, so it 
is clearly a blocking issue with the current version.

Alex, have you had a chance to check if the current version (-04) 
addresses your discuss?

Hopefully we can figure out how to resolve these issues in 
Minneapolis, so that the document can be approved.

See you all in Minneapolis!
Margaret

Thomas Narten:
Discuss:
[2005-02-25] >    1.  For IPv4 it is the 16-bit one's complement of the one's
>         complement sum of the IGMP message, starting with the Type field.
>         For computing the checksum, the checksum field is set to 0.
>

Checksum does not include any IPv4 header fields. This seems like a
bad design choice. Note that in the IPv6 case, the checksum does
include a pseudo-header. Why not be consistent?

>     1.  The expiration of the periodic advertisement interval timer.
>         Note that it this timer is not strictly periodic since it is a
>         random number between MaxAdvertisementInterval and
>         MinAdvertisementInterval.

this doesn't seem good. The spread between these values can be pretty
wide, I think. What you want is an average value with some randomness
to prevent syncrhonization. You don't want the value to be completely
random between (say) 3 and 180 seconds.

Alex Zinin:
Discuss:
[2004-12-02] Rather minor DISCUSS:

>  2.  Protocol Overview
...
>     All MRD messages are sent with an IPv4 TTL or IPv6 Hop Limit of 1 and
>     contain the Router Alert Option[4][5].  All MRD messages SHOULD be
>     Advertisement and Termination messages are sent to the All-Snoopers
>     multicast address.

To what rate? Same comment for other instances of rate limiting in the doc.

>  3.1.2  MinAdvertisementInterval
>
Does this section specify intervals for unsolicited Ads only or
for solicited as well?

_______________________________________________
magma mailing list
magma@ietf.org
https://www1.ietf.org/mailman/listinfo/magma