IETF Logo Mail Archive

Re: [Roll] Discussion/Comments For draft-ietf-roll-trickle-mcast-03

Abdussalam Baryun <abdussalambaryun@gmail.com> Mon, 28 January 2013 17:11 UTC

Return-Path: <abdussalambaryun@gmail.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 C4DF521F87E0 for <roll@ietfa.amsl.com>; Mon, 28 Jan 2013 09:11:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.589
X-Spam-Level:
X-Spam-Status: No, score=-3.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 CYkrca07Uyix for <roll@ietfa.amsl.com>; Mon, 28 Jan 2013 09:11:20 -0800 (PST)
Received: from mail-pb0-f45.google.com (mail-pb0-f45.google.com [209.85.160.45]) by ietfa.amsl.com (Postfix) with ESMTP id 56F0021F8480 for <roll@ietf.org>; Mon, 28 Jan 2013 09:11:20 -0800 (PST)
Received: by mail-pb0-f45.google.com with SMTP id rq13so1587986pbb.32 for <roll@ietf.org>; Mon, 28 Jan 2013 09:11:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=TqG69uJr+cqcpxEJzIJU5CcAOd3IbJearNdADgeVAHQ=; b=Hkx9QRNutRO/lNCysg1LU7Y8IVl3dSJfs+uSG6EkQ+96FO3ce08Wq0B5wJVrQtB0WM utC18FFK2e7jrN3VQy1ESQaA3z1P51h3YV5+bMWGkIKZCewaZNXH7g19Uy8Fs33nlXM+ BZFGFLi/I6R/NeRIIVAPRsfdPOONZ+4e2NlRt4EVWep7adwdti5XrwSEvt7aoCnACIke cpt0pbjROcqEm9Kh+ewyL3W7ooQiZdRVquX7QsKefzrVKWCRXdaw4KgRLuiJ/emsWQgA f5W9sFh7tBvaH0J6Oatuyjru2SAtzeozJYwGm5hlDA5iNr0FKkboJNNj1g0u3xzjLVtz 0ojg==
MIME-Version: 1.0
X-Received: by 10.66.72.226 with SMTP id g2mr37294883pav.67.1359393080109; Mon, 28 Jan 2013 09:11:20 -0800 (PST)
Received: by 10.68.218.134 with HTTP; Mon, 28 Jan 2013 09:11:20 -0800 (PST)
In-Reply-To: <B50D0F163D52B74DA572DD345D5044AF186E4782@xmb-rcd-x04.cisco.com>
References: <CADnDZ88Vq5h+dzJNQfCStc4w9G+Bqqk7A+uQo0bDPD=fhvE=TA@mail.gmail.com> <CADnDZ8_JLNMgPmd1ztChd63Fwjiw++JZ4fdPBv_wJNWcFBubmQ@mail.gmail.com> <B50D0F163D52B74DA572DD345D5044AF186E4114@xmb-rcd-x04.cisco.com> <CADnDZ89fjEqfWriDr9MerhgUZzqgccMDCEOctGGSwFEw2ktOCg@mail.gmail.com> <B50D0F163D52B74DA572DD345D5044AF186E448A@xmb-rcd-x04.cisco.com> <CADnDZ8_+27oxZg7Xu5k8t5B5QFQFRKs1EY5Vf7KSQe1hcckzug@mail.gmail.com> <B50D0F163D52B74DA572DD345D5044AF186E45D2@xmb-rcd-x04.cisco.com> <CADnDZ88u3ed3hEe_14mnpDH_O9JXbUNjyBRZ1ENpuJf5sBE1Kg@mail.gmail.com> <B50D0F163D52B74DA572DD345D5044AF186E4782@xmb-rcd-x04.cisco.com>
Date: Mon, 28 Jan 2013 18:11:20 +0100
Message-ID: <CADnDZ8896uFgWnDL4Vf7jvVhTPS30zxD1BsRbuLkhTHymyUdNw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Jonathan Hui (johui)" <johui@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "richard.kelsey@silabs.com Kelsey" <richard.kelsey@silabs.com>, roll WG <roll@ietf.org>
Subject: Re: [Roll] Discussion/Comments For draft-ietf-roll-trickle-mcast-03
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: Mon, 28 Jan 2013 17:11:20 -0000

Ok so my understanding before was correct. Therefore, inside the MPL
domain there is no need for IP multicast, just MPL multicast using its
forwarders, is this correct?

AB

On 1/28/13, Jonathan Hui (johui) <johui@cisco.com> wrote:
>
> IPv6-in-IPv6 encapsulation is not required if the IPv6 Destination Address
> is the MPL Domain Address.
>
> But whether or not encapsulation is used, Section 10.1 specifies:
>
>      The IPv6 Destination Address MUST be set to the MPL Domain Address
>       corresponding to the MPL Domain.
>
> And as Section 2 specifies, the MPL Domain Address is a multicast address.
>
> --
> Jonathan Hui
>
> On Jan 28, 2013, at 9:01 AM, Abdussalam Baryun <abdussalambaryun@gmail.com>
> wrote:
>
>> On 1/28/13, Jonathan Hui (johui) <johui@cisco.com> wrote:
>>>
>>> MPL forwards IPv6 multicast messages using IPv6 multicast messages
>>> (hence
>>> the IPv6-in-IPv6 encapsulation).
>>>
>>
>> So I understand from your reply that MPL uses always IPv6 multicast
>> encapsulation for its data. I thought before it was only outside the
>> MPL domains, that it will use IP-in-IP
>>
>> AB
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
>
>

v2.23.0 | Report a Bug | By Email