Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain
"Jonathan Hui (johui)" <johui@cisco.com> Fri, 02 November 2012 01:13 UTC
Return-Path: <johui@cisco.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 A6CB921F89F5 for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 18:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fV9V0wYFA206 for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 18:13:24 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id C64BB21F89A8 for <roll@ietf.org>; Thu, 1 Nov 2012 18:13:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3274; q=dns/txt; s=iport; t=1351818804; x=1353028404; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Q96wuvcujGxmIlwEr1UMpcLaY5ks6rh7qUV90eay7Y8=; b=HorVgPak0PD0mV7biYFIZs5tWwm/qqMFDKnaP3APuHe9V3g891IRsPst vKYJExNi0shxjQFI0N37piqRSEGpvUg2P9CxGr/4rpGyRolqNUJ3vVp3d 71FNzuseC434SndGmkddVbBvE+r36xEcz0IXCq/7wKiA/HE2Bpx5KBVt4 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAIwdk1CtJXHB/2dsb2JhbABEwzKBCIIeAQEBAwEBAQEPAVsLBQsCAQgOCgoCIicLJQIEDgUIGodeBgucfqAei3skhTZhA5cTjT2Ba4JvgWQXHg
X-IronPort-AV: E=Sophos;i="4.80,696,1344211200"; d="scan'208";a="137961407"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-8.cisco.com with ESMTP; 02 Nov 2012 01:13:24 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id qA21DOUj019683 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 Nov 2012 01:13:24 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.200]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.001; Thu, 1 Nov 2012 20:13:24 -0500
From: "Jonathan Hui (johui)" <johui@cisco.com>
To: Dario Tedeschi <dat@exegin.com>
Thread-Topic: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain
Thread-Index: AQHNuEWTVKkUNGCnjEqLpghV1euTUw==
Date: Fri, 02 Nov 2012 01:13:23 +0000
Message-ID: <B50D0F163D52B74DA572DD345D5044AF0F6F22CD@xmb-rcd-x04.cisco.com>
References: <058.e817419e990e1afb26be9aa25d5cfc21@trac.tools.ietf.org> <B50D0F163D52B74DA572DD345D5044AF0F6EF7A3@xmb-rcd-x04.cisco.com> <50931AE9.9030800@exegin.com>
In-Reply-To: <50931AE9.9030800@exegin.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.84.164]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19328.001
x-tm-as-result: No--38.895900-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <4083C02167F3E34CB7A9727279887564@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "roll@ietf.org WG" <roll@ietf.org>, "draft-ietf-roll-trickle-mcast@tools.ietf.org" <draft-ietf-roll-trickle-mcast@tools.ietf.org>, "mcr@sandelman.ca" <mcr@sandelman.ca>
Subject: Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 02 Nov 2012 01:13:26 -0000
Hi Dario, Unicast-prefix-based multicast addresses also contain a scope identifier. So while the prefix does bound the scope, the scope of a prefix can contain multiple scopes. In any case, I don't think I properly articulated what I had in mind in my email below. It seems that we are converging on a definition where an MPL domain is defined by the IPv6 multicast address that interfaces subscribe to. In other words, an IPv6 multicast address identifies an MPL domain. All MPL multicast packets containing an MPL Option must have the IPv6 Destination Address set to the MPL domain that they are being transported in. If an MPL forwarder wants to forward a multicast packet within an MPL domain and that multicast packet does not have an IPv6 Destination Address corresponding to the domain's IPv6 multicast address, then the forwarder MUST encapsulate it. So now it becomes a simple address match rather whether an IPv6 address is within the scope zone. Does that solve the issue? -- Jonathan Hui On Nov 1, 2012, at 5:59 PM, Dario Tedeschi <dat@exegin.com> wrote: > I'm not so sure. What if, for example, I connected my BR to an existing network that already had say scope 4 (admin-scope) configured to cover a wider domain than just the PAN. I then could not configure the BR to report 4 as the scope of the PAN (the "MPL scope"). Yes, one could use scope 3, but it is currently reserved. Besides, it wouldn't really solve the problem, if you consider that scope 3 could quite easily also cover a wider domain than just the PAN. > > This is where unicast-prefix-based multicast addressing would become useful. It would remove the need for an "MPL scope", since the MPL domain would be defined by the PAN's prefix. > > - Dario > > > On 01/11/2012 8:28 AM, Jonathan Hui (johui) wrote: >> If the draft indicates that the MPL domain scope is a required configuration parameter, would that be sufficient? >> >> -- >> Jonathan Hui >> >> On Oct 31, 2012, at 7:37 AM, roll issue tracker<trac+roll@trac.tools.ietf.org> wrote: >> >>> #105: trickle-mcast: how to determine scope of MPL domain >>> >>> There's no explanation on how a node would determine what scope >>> corresponds >>> to a MPL domain. How would it do that without being given some additional >>> information from the edge-router/s. I think what is needed, here, is some >>> multicast routing information from the edge-router/s. >>> >>> -- >>> -----------------------------+--------------------------------------------- >>> Reporter: mcr@… | Owner: draft-ietf-roll-trickle-mcast@… >>> Type: defect | Status: new >>> Priority: major | Milestone: >>> Component: trickle-mcast | Version: >>> Severity: In WG Last Call | Keywords: >>> -----------------------------+--------------------------------------------- >>> >>> Ticket URL:<http://trac.tools.ietf.org/wg/roll/trac/ticket/105> >>> roll<http://tools.ietf.org/wg/roll/> >>> >> _______________________________________________ >> Roll mailing list >> Roll@ietf.org >> https://www.ietf.org/mailman/listinfo/roll >
- [Roll] [roll] #105: trickle-mcast: how to determi… roll issue tracker
- Re: [Roll] [roll] #105: trickle-mcast: how to det… roll issue tracker
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dario Tedeschi
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Jonathan Hui (johui)
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Jonathan Hui (johui)
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Don Sturek
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Jonathan Hui (johui)
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dario Tedeschi
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Jonathan Hui (johui)
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Jonathan Hui (johui)
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dario Tedeschi
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dario Tedeschi
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Yoshihiro Ohba
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Jonathan Hui (johui)
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dario Tedeschi
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Michael Richardson
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Jonathan Hui (johui)
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Robert Cragie
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dario Tedeschi
- Re: [Roll] [roll] #105: trickle-mcast: how to det… peter van der Stok
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dario Tedeschi
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dario Tedeschi
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dario Tedeschi
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Michael Richardson
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Michael Richardson
- Re: [Roll] [roll] #105: trickle-mcast: how to det… peter van der Stok
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Robert Cragie
- Re: [Roll] [roll] #105: trickle-mcast: how to det… roll issue tracker
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dijk, Esko
- Re: [Roll] [roll] #105: trickle-mcast: how to det… peter van der Stok
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dijk, Esko
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Don Sturek
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Don Sturek
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Robert Cragie
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dario Tedeschi
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dijk, Esko
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dijk, Esko
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dijk, Esko
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Dijk, Esko
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Michael Richardson
- Re: [Roll] [roll] #105: trickle-mcast: how to det… Robert Cragie
- Re: [Roll] [roll] #105: trickle-mcast: how to det… roll issue tracker
- Re: [Roll] [roll] #105: trickle-mcast: how to det… roll issue tracker