Re: [Idr] 答复: WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)

Robert Raszuk <robert@raszuk.net> Fri, 24 July 2020 14:02 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B43A3A087D for <idr@ietfa.amsl.com>; Fri, 24 Jul 2020 07:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 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, HTML_MESSAGE=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=raszuk.net
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 dPuZFdJxYgeS for <idr@ietfa.amsl.com>; Fri, 24 Jul 2020 07:02:36 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 B893A3A087F for <idr@ietf.org>; Fri, 24 Jul 2020 07:02:35 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id a8so7122155edy.1 for <idr@ietf.org>; Fri, 24 Jul 2020 07:02:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rSt7kMnyhg49GB4+XvXZyW9MQb62aEgRY8VE5AtAIns=; b=Ut3iTcUW64ZWWuIt/j6D5zN//i0EsfZeOzPZtXnORuaHqFCZEQb0OkBVSYiLY59fHS ryjT/5LoWePpSuYsURgO2yZR3pBAN8Mk3InIvzPA78IryNhD/xl3PNgZaKcQl2QUXBDT ivQwqqUVmcDYx9JduR0557o6srInfZDes/j9iO9UhQCA69JJzlwmIZPsnCqg0GALbYsf Opr5haFDdyoBaR0WMOCKb46wFvOWYwsGyBamVACm92+n13BI8Qb7CkC5oSKIrYBJOgCg 0kDBnCTj2HD+YjSNfbXejUNsTwiEc85FIDAYkNFyxadJ6VxNGu3cIDAK+ZvgTKm0plR3 dWbg==
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=rSt7kMnyhg49GB4+XvXZyW9MQb62aEgRY8VE5AtAIns=; b=Zi5BqOdakvVoKg7hs4W73cW+HQBGeuDTZm0h3ETSR0LVWY49e6xPIjyNcjVnEx9Gpi CafsnT8CiY4lGqbIz6uHkw4VUa+k0Qg2Lk8AiSzB/b/QZoWmjNxrVgbPk0aB8wS/6p/Z xpLcFPDtnMR61z5SGzq548uK1LSY6yRnl9+ivX5O8YK0aACb8YhedUyYXBRaBQfKBRkh 4DEkhapM/GgM+3i6MHMtx5pq6nv9Q7Ot8Dr1DJuc5RlZvdwFRgCC/NQvTUfAIJyGnGbL 9hAP3O4NULoCWU9O8PYEZjgu/o5YRDxSSShRk/iQt7J9Y+hPaJr3INNPm7xJ7KauBmfW 7olA==
X-Gm-Message-State: AOAM533/t7vS1BzDcQyn84ioQMGws8Bj6XrQJTCIrED9jOg2knmMAlWX o7lM1Xwrg+e8/MFddWwWfjmIxpkF3XZrHK8RdDCR4g==
X-Google-Smtp-Source: ABdhPJwnyZuPA3bmXq0L51bOGIb1JI3E8LUS2Xy0960tbTNqyQg5HG3+Akit2ZA5s/aq7jivjS5nmcmeSD9HANGGU98=
X-Received: by 2002:aa7:dd14:: with SMTP id i20mr9406370edv.41.1595599353987; Fri, 24 Jul 2020 07:02:33 -0700 (PDT)
MIME-Version: 1.0
References: <003701d65aa9$689a64d0$39cf2e70$@ndzh.com> <000001d661b9$c54250f0$4fc6f2d0$@chinatelecom.cn> <CABNhwV2T0eaSQmH56-VdFWON4wb7xs18-UdJ_x+4mQKxJNPyEg@mail.gmail.com>
In-Reply-To: <CABNhwV2T0eaSQmH56-VdFWON4wb7xs18-UdJ_x+4mQKxJNPyEg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 24 Jul 2020 16:02:24 +0200
Message-ID: <CAOj+MMH1O9U-NbEHX2TmMbd_zpy-J9FmHQC6vVfjkMfUouozHg@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: Ou Liang <ouliang@chinatelecom.cn>, "idr@ietf. org" <idr@ietf.org>, Susan Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary="000000000000b2e27d05ab306cc1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/lL-rdq9TeN9DWKZWWSvo0KDXr0U>
Subject: Re: [Idr] =?utf-8?b?562U5aSNOiBXRyBMQyBvbiBkcmFmdC1pZXRmLWlkci1ycGQt?= =?utf-8?q?05=2Etxt_=287/15_to_7/29/2020=29?=
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jul 2020 14:02:41 -0000

> If wide communities has been abandoned

It has not been abandoned. We were waiting for more implementations -
that's all.

Thx.
R.

On Fri, Jul 24, 2020 at 3:44 PM Gyan Mishra <hayabusagsm@gmail.com> wrote:

>
> Hi Everyone
>
> There has been a lot of concern related to this draft after being adopted
> in 2019 and not having much feedback till now on WGLC.
>
> I agree with Ketan’s comments that it is two early for WGLC as their are
> significant questions and concerns that need to be addressed before we can
> proceed any further.
>
> A question was raised as is this an NMS function similar to BGP flowspec
> and if so then netconf and Yang already provides that solution.
>
> For SR we already have a centralized PCE controller based policy push that
> utilizes BGP LS to gather path information from the IGP for path steering.
>
> This draft seems to be reinventing a wheel that has been invented.
>
> 1) Do you feel this draft has an solution that is acceptable
>
>    With the IPR as a WG RFC?  No
>
>
>
> 2) Do you feel this draft is ready to publish? No
>
>
>
> 3) Do you know of implementations of this draft? No
>
>
>
> 4) Do you know of deployments of this draft?  No
>
> If so, is this feature useful in the deploy ments.
>
>
>
> 5) Do you feel that Wide Communities is ready for
>
> Publication?
>
> From the data tracker for wide communities the draft was adopted but since
> has expired.  The RPD draft is hinged on publication of wide communities.
> If wide communities has been abandoned I think that would impact this draft.
>
> https://datatracker.ietf.org/doc/draft-ietf-idr-wide-bgp-communities/
>
> My suggestion as others have stated is to not proceed with this document
> on WGLC and have further discussion if agreed to analyze how this draft
> fills a gap that exist today given the current solutions we have today with
> NMS Yang and Netconf as well as existing centralized PCE controller based
> solution for SR-TE policy push.
>
>
> Kind Regards
>
> Gyan
>
> On Fri, Jul 24, 2020 at 8:56 AM Ou Liang <ouliang@chinatelecom.cn> wrote:
>
>> Hi Everyone,
>>
>>
>>
>>     I support the WGLC of the draft.
>>
>>
>>
>> Best Regards,
>>
>> Liang Ou as a co-author
>>
>>
>>
>> *发件人:* Idr [mailto:idr-bounces@ietf.org] *代表 *Susan Hares
>> *发送时间:* 2020年7月15日 21:11
>>
>> *收件人:* idr@ietf.org
>> *主题:* [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)
>>
>>
>>
>> This begins a 2 week WG LC on draft-ietf-idr-rpd
>>
>> from 7/15 to 7/29/2020.  You can obtain this draft at:
>>
>> https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/
>>
>>
>>
>> This draft defines a new AFI/SAFI and new atoms
>>
>> for the Wide Communities.  This WG LC has been delayed
>>
>> as I waited for a resubmission of the Wide Communities draft.
>>
>> I had hoped to do these 2 WG LC in parallel.
>>
>>
>>
>> I’ve not received the Wide Communities draft, but we will
>>
>> start this WGLC to provide feedback to the authors.
>>
>> We may have to run a short follow-up to this WG LC
>>
>> If there are changes to the Wide Communities draft during
>>
>> Its WG LC.
>>
>>
>>
>> There is an IPR statement on this draft.
>>
>>
>>
>> In your responses please answer the following questions:
>>
>>
>>
>> 1) Do you feel this draft has an solution that is acceptable
>>
>>    With the IPR as a WG RFC?
>>
>>
>>
>> 2) Do you feel this draft is ready to publish?
>>
>>
>>
>> 3) Do you know of implementations of this draft?
>>
>>
>>
>> 4) Do you know of deployments of this draft?
>>
>> If so, is this feature useful in the deploy ments.
>>
>>
>>
>> 5) Do you feel that Wide Communities is ready for
>>
>> Publication?
>>
>>
>>
>> Cheerily, Susan Hares
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>>
> --
>
> <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions A**rchitect *
>
>
>
> *M 301 502-134713101 Columbia Pike *Silver Spring, MD
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>