Re: [Softwires] Problem in draft-ietf-softwire-multicast-prefix-option

<> Wed, 08 June 2016 14:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6873212D79D for <>; Wed, 8 Jun 2016 07:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nsmAvsnQFohO for <>; Wed, 8 Jun 2016 07:50:55 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AB31B12D5CA for <>; Wed, 8 Jun 2016 07:50:53 -0700 (PDT)
Received: from (unknown [xx.xx.xx.3]) by (ESMTP service) with ESMTP id E6A9918CA55; Wed, 8 Jun 2016 16:50:51 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id B013C4C063; Wed, 8 Jun 2016 16:50:51 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([fe80::c1d7:e278:e357:11ad%19]) with mapi id 14.03.0294.000; Wed, 8 Jun 2016 16:50:51 +0200
From: <>
To: ian Farrer <>, "" <>, Jacni Qin <>, "" <>
Thread-Topic: Problem in draft-ietf-softwire-multicast-prefix-option
Thread-Index: AQHRwY+pjD8GiTRpEkWX2QNRUGBtGZ/fo66g
Date: Wed, 8 Jun 2016 14:50:51 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008DAECE0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <trinity-fbc98ae4-0413-4cea-8842-a5959c4e303a-1465395089242@3capp-mailcom-bs12>
In-Reply-To: <trinity-fbc98ae4-0413-4cea-8842-a5959c4e303a-1465395089242@3capp-mailcom-bs12>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933008DAECE0OPEXCLILMA3corp_"
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2016.6.8.132415
Archived-At: <>
Cc: "" <>
Subject: Re: [Softwires] Problem in draft-ietf-softwire-multicast-prefix-option
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 08 Jun 2016 14:50:56 -0000

Hi Ian,

Please see inline.


De : ian Farrer []
Envoyé : mercredi 8 juin 2016 16:11
À :; BOUCADAIR Mohamed IMT/OLN; Jacni Qin;
Cc :
Objet : Problem in draft-ietf-softwire-multicast-prefix-option


On reviewing this draft I would like to raise a problem with section 5 of the draft. The text is:

"If all the enclosed IPv4-embedded IPv6 multicast prefixes have the same scope, the first instance of the option MUST be used."

The problem is that this contravenes section 17 of RFC7227:

Option order, either the order among many DHCPv6 options or the order

   of multiple instances of the same option, SHOULD NOT be significant.

   New documents MUST NOT assume any specific option processing order.

[Med] That sentence does not assume any (preference) order. It does only provide one way to select one instance among that list. As a reminder, the server is supposed to return one instance (per scope).

I raised this with the DHC WG chairs, and they have a couple of suggestions:

1. Define an encapsulating option - as the data inside an option can be order dependent.
2. Add a “preference” (octet?) and then a client can sort them based on this preference.