Re: [Roll] draft-ietf-roll-trickle-mcast-02 (proposed text)

I have several comments listed below:

1. Why is the S field needed when the seed's length can be determined by 
the Opt Data Len field?

2. Nodes that do not understand the Trickle Multicast option should 
*not* process the packet further. This is to ensure those nodes do not 
cause packet storms or pass multiple copies of the same multicast 
datagram to higher layers.

3. Consider setting the two high order bits in the option type to b01 
(discard the packet). This would be consistent with RFC 6553 and satisfy 
my comment 2.

4. Using the source IPv6 address as the seed won't work for hop-by-hop 
"tunneling", because the outer source address changes at each hop.

5. Exactly how is consistency/inconsistency used in the proactive mode? 
It doesn't seem to be explained anywhere.

6. For consistency, interoperability and implementation simplicity 
consider stipulating one scope used for the outer header (i.e. 
link-local scope).

7. Ideally, a link-local multicast group assigned to MPL should be used 
in the outer destination to ensure that only MPL aware nodes receive MPL 
encapsulated datagrams. An MPL multicast group would clearly define the 
boundaries of an MPL domain.

- Dario

On 03/08/2012 10:48 AM, Jonathan Hui (johui) wrote:
> We've been working on an update to draft-ietf-roll-trickle-mcast.  I've attached a draft of the proposed text.  Note that we will *not* be presenting this draft at the ROLL WG meeting.
>
> In a prior mail, I noted some deficiencies with the initial draft that was posted.  We will discuss some of these deficiencies at the ROLL WG meeting today.  The purpose of this mail is to give you some insight into solving those deficiencies as well as incorporating suggestions that were brought up on the list.  If you get a chance to glance through before the WG meeting, great.  In either case, let's continue the discussion on the list.
>
> Always looking for your feedback, especially from implementors.
>
> Thanks!
>
> --
> Jonathan Hui
>
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll