Subject: Re: [Softwires] MUST or must for /96 in draft-ietf-softwire-multicast-prefix-option-03?

From: <[email-masked]>
Date: Fri, 12 Apr 2013 09:48:19 +0200

Hi Tom,

Please see inline.

Cheers,
Med

>-----Message d'origine-----
>De : [email-masked] [mailto:[email-masked]] De la
>part de Tom Taylor
>Envoyé : vendredi 29 mars 2013 17:12
>À : Softwires
>Objet : Re: [Softwires] MUST or must for /96 in draft-ietf-softwire-
>multicast-prefix-option-03?
>
>Apologies, that second question is covered thoroughly by client
>behaviour, section 5.

[Med] That's fine. Thanks for double checking it.

>
>On 29/03/2013 12:05 PM, Tom Taylor wrote:
>> I actually have two questions about the prefix-length fields in the
>option.
>>
>> First, in section 4, there is the statement:
>>
>>     When ASM_PREFIX64 and SSM_PREFIX64 are configured, the length of
>>     these prefixes must be /96.
>>
>> Is that meant to be a MUST?

[Med] The normative language is not used in that section as it provides only guidelines. You may noticed, we didn't entitled that section "Server Behavior". This is a comment I have received from T. Lemon for another document.

>>
>> The second question is whether the absence of a particular prefix from a
>> particular option is indicated by a prefix length of zero. If so, should
>> that be mentioned somewhere in section 3, or is it covered by standard
>> DHCP practice?
>>
>> Tom Taylor
>_______________________________________________
>Softwires mailing list
>[email-masked]
>https://www.ietf.org/mailman/listinfo/softwires