Re: [GROW] route leak solution and IANA large community register

Job Snijders <job@instituut.net> Tue, 09 March 2021 20:08 UTC

Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 442DB3A098D for <grow@ietfa.amsl.com>; Tue, 9 Mar 2021 12:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.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 y2FEUo1Vd6pZ for <grow@ietfa.amsl.com>; Tue, 9 Mar 2021 12:08:46 -0800 (PST)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 6EE223A098C for <grow@ietf.org>; Tue, 9 Mar 2021 12:08:46 -0800 (PST)
Received: by mail-ed1-x536.google.com with SMTP id b13so22910346edx.1 for <grow@ietf.org>; Tue, 09 Mar 2021 12:08:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=resent-from:resent-date:resent-message-id:resent-to:delivered-to :date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=dpPj4nsHW3+hmBzTYFryAXWtMCZFsHinsgknEmPFeXU=; b=F6mu1m6eA+ZWPN0NCkx8tfxhazbYEuQG1A7wnEnVhm/DAMVRttl/CB9R91NZs3S1Mo MDq4gb4wCJpI+QMjf1fcAahl5rsO9fQcZ+vbdG3wqq7Mn95YqGwIeb20160hP0qX2734 1jqpNK2lI9EHkeabpuvBMBYmGTxvzkjeBt4k5u2IP3qxnAB9YcK4p/BsF9DzsA/AXzZ7 tbnHNvg8LTp7TxWZquy6lJp1PGLeNlrcbmGyy+AKhBsKkj1VLhWY2fP6xesLkhWnDoJA 2JPTo4yCWPOfcZFJ6QHWx4XbcWEl94n3G3cZjCVy+kmYbJpO5TfTEis03DfH+V4qUcGa xbBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:resent-from:resent-date:resent-message-id :resent-to:delivered-to:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=dpPj4nsHW3+hmBzTYFryAXWtMCZFsHinsgknEmPFeXU=; b=TSVFVt7l81d8RIa96IoOMUa2No86sXGtFttkbcAeuW4NJTGV1i2fEEwj+EjHkNwES4 jI9RdNHpYuZ80zK0Oo7IKgK3UZmSHHOfI9aN8BDl/nFLBPe2sVzUw2YjPshhOJQu3q6C CEthOQbazIb5edurkpC198xEDTVOcDRIdc5FhNv6vicjb4qFFjfMD/v2+HRZVld0doqw BaZrOlfXwmR1gt4gw9ceFwntbb3gaAICjqkCxJH3otK/P6qtDGqREJCXU7WHD/MpteCk 2B80bJqL8yV6Yw5UDcH+gmL+NKoA2N7bYibsAkbJapy3fanbWXEp/81XTYOClRSEP69Q SLgg==
X-Gm-Message-State: AOAM5303/mP1VUZmBf1A4FtA3N/3C9oDHr+Me+bJ1S9h/rLsQdvaiJsf VThh5L97ZRLG23YTUggDWsQyI1y4wsHruH7N
X-Google-Smtp-Source: ABdhPJyTraWKdCWKmT57g0e/Gaz4nMFVCxy5nk/1dYG+31dPYY/raj21cM9YHhhroem9ffCsTQNQVg==
X-Received: by 2002:a05:6402:484:: with SMTP id k4mr6090246edv.321.1615320523874; Tue, 09 Mar 2021 12:08:43 -0800 (PST)
Received: from bench.sobornost.net (mieli.sobornost.net. [45.138.228.4]) by smtp.gmail.com with ESMTPSA id bi26sm8875464ejb.120.2021.03.09.12.08.42 for <grow@ietf.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 09 Mar 2021 12:08:42 -0800 (PST)
Received: from localhost (bench.sobornost.net [local]) by bench.sobornost.net (OpenSMTPD) with ESMTPA id b8330bd3 for <grow@ietf.org>; Tue, 9 Mar 2021 20:08:42 +0000 (UTC)
Resent-From: Job Snijders <job@sobornost.net>
Resent-Date: Tue, 09 Mar 2021 20:08:42 +0000
Resent-Message-ID: <YEfVytKqg3GcKocm@bench.sobornost.net>
Resent-To: grow@ietf.org
Delivered-To: job@freedom.nl
Received: from smtp.freedom.nl ([10.10.3.36]) by c03ms02.soverin.net with LMTP id uMdFEgHAR2BtRAAALNfU0g (envelope-from <job@instituut.net>) for <job@freedom.nl>; Tue, 09 Mar 2021 18:35:45 +0000
Received: from smtp.freedom.nl (smtp.freedom.nl [116.202.65.211]) by soverin.net
Received: from localhost (bench.sobornost.net [local]) by bench.sobornost.net (OpenSMTPD) with ESMTPA id 541401c0; Tue, 9 Mar 2021 18:35:40 +0000 (UTC)
Date: Tue, 09 Mar 2021 18:35:40 +0000
From: Job Snijders <job@instituut.net>
To: Susan Hares <shares@ndzh.com>
Cc: "'Sriram, Kotikalapudi (Fed)'" <kotikalapudi.sriram@nist.gov>, 'Christopher Morrow' <christopher.morrow@gmail.com>, grow-chairs@ietf.org, idr-chairs@ietf.org, 'GROW WG' <grow@ietf.org>
Message-ID: <YEe//IaKrADaCKbv@bench.sobornost.net>
References: <SA9PR09MB48140BE009F021BA83A2EA3D84949@SA9PR09MB4814.namprd09.prod.outlook.com> <019001d71509$dea9adf0$9bfd09d0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <019001d71509$dea9adf0$9bfd09d0$@ndzh.com>
X-Virus-Scanned: clamav-milter 0.102.4 at c03mi01
X-Virus-Status: Clean
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/NuMl2W4mVLClkYRNYXi5AGLelsA>
Subject: Re: [GROW] route leak solution and IANA large community register
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2021 20:08:48 -0000

Dear Sriram, Sue,

Working Group Last Call is possible, but I suspect after WGLC it will
not be possible for the document to progress beyond the Shepherd
Write-up step, because the current -04 version essentially is blocking
on a normative dependency on 'draft-heitz-idr-wklc' (or any successor).

My recommendation would be to let both efforts proceed independently, 
as it probably would be good to continue discussion on whether
draft-ietf-grow-route-leak-detection-mitigation's objective can only be
solved with Large Communities; and separately whether in the large
communities 'space' a segment of the 'spectrum' should be set aside for
future well-known through standards documented signaling.

Kind regards,

Job
GROW Working Group Chair

On Tue, Mar 09, 2021 at 12:30:14PM -0500, Susan Hares wrote:
> Sriram:
> 
> If IDR adopts the draft, you can ask for early allocation on the registry.
> Before that point,  let me chat with the IDR co-chairs and ADs to what other
> options you have. 
> 
> Cheers,  Sue 
> 
> -----Original Message-----
> From: Sriram, Kotikalapudi (Fed) [mailto:kotikalapudi.sriram@nist.gov] 
> Sent: Sunday, March 7, 2021 6:26 PM
> To: Christopher Morrow; Job Snijders
> Cc: grow-chairs@ietf.org; GROW WG; idr-chairs@ietf.org; Susan Hares;
> a.e.azimov@gmail.com
> Subject: route leak solution and IANA large community register
> 
> I have a question for the GROW Chairs and anyone who can help.
> 
> There are these two drafts:
> Methods for Detection and Mitigation of BGP Route Leaks
> https://tools.ietf.org/html/draft-ietf-grow-route-leak-detection-mitigation-
> 04
> 
> BGP Well Known Large Community
> https://tools.ietf.org/html/draft-heitz-idr-wklc-01
> 
> The first is in a mature state in GROW and the second is in a
> pre-adoption-call state in IDR. The first draft requests IANA for an
> allocation in well-known Large Community (WKLC) registry but no such IANA
> registry exists yet. The second draft (in IDR) is making an effort to
> specify and request the creation of an IANA WKLC registry. This work seems
> to be going slow in IDR -- partly the authors are responsible (including
> me).  
> 
> Question: Is the creation of an IANA Large Community registry a prerequisite
> for a WGLC on the first one (in GROW)? Or, it is possible to have WGLC
> requested/completed on the first one and then wait for the creation of the
> IANA LC registry?
> 
> Thanks.
> 
> Sriram  
> 
> 
> 
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow