Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt

[Stig Venaas <[e-mail]>]

On 14.08.2012 14:43, Lee, Yiu wrote:
> Hi Stig,
>
> Since we want T=1, this will not meet the "well-known" requirement defined
> in RFC4291. If we don't want to define a flag, what is the proper way to
> describe ffxx:8000::/20 and ffxx:0:8000::/96?

You could list them for all values of xx perhaps. I would maybe use
"x" and "y" and then discuss the allowed values.

There are scope relative allocations today, the main thing is that we
don't want to require the flags to be "0". Or maybe we want to require
the T-bit to be set. As I wrote earlier, I would think of these
addresses as transient, and T=1 is required for Embedded-RP etc.

The issue though is that if T=1, then it is not really an IANA
allocation as I see it, because IANA allocations have T=0. But if there
is IETF consensus, then one can still reserve these prefixes.

Stig

>
> Thanks,
> Yiu
>
>
> On 8/13/12 7:18 PM, "Stig Venaas" <[e-mail]> wrote:
>
>> On 13.08.2012 14:46, Brian Haberman wrote:
>>> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>>>> Hi authors,
>>>>
>>>> Thanks for the revised draft, I find that the revision is in the right
>>>> direction.
>>>>
>>>> I am confused on the prefix lengths:
>>>> on Figure 2,
>>>> ffxx:8000:0:abc::/96
>>>> while in Section 3.1
>>>> ffxx:8000::/20
>>>>
>>>
>>> The x's correspond to the flags and scope fields within the multicast
>>> address.  Take a look at:
>>>
>>>
>>> http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-a
>>> ddresses.xml#ipv6-multicast-addresses-4
>>
>> We have one minor issue here though. They cannot simply be IANA
>> allocations, since they would not have the transient bit set. In
>> this case, the idea is that it should work for flag nibble values
>> like 1, 3 and 7. Actually I believe the transient bit should always
>> be set for these groups.
>>
>> Stig
>>
>>>
>>>
>>>> How come these are reserved prefixes?
>>>> What are the values that are reserved?
>>>>
>>>> If you look at RFC 6052, the unicast translation specification,
>>>> 64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
>>>> the prefix definition.
>>>>
>>>> Regards,
>>>>
>>>> Behcet
>>>>
>>>> On Fri, Aug 10, 2012 at 1:49 AM,  <[e-mail]> wrote:
>>>>>
>>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>>> directories.
>>>>>    This draft is a work item of the MBONE Deployment Working Group of
>>>>> the IETF.
>>>>>
>>>>>           Title           : IPv6 Multicast Address With Embedded IPv4
>>>>> Multicast Address
>>>>>           Author(s)       : Mohamed Boucadair
>>>>>                             Jacni Qin
>>>>>                             Yiu L. Lee
>>>>>                             Stig Venaas
>>>>>                             Xing Li
>>>>>                             Mingwei Xu
>>>>>           Filename        :
>>>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>>>           Pages           : 13
>>>>>           Date            : 2012-08-09
>>>>>
>>>>> Abstract:
>>>>>      This document reserves two IPv6 multicast prefixes to be used in
>>>>> the
>>>>>      context of IPv4-IPv6 interconnection.  The document specifies an
>>>>>      algorithmic translation of an IPv6 multicast address to a
>>>>>      corresponding IPv4 multicast address, and vice versa.  This
>>>>>      algorithmic translation can be used in both IPv4-IPv6 translation
>>>>> or
>>>>>      encapsulation schemes.
>>>>>
>>>>>
>>>>>
>>>>> The IETF datatracker status page for this draft is:
>>>>>
>>>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address
>>>>> -format
>>>>>
>>>>>
>>>>> There's also a htmlized version available at:
>>>>>
>>>>> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-forma
>>>>> t-03
>>>>>
>>>>>
>>>>> A diff from the previous version is available at:
>>>>>
>>>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-address
>>>>> -format-03
>>>>>
>>>>>
>>>>>
>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>
>>>>> _______________________________________________
>>>>> MBONED mailing list
>>>>> [e-mail]
>>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>> _______________________________________________
>>>> MBONED mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>
>>>
>>>
>>> _______________________________________________
>>> MBONED mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/mboned
>>
>> _______________________________________________
>> MBONED mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/mboned