Re: [Roll] draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
"Popa, Daniel" <Daniel.Popa@itron.com> Fri, 25 October 2013 11:35 UTC
Return-Path: <Daniel.Popa@itron.com>
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 00CD111E831B for <roll@ietfa.amsl.com>; Fri, 25 Oct 2013 04:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level:
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 MXeWwfMtVRoZ for <roll@ietfa.amsl.com>; Fri, 25 Oct 2013 04:35:21 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0158.outbound.protection.outlook.com [207.46.163.158]) by ietfa.amsl.com (Postfix) with ESMTP id C4EF611E83BF for <roll@ietf.org>; Fri, 25 Oct 2013 04:35:19 -0700 (PDT)
Received: from CO1PR04MB346.namprd04.prod.outlook.com (10.141.52.25) by CO1PR04MB345.namprd04.prod.outlook.com (10.141.52.20) with Microsoft SMTP Server (TLS) id 15.0.785.10; Fri, 25 Oct 2013 11:35:14 +0000
Received: from CO1PR04MB346.namprd04.prod.outlook.com ([169.254.1.219]) by CO1PR04MB346.namprd04.prod.outlook.com ([169.254.1.238]) with mapi id 15.00.0785.001; Fri, 25 Oct 2013 11:35:14 +0000
From: "Popa, Daniel" <Daniel.Popa@itron.com>
To: "consultancy@vanderstok.org" <consultancy@vanderstok.org>, Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
Thread-Index: AQHO0DhAMKsCNOt2fEejpOHp8pqxMpoDbJ2AgAHC0gCAABmFoA==
Date: Fri, 25 Oct 2013 11:35:13 +0000
Message-ID: <dff48375f5b44926bdcf392a82927406@CO1PR04MB346.namprd04.prod.outlook.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <CAJE_bqdL3v4XK+dJPx1ZVFoRS+yjFDZEwVZ64fhYW6QUWVS6JA@mail.gmail.com> <52FECA00-C316-4693-A821-7EA6510AC0F8@gmail.com> <CAJE_bqcvQSiNTbbOvUEBvLC1uK5kAFfF04ZbQ=DFpwKb+ynATw@mail.gmail.com> <CABOxzu20qONjQ71EWyob2Th+PJGpFz_Cw8jhvbmiEtojd+ihHg@mail.gmail.com> <CADrU+dJQdxWoEpLdZq_vYf1CcV1nh43v+votYZ4WCqwj+o1r3Q@mail.gmail.com> <1889382d8c35c9325f1bc615f6bf6c8e@xs4all.nl>
In-Reply-To: <1889382d8c35c9325f1bc615f6bf6c8e@xs4all.nl>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [109.2.132.2]
x-forefront-prvs: 0010D93EFE
x-forefront-antispam-report: SFV:NSPM; SFS:(377424004)(24454002)(199002)(189002)(55784002)(51704005)(377454003)(63696002)(81342001)(65816001)(74316001)(85306002)(66066001)(80022001)(81686001)(69226001)(81816001)(74662001)(31966008)(47446002)(74502001)(83322001)(81542001)(80976001)(19580405001)(19580395003)(15975445006)(76786001)(74706001)(56776001)(76796001)(50986001)(49866001)(47976001)(33646001)(47736001)(51856001)(46102001)(54316002)(54356001)(77982001)(4396001)(56816003)(53806001)(85806002)(59766001)(77096001)(76576001)(76482001)(83072001)(79102001)(74876001)(74366001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR04MB345; H:CO1PR04MB346.namprd04.prod.outlook.com; CLIP:109.2.132.2; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: itron.com
Subject: Re: [Roll] draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [roll] #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: Fri, 25 Oct 2013 11:35:26 -0000
Hi Peter, By "homogeneous multi-link network" do you refer to "homogeneous link-layer technology" ? If this is the case, I suggest we do not correlate the scope of the multicast to the use of a specific link-layer technology... We should be able to deploy systems where all nodes in a multi-link network can be members of the same "multilink-local multicast scope", independently of the link-layer technology they use (homogeneous or heterogeneous) to communicate with each other. Regards, Daniel -----Message d'origine----- De : roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] De la part de peter van der Stok Envoyé : vendredi 25 octobre 2013 11:53 À : roll@ietf.org Objet : Re: [Roll] draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local) I like the consensus that seems to emerge. It should be clear that the realm-local specification concerns a homogeneous multi-link network For example: o Multiple links, following the same IP over Foo specification, and the interfaces attached to those links may form a multilink-local scope based on underlying network technology; for example, [cite the IP-over-IEEE802.15.4 definition]. Peter Robert Cragie schreef op 2013-10-24 08:59: > On 23 October 2013 22:38, Kerry Lynn <kerlyn@ieee.org> wrote: > >> On Wed, Oct 23, 2013 at 5:21 PM, 神明達哉 <jinmei@wide.ad.jp> >> wrote: >> >>> At Wed, 23 Oct 2013 15:56:46 -0400, >>> >>> Ralph Droms <rdroms.ietf@gmail.com> wrote: >>> >>>> Perhaps we want to go a step farther and take the zone boundary >>> text >>>> out of RFC 4007 altogether? >>> >>> Basically works for me. > > <RCC>Me too</RCC> > >>>> OLD: >>>> >>>> o The boundaries of zones of a scope other than >>> interface-local, >>>> link-local, and global must be defined and configured by >>> network >>>> administrators >>>> >>>> NEW: >>>> >>>> o The boundaries of zones of a scope are defined by the IPv6 >>>> addressing architecture. >>> >>> With a reference (it's currently RFC 4291)? >>> >>> I'd also note that not all points described in the RFC 4007 text are >>> described in RFC 4291 (at least not very clearly). So, not just >>> remove the text from RFC 4007, I'd like to unify it in the address >>> architecture, e.g. update the following part of RFC 4291: >>> >>> Admin-Local scope is the smallest scope that must be >>> administratively configured, i.e., not automatically derived from >>> physical connectivity or other, non-multicast-related configuration. >>> >>> as follows: >>> >>> Admin-Local scope is the smallest scope that must be >>> administratively configured, i.e., not automatically derived from >>> physical connectivity or other, non-multicast-related configuration. >>> For all non-reserved scopes except the global scope, the zone >>> boundaries must also be administratively configured. >> >> I think this statement is self-contradictory. When automatic >> configuration is discussed, it is in relation to zone boundaries. >> Here's an attempt to explain >> >> this without negations: >> >> Interface-Local, Link-Local, and Realm-Local scope boundaries are >> automatically >> >> derived from physical connectivity or other, non-multicast related >> configuration. >> >> Global scope has no boundary. The boundaries of all other >> non-reserved scopes >> >> are administratively configured. > > <RCC> > That makes it clear. IMO RFC4007 should be changed to something like: > > o Each interface on a node comprises a single zone of interface-local > scope (for multicast only). > > o Each link and the interfaces attached to that link comprise a single > zone of link-local scope (for both unicast and multicast). > > o Multiple links and the interfaces attached to those links may form a > multilink-local scope based on underlying network technology; for > example, [cite the IP-over-IEEE802.15.4 definition]. > > o There is a single zone of global scope (for both unicast and > multicast) comprising all the links and interfaces in the Internet. > > o The boundaries of zones of a scope other than interface-local, > link-local, multilink-local and global must be defined and configured > by network administrators. > > Either that or just remove the text as Ralph suggested earlier. > </RCC> > >> BTW, just my opinion, but "Realm-Local" might be more meaningfully >> named >> >> "Multilink-Local" > > <RCC> I agree - it is more meaningful</RCC> > >> -K- >> >>> -- >>> JINMEI, Tatuya >>> >> -------------------------------------------------------------------- >>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative >>> Requests: >>> https://www.ietf.org/mailman/listinfo/ipv6 [1] >>> >> -------------------------------------------------------------------- >> >> _______________________________________________ >> Roll mailing list >> Roll@ietf.org >> https://www.ietf.org/mailman/listinfo/roll [2] > > > > Links: > ------ > [1] https://www.ietf.org/mailman/listinfo/ipv6 > [2] https://www.ietf.org/mailman/listinfo/roll > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll _______________________________________________ Roll mailing list Roll@ietf.org https://www.ietf.org/mailman/listinfo/roll
- [Roll] [roll] #132: draft-ietf-roll-trickle-mcast… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- [Roll] trickle-mcast-04 - Clarify scope value of … Michael Richardson
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ulrich Herberg
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ulrich Herberg
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Don Sturek
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ulrich Herberg
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Jonathan Hui (johui)
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ulrich Herberg
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ralph Droms (rdroms)
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Don Sturek
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ulrich Herberg
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ralph Droms (rdroms)
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Michael Richardson
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Pascal Thubert (pthubert)
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ralph Droms
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Michael Richardson
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Abdussalam Baryun
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Robert Cragie
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Mark ZZZ Smith
- Re: [Roll] trickle-mcast-04 - Clarify scope value… peter van der Stok
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Michael Richardson
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ralph Droms (rdroms)
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ulrich Herberg
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Michael Richardson
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Robert Cragie
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Don Sturek
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ralph Droms (rdroms)
- Re: [Roll] trickle-mcast-04 - Clarify scope value… peter van der Stok
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Don Sturek
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Michael Richardson
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Michael Richardson
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Ralph Droms (rdroms)
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Robert Cragie
- Re: [Roll] trickle-mcast-04 - Clarify scope value… Michael Richardson
- Re: [Roll] trickle-mcast-04 - Clarify scope value… JINMEI Tatuya / 神明達哉
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Kerry Lynn
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Michael Richardson
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Kerry Lynn
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Ralph Droms
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Michael Richardson
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Ralph Droms (rdroms)
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Carsten Bormann
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Ralph Droms
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Ralph Droms
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Michael Richardson
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Don Sturek
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Ralph Droms (rdroms)
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Michael Richardson
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Michael Richardson
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Robert Cragie
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Don Sturek
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Ralph Droms
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Don Sturek
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Ralph Droms (rdroms)
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Michael Richardson
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Michael Richardson
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Kerry Lynn
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Michael Richardson
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Ralph Droms (rdroms)
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Kerry Lynn
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Richard Kelsey
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Ralph Droms (rdroms)
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Robert Cragie
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Robert Cragie
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Kerry Lynn
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Robert Cragie
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Kerry Lynn
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… peter van der Stok
- [Roll] draft-ietf-6man-multicast-scopes updates R… Ralph Droms
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Kerry Lynn
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… Ralph Droms
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Ralph Droms
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Kerry Lynn
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Robert Cragie
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… peter van der Stok
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Popa, Daniel
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Robert Cragie
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Ralph Droms (rdroms)
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Ralph Droms (rdroms)
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Kerry Lynn
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] Consensus Call -- resolution for #132:… Michael Richardson
- [Roll] Consensus Call -- resolution for #132: dra… Michael Richardson
- Re: [Roll] Consensus Call -- resolution for #132:… Kerry Lynn
- Re: [Roll] Consensus Call -- resolution for #132:… yoshihiro.ohba
- Re: [Roll] Consensus Call -- resolution for #132:… Michael Richardson
- Re: [Roll] Consensus Call -- resolution for #132:… Kerry Lynn
- Re: [Roll] Consensus Call -- resolution for #132:… Ralph Droms (rdroms)
- Re: [Roll] Consensus Call -- resolution for #132:… yoshihiro.ohba
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] Consensus Call -- resolution for #132:… Popa, Daniel
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… 神明達哉
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… 神明達哉
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… 神明達哉
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Dave Thaler
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Dave Thaler
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… 神明達哉
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Stig Venaas
- Re: [Roll] Consensus Call -- resolution for #132:… Robert Cragie
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] Consensus Call -- resolution for #132:… Michael Richardson
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker
- Re: [Roll] [roll] #132: draft-ietf-roll-trickle-m… roll issue tracker