[Idr] IANA allocation request for draft-ietf-idr-bgp-ls-sr-policy-01
Ketan Talaulikar <ketant.ietf@gmail.com> Wed, 27 September 2023 05:10 UTC
Return-Path: <ketant.ietf@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 C0499C16B5BC; Tue, 26 Sep 2023 22:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UZr_HtM0TgIY; Tue, 26 Sep 2023 22:10:55 -0700 (PDT)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33FA3C1CCC8B; Tue, 26 Sep 2023 22:10:22 -0700 (PDT)
Received: by mail-ej1-x629.google.com with SMTP id a640c23a62f3a-9adb9fa7200so2282784066b.0; Tue, 26 Sep 2023 22:10:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695791420; x=1696396220; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=rUQqliwpmgtgepI79p+Nk6FtrkonMm/X4GN9ywkufow=; b=b0usAYmQAekTygAqFWY+VoJ7ZtpXJ1F+Q5ar3lVq3AWzCbxLwAdiftWtyo8aIY+bwZ 2AhzBswyAq6hTrzhQBO4shThzEm+Jd/oIcL1wRiQxkQqmwgdE7qmTyMvdAPqe/dEZrUl tkyahDxbUz43O4y5IMQ23pFVMtZoEvDR6pZUhYHN4O+eELE8/z1pNnd4E09ZhD8hZqLO xpq+FS146seIFwHb7cEPyJVyW1ot1FGS69b8nVCgeuFFURzc81AOuJGtN7zg3/QIIJXH s1UQDWipKtWtrEn3VlZE/DGp2qSUaTM7/Alps5bVwzzfUgCNfpvLFeG38ejRdbNUaqFe HYHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695791420; x=1696396220; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=rUQqliwpmgtgepI79p+Nk6FtrkonMm/X4GN9ywkufow=; b=P0DQhlEQ3OF1pPWglD3N8pa2slCdSNMUz0c5wU9bqmduJUY6tf0dff0t7BLll0RKGv WpKF9WOVXV7gQtgkGdpFL0CnJ5xrklcsiwW8JeFdkuaB4XIvbF35f6Bd4QpDC2OF9s8E 2D2subHDj+HXMFRvN4cM7LOD/hoxQxz3R5/z+7rfxA8VOI2eJ4QmNslyq1ExR6T9OyDF rW3jGejRxKA2S4pvsXIg/hiGmCOurh/gRLbCM0p3LuFJhEijNxkbxo5IrWSgc6mrcfti S1MJxVgm174dxySzH3cEDhNqmaKAgkMSEWvXBndeaXQgXYjM0FfaX3lQQxLfbsFXNN4R hBUg==
X-Gm-Message-State: AOJu0YxP6mMLHI35j2BIjtKxZ3cR3YvGBNvx4I7622hfCG4o1l2mGQtx b7235q10KgJhKZHg1fN5LbIZZ76n1uv0EtguXaIccDOF
X-Google-Smtp-Source: AGHT+IGSBEYIYjC//R6Jx/vC/BiV+cwmAxJ6VkHt5+gUvSrPhSSUwjkyGomuE5OW/D2cC4e4NzjnBjqk8DcU3NP8d4k=
X-Received: by 2002:a17:906:7955:b0:9ae:705a:8451 with SMTP id l21-20020a170906795500b009ae705a8451mr7480435ejo.25.1695791420265; Tue, 26 Sep 2023 22:10:20 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR08MB48729370D9A713DA28155E3DB3EDA@BYAPR08MB4872.namprd08.prod.outlook.com> <CAH6gdPwxMcXVyDAMA9+vM=i4bf8q=GZ45muG8OkDJ0DVabrUPw@mail.gmail.com>
In-Reply-To: <CAH6gdPwxMcXVyDAMA9+vM=i4bf8q=GZ45muG8OkDJ0DVabrUPw@mail.gmail.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Wed, 27 Sep 2023 10:40:09 +0530
Message-ID: <CAH6gdPw+t7L=XoBKi6mhNiOd=azUnkMKp2iAfFFC9i3uq6Dyew@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>, idr-chairs <idr-chairs@ietf.org>
Cc: "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000037d7550606503519"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/M_TE2_NhzRYLtruOcehNf73C8ZA>
Subject: [Idr] IANA allocation request for draft-ietf-idr-bgp-ls-sr-policy-01
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 27 Sep 2023 05:10:55 -0000
< Changing the subject to highlight the request for IANA allocation > Hi Sue, Please let us (authors) know if we can go ahead and request the same with IANA. Note this is not an early allocation but a normal allocation request via "Expert Review" procedures. Thanks, Ketan On Fri, Sep 22, 2023 at 4:55 PM Ketan Talaulikar <ketant.ietf@gmail.com> wrote: > Hi Sue, > > As indicated during the presentation during IETF 117, the authors would > like to request allocations for the pending code points for this draft as > follows: > > 1214 (suggested) SR Segment List Identifier > > 1215 (suggested) SR Bidirectional Group Constraint > > 1216 (suggested) SR Metric Constraint > > 1217 (suggested) SR Segment List Bandwidth > > > This will help us start preparation of implementation reports for this > draft as well. > > Also, thanks for your review and please check inline below for responses. > > > On Fri, Sep 8, 2023 at 4:02 PM Susan Hares <shares@ndzh.com> wrote: > >> This is a shepherd report for draft-ietf-idr-bgp-ls-sr-policy-00. >> >> >> >> This draft will need to be adjusted after >> draft-ietf-idr-segment-routing-te-policy is split into two drafts. >> > > KT> I am not sure that would be necessary. That draft was about BGP SR > Policy SAFI and this is BGP-LS SAFI - they are different and independent. > > >> >> >> Why?: draft-ietf-idr-segment-routing-te-policy is an informative >> reference. >> > > KT> There is no normative dependence on the BGP SR Policy SAFI document. > This BGP-LS draft is about (northbound) advertisement of SR Policies from > routers (headend) to controllers. The source of the SR Policy on the > headend could be local configuration (e.g., via CLI, Netconf, etc.) or via > protocols PCEP or BGP SR Policy SAFI. > > >> >> >> Other-things to fix: >> >> >> >> Section 5.2 – >> >> >> >> U-flag – specify what the flag means when the bit is zero. >> > > KT> When clear it indicates that this CP is using the specified BSID. This > flag is ignored when there is no specified BSID. Will include this in the > next update. > > >> >> >> Section 7.0 >> >> >> >> Thank you for putting RFC7752bis in this document. >> >> I recommend you consider adding a bit more text prior to WG LC. >> >> Consider issues on rapid change and detection. >> > > KT> Could you please elaborate a bit more on this? There is nothing of the > nature of "statistics" or "counters" that are being advertised here which > could change rapidly. This is quite similar to protocol state - albeit > related to SR Policies. > > >> >> >> Section 9.0 >> >> >> >> This section needs upgrading to present the likely problems. >> >> At least you should consider what RFC7752bis issues have been closed. >> > > KT> Agree. Will update this section for the next update. > > Thanks, > Ketan > > >> >> >> I will add this to the early review queue as soon as the >> draft-ietf-idr-segment-routing-te-policy is completed. >> >> >> >> Cheers, Sue >> >
- [Idr] Shepherd report on draft-ietf-idr-bgp-ls-sr… Susan Hares
- Re: [Idr] Shepherd report on draft-ietf-idr-bgp-l… Ketan Talaulikar
- [Idr] IANA allocation request for draft-ietf-idr-… Ketan Talaulikar
- Re: [Idr] IANA allocation request for draft-ietf-… Susan Hares
- Re: [Idr] Shepherd report on draft-ietf-idr-bgp-l… Ketan Talaulikar
- Re: [Idr] Shepherd report on draft-ietf-idr-bgp-l… Susan Hares