IETF Logo Mail Archive

Re: [ssm] what to say about scoping for v6 [was ...last call...]

Brian Haberman <bkhabs@nc.rr.com> Wed, 12 March 2003 18:50 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 NAA16015 for <ssm-archive@odin.ietf.org>; Wed, 12 Mar 2003 13:50:15 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h2CJ4Ja04172 for ssm-archive@odin.ietf.org; Wed, 12 Mar 2003 14:04:19 -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 h2CJ4JO04169 for <ssm-web-archive@optimus.ietf.org>; Wed, 12 Mar 2003 14:04:19 -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 NAA15967 for <ssm-web-archive@ietf.org>; Wed, 12 Mar 2003 13:49:43 -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 h2CJ3ZO04050; Wed, 12 Mar 2003 14:03:35 -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 h2CIw3O03825 for <ssm@optimus.ietf.org>; Wed, 12 Mar 2003 13:58:03 -0500
Received: from ms-smtp-02.southeast.rr.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15820 for <ssm@ietf.org>; Wed, 12 Mar 2003 13:43:28 -0500 (EST)
Received: from mail4.nc.rr.com (fe4 [24.93.67.51]) by ms-smtp-02.southeast.rr.com (8.12.5/8.12.2) with ESMTP id h2CIhHgQ004897; Wed, 12 Mar 2003 13:43:17 -0500 (EST)
Received: from nc.rr.com ([63.109.132.2]) by mail4.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); Wed, 12 Mar 2003 13:46:22 -0500
Message-ID: <3E6F8024.40405@nc.rr.com>
Date: Wed, 12 Mar 2003 13:44:52 -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] what to say about scoping for v6 [was ...last call...]
References: <20030312180804.1788F10B7A7@holbrook-laptop.cisco.com>
In-Reply-To: <20030312180804.1788F10B7A7@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:
>>However, I'd like a statement in the security considerations, perhaps 
>>along the lines of:
>>
>>One should note that the use of IPv6 scoped addresses either in S or G may
>>cause significant complexities, for example regarding mismatching scopes
>>between S and G or regarding forwarding decisions for a scoped (S,G).  
>>The implications of scoped addresses are described in other documents
>>[REF:SCOPED-ARCH]
> 
> 
> Isn't the scoping behavior simply that the most restrictive (smallest)
> scope applies.  A packet is forwarded neither across a source-scope
> boundary nor across a destination-scope boundary.  Unless I'm missing
> something, this actually sounds rather uncomplicated to me.  Is there
> something that makes this tricky?

Not that I am aware of.

> 
> Is there something about this that makes it a Security Considerations
> issue?

I don't see a huge need for it.  Especially since it affects all
forwarding of scoped addresses, not just multicast.

Brian

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

v2.23.0 | Report a Bug | By Email