Re: [Idr] Early allocation expiration for draft-ietf-idr-eag-distribution [was: Re: [idr] 2nd attempt - WG LC on draft -ietf-idr-eag-distribution (10/21/2018 to 11/3/2018) - ]

Jeff Tantsura <jefftant.ietf@gmail.com> Fri, 18 October 2019 21:21 UTC

Return-Path: <jefftant.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 50E31120074; Fri, 18 Oct 2019 14:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 nVCSGk8dNNCo; Fri, 18 Oct 2019 14:21:52 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 8A8F612008C; Fri, 18 Oct 2019 14:21:49 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id e10so4011344pgd.11; Fri, 18 Oct 2019 14:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=dK1nXFRWb+8uiGp1dLpvOU8fRgjEengsqCUgQGYP4NE=; b=vb6c4u5yUkGYJiLT7fFTqTwu9YnrdoB4fdCeQ+XjRW8GoCGQCR1gyKMItDbqFHkJxx Fs3OpQLQYs/xpfrBMlXBwgSIEAJGU46ranVMfbuUrcS+JCvM3wAGPaxSTvDrBqfAHBsh 10XWPwOaPTT5TOv0qXTUdrOmVWxapC8GJ/RuzKaxSoTKv4CDtX8u4fdy5DcCk7ioVffA tGzqextpe/0nKf5TUuKcbLwG/0mrBGr2wmLuxDArcoevSh6i6DaA75/31QZwXI+J8DqR ZpJZT+KmddZ0vELdOpqLj5plWfBQYxzMXBpPhVtlpq+F2MFCdXsE2LfFITeNMy4i3KJF T3BQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=dK1nXFRWb+8uiGp1dLpvOU8fRgjEengsqCUgQGYP4NE=; b=NT31vsDM/oSxh+nIRdRrhz07bm5iUxYfJO8LzpWBuF1UUA7cMu157qH1ImuRWXn4cd wbpXQRgIrbD3Ut8qYyzSrt70AjpFb6Pa712M8cB9GiGu0yiOzQWNr73I2oowXc68aMAg o+In9AvwNryqhLutfOjMMG9OKGHlQPNVxK13IacfMkaAb4A7uIkPZf+e79StsYsFre69 wRQ9enhAmXCMJoNHDeyqWtI0nEd6rIjYFBNQTn0gM46h1FvZYzf59fTeeARWt2D17tWg u4KGveqCygcqdyeOrlHIsrw9WwXdljqxWNErjUOl5RMMoB2SKC4ohgaj6eLDjx+277SQ dDyw==
X-Gm-Message-State: APjAAAVxJ54voOGXviZxyeyW/gyzcQb0siXmubKOQ/FpUazuCb8ELaAu iWcz6Qbe92o1eeeNjrNeEIE=
X-Google-Smtp-Source: APXvYqzeRtSTQ2duhj5ToFoVGF/xUpkBKhkIJ344bZ00+buIDgV3Xh9EmpbYDUzzlofJb/F3yl0YoA==
X-Received: by 2002:a17:90a:bb98:: with SMTP id v24mr13349170pjr.10.1571433708498; Fri, 18 Oct 2019 14:21:48 -0700 (PDT)
Received: from [10.5.5.194] ([50.235.77.202]) by smtp.gmail.com with ESMTPSA id e127sm7899049pfe.37.2019.10.18.14.21.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Oct 2019 14:21:47 -0700 (PDT)
Date: Fri, 18 Oct 2019 14:21:39 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>, Hares Susan <shares@ndzh.com>, "=?utf-8?Q?idr=40ietf.org?=" <idr@ietf.org>, "=?utf-8?Q?draft-ietf-idr-eag-distribution=40ietf.org?=" <draft-ietf-idr-eag-distribution@ietf.org>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Ketan Talaulikar (ketant)" <ketant@cisco.com>
Message-ID: <080e197f-5d67-4e37-9865-77f374e08bb3@Spark>
In-Reply-To: <SN6PR11MB28455987D3DCA12751953805C1430@SN6PR11MB2845.namprd11.prod.outlook.com>
References: <01a101d4754d$df996290$9ecc27b0$@ndzh.com> <DD519231-08F0-45B8-A360-6007329443EB@juniper.net> <BYAPR11MB36383A5C21E307F08BB87682C1430@BYAPR11MB3638.namprd11.prod.outlook.com> <SN6PR11MB28456BE84DB3626C0E483EDFC1430@SN6PR11MB2845.namprd11.prod.outlook.com> <SN6PR11MB28455987D3DCA12751953805C1430@SN6PR11MB2845.namprd11.prod.outlook.com>
X-Readdle-Message-ID: 080e197f-5d67-4e37-9865-77f374e08bb3@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5daa2ce8_1958bd17_cdaa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/qe8JPFBvGAfAinSDzeGiiB4-zpo>
Subject: Re: [Idr] Early allocation expiration for draft-ietf-idr-eag-distribution [was: Re: [idr] 2nd attempt - WG LC on draft -ietf-idr-eag-distribution (10/21/2018 to 11/3/2018) - ]
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, 18 Oct 2019 21:21:56 -0000

Dear chairs,

The draft in question has now implementations (as reported by Ketan) and authors believe it is ready for WGLC.
Kindly request you to start with the LC.

Thanks and have a great weekend!

Cheers,
Jeff
On Mar 22, 2019, 4:00 PM -0700, Ketan Talaulikar (ketant) <ketant@cisco.com>om>, wrote:
> Hi John/Sue,
>
> The report is updated with two implementations that we (Les & I) know of.
>
> These implementations were not available at the time of the previous WGLC and request for implementation reports. We would certainly like for the codepoint’s early allocation to be extended.
>
> Thanks,
> Ketan
>
> From: Ketan Talaulikar (ketant)
> Sent: 23 March 2019 02:49
> To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>rg>; Hares Susan <shares@ndzh.com>om>; idr@ietf.org; draft-ietf-idr-eag-distribution@ietf.org; Les Ginsberg (ginsberg) <ginsberg@cisco.com>
> Subject: Re: Early allocation expiration for draft-ietf-idr-eag-distribution [was: Re: [idr] 2nd attempt - WG LC on draft -ietf-idr-eag-distribution (10/21/2018 to 11/3/2018) - ]
>
> + 1
> From: Idr <idr-bounces@ietf.org> on behalf of Les Ginsberg (ginsberg) <ginsberg@cisco.com>
> Sent: Saturday, March 23, 2019 2:15:55 AM
> To: John Scudder; Hares Susan; idr@ietf.org; draft-ietf-idr-eag-distribution@ietf.org
> Subject: Re: [Idr] Early allocation expiration for draft-ietf-idr-eag-distribution [was: Re: [idr] 2nd attempt - WG LC on draft -ietf-idr-eag-distribution (10/21/2018 to 11/3/2018) - ]
>
> John –
>
> There are implementations of both RFC 7308 and draft-ietf-idr-eag-distribution.
>
> So I definitely support completing this work and can provide further info on the implementations I am aware of if requested.
>
>    Les
>
>
>
> From: Idr <idr-bounces@ietf.org> On Behalf Of John Scudder
> Sent: Friday, March 22, 2019 1:16 PM
> To: Hares Susan <shares@ndzh.com>om>; idr@ietf.org; draft-ietf-idr-eag-distribution@ietf.org
> Subject: [Idr] Early allocation expiration for draft-ietf-idr-eag-distribution [was: Re: [idr] 2nd attempt - WG LC on draft -ietf-idr-eag-distribution (10/21/2018 to 11/3/2018) - ]
>
> Folks,
>
> I think this is the last traffic I’ve seen on this subject. IANA recently reminded us that we have an early allocation code point for this draft, see https://www.iana.org/assignments/bgp-ls-parameters/bgp-ls-parameters.xhtml
>
> 1173 Extended Administrative Group (TEMPORARY - registered 2018-04-09, expires 2019-04-09)
> 22/14
>
> Note the expiration date. RFC 7120 talks about expiration (https://tools.ietf.org/html/rfc7120#section-3.3), the summary is that we can ask for a renewal for one more year, if we don’t, the allocation gets marked as “deprecated". The chairs often request extension without discussing it with the WG, when we know forward progress is being made. For this draft, I’m not sure progress IS being made, so I would like to get WG input. At issue is whether requirement 2(d) of RFC 7120, "sufficient interest in the community”, is still being met.
>
> When I look at the draft side by side with RFC 7308 I see that it’s more or less a translation, the way we often see for BGP-LS specs. Possibly in light of this the lack of WGLC response was because WG participants considered it too boring to review (sorry) and not exactly due to a lack of desire to see the document advance? On the other hand, with a cursory google search I didn’t find evidence of any vendor claiming support for RFC 7308… which, if so, doesn’t make me optimistic about implementation of this draft (and none has been reported yet, see https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-eag-distribution%20implementations). The close tracking between bgp-ls specs and IGP specs is one place where the lack of consistency between WG policies is problematic, where we want implementation to advance to RFC and the IGPs don’t.
>
> Since the allocation doesn’t expire until April 9, we have a few weeks. I plan to bring this up at Monday’s meeting, although I encourage you to follow up to this thread too. But to cut to the chase, I think we either need to muster the enthusiasm to complete WGLC for this draft, in which case I will gladly request an extension of the allocation, or… not.
>
> Thanks,
>
> —John
>
> > On Nov 5, 2018, at 4:24 PM, Susan Hares <shares@ndzh.com> wrote:
> >
> > Greetings:
> >
> > There was no response for the WG LC for draft-ietf-idr-eag-distribution-07.txt.
> >
> > Since we had no response and no implementation reports, this draft has not reached consensus.  It will return to the status of WG draft.
> >
> > Cheerily, Susan Hares
> > Shepherd
> > WG Co-chair
>