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

Ines Robles <mariainesrobles@googlemail.com> Fri, 01 November 2019 08:19 UTC

Return-Path: <mariainesrobles@googlemail.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 B1F42120145 for <roll@ietfa.amsl.com>; Fri, 1 Nov 2019 01:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_HELO_NONE=0.001, 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=googlemail.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 yCfGijElUMpv for <roll@ietfa.amsl.com>; Fri, 1 Nov 2019 01:19:48 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 ABA7012012C for <roll@ietf.org>; Fri, 1 Nov 2019 01:19:48 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id u8so10066514iom.5 for <roll@ietf.org>; Fri, 01 Nov 2019 01:19:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ln6OEMDfJlr7Q0iuFLG2+s2vf7ph143VlVDYemDvza0=; b=jV+YRs4idU3DnGS7bFYVMjfcl9xJaUFg9tPCVqeF4gS1bBq279uWNlnjCiWZFJ00CJ B8sBzJTZLV4zy2ip+ySGZ1BdX6qGx36xgeKpiKOmwwL8sHnKAFfEFc6AdGPlB32BnBMh /6twH9oUqobRaY/JVltvOQv5KHJL3+K1BXMporHzIz5zRe/Yo9HPzLOdHLpWL8I8d+zF vluWIcKfs42FczAQBzicui3coc4aMsqXO7rJJji6noKNx3T1aRaEuXhceyr+K1vH1xkK xjcJ6jy5Qkqa1FXbYdWCPennYfPrzYHO7Dsb93DDN4cbMiRVy3CLdq3vhi130r+IvjXt AKeQ==
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=ln6OEMDfJlr7Q0iuFLG2+s2vf7ph143VlVDYemDvza0=; b=CLzTQS8DnY1E8xDsjr8UQU+ILCdqtqRZQgLM+DDCG7dNmRMOIyOpOAWVZqC2C/Hf/t N8PDZYk5mrdou/TSNyaFy2TesHK98inEG3LuqnfCat/p9d0nZsiFZdkygPRQhLMIizLL LB1DV3LeUj0hkTNhBR4cgCWuiseunE1lonqK3YmoJy0quQozviFhkTEwFV77flk1FvSr IMQsWfCgyZrOy0oeRz2TlhugaQ75+k+Imj1L4vye9NSHHiExtWBfIymD1Va6jJHdrEku 0StU4QFfb/m+Q2k0/e+xz//hvugveSiCiJqa1YAKgCbUROMpjDGON9Aqk4/QAmNTZvHC RmLw==
X-Gm-Message-State: APjAAAUcJV+lJWSutf0rUAFwhdCY+3NzAyWUxWNakXIa4Ch1e+K5VSdA XpvrP1ZwAtCoXC2fom1Wf+Wtt2H6DQRpCoHP6V4DIw==
X-Google-Smtp-Source: APXvYqys4OldJutcafcdfTamAWiwEslWvCyFIvlXFa7a6jbf6b6NzeVTVfJwwyn9MUevtMt2z0qdlEdZchdqz+0XH2w=
X-Received: by 2002:a6b:b294:: with SMTP id b142mr8723979iof.243.1572596387428; Fri, 01 Nov 2019 01:19:47 -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: Ines Robles <mariainesrobles@googlemail.com>
Date: Fri, 1 Nov 2019 10:19:10 +0200
Message-ID: <CAP+sJUebf5HV91FfencRr_fBPgdNB29Y-+K0qp2guzVwkGF10g@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000c3b75059644a148"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/vxFu3Gnv0225e1I4zt7xjqdUB9s>
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: Fri, 01 Nov 2019 08:19:51 -0000

Hi,

This is a lot of stuff and I expect we’ll need more time than I initially
> expected at the WG meetings.
>

We will take that into account when we build the agenda ;-)

Thanks,

Ines.

>
> 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
>