Re: [Idr] new thread regarding capabilities handling

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 27 April 2017 06:14 UTC

Return-Path: <swmike@swm.pp.se>
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 7CE67127071 for <idr@ietfa.amsl.com>; Wed, 26 Apr 2017 23:14:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 6YGC1hIydahA for <idr@ietfa.amsl.com>; Wed, 26 Apr 2017 23:14:10 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15671120326 for <idr@ietf.org>; Wed, 26 Apr 2017 23:14:09 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 03EF7A6; Thu, 27 Apr 2017 08:14:07 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1493273648; bh=1cwd5HFR7cu+oMIxhSwrlnuxAQZfbZgosGjbfc5SLYU=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=MRySGf6M8nFd8ko/GDPhvYDJIS2QCXn9YIWa8WLhMQvYlpgmIMpgh9SuZqa6+SRS4 cbpoSpayDg4ttwmYF5GjTg1mI8hdriRX8aHwr6D8lWCfQanSrHsxQ3cifCfUOtTumv 71qAX2zgWaQ01tkXtY8yVyR7qxJDtqjCSZe/CK5E=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id F30F3A4; Thu, 27 Apr 2017 08:14:07 +0200 (CEST)
Date: Thu, 27 Apr 2017 08:14:07 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Enke Chen <enkechen@cisco.com>
cc: idr@ietf.org
In-Reply-To: <a7a10b72-2215-9968-e4c8-0592e29ce893@cisco.com>
Message-ID: <alpine.DEB.2.02.1704270812470.5591@uplift.swm.pp.se>
References: <alpine.DEB.2.02.1704270713380.5591@uplift.swm.pp.se> <a7a10b72-2215-9968-e4c8-0592e29ce893@cisco.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/rCozn0tnTmjckx1OnFr0YBfAsp4>
Subject: Re: [Idr] new thread regarding capabilities handling
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 27 Apr 2017 06:14:12 -0000

On Wed, 26 Apr 2017, Enke Chen wrote:

> Hi, Mikael:
>
> Please take a look at the "BGP Dynamic Capability" draft:
>
>   https://www.ietf.org/archive/id/draft-ietf-idr-dynamic-cap-14.txt

So this is a draft first posted in 2001, with a last revision in 2011.

What's the back story here? This is obviously a well-known understood 
problem then for 16 years already, why don't we still have this in 2017?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se