Re: Re: [magma] WG Last Call: draft-holbrook-idmr-igmpv3-ssm-05.txt
Hugh Holbrook <holbrook@cisco.com> Mon, 16 February 2004 09:46 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08300 for <magma-archive@ietf.org>; Mon, 16 Feb 2004 04:46:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsfKK-0006Jd-00 for magma-archive@ietf.org; Mon, 16 Feb 2004 04:46:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsfJO-0006Di-00 for magma-archive@ietf.org; Mon, 16 Feb 2004 04:45:10 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AsfIl-0006An-00; Mon, 16 Feb 2004 04:44:31 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by mx2.foretec.com with esmtp (Exim 4.24) id 1Asf51-0002QX-B7; Mon, 16 Feb 2004 04:30:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Asf4k-0007mf-Po; Mon, 16 Feb 2004 04:30:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Asf3s-0007kz-Ls for magma@optimus.ietf.org; Mon, 16 Feb 2004 04:29:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07867 for <magma@ietf.org>; Mon, 16 Feb 2004 04:29:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Asf3p-0005Ux-00 for magma@ietf.org; Mon, 16 Feb 2004 04:29:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Asf2r-0005SK-00 for magma@ietf.org; Mon, 16 Feb 2004 04:28:06 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Asf2f-0005Ps-00 for magma@ietf.org; Mon, 16 Feb 2004 04:27:53 -0500
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 16 Feb 2004 01:35:54 +0000
Received: from mira-sjc5-f.cisco.com (IDENT:mirapoint@mira-sjc5-f.cisco.com [171.71.163.13]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i1G9RM4U017714; Mon, 16 Feb 2004 01:27:22 -0800 (PST)
Received: from holbrook-laptop.cisco.com (gorilla.cisco.com [171.69.23.149]) by mira-sjc5-f.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id APF22006; Mon, 16 Feb 2004 01:27:21 -0800 (PST)
Received: by holbrook-laptop.cisco.com (Postfix, from userid 500) id 8479110B834; Mon, 16 Feb 2004 01:28:54 -0800 (PST)
From: Hugh Holbrook <holbrook@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: MAGMA Mailing List <magma@ietf.org>
In-reply-to: <Pine.LNX.4.44.0311031330380.30770-100000@netcore.fi>
Subject: Re: Re: [magma] WG Last Call: draft-holbrook-idmr-igmpv3-ssm-05.txt
Reply-To: holbrook@cisco.com
Message-Id: <20040216092854.8479110B834@holbrook-laptop.cisco.com>
Date: Mon, 16 Feb 2004 01:28:54 -0800
Sender: magma-admin@ietf.org
Errors-To: magma-admin@ietf.org
X-BeenThere: magma@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=unsubscribe>
List-Id: Multicast and Anycast Group Membership <magma.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Hi, Pekka. Thanks for your comments. I updated the draft to incorporate all of your suggestions. An -06 version that incorporates all these changes as well as a few more bits of wordsmithing should show up in the ID directory shortly. See inline for details. > Date: Mon, 3 Nov 2003 13:32:30 +0200 (EET) > From: Pekka Savola <pekkas@netcore.fi> > > On Tue, 28 Oct 2003, Isidor Kouvelas wrote: > > This is the start of a one week WG Last Call to advance > > draft-holbrook-idmr-igmpv3-ssm-05.txt as a Proposed Standard. This > > document has had text cleanup and clarification changes made to it as > > a result of comments from the -04 version Last Call. This Last Call > > will end on Nov 5, 2003. > > Sorry for missing the LC the last time. The comments below. > > In summary, I think the document is in a pretty good shape. However, I > think it needs especially more clarification where the document includes > modifications or clarifications. I'd recommend writing clarifications in > such a manner that it would be clear they're clarifications. More > comments below.. > > substantial > ----------- > > 1) there are several places in the spec which use the uppercase requirements > language where it's not clear whether it's really just a re-statement of > some other spec's requirement (then it should be reworded slightly), or > missing a MODIFICATION tag, for example: > - SHOULD in section 2 > - SHOULD NOT in section 2.2.2 > - SHOULD in section 2.2.5 > - MUST in section 2.2.7 > - everything in section 3.1 I agree with you on this. I went through and cleaned up the language substantially. Every use of RFC 2119 all-caps requirements language is now very clear as to whether it modifies or merely restates requirements from IGMPv3/MLDv2. In doing so, I mostly eliminated the SHOULD/MAY/MUST language where I was just clarifying, and in a few cases I left it in but added a phrase like "as required by [IGMPv3,MLDv2]". > 2) "SSM-aware host" is defined as a host which has a configuration > option to manually override the SSM config ranges. HELLO?!?! Isn't > a host which knows the current SSM ranges is equally SSM-aware. I > fail to see why you'd have to be able to configure the "SSM-aware" > club. That sure wasn't my intention, so I fixed up the text as follows: ... A host that knows the SSM address range and is capable of applying SSM semantics to it is described as an "SSM-aware" host. A host or router may be configured to apply SSM semantics to addresses other than those in the IANA-allocated range. The GMP module on a host... > 3) The SSM range for IPv6 is defined in section 2 as FF3x::/32. > Some others interpret RFC3306 so that the SSM range is FF3x::/96. > Which is it? This may need to be clarified somewhere.. maybe > someone knows what is the appropriate one to use.. We discussed this a while back and the full story is spelled out in draft-ietf-ssm-arch-04.txt. I added the following text referring to that document: The 232/8 IPv4 address range is currently allocated for SSM by IANA [IANA-ALLOCATION]. In IPv6, the FF3x::/32 range (where 'x' is a valid IPv6 multicast scope value) is reserved for SSM semantics [RFC3306], although today SSM allocations are restricted to FF3x::/96. ([SSM] has a more thorough discussion of this topic.) And since you ask here's the longer text from the -arch document: For IPv6, the address prefix FF3x::/32 is reserved for source-specific multicast use, where 'x' is any valid scope identifier, by [IPV6-UBM]. Using the terminology of [IPv6-UBM], all SSM addresses must have P=1, T=1, and plen=0. [IPv6-MALLOC] mandates that the network prefix field of an SSM address also be set to zero, hence all SSM addresses fall in the FF3x::/96 range. Future documents may allow a non-zero network prefix field if, for instance, a new IP address to MAC address mapping is defined. Thus, address allocation should occur within the FF3x::/96 range, but a system should treat all of FF3x::/32 as SSM addresses, to allow for compatibility with possible future uses of the network prefix field. > 4) section 2 describes the modifications and defines an "SSM-aware host". > Is there a need to do something similar for routers? May be necessary if > section 3 lists any modifications, not just clarifications. I think this is a good idea, so I did this and updated the intro and abstract accordingly. > editorial > --------- I made all of your suggested editorial changes. Thanks again. -Hugh _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma
- [magma] WG Last Call: draft-holbrook-idmr-igmpv3-… Isidor Kouvelas
- Re: [magma] WG Last Call: draft-holbrook-idmr-igm… Pekka Savola
- Re: Re: [magma] WG Last Call: draft-holbrook-idmr… Hugh Holbrook