Re: [Roll] [ROLL] Projected DAO and Extended MOP

rabi narayan sahoo <rabinarayans0828@gmail.com> Sat, 02 November 2019 05:02 UTC

Return-Path: <rabinarayans0828@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 EADAF120074 for <roll@ietfa.amsl.com>; Fri, 1 Nov 2019 22:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Gomq2T0JsCes for <roll@ietfa.amsl.com>; Fri, 1 Nov 2019 22:02:55 -0700 (PDT)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 DE75412002F for <roll@ietf.org>; Fri, 1 Nov 2019 22:02:54 -0700 (PDT)
Received: by mail-il1-x130.google.com with SMTP id m5so1257873ilq.0 for <roll@ietf.org>; Fri, 01 Nov 2019 22:02:54 -0700 (PDT)
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=xsSB7UoiX8AJdv7Ha8+JfV/bEm3XzTR8/gQYnmW2b8s=; b=vOFGYFb1FOmJzE0aDG0wbL6C1esE1T92Tn5KSWSiwnlwgI+US2NP+DInk4pR465mKU 9P/P5Qt+Hg5O909Do2gTswirjcibmv3v79QVobh9eliJtd4bXfs6FN43Zud0Z+m08t2n hLVuWGpLVI6tYut3JOGb7OfTGwn0RwBWxxUPlHfTWL5pMHzAqGYrvbnpPvRgXnRvzrBW RAhac5AjShGfD09UsXJQ6QOrLT/4wses1f7Z9JGp8V3KyLguQUqnVJG8H3rXyhxXA2Uv GNCWY4vd24MsUtn6wkEi39s7MkUMkiSzAqgDU35Y3dyzZSma8qKAJI9nr6VTuzWv+eIB 9opA==
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=xsSB7UoiX8AJdv7Ha8+JfV/bEm3XzTR8/gQYnmW2b8s=; b=SmEiVGht+EbxrQZBLNTKr1bmB1Lcw4btthsNWL7q6qnn8W4de6wevm1vbnh+PRcDdZ 6pcqfZgSB7xq9ek3/HuRgcZ18w5gSq7TRpMurfJK0bayoDMJtek+KEIgepND3U43q1D8 wqOuvvh3gyB+8lFH2S5Dy+V9lUEZAX2Qemm5TOmvbMLX2htsJJjn7XlSCDjMCvjglzPX 7IEYsTf8D/UsdAmYtbU0LuVNZJVkxnc9M/AiLT6Fofh865Pr8fNthdhbRs3CvVo3GnxH otFvm8lRbNTtAAOPCU3C+geHJGCxVitVw+uQ5RlhOP2L9e1Cf9XtEKnfCHqttK3YQkCa IxSg==
X-Gm-Message-State: APjAAAUcpW1JvS6aP3xka+0pihQ9VslTC/ucvvVB1SmvDF93VdcjVIb3 7gM0W5ZhK4BcBi/wOzd2S5CJEtFXeqJdCpJGJzYWCD2o
X-Google-Smtp-Source: APXvYqzjWDodbHDNB4oSkkm2RG3M5gq9i3hFcbcd4W8TIsyt8iYS5l+w0fAMZ2Sz2zai7A56kEO5CkZ5EYRcTLly4CY=
X-Received: by 2002:a92:831d:: with SMTP id f29mr17365208ild.263.1572670973993; Fri, 01 Nov 2019 22:02:53 -0700 (PDT)
MIME-Version: 1.0
References: <CAPT0++1=SzA2hs3rgG2Wr8FrJAw7t=4ukBH=DOxT-G+th_GQUQ@mail.gmail.com> <1FD20A4E-D78D-44C3-B6AB-09BC47B1D5A2@cisco.com>
In-Reply-To: <1FD20A4E-D78D-44C3-B6AB-09BC47B1D5A2@cisco.com>
From: rabi narayan sahoo <rabinarayans0828@gmail.com>
Date: Sat, 2 Nov 2019 10:32:41 +0530
Message-ID: <CAPT0++0JqDAJbKxW96OyjkJ=BB6SxyB6=AAu31rnbkRuVQOMGQ@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c0ea17059655fe90"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/n9jpG1zU6moCeRgFNM2VI3Yv-6A>
Subject: Re: [Roll] [ROLL] Projected DAO and Extended MOP
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: Sat, 02 Nov 2019 05:02:57 -0000

Hi
I won't be coming to Singapore. I will attend the sessions remotely.
I hope sibling advertisement will have network metric information too. We
should also consider adding a option to DIO for disseminating PCE
information if PCE is not part of BR.
Looking forward for the new version of the draft.
Thanks
Rabi

On Fri, 1 Nov, 2019, 1:31 PM Pascal Thubert (pthubert), <pthubert@cisco.com>
wrote:

> This is all very convincing Rabi.
>
> Let’s discuss in Singapore. Will you be present ?
>
> I plan to publish an update today or Monday.
> The update will have proposals for a number of items that were in the
> table, advertising siblings, requesting a route, compressing the VIO based
> on RFC 8138 and building Tracks.
>
> This is a lot of stuff and I expect we’ll need more time than I initially
> expected at the WG meetings.
>
> Regards,
>
> Pascal
>
> Le 1 nov. 2019 à 01:24, rabi narayan sahoo <rabinarayans0828@gmail.com> a
> écrit :
>
> 
> Hello All
>
> If my understanding is not wrong ID draft-ietf-roll-mopex-cap-00 is
> introduced to support Projected DAO. I think Extended MOP is not required
> for projected DAO.
>
> Objective of P-DAO is to enable a path computing element (PCE) with
> global topological view of the network, knowledge of device capabilities
> and various network parameters to compute and install optimized (TE) routes
> to meet certain application requirements (Application scenarios requiring
> P2P path between devices).
>
> Why Projected DAO is more of a Capability Compare to the Mode of Operation?
>
> 1-     The core mesh network will always operate either in Storing or
> Non-Storing mode. Projected DAO will use the underlying topology to compute
> more efficient p-routes and install them either in storing or non-storing
> mode. A new LR, irrespective of it supports projected DAO or not it has to
> join the network. This joining decision is completely based on which mode
> global network is operating and the new LR supports it or not.
>
>
> 2-     P-DAO is more like a capability. This capability mostly includes
> if the LR has enough memory to store the P-Routes and support to do SRH
> based packet forwarding.
>
> Let’s consider the below scenarios
>
> 1—Global Network is Storing
>
>
>    - P-Route to be installed in Storing mode
>
> For this to work all the LR need to have P-Route table
>
>
>    -   P-Route to be installed is non-storing
>
> Just the Ingress node must store the route entry in the P-Route table and
> all other intermediate LRs in the P-Route process the SRH header and
> forward the packet.
>
> 2—Global Network is Non-Storing
>
>                Same requirement as above mentioned in storing mode case.
> So P-DAO is independent of global mode of operation of the LLN.
>
> What do you all think?
>
> Thanks
> Rabi
>
> _______________________________________________
> 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
>