Re: [Roll] [roll] #128: Trickle multicast could be considered in other applications?
"roll issue tracker" <trac+roll@trac.tools.ietf.org> Tue, 02 July 2013 14:40 UTC
Return-Path: <trac+roll@trac.tools.ietf.org>
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 EA3F221F9F28 for <roll@ietfa.amsl.com>; Tue, 2 Jul 2013 07:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level:
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Q8hpS3kMsVP3 for <roll@ietfa.amsl.com>; Tue, 2 Jul 2013 07:40:19 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8A521F9F23 for <roll@ietf.org>; Tue, 2 Jul 2013 07:40:19 -0700 (PDT)
Received: from localhost ([127.0.0.1]:56630 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+roll@trac.tools.ietf.org>) id 1Uu1kW-00046Z-BY; Tue, 02 Jul 2013 16:40:08 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: roll issue tracker <trac+roll@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: johui@cisco.com, mariainesrobles@gmail.com, mcr@sandelman.ca
X-Trac-Project: roll
Date: Tue, 02 Jul 2013 14:40:07 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/roll/trac/ticket/128#comment:2
Message-ID: <082.d1078fc5c4cb437a2c2c83a3dc10d6a9@trac.tools.ietf.org>
References: <067.081907fd6195c3034e6e8c71a7eb4a93@trac.tools.ietf.org>
X-Trac-Ticket-ID: 128
In-Reply-To: <067.081907fd6195c3034e6e8c71a7eb4a93@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: johui@cisco.com, mariainesrobles@gmail.com, mcr@sandelman.ca, roll@ietf.org
X-SA-Exim-Mail-From: trac+roll@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Cc: roll@ietf.org
Subject: Re: [Roll] [roll] #128: Trickle multicast could be considered in other applications?
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: 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: Tue, 02 Jul 2013 14:40:20 -0000
#128: Trickle multicast could be considered in other applications? Comment (by mcr@sandelman.ca): > can MPL operate in a mixed environment where not all routers are MPL capable? I think that MPL can not operate in a mixed environment. An MPL aware router could route between MPL and traditional multicast routing protocols, and this could occur even if the router was one-armed. > do the hosts need to be in any way aware that their mcast is supported by MPL? I believe that non-MPL aware hosts will not be listening to the right subnet-local mcast groups, and so they will not see the MPL. MPL and non-MPL multicast will be ships in the night. -- ---------------------------------------+------------------------------ Reporter: mariainesrobles@gmail.com | Owner: johui@cisco.com Type: enhancement | Status: new Priority: minor | Milestone: Component: trickle-mcast | Version: Severity: In WG Last Call | Resolution: Keywords: | ---------------------------------------+------------------------------ Ticket URL: <http://trac.tools.ietf.org/wg/roll/trac/ticket/128#comment:2> roll <http://tools.ietf.org/wg/roll/>
- [Roll] [roll] #128: Trickle multicast could be co… roll issue tracker
- Re: [Roll] [roll] #128: Trickle multicast could b… roll issue tracker
- Re: [Roll] [roll] #128: Trickle multicast could b… roll issue tracker
- Re: [Roll] [roll] #128: Trickle multicast could b… roll issue tracker
- Re: [Roll] [roll] #128: Trickle multicast could b… Michael Richardson
- Re: [Roll] [roll] #128: Trickle multicast could b… Kerry Lynn
- Re: [Roll] [roll] #128: Trickle multicast could b… Michael Richardson
- Re: [Roll] [roll] #128: Trickle multicast could b… Kerry Lynn
- Re: [Roll] [roll] #128: Trickle multicast could b… Michael Richardson
- Re: [Roll] [roll] #128: Trickle multicast could b… Dijk, Esko
- Re: [Roll] [roll] #128: Trickle multicast could b… Don Sturek
- Re: [Roll] [roll] #128: Trickle multicast could b… Dijk, Esko
- Re: [Roll] [roll] #128: Trickle multicast could b… Robert Cragie
- Re: [Roll] [roll] #128: Trickle multicast could b… Robert Cragie
- Re: [Roll] [roll] #128: Trickle multicast could b… Michael Richardson
- Re: [Roll] [roll] #128: Trickle multicast could b… Dijk, Esko
- Re: [Roll] [roll] #128: Trickle multicast could b… Don Sturek
- Re: [Roll] [roll] #128: Trickle multicast could b… roll issue tracker
- Re: [Roll] [roll] #128: Trickle multicast could b… roll issue tracker