Re: [spring] [Detnet] IETF-111 SPRING presentation on sr-redundancy-protection

Gyan Mishra <hayabusagsm@gmail.com> Tue, 27 July 2021 06:27 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 765323A1677; Mon, 26 Jul 2021 23:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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 ZCaAPu1IodAn; Mon, 26 Jul 2021 23:27:21 -0700 (PDT)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (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 5C4FA3A1673; Mon, 26 Jul 2021 23:27:21 -0700 (PDT)
Received: by mail-pl1-x634.google.com with SMTP id f13so4137824plj.2; Mon, 26 Jul 2021 23:27:21 -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 :cc; bh=Vd0D8gdsDanJko+kZ8TrI/NQSQkGAh+jM+4gtCVlXyo=; b=OK5wnVjQcbnk8WemugzZ1EE6s2MzxJuF99QyBzG41cwxVOV5jp1O9rt+Do+AG0ByTZ bhtr4NfaA4bzz3Y9AZftVcMGNLqQrxNWrdGWY/8sMZSAkLw0dJYaIX0jvLA88GnjttGc u9y/uQNLqQsfUShIH11ERCpNVzvYGrhmK9S1pjtjV1gKkvahQL8sK/jXQv7IsHQY55TZ +kCx+G7eZZIO9NUGcnFFXYkWl5cpfPRUpx0eyVtS2DSj/olXzj8gcP0AGDzNMJ+WJh5p /8PAFlDfTHtQhQmcA8xHU58tCgsAXYg9BsaqB9yA+rQcXuaRLifc69ExxHeBwTUEfI/W Ql4A==
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:cc; bh=Vd0D8gdsDanJko+kZ8TrI/NQSQkGAh+jM+4gtCVlXyo=; b=KEeKyd5fDgtwSRNht42G71OsSyd4SbvWoL+2xAvQudBJjJsALykqljrJqOQktbnqnq gPCEwyBfnTYewgJ2vmtT1DTY0ZL10aU+y3R4f+Rc36N0h+a747/oF/9Bih62g/QFFlOq 4r/E74KkhXT8LmzZu+KUE+R8xbeU6uKCwDx5QG0JfuQAkldNxWMxEXYybrz+nNeyx/wy 76psFWjmr+iNUWYrhgCR36SA6Be9CXi1k7dBBN3xfxJ/mMYRVg2vNPyDJMOy1UxC4Y7R XjhCgln4ovpXu+koGZvgEFJFrfCgKn7RK7n+0XUDN58PfQhjLRhiXfEh/b3R4DR89wx0 3Dfw==
X-Gm-Message-State: AOAM530ZEqEFZWYx82zkwMQQiriFy8V0FUHjy4he0Vf0zF0oCn0LO0Sz s+2335GbMcphANDCtKRQvfIEFHN7zPu+tfSOUZfuVQmoxHk=
X-Google-Smtp-Source: ABdhPJzOnzox+71DSZM+470ifcb2L8qA4zNBORLiQTAj8JHPL4zYoqhMc/m36gNYfV9cYbfFuzDOz2a4L/VpyNVoM2U=
X-Received: by 2002:a65:40cc:: with SMTP id u12mr18125692pgp.18.1627367240490; Mon, 26 Jul 2021 23:27:20 -0700 (PDT)
MIME-Version: 1.0
References: <AM0PR07MB534758C127CEEBFDEF67C327ACE89@AM0PR07MB5347.eurprd07.prod.outlook.com> <047f01c93fde45aeaa2dfc6147bbf5c4@huawei.com> <AM0PR07MB534714E9AC4AE20ADB06779BACE89@AM0PR07MB5347.eurprd07.prod.outlook.com>
In-Reply-To: <AM0PR07MB534714E9AC4AE20ADB06779BACE89@AM0PR07MB5347.eurprd07.prod.outlook.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Tue, 27 Jul 2021 02:27:09 -0400
Message-ID: <CABNhwV1JBWmEUm+Q9HiKviVVpftej_QAFi2U91yYE5=yCcLo+g@mail.gmail.com>
To: =?UTF-8?Q?Bal=C3=A1zs_Varga_A?= <balazs.a.varga=40ericsson.com@dmarc.ietf.org>
Cc: "Yangfan (IP Standard)" <shirley.yangfan@huawei.com>, "detnet@ietf.org" <detnet@ietf.org>, "draft-geng-spring-sr-redundancy-protection@ietf.org" <draft-geng-spring-sr-redundancy-protection@ietf.org>, spring <spring@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000049e24a05c814f64c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/wbHm71czcs5DqCVjIvd_WHYHU7k>
Subject: Re: [spring] [Detnet] IETF-111 SPRING presentation on sr-redundancy-protection
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2021 06:27:27 -0000

Hi Balázs

Very nicely put that the redundancy protection draft was inspired by DETNET
framework  to now provide extensions to improve the functionality of SR.

We will make that clear in the draft.

As for DETNET use case I think we can leave off the table for now and
update the draft accordingly.  After adoption we can investigate the
possibilities and of making the redundancy protection inclusive of DETNET.
I think the hurdle of P2MP and as that is out of scope today and as DETNET
to be an inclusive use case we would have to figure out P2MP which will be
challenging.

Kind Regards

Gyan
On Mon, Jul 26, 2021 at 5:20 PM Balázs Varga A <balazs.a.varga=
40ericsson.com@dmarc.ietf.org> wrote:

> Hi Fan,
>
>
>
> Thanks for your prompt reply.
>
> I agree with your direction to redefine the target of this mechanism. In
> my view your draft was “inspired by DetNet” and
>
> intends to improve the functionality of SR. That is absolutely fine. :--))
>
>
>
> Please, make it clear in the draft as well, that would avoid any
> misinterpretations.
>
>
>
> Thanks & Cheers
>
> Bala’zs
>
>
>
>
>
> *From:* Yangfan (IP Standard) <shirley.yangfan@huawei.com>
> *Sent:* Monday, July 26, 2021 11:09 PM
> *To:* Balázs Varga A <balazs.a.varga@ericsson.com>om>;
> draft-geng-spring-sr-redundancy-protection@ietf.org
> *Cc:* spring <spring@ietf.org>rg>; detnet@ietf.org
> *Subject:* 答复: IETF-111 SPRING presentation on sr-redundancy-protection
>
>
>
> Hi Balazs,
>
>
>
> Thank you for your comments.
>
> As what Gyan mentioned during the presentation, this draft redefines
> redundancy protection as a general protection mechanism designed for SR
> network. Firstly, it is a general mechanism can be used in many uses cases,
> not only DetNet use case. Secondly, it applies to SR network, not a general
> IP or MPLS data plane solution which Detnet requires. Since the scope is
> changed, I don’t think redundancy protection is necessary to follow DetNet
> architecture.
>
> If redundancy protection is not a DetNet mechanism, I don’t think it
> should cover both P2P and P2MP services.
>
> We are happy to address the comments that relates to redundancy protection
> in next revision.
>
>
>
> Thanks.
>
> Fan
>
>
>
> *发件人**:* Balázs Varga A [mailto:balazs.a.varga@ericsson.com
> <balazs.a.varga@ericsson.com>]
> *发送时间:* 2021年7月27日 4:49
> *收件人:* draft-geng-spring-sr-redundancy-protection@ietf.org
> *抄送:* spring <spring@ietf.org>rg>; detnet@ietf.org
> *主题:* IETF-111 SPRING presentation on sr-redundancy-protection
>
>
>
> Hi,
>
>
>
> As time not permitted comments during the SPRING meeting, major comments
> regarding the
>
> redundancy protection presentation:
>
>
> https://datatracker.ietf.org/meeting/111/materials/slides-111-spring-sr-for-redundancy-protection-00
>
>
>
> 1, General: despite the reference to DetNet this draft is not compliant
> with Figure 1 of RFC8655 (DetNet Architecture)
>
> 2, Slide-9: DetNet provides both p2p and p2mp services. This draft only
> p2p, so many DetNet use cases cannot be supported
>
> 3, Slide-9: there were many DetNet related comments on the list. Only some
> were addressed in the latest version of the draft.
>
>
>
> Thanks & Cheers
>
> Bala’zs
>
>
>
>
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*