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> Thu, 17 October 2013 16:16 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 0817711E825D; Thu, 17 Oct 2013 09:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 UnBzs2Kz6Bcu; Thu, 17 Oct 2013 09:16:43 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 489ED11E8271; Thu, 17 Oct 2013 09:16:39 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id c11so2594439wgh.9 for <multiple recipients>; Thu, 17 Oct 2013 09:16:37 -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=3m6QM95Y58yuqeOqhvhP2HX72L7Ku2fd+vuM74irvOg=; b=NOsj4d0ELoDKRGIuUSYQ7lmuy9uWf61D+kX//zUmIdRX2llO0jnI/5mXaHiR3K7jMI qlqkRA1B+pZq1mGx5UUfvKCjwJhV8gkq5oHporzBvLMKc98NNOIA8s9GA1vMYwPSP/06 JkD7+yVmrJsK0t8+Cmrm+fg4XquyjVZiHOZvUvn9JxqYpGU+dJXMvuMKmzwcmhTO2XZT lbQaFavIZKKgipXT4juwKVKFJptkJPO1pIhz5UOJfrGjbGhl55uRobzhqoWqppjXXI/E JF3xTWuJurE8CndCCEq1UDi5508G85Zst16lkGyERDIDSsiOTixTgENidljhyZsylVno l/sw==
MIME-Version: 1.0
X-Received: by 10.180.182.15 with SMTP id ea15mr29921654wic.16.1382026597536; Thu, 17 Oct 2013 09:16:37 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.216.227.132 with HTTP; Thu, 17 Oct 2013 09:16:37 -0700 (PDT)
In-Reply-To: <3CC8783F-F4DA-47B9-A051-DBBA6EF00C19@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>
Date: Thu, 17 Oct 2013 12:16:37 -0400
X-Google-Sender-Auth: _d8c8iiXon2bZ9RiaS8uIK7F4Xw
Message-ID: <CABOxzu1VMw3EkCCkXRU4h=obSKbO8JSXfS+_NJ-S-vV3bkuP+g@mail.gmail.com>
From: Kerry Lynn <kerlyn@ieee.org>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b62535a6a98d504e8f2243a"
Cc: "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: Thu, 17 Oct 2013 16:16:44 -0000

On Thu, Oct 17, 2013 at 12:10 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:

> Kerry correctly points out that RFC 4007 and RFC 4291 are in conflict
> regarding the way in which multicast scope 3 is defined:
>
> RFC 4007, section 5:
>
>    o  The boundaries of zones of a scope other than interface-local,
>       link-local, and global must be defined and configured by network
>       administrators.
>
> RFC 4291, section 2.7:
>
>          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.
>
> Noting this conflict, I propose adding a bit of text to
> draft-ietf-6man-multicast-scopes to update RFC 4007 for consistency with
> RFC 4291:
>
> Add section 3 (and renumber current section 3-5):
>
> 3.  Updates to RFC 4007, section 5
>
>    Section 5 of RFC 4007 and section 2.7 of RFC 4291 disagree about the
>    way in which multicast scope 3 is configured.  To resolve that
> disagreement,
>    change the last bullet in the list in section 5 of RFC 4007 as follows:
>
> 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  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.
>
> Looking for consensus in the 6man WG before I make this change...
>
> +1

-K-


> - Ralph
>
> On Oct 16, 2013, at 10:04 AM 10/16/13, Kerry Lynn <kerlyn@ieee.org> wrote:
>
> > [...]
>
> > I think Ralph's approach is the correct one.  His
> draft-droms-6man-multicast-scopes belongs in
> > 6man as it re-defines a reserved code point in the IPv6 addressing
> architecture.  It nominally
> > updates RFC 4291 but should probably also update RFC 4007 as these RFCs
> are in conflict
> > regarding the automatic definition of scope 0x03.
> [...]
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>

v2.23.0 | Report a Bug | By Email