Re: [Idr] new thread regarding capabilities handling

Enke Chen <enkechen@cisco.com> Thu, 27 April 2017 06:18 UTC

Return-Path: <enkechen@cisco.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 B8F60128656 for <idr@ietfa.amsl.com>; Wed, 26 Apr 2017 23:18:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 MjYekQfhMLEI for <idr@ietfa.amsl.com>; Wed, 26 Apr 2017 23:18:00 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A790127071 for <idr@ietf.org>; Wed, 26 Apr 2017 23:18:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=586; q=dns/txt; s=iport; t=1493273880; x=1494483480; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=s08mscB3+gCyoBPFr1EjCKcf1SUgQe9+gYb0O014cT4=; b=GeuucFJhi0GjdQxZNKFRA1o8i3Jyrk45XXSKsaUkbB9etH/fHk0TnfzZ 9tDBe1GpgN3D7LMF2HxbeELRwdKIAzmwPPk+UySb0BpDdJkdHaWB06VRp 1EjWcc3d4fVAqxMSfU3vDjUXd33ycO6sidPRxDrfVvkATdPKQ5hxzavim c=;
X-IronPort-AV: E=Sophos;i="5.37,257,1488844800"; d="scan'208";a="417764681"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Apr 2017 06:17:59 +0000
Received: from [10.82.220.141] (rtp-vpn3-1160.cisco.com [10.82.220.141]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v3R6Hwop010422; Thu, 27 Apr 2017 06:17:59 GMT
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <alpine.DEB.2.02.1704270713380.5591@uplift.swm.pp.se> <a7a10b72-2215-9968-e4c8-0592e29ce893@cisco.com> <alpine.DEB.2.02.1704270812470.5591@uplift.swm.pp.se>
Cc: idr@ietf.org, Enke Chen <enkechen@cisco.com>
From: Enke Chen <enkechen@cisco.com>
Message-ID: <cf8fc34c-7de7-89a0-9c71-05b56037ec81@cisco.com>
Date: Wed, 26 Apr 2017 23:17:58 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1704270812470.5591@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_GOk7qLlaMYq3UO-ClyDPcj3mMM>
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:18:01 -0000

Low demand. The feature request has never bubbled to the top tier for implementation.

-- Enke

On 4/26/17 11:14 PM, Mikael Abrahamsson wrote:
> 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?
>