IETF Logo Mail Archive

Re: [ssm] another last call for draft-ietf-ssm-arch - ending 3/24

Brian Haberman <bkhabs@nc.rr.com> Tue, 11 March 2003 14:11 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 JAA19969 for <ssm-archive@odin.ietf.org>; Tue, 11 Mar 2003 09:11:04 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h2BEOXM00627 for ssm-archive@odin.ietf.org; Tue, 11 Mar 2003 09:24:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BEOWO00624 for <ssm-web-archive@optimus.ietf.org>; Tue, 11 Mar 2003 09:24:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19942 for <ssm-web-archive@ietf.org>; Tue, 11 Mar 2003 09:10:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BEMGO00531; Tue, 11 Mar 2003 09:22:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2BELGO00497 for <ssm@optimus.ietf.org>; Tue, 11 Mar 2003 09:21:16 -0500
Received: from ms-smtp-03.southeast.rr.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19898 for <ssm@ietf.org>; Tue, 11 Mar 2003 09:07:17 -0500 (EST)
Received: from mail4.nc.rr.com (fe4 [24.93.67.51]) by ms-smtp-03.southeast.rr.com (8.12.5/8.12.2) with ESMTP id h2BDIaHU003192; Tue, 11 Mar 2003 08:19:40 -0500 (EST)
Received: from nc.rr.com ([63.109.132.2]) by mail4.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); Tue, 11 Mar 2003 07:50:17 -0500
Message-ID: <3E6DDB30.5040704@nc.rr.com>
Date: Tue, 11 Mar 2003 07:48:48 -0500
From: Brian Haberman <bkhabs@nc.rr.com>
Organization: No Organization Here
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: holbrook@cisco.com
CC: Pekka Savola <pekkas@netcore.fi>, ssm@ietf.org
Subject: Re: [ssm] another last call for draft-ietf-ssm-arch - ending 3/24
References: <20030311064938.AFB8210B7A7@holbrook-laptop.cisco.com>
In-Reply-To: <20030311064938.AFB8210B7A7@holbrook-laptop.cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Hugh Holbrook wrote:

>>Administrative scoping should not relied upon as a security measure
>>[ADMIN-SCOPE]; however, in many cases it is at least a part of security
>>solutions.  It should be noted that no administrative scoping exists for
>>IPv4 source-specific multicast.  An alternative approach is to configure
>>manual access-lists to create such scoping if necessary.
> 
> 
> This text looks pretty good to me.  I will add it to the Security
> Considerations section, barring any objects.

Looks fine to me.

Brian


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

v2.23.0 | Report a Bug | By Email