Re: [Idr] WG LC for draft-ietf-idr-bgp-open-policy-10.txt (6/4 to 6/18) - WG LC completed, awaiting -12.txt

Alexander Azimov <a.e.azimov@gmail.com> Tue, 07 July 2020 19:48 UTC

Return-Path: <a.e.azimov@gmail.com>
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 59FF43A08FA for <idr@ietfa.amsl.com>; Tue, 7 Jul 2020 12:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level:
X-Spam-Status: No, score=-1.097 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, 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 AbdRjcS-Eksb for <idr@ietfa.amsl.com>; Tue, 7 Jul 2020 12:48:06 -0700 (PDT)
Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (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 709C23A091D for <idr@ietf.org>; Tue, 7 Jul 2020 12:48:06 -0700 (PDT)
Received: by mail-oi1-x235.google.com with SMTP id l63so34428191oih.13 for <idr@ietf.org>; Tue, 07 Jul 2020 12:48:06 -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=au0oRgz/62JamYJ+nhhh0PRtQtYSEYA7kHpeC8y1Gz4=; b=B/QG5/T0IWEQXZOtYDQXze1vHvAJpJ4DKPJWdC8gu1Z4GDINmIFoDfkE8GDihs01AU vCFMYGYRMIHrEFUY5LDtJL7vQBwZQjw1ubi9bLqRHNghvKwrwIAogTCy/M5ly4qekRJA XZk+WqwY1PZD214kpuT6v68FXvYFFXMJE1jNu2WfyO7voRkv6hMruRqbT7UWdG3TaeQv bW/Re5EfK0DWi1Ti1CHSbhTmxoEQEHtSMT5FvVoyAUsD/vJ9+97fVnlA+9EgL64be2y1 wwyTz5DUAtNNC3aCSgEZio7/6b6fCoRpY/PP+Rqp22/9y4SqirAfcQxTzVl/sYzSLXdd gx5w==
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=au0oRgz/62JamYJ+nhhh0PRtQtYSEYA7kHpeC8y1Gz4=; b=XKLdCX4Kkm8cfupV1amZQVa5F+CbbH3O3c3nHl86hTrRnQe+y4ONsV6FBjf3A8L4T7 i/ADx3IHSYbYcD6jSiSubxRD1J71qeWXkLYZwVken2k1afoS7MJR52ahTNXMRknvtTRj Q3C0cls927khUYYqNw3fLSD+ndV53NbQvsvcuad1N4KndEm/DkPb+Pre6C5QrjeP3/+r Y4ha8gct9V5VfQCfXlOhzHJSVarh5mS9qKWcZzf9tPBmGRKD9ZO71s4iSERuv+wyf0VO vol/Whv3DXKsfIx+nadBwgdOGT4z3j9/c06bbFx4g98x6vYw06/j++7wQCxrnDClUSqc F91Q==
X-Gm-Message-State: AOAM533AaDWMBAxbTh7UV0aaqnL+dqOOAAYSWyqqpCraaV3JOdQofYI+ Gd5omu6BQUL9LQVzTudjyyrZr0MEezFUbaTCSmQ=
X-Google-Smtp-Source: ABdhPJyWDX/z9CXUTBl67TnAL0UMZlwJxF1Wd8erCB/l3zMXx/OET4SgYR8m+9vyM1lRiBmgi/adu94/+BteTDBzfns=
X-Received: by 2002:aca:5885:: with SMTP id m127mr3272343oib.4.1594151285630; Tue, 07 Jul 2020 12:48:05 -0700 (PDT)
MIME-Version: 1.0
References: <BL0PR0901MB368202D333455541409DBF2184680@BL0PR0901MB3682.namprd09.prod.outlook.com> <BL0PR0901MB3682A0E599708BDDFD2E2A7B84690@BL0PR0901MB3682.namprd09.prod.outlook.com> <CAH1iCiqfkmbZHyVaYotdEV7VJkgc==xtJqLjuVcHE6e+YZgwdg@mail.gmail.com> <CAEGSd=BmyL0Z3DqdkotF=+BjyX8-b5ZkBnD-YS=d=-bJyDNUtg@mail.gmail.com> <000001d653d5$f0886b60$d1994220$@ndzh.com> <CAH1iCipoye4KmWF=cdP7HftuwDZ13wi_ePMFFD9vgqPMWoT6PA@mail.gmail.com> <002d01d653e5$037f7830$0a7e6890$@ndzh.com>
In-Reply-To: <002d01d653e5$037f7830$0a7e6890$@ndzh.com>
From: Alexander Azimov <a.e.azimov@gmail.com>
Date: Tue, 07 Jul 2020 22:47:54 +0300
Message-ID: <CAEGSd=A_79=ctkNQ0p-wZDTnP7sR9Ziv4zrfVH2132wybW35uw@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: Brian Dickson <brian.peter.dickson@gmail.com>, IDR <idr@ietf.org>, "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram=40nist.gov@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001928b105a9df4558"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/gc3IyVjNKFJR5R4evSCAnjJSjqQ>
Subject: Re: [Idr] WG LC for draft-ietf-idr-bgp-open-policy-10.txt (6/4 to 6/18) - WG LC completed, awaiting -12.txt
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: Tue, 07 Jul 2020 19:48:08 -0000

Susan,

I've just pushed -13, it should resolve the ambiguity in roles definition.

вт, 7 июл. 2020 г. в 01:30, Susan Hares <shares@ndzh.com>:

> Brian and Alex:
>
>
>
> Would you please provide the text with the minor nits as -13.txt – so I
> know you are ready for shepherd’s review.
>
> I’d like to get this off to Alvaro’s list this week.
>
>
>
> Thank you, Susan Hares
>
>
>
> *From:* Brian Dickson [mailto:brian.peter.dickson@gmail.com]
> *Sent:* Monday, July 6, 2020 6:17 PM
> *To:* Susan Hares
> *Cc:* Alexander Azimov; IDR; Sriram, Kotikalapudi (Fed)
> *Subject:* Re: [Idr] WG LC for draft-ietf-idr-bgp-open-policy-10.txt (6/4
> to 6/18) - WG LC completed, awaiting -12.txt
>
>
>
> Hi, Sue,
>
>
>
> Per Alex's response, no changes. The table and policy are clear.
>
> The only possible change would be minor text changes to reference the
> table in the main text, if that makes sense to do (i.e. makes the document
> clearer to the reader.)
>
>
>
> Brian
>
>
>
> On Mon, Jul 6, 2020 at 1:42 PM Susan Hares <shares@ndzh.com> wrote:
>
> Alex and Brian:
>
>
>
> If you add any new limitations, this will need to go back through WG LC.
>
>
>
> However, WG LC is only 2 weeks (if no changes are made).   If you think it
> is required, then add it now – before I put in my shepherd’s repor.t
>
>
>
> Sue
>
>
>
> *From:* Idr [mailto:idr-bounces@ietf.org] *On Behalf Of *Alexander Azimov
> *Sent:* Monday, July 6, 2020 4:13 PM
> *To:* Brian Dickson
> *Cc:* IDR; Sriram, Kotikalapudi (Fed); Susan Hares
> *Subject:* Re: [Idr] WG LC for draft-ietf-idr-bgp-open-policy-10.txt (6/4
> to 6/18) - WG LC completed, awaiting -12.txt
>
>
>
> Brian,
>
>
>
> I don't feel it's good to add any limitations aka stripping. Roles are
> negotiated, that is their main idea.
>
> And we already have an allocation policy for future roles:
>
>
>
>    The allocation policy for new entries up to and including
>    value 127 is "Expert Review" [RFC5226].  The allocation policy for
>    values 128 through 251 is "First Come First Served".  The values from
>    252 through 255 are for "Experimental Use".
>
>
>
>
>
>
>
> пн, 6 июл. 2020 г. в 22:49, Brian Dickson <brian.peter.dickson@gmail.com>:
>
>
>
>
>
> On Mon, Jul 6, 2020 at 11:24 AM Sriram, Kotikalapudi (Fed)
> <kotikalapudi.sriram=40nist.gov@dmarc.ietf.org> wrote:
>
> Hi Gyan,
>
> You wrote:
> "In the context of keeping the door open for future internal roles as the
> reader would be confused when reading “any” meaning iBGP, however internal
> roles don’t exist today.  My recommendation would be to update the draft to
> say “any” when the internal roles are explicitly defined.  That could be
> done anytime when you have fully vetted the internal role concept and the
> draft is updated accordingly."
>
> Would the following substitution take care of your concern?
>
> Current text: BGP Role is a new configuration option that can
> be configured on any BGP session.
>
> New text: This document specifies a new configuration option
> BGP Role that is intended to be used with eBGP.
> However, in the future, the applicability of BGP Role
> can be extended to iBGP when suitable internal roles are defined.
>
>
>
> As an alternative, maybe change the text so that it references an IANA
> table, and have the new table introduced via the IANA Actions section, with
> particulars about how new table entries get added?
>
> Allow for private roles as well as new standard roles, with details on
> what to do with private roles (if private roles are defined/allowed), e.g.
> strip or substitute on announcement via eBGP.
>
> Or just have the well-defined roles table only, and require standards
> action to add table entries with reference to RFCs in the table.
>
>
>
> Brian
>
>
>
> Thanks.
>
> Sriram
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
>
>
>
> --
>
> Best regards,
>
> Alexander Azimov
>
>

-- 
Best regards,
Alexander Azimov