IETF Logo Mail Archive

Re: [Roll] Consensus Call -- resolution for #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local

<yoshihiro.ohba@toshiba.co.jp> Sun, 03 November 2013 08:09 UTC

Return-Path: <yoshihiro.ohba@toshiba.co.jp>
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 A161411E81B8 for <roll@ietfa.amsl.com>; Sun, 3 Nov 2013 01:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.741
X-Spam-Level:
X-Spam-Status: No, score=-6.741 tagged_above=-999 required=5 tests=[AWL=1.349, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-8, UNPARSEABLE_RELAY=0.001]
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 Me6Qz6pfC+5J for <roll@ietfa.amsl.com>; Sun, 3 Nov 2013 01:09:21 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE7B11E81BA for <roll@ietf.org>; Sun, 3 Nov 2013 01:09:18 -0700 (PDT)
Received: from tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp ([133.199.232.103]) by imx12.toshiba.co.jp with ESMTP id rA389AOB008974 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 3 Nov 2013 17:09:10 +0900 (JST)
Received: from tsbmgw-mgw01 (localhost [127.0.0.1]) by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id rA389AiL009572; Sun, 3 Nov 2013 17:09:10 +0900
Received: from localhost ([127.0.0.1]) by tsbmgw-mgw01 (JAMES SMTP Server 2.3.1) with SMTP ID 32; Sun, 3 Nov 2013 17:09:10 +0900 (JST)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by tsbmgw-mgw01.tsbmgw-mgw01.toshiba.co.jp (8.13.8/8.14.5) with ESMTP id rA389A28009569; Sun, 3 Nov 2013 17:09:10 +0900
Received: (from root@localhost) by arc11.toshiba.co.jp id rA389AWE022878; Sun, 3 Nov 2013 17:09:10 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id TAA22877; Sun, 3 Nov 2013 17:09:10 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id rA38998s017197; Sun, 3 Nov 2013 17:09:09 +0900 (JST)
Received: from tgxml345.toshiba.local by toshiba.co.jp id rA3899pb001326; Sun, 3 Nov 2013 17:09:09 +0900 (JST)
Received: from TGXML338.toshiba.local ([169.254.4.201]) by tgxml345.toshiba.local ([133.199.60.32]) with mapi id 14.03.0158.001; Sun, 3 Nov 2013 17:09:09 +0900
From: yoshihiro.ohba@toshiba.co.jp
To: roll@ietf.org
Thread-Topic: [Roll] Consensus Call -- resolution for #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local
Thread-Index: AQHO11wkInPumryEmEql3T+C/ZlDXpoTKBeA
Date: Sun, 03 Nov 2013 08:09:09 +0000
Message-ID: <674F70E5F2BE564CB06B6901FD3DD78B1888633B@tgxml338.toshiba.local>
References: <067.7473226c34e99536104b136c326ce300@trac.tools.ietf.org> <082.6d923b56e89f979e00a33a1bab8bbfc5@trac.tools.ietf.org> <13799.1383338682@sandelman.ca>
In-Reply-To: <13799.1383338682@sandelman.ca>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
x-originating-ip: [133.199.75.175]
msscp.transfermailtomossagent: 103
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mariainesrobles@gmail.com, johui@cisco.com, rdroms@cisco.com
Subject: Re: [Roll] Consensus Call -- resolution for #132: draft-ietf-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: Sun, 03 Nov 2013 08:09:27 -0000

I prefer describing 802.15.4-specific realm-local scope boundary definition in another RFC so that both trickle-mcast and multicast-scopes drafts are fully independent of any link-layer.   

Regards,
Yoshihiro Ohba


-----Original Message-----
From: roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] On Behalf Of Michael Richardson
Sent: Saturday, November 02, 2013 5:45 AM
To: roll@ietf.org
Cc: mariainesrobles@gmail.com; johui@cisco.com; rdroms@cisco.com
Subject: [Roll] Consensus Call -- resolution for #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local


I would like to ask the WG to speak now if you object to this solution, specifically with the the text going into mcast-05.

Ralph wrote:
>  This text could be added to draft-ietf-roll-trickle-mcast-05, or to
>  draft-ietf-6man-multicast-scopes-00 or published separately in yet  
> another "world's shortest RFC".
> 
>  Second, draft-ietf-roll-trickle-mcast-05 should be changed to read:
> 
>     When used with MPL, Realm-local scope is defined according to the
>     underlying network technology; for example, [cite the
>     IP-over-IEEE802.15.4 definition].
> 
>  As a further refinement, I suggest text be added to
>  draft-ietf-roll-trickle-mcast-05 to the effect of:
> 
>     "scop 4" can also be used with MPL to cover deployments that use
>     administratively defined scopes that cover, for example, subnets
>     based on different underlying network technologies.
> 
>  - Ralph

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works 
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/

v2.23.0 | Report a Bug | By Email