[ssm] AD-review comments on draft-ietf-ssm-arch-04.txt

Alex Zinin <zinin@psg.com> Tue, 13 April 2004 22:15 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14511 for <ssm-archive@lists.ietf.org>; Tue, 13 Apr 2004 18:15:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BDVxm-0003u2-8V; Tue, 13 Apr 2004 18:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BDVtD-0002PA-2u for ssm@optimus.ietf.org; Tue, 13 Apr 2004 17:56:19 -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 RAA12158 for <ssm@ietf.org>; Tue, 13 Apr 2004 17:56:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BDVt9-0007jb-00 for ssm@ietf.org; Tue, 13 Apr 2004 17:56:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BDVhF-0006CJ-00 for ssm@ietf.org; Tue, 13 Apr 2004 17:43:58 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1BDVV0-00055a-00 for ssm@ietf.org; Tue, 13 Apr 2004 17:31:19 -0400
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1]) by psg.com with esmtp (Exim 4.30; FreeBSD) id 1BDVUz-0002Y3-Um for ssm@ietf.org; Tue, 13 Apr 2004 21:31:18 +0000
Date: Tue, 13 Apr 2004 14:31:16 -0700
From: Alex Zinin <zinin@psg.com>
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1998261226.20040413143116@psg.com>
To: ssm@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [ssm] AD-review comments on draft-ietf-ssm-arch-04.txt
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>
Content-Transfer-Encoding: 7bit

Folks-

 Please find attached my AD-review comments on the SSM architecture
 document.

-- 
Alex
http://www.psg.com/~zinin/

Generally the document is in a great shape. Very good job. I have one meta
issue and one editorial nit.

Meta:

 The document does not spell out what protocols hosts and routers MUST
 implement. I.e., this kind of document is expected to specify the
 mandatory-to-implement mechanisms that will ensure that hosts and routers can
 interoperate. However, there is no place in the document where it says
 something like "hosts supporting the SSM network service MUST implement IGMPv3
 for IPv4 and MLDv2 for IPv6", or "routers supporting the SSM network service
 MUST implement PIM-SSM..."

Editorial

 The following part:

> 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].

 should be moved inside the body of the document (preferably not in Abstract)

 Abstract:

> IP addresses in the 232/8 (232.0.0.0 to 232.255.255.255) range are
> 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
                                  ^^
                                needs to be expanded. "This document" ?


 Section "Intellectual Property Rights Notice". To reflect the situation
 with Apple, this section also needs to include the following paragraph
 from RFC 2026.

         "The IETF has been notified of intellectual property rights
         claimed in regard to some or all of the specification contained
         in this document.  For more information consult the online list
         of claimed rights."



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