IETF Logo Mail Archive

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

"Jonathan Hui (johui)" <johui@cisco.com> Mon, 28 January 2013 17:14 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 E9C0F21F87FE for <roll@ietfa.amsl.com>; Mon, 28 Jan 2013 09:14:39 -0800 (PST)
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=[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 CN3K+ibxQHhb for <roll@ietfa.amsl.com>; Mon, 28 Jan 2013 09:14:35 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 8C9A821F862E for <roll@ietf.org>; Mon, 28 Jan 2013 09:14:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1784; q=dns/txt; s=iport; t=1359393275; x=1360602875; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=YUKesJZcmK2p/gexISwTorOwbO19KvwQWdTo7Jc6UDo=; b=hjOSQY/n75BXkbuy7UPtgor08+BRgtqABB+aiczhXfAxdiNhRpFE5DUZ L3i8okotRh2GfnPUgPEE/WI6aVxem+RQDc+Nee3hUP85b7g/xr+a2tyJM LV6UtelWTlzDKHXoYhr01QEr7fSy3BThmte/FKf5RnBQgLjQBZscC0U8q E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAK2xBlGtJXG8/2dsb2JhbABEvlQWc4IeAQEBAwEBAQE3NAsFCwIBCBgKFBAhBgslAgQOBQiHdwMJBgy2IQ2JUQSMEIQ0YQOUN40MhRKCd4Ik
X-IronPort-AV: E=Sophos;i="4.84,553,1355097600"; d="scan'208";a="169272327"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 28 Jan 2013 17:14:35 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r0SHEZvu005244 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 28 Jan 2013 17:14:35 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.79]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.004; Mon, 28 Jan 2013 11:14:34 -0600
From: "Jonathan Hui (johui)" <johui@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Thread-Topic: [Roll] Discussion/Comments For draft-ietf-roll-trickle-mcast-03
Thread-Index: AQHN/W9oT2fXxKK2sEKFqr+pjlBCPw==
Date: Mon, 28 Jan 2013 17:14:34 +0000
Message-ID: <B50D0F163D52B74DA572DD345D5044AF186E4839@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> <CADnDZ8896uFgWnDL4Vf7jvVhTPS30zxD1BsRbuLkhTHymyUdNw@mail.gmail.com>
In-Reply-To: <CADnDZ8896uFgWnDL4Vf7jvVhTPS30zxD1BsRbuLkhTHymyUdNw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [128.107.155.2]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9C6E32A74781684A86AA38A30184F47E@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:14:40 -0000

Correct.  An MPL Forwarder forwards a message to its next hop using link-layer multicast (which many LLN technologies map to link-layer broadcast).

--
Jonathan Hui

On Jan 28, 2013, at 9:11 AM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:

> 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
>> 
>> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll

v2.23.0 | Report a Bug | By Email