[ssm] draft-ietf-ssm-arch last call changes summary

Hugh Holbrook <holbrook@cisco.com> Wed, 15 January 2003 10:16 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21701 for <ssm-archive@lists.ietf.org>; Wed, 15 Jan 2003 05:16:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FAVPJ29700; Wed, 15 Jan 2003 05:31:25 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FAOXJ29515 for <ssm@optimus.ietf.org>; Wed, 15 Jan 2003 05:24:33 -0500
Received: from sj-msg-core-4.cisco.com (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21621 for <ssm@ietf.org>; Wed, 15 Jan 2003 05:09:29 -0500 (EST)
Received: from holbrook-laptop.cisco.com (sjc-vpn1-676.cisco.com []) by sj-msg-core-4.cisco.com (8.12.2/8.12.6) with ESMTP id h0FACm0E001805 for <ssm@ietf.org>; Wed, 15 Jan 2003 02:12:49 -0800 (PST)
Received: by holbrook-laptop.cisco.com (Postfix, from userid 500) id 79A8510B7A7; Wed, 15 Jan 2003 05:10:35 -0500 (EST)
From: Hugh Holbrook <holbrook@cisco.com>
To: ssm@ietf.org
Reply-To: holbrook@cisco.com
Message-Id: <20030115101035.79A8510B7A7@holbrook-laptop.cisco.com>
Date: Wed, 15 Jan 2003 05:10:35 -0500
Subject: [ssm] draft-ietf-ssm-arch last call changes summary
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>

I am about to submit a new version of draft-ietf-ssm-arch to the I-D
archives.  I've attached a list of the changes in the upcoming
version, with the source of the request.  I believe this new revision
addresses all of the comments that came up during the wg last call.

If you have any comments that you haven't yet sent or that I've missed
and aren't addressed below, please (re)send them ASAP.

- [pavlin] Added text: OS API should return an error for a (*,G)
  request on an SSM address.

- [pavlin] Added a note about limitations of SSM.  (1) Any
  multi-source aspect apps must be implemented in the application
  layer.  (2) SSM does not support network-layer resource discovery.

- [pekka/brian] Added clarification about the SSM address range
        FF3x::/32 is reserved for SSM
           P=1 and T=1 and plen=0 is required.
        Thus, FF3x::/96 is the actual range today because 
           network prefix field must be zero
        But we leave open the possibility of putting something else in the
           network prefix field.

- [pavlin] Changed erroneous FF2x:: to FF3x::

- [pekka] New text on administrative scoping to describe admin-scoping
  in v6 and to clarify that there is none for IPv4.

- [pekka] New text on source routing: A router SHOULD NOT allow
  source-routing to an SSM addr; MAY have a config option to allow it

- [me/bweis/mbaugher] 
  Add security considerations text describing the IPSec/SSM issue.

- Minor things:

  - [pavlin] Use consistent capitalization on v6 addresses
  - [me] Use consistent capitalization of Source-Specific
  - [pavlin] id-nits
    - Removed references from abstract and shortened it
    - Modified address ranges
    - Added IPR notice and Copyright Statement.
  - [brad] Changed author mailing address

Ssm mailing list