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)

[神明達哉 <[e-mail]>]

At Wed, 23 Oct 2013 15:56:46 -0400,
Ralph Droms <[e-mail]> 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