Re: [MBONED] I-D ACTION:draft-ietf-mboned-mcast-arpa-01.txt

Peter Koch wrote:
> Dear mboned wg,
> 
>> 	Title		: Moving MCAST.NET into the ARPA infrastructure top level domain
>> 	Filename	: draft-ietf-mboned-mcast-arpa-01.txt
> 
> this version incorporates coments received during the Prague meeting.
> 
> Eligibility for a name in MCAST.ARPA is limited to group addresses from
> 224.0.0/24 and 224.0.1/24, because other addresses in 224/8 aren't as
> tightly controlled. The draft hopefully makes clear how a corresponding
> reverse mapping entry will look like.
> 
> I'd like to receive advice on which IPv6 group addresses should be treated
> the same way.

For IPv6 it would certainly be a subset of the permanent allocations,
which all got the T (transient) flag set to 0. From RFC 3307:

4.1  Permanent IPv6 Multicast Addresses

    Permanent multicast addresses, like those defined in [RFC 2375], are
    allocated by IANA.  These addresses will be assigned with group ID's,
    in the range of 0x00000001 to 0x3FFFFFFF, on an Expert Review basis.

    Multicast addresses assigned by IANA MUST have the T bit set to 0 and
    the P bit set to 0.

The question is whether all of these should be in the DNS, or what the
rule should be.

Most of the IANA assigned IPv6 multicast addresses are listed in RFC
2375. I believe all of those belong in the DNS,

Stig

> 
> For detailed changes please have a look at
> <http://tools.ietf.org/wg/mboned/draft-ietf-mboned-mcast-arpa/>
> 
> Thanks,
>   Peter
> 
> 
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www1.ietf.org/mailman/listinfo/mboned

_______________________________________________
MBONED mailing list
MBONED@ietf.org
https://www1.ietf.org/mailman/listinfo/mboned