IETF Logo Mail Archive

Re: [Roll] draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)

Kerry Lynn <kerlyn@ieee.org> Wed, 23 October 2013 21:38 UTC

Return-Path: <kerlyn2001@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 C870C11E825B; Wed, 23 Oct 2013 14:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.101
X-Spam-Level:
X-Spam-Status: No, score=-1.101 tagged_above=-999 required=5 tests=[AWL=-0.876, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, 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 s7qAPlLeCY4O; Wed, 23 Oct 2013 14:38:15 -0700 (PDT)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3F10C11E8181; Wed, 23 Oct 2013 14:38:10 -0700 (PDT)
Received: by mail-ob0-f180.google.com with SMTP id wo20so1484406obc.11 for <multiple recipients>; Wed, 23 Oct 2013 14:38:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=WFKYjAmQ4nr9G1lcaLcyAVnAUYOqkzPKrb+YD0sFrtE=; b=wGBBtan1X6n2EkjZ5j+5oOJkcDUeIbHKsj4egRY2Sok5dfhjyGPbkevrhCv+uthdyJ WoEslCwLQXBcX7BMWsaHfPaaMnnNK6vB2rsx172TMQXAA3xmYeF8ApJzwkbcYwZV92qY /s594eh+wsBOdJgTPq2QDWzavmSeBWGEjxc5TY6LB2mYNy4pt37X8koaP/vobekRw8f9 k3dPgOQgpC2qh1fLBikJufvlTwy7B6prc02CrEnFzKVIDY6bPeTFTZzsUgVWvah5GRHo DVSb2rz0DGsR/6Mmwl07Dlx2Tw/LbiAwaqz+etXUlEsT/44xapSsB31Ys9sZo2pvOX1m Mc5g==
MIME-Version: 1.0
X-Received: by 10.182.246.74 with SMTP id xu10mr3755288obc.23.1382564287673; Wed, 23 Oct 2013 14:38:07 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.60.73.6 with HTTP; Wed, 23 Oct 2013 14:38:07 -0700 (PDT)
In-Reply-To: <CAJE_bqcvQSiNTbbOvUEBvLC1uK5kAFfF04ZbQ=DFpwKb+ynATw@mail.gmail.com>
References: <3599.1381852752@sandelman.ca> <CE82BA46.24343%d.sturek@att.net> <CABOxzu2nLuny5uySEEdb6ji9ucE6xqGZ6DLe-mc6KUqVszNfFg@mail.gmail.com> <525DC6C9.2010808@gridmerge.com> <CABOxzu2apwBRpU1h4mKJwpO+U+Y9Q_q-h5AhZ+hGzAdjdPdmUQ@mail.gmail.com> <525E5064.4050109@gridmerge.com> <CABOxzu0L-EY0iDGpAJ+ER15CPL-3v8F77ewn-G=gZYODixevZg@mail.gmail.com> <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@gmail.com> <CAJE_bqdL3v4XK+dJPx1ZVFoRS+yjFDZEwVZ64fhYW6QUWVS6JA@mail.gmail.com> <52FECA00-C316-4693-A821-7EA6510AC0F8@gmail.com> <CAJE_bqcvQSiNTbbOvUEBvLC1uK5kAFfF04ZbQ=DFpwKb+ynATw@mail.gmail.com>
Date: Wed, 23 Oct 2013 17:38:07 -0400
X-Google-Sender-Auth: 49IQKZyZDA0hkIuuNaDVCXN-aH8
Message-ID: <CABOxzu20qONjQ71EWyob2Th+PJGpFz_Cw8jhvbmiEtojd+ihHg@mail.gmail.com>
From: Kerry Lynn <kerlyn@ieee.org>
To: 神明達哉 <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary="001a11c2e6083efebb04e96f5567"
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Subject: Re: [Roll] draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [roll] #132: draft-ietf-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: Wed, 23 Oct 2013 21:38:20 -0000

On Wed, Oct 23, 2013 at 5:21 PM, 神明達哉 <jinmei@wide.ad.jp> wrote:

> At Wed, 23 Oct 2013 15:56:46 -0400,
> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>
> > Perhaps we want to go a step farther and take the zone boundary text
> > out of RFC 4007 altogether?
>
> Basically works for me.
>
> > OLD:
> >
> >   o  The boundaries of zones of a scope other than interface-local,
> >      link-local, and global must be defined and configured by network
> >      administrators
> >
> > NEW:
> >
> >   o  The boundaries of zones of a scope are defined by the IPv6
> >      addressing architecture.
>
> With a reference (it's currently RFC 4291)?
>
> I'd also note that not all points described in the RFC 4007 text are
> described in RFC 4291 (at least not very clearly).  So, not just
> remove the text from RFC 4007, I'd like to unify it in the address
> architecture, e.g. update the following part of RFC 4291:
>
>          Admin-Local scope is the smallest scope that must be
>          administratively configured, i.e., not automatically derived
>          from physical connectivity or other, non-multicast-related
>          configuration.
>
> as follows:
>
>          Admin-Local scope is the smallest scope that must be
>          administratively configured, i.e., not automatically derived
>          from physical connectivity or other, non-multicast-related
>          configuration.  For all non-reserved scopes except the global
>          scope, the zone boundaries must also be administratively
>          configured.
>
> I think this statement is self-contradictory.  When automatic
configuration is
discussed, it is in relation to zone boundaries.  Here's an attempt to
explain
this without negations:

    Interface-Local, Link-Local, and Realm-Local scope boundaries are
automatically
    derived from physical connectivity or other, non-multicast related
configuration.
    Global scope has no boundary.  The boundaries of all other non-reserved
scopes
    are administratively configured.

BTW, just my opinion, but "Realm-Local" might be more meaningfully named
"Multilink-Local"

-K-

--
> JINMEI, Tatuya
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email