Re: [Roll] quasem load-balancing: Figure 3: The amended DIO message format

"Qasem, Mamoun" <M.Qasem@napier.ac.uk> Thu, 30 March 2017 17:48 UTC

Received-SPF: Pass (protection.outlook.com: domain of napier.ac.uk designates 146.176.4.2 as permitted sender) receiver=protection.outlook.com; client-ip=146.176.4.2; helo=owa.napier.ac.uk;
From: "Qasem, Mamoun" <M.Qasem@napier.ac.uk>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "roll@ietf.org" <roll@ietf.org>
CC: "draft-qasem-roll-rpl-load-balancing@ietf.org" <draft-qasem-roll-rpl-load-balancing@ietf.org>
Thread-Topic: quasem load-balancing: Figure 3: The amended DIO message format
Thread-Index: AQHSqXslS+rOo0HSQkWuIYnszD/AC6Gtpimw
Date: Thu, 30 Mar 2017 17:48:29 +0000
Message-ID: <CEB42D9A3A97D8429B05740EDE4119C5062466E1@MER-EXCH1.napier.ac.uk>
References: <5977.1490894952@obiwan.sandelman.ca>
In-Reply-To: <5977.1490894952@obiwan.sandelman.ca>
Accept-Language: en-US, en-GB
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 30 Mar 2017 17:48:40.1072 (UTC)
X-MS-Exchange-CrossTenant-Id: 99e0dc58-9c4b-4820-8617-04c386c254c6
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=99e0dc58-9c4b-4820-8617-04c386c254c6; Ip=[146.176.4.2]; Helo=[owa.napier.ac.uk]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR01MB0444
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/dxzbRWssWAwUjV4A4dT1YKTziQg>
Subject: Re: [Roll] quasem load-balancing: Figure 3: The amended DIO message format
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Mar 2017 17:48:52 -0000

Yes you are right. So i amended the current with a new option format as below, and the presentation today gana to include this.

       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |   Type        | Option Length |    Flags    |                 |                                                 |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- +|                   +
       |                                                                                                                                  |
       +                                                                                                                               +
       |                                                                                                                                  |
       +                        Parent Address                                                                               +
       |                                                                                                                                  |
       +                                                                                            +-+-+-+-+-+-+-+-+-+
       |                                                                                             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

You are most welcome to come along.
Mamoun


________________________________________
From: Michael Richardson [mcr+ietf@sandelman.ca]
Sent: Thursday, March 30, 2017 6:29 PM
To: roll@ietf.org
Cc: draft-qasem-roll-rpl-load-balancing@ietf.org
Subject: quasem load-balancing: Figure 3: The amended DIO message format

In draft-qasem-roll-rpl-load-balancing, you show:

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       | RPLInstanceID |Version Number |             Rank              |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |G|0| MOP | Prf |     DTSN      |     Flags     |   Reserved    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                                                               |
       +                                                               +
       |                                                               |
       +                            DODAGID                            +
       |                                                               |
       +                                                               +
       |                                                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                                                               |
       +                                                               +
       |                                                               |
       +                            Parent Address                     +
       |                                                               |

That is, you have changed the DIO Base Object in a non-backwards compatible
way.   There is no way to deploy this without upgrading all nodes.

Please instead, define a new DIO Option. This is trivially done and is
easily incrementally deployable.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
IETF ROLL WG outgoing co-chair.    http://datatracker.ietf.org/wg/roll/charter/

This message and its attachment(s) are intended for the addressee(s) only and should not be read, copied, disclosed, forwarded or relied upon by any person other than the intended addressee(s) without the permission of the sender. If you are not the intended addressee you must not take any action based on this message and its attachment(s) nor must you copy or show them to anyone. Please respond to the sender and ensure that this message and its attachment(s) are deleted.

It is your responsibility to ensure that this message and its attachment(s) are scanned for viruses or other defects. Edinburgh Napier University does not accept liability for any loss or damage which may result from this message or its attachment(s), or for errors or omissions arising after it was sent. Email is not a secure medium. Emails entering Edinburgh Napier University's system are subject to routine monitoring and filtering by Edinburgh Napier University.

Edinburgh Napier University is a registered Scottish charity. Registration number SC018373

[Roll] quasem load-balancing: Figure 3: The amend… Michael Richardson
Re: [Roll] quasem load-balancing: Figure 3: The a… Qasem, Mamoun