Re: [Bgp-autoconf] assumptions

Jeff Tantsura <jefftant.ietf@gmail.com> Tue, 25 February 2020 22:43 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: bgp-autoconf@ietfa.amsl.com
Delivered-To: bgp-autoconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 377073A044A for <bgp-autoconf@ietfa.amsl.com>; Tue, 25 Feb 2020 14:43:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bIz6NwofTjm for <bgp-autoconf@ietfa.amsl.com>; Tue, 25 Feb 2020 14:43:26 -0800 (PST)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (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 6EC603A045B for <bgp-autoconf@ietf.org>; Tue, 25 Feb 2020 14:43:26 -0800 (PST)
Received: by mail-pj1-x102b.google.com with SMTP id 12so382413pjb.5 for <bgp-autoconf@ietf.org>; Tue, 25 Feb 2020 14:43:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=Qw0kZEUxGkfiIoM5V/wgg8JTGL+Es4yT3ROCG1bETQI=; b=bxHSmg/eKT7sQkGW3ii4KQpvXFaVUZjgs2fLv0N1IQmYK0tGvyQk0SzDego6yE1wSt s6+qiNDkcbjAwa6fumsxHDzmPU5xJPJVJGrg2ReObtZOMErfCCPHDr6bxPiInfHuILqX X7IY+LEXtycb+mUSGHbt0YIX7iEhekBUWnQZm/eKRfLylw0zdAzP0fLDsOd3xO5r9qNY L+1DyxXFeNDOq102PQtBiobsnVkQXd8a+KhZoF5o9VX23dEjt42D+MRVg5dQrO2dAR91 cokxU3mFBvRPy3JxvSG8JQb05ClcXxT1iibi49xoxc66P57wITDLzMbsp6ypqzUYkKcQ OgrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=Qw0kZEUxGkfiIoM5V/wgg8JTGL+Es4yT3ROCG1bETQI=; b=YMfoRymHNKPCJ+Z3x7kdczihDLlsolAHa4jc9C+tps6mQfch7Cv3e+CP8bayb3568y zlinQo3GlA5sNPSY/H3vzNxQ3o4KYDzIKukM1H2vFt0oyrPSRyBOFSlr6+6cRm7ThrNu gMk8u4Om7L8p9kW4oUxvlc2bmlh4VqodB1skc0wRLoWhOfs/jpj5SIfDiugx0OXDAWSm ywq0FOwlc4NDnJKyc06d+MblkUZh+MGQdsuyMfs+pxoR8h7lQf6mMvqody8Lc/k1uwbB 9m8R7ndTCjT/KufhYSXOaf4PPMJjg0p19+GDEUP0xDwiE85IUUXTUAEdpDBl96QrDZUu +hWQ==
X-Gm-Message-State: APjAAAUaqqdn3nhajjaNSCE254cb8Nx1Gtmd8DPbW8unkwlt65+0eHoB UMBn7fbCKNvpbmEuVm4HIh0=
X-Google-Smtp-Source: APXvYqzH9800+6XuWj8bgP9P9MJHhWSeJaHBKQAIV9cgLSm9R6YrcC0Gt5DYzGvjCrU34UCc612hRA==
X-Received: by 2002:a17:902:9b8b:: with SMTP id y11mr794241plp.189.1582670605992; Tue, 25 Feb 2020 14:43:25 -0800 (PST)
Received: from ?IPv6:2607:fb90:4e32:100c:712c:3cb3:c791:a3c0? ([2607:fb90:4e32:100c:712c:3cb3:c791:a3c0]) by smtp.gmail.com with ESMTPSA id a22sm108118pfk.108.2020.02.25.14.43.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 25 Feb 2020 14:43:25 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-26A1E3B3-58B2-41CB-B245-F4FA9436530E
Content-Transfer-Encoding: 7bit
From: Jeff Tantsura <jefftant.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 25 Feb 2020 14:43:23 -0800
Message-Id: <47BCD9AD-DF94-457D-808D-8ECA3C7B1A69@gmail.com>
References: <F9DF2BA0-3980-488E-B10B-B8E57C804DAB@pfrc.org>
Cc: Randy Bush <randy@psg.com>, bgp autoconf <bgp-autoconf@ietf.org>, "Dongjie (Jimmy)" <jie.dong@huawei.com>
In-Reply-To: <F9DF2BA0-3980-488E-B10B-B8E57C804DAB@pfrc.org>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/Ua_9fIJOmBFvUIR3DJ9IImyJ6WI>
Subject: Re: [Bgp-autoconf] assumptions
X-BeenThere: bgp-autoconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP autoconfiguration design team discussion list <bgp-autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bgp-autoconf/>
List-Post: <mailto:bgp-autoconf@ietf.org>
List-Help: <mailto:bgp-autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2020 22:43:28 -0000

+1

Regards,
Jeff

> On Feb 25, 2020, at 12:14, Jeffrey Haas <jhaas@pfrc.org> wrote:
> 
> 
> 
>> On Feb 25, 2020, at 2:49 PM, Randy Bush <randy@psg.com> wrote:
>> 
>> hi jie,
>> 
>>>>  o we are not changing bgp
>>> [Jie] Not sure we discussed this during the conference call or not.
>> 
>> actually, i made the assertion three times.  there was no response.
>> so i have made it again :)
> 
> Actually, I had commented on the possible need to push some of this stuff into BGP depending on where we drew our lines on some of the layering.
> 
> I'd like to avoid unnecessary changes.  I'm not willing to rule them out.
> 
> I believe that sticking with as close to base BGP as possible is a feature: It means that auto-discovery features can be lightly strapped on top of boring BGP implementations that have modest support for programmatic neighbor setup.
> 
> -- Jeff
> 
> -- 
> Bgp-autoconf mailing list
> Bgp-autoconf@ietf.org
> https://www.ietf.org/mailman/listinfo/bgp-autoconf