Re: [Roll] Last Call: draft-ietf-roll-trickle-mcast-05.txt

On Oct 23, 2013, at 2:19 PM 10/23/13, Michael Richardson <mcr+ietf@sandelman.ca> wrote:

> 
> Ines  Robles <mariainesrobles@googlemail.com> wrote:
>> Just a reminder, 
> 
> Thanks.
> 
>> So far, there are three open tickets:
> 
>> Ticket #103: trickle-mcast: suppress ICMP messages for
>> PROACTIVE_TIMER_EXPIRATIONS
> 
> I don't think we got consensus on this, but maybe I'm wrong.
> 
>> Ticket #132: 
> 
>> draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 -
>> subnet-local
> 
> I really don't understand the dispute, and it's gonna take some in-person
> discussion.

Without a WG meeting in Vancouver, how will this in-person discussion take place?

I'd be happy to have a one-to-one or sponsor a multi-way teleconf to discuss the issue.

In my opinion, the problem is pretty clear:

 draft-ietf-roll-trickle-mcast-05 and draft-ietf-6man-multicast-scopes-00
 are in conflict with each other.

 From draft-ietf-roll-trickle-mcast-05:

    When
    used with MPL, Realm-Local scope is administratively defined and used
    to define the boundaries of multicast message dissemination by MPL.

 From draft-ietf-6man-multicast-scopes-00:

    Realm-Local scope is the largest scope that is automatically
    configured, i.e., automatically derived from physical
    connectivity or other, non-multicast-related configuration.

 Specifically, "administratively defined" seems to me to be in direct
 conflict with "automatically configured".

Part of the solution will require either a change in either draft-ietf-roll-trickle-mcast or draft-ietf-6man-multicast-scopes.  I think we have WG support, if not consensus, to edit draft-ietf-roll-trickle-mcast-05:

OLD:

    When
    used with MPL, Realm-Local scope is administratively defined and used
    to define the boundaries of multicast message dissemination by MPL.

NEW:

    When
    used with MPL, Realm-Local scope is defined according to
    the underlying network technology; for example, [cite the
    IP-over-IEEE802.15.4 definition].

One additional bit of text is needed, but not necessarily in draft-ietf-roll-trickle-mcast, to define explicitly the meaning of scop 3 in an IEEE802.15.4 network (which is the definition to be cited in the NEW text above):

    When used in an IP-over-IEEE802.15.4 network, "scop 3" is defined
    to include all interfaces sharing a PAN ID.

As a further refinement, I suggest text be added to draft-ietf-roll-trickle-mcast-05 to the effect of (this refinement has seen less WG discussion, in my opinion):

    "scop 4" can also be used with MPL to cover deployments
    that use administratively defined scopes that cover, for
    example, subnets based on different underlying network
    technologies.

>  Not clear to me that it's going to be an edit to this document.draft-ietf-roll-trickle-mcast-05

I'm pretty sure *something* has to be changed in draft-ietf-roll-trickle-mcast unless the definition of scop 3 is changed in draft-ietf-6man-multicast-scopes.

- Ralph

> 
>> Ticket #134
>> draft-ietf-roll-trickle-mcast-05 - Minor editorial comments
> 
> Something which I hope the authors will just act on.
> 
> -- 
> ]               Never tell me the odds!                 | ipv6 mesh networks [ 
> ]   Michael Richardson, Sandelman Software Works        | network architect  [ 
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
> 	
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll