Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
神明達哉 <jinmei@wide.ad.jp> Wed, 23 October 2013 21:21 UTC
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6301A11E8241; Wed, 23 Oct 2013 14:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.222
X-Spam-Level: *
X-Spam-Status: No, score=1.222 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FM_FORGED_GMAIL=0.622, 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 zQL4SoUvRKmo; Wed, 23 Oct 2013 14:21:18 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 9312711E821A; Wed, 23 Oct 2013 14:21:17 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id c11so1459355wgh.14 for <multiple recipients>; Wed, 23 Oct 2013 14:21:16 -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=QkZvQBlQAyOoTKz/4ac6WYSVeH/tIOr56sH8bz9Wpf8=; b=f4TsX/CVAuMqRVMSGDSp2YJ68hbkzCtUqbCNAmw7aUnPIaZtHMJvqUkmpwdL5RLAcI aj0iaOFQyVtOPBdk6NUvWrUJuD2MJNKTbyP4i4QeM6Toc++VV2eIHmO2Dfy8jmzn+6Vq mJkelwVnwtUtFLBPE1WiQDQnPDy21td5vQbH3MuJ2iW5FXCC0njL/sYFD3LEBQGpxu9m KO9HII5U376vNPdc6uSCQJv/HGzBZRW6ch8dayOStskc4kr3WhkgwOssQBN3hCgKKPNy Jup63nPwVbs0q2/88gm+f39ATb6ZW+aGggPLqabL2Wl6x2enRmRoheoGaXGBeP0tT2GL L00A==
MIME-Version: 1.0
X-Received: by 10.194.175.66 with SMTP id by2mr3319478wjc.59.1382563276700; Wed, 23 Oct 2013 14:21:16 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Wed, 23 Oct 2013 14:21:16 -0700 (PDT)
In-Reply-To: <52FECA00-C316-4693-A821-7EA6510AC0F8@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>
Date: Wed, 23 Oct 2013 14:21:16 -0700
X-Google-Sender-Auth: 9r766Kso1DOa8mTJr0OgNTJrxjI
Message-ID: <CAJE_bqcvQSiNTbbOvUEBvLC1uK5kAFfF04ZbQ=DFpwKb+ynATw@mail.gmail.com>
Subject: Re: draft-ietf-6man-multicast-scopes updates RFC 4007 (Was Re: [Roll] [roll] #132: draft-ietf-roll-trickle-mcast-04 - Clarify scope value of 3 - subnet-local)
From: 神明達哉 <jinmei@wide.ad.jp>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Oct 2013 21:21:18 -0000
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. -- JINMEI, Tatuya
- Re: draft-ietf-6man-multicast-scopes updates RFC … 神明達哉
- draft-ietf-6man-multicast-scopes updates RFC 4007… Ralph Droms
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Kerry Lynn
- Re: draft-ietf-6man-multicast-scopes updates RFC … Ralph Droms
- Re: draft-ietf-6man-multicast-scopes updates RFC … 神明達哉
- Re: draft-ietf-6man-multicast-scopes updates RFC … Kerry Lynn
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Robert Cragie
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… 神明達哉
- Re: draft-ietf-6man-multicast-scopes updates RFC … Ralph Droms (rdroms)
- RE: draft-ietf-6man-multicast-scopes updates RFC … Dave Thaler
- Re: draft-ietf-6man-multicast-scopes updates RFC … Ralph Droms (rdroms)
- RE: draft-ietf-6man-multicast-scopes updates RFC … Dave Thaler
- Re: [Roll] draft-ietf-6man-multicast-scopes updat… Kerry Lynn
- Re: draft-ietf-6man-multicast-scopes updates RFC … 神明達哉
- Re: draft-ietf-6man-multicast-scopes updates RFC … Stig Venaas