RE: Review of draft-ietf-softwire-multicast-prefix-option-11

<> Mon, 09 January 2017 07:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 30732129B98; Sun, 8 Jan 2017 23:43:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.118
X-Spam-Status: No, score=-5.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ayKqTXfcpauo; Sun, 8 Jan 2017 23:43:03 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 53F40129B94; Sun, 8 Jan 2017 23:43:00 -0800 (PST)
Received: from (unknown [xx.xx.xx.8]) by (ESMTP service) with ESMTP id 95B6160A65; Mon, 9 Jan 2017 08:42:58 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.10]) by (ESMTP service) with ESMTP id 6901980066; Mon, 9 Jan 2017 08:42:58 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM5C.corporate.adroot.infra.ftgroup ([fe80::4bd:9b2b:3651:6fba%19]) with mapi id 14.03.0319.002; Mon, 9 Jan 2017 08:42:58 +0100
To: Roni Even <>, "" <>
Subject: RE: Review of draft-ietf-softwire-multicast-prefix-option-11
Thread-Topic: Review of draft-ietf-softwire-multicast-prefix-option-11
Thread-Index: AQHSakTvcdQqqowUCUaeKEwMp0GtyKEvtzTA
Date: Mon, 09 Jan 2017 07:42:56 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009DE1B41@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>, "" <>, "" <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 09 Jan 2017 07:43:05 -0000

Dear Roni,

Thank you for the review. 

Please see inline.


> -----Message d'origine-----
> De : Roni Even []
> Envoyé : lundi 9 janvier 2017 07:52
> À :
> Cc :;; draft-ietf-softwire-multicast-
> Objet : Review of draft-ietf-softwire-multicast-prefix-option-11
> Reviewer: Roni Even
> Review result: Almost Ready
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <>.
> Please resolve these comments along with any other Last Call comments
> you may receive.
> Document:  draft-ietf-softwire-multicast-prefix-option-11
> Reviewer: Roni Even
> Review Date:2017-1-9
> IETF LC End Date: 2017–1-12
> IESG Telechat date:
> Summary: This draft is almost  ready for publication as a standard
> track RFC.
> Major issues:
> Minor issues:
> 1.	In section 4 first paragraph say “DHCP servers supporting
> OPTION_V6_PREFIX64 should be configured with U_PREFIX64 and at least
> one multicast PREFIX64 (i.e., ASM_PREFIX64 and/or SSM_PREFIX64).” From
> the rest of the section I understand that for SSM deployments both
> U_PREFIX64 and SSM_PREFIX64 MUST be configured.

[Med] Yes. If you prefer, I can change the text to make this more clear:

  DHCP servers supporting OPTION_V6_PREFIX64 should be configured with
   U_PREFIX64 and at least one multicast PREFIX64 (i.e., ASM_PREFIX64
   and/or SSM_PREFIX64).

   DHCP servers supporting OPTION_V6_PREFIX64 must be configured with
   ASM_PREFIX64 or SSM_PREFIX64, and may be configured with both.
   U_PREFIX64 must also be configured when SSM_PREFIX64 is provided.
   U_PREFIX64 may be configured when only ASM_PREFIX64 is provided.

> What is the reason for “should” in the first paragraph? Are there
> cases where ASM_PREFIX64 or ASM_PREFIX64 and SSM_PREFIX64 are
> specified and there is no need to specify U_PREFIX64, maybe these
> cases should be described.

[Med] The presence of the unicast address is mandatory for the SSM case because it is required to form an IPv6 address from an IPv4 address to subscribe to a multicast content from a particular source. For the ASM case, the configuration of the U_PREFIX64 is not mandatory in the following cases: (1) a local mapping algorithm is enabled by the function that grafts the IPv4 multicast host side with an IPv6 multicast tree or (2) in deployments that make use of the WKP (64:ff9b::/96, RFC6052).

I can add this NEW text:

   Note that U_PREFIX64 is not mandatory for the ASM case if, for
   example, a local address mapping algorithm is supported or the Well-
   Know Prefix (64:ff9b::/96) is used.

> Nits/editorial comments:
> 1.	RFC2119 keywords in the document are sometime capitalized and
> sometime not. I think it will be good to have consistency and if they
> do not intend to have RFC2119 semantics some other words should be
> used

[Med] I guess you are referring to Section 4. We are not using normative language on purpose because of previous comments we received from some DHC experts (T. Lemon). The use of normative text for the server behavior would mean that we are updating RFC 3315, which we do not want to do. This is why we are defining this section as configuration guidelines.