Re: Re: [ssm] another last call for draft-ietf-ssm-arch - ending 3/24
Hugh Holbrook <holbrook@cisco.com> Thu, 08 May 2003 04:52 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00457 for <ssm-archive@odin.ietf.org>; Thu, 8 May 2003 00:52:39 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4851vf26954 for ssm-archive@odin.ietf.org; Thu, 8 May 2003 01:01:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4851u826951 for <ssm-web-archive@optimus.ietf.org>; Thu, 8 May 2003 01:01:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00450 for <ssm-web-archive@ietf.org>; Thu, 8 May 2003 00:52:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DdQ4-0007gU-00 for ssm-web-archive@ietf.org; Thu, 08 May 2003 00:54:12 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DdQ3-0007gQ-00 for ssm-web-archive@ietf.org; Thu, 08 May 2003 00:54:11 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h484w3826745; Thu, 8 May 2003 00:58:03 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h484ui826684 for <ssm@optimus.ietf.org>; Thu, 8 May 2003 00:56:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00396 for <ssm@ietf.org>; Thu, 8 May 2003 00:46:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DdL1-0007fQ-00 for ssm@ietf.org; Thu, 08 May 2003 00:48:59 -0400
Received: from sj-core-2.cisco.com ([171.71.177.254]) by ietf-mx with esmtp (Exim 4.12) id 19DdL0-0007fN-00 for ssm@ietf.org; Thu, 08 May 2003 00:48:59 -0400
Received: from holbrook-laptop.cisco.com (sjc-vpn3-623.cisco.com [10.21.66.111]) by sj-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h484nJFf028390; Wed, 7 May 2003 21:49:20 -0700 (PDT)
Received: by holbrook-laptop.cisco.com (Postfix, from userid 500) id 4D77310B7A7; Wed, 7 May 2003 21:41:32 -0700 (PDT)
From: Hugh Holbrook <holbrook@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Hugh Holbrook <holbrook@cisco.com>, ssm@ietf.org
In-reply-to: <Pine.LNX.4.44.0303061227210.15024-100000@netcore.fi>
Subject: Re: Re: [ssm] another last call for draft-ietf-ssm-arch - ending 3/24
Reply-To: holbrook@cisco.com
Message-Id: <20030508044132.4D77310B7A7@holbrook-laptop.cisco.com>
Date: Wed, 07 May 2003 21:41:32 -0700
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=subscribe>
Hey, Pekka. I was just finishing up the final tweaks to the draft realize that I never responded to your editorial comments from a few months back. I took pretty much all of your suggestions. For the record, here's what I did. -Hugh > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this > document are to be interpreted as described in RFC 2119 [RFC 2119]. > > ==> I believe this should be at the end of Introduction, but not sure..? RFC2119 says anywhere near the beginning is ok. > designated as source-specific multicast (SSM) destination addresses and > are reserved for use by source-specific applications and protocols. For > IP version 6 (IPv6), the address prefix FF3x::/32 is reserved for > Source-Specific Multicast use. It defines an extension to the Internet > > ==> source-specific multicast vs Source-Specific Multicast -- pick one for > consistancy > > Using the terminology of [IPv6-UBM], this means that P=1, T=1, and > plen=0 for any SSM address. Done > ==> "means that x=y for any address", is ok but could be a bit better, > maybe: > > Using the terminology of [IPv6-UBM], all SSM addresses must have P=1, T=1, and > plen=0. Done > within the FF3x::/96 range, but a system should treat all of FF3x::/32 > as an SSM address, to allow for compatibility with possible future uses > > ==> s/an SSM address/SSM addresses/ Done. > referred to as a "channel." In contrast to the ASM model of RFC 1112, > > ==> s/."/"./ ? I think ." is actually the right punctuation. > Identifier: G S,G > Receiver Operations: join, leave subscribe, unsubscribe > > ==> s/subscribe/Subscribe/, s/unsubscribe/Unsubscribe/ Done. > host IP module sends an unsubscription request for that channel out > interface I. > > ==> s/interface/the interface/, or "on interface". I used "to interface." > address range for IPv4). For IPv6, the randomization should apply to > the lower 32 bits of the address. > > ==> s/lower/lowest/ ? Done. > subscriber would be delivered to another's IP module, which would then > have to reject the datagram. > > ==> perhaps s/reject/discard/ would be slightly better? Done. > specify the required modifications to those protocols to support SSM. > > ==> s/required /required / (extra space) Done > 7. Security Considerations > > ==> add a 1-2 line summary of the subsections here. How's this? This section outlines security issues pertaining to SSM. The following topics are addressed: limitations of IPSec, denial of service attacks, source spoofing, and security issues related to administrative scoping. > To reduce the damage from such an attack, a router MAY have > configuration options to limit the following items: > > ==> s/limit/limit, for example,/ ? the list is not meant to be exclusive, > and it's a MAY after all.. > > risks unduly burdening the network infrastructure by deliver (S,G) Done. > ==> s/deliver/delivering/ Done. > -- > Pekka Savola "You each name yourselves king, yet the > Netcore Oy kingdom bleeds." > Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings > > _______________________________________________ > ssm mailing list > ssm@ietf.org > https://www1.ietf.org/mailman/listinfo/ssm _______________________________________________ ssm mailing list ssm@ietf.org https://www1.ietf.org/mailman/listinfo/ssm
- [ssm] another last call for draft-ietf-ssm-arch -… Hugh Holbrook
- Re: [ssm] another last call for draft-ietf-ssm-ar… Pekka Savola
- Re: Re: [ssm] another last call for draft-ietf-ss… Hugh Holbrook
- Re: Re: [ssm] another last call for draft-ietf-ss… Pekka Savola
- Re: [ssm] another last call for draft-ietf-ssm-ar… Brian Haberman
- Re: [ssm] another last call for draft-ietf-ssm-ar… Pekka Savola
- Re: [ssm] another last call for draft-ietf-ssm-ar… Brian Haberman
- Re: [ssm] another last call for draft-ietf-ssm-ar… Pekka Savola
- Re: [ssm] another last call for draft-ietf-ssm-ar… Brian Haberman
- Re: Re: Re: [ssm] another last call for draft-iet… Hugh Holbrook
- [ssm] what to say about scoping for v6 [was ...la… Hugh Holbrook
- [ssm] permanent ipv6 ssm addresses [was ...last c… Hugh Holbrook
- Re: [ssm] permanent ipv6 ssm addresses [was ...la… Brian Haberman
- Re: [ssm] another last call for draft-ietf-ssm-ar… Brian Haberman
- Re: [ssm] what to say about scoping for v6 [was .… Brian Haberman
- Re: Re: [ssm] permanent ipv6 ssm addresses [was .… Hugh Holbrook
- Re: [ssm] what to say about scoping for v6 [was .… Pekka Savola
- Re: Re: [ssm] what to say about scoping for v6 [w… Hugh Holbrook
- Re: [ssm] what to say about scoping for v6 [was .… Brian Haberman
- Re: Re: [ssm] what to say about scoping for v6 [w… Pekka Savola
- Re: [ssm] what to say about scoping for v6 Hitoshi Asaeda
- Re: Re: Re: [ssm] what to say about scoping for v… Hugh Holbrook
- Re: [ssm] what to say about scoping for v6 Pekka Savola
- Re: [ssm] what to say about scoping for v6 [was .… Brian Haberman
- Re: [ssm] what to say about scoping for v6 [was .… Pekka Savola
- Re: Re: [ssm] what to say about scoping for v6 [w… Hugh Holbrook
- Re: Re: [ssm] what to say about scoping for v6 [w… Pekka Savola
- Re: Re: [ssm] another last call for draft-ietf-ss… Hugh Holbrook