IETF Logo Mail Archive

Re: [Roll] DAO-Projection and new MOPs

Rahul Jadhav <rahul.ietf@gmail.com> Tue, 18 December 2018 16:44 UTC

Return-Path: <rahul.ietf@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C19121310F6 for <roll@ietfa.amsl.com>; Tue, 18 Dec 2018 08:44:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.098
X-Spam-Level:
X-Spam-Status: No, score=-0.098 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W1InpVJxUW4f for <roll@ietfa.amsl.com>; Tue, 18 Dec 2018 08:44:54 -0800 (PST)
Received: from mail-ua1-x92b.google.com (mail-ua1-x92b.google.com [IPv6:2607:f8b0:4864:20::92b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6127B130F15 for <roll@ietf.org>; Tue, 18 Dec 2018 08:44:54 -0800 (PST)
Received: by mail-ua1-x92b.google.com with SMTP id j3so5940669uap.3 for <roll@ietf.org>; Tue, 18 Dec 2018 08:44:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=JfnYRklgco0VyST+OEF7rXcRovjdfgtQA1FZeQ/WqTg=; b=f7lfdl6m6zs8KUOUw1r6ukgkOAJPKnui06Ava3+IRD74n89KOm4Zjpb6rYTGVJLgEc FhjoeiddmsxfC68KtPvDrNWiX4ZbXajTvks3LJZVAQlqUb9E2Qlv41ci+Cm5+6sKt2Mn EkO9aBuczyokaM6VHlK9RNIDGyVGSyPgGYCdwbY63QfmRqfnCtrrHT8KWGCeZUtbSIxp OY+0tZdsGcyXNocdN+yHN7R+GwySVyeb0Jh6mz0kn9gXWvzP00xe+XEmnxZViasG4lEh w4NVrtHrTUe9Vua+lKJ+NSoTrYTz94Udw3zGEDhqV9pfGlx9bBttXD+2TnibYRAQHjdq Ytqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=JfnYRklgco0VyST+OEF7rXcRovjdfgtQA1FZeQ/WqTg=; b=SFVqUPCEvULN64aaUOiwz02TAbXZs147q5A+GwO2Bl4qq3KBzYn0XUEVvI3PQV8EuE t/xHVA9wEVFc9MrspA/C2XQuvPwe6A5E1VGivoDODZlDVYVpif+2DgVLt1alw8tMMPaK K5iLoC0Am7FYwtDOm5AKZctZPl2QXGV+1iiS9ezNHhPZ+l41cWPbID9zYLaRGxqs1TxM SqBeufahChq7ccz+ji0fm6f7H6qPNpRpgWqFHQF/x1qaDMRoyFuZwmlParC9ukKpPbXe ZpoNXt1pdNqKEldyzh1tsQ9z5el5wPWZovy9pIUP2T5OGqv2wxSgRzo+lRgJVykVH0g7 pxNw==
X-Gm-Message-State: AA+aEWYCKzoF+87BdJ/Yqw/9c+2tugZxpiXFjKc2yv0KOzlh8A5TVySf 9ABZ0DylKHCS4WpB4CCdOy1fYLjLgTZhN92lCIYfVOZd
X-Google-Smtp-Source: AFSGD/U5gV3lm832lcC/WUAQOeM2LpzIg4khY8ktvEFtOpL/2KF5tYDffUBV9JMkJxmBaC1JGJSQgI1MFFe0ijKXhLk=
X-Received: by 2002:ab0:210e:: with SMTP id d14mr8560979ual.20.1545151492842; Tue, 18 Dec 2018 08:44:52 -0800 (PST)
MIME-Version: 1.0
References: <CAO0Djp0wiHUg15SfLzqXRF6Ko9JBbeL7C9CLZ6HRXcNxf+=Gew@mail.gmail.com> <0cb3313f79eb475090937a932b793efc@XCH-RCD-001.cisco.com> <16712.1545069107@localhost> <6811D20F-DC62-4E16-86EE-684BD288E2CF@cisco.com> <32162.1545150881@localhost>
In-Reply-To: <32162.1545150881@localhost>
From: Rahul Jadhav <rahul.ietf@gmail.com>
Date: Tue, 18 Dec 2018 22:14:41 +0530
Message-ID: <CAO0Djp3Lyd7+m0JheD-YfE6260Yvyk9eAV3x++Q12Z=LwXN7Qw@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000daedfd057d4e9d89"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/UdqEaJihgvySDCvsG1qsg9xr_oY>
Subject: Re: [Roll] DAO-Projection and new MOPs
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 18 Dec 2018 16:44:57 -0000

Currently we have,
4 MOPs defined in 6550,
1 MOP defined in p2p-rpl/6997,
1 in aodv-rpl,
2 are needed for dao projection.

Thus all 8 mops will be used and none left. Thus mop extension may have to
be handled before dao projection since extension will take one mop itself.

I am curious to know also if mop=0 is put to use by any one.

Regards,
Rahul

On Tue, 18 Dec 2018 at 10:05 PM, Michael Richardson <mcr@sandelman.ca>
wrote:

>
> Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
>     > Trouble is that there is no room left in MOP space (3 bits). We’ll
> soon
>     > need to define a value to mean extended.
>
> 3bits = 8 choices.  We have four choices now.
> Did MOP=0 ever have useful meaning?  (Tell me the use case...)
>
> I'd redefine that to mean extended, or 7 if we have to...
> But for the moment, I don't see why we can't allocate MOP=4 for this.
> I don't think new MOP's come along that often.
>
>     >> Le 17 déc. 2018 à 18:52, Michael Richardson <mcr+ietf@sandelman.ca>
> a
>     >> écrit :
>     >>
>     >>
>     >> I strongly believe that we should have a specific new MOP:
>     >> "Non-storing with DAO-project"
>     >>
>     >> --
>     >> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software
> Works
>     >> -= IPv6 IoT consulting =-
>     >>
>     >>
>     >>
>     >> _______________________________________________ Roll mailing list
>     >> Roll@ietf.org https://www.ietf.org/mailman/listinfo/roll
>     > _______________________________________________ Roll mailing list
>     > Roll@ietf.org https://www.ietf.org/mailman/listinfo/roll
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>

v2.23.0 | Report a Bug | By Email