IETF Logo Mail Archive

Re: [Idr] BGP: Vendor Specific Capabilities

Neil Matthew <neil@abelon.com> Tue, 22 April 2008 17:48 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3890E28C2FC; Tue, 22 Apr 2008 10:48:40 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DFD428C30E for <idr@core3.amsl.com>; Tue, 22 Apr 2008 10:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MlCHbyDgBXAG for <idr@core3.amsl.com>; Tue, 22 Apr 2008 10:48:37 -0700 (PDT)
Received: from mailout08.yourhostingaccount.com (mail18.yourhostingaccount.com [65.254.253.234]) by core3.amsl.com (Postfix) with ESMTP id 739B828C2FC for <idr@ietf.org>; Tue, 22 Apr 2008 10:48:37 -0700 (PDT)
Received: from mailscan14.yourhostingaccount.com ([10.1.15.14] helo=mailscan14.yourhostingaccount.com) by mailout08.yourhostingaccount.com with esmtp (Exim) id 1JoMbj-0007cv-1N for idr@ietf.org; Tue, 22 Apr 2008 13:48:43 -0400
Received: from impout02.yourhostingaccount.com ([10.1.55.2] helo=impout02.yourhostingaccount.com) by mailscan14.yourhostingaccount.com with esmtp (Exim) id 1JoMbi-0001z1-Ni; Tue, 22 Apr 2008 13:48:42 -0400
Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10]) by impout02.yourhostingaccount.com with NO UCE id GhoX1Z00B0D2B7u0000000; Tue, 22 Apr 2008 13:48:31 -0400
X-EN-OrigOutIP: 10.1.18.10
X-EN-IMPSID: GhoX1Z00B0D2B7u0000000
Received: from host86-156-115-228.range86-156.btcentralplus.com ([86.156.115.228] helo=[192.168.1.101]) by authsmtp10.yourhostingaccount.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim) id 1JoMbW-00089Z-M6; Tue, 22 Apr 2008 13:48:31 -0400
Message-ID: <480E24EA.2090609@abelon.com>
Date: Tue, 22 Apr 2008 18:48:26 +0100
From: Neil Matthew <neil@abelon.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: "'sundeep.mudgal@nokia.com'" <sundeep.mudgal@nokia.com>
References: <E5E76343C87BB34ABC6C3FDF3B31272702427B7B@daebe103.NOE.Nokia.com> <2EE638FFD18B294395AE688204CE7E6F1DFC1B05@EXCH-CLUSTER-09.force10networks.com>
In-Reply-To: <2EE638FFD18B294395AE688204CE7E6F1DFC1B05@EXCH-CLUSTER-09.force10networks.com>
X-EN-UserInfo: e65bfd3d72dfaaaf5ffb0de99fd01ea2:0d98aba8e5f6749be2df7f931a889135
X-EN-AuthUser: neilrm
X-EN-OrigIP: 86.156.115.228
X-EN-OrigHost: host86-156-115-228.range86-156.btcentralplus.com
Cc: "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] BGP: Vendor Specific Capabilities
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi

Given the wording of the question I'd like to stress the "local to the 
speaker" part. A peer should not close a connection just because it 
doesn't recognize a capability. It's up to the speaker to determine 
whether support for the particular capability is vital for the 
connection to continue.

Cheers

Neil

Kalpesh Zinjuwadia wrote:
>
> Implementation can choose either way. RFC3392 states that “the 
> decision is local to the speaker”.
>
> Thanks,
>
> Kalpesh
>
> *From:* idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] *On Behalf 
> Of *sundeep.mudgal@nokia.com
> *Sent:* Tuesday, April 22, 2008 8:36 AM
> *To:* idr@ietf.org
> *Subject:* [Idr] BGP: Vendor Specific Capabilities
>
> Hi,
>
> Could you please confirm whether vendor-specific capabilities should 
> be ignored or responded to with the unsupported capability message?
>
> Thanks,
> Sandeep Mudgal
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>   

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr

v2.15.0 | Report a Bug | By Email