Re: [Roll] trickle-mcast-04 - Clarify scope value of 3 - subnet-local

Ulrich Herberg <ulrich@herberg.name> Fri, 12 July 2013 04:31 UTC

Return-Path: <ulrich@herberg.name>
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 055DA21F9A04 for <roll@ietfa.amsl.com>; Thu, 11 Jul 2013 21:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.536
X-Spam-Level:
X-Spam-Status: No, score=-1.536 tagged_above=-999 required=5 tests=[AWL=-0.443, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 tZOeiDwfw93n for <roll@ietfa.amsl.com>; Thu, 11 Jul 2013 21:31:11 -0700 (PDT)
Received: from mail-vc0-x233.google.com (mail-vc0-x233.google.com [IPv6:2607:f8b0:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 0DF1821F99EB for <roll@ietf.org>; Thu, 11 Jul 2013 21:31:10 -0700 (PDT)
Received: by mail-vc0-f179.google.com with SMTP id hz11so7362595vcb.38 for <roll@ietf.org>; Thu, 11 Jul 2013 21:31:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=emtpkcz2vIvZRF4BLohHiA+ZyL+ZMU5llqfhdU9FrsI=; b=118p2hbh4+FQiV5stA3ND/stm3ucRc0egl6XJ+JbjvrrPxzml4vhCKo5bsDhuVPUsx dJkBpfZ1NrHDg+1mcoFwRnhiF93fjkZUNtSdsp9XvDTe8IKYH3nKsZ2nt8uox41ztDbY TDPdY1NDMoUwN633Af/Ftb23Q3ZPEaoTpaXII=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=emtpkcz2vIvZRF4BLohHiA+ZyL+ZMU5llqfhdU9FrsI=; b=k3aWNpgM4NO9LsJO1FFJYkIpY3Id17BicW+IUKHcMUgs65jWGH9k6nm4VhCAwEprIO U9mhRJo/ZKRJSVgQwOrZZFid3SJue08k4O1pWelIUVT1IIWI3Pa2XjLMoWPJ5ytxzUUt O/9Dw/7AiszQG3v/GkgEBAKErBVVq7YL/3YA4er9EsggtUe31VvgbXGwRnhEgop8ssKJ rKlSZhqBSqnKqynDIwAq9QXkm7ugP1kcp4oAetxfwWqzzoVYFSn+6BhRhlSR7POp6Uax 82G4svZGDcoMZ1Y9KyqvSZmDpZ3dBdf5fb5EeY8+thFDFSxJCQevdSiUjXoBtjt+jq+9 Ik3Q==
MIME-Version: 1.0
X-Received: by 10.220.143.140 with SMTP id v12mr23520912vcu.95.1373603467774; Thu, 11 Jul 2013 21:31:07 -0700 (PDT)
Received: by 10.221.55.70 with HTTP; Thu, 11 Jul 2013 21:31:07 -0700 (PDT)
In-Reply-To: <CE04C272.220FE%d.sturek@att.net>
References: <CAK=bVC_FSDU4a15j=akvhvWtKyq4Kms_yAMu91RCMtQDcca4LA@mail.gmail.com> <CE04C272.220FE%d.sturek@att.net>
Date: Thu, 11 Jul 2013 21:31:07 -0700
Message-ID: <CAK=bVC-Aau9F8XpYL67VTq8FJ3oiAS=BxwZUuMW8H0E=CNYYYw@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b342f44c25acf04e148fa5e"
X-Gm-Message-State: ALoCoQmnhtj3WsoCEs+GxGmAah3SOUblENPPKex6oyMfBALl/xD3CY7H3sehybQzBMxaMSXxqAMR
Cc: "Ralph Droms (rdroms)" <rdroms@cisco.com>
Subject: Re: [Roll] trickle-mcast-04 - Clarify scope value of 3 - subnet-local
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <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: Fri, 12 Jul 2013 04:31:12 -0000

Hi Don,

The IETF has already documented a solution in
http://tools.ietf.org/html/rfc5889
(using /128 prefixes)

I wrote a whole chapter on that issue in my Ph.D. Thesis a few years ago:
http://herberg.name/downloads/pubs/thesis.pdf

Regards
Ulrich



On Thursday, July 11, 2013, Don Sturek wrote:

> Hi Ulrich,
>
> I think the multi-link subnet is an unfortunate side effect of route over
> mesh protocols.
>
> I would be interested in hearing of any solution around this since we (the
> folks implementing ZigBee IP) seemed to have to go through a lot of
> trouble over multi-link subnets.....
>
> Don
>
>
> On 7/11/13 5:40 PM, "Ulrich Herberg" <ulrich@herberg.name <javascript:;>>
> wrote:
>
> >That's what I feared... I think it's an unfortunate decision.
> >
> >Btw, should that mean that RFC4903 should be obsoleted?
> >
> >Ulrich
> >
> >
> >On Thu, Jul 11, 2013 at 5:05 PM, Ralph Droms (rdroms) <rdroms@cisco.com<javascript:;>
> >
> >wrote:
> >>
> >>
> >> On Jul 11, 2013, at 6:29 PM, "Ulrich Herberg" <ulrich@herberg.name<javascript:;>
> >
> >>wrote:
> >>
> >>> On Thu, Jul 11, 2013 at 2:14 PM, Michael Richardson
> >>> <mcr+ietf@sandelman.ca <javascript:;>> wrote:
> >>>>
> >>>>> The most recent rev of draft-droms-6man-multicast-scopes defines
> >>>>>scope
> >>>>> 0x03 as:
> >>>>
> >>>>> 3  Network-Specific scope, greater than Link-Local scope, defined
> >>>>> automatically from the network topology
> >>>>
> >>>>> To be confirmed: will this definition suffice for MPL?
> >>>>
> >>>> I think it is sufficient, because we understand what it means.
> >>>> I am concerned about the word "Network"... which could mean anything
> >>>>to anyone.
> >>>>
> >>>> I'd think that the right word would be "subnet", because the intent
> >>>>is that
> >>>> it is for the entire /64 or whatever it is that one is using.  I
> >>>>think that
> >>>> is the term that is used in RFC4291.
> >>>
> >>>
> >>> I think that having a network-wide, multi-link subnet is a bad idea:
> >>> http://tools.ietf.org/html/rfc4903
> >>
> >> That decision has already been made and is carried through many
> >>protocols..
> >>
> >> - Ralph
> >>
> >>>
> >>> Regards
> >>> Ulrich
> >_______________________________________________
> >Roll mailing list
> >Roll@ietf.org <javascript:;>
> >https://www.ietf.org/mailman/listinfo/roll
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/roll
>