From idr-bounces@ietf.org  Wed Apr  2 10:30:04 2008
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 1AB0E28C528;
	Wed,  2 Apr 2008 10:30:04 -0700 (PDT)
X-Original-To: idr@ietf.org
Delivered-To: idr@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id A069228C2DA; Wed,  2 Apr 2008 10:30:01 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080402173001.A069228C2DA@core3.amsl.com>
Date: Wed,  2 Apr 2008 10:30:01 -0700 (PDT)
Cc: idr@ietf.org
Subject: [Idr] I-D Action:draft-ietf-idr-flow-spec-01.txt
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>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.


	Title           : Dissemination of flow specification rules
	Author(s)       : P. Roque Marques, et al.
	Filename        : draft-ietf-idr-flow-spec-01.txt
	Pages           : 25
	Date            : 2008-04-02

This document defines a new BGP NLRI encoding format that can be used
to distribute traffic flow specifications.  This allows the routing
system to propagate information regarding more-specific components of
the traffic aggregate defined by an IP destination prefix.

Additionally it defines two applications of that encoding format.
One that can be used to automate inter-domain coordination of traffic
filtering, such as what is required in order to mitigate
(distributed) denial of service attacks.  And a second application to
traffic filtering in the context of a BGP/MPLS VPN service.

The information is carried via the Border Gateway Protocol (BGP),
thereby reusing protocol algorithms, operational experience and
administrative processes such as inter-provider peering agreements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-flow-spec-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-idr-flow-spec-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-04-02102957.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--


From idr-bounces@ietf.org  Tue Apr  8 06:28:29 2008
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 7E59A28C3BA;
	Tue,  8 Apr 2008 06:28:29 -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 1497928C3B9
	for <idr@core3.amsl.com>; Tue,  8 Apr 2008 06:28:28 -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 pmUNzkg-ONDw for <idr@core3.amsl.com>;
	Tue,  8 Apr 2008 06:28:22 -0700 (PDT)
Received: from aibo.runbox.com (aibo.runbox.com [193.71.199.94])
	by core3.amsl.com (Postfix) with ESMTP id 9776528C3AF
	for <idr@ietf.org>; Tue,  8 Apr 2008 06:28:22 -0700 (PDT)
Received: from [10.9.9.162] (helo=pepper.runbox.com)
	by greyhound.runbox.com with esmtp (Exim 4.50)
	id 1JjDs2-0006oq-PP; Tue, 08 Apr 2008 15:28:18 +0200
Received: from [166.128.9.43] (helo=[166.128.9.43])
	by pepper.runbox.com with esmtpa  (uid:277705 )  (Exim 4.50)
	id 1JjDs1-0004Nj-Ne; Tue, 08 Apr 2008 15:28:18 +0200
Message-Id: <DF39D56D-2DA8-467A-BBD5-0DC779EC8DD1@runbox.com>
From: Sean Muller <seangmuller@runbox.com>
To: Jithu Arun Sreedhar <jithuarun@gmail.com>
In-Reply-To: <cf2df5d0803310123j2d07881dy8e9362b6728038bf@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 8 Apr 2008 08:28:14 -0500
References: <cf2df5d0803310123j2d07881dy8e9362b6728038bf@mail.gmail.com>
X-Mailer: Apple Mail (2.919.2)
Cc: idr@ietf.org
Subject: Re: [Idr] SendNOTIFICATIONwithoutOPEN
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

If I am reading the specification correctly the  =

SendNOTIFICATIONwithoutOPEN is for communicating error states so  =

unless the initial peering has occurred and/or this configuration is  =

setup on both peers the SendNOTIFICATIONwithoutOPEN would fail. Or am  =

I reading the specification wrong?


Sean Muller
seangmuller@runbox.com
214-250-3988 Cell
"Do or do not... there is no try.=94 Yoda







On Mar 31, 2008, at 3:23 AM, Jithu Arun Sreedhar wrote:
> Hi
>
> By the definition of SendNOTIFICATIONwithoutOPEN, it allows a peer to
> send a NOTIFICATION without first sending an OPEN message. But how do
> you convey this to the peer dynamically. Statically if you know so
> then the working of the attribute can be explained, but for dynamic
> configurations, for example an unconfigured peer, how do you let the
> BGP peer know that you are expecting a NOTIFICATION without an OPEN in
> case of an OPEN error.
>
> Jithu Arun Sreedhar.
> _______________________________________________
> 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


From idr-bounces@ietf.org  Wed Apr 16 06:32:38 2008
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 90C5B3A6D46;
	Wed, 16 Apr 2008 06:32:38 -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 27CE63A6D46
	for <idr@core3.amsl.com>; Wed, 16 Apr 2008 06:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ObNe5AyOsw89 for <idr@core3.amsl.com>;
	Wed, 16 Apr 2008 06:32:36 -0700 (PDT)
Received: from smtp3.sgsi.ucl.ac.be (smtpout.sgsi.ucl.ac.be [130.104.5.77])
	by core3.amsl.com (Postfix) with ESMTP id 4F8FB3A6BB9
	for <idr@ietf.org>; Wed, 16 Apr 2008 06:32:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=uclouvain.be; h=
	message-id:date:from:reply-to:mime-version:to:cc:subject:
	content-type:content-transfer-encoding; q=dns/txt; s=selucl; bh=
	+d3S6LW36XxYBAGuwY9ZP0UJ7aU=; b=Qa1uQh7pgLh2TL1BIXqquprsMe/q89Pz
	6UKFbdgoc2nx/pRb5rymqvKi/UHScGbOUQqLIa5DIQqBAmLSopeLgrKSuKNmkRLU
	i56esnM4GGwrgNaQ6XV/XSn5IC25z4ZmnXNVc39v4iAEoTDz8kSGgZ8CB6uj/epD
	Yy8wGe1p4v8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=uclouvain.be; h=message-id:date:
	from:reply-to:mime-version:to:cc:subject:content-type:
	content-transfer-encoding; q=dns; s=selucl; b=BF5HDB9LyyWBC6R+TP
	V6rsHyVVgetx6/xrVwfT2YgftzI0tvlkz+dzqdzUoCcElUcYYbpZyro8wGp5GXvh
	hpRDAnLyz3tE+onFsM+FkhkLSdJK6mInBJxnKKL5R9Hnz2RKTgVha63rASlPhyAX
	fUzArCN5nrhhJKEHO1EJkn4Zo=
Received: from nukuhiva.dhcp.info.ucl.ac.be (unknown [130.104.228.77])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: pifrancois@smtp3.sgsi.ucl.ac.be)
	by smtp3.sgsi.ucl.ac.be (Postfix) with ESMTP;
	Wed, 16 Apr 2008 15:33:06 +0200 (CEST)
Message-ID: <48060010.4080306@uclouvain.be>
Date: Wed, 16 Apr 2008 15:33:04 +0200
From: Pierre Francois <pierre.francois@uclouvain.be>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: idr@ietf.org
X-AV-Checked: ClamAV using ClamSMTP
X-Sgsi-Spamcheck: SASL authenticated, 
X-MailScanner-ID: 7D7C01C5D79.01F1F
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: pierre.francois@uclouvain.be
X-SGSI-Spam-Status: No
Cc: DECRAENE Bruno RD-CORE-ISS <bruno.decraene@orange-ftgroup.com>
Subject: [Idr] I-D Action:draft-francois-bgp-gshut-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: pierre.francois@uclouvain.be
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi all,

Please find below a draft that tries to address the requirements draft for the 
graceful shutdown of BGP sessions.

We would appreciate your feedback on this first attempt.

Regards,
Pierre.


-------- Original Message --------
Subject: I-D Action:draft-francois-bgp-gshut-00.txt
Date: Sat, 15 Mar 2008 13:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.

    Title           : Graceful BGP session shutdown
    Author(s)       : P. Francois, et al.
    Filename        : draft-francois-bgp-gshut-00.txt
    Pages           : 15
    Date            : 2008-03-15

This draft describes operational procedures aimed at reducing the
amount of traffic lost during planned maintenances of routers,
involving the shutdown of BGP peering sessions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-francois-bgp-gshut-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Tue Apr 22 08:36:55 2008
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 57BAD3A6C32;
	Tue, 22 Apr 2008 08:36:55 -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 C46273A6A8E
	for <idr@core3.amsl.com>; Tue, 22 Apr 2008 08:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 vsVNTY0ut4cG for <idr@core3.amsl.com>;
	Tue, 22 Apr 2008 08:36:50 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id F3E1828C46F
	for <idr@ietf.org>; Tue, 22 Apr 2008 08:36:24 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m3MFcMul010468 for <idr@ietf.org>; Tue, 22 Apr 2008 10:38:58 -0500
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 22 Apr 2008 18:35:49 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 22 Apr 2008 10:35:42 -0500
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 22 Apr 2008 10:35:39 -0500
Message-ID: <E5E76343C87BB34ABC6C3FDF3B31272702427B7B@daebe103.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: BGP:  Vendor Specific Capabilities
Thread-index: AcikjoQkoBpWMXC5QH2LtLt9J2knWg==
From: <sundeep.mudgal@nokia.com>
To: <idr@ietf.org>
X-OriginalArrivalTime: 22 Apr 2008 15:35:42.0161 (UTC)
	FILETIME=[8610AC10:01C8A48E]
X-Nokia-AV: Clean
Subject: [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: multipart/mixed; boundary="===============0463743884=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0463743884==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8A48E.85CD9E5E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8A48E.85CD9E5E
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable


Hi,

        Could you please confirm whether vendor-specific capabilities
should be ignored or responded to with the unsupported capability
message?

Thanks,
Sandeep Mudgal

------_=_NextPart_001_01C8A48E.85CD9E5E
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.3">
<TITLE>BGP:  Vendor Specific Capabilities</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi,</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Could you =
please confirm whether</FONT> <FONT SIZE=3D2 FACE=3D"Courier =
New">vendor-specific capabilities should be ignored or responded to with =
the unsupported capability message?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Thanks,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">Sandeep Mudgal</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C8A48E.85CD9E5E--

--===============0463743884==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0463743884==--


From idr-bounces@ietf.org  Tue Apr 22 10:24:56 2008
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 7264F3A6E83;
	Tue, 22 Apr 2008 10:24:56 -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 AFFEE3A68D2
	for <idr@core3.amsl.com>; Tue, 22 Apr 2008 10:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 S9QLcRgvHN0f for <idr@core3.amsl.com>;
	Tue, 22 Apr 2008 10:24:49 -0700 (PDT)
Received: from mx.force10networks.com (corp.force10networks.com
	[64.186.164.204])
	by core3.amsl.com (Postfix) with ESMTP id CBCEF3A6E7A
	for <idr@ietf.org>; Tue, 22 Apr 2008 10:24:49 -0700 (PDT)
Received: from mx.force10networks.com ([10.11.0.221]) by
	mx.force10networks.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 22 Apr 2008 10:23:16 -0700
Received: from exch7-sjc-fe.force10networks.com ([10.11.0.87]) by
	mx.force10networks.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 22 Apr 2008 10:23:15 -0700
Received: from EXCH-CLUSTER-09.force10networks.com ([10.11.10.113]) by
	exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi;
	Tue, 22 Apr 2008 10:23:16 -0700
From: Kalpesh Zinjuwadia <kzinjuwadia@force10networks.com>
To: "'sundeep.mudgal@nokia.com'" <sundeep.mudgal@nokia.com>, "idr@ietf.org"
	<idr@ietf.org>
Date: Tue, 22 Apr 2008 10:23:14 -0700
Thread-Topic: BGP:  Vendor Specific Capabilities
Thread-Index: AcikjoQkoBpWMXC5QH2LtLt9J2knWgADp51Q
Message-ID: <2EE638FFD18B294395AE688204CE7E6F1DFC1B05@EXCH-CLUSTER-09.force10networks.com>
References: <E5E76343C87BB34ABC6C3FDF3B31272702427B7B@daebe103.NOE.Nokia.com>
In-Reply-To: <E5E76343C87BB34ABC6C3FDF3B31272702427B7B@daebe103.NOE.Nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 22 Apr 2008 17:23:15.0922 (UTC)
	FILETIME=[8CCE7320:01C8A49D]
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: multipart/mixed; boundary="===============0234905480=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

--===============0234905480==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_2EE638FFD18B294395AE688204CE7E6F1DFC1B05EXCHCLUSTER09fo_"

--_000_2EE638FFD18B294395AE688204CE7E6F1DFC1B05EXCHCLUSTER09fo_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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 sunde=
ep.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 shoul=
d be ignored or responded to with the unsupported capability message?

Thanks,
Sandeep Mudgal

--_000_2EE638FFD18B294395AE688204CE7E6F1DFC1B05EXCHCLUSTER09fo_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas=
.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.or=
g/2001/04/xmlenc#" xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xm=
lns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http=
://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf=3D"http://schemas.micros=
oft.com/data/udc/xmlfile" xmlns:wf=3D"http://schemas.microsoft.com/sharepoi=
nt/soap/workflow/" xmlns:mver=3D"http://schemas.openxmlformats.org/markup-c=
ompatibility/2006" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/o=
mml" xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relation=
ships" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/t=
ypes" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/me=
ssages" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<title>BGP: Vendor Specific Capabilities</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Implementation can choose either way. RFC3392 states that &#=
8220;the
decision is local to the speaker&#8221;.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Thanks,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Kalpesh<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] <b>On Behalf Of </b>sund=
eep.mudgal@nokia.com<br>
<b>Sent:</b> Tuesday, April 22, 2008 8:36 AM<br>
<b>To:</b> idr@ietf.org<br>
<b>Subject:</b> [Idr] BGP: Vendor Specific Capabilities<o:p></o:p></span></=
p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Hi,</s=
pan> <o:p></o:p></p>

<p><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Could you please confirm whether</span> <span style=3D'font-size:10.0pt;
font-family:"Courier New"'>vendor-specific capabilities should be ignored o=
r
responded to with the unsupported capability message?</span><o:p></o:p></p>

<p><span style=3D'font-size:10.0pt;font-family:"Courier New"'>Thanks,</span=
> <br>
<span style=3D'font-size:10.0pt;font-family:"Courier New"'>Sandeep Mudgal</=
span> <o:p></o:p></p>

</div>

</body>

</html>

--_000_2EE638FFD18B294395AE688204CE7E6F1DFC1B05EXCHCLUSTER09fo_--

--===============0234905480==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0234905480==--


From idr-bounces@ietf.org  Tue Apr 22 10:48:40 2008
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 =93the =

> decision is local to the speaker=94.
>
> 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


From idr-bounces@ietf.org  Tue Apr 22 10:59:35 2008
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 30DC93A6E67;
	Tue, 22 Apr 2008 10:59:35 -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 87DD33A6E61
	for <idr@core3.amsl.com>; Tue, 22 Apr 2008 10:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 lewPfgsgyWJp for <idr@core3.amsl.com>;
	Tue, 22 Apr 2008 10:59:32 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id 2517F3A6D4F
	for <idr@ietf.org>; Tue, 22 Apr 2008 10:59:32 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id 365E453E201;
	Tue, 22 Apr 2008 13:59:38 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id SZ-wKHtaFj2N; Tue, 22 Apr 2008 13:59:22 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id 2A68653E1B5;
	Tue, 22 Apr 2008 13:59:22 -0400 (EDT)
Message-Id: <1BA6DC24-A122-4453-B0A8-D093DC54880F@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: <sundeep.mudgal@nokia.com> <sundeep.mudgal@nokia.com>
In-Reply-To: <E5E76343C87BB34ABC6C3FDF3B31272702427B7B@daebe103.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 22 Apr 2008 13:59:20 -0400
References: <E5E76343C87BB34ABC6C3FDF3B31272702427B7B@daebe103.NOE.Nokia.com>
X-Mailer: Apple Mail (2.919.2)
Cc: 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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

It should be ignored.  Per RFC 3392, the unsupported capability  
message is a way to complain if your peer doesn't support a capability  
that you insist on having support for.  An example would be if the  
peer doesn't support MP-BGP and you are trying to establish a v6  
peering.  Here is the pertinent text from RFC 3392:

"If a BGP speaker that supports a certain capability determines that  
its peer doesn't support this capability, the speaker MAY send a  
NOTIFICATION message to the peer, and terminate peering (see Section  
"Extensions to Error Handling" for more details). The Error Subcode in  
the message is set to Unsupported Capability. The message SHOULD  
contain the capability (capabilities) that causes the speaker to send  
the message. The decision to send the message and terminate peering is  
local to the speaker. If terminated, such peering SHOULD NOT be re- 
established automatically."

I apologize for the confusing name of the notification message.   
Probably something like "Required Capability Missing" would have been  
better. :-(

Correct behavior with respect to any unknown capability from your peer  
(whether vendor-specific or otherwise) is generally to ignore it.

--John

On Apr 22, 2008, at 11:35 AM, <sundeep.mudgal@nokia.com> <sundeep.mudgal@nokia.com 
 > wrote:

>
> 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


From idr-bounces@ietf.org  Tue Apr 22 11:48:44 2008
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 552213A6B8B;
	Tue, 22 Apr 2008 11:48:44 -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 4F2B43A6D21
	for <idr@core3.amsl.com>; Tue, 22 Apr 2008 11:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 zHy+6QXRRBWY for <idr@core3.amsl.com>;
	Tue, 22 Apr 2008 11:48:31 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 3CF373A6988
	for <idr@ietf.org>; Tue, 22 Apr 2008 11:48:17 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m3MIi8sj019031; Tue, 22 Apr 2008 13:44:20 -0500
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 22 Apr 2008 21:41:11 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 22 Apr 2008 13:41:07 -0500
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 22 Apr 2008 13:39:40 -0500
Message-ID: <E5E76343C87BB34ABC6C3FDF3B31272756B0D4@daebe103.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: [Idr] BGP:  Vendor Specific Capabilities
Thread-index: AcikoqkQvLro6HjNRb+Ta63UoQH/BAABZAiq
References: <E5E76343C87BB34ABC6C3FDF3B31272702427B7B@daebe103.NOE.Nokia.com>
	<1BA6DC24-A122-4453-B0A8-D093DC54880F@bgp.nu>
From: <sundeep.mudgal@nokia.com>
To: <jgs@bgp.nu>
X-OriginalArrivalTime: 22 Apr 2008 18:41:07.0382 (UTC)
	FILETIME=[6D36AD60:01C8A4A8]
X-Nokia-AV: Clean
Cc: 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: multipart/mixed; boundary="===============1399992116=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1399992116==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8A4A8.6C8A6052"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8A4A8.6C8A6052
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

So when you say "ignore", does it mean that peer continues with the =
connection or drop the connection without sending any notification?


-----Original Message-----
From: ext John G. Scudder [mailto:jgs@bgp.nu]
Sent: Tue 4/22/2008 12:59 PM
To: Mudgal Sundeep (Nokia-S&S/MtView)
Cc: idr@ietf.org
Subject: Re: [Idr] BGP:  Vendor Specific Capabilities
=20
It should be ignored.  Per RFC 3392, the unsupported capability =20
message is a way to complain if your peer doesn't support a capability =20
that you insist on having support for.  An example would be if the =20
peer doesn't support MP-BGP and you are trying to establish a v6 =20
peering.  Here is the pertinent text from RFC 3392:

"If a BGP speaker that supports a certain capability determines that =20
its peer doesn't support this capability, the speaker MAY send a =20
NOTIFICATION message to the peer, and terminate peering (see Section =20
"Extensions to Error Handling" for more details). The Error Subcode in =20
the message is set to Unsupported Capability. The message SHOULD =20
contain the capability (capabilities) that causes the speaker to send =20
the message. The decision to send the message and terminate peering is =20
local to the speaker. If terminated, such peering SHOULD NOT be re-=20
established automatically."

I apologize for the confusing name of the notification message.  =20
Probably something like "Required Capability Missing" would have been =20
better. :-(

Correct behavior with respect to any unknown capability from your peer =20
(whether vendor-specific or otherwise) is generally to ignore it.

--John

On Apr 22, 2008, at 11:35 AM, <sundeep.mudgal@nokia.com> =
<sundeep.mudgal@nokia.com=20
 > wrote:

>
> Hi,
>
>         Could you please confirm whether vendor-specific =20
> capabilities should be ignored or responded to with the unsupported =20
> capability message?
>
> Thanks,
> Sandeep Mudgal
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr



------_=_NextPart_001_01C8A4A8.6C8A6052
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.3">
<TITLE>RE: [Idr] BGP:  Vendor Specific Capabilities</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>So when you say &quot;ignore&quot;, does it mean that =
peer continues with the connection or drop the connection without =
sending any notification?<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: ext John G. Scudder [<A =
HREF=3D"mailto:jgs@bgp.nu">mailto:jgs@bgp.nu</A>]<BR>
Sent: Tue 4/22/2008 12:59 PM<BR>
To: Mudgal Sundeep (Nokia-S&amp;S/MtView)<BR>
Cc: idr@ietf.org<BR>
Subject: Re: [Idr] BGP:&nbsp; Vendor Specific Capabilities<BR>
<BR>
It should be ignored.&nbsp; Per RFC 3392, the unsupported =
capability&nbsp;<BR>
message is a way to complain if your peer doesn't support a =
capability&nbsp;<BR>
that you insist on having support for.&nbsp; An example would be if =
the&nbsp;<BR>
peer doesn't support MP-BGP and you are trying to establish a =
v6&nbsp;<BR>
peering.&nbsp; Here is the pertinent text from RFC 3392:<BR>
<BR>
&quot;If a BGP speaker that supports a certain capability determines =
that&nbsp;<BR>
its peer doesn't support this capability, the speaker MAY send =
a&nbsp;<BR>
NOTIFICATION message to the peer, and terminate peering (see =
Section&nbsp;<BR>
&quot;Extensions to Error Handling&quot; for more details). The Error =
Subcode in&nbsp;<BR>
the message is set to Unsupported Capability. The message =
SHOULD&nbsp;<BR>
contain the capability (capabilities) that causes the speaker to =
send&nbsp;<BR>
the message. The decision to send the message and terminate peering =
is&nbsp;<BR>
local to the speaker. If terminated, such peering SHOULD NOT be re-<BR>
established automatically.&quot;<BR>
<BR>
I apologize for the confusing name of the notification =
message.&nbsp;&nbsp;<BR>
Probably something like &quot;Required Capability Missing&quot; would =
have been&nbsp;<BR>
better. :-(<BR>
<BR>
Correct behavior with respect to any unknown capability from your =
peer&nbsp;<BR>
(whether vendor-specific or otherwise) is generally to ignore it.<BR>
<BR>
--John<BR>
<BR>
On Apr 22, 2008, at 11:35 AM, &lt;sundeep.mudgal@nokia.com&gt; =
&lt;sundeep.mudgal@nokia.com<BR>
&nbsp;&gt; wrote:<BR>
<BR>
&gt;<BR>
&gt; Hi,<BR>
&gt;<BR>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Could you please =
confirm whether vendor-specific&nbsp;<BR>
&gt; capabilities should be ignored or responded to with the =
unsupported&nbsp;<BR>
&gt; capability message?<BR>
&gt;<BR>
&gt; Thanks,<BR>
&gt; Sandeep Mudgal<BR>
&gt;<BR>
&gt; _______________________________________________<BR>
&gt; Idr mailing list<BR>
&gt; Idr@ietf.org<BR>
&gt; <A =
HREF=3D"https://www.ietf.org/mailman/listinfo/idr">https://www.ietf.org/m=
ailman/listinfo/idr</A><BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C8A4A8.6C8A6052--

--===============1399992116==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1399992116==--


From idr-bounces@ietf.org  Tue Apr 22 13:53:21 2008
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 A31DD3A6D39;
	Tue, 22 Apr 2008 13:53:21 -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 6EA063A6E4A
	for <idr@core3.amsl.com>; Tue, 22 Apr 2008 13:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 mlcWWHmOq2Xp for <idr@core3.amsl.com>;
	Tue, 22 Apr 2008 13:53:19 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id 0B06D3A6D39
	for <idr@ietf.org>; Tue, 22 Apr 2008 13:53:19 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id 9652353E1F4;
	Tue, 22 Apr 2008 16:25:11 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id TSzJ1NmdJM+5; Tue, 22 Apr 2008 16:25:05 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id 62CC353E003;
	Tue, 22 Apr 2008 16:25:04 -0400 (EDT)
Message-Id: <11DD8C70-3582-41F3-A197-2891924D8398@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: "sundeep.mudgal@nokia.com" <sundeep.mudgal@nokia.com>
In-Reply-To: <E5E76343C87BB34ABC6C3FDF3B31272756B0D4@daebe103.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 22 Apr 2008 16:25:02 -0400
References: <E5E76343C87BB34ABC6C3FDF3B31272702427B7B@daebe103.NOE.Nokia.com>
	<1BA6DC24-A122-4453-B0A8-D093DC54880F@bgp.nu>
	<E5E76343C87BB34ABC6C3FDF3B31272756B0D4@daebe103.NOE.Nokia.com>
X-Mailer: Apple Mail (2.919.2)
Cc: 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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Continue the connection.  In general one can think of the semantics of  
a BGP capability as being "I am able to do X" rather than "I insist on  
doing X".  If a pair of peers exchanges X, then that capability will  
typically be used.  If the peers do not exchange X, then it won't be.   
So, if your peer sends you X, and you don't support X, there's no  
problem.  You simply won't send X, so the peer won't attempt to use X  
on that peering.

--John

On Apr 22, 2008, at 2:39 PM, sundeep.mudgal@nokia.com wrote:

> So when you say "ignore", does it mean that peer continues with the  
> connection or drop the connection without sending any notification?
>
>
> -----Original Message-----
> From: ext John G. Scudder [mailto:jgs@bgp.nu]
> Sent: Tue 4/22/2008 12:59 PM
> To: Mudgal Sundeep (Nokia-S&S/MtView)
> Cc: idr@ietf.org
> Subject: Re: [Idr] BGP:  Vendor Specific Capabilities
>
> It should be ignored.  Per RFC 3392, the unsupported capability
> message is a way to complain if your peer doesn't support a capability
> that you insist on having support for.  An example would be if the
> peer doesn't support MP-BGP and you are trying to establish a v6
> peering.  Here is the pertinent text from RFC 3392:
>
> "If a BGP speaker that supports a certain capability determines that
> its peer doesn't support this capability, the speaker MAY send a
> NOTIFICATION message to the peer, and terminate peering (see Section
> "Extensions to Error Handling" for more details). The Error Subcode in
> the message is set to Unsupported Capability. The message SHOULD
> contain the capability (capabilities) that causes the speaker to send
> the message. The decision to send the message and terminate peering is
> local to the speaker. If terminated, such peering SHOULD NOT be re-
> established automatically."
>
> I apologize for the confusing name of the notification message.
> Probably something like "Required Capability Missing" would have been
> better. :-(
>
> Correct behavior with respect to any unknown capability from your peer
> (whether vendor-specific or otherwise) is generally to ignore it.
>
> --John
>
> On Apr 22, 2008, at 11:35 AM, <sundeep.mudgal@nokia.com> <sundeep.mudgal@nokia.com
>  > wrote:
>
> >
> > 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


From idr-bounces@ietf.org  Tue Apr 29 11:52:05 2008
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 786943A6D0B;
	Tue, 29 Apr 2008 11:52:05 -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 164DB3A6D0B
	for <idr@core3.amsl.com>; Tue, 29 Apr 2008 11:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5W83XFvQ-LFn for <idr@core3.amsl.com>;
	Tue, 29 Apr 2008 11:52:04 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id C858C3A6DD6
	for <idr@ietf.org>; Tue, 29 Apr 2008 11:51:33 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id 9BCB453E1B5
	for <idr@ietf.org>; Tue, 29 Apr 2008 14:51:36 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id 7AKowXBtDHgi for <idr@ietf.org>;
	Tue, 29 Apr 2008 14:51:19 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id E653F53E0FC
	for <idr@ietf.org>; Tue, 29 Apr 2008 14:51:18 -0400 (EDT)
Message-Id: <818DEA85-D9F0-4899-A057-D621C5DA31D0@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: idr <idr@ietf.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 29 Apr 2008 14:51:16 -0400
References: <20080429184121.CDDEA3A6CA9@core3.amsl.com>
X-Mailer: Apple Mail (2.919.2)
Subject: [Idr] Fwd: New Version Notification for
	draft-scudder-idr-rfc3392-bis-00
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Folks,

I've done some minor updates to the Capabilities Advertisement  
specification to address confusion about the "Unsupported Capability"  
NOTIFICATION message:

	Appendix B.  Comparison with RFC 3392
	
	   In addition to minor editorial changes, this document also clarifies
	   the use of the Unsupported Optional Parameter NOTIFICATION message,
	   and updates references to the base BGP-4 specification [RFC4271] and
	   security analysis [RFC4272].

The draft is at http://www.ietf.org/internet-drafts/draft-scudder-idr-rfc3392-bis-00.txt 
.

Comments welcome.  One thing that occurred to me was to rename  
"Unsupported Capability" to "Required Capability Missing", however  
that might do more harm than good by renaming an existing code point,  
so I didn't.

I'd like to propose this as a WG item (if indeed such a request is  
even required for an update to an existing WG document?).

Thanks,

--John

Begin forwarded message:

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: April 29, 2008 2:41:21 PM GMT-04:00
> To: jgs@juniper.net
> Cc: rchandra@sonoasystems.com
> Subject: New Version Notification for draft-scudder-idr-rfc3392-bis-00
>
>
> A new version of I-D, draft-scudder-idr-rfc3392-bis-00.txt has been  
> successfuly submitted by John Scudder and posted to the IETF  
> repository.
>
> Filename:	 draft-scudder-idr-rfc3392-bis
> Revision:	 00
> Title:		 Capabilities Advertisement with BGP-4
> Creation_date:	 2008-04-29
> WG ID:		 Independent Submission
> Number_of_pages: 7
>
> Abstract:
> This document defines an Optional Parameter, called Capabilities,
> that is expected to facilitate the introduction of new capabilities
> in the Border Gateway Protocol (BGP) by providing graceful capability
> advertisement without requiring that BGP peering be terminated.  This
> document obsoletes RFC 3392.
>
>
>
> The IETF Secretariat.
>
>

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


From idr-bounces@ietf.org  Tue Apr 29 11:59:07 2008
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 ACCF73A6B52;
	Tue, 29 Apr 2008 11:59:07 -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 4F8F23A69F3
	for <idr@core3.amsl.com>; Tue, 29 Apr 2008 11:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 91U9hCmPWlVm for <idr@core3.amsl.com>;
	Tue, 29 Apr 2008 11:59:00 -0700 (PDT)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.189])
	by core3.amsl.com (Postfix) with ESMTP id 1F7503A6B52
	for <idr@ietf.org>; Tue, 29 Apr 2008 11:58:59 -0700 (PDT)
Received: by ti-out-0910.google.com with SMTP id i7so51221tid.25
	for <idr@ietf.org>; Tue, 29 Apr 2008 11:59:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	bh=zy+3JlvYPdXv7oAXZ6X4RTUNwpnbRAZLgqgJ9Y/Q0PM=;
	b=YWSH0mFZ2NCL6wmBYzyP56RIhpJUfk0rid/ZHhSc/6RwyzWo9xC7Rbe8+cJQ26utSrZORuV5rnNC4Jc1amDWTPNjkpRs4t6WGdjsxFIvSdGp9uc3x89A2seBDGRzGFPFMpjN+qoS0TqoGDBPYSUKORKKBn8e0T17jiO8Cvtyi8c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=ddvX84YEz0fnB6lCGLBIt5nG8TBGz6sYsTyRyOs2Fhug/YdL0Rw7cseOOaeVkWejFkfruAcuYck9tTUYzhvbEHGXduCL2aECpNvGNWQ1k8I948gJlvfYVCbGVIHnxU2U3Vit3SDjO75U1nkKxCue6DXSg/t7DajWoviWGh14cKE=
Received: by 10.110.20.17 with SMTP id 17mr905081tit.48.1209495542603;
	Tue, 29 Apr 2008 11:59:02 -0700 (PDT)
Received: by 10.110.49.3 with HTTP; Tue, 29 Apr 2008 11:59:02 -0700 (PDT)
Message-ID: <8320074d0804291159i7409cdcbn61d9889564becd86@mail.gmail.com>
Date: Wed, 30 Apr 2008 00:29:02 +0530
From: "Rohan Sen" <senrohan@gmail.com>
To: idr@ietf.org
MIME-Version: 1.0
Subject: [Idr] BGP Next Hop attribute and MP_REACH_NLRI next hop field
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: multipart/mixed; boundary="===============0709888116=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

--===============0709888116==
Content-Type: multipart/alternative; 
	boundary="----=_Part_21743_23640306.1209495542608"

------=_Part_21743_23640306.1209495542608
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All,

For cases in BGP (like VPN) where MP_REACH_NLRI attribute is used to carry
route information in an Update message, we also specify the next hop for the
prefixes inside this attribute itself. But if we are sending IPv4 routes
inside MP_REACH_NLRI->NLRI field, and we also add the standard Next Hop path
attribute then will that carry any special meaning? My confusion is that
whether the NLRI path attribute can coexist with MP_REACH_NLRI attribute or
not. If yes, then in which scenario.

Any help in this regard would be highly appreciated.

-- 
thanks,
Rohan Sen

------=_Part_21743_23640306.1209495542608
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All,<br><br>For cases in BGP (like VPN) where MP_REACH_NLRI attribute is used to carry route information in an Update message, we also specify the next hop for the prefixes inside this attribute itself. But if we are sending IPv4 routes inside MP_REACH_NLRI-&gt;NLRI field, and we also add the standard Next Hop path attribute then will that carry any special meaning? My confusion is that whether the NLRI path attribute can coexist with MP_REACH_NLRI attribute or not. If yes, then in which scenario.<br>
<br>Any help in this regard would be highly appreciated.<br clear="all"><br>-- <br>thanks,<br>Rohan Sen

------=_Part_21743_23640306.1209495542608--

--===============0709888116==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0709888116==--


From idr-bounces@ietf.org  Tue Apr 29 12:24:31 2008
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 C9F0A28C281;
	Tue, 29 Apr 2008 12:24:31 -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 3DA0528C304
	for <idr@core3.amsl.com>; Tue, 29 Apr 2008 12:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 Dxe4QCdhTshG for <idr@core3.amsl.com>;
	Tue, 29 Apr 2008 12:24:29 -0700 (PDT)
Received: from mx.force10networks.com (corp.force10networks.com
	[64.186.164.204])
	by core3.amsl.com (Postfix) with ESMTP id 5A01C28C281
	for <idr@ietf.org>; Tue, 29 Apr 2008 12:24:29 -0700 (PDT)
Received: from mx.force10networks.com ([10.11.0.221]) by
	mx.force10networks.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 29 Apr 2008 12:22:47 -0700
Received: from exch7-sjc-fe.force10networks.com ([10.11.0.87]) by
	mx.force10networks.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 29 Apr 2008 12:22:47 -0700
Received: from EXCH-CLUSTER-09.force10networks.com ([10.11.10.113]) by
	exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi;
	Tue, 29 Apr 2008 12:22:47 -0700
From: Kalpesh Zinjuwadia <kzinjuwadia@force10networks.com>
To: 'Rohan Sen' <senrohan@gmail.com>, "idr@ietf.org" <idr@ietf.org>
Date: Tue, 29 Apr 2008 12:22:46 -0700
Thread-Topic: [Idr] BGP Next Hop attribute and MP_REACH_NLRI next hop field
Thread-Index: AciqKt/7NJPCFomLSCy7GIFWPfN5vwAAhlfg
Message-ID: <2EE638FFD18B294395AE688204CE7E6F1DFC1B53@EXCH-CLUSTER-09.force10networks.com>
References: <8320074d0804291159i7409cdcbn61d9889564becd86@mail.gmail.com>
In-Reply-To: <8320074d0804291159i7409cdcbn61d9889564becd86@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 29 Apr 2008 19:22:47.0008 (UTC)
	FILETIME=[67FF9600:01C8AA2E]
Subject: Re: [Idr] BGP Next Hop attribute and MP_REACH_NLRI next hop field
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: multipart/mixed; boundary="===============2122648051=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

--===============2122648051==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_2EE638FFD18B294395AE688204CE7E6F1DFC1B53EXCHCLUSTER09fo_"

--_000_2EE638FFD18B294395AE688204CE7E6F1DFC1B53EXCHCLUSTER09fo_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Does the update in your case have any ipv4-unicast NLRIs (outside the MP_RE=
ACH attr)?

Per RFC 2858 (sec 2; last para), if there are no NLRIs (except the ones in =
MP_REACH_NLRI) to be sent, Next-hop attribute should not be sent. Receiver =
should ignore Next-hop attribute, if received.

If MP_REACH_NLRI is carrying IPv4 routes, the Next-hop in this attribute it=
self should be used. Having the Next-hop path attribute should not change a=
nything for these routes.

Thanks,
Kalpesh

From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of Rohan=
 Sen
Sent: Tuesday, April 29, 2008 11:59 AM
To: idr@ietf.org
Subject: [Idr] BGP Next Hop attribute and MP_REACH_NLRI next hop field

Hi All,

For cases in BGP (like VPN) where MP_REACH_NLRI attribute is used to carry =
route information in an Update message, we also specify the next hop for th=
e prefixes inside this attribute itself. But if we are sending IPv4 routes =
inside MP_REACH_NLRI->NLRI field, and we also add the standard Next Hop pat=
h attribute then will that carry any special meaning? My confusion is that =
whether the NLRI path attribute can coexist with MP_REACH_NLRI attribute or=
 not. If yes, then in which scenario.

Any help in this regard would be highly appreciated.

--
thanks,
Rohan Sen

--_000_2EE638FFD18B294395AE688204CE7E6F1DFC1B53EXCHCLUSTER09fo_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Does the update in your case have any ipv4-unicast NLRIs
(outside the MP_REACH attr)?<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Per RFC 2858 (sec 2; last para), if there are no NLRIs (exce=
pt
the ones in MP_REACH_NLRI) to be sent, Next-hop attribute should not be sen=
t. Receiver
should ignore Next-hop attribute, if received.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>If MP_REACH_NLRI is carrying IPv4 routes, the Next-hop in th=
is
attribute itself should be used. Having the Next-hop path attribute should =
not
change anything for these routes.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Thanks,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Kalpesh<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] <b>On Behalf Of </b>Roha=
n
Sen<br>
<b>Sent:</b> Tuesday, April 29, 2008 11:59 AM<br>
<b>To:</b> idr@ietf.org<br>
<b>Subject:</b> [Idr] BGP Next Hop attribute and MP_REACH_NLRI next hop fie=
ld<o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Hi All,<br>
<br>
For cases in BGP (like VPN) where MP_REACH_NLRI attribute is used to carry
route information in an Update message, we also specify the next hop for th=
e
prefixes inside this attribute itself. But if we are sending IPv4 routes in=
side
MP_REACH_NLRI-&gt;NLRI field, and we also add the standard Next Hop path
attribute then will that carry any special meaning? My confusion is that
whether the NLRI path attribute can coexist with MP_REACH_NLRI attribute or
not. If yes, then in which scenario.<br>
<br>
Any help in this regard would be highly appreciated.<br clear=3Dall>
<br>
-- <br>
thanks,<br>
Rohan Sen <o:p></o:p></p>

</div>

</body>

</html>

--_000_2EE638FFD18B294395AE688204CE7E6F1DFC1B53EXCHCLUSTER09fo_--

--===============2122648051==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2122648051==--


From idr-bounces@ietf.org  Tue Apr 29 15:40:48 2008
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 CA4F63A6ABA;
	Tue, 29 Apr 2008 15:40:48 -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 9D8FE3A6983
	for <idr@core3.amsl.com>; Tue, 29 Apr 2008 15:40:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 K-xVij8FqK6o for <idr@core3.amsl.com>;
	Tue, 29 Apr 2008 15:40:43 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 3609F28C0FC
	for <idr@ietf.org>; Tue, 29 Apr 2008 15:40:43 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m3TMeuK9000683; Tue, 29 Apr 2008 17:43:14 -0500
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 30 Apr 2008 01:40:24 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 29 Apr 2008 17:40:22 -0500
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 29 Apr 2008 17:40:21 -0500
Message-ID: <E5E76343C87BB34ABC6C3FDF3B31272756B0E8@daebe103.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: [Idr] BGP:  Vendor Specific Capabilities
Thread-index: AciktvsgnnNwyMcISmq7UspAo7tTGAFju6VL
References: <E5E76343C87BB34ABC6C3FDF3B31272702427B7B@daebe103.NOE.Nokia.com>
	<1BA6DC24-A122-4453-B0A8-D093DC54880F@bgp.nu>
	<E5E76343C87BB34ABC6C3FDF3B31272756B0D4@daebe103.NOE.Nokia.com>
	<11DD8C70-3582-41F3-A197-2891924D8398@bgp.nu>
From: <sundeep.mudgal@nokia.com>
To: <jgs@bgp.nu>
X-OriginalArrivalTime: 29 Apr 2008 22:40:22.0412 (UTC)
	FILETIME=[025EACC0:01C8AA4A]
X-Nokia-AV: Clean
Cc: 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: multipart/mixed; boundary="===============1742512228=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1742512228==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8AA4A.01AACBDA"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AA4A.01AACBDA
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



  John,

       I have one more more doubt which needs clarification :

          In response to an open message with capabilities, a peer that =
supports no capabilities=20

                1) MUST send NOTIFICATION message with unsupported =
optional parameter.
                   =20
                                 OR

                 2) SHOULD send NOTIFICATION message with unsupported =
optional parameter.


        Say for example, as a BGP speaker X support some capability and =
its  peer Y has the basic implementation of BGP without any optional =
capabilities. So in that case:

             - Will the peer Y always (MUST) send NOTIFICATION message =
to the speaker X with unsupported optional parameter?=20

             - Or if a peer Y doesn't send any notification and closes =
the connection then should the speaker X send a new open message without =
any optional capabilities or should speaker X wait for the peer's open =
message and adjust accordingly?
                     =20

        I don't see this defined clearly in any of the RFCs which I have =
read. Could you please clarify this or point me to the section of RFC =
which states this?

thanks,
Sundeep


       =20


-----Original Message-----
From: ext John G. Scudder [mailto:jgs@bgp.nu]
Sent: Tue 4/22/2008 3:25 PM
To: Mudgal Sundeep (Nokia-S&S/MtView)
Cc: idr@ietf.org
Subject: Re: [Idr] BGP:  Vendor Specific Capabilities
=20
Continue the connection.  In general one can think of the semantics of =20
a BGP capability as being "I am able to do X" rather than "I insist on =20
doing X".  If a pair of peers exchanges X, then that capability will =20
typically be used.  If the peers do not exchange X, then it won't be.  =20
So, if your peer sends you X, and you don't support X, there's no =20
problem.  You simply won't send X, so the peer won't attempt to use X =20
on that peering.

--John

On Apr 22, 2008, at 2:39 PM, sundeep.mudgal@nokia.com wrote:

> So when you say "ignore", does it mean that peer continues with the =20
> connection or drop the connection without sending any notification?
>
>
> -----Original Message-----
> From: ext John G. Scudder [mailto:jgs@bgp.nu]
> Sent: Tue 4/22/2008 12:59 PM
> To: Mudgal Sundeep (Nokia-S&S/MtView)
> Cc: idr@ietf.org
> Subject: Re: [Idr] BGP:  Vendor Specific Capabilities
>
> It should be ignored.  Per RFC 3392, the unsupported capability
> message is a way to complain if your peer doesn't support a capability
> that you insist on having support for.  An example would be if the
> peer doesn't support MP-BGP and you are trying to establish a v6
> peering.  Here is the pertinent text from RFC 3392:
>
> "If a BGP speaker that supports a certain capability determines that
> its peer doesn't support this capability, the speaker MAY send a
> NOTIFICATION message to the peer, and terminate peering (see Section
> "Extensions to Error Handling" for more details). The Error Subcode in
> the message is set to Unsupported Capability. The message SHOULD
> contain the capability (capabilities) that causes the speaker to send
> the message. The decision to send the message and terminate peering is
> local to the speaker. If terminated, such peering SHOULD NOT be re-
> established automatically."
>
> I apologize for the confusing name of the notification message.
> Probably something like "Required Capability Missing" would have been
> better. :-(
>
> Correct behavior with respect to any unknown capability from your peer
> (whether vendor-specific or otherwise) is generally to ignore it.
>
> --John
>
> On Apr 22, 2008, at 11:35 AM, <sundeep.mudgal@nokia.com> =
<sundeep.mudgal@nokia.com
>  > wrote:
>
> >
> > 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
>
>



------_=_NextPart_001_01C8AA4A.01AACBDA
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.3">
<TITLE>RE: [Idr] BGP:  Vendor Specific Capabilities</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<BR>

<P><FONT SIZE=3D2>&nbsp; John,<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I have one more more doubt which =
needs clarification :<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In response to an =
open message with capabilities, a peer that supports no capabilities<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; 1) MUST send NOTIFICATION message with unsupported =
optional parameter.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OR<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; 2) SHOULD send NOTIFICATION message with =
unsupported optional parameter.<BR>
<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Say for example, as a BGP =
speaker X support some capability and its&nbsp; peer Y has the basic =
implementation of BGP without any optional capabilities. So in that =
case:<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- Will the peer Y always (MUST) send NOTIFICATION message to the speaker =
X with unsupported optional parameter?<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- Or if a peer Y doesn't send any notification and closes the connection =
then should the speaker X send a new open message without any optional =
capabilities or should speaker X wait for the peer's open message and =
adjust accordingly?<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I don't see this defined =
clearly in any of the RFCs which I have read. Could you please clarify =
this or point me to the section of RFC which states this?<BR>
<BR>
thanks,<BR>
Sundeep<BR>
<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: ext John G. Scudder [<A =
HREF=3D"mailto:jgs@bgp.nu">mailto:jgs@bgp.nu</A>]<BR>
Sent: Tue 4/22/2008 3:25 PM<BR>
To: Mudgal Sundeep (Nokia-S&amp;S/MtView)<BR>
Cc: idr@ietf.org<BR>
Subject: Re: [Idr] BGP:&nbsp; Vendor Specific Capabilities<BR>
<BR>
Continue the connection.&nbsp; In general one can think of the semantics =
of&nbsp;<BR>
a BGP capability as being &quot;I am able to do X&quot; rather than =
&quot;I insist on&nbsp;<BR>
doing X&quot;.&nbsp; If a pair of peers exchanges X, then that =
capability will&nbsp;<BR>
typically be used.&nbsp; If the peers do not exchange X, then it won't =
be.&nbsp;&nbsp;<BR>
So, if your peer sends you X, and you don't support X, there's =
no&nbsp;<BR>
problem.&nbsp; You simply won't send X, so the peer won't attempt to use =
X&nbsp;<BR>
on that peering.<BR>
<BR>
--John<BR>
<BR>
On Apr 22, 2008, at 2:39 PM, sundeep.mudgal@nokia.com wrote:<BR>
<BR>
&gt; So when you say &quot;ignore&quot;, does it mean that peer =
continues with the&nbsp;<BR>
&gt; connection or drop the connection without sending any =
notification?<BR>
&gt;<BR>
&gt;<BR>
&gt; -----Original Message-----<BR>
&gt; From: ext John G. Scudder [<A =
HREF=3D"mailto:jgs@bgp.nu">mailto:jgs@bgp.nu</A>]<BR>
&gt; Sent: Tue 4/22/2008 12:59 PM<BR>
&gt; To: Mudgal Sundeep (Nokia-S&amp;S/MtView)<BR>
&gt; Cc: idr@ietf.org<BR>
&gt; Subject: Re: [Idr] BGP:&nbsp; Vendor Specific Capabilities<BR>
&gt;<BR>
&gt; It should be ignored.&nbsp; Per RFC 3392, the unsupported =
capability<BR>
&gt; message is a way to complain if your peer doesn't support a =
capability<BR>
&gt; that you insist on having support for.&nbsp; An example would be if =
the<BR>
&gt; peer doesn't support MP-BGP and you are trying to establish a =
v6<BR>
&gt; peering.&nbsp; Here is the pertinent text from RFC 3392:<BR>
&gt;<BR>
&gt; &quot;If a BGP speaker that supports a certain capability =
determines that<BR>
&gt; its peer doesn't support this capability, the speaker MAY send =
a<BR>
&gt; NOTIFICATION message to the peer, and terminate peering (see =
Section<BR>
&gt; &quot;Extensions to Error Handling&quot; for more details). The =
Error Subcode in<BR>
&gt; the message is set to Unsupported Capability. The message =
SHOULD<BR>
&gt; contain the capability (capabilities) that causes the speaker to =
send<BR>
&gt; the message. The decision to send the message and terminate peering =
is<BR>
&gt; local to the speaker. If terminated, such peering SHOULD NOT be =
re-<BR>
&gt; established automatically.&quot;<BR>
&gt;<BR>
&gt; I apologize for the confusing name of the notification message.<BR>
&gt; Probably something like &quot;Required Capability Missing&quot; =
would have been<BR>
&gt; better. :-(<BR>
&gt;<BR>
&gt; Correct behavior with respect to any unknown capability from your =
peer<BR>
&gt; (whether vendor-specific or otherwise) is generally to ignore =
it.<BR>
&gt;<BR>
&gt; --John<BR>
&gt;<BR>
&gt; On Apr 22, 2008, at 11:35 AM, &lt;sundeep.mudgal@nokia.com&gt; =
&lt;sundeep.mudgal@nokia.com<BR>
&gt;&nbsp; &gt; wrote:<BR>
&gt;<BR>
&gt; &gt;<BR>
&gt; &gt; Hi,<BR>
&gt; &gt;<BR>
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Could you =
please confirm whether vendor-specific<BR>
&gt; &gt; capabilities should be ignored or responded to with the =
unsupported<BR>
&gt; &gt; capability message?<BR>
&gt; &gt;<BR>
&gt; &gt; Thanks,<BR>
&gt; &gt; Sandeep Mudgal<BR>
&gt; &gt;<BR>
&gt; &gt; _______________________________________________<BR>
&gt; &gt; Idr mailing list<BR>
&gt; &gt; Idr@ietf.org<BR>
&gt; &gt; <A =
HREF=3D"https://www.ietf.org/mailman/listinfo/idr">https://www.ietf.org/m=
ailman/listinfo/idr</A><BR>
&gt;<BR>
&gt;<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C8AA4A.01AACBDA--

--===============1742512228==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1742512228==--


From idr-bounces@ietf.org  Tue Apr 29 16:33:42 2008
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 E53FA3A6AF7;
	Tue, 29 Apr 2008 16:33:41 -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 51D9E3A6872
	for <idr@core3.amsl.com>; Tue, 29 Apr 2008 16:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 QY4Lmtnlqj9m for <idr@core3.amsl.com>;
	Tue, 29 Apr 2008 16:33:39 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id A08FE3A69B5
	for <idr@ietf.org>; Tue, 29 Apr 2008 16:33:39 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id ABD9C53E1AF;
	Tue, 29 Apr 2008 19:33:42 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id rFiB2ohyp1od; Tue, 29 Apr 2008 19:33:36 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id E9BBE53E0FC;
	Tue, 29 Apr 2008 19:33:35 -0400 (EDT)
Message-Id: <A0C7C7C2-38BE-4447-BE7C-250C9BC07174@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: <sundeep.mudgal@nokia.com>
In-Reply-To: <E5E76343C87BB34ABC6C3FDF3B31272756B0E8@daebe103.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 29 Apr 2008 19:33:34 -0400
References: <E5E76343C87BB34ABC6C3FDF3B31272702427B7B@daebe103.NOE.Nokia.com>
	<1BA6DC24-A122-4453-B0A8-D093DC54880F@bgp.nu>
	<E5E76343C87BB34ABC6C3FDF3B31272756B0D4@daebe103.NOE.Nokia.com>
	<11DD8C70-3582-41F3-A197-2891924D8398@bgp.nu>
	<E5E76343C87BB34ABC6C3FDF3B31272756B0E8@daebe103.NOE.Nokia.com>
X-Mailer: Apple Mail (2.919.2)
Cc: 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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Well this is an RFC 4271 question really.  You will find the answer in  
Section 6.2, OPEN Message Error Handling:

    If one of the Optional Parameters in the OPEN message is not
    recognized, then the Error Subcode MUST be set to Unsupported
    Optional Parameters.

So in answer to the first part of your question, that's a MUST.

Regarding what to do if the peer closes the connection without any  
indication of why (no NOTIFICATION) it's really up to you, but I would  
be disinclined to go through extensive gyrations trying to guess what  
the peer's problem is.

--John

On Apr 29, 2008, at 6:40 PM, <sundeep.mudgal@nokia.com> wrote:

>
>
>   John,
>
>        I have one more more doubt which needs clarification :
>
>           In response to an open message with capabilities, a peer  
> that supports no capabilities
>
>                 1) MUST send NOTIFICATION message with unsupported  
> optional parameter.
>
>                                  OR
>
>                  2) SHOULD send NOTIFICATION message with  
> unsupported optional parameter.
>
>
>         Say for example, as a BGP speaker X support some capability  
> and its  peer Y has the basic implementation of BGP without any  
> optional capabilities. So in that case:
>
>              - Will the peer Y always (MUST) send NOTIFICATION  
> message to the speaker X with unsupported optional parameter?
>
>              - Or if a peer Y doesn't send any notification and  
> closes the connection then should the speaker X send a new open  
> message without any optional capabilities or should speaker X wait  
> for the peer's open message and adjust accordingly?
>
>
>         I don't see this defined clearly in any of the RFCs which I  
> have read. Could you please clarify this or point me to the section  
> of RFC which states this?
>
> thanks,
> Sundeep
>
...
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Tue Apr 29 21:39:04 2008
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 B65F43A69CF;
	Tue, 29 Apr 2008 21:39:04 -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 DB71F3A69CF
	for <idr@core3.amsl.com>; Tue, 29 Apr 2008 21:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186, 
	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 RGqlNR5SmHOh for <idr@core3.amsl.com>;
	Tue, 29 Apr 2008 21:39:00 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id B57BB3A677E
	for <idr@ietf.org>; Tue, 29 Apr 2008 21:38:59 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id C04B1268494; Tue, 29 Apr 2008 22:39:02 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	for idr@ietf.org; Tue, 29 Apr 2008 22:39:02 -0600 (MDT)
	(envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=54121; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: idr idr <idr@ietf.org>
Content-Type: multipart/mixed; boundary=Apple-Mail-9--705107256
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 29 Apr 2008 22:38:46 -0600
References: <20080425213001.4EB133A69E7@core3.amsl.com>
X-Mailer: Apple Mail (2.919.2)
Subject: [Idr] Fwd: I-D ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


--Apple-Mail-9--705107256
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

	
Surprisingly, I don't recall seeing this draft discussed here yet.

In short, I think the is a really bad idea.  It's bad enough the route
reflection spec was changed from 1966 to 2796 to permit an RR
to reflect routes to a client even if they were learned from that
client - arguably, to enable an implementation optimization, but
for this to recommend a well-known community and further recommend
disabling RFC 1966 "suppression" on the RR if the BGP community
is present in order to save configuration overhead on the PEs is
going a bit overboard.

-danny


Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: April 25, 2008 3:30:01 PM MDT
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-pmohapat-idr-acceptown-community-01.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title		: BGP ACCEPT_OWN Well-known Community Attribute
> 	Author(s)	: J. Uttaro, P. Mohapatra, D. Smith, R. Raszuk, J. Scudder
> 	Filename	: draft-pmohapat-idr-acceptown-community-01.txt
> 	Pages		: 8
> 	Date		: 2008-4-25
> 	
> It may be useful for a BGP speaker in an autonomous system to receive
>   and accept its own advertised route from a route reflector with more
>   fine-grained route control. For example, the route reflector can
>   change certain attributes of a route as desired, and then re-
>   advertise it back to the originator. Though it is possible to  
> perform
>   such policy control directly at the originator, it may be
>   operationally cumbersome in a network with a large number of border
>   routers having complex BGP policies.
>
>   This draft defines a new and well-known BGP community value,
>   ACCEPT_OWN, that signals a BGP speaker to accept an UPDATE message
>   and process the associated routes even when the ORIGINATOR_ID or the
>   NEXT_HOP matches that of the receiving speaker.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-pmohapat-idr-acceptown-community-01.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.

--Apple-Mail-9--705107256
Content-Disposition: attachment;
	filename=mime-attachment
Content-Type: message/external-body;
	x-unix-mode=0666;
	name="mime-attachment"
Content-Transfer-Encoding: 7bit

Content-Type: text/plain<BR>Content-ID: &lt;2008-4-25141805.I-D@ietf.org&gt;<BR><BR>


--Apple-Mail-9--705107256
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


--Apple-Mail-9--705107256
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--Apple-Mail-9--705107256--


From idr-bounces@ietf.org  Wed Apr 30 02:26:42 2008
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 B025C28C3A0;
	Wed, 30 Apr 2008 02:26:42 -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 C7C2928C36B
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 02:26:41 -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 zMhtsxOl3lcQ for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 02:26:37 -0700 (PDT)
Received: from softy.ision.net (softy.ision.net [194.163.250.97])
	by core3.amsl.com (Postfix) with ESMTP id 3C2983A690E
	for <idr@ietf.org>; Wed, 30 Apr 2008 02:26:07 -0700 (PDT)
Received: from paul.de.easynet.net ([195.180.208.152]
	helo=paul.adoffice.de.easynet.net)
	by softy.ision.net with esmtp (Exim 4.50)
	id 1Jr8Zk-0007E6-7p; Wed, 30 Apr 2008 11:26:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 30 Apr 2008 11:26:08 +0200
Message-ID: <7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
In-Reply-To: <64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
Thread-Index: AciqfCRVickn4exISLyObOjsO0nbgQAJCx2w
References: <20080425213001.4EB133A69E7@core3.amsl.com>
	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
From: "Ilya Varlashkin" <Ilya.Varlashkin@de.easynet.net>
To: "Danny McPherson" <danny@tcb.net>,
	"idr idr" <idr@ietf.org>
Subject: Re: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

> -----Original Message-----
> From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On 
> Behalf Of Danny McPherson
> Sent: Wednesday, April 30, 2008 6:39 AM
> To: idr idr
> Subject: [Idr] Fwd: I-D 
> ACTION:draft-pmohapat-idr-acceptown-community-01.txt
> 
> 	
> Surprisingly, I don't recall seeing this draft discussed here yet.
> 
> In short, I think the is a really bad idea.  It's bad enough 
> the route reflection spec was changed from 1966 to 2796 to 
> permit an RR to reflect routes to a client even if they were 
> learned from that client - arguably, to enable an 
> implementation optimization, but for this to recommend a 
> well-known community and further recommend disabling RFC 1966 
> "suppression" on the RR if the BGP community is present in 
> order to save configuration overhead on the PEs is going a 
> bit overboard.
> 

I share Danny's view regarding this proposal. To me it seems like
ACCEPT_OWN doesn't add anything what is not possible today, while
potentially creates opportunities for new bugs in the heart of BGP route
handling both on RR and edge routers; as well as, from operational
prospective, undermining stable operations of the route reflector(s). 

Often operations of the core network and the edge are split between
different teams, and route reflectors are often operated by the core
team who needs to ensure that network runs fine as whole, once setup
RR's are usually left intact. ACCEPT_OWN implies that policies regarding
inter-VPN route import/export will shift from the edge to the core,
while still being operated by edge/access team. Due to misconfiguration
on RR during manipulation of inter-VPN policies, there will be risk to
affect routing stability of the whole network, which is bad idea.

Usually RR's do not have specific VPN's defined and just relay routes
based on generic BGP rules. ACCEPT_OWN will require RR to be aware at
least of some VPN's (many in fact, else it doesn't make sense). This
will require extra work on RR part, extra data structures, code, meaning
more opportunities for things to go wrong.

Next, it's quite possible that for the path optimisations BGP clients
will peer not only with RR, but also between themselves and
client-to-client reflection is disabled. This will break integrity of
the routing information within AS since RR will send modified updates
only to non-clients, while clients within the cluster will still have
original unmodified information about given prefix.

Last, same functionality as offered by ACCEPT_OWN is reasonably easy
implemented on PE via generic policies that are setup once VRF
provisioned. Complexity that is necessary to mark prefixes with
ACCEPT_OWN community is on par with complexity necessary to tag prefixes
with something else and use generic policies locally on PE. So at the
end of the day, moving policies to RR isn't magic bullet that will
eliminate need for any work on PE, and on the other hand efficient
generic policies can make PE configuration as easy as it would be done
on RR.

Kind regards,
iLya
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Wed Apr 30 06:36:13 2008
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 249FB28C3CA;
	Wed, 30 Apr 2008 06:36:13 -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 8A0B628C3C6
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 06:36:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 KBcWlVBzl45U for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 06:36:06 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173])
	by core3.amsl.com (Postfix) with ESMTP id 299A228C3B3
	for <idr@ietf.org>; Wed, 30 Apr 2008 06:36:03 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob110.postini.com
	([64.18.6.12]) with SMTP; Wed, 30 Apr 2008 06:34:48 PDT
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 30 Apr 2008 06:33:04 -0700
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m3UDX4x97759
	for <idr@ietf.org>; Wed, 30 Apr 2008 06:33:04 -0700 (PDT)
	(envelope-from yakov@juniper.net)
Message-Id: <200804301333.m3UDX4x97759@magenta.juniper.net>
To: idr@ietf.org
MIME-Version: 1.0
Content-ID: <28503.1209562384.1@juniper.net>
Date: Wed, 30 Apr 2008 06:33:04 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 30 Apr 2008 13:33:04.0119 (UTC)
	FILETIME=[B7A29070:01C8AAC6]
Subject: [Idr] Fwd: New Version Notification for
	draft-scudder-idr-rfc3392-bis-
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Folks,

There is a request (see attached) to accept draft-scudder-idr-rfc3392-bis
as an IDR WG item. Please send your comments to the list. The deadline
for comments is May 14.

Yakov.
------- Forwarded Message

Date:    Tue, 29 Apr 2008 14:51:16 -0400
From:    "John G. Scudder" <jgs@bgp.nu>
To:      idr <idr@ietf.org>
Subject: [Idr] Fwd: New Version Notification for draft-scudder-idr-rfc3392-bis-
	  00

Folks,

I've done some minor updates to the Capabilities Advertisement  
specification to address confusion about the "Unsupported Capability"  
NOTIFICATION message:

	Appendix B.  Comparison with RFC 3392
	
	   In addition to minor editorial changes, this document also clarifies
	   the use of the Unsupported Optional Parameter NOTIFICATION message,
	   and updates references to the base BGP-4 specification [RFC4271] and
	   security analysis [RFC4272].

The draft is at http://www.ietf.org/internet-drafts/draft-scudder-idr-rfc3392-b
is-00.txt 
.

Comments welcome.  One thing that occurred to me was to rename  
"Unsupported Capability" to "Required Capability Missing", however  
that might do more harm than good by renaming an existing code point,  
so I didn't.

I'd like to propose this as a WG item (if indeed such a request is  
even required for an update to an existing WG document?).

Thanks,

- --John

Begin forwarded message:

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: April 29, 2008 2:41:21 PM GMT-04:00
> To: jgs@juniper.net
> Cc: rchandra@sonoasystems.com
> Subject: New Version Notification for draft-scudder-idr-rfc3392-bis-00
>
>
> A new version of I-D, draft-scudder-idr-rfc3392-bis-00.txt has been  
> successfuly submitted by John Scudder and posted to the IETF  
> repository.
>
> Filename:	 draft-scudder-idr-rfc3392-bis
> Revision:	 00
> Title:		 Capabilities Advertisement with BGP-4
> Creation_date:	 2008-04-29
> WG ID:		 Independent Submission
> Number_of_pages: 7
>
> Abstract:
> This document defines an Optional Parameter, called Capabilities,
> that is expected to facilitate the introduction of new capabilities
> in the Border Gateway Protocol (BGP) by providing graceful capability
> advertisement without requiring that BGP peering be terminated.  This
> document obsoletes RFC 3392.
>
>
>
> The IETF Secretariat.
>
>

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

------- End of Forwarded Message

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


From idr-bounces@ietf.org  Wed Apr 30 07:02:53 2008
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 805AA3A6B46;
	Wed, 30 Apr 2008 07:02:53 -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 8D7273A6A71
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 07:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149, 
	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 nVi4zrqQ8Ym3 for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 07:02:50 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id B15B83A6BE4
	for <idr@ietf.org>; Wed, 30 Apr 2008 07:02:49 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id AD182268494; Wed, 30 Apr 2008 08:02:52 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 30 Apr 2008 08:02:52 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=55539; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <0B82A4F5-4D76-427B-8CB3-386C0F6A64F2@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: Yakov Rekhter <yakov@juniper.net>
In-Reply-To: <200804301333.m3UDX4x97759@magenta.juniper.net>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 08:02:37 -0600
References: <200804301333.m3UDX4x97759@magenta.juniper.net>
X-Mailer: Apple Mail (2.919.2)
Cc: idr@ietf.org
Subject: Re: [Idr] Fwd: New Version Notification for
	draft-scudder-idr-rfc3392-bis-
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


On Apr 30, 2008, at 7:33 AM, Yakov Rekhter wrote:

> Folks,
>
> There is a request (see attached) to accept draft-scudder-idr- 
> rfc3392-bis
> as an IDR WG item. Please send your comments to the list. The deadline
> for comments is May 14.

I support this as an IDR WG item.

One minor comment..   I think we should rename "Unsupported Capability"
to "Required Capability Missing", and given that the codepoint itself  
isn't
changing, just the descriptor, there should be no issues here.

-danny


>
>
> Yakov.
> ------- Forwarded Message
>
> Date:    Tue, 29 Apr 2008 14:51:16 -0400
> From:    "John G. Scudder" <jgs@bgp.nu>
> To:      idr <idr@ietf.org>
> Subject: [Idr] Fwd: New Version Notification for draft-scudder-idr- 
> rfc3392-bis-
> 	  00
>
> Folks,
>
> I've done some minor updates to the Capabilities Advertisement
> specification to address confusion about the "Unsupported Capability"
> NOTIFICATION message:
>
> 	Appendix B.  Comparison with RFC 3392
> 	
> 	   In addition to minor editorial changes, this document also  
> clarifies
> 	   the use of the Unsupported Optional Parameter NOTIFICATION  
> message,
> 	   and updates references to the base BGP-4 specification [RFC4271]  
> and
> 	   security analysis [RFC4272].
>
> The draft is at http://www.ietf.org/internet-drafts/draft-scudder-idr-rfc3392-b
> is-00.txt
> .
>
> Comments welcome.  One thing that occurred to me was to rename
> "Unsupported Capability" to "Required Capability Missing", however
> that might do more harm than good by renaming an existing code point,
> so I didn't.
>
> I'd like to propose this as a WG item (if indeed such a request is
> even required for an update to an existing WG document?).
>
> Thanks,
>
> - --John
>
> Begin forwarded message:
>
>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>> Date: April 29, 2008 2:41:21 PM GMT-04:00
>> To: jgs@juniper.net
>> Cc: rchandra@sonoasystems.com
>> Subject: New Version Notification for draft-scudder-idr-rfc3392- 
>> bis-00
>>
>>
>> A new version of I-D, draft-scudder-idr-rfc3392-bis-00.txt has been
>> successfuly submitted by John Scudder and posted to the IETF
>> repository.
>>
>> Filename:	 draft-scudder-idr-rfc3392-bis
>> Revision:	 00
>> Title:		 Capabilities Advertisement with BGP-4
>> Creation_date:	 2008-04-29
>> WG ID:		 Independent Submission
>> Number_of_pages: 7
>>
>> Abstract:
>> This document defines an Optional Parameter, called Capabilities,
>> that is expected to facilitate the introduction of new capabilities
>> in the Border Gateway Protocol (BGP) by providing graceful capability
>> advertisement without requiring that BGP peering be terminated.  This
>> document obsoletes RFC 3392.
>>
>>
>>
>> The IETF Secretariat.
>>
>>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
> ------- End of Forwarded Message
>
> _______________________________________________
> 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


From idr-bounces@ietf.org  Wed Apr 30 08:30:17 2008
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 6EF1A28C3A2;
	Wed, 30 Apr 2008 08:30:17 -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 D2A4E28C3D9
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 08:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 AQjLk0siQMx7 for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 08:30:09 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id CEFE928C3D3
	for <idr@ietf.org>; Wed, 30 Apr 2008 08:30:08 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id B762153E1F4;
	Wed, 30 Apr 2008 11:30:11 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id fXZFZJI0zhyZ; Wed, 30 Apr 2008 11:30:03 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id C5C5353E0FC;
	Wed, 30 Apr 2008 11:30:02 -0400 (EDT)
Message-Id: <DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: Ilya Varlashkin <Ilya.Varlashkin@de.easynet.net>,
	Danny McPherson <danny@tcb.net>
In-Reply-To: <7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 11:30:01 -0400
References: <20080425213001.4EB133A69E7@core3.amsl.com>
	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
X-Mailer: Apple Mail (2.919.2)
Cc: idr <idr@ietf.org>
Subject: Re: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Danny:

I get that you have a bad feeling about the idea.  Can you provide  
some specifics, though?  As far as I can tell, the proposed extension  
is safe (for the same value of "safe" as the rest of the  
protocol...).  See also my comments below regarding defaulting it off.

Ilya:

The main point of your comments seems to be "I would never configure  
my network that way".  You also make some assumptions about the  
organizational structure of the network operator.  Of course, nobody  
would ever try to force you to adopt this model.  The question is why  
you think others shouldn't be allowed to configure their networks that  
way.

With regard to some of your other points, I think the proposed feature  
should be only be enabled if configured, i.e. the default should be  
the current behavior.  The draft should be updated to say this  
explicitly.  As long as it defaults to off, usage of the feature  
becomes a "consenting adults" thing.  As for your observations  
regarding specific deployments (e.g., disabled client-to-client  
reflection) I think it's reasonable to ask that the network operator  
know what they're doing before enabling the feature and will avoid  
using configurations which are broken!  This is no different than the  
situation today, since the possibility to configure the protocol in  
broken ways has always existed, nor is it unique to BGP.

Finally, I don't agree with this point:

> Usually RR's do not have specific VPN's defined and just relay routes
> based on generic BGP rules. ACCEPT_OWN will require RR to be aware at
> least of some VPN's (many in fact, else it doesn't make sense). This
> will require extra work on RR part, extra data structures, code,  
> meaning
> more opportunities for things to go wrong.

In fact, very little new RR code would be required to take advantage  
of the feature.  The RR needs to be able to match on an RT, add an RT,  
and add the well-known community.  Matching and adding RTs (which are  
just extended communities) and adding other communities is existing  
functionality.  This requires additional configuration, but little or  
no new code.

Regards,

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


From idr-bounces@ietf.org  Wed Apr 30 08:54:45 2008
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 D61643A6B1B;
	Wed, 30 Apr 2008 08:54:45 -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 D2C443A6DE3
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 08:54:44 -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 nWbEVx4hGl5e for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 08:54:44 -0700 (PDT)
Received: from softy.ision.net (softy.ision.net [194.163.250.97])
	by core3.amsl.com (Postfix) with ESMTP id A041D3A699C
	for <idr@ietf.org>; Wed, 30 Apr 2008 08:54:43 -0700 (PDT)
Received: from paul.de.easynet.net ([195.180.208.152]
	helo=paul.adoffice.de.easynet.net)
	by softy.ision.net with esmtp (Exim 4.50)
	id 1JrEdo-0001zC-Ni; Wed, 30 Apr 2008 17:54:44 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 30 Apr 2008 17:54:44 +0200
Message-ID: <7000E71D8C525042A815432358B2F1240138D465@paul.adoffice.local.de.easynet.net>
In-Reply-To: <DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
Thread-Index: Aciq1xhWgztVONHoTbi+2B249jaQOgAAVTSQ
References: <20080425213001.4EB133A69E7@core3.amsl.com>
	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
From: "Ilya Varlashkin" <Ilya.Varlashkin@de.easynet.net>
To: "John G. Scudder" <jgs@bgp.nu>,
	"Danny McPherson" <danny@tcb.net>
Cc: idr <idr@ietf.org>
Subject: Re: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

John, 

> -----Original Message-----
> would ever try to force you to adopt this model.  The 
> question is why  
> you think others shouldn't be allowed to configure their 
> networks that  
> way.
> 

I do not worry that someone will force me, nor do I want to tell others
how to configure and operate their network. But adding this specific
functionality will require changes in one of the core BGP parts. 

> With regard to some of your other points, I think the 
> proposed feature  
> should be only be enabled if configured, i.e. the default should be  
> the current behavior.  The draft should be updated to say this  
> explicitly.  As long as it defaults to off, usage of the feature  
> becomes a "consenting adults" thing.  As for your observations  

Even if this feature is off by default, it's still addition of the new
code to the core part of BGP. So there is risk that things will go wrong
with implementing the code (I do not worry about enabling feature since
I don't have to enable it) and this may destabilise current BGP
functionality. Since hardly any vendor will ship two versions of
router's software - one with and one without new code, it's obvious that
one day even networks that don't need this functionality will have to
become field testers of the new BGP code, and this is exactly part I
worry about.

> In fact, very little new RR code would be required to take advantage  
> of the feature.  The RR needs to be able to match on an RT, 

Ok I see you point for this one.

Kind regards,
iLya
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Wed Apr 30 09:07:02 2008
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 E53563A6E94;
	Wed, 30 Apr 2008 09:07:01 -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 58CCC3A6C99
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 09:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level: 
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124, 
	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 9tN+bSeDrppU for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 09:06:59 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 05AAA3A6A25
	for <idr@ietf.org>; Wed, 30 Apr 2008 09:06:53 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id C54AB268494; Wed, 30 Apr 2008 10:06:56 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 30 Apr 2008 10:06:56 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=55699; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: John G. Scudder <jgs@bgp.nu>
In-Reply-To: <DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 10:06:41 -0600
References: <20080425213001.4EB133A69E7@core3.amsl.com>
	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


On Apr 30, 2008, at 9:30 AM, John G. Scudder wrote:

> Danny:
>
> I get that you have a bad feeling about the idea.  Can you provide
> some specifics, though?  As far as I can tell, the proposed extension
> is safe (for the same value of "safe" as the rest of the
> protocol...).  See also my comments below regarding defaulting it off.

Take, for example, the case where the client doesn't know how
to handle the new community and some routing information loop
results.

I saw this occur in a real network when vendor 'n' changed their
RR behavior to that of 2796 and reflected routes back to clients
while the clients, vendor 'm', didn't know they were supposed to
drop the routes.

Additional configuration would be required to avoid the above,
and even more care would now be required to setup congruent
or overlay BGP topologies - while localized configuration is what
you're trying to avoid on the PEs in the application provided.

I suspect there are other scenarios where this could occur,
in particular if hierarchal RRs are used, etc..,

> With regard to some of your other points, I think the proposed feature
> should be only be enabled if configured, i.e. the default should be
> the current behavior.  The draft should be updated to say this
> explicitly.  As long as it defaults to off, usage of the feature
> becomes a "consenting adults" thing.  As for your observations
> regarding specific deployments (e.g., disabled client-to-client
> reflection) I think it's reasonable to ask that the network operator
> know what they're doing before enabling the feature and will avoid
> using configurations which are broken!  This is no different than the
> situation today, since the possibility to configure the protocol in
> broken ways has always existed, nor is it unique to BGP.
>
> Finally, I don't agree with this point:
>
>> Usually RR's do not have specific VPN's defined and just relay routes
>> based on generic BGP rules. ACCEPT_OWN will require RR to be aware at
>> least of some VPN's (many in fact, else it doesn't make sense). This
>> will require extra work on RR part, extra data structures, code,
>> meaning
>> more opportunities for things to go wrong.
>
> In fact, very little new RR code would be required to take advantage
> of the feature.  The RR needs to be able to match on an RT, add an RT,
> and add the well-known community.  Matching and adding RTs (which are
> just extended communities) and adding other communities is existing
> functionality.  This requires additional configuration, but little or
> no new code.

Right, it's the client that needs most of the code..  Of course,
more than likely, the clients and the RRs will be on the same
code base - unless there are address family overlays constructed,
and then we're adding one more variable to the mis-configuration
opportunity mix, when some clients are older and can't support
newer code, then I've got a mix of topology and behavior types
that didn't previously exist.

How much configuration overhead is actually being saved
on the PEs that justifies changing basic BGP specification
behavior and introducing even more redundant network
state?

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


From idr-bounces@ietf.org  Wed Apr 30 10:29:16 2008
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 3ABF53A69C9;
	Wed, 30 Apr 2008 10:29:16 -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 4F73C3A680C
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 10:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ukyMjS6bk--D for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 10:29:13 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 8E55E3A6849
	for <idr@ietf.org>; Wed, 30 Apr 2008 10:29:13 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 30 Apr 2008 10:29:16 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m3UHTGq1003985; 
	Wed, 30 Apr 2008 10:29:16 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m3UHTGsD013508;
	Wed, 30 Apr 2008 17:29:16 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 10:29:15 -0700
Received: from [10.21.69.88] ([10.21.69.88]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 10:29:15 -0700
Message-ID: <4818ACAF.6000306@cisco.com>
Date: Wed, 30 Apr 2008 10:30:23 -0700
From: Enke Chen <enkechen@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Yakov Rekhter <yakov@juniper.net>
References: <200804301333.m3UDX4x97759@magenta.juniper.net>
In-Reply-To: <200804301333.m3UDX4x97759@magenta.juniper.net>
X-OriginalArrivalTime: 30 Apr 2008 17:29:15.0369 (UTC)
	FILETIME=[B65BB590:01C8AAE7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3747; t=1209576556;
	x=1210440556; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=enkechen@cisco.com;
	z=From:=20Enke=20Chen=20<enkechen@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20Fwd=3A=20New=20Version=20Notifi
	cation=20for=09draft-scudder-idr-rfc3392-bis- |Sender:=20;
	bh=DAoe0ca1d1R+KDgoiGTONe/EXkU+MrZLJwn75HH0bq0=;
	b=uJAWlUqXtEr1Sci1bGiKv9i6J/i3rPFGHOYXYvnJPQrY7GYO/G5H1RT5qA
	b98nw72Z3yvr8XLkwYsiSvec5xbTzSCET6T1+K/4TDN2xaxSpeNKf5JN6zg8
	iNwVKXkf2kBP82wEwnP/dH9n74LGXHv9kE/wzUNhXchWlJ5y1FzA8=;
Authentication-Results: sj-dkim-1; header.From=enkechen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: idr@ietf.org
Subject: Re: [Idr] Fwd: New Version Notification
	for	draft-scudder-idr-rfc3392-bis-
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi, folks:

While we are at it, I suggest that we also clarify on the encoding of 
the capabilities.  Currently there exist two encodings for capabilities 
in the "Optional Parameters" field of the OPEN message, and both are 
deployed:

(1) List the capabilities in one "optional parameter":

      Parm. Type - capability
      Parm. Length
      cap_1, cap_1_len, cap_1_value
      ...
      cap_n, cap_n_len, cap_n_value

(2) List the capabilities in multiple "optional parameters":

      Parm. Type - capability
      Parm. Length
      cap_1, cap_1_len, cap_1_value
      ...
      Parm. Type - capability
      Parm. Length
      cap_n, cap_n_len, cap_n_value

Ideally #1 is more correct for TLV encoding.  But we started with #2 :-(

I suggest that we add some text in the document to point out their 
existence and state that both types MUST be accepted.

Thanks.   -- Enke

Yakov Rekhter wrote:
> Folks,
>
> There is a request (see attached) to accept draft-scudder-idr-rfc3392-bis
> as an IDR WG item. Please send your comments to the list. The deadline
> for comments is May 14.
>
> Yakov.
> ------- Forwarded Message
>
> Date:    Tue, 29 Apr 2008 14:51:16 -0400
> From:    "John G. Scudder" <jgs@bgp.nu>
> To:      idr <idr@ietf.org>
> Subject: [Idr] Fwd: New Version Notification for draft-scudder-idr-rfc3392-bis-
> 	  00
>
> Folks,
>
> I've done some minor updates to the Capabilities Advertisement  
> specification to address confusion about the "Unsupported Capability"  
> NOTIFICATION message:
>
> 	Appendix B.  Comparison with RFC 3392
> 	
> 	   In addition to minor editorial changes, this document also clarifies
> 	   the use of the Unsupported Optional Parameter NOTIFICATION message,
> 	   and updates references to the base BGP-4 specification [RFC4271] and
> 	   security analysis [RFC4272].
>
> The draft is at http://www.ietf.org/internet-drafts/draft-scudder-idr-rfc3392-b
> is-00.txt 
> .
>
> Comments welcome.  One thing that occurred to me was to rename  
> "Unsupported Capability" to "Required Capability Missing", however  
> that might do more harm than good by renaming an existing code point,  
> so I didn't.
>
> I'd like to propose this as a WG item (if indeed such a request is  
> even required for an update to an existing WG document?).
>
> Thanks,
>
> - --John
>
> Begin forwarded message:
>
>   
>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>> Date: April 29, 2008 2:41:21 PM GMT-04:00
>> To: jgs@juniper.net
>> Cc: rchandra@sonoasystems.com
>> Subject: New Version Notification for draft-scudder-idr-rfc3392-bis-00
>>
>>
>> A new version of I-D, draft-scudder-idr-rfc3392-bis-00.txt has been  
>> successfuly submitted by John Scudder and posted to the IETF  
>> repository.
>>
>> Filename:	 draft-scudder-idr-rfc3392-bis
>> Revision:	 00
>> Title:		 Capabilities Advertisement with BGP-4
>> Creation_date:	 2008-04-29
>> WG ID:		 Independent Submission
>> Number_of_pages: 7
>>
>> Abstract:
>> This document defines an Optional Parameter, called Capabilities,
>> that is expected to facilitate the introduction of new capabilities
>> in the Border Gateway Protocol (BGP) by providing graceful capability
>> advertisement without requiring that BGP peering be terminated.  This
>> document obsoletes RFC 3392.
>>
>>
>>
>> The IETF Secretariat.
>>
>>
>>     
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
> ------- End of Forwarded Message
>
> _______________________________________________
> 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


From idr-bounces@ietf.org  Wed Apr 30 10:48:17 2008
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 1B1D23A6DD9;
	Wed, 30 Apr 2008 10:48:17 -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 9C3AF3A6DD9
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 10:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 LBG9-jFwvIgz for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 10:48:13 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id 430673A6DB0
	for <idr@ietf.org>; Wed, 30 Apr 2008 10:46:07 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id F243253E1AF;
	Wed, 30 Apr 2008 13:46:09 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id nobvvzrdvA9B; Wed, 30 Apr 2008 13:45:55 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id CAA2653E0FC;
	Wed, 30 Apr 2008 13:45:54 -0400 (EDT)
Message-Id: <014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: Danny McPherson <danny@tcb.net>
In-Reply-To: <39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 13:45:53 -0400
References: <20080425213001.4EB133A69E7@core3.amsl.com>
	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On Apr 30, 2008, at 12:06 PM, Danny McPherson wrote:
> Take, for example, the case where the client doesn't know how
> to handle the new community and some routing information loop
> results.

The nice thing is that the feature is backward compatible and fails  
safe -- if the client doesn't know how to handle the community, then  
it sees itself in the ORIGINATOR_ID and drops the route.  No route, no  
routing information loop.  Granted the behavior of dropping the route  
is undesired, but not horrible.

> I saw this occur in a real network when vendor 'n' changed their
> RR behavior to that of 2796 and reflected routes back to clients
> while the clients, vendor 'm', didn't know they were supposed to
> drop the routes.

Interesting -- one would have expected the vendor 'm' router to drop  
the routes even if it didn't understand ORIGINATOR_ID, due to the  
NEXT_HOP check.  I guess if the NEXT_HOP were getting rewritten...

But in any event this particular case is academic because of the "fail  
safe" behavior discussed above -- any client that interoperates with a  
2796 RR will fail safe.  (Any client that doesn't interoperate with a  
2796 RR is arguably pretty broken at this point.)

> How much configuration overhead is actually being saved
> on the PEs that justifies changing basic BGP specification
> behavior

One of my co-authors may want to address this point.  From my PoV,  
suffice it to say there's real demand for the feature.

> and introducing even more redundant network
> state?

What is the redundant network state you're referring to?  The "address  
family overlays" I snipped out of the quote?  Something else?

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


From idr-bounces@ietf.org  Wed Apr 30 13:12:32 2008
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 9531F3A69C9;
	Wed, 30 Apr 2008 13:12:32 -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 D19F93A6A53
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 13:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level: 
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106, 
	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 L7emSFdURl5e for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 13:12:31 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id E6C8D3A69C9
	for <idr@ietf.org>; Wed, 30 Apr 2008 13:12:30 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id B86672684A6; Wed, 30 Apr 2008 14:12:33 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 30 Apr 2008 14:12:33 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=56682; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: John G. Scudder <jgs@bgp.nu>
In-Reply-To: <014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 14:12:18 -0600
References: <20080425213001.4EB133A69E7@core3.amsl.com>
	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>
	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


On Apr 30, 2008, at 11:45 AM, John G. Scudder wrote:
> The nice thing is that the feature is backward compatible and fails
> safe -- if the client doesn't know how to handle the community, then
> it sees itself in the ORIGINATOR_ID and drops the route.  No route, no
> routing information loop.  Granted the behavior of dropping the route
> is undesired, but not horrible.

Even your draft disagrees with this, else it wouldn't mention
the disabling RFC 1966 behavior (as opposed to the discard
based on ORIGINATOR_ID on the client that RFC 2796
introduced -  for no valid _protocol reason, mind you, which
annoys me considerably).  Along this vein, I would be quite
interested in someone providing an explanation of why this
behavior was changed from 1966 to 2796....

> Interesting -- one would have expected the vendor 'm' router to drop
> the routes even if it didn't understand ORIGINATOR_ID, due to the
> NEXT_HOP check.  I guess if the NEXT_HOP were getting rewritten...
>
> But in any event this particular case is academic because of the "fail
> safe" behavior discussed above -- any client that interoperates with a
> 2796 RR will fail safe.  (Any client that doesn't interoperate with a
> 2796 RR is arguably pretty broken at this point.)

Right, but see my point above...  This assumes all clients employ
the discard behavior of 2796.

> One of my co-authors may want to address this point.  From my PoV,
> suffice it to say there's real demand for the feature.

I'm sure there is demand to make 2547 configuration simpler, but
that doesn't mean it's something we should change fundamental
BGP behavior to facilitate.  I would be interested in here from your
co-authors..

> What is the redundant network state you're referring to?  The "address
> family overlays" I snipped out of the quote?

No, I've come to accept the AF overlays..   What troubles me is the fact
that we're using BGP to enable a RR to modify an update learned from
a client, and to reflect that update back to that client - just does  
seem
good routing protocol hygiene to me, to save configuration overhead
on the client, when it'll surely be further required on the RRs.

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


From idr-bounces@ietf.org  Wed Apr 30 13:37:08 2008
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 2871D28C359;
	Wed, 30 Apr 2008 13:37:08 -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 C438F3A68AF
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 13:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 UEVSaAa6UKoK for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 13:37:05 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 410243A696A
	for <idr@ietf.org>; Wed, 30 Apr 2008 13:36:33 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 30 Apr 2008 13:36:36 -0700
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m3UKaaEo014730; 
	Wed, 30 Apr 2008 13:36:36 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m3UKaahh014516;
	Wed, 30 Apr 2008 20:36:36 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 13:36:35 -0700
Received: from [10.21.69.88] ([10.21.69.88]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 13:36:35 -0700
Message-ID: <4818D897.3070804@cisco.com>
Date: Wed, 30 Apr 2008 13:37:43 -0700
From: Enke Chen <enkechen@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Danny McPherson <danny@tcb.net>
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
	<4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
In-Reply-To: <4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
X-OriginalArrivalTime: 30 Apr 2008 20:36:35.0605 (UTC)
	FILETIME=[E20F9C50:01C8AB01]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1407; t=1209587796;
	x=1210451796; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=enkechen@cisco.com;
	z=From:=20Enke=20Chen=20<enkechen@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20Fwd=3A=20I-D=09ACTION=3Adraft-p
	mohapat-idr-acceptown-community-01.txt |Sender:=20;
	bh=fj4r73IhphLbKuprYTl4DKGs2Im2yHEcLS+AlqCbK04=;
	b=te7mI6YU+oe+1pnI5Cym1RtKz/zWRzjw1kSaEe2VCJa/PjGV6a3HM5suJC
	d3jh+ZOrzDC7pPm9+XvVp92ZKlYroxSIi7G/0FcJKxMoKEGY9hKaU2oTeV5R
	nb4xieUCNi;
Authentication-Results: sj-dkim-4; header.From=enkechen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd:
	I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi, Danny:

Regarding the specific change from 1966 to RFC 2796 that you mentioned, 
the reason was to make the spec. be consistent with the deployment 
(which has the behavior since Day 1 of the RR era).   AFAIK, there is 
nothing unusual about it in the iterative process for a protocol, and it 
is not alone. Take RFC 4271 as an example, one of the changes is the 
following:

     UPDATE Message Error subcode 7 (AS Routing Loop) has been deprecated.


The change reflects deployment and allows for implementation flexibility.

-- Enke

Danny McPherson wrote:
> On Apr 30, 2008, at 11:45 AM, John G. Scudder wrote:
>   
>> The nice thing is that the feature is backward compatible and fails
>> safe -- if the client doesn't know how to handle the community, then
>> it sees itself in the ORIGINATOR_ID and drops the route.  No route, no
>> routing information loop.  Granted the behavior of dropping the route
>> is undesired, but not horrible.
>>     
>
> Even your draft disagrees with this, else it wouldn't mention
> the disabling RFC 1966 behavior (as opposed to the discard
> based on ORIGINATOR_ID on the client that RFC 2796
> introduced -  for no valid _protocol reason, mind you, which
> annoys me considerably).  Along this vein, I would be quite
> interested in someone providing an explanation of why this
> behavior was changed from 1966 to 2796....
>   
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr


From idr-bounces@ietf.org  Wed Apr 30 13:40:20 2008
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 87EF43A696A;
	Wed, 30 Apr 2008 13:40:20 -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 96B683A696A
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 13:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093, 
	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 jEaNZ34QztcJ for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 13:40:18 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id CE8543A68AF
	for <idr@ietf.org>; Wed, 30 Apr 2008 13:40:18 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id AC0F82680D7; Wed, 30 Apr 2008 14:40:21 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 30 Apr 2008 14:40:21 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=56717; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: Enke Chen <enkechen@cisco.com>
In-Reply-To: <4818D897.3070804@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 14:40:05 -0600
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
	<4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
	<4818D897.3070804@cisco.com>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd:
	I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


On Apr 30, 2008, at 2:37 PM, Enke Chen wrote:

> Hi, Danny:
>
> Regarding the specific change from 1966 to RFC 2796 that you  
> mentioned, the reason was to make the spec. be consistent with the  
> deployment (which has the behavior since Day 1 of the RR era).

Not all implementations, else I'd have not seen conflicts ~10
years ago between two of the most prominent implementations.

> AFAIK, there is nothing unusual about it in the iterative process  
> for a protocol, and it is not alone. Take RFC 4271 as an example,  
> one of the changes is the following:
>
>    UPDATE Message Error subcode 7 (AS Routing Loop) has been  
> deprecated.
>
>
> The change reflects deployment and allows for implementation  
> flexibility.

Flexibility?  That's a gratuitous choice of words...

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


From idr-bounces@ietf.org  Wed Apr 30 13:44:53 2008
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 A56FA3A6AB7;
	Wed, 30 Apr 2008 13:44:53 -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 0AB133A6943
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 13:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 jzpCqQQFZSl7 for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 13:44:51 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id 1ED0A3A694A
	for <idr@ietf.org>; Wed, 30 Apr 2008 13:44:51 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id C1C2B53E1AF;
	Wed, 30 Apr 2008 16:44:53 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id RarcPpziRJfV; Wed, 30 Apr 2008 16:44:47 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id 7ABF153E0FC;
	Wed, 30 Apr 2008 16:44:46 -0400 (EDT)
Message-Id: <F4023837-6087-45A9-8D43-D248F89A27EC@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: Danny McPherson <danny@tcb.net>
In-Reply-To: <4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 16:44:45 -0400
References: <20080425213001.4EB133A69E7@core3.amsl.com>
	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>
	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
	<4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On Apr 30, 2008, at 4:12 PM, Danny McPherson wrote:
> On Apr 30, 2008, at 11:45 AM, John G. Scudder wrote:
>> The nice thing is that the feature is backward compatible and fails
>> safe -- if the client doesn't know how to handle the community, then
>> it sees itself in the ORIGINATOR_ID and drops the route.  No route,  
>> no
>> routing information loop.  Granted the behavior of dropping the route
>> is undesired, but not horrible.
>
> Even your draft disagrees with this, else it wouldn't mention
> the disabling RFC 1966 behavior

Not so.  The reason for that is to allow RR hierarchy to be used.   
Since the point of the draft is that the route's originator has to see  
it, it's important that RR's transparently pass it through.  I'm at a  
loss to see how you can interpret this as a tacit disagreement with my  
statement above.

> (as opposed to the discard
> based on ORIGINATOR_ID on the client that RFC 2796
> introduced -  for no valid _protocol reason, mind you, which
> annoys me considerably).  Along this vein, I would be quite
> interested in someone providing an explanation of why this
> behavior was changed from 1966 to 2796....

I suggest you take it up with that RFC's authors or check the archives  
-- I don't know the answer.  (I would say that implementability can be  
a "valid_protocol reason" though.)

>> Interesting -- one would have expected the vendor 'm' router to drop
>> the routes even if it didn't understand ORIGINATOR_ID, due to the
>> NEXT_HOP check.  I guess if the NEXT_HOP were getting rewritten...
>>
>> But in any event this particular case is academic because of the  
>> "fail
>> safe" behavior discussed above -- any client that interoperates  
>> with a
>> 2796 RR will fail safe.  (Any client that doesn't interoperate with a
>> 2796 RR is arguably pretty broken at this point.)
>
> Right, but see my point above...  This assumes all clients employ
> the discard behavior of 2796.

Well, that OR they properly implement the base spec and drop routes  
which have themselves as NEXT_HOP.

Do you really think that a client which doesn't interoperate with 2796  
RRs is viable in a network at all?  Especially one which also violates  
the base spec by not checking the NEXT_HOP?

>> One of my co-authors may want to address this point.  From my PoV,
>> suffice it to say there's real demand for the feature.
>
> I'm sure there is demand to make 2547 configuration simpler, but
> that doesn't mean it's something we should change fundamental
> BGP behavior to facilitate.  I would be interested in here from your
> co-authors..

I'm sure one of them will chime in.

>> What is the redundant network state you're referring to?  The  
>> "address
>> family overlays" I snipped out of the quote?
>
> No, I've come to accept the AF overlays..   What troubles me is the  
> fact
> that we're using BGP to enable a RR to modify an update learned from
> a client, and to reflect that update back to that client - just does  
> seem
> good routing protocol hygiene to me, to save configuration overhead
> on the client, when it'll surely be further required on the RRs.

OK, I don't see where this is "redundant network state" to speak of.   
Well, I guess for each route treated in this way there's one extra  
route exported from the RR to the route's originator -- but then again  
that is a route which the RR has to export to the rest of the network  
anyway.  So the RR does in effect no extra work.  The PE receiving the  
route does store a little extra stuff, but then again there would be  
some state for that route if it was locally exported between VRFs  
too.  Seems to me as though state -- both dynamic and configuration --  
is more-or-less a wash.

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


From idr-bounces@ietf.org  Wed Apr 30 13:48:03 2008
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 48DBB28C2BB;
	Wed, 30 Apr 2008 13:48:03 -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 ED3B83A6C63
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 13:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 9wQ07sW8CVBY for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 13:48:01 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 1759E3A6B85
	for <idr@ietf.org>; Wed, 30 Apr 2008 13:48:01 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 30 Apr 2008 13:48:04 -0700
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m3UKm3ko004206; 
	Wed, 30 Apr 2008 13:48:03 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m3UKm3mA018966;
	Wed, 30 Apr 2008 20:48:03 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 13:48:03 -0700
Received: from [10.21.69.88] ([10.21.69.88]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 13:48:03 -0700
Message-ID: <4818DB47.8040002@cisco.com>
Date: Wed, 30 Apr 2008 13:49:11 -0700
From: Enke Chen <enkechen@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Danny McPherson <danny@tcb.net>
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
	<4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
	<4818D897.3070804@cisco.com>
	<DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net>
In-Reply-To: <DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net>
X-OriginalArrivalTime: 30 Apr 2008 20:48:03.0656 (UTC)
	FILETIME=[7C2BDC80:01C8AB03]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1073; t=1209588483;
	x=1210452483; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=enkechen@cisco.com;
	z=From:=20Enke=20Chen=20<enkechen@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20Fwd=3A=20I-D=09ACTION=3Adraft-p
	mohapat-idr-acceptown-community-01.txt |Sender:=20;
	bh=n4XNv1po/olP8p3UDILCKmmbUyBtgEFKKL0F+7sD0Sg=;
	b=cxvx9aiPL2biwRkTN2SNRz/ggjzI5Jv5rKO1lcPWiCYedIbjT5p6PBNt79
	qS7A3nFkSrALQIsWZyt6yfFbQUy31lJdPDKLRAI+hLPdq1BrI93oiMuttRpO
	3lFu0YFAUt;
Authentication-Results: sj-dkim-4; header.From=enkechen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd:
	I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Danny McPherson wrote:
>
> On Apr 30, 2008, at 2:37 PM, Enke Chen wrote:
>
>> Hi, Danny:
>>
>> Regarding the specific change from 1966 to RFC 2796 that you 
>> mentioned, the reason was to make the spec. be consistent with the 
>> deployment (which has the behavior since Day 1 of the RR era).
>
> Not all implementations, else I'd have not seen conflicts ~10
> years ago between two of the most prominent implementations.

So would you prefer declaring the major deployment as "illegal", and 
somehow having all the deployment rolled back?

>
>> AFAIK, there is nothing unusual about it in the iterative process for 
>> a protocol, and it is not alone. Take RFC 4271 as an example, one of 
>> the changes is the following:
>>
>>    UPDATE Message Error subcode 7 (AS Routing Loop) has been deprecated.
>>
>>
>> The change reflects deployment and allows for implementation 
>> flexibility.
>
> Flexibility?  That's a gratuitous choice of words...

It's meant for the "AS Routing loop", although it equally applies to the 
RR case.

-- Enke


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


From idr-bounces@ietf.org  Wed Apr 30 13:53:15 2008
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 C17BB3A6CB9;
	Wed, 30 Apr 2008 13:53:15 -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 8C37A3A6A26
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 13:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083, 
	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 3K3kG16R6bKV for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 13:53:13 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id C25923A6C63
	for <idr@ietf.org>; Wed, 30 Apr 2008 13:53:13 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 9DD6A2680D7; Wed, 30 Apr 2008 14:53:16 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 30 Apr 2008 14:53:16 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=56723; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: Enke Chen <enkechen@cisco.com>
In-Reply-To: <4818DB47.8040002@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 14:53:00 -0600
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
	<4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
	<4818D897.3070804@cisco.com>
	<DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net>
	<4818DB47.8040002@cisco.com>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd:
	I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


On Apr 30, 2008, at 2:49 PM, Enke Chen wrote:
> So would you prefer declaring the major deployment as "illegal", and
> somehow having all the deployment rolled back?

Sure..  I don't like the idea of changing specs to accommodate
implementation optimizations.

> It's meant for the "AS Routing loop", although it equally applies to  
> the
> RR case.

No, that to accommodate use cases that are themselves
arguably hacks.  It wasn't meant to allow AN implementation
to be optimized.

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


From idr-bounces@ietf.org  Wed Apr 30 13:55:21 2008
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 025193A6BC7;
	Wed, 30 Apr 2008 13:55:21 -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 84C0E3A6BC7
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 13:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 oWXQdv6kWcWK for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 13:55:18 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 6E72B3A6A8B
	for <idr@ietf.org>; Wed, 30 Apr 2008 13:55:18 -0700 (PDT)
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 30 Apr 2008 13:55:21 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m3UKtLcH018380; 
	Wed, 30 Apr 2008 13:55:21 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m3UKtEnr023115;
	Wed, 30 Apr 2008 20:55:21 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 13:55:20 -0700
Received: from [10.21.69.88] ([10.21.69.88]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 13:55:20 -0700
Message-ID: <4818DCFC.70001@cisco.com>
Date: Wed, 30 Apr 2008 13:56:28 -0700
From: Enke Chen <enkechen@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Danny McPherson <danny@tcb.net>
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
	<4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
	<4818D897.3070804@cisco.com>
	<DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net>
	<4818DB47.8040002@cisco.com>
	<82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net>
In-Reply-To: <82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net>
X-OriginalArrivalTime: 30 Apr 2008 20:55:20.0176 (UTC)
	FILETIME=[805B8700:01C8AB04]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=597; t=1209588921; x=1210452921;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=enkechen@cisco.com;
	z=From:=20Enke=20Chen=20<enkechen@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20Fwd=3A=20I-D=09ACTION=3Adraft-p
	mohapat-idr-acceptown-community-01.txt |Sender:=20;
	bh=VnM4qhyLU1KS3P9kjgDEDC7aa+Uk+phyfRZ/980CrnQ=;
	b=IJy6Cmob9aHenwEmh2FID4FqQTcx/HRsSIT0B5slUsJjgNXN1NIims4rKY
	JbyL1Huoo/wdgAX/K/78boUiO0S867LZk9Z3AM33zjOfCyR/J/f5n+GN/i+p
	GmHh0/hWZp;
Authentication-Results: sj-dkim-4; header.From=enkechen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd:
	I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Danny McPherson wrote:
>
> On Apr 30, 2008, at 2:49 PM, Enke Chen wrote:
>> So would you prefer declaring the major deployment as "illegal", and
>> somehow having all the deployment rolled back?
>
> Sure..  I don't like the idea of changing specs to accommodate
> implementation optimizations.

welcome to the real world :-)

-- Enke

>
>> It's meant for the "AS Routing loop", although it equally applies to the
>> RR case.
>
> No, that to accommodate use cases that are themselves
> arguably hacks.  It wasn't meant to allow AN implementation
> to be optimized.
>
> -danny

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


From idr-bounces@ietf.org  Wed Apr 30 14:19:50 2008
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 970723A6CF4;
	Wed, 30 Apr 2008 14:19:50 -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 E902A3A6A4E
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 14:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074, 
	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 7e34C6lQ4kgu for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 14:19:45 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 177323A6CD6
	for <idr@ietf.org>; Wed, 30 Apr 2008 14:19:44 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id B3267268494; Wed, 30 Apr 2008 15:19:47 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 30 Apr 2008 15:19:47 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=56772; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <80A0A0C2-F44E-46F9-967A-BC2690EFC29D@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: "John G. Scudder" <jgs@bgp.nu>
In-Reply-To: <F4023837-6087-45A9-8D43-D248F89A27EC@bgp.nu>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 15:19:31 -0600
References: <20080425213001.4EB133A69E7@core3.amsl.com>
	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>
	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
	<4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
	<F4023837-6087-45A9-8D43-D248F89A27EC@bgp.nu>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

>
> Not so.  The reason for that is to allow RR hierarchy to be used.
> Since the point of the draft is that the route's originator has to see
> it, it's important that RR's transparently pass it through.  I'm at a
> loss to see how you can interpret this as a tacit disagreement with my
> statement above.

Then why the 1966 text at all, that was my point.

> I suggest you take it up with that RFC's authors or check the archives
> -- I don't know the answer.  (I would say that implementability can  
> be  
> a "valid_protocol reason" though.)

Heh, that's the high road :-)

> Well, that OR they properly implement the base spec and drop routes
> which have themselves as NEXT_HOP.
>
> Do you really think that a client which doesn't interoperate with 2796
> RRs is viable in a network at all?  Especially one which also violates
> the base spec by not checking the NEXT_HOP?

I've seen it before in a real network.

> OK, I don't see where this is "redundant network state" to speak of.
> Well, I guess for each route treated in this way there's one extra
> route exported from the RR to the route's originator -- but then again
> that is a route which the RR has to export to the rest of the network
> anyway.  So the RR does in effect no extra work.  The PE receiving the
> route does store a little extra stuff, but then again there would be
> some state for that route if it was locally exported between VRFs
> too.  Seems to me as though state -- both dynamic and configuration --
> is more-or-less a wash.

Well, upon thinking about this a bit more, it also seems silly to
me that a network would be architected in such a way as to allow
problems with an 'upstream' RR to affect connectivity between
two VRFs on the same PE.  I'd think to an operator trying to ensure
availability would be worth the configuration overhead, even if
some folks consider the extra 'state' a wash.

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


From idr-bounces@ietf.org  Wed Apr 30 14:30:51 2008
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 BEE193A6BA4;
	Wed, 30 Apr 2008 14:30:51 -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 F34C03A6D81
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 14:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 QJ3oYFSb4K3O for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 14:30:50 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id E89D53A694A
	for <idr@ietf.org>; Wed, 30 Apr 2008 14:30:49 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id 72D3A53E1B5;
	Wed, 30 Apr 2008 17:30:52 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id nmNSeLESSbL4; Wed, 30 Apr 2008 17:30:46 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id 86E6353E1AF;
	Wed, 30 Apr 2008 17:30:45 -0400 (EDT)
Message-Id: <52EEA4F2-1AC8-4625-9922-9558B39253B5@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: Enke Chen <enkechen@cisco.com>
In-Reply-To: <4818ACAF.6000306@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 17:30:44 -0400
References: <200804301333.m3UDX4x97759@magenta.juniper.net>
	<4818ACAF.6000306@cisco.com>
X-Mailer: Apple Mail (2.919.2)
Cc: Yakov Rekhter <yakov@juniper.net>, idr@ietf.org
Subject: Re: [Idr] Fwd: New Version Notification
	for	draft-scudder-idr-rfc3392-bis-
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Enke,

Would adding this paragraph at the end of section 4 cover your point?

    The Capabilities Optional Parameter SHOULD only be included in the
    OPEN message once.  If the BGP speaker wishes to include multiple
    capabilities in the OPEN message, it SHOULD do so as discussed  
above,
    by listing all those capabilities within the same Capabilities
    Optional Parameter.  However, for backward compatibility a BGP
    speaker MUST be prepared to receive an OPEN message which contains
    multiple Capabilities Optional Parameters, each of which contains  
one
    or more capabilities.  The set of capabilities should be processed
    the same in either case, whether the it is listed within a single
    Capabilities Optional Parameter, or within multiple.

Thanks,

--John

On Apr 30, 2008, at 1:30 PM, Enke Chen wrote:

> Hi, folks:
>
> While we are at it, I suggest that we also clarify on the encoding of
> the capabilities.  Currently there exist two encodings for  
> capabilities
> in the "Optional Parameters" field of the OPEN message, and both are
> deployed:
>
> (1) List the capabilities in one "optional parameter":
>
>      Parm. Type - capability
>      Parm. Length
>      cap_1, cap_1_len, cap_1_value
>      ...
>      cap_n, cap_n_len, cap_n_value
>
> (2) List the capabilities in multiple "optional parameters":
>
>      Parm. Type - capability
>      Parm. Length
>      cap_1, cap_1_len, cap_1_value
>      ...
>      Parm. Type - capability
>      Parm. Length
>      cap_n, cap_n_len, cap_n_value
>
> Ideally #1 is more correct for TLV encoding.  But we started with  
> #2 :-(
>
> I suggest that we add some text in the document to point out their
> existence and state that both types MUST be accepted.
>
> Thanks.   -- Enke
>
> Yakov Rekhter wrote:
>> Folks,
>>
>> There is a request (see attached) to accept draft-scudder-idr- 
>> rfc3392-bis
>> as an IDR WG item. Please send your comments to the list. The  
>> deadline
>> for comments is May 14.
>>
>> Yakov.
>> ------- Forwarded Message
>>
>> Date:    Tue, 29 Apr 2008 14:51:16 -0400
>> From:    "John G. Scudder" <jgs@bgp.nu>
>> To:      idr <idr@ietf.org>
>> Subject: [Idr] Fwd: New Version Notification for draft-scudder-idr- 
>> rfc3392-bis-
>> 	  00
>>
>> Folks,
>>
>> I've done some minor updates to the Capabilities Advertisement
>> specification to address confusion about the "Unsupported Capability"
>> NOTIFICATION message:
>>
>> 	Appendix B.  Comparison with RFC 3392
>> 	
>> 	   In addition to minor editorial changes, this document also  
>> clarifies
>> 	   the use of the Unsupported Optional Parameter NOTIFICATION  
>> message,
>> 	   and updates references to the base BGP-4 specification  
>> [RFC4271] and
>> 	   security analysis [RFC4272].
>>
>> The draft is at http://www.ietf.org/internet-drafts/draft-scudder-idr-rfc3392-b
>> is-00.txt
>> .
>>
>> Comments welcome.  One thing that occurred to me was to rename
>> "Unsupported Capability" to "Required Capability Missing", however
>> that might do more harm than good by renaming an existing code point,
>> so I didn't.
>>
>> I'd like to propose this as a WG item (if indeed such a request is
>> even required for an update to an existing WG document?).
>>
>> Thanks,
>>
>> - --John
>>
>> Begin forwarded message:
>>
>>
>>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>>> Date: April 29, 2008 2:41:21 PM GMT-04:00
>>> To: jgs@juniper.net
>>> Cc: rchandra@sonoasystems.com
>>> Subject: New Version Notification for draft-scudder-idr-rfc3392- 
>>> bis-00
>>>
>>>
>>> A new version of I-D, draft-scudder-idr-rfc3392-bis-00.txt has been
>>> successfuly submitted by John Scudder and posted to the IETF
>>> repository.
>>>
>>> Filename:	 draft-scudder-idr-rfc3392-bis
>>> Revision:	 00
>>> Title:		 Capabilities Advertisement with BGP-4
>>> Creation_date:	 2008-04-29
>>> WG ID:		 Independent Submission
>>> Number_of_pages: 7
>>>
>>> Abstract:
>>> This document defines an Optional Parameter, called Capabilities,
>>> that is expected to facilitate the introduction of new capabilities
>>> in the Border Gateway Protocol (BGP) by providing graceful  
>>> capability
>>> advertisement without requiring that BGP peering be terminated.   
>>> This
>>> document obsoletes RFC 3392.
>>>
>>>
>>>
>>> The IETF Secretariat.
>>>
>>>
>>>
>>
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>>
>> ------- End of Forwarded Message
>>
>> _______________________________________________
>> 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
>

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


From idr-bounces@ietf.org  Wed Apr 30 14:32:11 2008
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 A1FD728C3D2;
	Wed, 30 Apr 2008 14:32:11 -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 7E0B228C397
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 14:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 oNfvAtSuh+ED for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 14:32:08 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id 0F08C28C3FA
	for <idr@ietf.org>; Wed, 30 Apr 2008 14:31:20 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id B327053E1F4;
	Wed, 30 Apr 2008 17:31:22 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id NMMuPcO2uZon; Wed, 30 Apr 2008 17:31:12 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id 1407653E1B5;
	Wed, 30 Apr 2008 17:31:11 -0400 (EDT)
Message-Id: <ECC75E57-CBCA-4E48-B88F-23442E398F65@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: Danny McPherson <danny@tcb.net>
In-Reply-To: <0B82A4F5-4D76-427B-8CB3-386C0F6A64F2@tcb.net>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 17:31:11 -0400
References: <200804301333.m3UDX4x97759@magenta.juniper.net>
	<0B82A4F5-4D76-427B-8CB3-386C0F6A64F2@tcb.net>
X-Mailer: Apple Mail (2.919.2)
Cc: Yakov Rekhter <yakov@juniper.net>, idr@ietf.org
Subject: Re: [Idr] Fwd: New Version Notification for
	draft-scudder-idr-rfc3392-bis-
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On Apr 30, 2008, at 10:02 AM, Danny McPherson wrote:
> One minor comment..   I think we should rename "Unsupported  
> Capability"
> to "Required Capability Missing", and given that the codepoint itself
> isn't
> changing, just the descriptor, there should be no issues here.

Clearly this is OK by me if the WG is happy with it.

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


From idr-bounces@ietf.org  Wed Apr 30 14:32:13 2008
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 03A8228C37F;
	Wed, 30 Apr 2008 14:32:13 -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 F04CC28C3D2
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 14:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level: 
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[AWL=0.068, 
	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 TBP6K8ie7pYY for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 14:32:10 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id D06C428C0EF
	for <idr@ietf.org>; Wed, 30 Apr 2008 14:31:40 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id ABE382680D7; Wed, 30 Apr 2008 15:31:43 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 30 Apr 2008 15:31:43 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=56778; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <8D3C8A4B-B80B-4983-8DC7-A142FFA4B41C@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: Enke Chen <enkechen@cisco.com>
In-Reply-To: <4818DCFC.70001@cisco.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 15:31:28 -0600
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
	<4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
	<4818D897.3070804@cisco.com>
	<DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net>
	<4818DB47.8040002@cisco.com>
	<82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net>
	<4818DCFC.70001@cisco.com>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd:
	I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


On Apr 30, 2008, at 2:56 PM, Enke Chen wrote:
>>
>> Sure..  I don't like the idea of changing specs to accommodate
>> implementation optimizations.
>
> welcome to the real world :-)

I do understand the reasoning behind this, although I
don't agree with it.

In the real world, operators are complaining about DFZ
sizes (unique routes), and routing scalability, and churn,
little implementation tweaks that surface as base spec
changes like this have serious implications.

Consider this 'optimization', for example.  Now, most
clusters have at least 2-3 RRs, and many clients.  If you've
got a single client that has 50k external paths that it sees
as best, and that client advertises them to the RRs, and
the RRs reflect them back, just so that the client can discard
them, then unless I'm confused, that little optimization just cost
you 150k (50k routes * 3 RRs, reflected back to client they
were learned from) worth update processing resources on
the clients.  Not to mention implications on churn, or additional
layers of RR hierarchy, or the dynamics this introduces in a
REAL network.

 From a network-level perspective I don't see much of an
optimization at all, quite the contrary, actually.

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


From idr-bounces@ietf.org  Wed Apr 30 14:48:12 2008
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 7E4213A6A4E;
	Wed, 30 Apr 2008 14:48:12 -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 8EE263A6A23
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 14:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 jzISdKF+Wii8 for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 14:48:10 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 0F6393A6961
	for <idr@ietf.org>; Wed, 30 Apr 2008 14:48:10 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 30 Apr 2008 14:48:12 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m3ULmCkR008734; 
	Wed, 30 Apr 2008 14:48:12 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m3ULmCNK003793;
	Wed, 30 Apr 2008 21:48:12 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 14:48:12 -0700
Received: from [10.21.69.88] ([10.21.69.88]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 14:48:11 -0700
Message-ID: <4818E960.70107@cisco.com>
Date: Wed, 30 Apr 2008 14:49:20 -0700
From: Enke Chen <enkechen@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: "John G. Scudder" <jgs@bgp.nu>
References: <200804301333.m3UDX4x97759@magenta.juniper.net>
	<4818ACAF.6000306@cisco.com>
	<52EEA4F2-1AC8-4625-9922-9558B39253B5@bgp.nu>
In-Reply-To: <52EEA4F2-1AC8-4625-9922-9558B39253B5@bgp.nu>
X-OriginalArrivalTime: 30 Apr 2008 21:48:12.0031 (UTC)
	FILETIME=[E2EE30F0:01C8AB0B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5159; t=1209592092;
	x=1210456092; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=enkechen@cisco.com;
	z=From:=20Enke=20Chen=20<enkechen@cisco.com>
	|Subject:=20Re=3A=20[Idr]=20Fwd=3A=20New=20Version=20Notifi
	cation=20for=09draft-scudder-idr-rfc3392-bis- |Sender:=20;
	bh=T+55zSlPMeZGgyUzgkxxCOxMJ+ifsVpw6W+mFtDg4QE=;
	b=sz8fDbnsGcvb9gcA90DAMBa6Ksr/CrkIW9YF8/vCR5qfi/okxUAC5H3yWN
	rSeECPjCnCM9UuoqoMV45OP0S0aA9khDxf6NhZUsgMj1zrk7M+FjfUXQun5T
	eu67UhG4PR;
Authentication-Results: sj-dkim-2; header.From=enkechen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: Yakov Rekhter <yakov@juniper.net>, idr@ietf.org
Subject: Re: [Idr] Fwd: New Version Notification
	for	draft-scudder-idr-rfc3392-bis-
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi,. John:

It looks good.

Thanks.   -- Enke

John G. Scudder wrote:
> Enke,
>
> Would adding this paragraph at the end of section 4 cover your point?
>
>    The Capabilities Optional Parameter SHOULD only be included in the
>    OPEN message once.  If the BGP speaker wishes to include multiple
>    capabilities in the OPEN message, it SHOULD do so as discussed above,
>    by listing all those capabilities within the same Capabilities
>    Optional Parameter.  However, for backward compatibility a BGP
>    speaker MUST be prepared to receive an OPEN message which contains
>    multiple Capabilities Optional Parameters, each of which contains one
>    or more capabilities.  The set of capabilities should be processed
>    the same in either case, whether the it is listed within a single
>    Capabilities Optional Parameter, or within multiple.
>
> Thanks,
>
> --John
>
> On Apr 30, 2008, at 1:30 PM, Enke Chen wrote:
>
>> Hi, folks:
>>
>> While we are at it, I suggest that we also clarify on the encoding of
>> the capabilities.  Currently there exist two encodings for capabilities
>> in the "Optional Parameters" field of the OPEN message, and both are
>> deployed:
>>
>> (1) List the capabilities in one "optional parameter":
>>
>>      Parm. Type - capability
>>      Parm. Length
>>      cap_1, cap_1_len, cap_1_value
>>      ...
>>      cap_n, cap_n_len, cap_n_value
>>
>> (2) List the capabilities in multiple "optional parameters":
>>
>>      Parm. Type - capability
>>      Parm. Length
>>      cap_1, cap_1_len, cap_1_value
>>      ...
>>      Parm. Type - capability
>>      Parm. Length
>>      cap_n, cap_n_len, cap_n_value
>>
>> Ideally #1 is more correct for TLV encoding.  But we started with #2 :-(
>>
>> I suggest that we add some text in the document to point out their
>> existence and state that both types MUST be accepted.
>>
>> Thanks.   -- Enke
>>
>> Yakov Rekhter wrote:
>>> Folks,
>>>
>>> There is a request (see attached) to accept 
>>> draft-scudder-idr-rfc3392-bis
>>> as an IDR WG item. Please send your comments to the list. The deadline
>>> for comments is May 14.
>>>
>>> Yakov.
>>> ------- Forwarded Message
>>>
>>> Date:    Tue, 29 Apr 2008 14:51:16 -0400
>>> From:    "John G. Scudder" <jgs@bgp.nu>
>>> To:      idr <idr@ietf.org>
>>> Subject: [Idr] Fwd: New Version Notification for 
>>> draft-scudder-idr-rfc3392-bis-
>>>       00
>>>
>>> Folks,
>>>
>>> I've done some minor updates to the Capabilities Advertisement
>>> specification to address confusion about the "Unsupported Capability"
>>> NOTIFICATION message:
>>>
>>>     Appendix B.  Comparison with RFC 3392
>>>     
>>>        In addition to minor editorial changes, this document also 
>>> clarifies
>>>        the use of the Unsupported Optional Parameter NOTIFICATION 
>>> message,
>>>        and updates references to the base BGP-4 specification 
>>> [RFC4271] and
>>>        security analysis [RFC4272].
>>>
>>> The draft is at 
>>> http://www.ietf.org/internet-drafts/draft-scudder-idr-rfc3392-b
>>> is-00.txt
>>> .
>>>
>>> Comments welcome.  One thing that occurred to me was to rename
>>> "Unsupported Capability" to "Required Capability Missing", however
>>> that might do more harm than good by renaming an existing code point,
>>> so I didn't.
>>>
>>> I'd like to propose this as a WG item (if indeed such a request is
>>> even required for an update to an existing WG document?).
>>>
>>> Thanks,
>>>
>>> - --John
>>>
>>> Begin forwarded message:
>>>
>>>
>>>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>>>> Date: April 29, 2008 2:41:21 PM GMT-04:00
>>>> To: jgs@juniper.net
>>>> Cc: rchandra@sonoasystems.com
>>>> Subject: New Version Notification for draft-scudder-idr-rfc3392-bis-00
>>>>
>>>>
>>>> A new version of I-D, draft-scudder-idr-rfc3392-bis-00.txt has been
>>>> successfuly submitted by John Scudder and posted to the IETF
>>>> repository.
>>>>
>>>> Filename:     draft-scudder-idr-rfc3392-bis
>>>> Revision:     00
>>>> Title:         Capabilities Advertisement with BGP-4
>>>> Creation_date:     2008-04-29
>>>> WG ID:         Independent Submission
>>>> Number_of_pages: 7
>>>>
>>>> Abstract:
>>>> This document defines an Optional Parameter, called Capabilities,
>>>> that is expected to facilitate the introduction of new capabilities
>>>> in the Border Gateway Protocol (BGP) by providing graceful capability
>>>> advertisement without requiring that BGP peering be terminated.  This
>>>> document obsoletes RFC 3392.
>>>>
>>>>
>>>>
>>>> The IETF Secretariat.
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Idr mailing list
>>> Idr@ietf.org
>>> https://www.ietf.org/mailman/listinfo/idr
>>>
>>> ------- End of Forwarded Message
>>>
>>> _______________________________________________
>>> 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
>>
>

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


From idr-bounces@ietf.org  Wed Apr 30 15:03:33 2008
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 244C73A698C;
	Wed, 30 Apr 2008 15:03:33 -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 7DE503A684D
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 15:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 Ih7WvK8sdi26 for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 15:03:30 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id BB2A328C435
	for <idr@ietf.org>; Wed, 30 Apr 2008 15:03:10 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id 6A84453E1AF;
	Wed, 30 Apr 2008 18:03:13 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id V8rVgUto1e79; Wed, 30 Apr 2008 18:03:07 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id 616FD53E0FC;
	Wed, 30 Apr 2008 18:03:07 -0400 (EDT)
Message-Id: <B8D6A07F-5E2F-480C-8BC2-AC49F6A36A16@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: Danny McPherson <danny@tcb.net>
In-Reply-To: <80A0A0C2-F44E-46F9-967A-BC2690EFC29D@tcb.net>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 18:03:05 -0400
References: <20080425213001.4EB133A69E7@core3.amsl.com>
	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>
	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
	<4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
	<F4023837-6087-45A9-8D43-D248F89A27EC@bgp.nu>
	<80A0A0C2-F44E-46F9-967A-BC2690EFC29D@tcb.net>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On Apr 30, 2008, at 5:19 PM, Danny McPherson wrote:
>> Do you really think that a client which doesn't interoperate with  
>> 2796
>> RRs is viable in a network at all?  Especially one which also  
>> violates
>> the base spec by not checking the NEXT_HOP?
>
> I've seen it before in a real network.

And did you think that client was behaving appropriately then?  If so,  
why did you think it was OK for the client to violate the base spec?   
Also, you mentioned that your "real network" example was from ~10  
years ago, so while it's interesting... do you think such clients are  
still likely to exist *today*?

> Well, upon thinking about this a bit more, it also seems silly to
> me that a network would be architected in such a way as to allow
> problems with an 'upstream' RR to affect connectivity between
> two VRFs on the same PE.  I'd think to an operator trying to ensure
> availability would be worth the configuration overhead, even if
> some folks consider the extra 'state' a wash.

I guess different operators have different views about where in the  
optimization space they want to live.  For that matter, if the  
(redundant pair of) RRs goes south, the PE's connectivity to the rest  
of the world is broken anyway, local connectivity is just a special  
case.  I can understand why the survival of that special case when the  
rest of the world is broken may not be seen as a deal-breaker.

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


From idr-bounces@ietf.org  Wed Apr 30 15:05:26 2008
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 0FD803A6955;
	Wed, 30 Apr 2008 15:05:26 -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 54F4F3A6C63
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 15:05:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 qbJTUCsJQnCN for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 15:05:23 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157])
	by core3.amsl.com (Postfix) with ESMTP id 5ABFF3A6B17
	for <idr@ietf.org>; Wed, 30 Apr 2008 15:05:02 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob102.postini.com
	([64.18.6.12]) with SMTP; Wed, 30 Apr 2008 15:04:46 PDT
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 30 Apr 2008 15:04:37 -0700
Received: from [172.26.250.99] ([172.26.250.99])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m3UM4Zx93288;
	Wed, 30 Apr 2008 15:04:35 -0700 (PDT)
	(envelope-from raszuk@juniper.net)
Message-ID: <4818ECF1.1030909@juniper.net>
Date: Wed, 30 Apr 2008 15:04:33 -0700
From: Robert Raszuk <raszuk@juniper.net>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Danny McPherson <danny@tcb.net>
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu><4686A93B-EF16-48DC-9775-1BD241575360@tcb.net><4818D897.3070804@cisco.com><DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net><4818DB47.8040002@cisco.com><82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net><4818DCFC.70001@cisco.com>
	<8D3C8A4B-B80B-4983-8DC7-A142FFA4B41C@tcb.net>
In-Reply-To: <8D3C8A4B-B80B-4983-8DC7-A142FFA4B41C@tcb.net>
X-OriginalArrivalTime: 30 Apr 2008 22:04:37.0002 (UTC)
	FILETIME=[2E04D6A0:01C8AB0E]
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr]
	Fwd:I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@juniper.net
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Danny,

In your below mail you are missing one fundamental practical data.

It is very cheap and easy to drop the unneeded route on inbound while it 
is very CPU intensive to build separate updates to each peer.

With current link bandwith the amount of traffic generated due to that 
is just white noise.

IMHO based on the most common implementations at that time that was the 
main reason for the RR spec change.

**

Now back to accept-own community I really see nothing wrong with it. If 
you are trying to say this is bad just because some implementations to 
not support 2796 that's I am afraid wrong avenue.

There are practical applications for this enhancement of which one is 
described in the draft.

As general rule of thumb I think there is need to support more 
automation in the network provisioning among many providers. There is 
also a demand in the market for more dynamic behavior of running 
applications. This is just right on this spot attempt to support one of 
them.

Cheers,
R.

PS. As to the comment from Ilya that this draft may break BGP 
implementations ... one needs to realize that conditional one more check 
during inbound processing requires negligible amount of new BGP code.

And I would like to point out that in most BGP implementations I am 
familiar with every month amount of code changes which go in even in the 
fundamental parts of BGP assuming one may freeze all IDR work is much 
much much higher then such draft would require.


> On Apr 30, 2008, at 2:56 PM, Enke Chen wrote:
>  >>
>  >> Sure..  I don't like the idea of changing specs to accommodate
>  >> implementation optimizations.
>  >
>  > welcome to the real world :-)
> 
> I do understand the reasoning behind this, although I
> don't agree with it.
> 
> In the real world, operators are complaining about DFZ
> sizes (unique routes), and routing scalability, and churn,
> little implementation tweaks that surface as base spec
> changes like this have serious implications.
> 
> Consider this 'optimization', for example.  Now, most
> clusters have at least 2-3 RRs, and many clients.  If you've
> got a single client that has 50k external paths that it sees
> as best, and that client advertises them to the RRs, and
> the RRs reflect them back, just so that the client can discard
> them, then unless I'm confused, that little optimization just cost
> you 150k (50k routes * 3 RRs, reflected back to client they
> were learned from) worth update processing resources on
> the clients.  Not to mention implications on churn, or additional
> layers of RR hierarchy, or the dynamics this introduces in a
> REAL network.
> 
>  From a network-level perspective I don't see much of an
> optimization at all, quite the contrary, actually.
> 
> -danny
> _______________________________________________
> 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


From idr-bounces@ietf.org  Wed Apr 30 15:28:00 2008
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 3DB6A3A6AD7;
	Wed, 30 Apr 2008 15:28:00 -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 DD8F03A6AD7
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 15:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062, 
	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 Zzd53rE5hFU5 for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 15:27:58 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id F16133A6A0A
	for <idr@ietf.org>; Wed, 30 Apr 2008 15:27:57 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id A9EA22680D7; Wed, 30 Apr 2008 16:28:00 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 30 Apr 2008 16:28:00 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=57085; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <59351B8C-437C-4803-833B-D8A5036667E0@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: "John G. Scudder" <jgs@bgp.nu>
In-Reply-To: <B8D6A07F-5E2F-480C-8BC2-AC49F6A36A16@bgp.nu>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 16:27:44 -0600
References: <20080425213001.4EB133A69E7@core3.amsl.com>
	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>
	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>
	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>
	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>
	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu>
	<4686A93B-EF16-48DC-9775-1BD241575360@tcb.net>
	<F4023837-6087-45A9-8D43-D248F89A27EC@bgp.nu>
	<80A0A0C2-F44E-46F9-967A-BC2690EFC29D@tcb.net>
	<B8D6A07F-5E2F-480C-8BC2-AC49F6A36A16@bgp.nu>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr] Fwd: I-D
	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


On Apr 30, 2008, at 4:03 PM, John G. Scudder wrote:
> And did you think that client was behaving appropriately then?

No, neither did your current employer.  But the other vendor
pointed to the spec changes and said they were compliant and
the client needs to know it's a client and needs to drop the
extraneous updates.

I'd be keen on revamping 2796 again to remove that local
optimization, personally.  I'm no fan of expanding upon it.

> If so,
> why did you think it was OK for the client to violate the base spec?
> Also, you mentioned that your "real network" example was from ~10
> years ago, so while it's interesting... do you think such clients are
> still likely to exist *today*?

Depends on whether I think the spec change was
appropriate or not.  Again, local optimizations that
result in much more system-wide state I'm not a big
fan of.

> I guess different operators have different views about where in the
> optimization space they want to live.  For that matter, if the
> (redundant pair of)

If they're redundant, then there's dual the amount of
extraneous state, and they may still share a common
switched link layer or the like.

> RRs goes south, the PE's connectivity to the rest
> of the world is broken anyway, local connectivity is just a special
> case.  I can understand why the survival of that special case when the
> rest of the world is broken may not be seen as a deal-breaker.

Perhaps.  I wouldn't buy such a service from an operator
that designed their network in this manner, you might (although
I doubt it :-), but fair enough.

I believe folks that are implementing this may want to help
their customers understand this case, and I think the
draft would benefit from it's discussion as well.

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


From idr-bounces@ietf.org  Wed Apr 30 15:39:23 2008
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 018613A697F;
	Wed, 30 Apr 2008 15:39:23 -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 D36F13A6969
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 15:39:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057, 
	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 tW9RaOjy19bG for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 15:39:20 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id D531B3A6848
	for <idr@ietf.org>; Wed, 30 Apr 2008 15:39:20 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id AC59C2680D7; Wed, 30 Apr 2008 16:39:23 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 30 Apr 2008 16:39:23 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=57094; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <157A9EDC-B512-4C05-A257-72D70DFB44FA@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: raszuk@juniper.net
In-Reply-To: <4818ECF1.1030909@juniper.net>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 16:39:08 -0600
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu><4686A93B-EF16-48DC-9775-1BD241575360@tcb.net><4818D897.3070804@cisco.com><DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net><4818DB47.8040002@cisco.com><82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net><4818DCFC.70001@cisco.com>
	<8D3C8A4B-B80B-4983-8DC7-A142FFA4B41C@tcb.net>
	<4818ECF1.1030909@juniper.net>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr]
	Fwd:I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


On Apr 30, 2008, at 4:04 PM, Robert Raszuk wrote:

> Hi Danny,
>
> In your below mail you are missing one fundamental practical data.

No, I'm not missing this, I understand it, I know why the spec
change was made.

> It is very cheap and easy to drop the unneeded route on inbound  
> while it
> is very CPU intensive to build separate updates to each peer.

Really?  Where's the line drawn?  What about when there are
one million updates being dropped?  I could probably make a
case for this today?  What about legit updates queued behind
these?  I don't believe introducing extraneous routing system
level state to allow more efficient update generation is a valid
excuse.

> With current link bandwith the amount of traffic generated due to that
> is just white noise.

Traffic wasn't the issue.  It's more CPU, memory, etc..  Just
because it's available doesn't mean it's free.

> IMHO based on the most common implementations at that time that was  
> the
> main reason for the RR spec change.

"Implementations" should be "implementation" there, not the
plural.

>
> **
>
> Now back to accept-own community I really see nothing wrong with it.  
> If
> you are trying to say this is bad just because some implementations to
> not support 2796 that's I am afraid wrong avenue.

Perhaps, if you're in the business of selling CPUs and memory.

> There are practical applications for this enhancement of which one is
> described in the draft.

Yes, one that introduces even local PE VRF-VRF connectivity
reliance on upstream RRs..

> As general rule of thumb I think there is need to support more
> automation in the network provisioning among many providers. There is
> also a demand in the market for more dynamic behavior of running
> applications. This is just right on this spot attempt to support one  
> of
> them.

Perhaps, but I think it ugly because of both clean routing hygiene
issues, and the network architectural fault considerations I've already
outlined.

>
> Cheers,
> R.
>
> PS. As to the comment from Ilya that this draft may break BGP
> implementations ... one needs to realize that conditional one more  
> check
> during inbound processing requires negligible amount of new BGP code.

Negligible, can you quantify that?  How many routes?  How much
churn?

> And I would like to point out that in most BGP implementations I am
> familiar with every month amount of code changes which go in even in  
> the
> fundamental parts of BGP assuming one may freeze all IDR work is much
> much much higher then such draft would require.

I don't understand what point you're making here.

-danny

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


From idr-bounces@ietf.org  Wed Apr 30 15:52:30 2008
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 9405B3A695F;
	Wed, 30 Apr 2008 15:52:30 -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 0EE743A69A1
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 15:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level: 
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 wv6eTazit4-W for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 15:52:28 -0700 (PDT)
Received: from bgp.nu (bgp.nu [64.27.28.76])
	by core3.amsl.com (Postfix) with ESMTP id 4B0683A695F
	for <idr@ietf.org>; Wed, 30 Apr 2008 15:52:28 -0700 (PDT)
Received: from localhost (bgp.nu [64.27.28.76])
	by bgp.nu (Postfix) with ESMTP id 116C153E1AF;
	Wed, 30 Apr 2008 18:52:31 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([64.27.28.76])
	by localhost (bgp.nu [64.27.28.76]) (amavisd-new, port 10024)
	with LMTP id Hhztz0pB7l7u; Wed, 30 Apr 2008 18:52:24 -0400 (EDT)
Received: from [172.16.13.201] (dsl093-003-111.det1.dsl.speakeasy.net
	[66.93.3.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by bgp.nu (Postfix) with ESMTP id 1D52253E0FC;
	Wed, 30 Apr 2008 18:52:24 -0400 (EDT)
Message-Id: <E41B60B6-6B6C-4EF1-9170-BDAAE23B9D7E@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: Danny McPherson <danny@tcb.net>
In-Reply-To: <157A9EDC-B512-4C05-A257-72D70DFB44FA@tcb.net>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 18:52:22 -0400
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu><4686A93B-EF16-48DC-9775-1BD241575360@tcb.net><4818D897.3070804@cisco.com><DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net><4818DB47.8040002@cisco.com><82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net><4818DCFC.70001@cisco.com>
	<8D3C8A4B-B80B-4983-8DC7-A142FFA4B41C@tcb.net>
	<4818ECF1.1030909@juniper.net>
	<157A9EDC-B512-4C05-A257-72D70DFB44FA@tcb.net>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr]
	Fwd:I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On Apr 30, 2008, at 6:39 PM, Danny McPherson wrote:
>> With current link bandwith the amount of traffic generated due to  
>> that
>> is just white noise.
>
> Traffic wasn't the issue.  It's more CPU, memory, etc..  Just
> because it's available doesn't mean it's free.

Regarding memory, it needn't be consumed for a this-is-my-own-route  
path.  (It may be, but this is an implementation decision.)

Regarding CPU, remember that you want to optimize the bottleneck,  
nothing else matters really.  In most cases, the RR is the control  
plane bottleneck.  Loading it up more to protect the CPUs of non- 
bottleneck devices seems like an odd design decision.

>> IMHO based on the most common implementations at that time that was
>> the
>> main reason for the RR spec change.
>
> "Implementations" should be "implementation" there, not the
> plural.

FWIW I'm aware of at least three implementations that independently  
arrived at this same "optimization".

>> Now back to accept-own community I really see nothing wrong with it.
>> If
>> you are trying to say this is bad just because some implementations  
>> to
>> not support 2796 that's I am afraid wrong avenue.
>
> Perhaps, if you're in the business of selling CPUs and memory.

I don't really see the connection.

>> There are practical applications for this enhancement of which one is
>> described in the draft.
>
> Yes, one that introduces even local PE VRF-VRF connectivity
> reliance on upstream RRs..

As we've discussed already.  I don't think this point is any different?

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


From idr-bounces@ietf.org  Wed Apr 30 16:19:05 2008
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 628723A68F3;
	Wed, 30 Apr 2008 16:19:05 -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 B841A3A6A33
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 16:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 xS14+7rwJsgP for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 16:19:03 -0700 (PDT)
Received: from mx4.ca.afilias.info (vgateway.libertyrms.info [207.219.45.62])
	by core3.amsl.com (Postfix) with ESMTP id BF07C3A68F3
	for <idr@ietf.org>; Wed, 30 Apr 2008 16:19:02 -0700 (PDT)
Received: from briand-vpn.int.libertyrms.com ([10.1.7.90])
	by mx4.ca.afilias.info with esmtp (Exim 4.22)
	id 1JrLZT-0004wa-Kl; Wed, 30 Apr 2008 19:18:43 -0400
Message-ID: <4818FEC1.4050308@ca.afilias.info>
Date: Wed, 30 Apr 2008 19:20:33 -0400
From: Brian Dickson <briand@ca.afilias.info>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: "John G. Scudder" <jgs@bgp.nu>
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu><4686A93B-EF16-48DC-9775-1BD241575360@tcb.net><4818D897.3070804@cisco.com><DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net><4818DB47.8040002@cisco.com><82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net><4818DCFC.70001@cisco.com>	<8D3C8A4B-B80B-4983-8DC7-A142FFA4B41C@tcb.net>	<4818ECF1.1030909@juniper.net>	<157A9EDC-B512-4C05-A257-72D70DFB44FA@tcb.net>
	<E41B60B6-6B6C-4EF1-9170-BDAAE23B9D7E@bgp.nu>
In-Reply-To: <E41B60B6-6B6C-4EF1-9170-BDAAE23B9D7E@bgp.nu>
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
Cc: idr idr <idr@ietf.org>, Danny McPherson <danny@tcb.net>
Subject: Re: [Idr]
	Fwd:I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

John G. Scudder wrote:
> On Apr 30, 2008, at 6:39 PM, Danny McPherson wrote:
>   
>> Traffic wasn't the issue.  It's more CPU, memory, etc..  Just
>> because it's available doesn't mean it's free.
>>     
>
> Regarding memory, it needn't be consumed for a this-is-my-own-route  
> path.  (It may be, but this is an implementation decision.)
>
>   

You need to be careful about steady-state memory usage vs 
high-water-mark memory usage.
Processing updates chews memory *prior* to installation of entries in 
various RIBs/FIBs, and
unless you have an excess of CPU power (and can handle line-rate packets 
in the slow path),
it isn't possible to feasibly pre-filter without degrading performance.

And not pre-filtering means memory gets hit on the transient prior to 
discarding this-is-my-own-route.

> Regarding CPU, remember that you want to optimize the bottleneck,  
> nothing else matters really.  In most cases, the RR is the control  
> plane bottleneck.  Loading it up more to protect the CPUs of non- 
> bottleneck devices seems like an odd design decision.
>
>   

The red flag has gone up. Using the term "*the* bottleneck" means you 
don't understand the nature
of complex systems. Yes, there will *always* be a bottleneck. However, 
solving for one bottleneck
will *always* move the bottleneck to some other place. It may be 
acceptable for a stable state with
several equally-pernicious bottlenecks affecting the system, or to move 
the bottleneck to a portion of
the solution space that scales best (e.g. one that scales as O(n log n) 
vs one that scales as O(n^2).

The two other points I'd like to make, are, that:
(1) saying "in most cases" is the same as saying "it's not always the 
case". Solving for one case without
considering other cases is very short-sighted and can cause unforseen 
consequences. It is much better
to *consider* those cases, explicitly, and discuss whether and to what 
degree they would get affected; and

(2) keep in mind - an RR is *strictly* control plane. It is possible for 
it to reside on a device that also does
data plane stuff. However, if RR performance is a huge deal, throwing 
*computer* hardware at it, rather
than *router* hardware at it, is an entirely feasible solution - with 
likely higher (by orders of magnitude)
ceiling on performance that can be bought, and likely at much lower 
price point than equivalent router vendor
RR solutions. RR can achieve equivalent topological solutions (and thus 
avoid topological variance versus
router-based RR's) by sitting as a one-armed device hanging off a core 
router.

There is something to very much consider, however:
RR's are fundamentally required to achieve suitable scaling on big 
non-VPN networks.
Please keep those networks in mind when messing about with core BGP 
protocols.

(Never mind that I'm working on something to *really* mess with those 
same core BGP protocols... but with good reason. :-) )

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


From idr-bounces@ietf.org  Wed Apr 30 16:34:45 2008
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 982473A6A2A;
	Wed, 30 Apr 2008 16:34:45 -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 92B9C3A6A2A
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 16:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 bPye1RHH4rrn for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 16:34:43 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155])
	by core3.amsl.com (Postfix) with ESMTP id F016A3A677D
	for <idr@ietf.org>; Wed, 30 Apr 2008 16:34:42 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob101.postini.com
	([64.18.6.12]) with SMTP; Wed, 30 Apr 2008 16:34:45 PDT
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Apr 2008 16:30:36 -0700
Received: from [172.26.250.99] ([172.26.250.99])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m3UNUZx19769;
	Wed, 30 Apr 2008 16:30:35 -0700 (PDT)
	(envelope-from raszuk@juniper.net)
Message-ID: <48190119.60705@juniper.net>
Date: Wed, 30 Apr 2008 16:30:33 -0700
From: Robert Raszuk <raszuk@juniper.net>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Danny McPherson <danny@tcb.net>
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu><4686A93B-EF16-48DC-9775-1BD241575360@tcb.net><4818D897.3070804@cisco.com><DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net><4818DB47.8040002@cisco.com><82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net><4818DCFC.70001@cisco.com>
	<8D3C8A4B-B80B-4983-8DC7-A142FFA4B41C@tcb.net>
	<4818ECF1.1030909@juniper.net>
	<157A9EDC-B512-4C05-A257-72D70DFB44FA@tcb.net>
In-Reply-To: <157A9EDC-B512-4C05-A257-72D70DFB44FA@tcb.net>
X-OriginalArrivalTime: 30 Apr 2008 23:30:36.0953 (UTC)
	FILETIME=[3196E090:01C8AB1A]
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr]
	Fwd:I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@juniper.net
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Danny,

>  > It is very cheap and easy to drop the unneeded route on inbound 
>  > while it is very CPU intensive to build separate updates to each peer.
> 
> Really?  Where's the line drawn?  What about when there are
> one million updates being dropped?  I could probably make a
> case for this today?  What about legit updates queued behind
> these?

Let me address your concerns one by one ...

* The line is drawn when you have 100s of PEs to send the same 
information to.

* The milion updates to be dropped .... Clearly you must be talking 
about VPN routes. If so there are hardly single PE with milion routes to 
  make such a case today. Total number of routes yes but this draft is 
orthogonal to this. You are complaining about the 2796 case again here.

* Each PE can today receive only legit updates with or without of this 
draft including RRs support for 2796. There are well know standard based 
technics for this example: rfc4684.

Can you tell us how your argument holds when you support rfc4684 ?

>  > With current link bandwith the amount of traffic generated due to that
>  > is just white noise.
> 
> Traffic wasn't the issue.  It's more CPU, memory, etc..  Just
> because it's available doesn't mean it's free.

Memory is just a transient memory. If your CPU suffers with inbound 
filtering I think there are much bigger issues behind the scenes.

Keep in mind that discussed here draft does not increase number of 
routes each PE would receive even by a single one. All of your points 
Danny flame the issue of reflecting back the information to the client 
which were originated by it before. Perhaps this is a valid theoretical 
complain but it is just out of this topic. And as said before this is 
all for VPN space where this problem has already been addressed by rfc4684.

>  > There are practical applications for this enhancement of which one is
>  > described in the draft.
> 
> Yes, one that introduces even local PE VRF-VRF connectivity
> reliance on upstream RRs..

You are missing the big picture :) This is to provide functional 
consistency ... RR will propagate the same very update to all PE - which 
very often are in hundreds or maybe thousands of today's large 
providers. Only one of them originated the route .. appending this new 
community will not have any impact in all of the PEs .. only in the 
originator which will accept the route and perform required action which 
will be consistent with all other PEs in the network.

>  > As general rule of thumb I think there is need to support more
>  > automation in the network provisioning among many providers. There is
>  > also a demand in the market for more dynamic behavior of running
>  > applications. This is just right on this spot attempt to support one 
>  > of
>  > them.
> 
> Perhaps, but I think it ugly because of both clean routing hygiene
> issues, and the network architectural fault considerations I've already
> outlined.

Recently we have had hussars bashing "BGP overload" ... now in 2008 
perhaps we see a new trend "routing hygiene". So can you spell what is 
so unhygienic in this draft ? All points you have brought so far talk 
about solved issue (in the VPN space) if reflecting unneeded routes to 
PEs ... but non of your points refer to this draft. Can you put in 
points how this draft make this any worse ?

Cheers,
R.

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


From idr-bounces@ietf.org  Wed Apr 30 16:52:58 2008
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 E62563A6A76;
	Wed, 30 Apr 2008 16:52:57 -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 C7DCF3A63EC
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 16:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053, 
	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 khCCUO+S2Oan for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 16:52:56 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 170263A69A1
	for <idr@ietf.org>; Wed, 30 Apr 2008 16:52:56 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0)
	id AE5CE2680D7; Wed, 30 Apr 2008 17:52:58 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET
	[151.118.146.11]) (authenticated-user smtp)
	(TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP;
	Wed, 30 Apr 2008 17:52:58 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11;
	client-port=57364; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <F95B588A-D821-4FFD-BD5F-8A4721FB18A4@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: raszuk@juniper.net
In-Reply-To: <48190119.60705@juniper.net>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 17:52:42 -0600
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu><4686A93B-EF16-48DC-9775-1BD241575360@tcb.net><4818D897.3070804@cisco.com><DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net><4818DB47.8040002@cisco.com><82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net><4818DCFC.70001@cisco.com>
	<8D3C8A4B-B80B-4983-8DC7-A142FFA4B41C@tcb.net>
	<4818ECF1.1030909@juniper.net>
	<157A9EDC-B512-4C05-A257-72D70DFB44FA@tcb.net>
	<48190119.60705@juniper.net>
X-Mailer: Apple Mail (2.919.2)
Cc: idr idr <idr@ietf.org>
Subject: Re: [Idr]
	Fwd:I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


Regarding all your other text, I don't have any new points
to make and haven't changed my position, so I'll avoid
further discussion on that.

> Recently we have had hussars bashing "BGP overload" ... now in 2008
> perhaps we see a new trend "routing hygiene". So can you spell what is
> so unhygienic in this draft ? All points you have brought so far talk
> about solved issue (in the VPN space) if reflecting unneeded routes to
> PEs ... but non of your points refer to this draft. Can you put in
> points how this draft make this any worse ?

It's "be liberal in what you accept, conservative in what you
send", NOT "be liberal in what you send because others
are liberal in what they accept" :-)

I understand the utility of your proposal, I understand why
you selected the mechanism you did.  My concern is that all
these tweaks have system-wide implications, and we all
need to be cognizant of that when proposing solutions to
problems operators have.

-danny







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


From idr-bounces@ietf.org  Wed Apr 30 18:15:49 2008
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 6AD563A6A91;
	Wed, 30 Apr 2008 18:15:49 -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 15A533A6A91
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 18:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.835
X-Spam-Level: 
X-Spam-Status: No, score=-5.835 tagged_above=-999 required=5 tests=[AWL=0.764, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 EHq3h8O79pCN for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 18:15:46 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177])
	by core3.amsl.com (Postfix) with ESMTP id 9CB343A6BC2
	for <idr@ietf.org>; Wed, 30 Apr 2008 18:15:45 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob112.postini.com
	([64.18.6.12]) with SMTP; Wed, 30 Apr 2008 18:15:46 PDT
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 30 Apr 2008 18:15:10 -0700
Received: from [172.16.13.201] ([172.16.13.201])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m411F9x49219;
	Wed, 30 Apr 2008 18:15:09 -0700 (PDT) (envelope-from jgs@juniper.net)
Message-Id: <80344ED8-5C18-48A7-ABDA-2063A63DEBCB@juniper.net>
From: "John G. Scudder" <jgs@juniper.net>
To: Brian Dickson <briand@ca.afilias.info>
In-Reply-To: <4818FEC1.4050308@ca.afilias.info>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 21:15:07 -0400
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu><4686A93B-EF16-48DC-9775-1BD241575360@tcb.net><4818D897.3070804@cisco.com><DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net><4818DB47.8040002@cisco.com><82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net><4818DCFC.70001@cisco.com>	<8D3C8A4B-B80B-4983-8DC7-A142FFA4B41C@tcb.net>	<4818ECF1.1030909@juniper.net>	<157A9EDC-B512-4C05-A257-72D70DFB44FA@tcb.net>
	<E41B60B6-6B6C-4EF1-9170-BDAAE23B9D7E@bgp.nu>
	<4818FEC1.4050308@ca.afilias.info>
X-Mailer: Apple Mail (2.919.2)
X-OriginalArrivalTime: 01 May 2008 01:15:10.0268 (UTC)
	FILETIME=[CCC6C7C0:01C8AB28]
Cc: idr idr <idr@ietf.org>, Danny McPherson <danny@tcb.net>
Subject: [Idr] Route reflectors [was: Re:
	Fwd:I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt]
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

I've changed the subject line since we have drifted far afield from  
discussion of draft-pmohapat-idr-acceptown-community-01.txt.

On Apr 30, 2008, at 7:20 PM, Brian Dickson wrote:
> John G. Scudder wrote:
>> On Apr 30, 2008, at 6:39 PM, Danny McPherson wrote:
>>> Traffic wasn't the issue.  It's more CPU, memory, etc..  Just
>>> because it's available doesn't mean it's free.
>>
>> Regarding memory, it needn't be consumed for a this-is-my-own- 
>> route  path.  (It may be, but this is an implementation decision.)
>
> You need to be careful about steady-state memory usage vs high-water- 
> mark memory usage.
> Processing updates chews memory *prior* to installation of entries  
> in various RIBs/FIBs, and
> unless you have an excess of CPU power (and can handle line-rate  
> packets in the slow path),
> it isn't possible to feasibly pre-filter without degrading  
> performance.
>
> And not pre-filtering means memory gets hit on the transient prior  
> to discarding this-is-my-own-route.

I have in-depth familiarity with several well-known BGP  
implementations, and I haven't the slightest idea what you're talking  
about.

>> Regarding CPU, remember that you want to optimize the bottleneck,   
>> nothing else matters really.  In most cases, the RR is the control   
>> plane bottleneck.  Loading it up more to protect the CPUs of non-  
>> bottleneck devices seems like an odd design decision.
>
> The red flag has gone up. Using the term "*the* bottleneck" means  
> you don't understand the nature
> of complex systems.

Tempting though it may be to pick up the gauntlet and enter into a  
full scale flame war, I hope you won't mind if I try to confine myself  
to the substance of your remarks rather than their tone.

> Yes, there will *always* be a bottleneck. However, solving for one  
> bottleneck
> will *always* move the bottleneck to some other place. It may be  
> acceptable for a stable state with
> several equally-pernicious bottlenecks affecting the system, or to  
> move the bottleneck to a portion of
> the solution space that scales best (e.g. one that scales as O(n log  
> n) vs one that scales as O(n^2).

Yes, this is algorithms 101.  I was making a rather simple point  
regarding networks as systems, viz the fact that if you've got one RR  
feeding a large number of clients, the RR usually needs to process a  
lot more stuff than the clients do.  It has N >> 1 peers (the clients  
and non-client peers); they have M << N peers (the RR, likely a  
redundant RR, and probably a smaller number of external peers).   
Granted that this isn't universally true, but one has to design to  
something and this would seem to be the common case.

It's rather grandiose to describe the issue under discussion (which,  
I'll remind you, is a tangent having to do with route reflection and  
the differences between RFC 1966 and RFC 2796) as an attempt to "solve  
for [the] bottleneck".  While a "solution" would be nice, I think most  
would settle for just increasing the bottleneck's diameter. :-)  In  
any event, this is water which ran under the bridge a long time ago.

> The two other points I'd like to make, are, that:
> (1) saying "in most cases" is the same as saying "it's not always  
> the case".

Well, yeah.

> Solving for one case without
> considering other cases is very short-sighted and can cause  
> unforseen consequences.

Thank you for this insight, I will strive to bear it in mind.

> It is much better
> to *consider* those cases, explicitly, and discuss whether and to  
> what degree they would get affected; and

Please feel free to redesign route reflection to be optimal in all  
cases if you have the time to spare!  Absent a really interesting  
point being raised, I'll probably refrain from further discussion of  
this topic myself though, since as I mentioned, this is water under  
the bridge.

> (2) keep in mind - an RR is *strictly* control plane. It is possible  
> for it to reside on a device that also does
> data plane stuff. However, if RR performance is a huge deal,  
> throwing *computer* hardware at it, rather
> than *router* hardware at it, is an entirely feasible solution -  
> with likely higher (by orders of magnitude)
> ceiling on performance that can be bought, and likely at much lower  
> price point than equivalent router vendor
> RR solutions. RR can achieve equivalent topological solutions (and  
> thus avoid topological variance versus
> router-based RR's) by sitting as a one-armed device hanging off a  
> core router.

OK.

> There is something to very much consider, however:
> RR's are fundamentally required

If you are going to insist on precision in the use of language, you  
should be careful with expressions like "fundamentally required".

> to achieve suitable scaling on big non-VPN networks.
> Please keep those networks in mind when messing about with core BGP  
> protocols.

I have some familiarity with the networks you are speaking of.  And to  
repeat one more time lest the confusion continue, the draft originally  
under discussion isn't about route reflection other than tangentially.

> (Never mind that I'm working on something to *really* mess with  
> those same core BGP protocols...

Yes, the first draft was interesting and I look forward to seeing the  
next draft.

> but with good reason. :-) )

That remains to be proven though it's an intriguing hypothesis.

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


From idr-bounces@ietf.org  Wed Apr 30 19:50:43 2008
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 B34A53A6B1C;
	Wed, 30 Apr 2008 19:50:43 -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 C84D53A6B1C
	for <idr@core3.amsl.com>; Wed, 30 Apr 2008 19:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.849
X-Spam-Level: 
X-Spam-Status: No, score=-5.849 tagged_above=-999 required=5 tests=[AWL=0.750, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 URbfkqCANOHf for <idr@core3.amsl.com>;
	Wed, 30 Apr 2008 19:50:40 -0700 (PDT)
Received: from mx4.ca.afilias.info (vgateway.libertyrms.info [207.219.45.62])
	by core3.amsl.com (Postfix) with ESMTP id 887E93A6A68
	for <idr@ietf.org>; Wed, 30 Apr 2008 19:50:40 -0700 (PDT)
Received: from briand-vpn.int.libertyrms.com ([10.1.7.90])
	by mx4.ca.afilias.info with esmtp (Exim 4.22)
	id 1JrOsb-0005lo-4d; Wed, 30 Apr 2008 22:50:41 -0400
Message-ID: <4819306E.8090106@ca.afilias.info>
Date: Wed, 30 Apr 2008 22:52:30 -0400
From: Brian Dickson <briand@ca.afilias.info>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: "John G. Scudder" <jgs@juniper.net>
References: <20080425213001.4EB133A69E7@core3.amsl.com>	<64E4CA6A-B8E4-4390-BDA6-39EF28E95AEA@tcb.net>	<7000E71D8C525042A815432358B2F1240138D45E@paul.adoffice.local.de.easynet.net>	<DE879141-E245-4051-A04D-9FF5CF97F892@bgp.nu>	<39074353-26E5-4239-A193-E4DD84AE75A0@tcb.net>	<014A2382-C5CE-4657-B4DA-FC84D7772359@bgp.nu><4686A93B-EF16-48DC-9775-1BD241575360@tcb.net><4818D897.3070804@cisco.com><DC5EBA07-BBE5-4D6D-9F3E-C40C66ACE34B@tcb.net><4818DB47.8040002@cisco.com><82B7CFF7-86CB-4DC7-BE53-29004128B5CB@tcb.net><4818DCFC.70001@cisco.com>	<8D3C8A4B-B80B-4983-8DC7-A142FFA4B41C@tcb.net>	<4818ECF1.1030909@juniper.net>	<157A9EDC-B512-4C05-A257-72D70DFB44FA@tcb.net>
	<E41B60B6-6B6C-4EF1-9170-BDAAE23B9D7E@bgp.nu>
	<4818FEC1.4050308@ca.afilias.info>
	<80344ED8-5C18-48A7-ABDA-2063A63DEBCB@juniper.net>
In-Reply-To: <80344ED8-5C18-48A7-ABDA-2063A63DEBCB@juniper.net>
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
Cc: idr idr <idr@ietf.org>, Danny McPherson <danny@tcb.net>
Subject: Re: [Idr] Route reflectors [was: Re:
	Fwd:I-D	ACTION:draft-pmohapat-idr-acceptown-community-01.txt]
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

John G. Scudder wrote:
> I've changed the subject line since we have drifted far afield from 
> discussion of draft-pmohapat-idr-acceptown-community-01.txt.
>
> On Apr 30, 2008, at 7:20 PM, Brian Dickson wrote:
>> John G. Scudder wrote:
>>> On Apr 30, 2008, at 6:39 PM, Danny McPherson wrote:
>>>
>>
>> The red flag has gone up. Using the term "*the* bottleneck" means you 
>> don't understand the nature
>> of complex systems.
>
> Tempting though it may be to pick up the gauntlet and enter into a 
> full scale flame war, I hope you won't mind if I try to confine myself 
> to the substance of your remarks rather than their tone.
>

Thanks. My comment was using "you" in the sense of "one", rather than 
you personally. No flame war was intended. :-)

>> Yes, there will *always* be a bottleneck. However, solving for one 
>> bottleneck
>> will *always* move the bottleneck to some other place. It may be 
>> acceptable for a stable state with
>> several equally-pernicious bottlenecks affecting the system, or to 
>> move the bottleneck to a portion of
>> the solution space that scales best (e.g. one that scales as O(n log 
>> n) vs one that scales as O(n^2).
>
> Yes, this is algorithms 101.

I wish it *were* 101, sadly, I suspect it is more along the lines of 
601, i.e. second year grad level, based on the frequency with which I 
see poorly designed (rather than merely poorly implemented) systems.

> I was making a rather simple point regarding networks as systems, viz 
> the fact that if you've got one RR feeding a large number of clients, 
> the RR usually needs to process a lot more stuff than the clients do.  
> It has N >> 1 peers (the clients and non-client peers); they have M << 
> N peers (the RR, likely a redundant RR, and probably a smaller number 
> of external peers).  Granted that this isn't universally true, but one 
> has to design to something and this would seem to be the common case.

There's more than one way to improve the performance and scalability of 
RR's.

For instance, in most of the networks I've built and run, and many 
others that I'm quite familiar with, there wasn't client-client 
reflection - for both performance concerns, as well as for the 
topological aspects, where in order to guarantee the RR makes a suitably 
sensible choice, it needs to also be in the data path.
If you have clients that see each other directly, and that bypass the 
box that is the RR, then client-client reflection can do seriously weird 
stuff even when you know what you're doing.

And, it also matters where you do policy stuff. If you put your policy 
stuff on the edges of your AS, then the RR's can be almost trivial, 
without touching updates beyond adding/changing the RR-specific bits, 
and possibly seeing further optimizations based on peer-groups.

My experience has been that for similar-class boxes acting as core and 
border routers, and core routers doing double duty as RRs, that you get 
the best bang for the buck when N is about the same as M. And not just 
because of RR scaling issues, but also because of the proportion of 
revenue-generating ports and boxes versus overhead ports and boxes.

>
> Please feel free to redesign route reflection to be optimal in all 
> cases if you have the time to spare!  Absent a really interesting 
> point being raised, I'll probably refrain from further discussion of 
> this topic myself though, since as I mentioned, this is water under 
> the bridge.
>

Ha ha ha! :-)

(I actually did start looking into RR design alternatives, and gained a 
real respect for the original authors of BGP. The implementation is 
easy, only because the underlying design got things right. Any deviation 
from the basics on how BGP works, gets really hairy really fast.)

>> There is something to very much consider, however:
>> RR's are fundamentally required
>
> If you are going to insist on precision in the use of language, you 
> should be careful with expressions like "fundamentally required".

I am (careful, that is).

For IBGP, there are obvious points at which the operational cost and 
overhead of having a full mesh, becomes excessive.
Without RRs, there are O(n^2) peering sessions, all of which are 
required to be properly configured to guarantee things work properly.
For a border router with (worst case) a single backhaul link to the rest 
of the AS, for every inbound EBGP update, there need to be N IBGP updates.
At the observed rate of thrash, for any given pipe size there is a 
corresponding value N at which updates more than fill the pipe, leading 
to congestive network collapse.

And, regardless of network size and thrash rate, as long as the pipe 
size is big enough to handle a single update stream without regularly 
congesting, an RR topology can be built to handle the network size and 
all updates.

That's what I mean when I say "fundamentally required" - that it is both 
necessary and sufficient, for arbitrarily large networks, to have RRs 
deployed to avoid congestive collapse.

But, I'm positive you already know all of what I just wrote.
(The words were for the benefit of anyone else that might wonder what I 
meant by "fundamentally required".)

>
>> (Never mind that I'm working on something to *really* mess with those 
>> same core BGP protocols...
>
> Yes, the first draft was interesting and I look forward to seeing the 
> next draft.
>

Thanks. (I've been trying to get permission from the authors of the 
"add-paths" draft to re-use it and augment it.)

>> but with good reason. :-) )
>
> That remains to be proven though it's an intriguing hypothesis.

I agree, and I hope to be able to produce convincing demonstrations of 
it, in due time.

I realize that until something of substance is available, it's academic; 
it took a bit of work to convince myself that it worked.

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


