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:28 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 C9EDA21F8D88 for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 08:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.215
X-Spam-Level:
X-Spam-Status: No, score=-10.215 tagged_above=-999 required=5 tests=[AWL=0.384, 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 ZERBHX4fuaMo for <roll@ietfa.amsl.com>; Thu, 1 Nov 2012 08:28:44 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 046DC21F8D86 for <roll@ietf.org>; Thu, 1 Nov 2012 08:28:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1166; q=dns/txt; s=iport; t=1351783724; x=1352993324; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=SgeF/4Evh+PwrQxzZyTCm4+3il6J/TBQsdxzR6LW/vo=; b=Oi/Ej3gxjRJ2bs6eWZ7SIJKu/hsq7NYcR4yt7zpaC6AkNj/8K/TTQ0MZ B2Uzhb+5me1gSpIJyliGo0L4TOsk+HYEHFWmhA4GtIKOMbum+u/Pudy1Q 11iEWUy8pC+klRFbWLkJRQRrugUNYqkSALR/ITjmLLTbXwJZwiHnpR3kF Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAB2UklCtJV2Y/2dsb2JhbABEw2uBCIIfAQEEEgFmEAIBCCIkMiUCBA4FCBqHZAucOKAwi3skhTZhA5cTjT2Ba4Jvghk
X-IronPort-AV: E=Sophos;i="4.80,693,1344211200"; d="scan'208";a="137825282"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP; 01 Nov 2012 15:28:43 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qA1FShLm000880 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 1 Nov 2012 15:28:43 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.200]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.001; Thu, 1 Nov 2012 10:28:43 -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: AQHNuEWTVKkUNGCnjEqLpghV1euTUw==
Date: Thu, 01 Nov 2012 15:28:42 +0000
Message-ID: <B50D0F163D52B74DA572DD345D5044AF0F6EF7A3@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--21.239000-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: <FADF30F75030554E99C2BE1EAFF9CDCB@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:28:44 -0000

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

v2.23.0 | Report a Bug | By Email