IETF Logo Mail Archive

Re: [Roll] [roll] #105: trickle-mcast: how to determine scope of MPL domain

"Jonathan Hui (johui)" <johui@cisco.com> Thu, 01 November 2012 15:56 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 2906E21F8F22 for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 08:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.27
X-Spam-Level:
X-Spam-Status: No, score=-10.27 tagged_above=-999 required=5 tests=[AWL=0.329, 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 Z0SPmWPaLNUJ for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 08:56:57 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 09C0621F8F1E for <roll@ietf.org>; Thu, 1 Nov 2012 08:56:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2323; q=dns/txt; s=iport; t=1351785417; x=1352995017; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yAg8gfN7U/ntGJ+/4ZgFeRe5FadRTb0xM2iNgtDnIi4=; b=MWNyW/gHd8g7ebHSwD1NCvw9hOlXILMH2JalDxHJkANNabpj7b/kBcIF 7GfFU1OxKB9r78vdCpClZj2vbi9nKp9buThrtnCV17HAG9sIpxJOzhvgk 1GuHbgLtwxh+fFLPk6H2PM/J+cZFo6G7wFWfK3yDf9g8bMK458VHW39qo E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAJKbklCtJXG9/2dsb2JhbAA6CsNrgQiCHwEBBBIBZhACAQgiJDIlAgQOBQgah2QLnEKgMot7EBSFNmEDlxONPYFrgm+CGQ
X-IronPort-AV: E=Sophos;i="4.80,693,1344211200"; d="scan'208";a="137829714"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-3.cisco.com with ESMTP; 01 Nov 2012 15:56:47 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id qA1Fuke9017646 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 1 Nov 2012 15:56:46 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.200]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.001; Thu, 1 Nov 2012 10:56:46 -0500
From: "Jonathan Hui (johui)" <johui@cisco.com>
To: "<roll@ietf.org>" <roll@ietf.org>
Thread-Topic: [roll] #105: trickle-mcast: how to determine scope of MPL domain
Thread-Index: AQHNuEl+VKkUNGCnjEqLpghV1euTUw==
Date: Thu, 01 Nov 2012 15:56:45 +0000
Message-ID: <B50D0F163D52B74DA572DD345D5044AF0F6EFA99@xmb-rcd-x04.cisco.com>
References: <058.e817419e990e1afb26be9aa25d5cfc21@trac.tools.ietf.org>
In-Reply-To: <058.e817419e990e1afb26be9aa25d5cfc21@trac.tools.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [128.107.155.10]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19328.001
x-tm-as-result: No--25.507300-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: <7870D56ED88C874698B37ADA81201EA4@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<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: Thu, 01 Nov 2012 15:56:58 -0000

[attempting to move the discussion to this ticket thread]

Peter has two concerns:
1) Encapsulation when the source and destination of a multicast packet are within the same MPL domain.
2) Limiting the physical extent of an MPL domain to a connected subset of devices within an LLN.

Restricting the MPL scope to link-local and requiring encapsulation for non-link-local multicast does not address either of Peter's concerns.

I think we can solve (2) by allowing the MPL scope to be non-link-local but still require encapsulation.  The outer IPv6 header's IPv6 Destination Address then serves to identify the MPL domain, with the IPv6 Destination Address carrying the IPv6 multicast group address for the MPL domain.  Of course, MPL interfaces would need to be configured with the appropriate IPv6 multicast group(s), but the actual configuration method can be left out-of-scope for this draft.

I think we can also solve (1) and (2) simultaneously if we require the IPv6 Destination Address to identify both the MPL domain and application endpoints.  Said differently, if the IPv6 Destination for the packet corresponds to the IPv6 multicast group address for an MPL domain, then no encapsulation is required.

Thoughts?

--
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/>
>

v2.23.0 | Report a Bug | By Email