IETF Logo Mail Archive

Re: [Roll] trickle-mcast-04 - Clarify scope value of 3 - subnet-local

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 17 July 2013 18:34 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47F6021F9A1C; Wed, 17 Jul 2013 11:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7RgAB9d6YFud; Wed, 17 Jul 2013 11:34:33 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 9AED921F99C3; Wed, 17 Jul 2013 11:34:33 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:3a60:77ff:fe38:e647]) by tuna.sandelman.ca (Postfix) with ESMTP id 685012017C; Wed, 17 Jul 2013 15:39:31 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id AD2AC63A7C; Wed, 17 Jul 2013 14:32:56 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 996CB63732; Wed, 17 Jul 2013 14:32:56 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, ipv6@ietf.org
In-Reply-To: <38A9423D-BBD7-48E9-846F-C1360BEFEE85@gmail.com>
References: <067.7473226c34e99536104b136c326ce300@trac.tools.ietf.org> <082.6ab8f10970432e6f2bb367aa0b632dda@trac.tools.ietf.org> <23575.1373577247@sandelman.ca> <4518F39EB578034D8C99A9B7776CDBA3793403@xmb-aln-x04.cisco.com> <4874.1373906541@sandelman.ca> <E045AECD98228444A58C61C200AE1BD841374DAF@xmb-rcd-x01.cisco.com> <38A9423D-BBD7-48E9-846F-C1360BEFEE85@gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 17 Jul 2013 14:32:56 -0400
Message-ID: <11395.1374085976@sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [Roll] trickle-mcast-04 - Clarify scope value of 3 - subnet-local
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2013 18:34:44 -0000

Ralph Droms <rdroms.ietf@gmail.com> wrote:
    > This draft is on the 6man agenda for Berlin.  I expect the discussion
    > will be taken up there.

    > In my opinion, the multicast scope should not be tied, thought the
    > words in the description of the scope, to the address assignment
    > architecture.

Do you have a specific use case that you are thinking of?

How can it be tied to the subnet, and yet not be related to the address
assignment architecture?  Can you suggest another definition?





--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works

v2.23.0 | Report a Bug | By Email