
From internet-drafts@ietf.org  Thu Sep 15 06:59:37 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA5A21F8B19; Thu, 15 Sep 2011 06:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.404
X-Spam-Level: 
X-Spam-Status: No, score=-102.404 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A6Ch3Ivwnpyq; Thu, 15 Sep 2011 06:59:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A48D21F8B13; Thu, 15 Sep 2011 06:59:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.60
Message-ID: <20110915135937.20309.65730.idtracker@ietfa.amsl.com>
Date: Thu, 15 Sep 2011 06:59:37 -0700
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-optimal-route-reflection-01.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Sep 2011 13:59:37 -0000

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

	Title           : BGP Optimal Route Reflection (BGP-ORR)
	Author(s)       : Robert Raszuk
                          Christian Cassar
                          Erik Aman
                          Bruno Decraene
	Filename        : draft-ietf-idr-bgp-optimal-route-reflection-01.txt
	Pages           : 19
	Date            : 2011-09-15

   [RFC4456] asserts that, because the Interior Gateway Protocol (IGP)
   cost to a given point in the network will vary across routers, &quot;the
   route reflection approach may not yield the same route selection
   result as that of the full IBGP mesh approach.&quot;  One practical
   implication of this assertion is that the deployment of route
   reflection may thwart the ability to achieve hot potato routing.  Hot
   potato routing attempts to direct traffic to the closest AS egress
   point in cases where no higher priority policy dictates otherwise.
   As a consequence of the route reflection method, the choice of exit
   point for a route reflector and its clients will be the egress point
   closest to the route reflector - and not necessarily closest to the
   RR clients.

   Section 11 of [RFC4456] describes a deployment approach and a set of
   constraints which, if satsified, would result in the deployment of
   route reflection yielding the same results as the iBGP full mesh
   approach.  Such a deployment approach would make route reflection
   compatible with the application of hot potato routing policy.

   As networks evolved to accommodate architectural requirements of new
   services, tunneled (LSP/IP tunneling) networks with centralized route
   reflectors became commonplace.  This is one type of common deployment
   where it would be impractical to satisfy the constraints described in
   Section 11 of [RFC4456].  Yet, in such an environment, hot potato
   routing policy remains desirable.

   This document proposes two new solutions which can be deployed to
   facilitate the application of closest exit point policy centralized
   route reflection deployments.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-optimal-route-reflec=
tion-01.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-idr-bgp-optimal-route-reflect=
ion-01.txt

From internet-drafts@ietf.org  Thu Sep 15 16:42:30 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BAFB11E8086; Thu, 15 Sep 2011 16:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.882
X-Spam-Level: 
X-Spam-Status: No, score=-98.882 tagged_above=-999 required=5 tests=[AWL=3.718, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EN-mFOX5cYLT; Thu, 15 Sep 2011 16:42:29 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB6BE21F8B46; Thu, 15 Sep 2011 16:42:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.60
Message-ID: <20110915234229.31818.48282.idtracker@ietfa.amsl.com>
Date: Thu, 15 Sep 2011 16:42:29 -0700
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-add-paths-06.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Sep 2011 23:42:30 -0000

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

	Title           : Advertisement of Multiple Paths in BGP
	Author(s)       : Daniel Walton
                          Enke Chen
                          Alvaro Retana
                          John Scudder
	Filename        : draft-ietf-idr-add-paths-06.txt
	Pages           : 8
	Date            : 2011-09-15

   In this document we propose a BGP extension that allows the
   advertisement of multiple paths for the same address prefix without
   the new paths implicitly replacing any previous ones.  The essence of
   the extension is that each path is identified by a path identifier in
   addition to the address prefix.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-add-paths-06.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-idr-add-paths-06.txt

From ilya@nobulus.com  Tue Sep 20 00:08:28 2011
Return-Path: <ilya@nobulus.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAC021F8A56 for <idr@ietfa.amsl.com>; Tue, 20 Sep 2011 00:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L2PJoie+98Yy for <idr@ietfa.amsl.com>; Tue, 20 Sep 2011 00:08:28 -0700 (PDT)
Received: from nobulus.com (nobulus.com [IPv6:2001:6f8:892:6ff::11:152]) by ietfa.amsl.com (Postfix) with ESMTP id D838D21F8A4E for <idr@ietf.org>; Tue, 20 Sep 2011 00:08:26 -0700 (PDT)
Received: from nobulus.com (localhost [127.0.0.1]) by nobulus.com (Postfix) with ESMTP id D77C3174E3 for <idr@ietf.org>; Tue, 20 Sep 2011 09:10:48 +0200 (CEST)
X-Virus-Scanned: amavisd-new at nobulus.com
Received: from nobulus.com ([127.0.0.1]) by nobulus.com (nobulus.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id EX62+dipGOWE for <idr@ietf.org>; Tue, 20 Sep 2011 09:10:47 +0200 (CEST)
Received: from hnivarlas1 (unknown [IPv6:2001:6f8:892:6f8:e5e8:3ac8:5411:865b]) by nobulus.com (Postfix) with ESMTPA id D0C5A174D8 for <idr@ietf.org>; Tue, 20 Sep 2011 09:10:44 +0200 (CEST)
Message-ID: <8A40E55A626749F6AEA72EB24BD844EE@hnivarlas1>
From: "iLya" <ilya@nobulus.com>
To: <idr@ietf.org>
Date: Tue, 20 Sep 2011 09:10:41 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8117.416
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416
Subject: [Idr] optional transitive - recognised but out of context
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2011 07:08:28 -0000

Hi,

yesterday and few days earlier several people have observed their BGP 
sessions being reset after seeing certain prefix. After some evaluation I've 
found that offending prefix (in global internet table) had optional 
transitive ATTR_SET (code 128) attached. Not having first hand access to 
platforms that exhibited session reset I'm speculating that they've 
recognised attribute as such but found it to be inappropriate for given 
context and so treated update as malformed with all consequences.

BGP specs seem to have only one place that could (with some stretching) 
justify such behaviour - from rfc4271#section-6.3 "...If an optional 
attribute is recognized, then the value of this attribute MUST be 
checked...". Wouldn't it be appropriate to add extra text that would clarify 
that optional transitive attributes out of context should not result in 
session reset?

P.S.: as far as I understood problematic BGP implementation is fixed in 
later software releases, but lack of clarity in BGP specs leaves room for 
similar problems in the future

Cheers,
iLya
 


From robert@raszuk.net  Tue Sep 20 00:33:02 2011
Return-Path: <robert@raszuk.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEDA621F85A4 for <idr@ietfa.amsl.com>; Tue, 20 Sep 2011 00:33:02 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29OdIFT3DwNQ for <idr@ietfa.amsl.com>; Tue, 20 Sep 2011 00:33:02 -0700 (PDT)
Received: from mail37.opentransfer.com (mail37.opentransfer.com [76.162.254.37]) by ietfa.amsl.com (Postfix) with SMTP id B37AE21F84CF for <idr@ietf.org>; Tue, 20 Sep 2011 00:33:01 -0700 (PDT)
Received: (qmail 13535 invoked by uid 399); 20 Sep 2011 07:35:26 -0000
Received: from unknown (HELO ?216.69.73.190?) (216.69.73.190) by mail37.opentransfer.com with SMTP; 20 Sep 2011 07:35:26 -0000
Message-ID: <4E78423D.9090403@raszuk.net>
Date: Tue, 20 Sep 2011 09:35:25 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: iLya <ilya@nobulus.com>
References: <8A40E55A626749F6AEA72EB24BD844EE@hnivarlas1>
In-Reply-To: <8A40E55A626749F6AEA72EB24BD844EE@hnivarlas1>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: idr@ietf.org
Subject: Re: [Idr] optional transitive - recognised but out of context
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2011 07:33:02 -0000

Hi Ilya,

Do you think that the below draft still does not formally address the 
problem you are describing ?

http://tools.ietf.org/html/draft-ietf-idr-optional-transitive-03

Cheers,
R.

> Hi,
>
> yesterday and few days earlier several people have observed their BGP
> sessions being reset after seeing certain prefix. After some evaluation
> I've found that offending prefix (in global internet table) had optional
> transitive ATTR_SET (code 128) attached. Not having first hand access to
> platforms that exhibited session reset I'm speculating that they've
> recognised attribute as such but found it to be inappropriate for given
> context and so treated update as malformed with all consequences.
>
> BGP specs seem to have only one place that could (with some stretching)
> justify such behaviour - from rfc4271#section-6.3 "...If an optional
> attribute is recognized, then the value of this attribute MUST be
> checked...". Wouldn't it be appropriate to add extra text that would
> clarify that optional transitive attributes out of context should not
> result in session reset?
>
> P.S.: as far as I understood problematic BGP implementation is fixed in
> later software releases, but lack of clarity in BGP specs leaves room
> for similar problems in the future
>
> Cheers,
> iLya
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
>


From ilya@nobulus.com  Tue Sep 20 01:37:05 2011
Return-Path: <ilya@nobulus.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E94AD21F84A8 for <idr@ietfa.amsl.com>; Tue, 20 Sep 2011 01:37:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cE-zLEMEWrmG for <idr@ietfa.amsl.com>; Tue, 20 Sep 2011 01:37:05 -0700 (PDT)
Received: from nobulus.com (nobulus.com [IPv6:2001:6f8:892:6ff::11:152]) by ietfa.amsl.com (Postfix) with ESMTP id 65A9621F84A7 for <idr@ietf.org>; Tue, 20 Sep 2011 01:37:05 -0700 (PDT)
Received: from nobulus.com (localhost [127.0.0.1]) by nobulus.com (Postfix) with ESMTP id 2EE871751A; Tue, 20 Sep 2011 10:39:30 +0200 (CEST)
X-Virus-Scanned: amavisd-new at nobulus.com
Received: from nobulus.com ([127.0.0.1]) by nobulus.com (nobulus.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xgTtrjvIYnh8; Tue, 20 Sep 2011 10:39:24 +0200 (CEST)
Received: from hnivarlas1 (unknown [IPv6:2001:6f8:892:6f8:e5e8:3ac8:5411:865b]) by nobulus.com (Postfix) with ESMTPA id 7F93917505; Tue, 20 Sep 2011 10:39:22 +0200 (CEST)
Message-ID: <6F5D87D5A529438AA45660713933A2CF@hnivarlas1>
From: "iLya" <ilya@nobulus.com>
To: <robert@raszuk.net>, <idr@ietf.org>
References: <8A40E55A626749F6AEA72EB24BD844EE@hnivarlas1> <4E78423D.9090403@raszuk.net>
In-Reply-To: <4E78423D.9090403@raszuk.net>
Date: Tue, 20 Sep 2011 10:39:19 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8117.416
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416
Subject: Re: [Idr] optional transitive - recognised but out of context
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2011 08:37:06 -0000

Hi Robert,

--------------------------------------------------
> Do you think that the below draft still does not formally address the 
> problem you are describing ?
>
> http://tools.ietf.org/html/draft-ietf-idr-optional-transitive-03
>

it goes in the right direction but stops short of saying whether recognised 
optional transitive attribute (partial or not) properly formed but out of 
context (e.g. L3VPN-specific attribute in global table) is an error or not. 
If authors of draft-ietf-idr-optional-transitive-03 consider the problem 
I've described to be within scope of the draft and could address it more 
explicitly, that would do.

Cheers,
iLya
 


From jalcaide@cisco.com  Tue Sep 20 04:47:04 2011
Return-Path: <jalcaide@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7842921F87D6 for <idr@ietfa.amsl.com>; Tue, 20 Sep 2011 04:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cH-HnOj1XYya for <idr@ietfa.amsl.com>; Tue, 20 Sep 2011 04:47:04 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by ietfa.amsl.com (Postfix) with ESMTP id DBA0821F8546 for <idr@ietf.org>; Tue, 20 Sep 2011 04:47:03 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p8KBnSpV019280 for <idr@ietf.org>; Tue, 20 Sep 2011 07:49:28 -0400 (EDT)
Received: from clubhouse-4.cisco.com (clubhouse-4.cisco.com [64.100.21.4]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p8KBnRVW027347; Tue, 20 Sep 2011 07:49:27 -0400 (EDT)
Date: Tue, 20 Sep 2011 07:49:27 -0400 (EDT)
From: Juan Alcaide <jalcaide@cisco.com>
To: iLya <ilya@nobulus.com>
In-Reply-To: <6F5D87D5A529438AA45660713933A2CF@hnivarlas1>
Message-ID: <alpine.GSO.2.00.1109200731480.3974@clubhouse-4.cisco.com>
References: <8A40E55A626749F6AEA72EB24BD844EE@hnivarlas1> <4E78423D.9090403@raszuk.net> <6F5D87D5A529438AA45660713933A2CF@hnivarlas1>
User-Agent: Alpine 2.00 (GSO 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: idr@ietf.org, robert@raszuk.net
Subject: Re: [Idr] optional transitive - recognised but out of context
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2011 11:47:04 -0000

iLya,

As I read it:

The draft only deals with malformed attributes. So it doesn't apply

To deal with optional attributes that are recognized, you have to refer to 
specific RFC/describing the specific attribute. For some attributes, it 
may be ok to reset, for others not. RFC4271:6.3 won't tell you what to do 
about an attribute that it's not defined there.

Unfortunately, this part is often missed.

2c,

-Juan

On Tue, 20 Sep 2011, iLya wrote:

> Hi Robert,
>
> --------------------------------------------------
>> Do you think that the below draft still does not formally address the 
>> problem you are describing ?
>> 
>> http://tools.ietf.org/html/draft-ietf-idr-optional-transitive-03
>> 
>
> it goes in the right direction but stops short of saying whether recognised 
> optional transitive attribute (partial or not) properly formed but out of 
> context (e.g. L3VPN-specific attribute in global table) is an error or not. 
> If authors of draft-ietf-idr-optional-transitive-03 consider the problem I've 
> described to be within scope of the draft and could address it more 
> explicitly, that would do.
>
> Cheers,
> iLya
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
>

From paul@jakma.org  Tue Sep 20 05:42:11 2011
Return-Path: <paul@jakma.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B116921F86A5 for <idr@ietfa.amsl.com>; Tue, 20 Sep 2011 05:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J17DTfWu7tOg for <idr@ietfa.amsl.com>; Tue, 20 Sep 2011 05:42:10 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7E08921F8593 for <idr@ietf.org>; Tue, 20 Sep 2011 05:42:10 -0700 (PDT)
Received: by wwf22 with SMTP id 22so467278wwf.13 for <idr@ietf.org>; Tue, 20 Sep 2011 05:44:35 -0700 (PDT)
Received: by 10.216.213.29 with SMTP id z29mr827949weo.7.1316522675699; Tue, 20 Sep 2011 05:44:35 -0700 (PDT)
Received: from jamaica.dcs.gla.ac.uk (jamaica.dcs.gla.ac.uk. [130.209.244.4]) by mx.google.com with ESMTPS id w31sm2139787wbm.12.2011.09.20.05.44.33 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 20 Sep 2011 05:44:34 -0700 (PDT)
Date: Tue, 20 Sep 2011 13:44:32 +0100 (BST)
From: Paul Jakma <paul@jakma.org>
X-X-Sender: paul@jamaica.dcs.gla.ac.uk
To: Robert Raszuk <robert@raszuk.net>
In-Reply-To: <4E78423D.9090403@raszuk.net>
Message-ID: <alpine.LFD.2.02.1109201343590.13262@jamaica.dcs.gla.ac.uk>
References: <8A40E55A626749F6AEA72EB24BD844EE@hnivarlas1> <4E78423D.9090403@raszuk.net>
User-Agent: Alpine 2.02 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: idr@ietf.org
Subject: Re: [Idr] optional transitive - recognised but out of context
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2011 12:42:11 -0000

On Tue, 20 Sep 2011, Robert Raszuk wrote:

> Hi Ilya,
>
> Do you think that the below draft still does not formally address the problem 
> you are describing ?
>
> http://tools.ietf.org/html/draft-ietf-idr-optional-transitive-03

Hmm, is it just me or does that not appear in the IDR docs page?

regards,
-- 
Paul Jakma  paul@jakma.org  twitter: @pjakma  PGP: 64A2FF6A
Fortune:
NEWS FLASH!!
Today the East German pole-vault champion became the West German pole-vault
champion.

From internet-drafts@ietf.org  Tue Sep 20 06:27:37 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B7F121F8C88; Tue, 20 Sep 2011 06:27:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vjFx3DZOXkO; Tue, 20 Sep 2011 06:27:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3024E21F8C76; Tue, 20 Sep 2011 06:27:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.60
Message-ID: <20110920132737.25095.32610.idtracker@ietfa.amsl.com>
Date: Tue, 20 Sep 2011 06:27:37 -0700
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-mrai-dep-04.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2011 13:27:37 -0000

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

	Title           : Revisions to the BGP &#39;Minimum Route Advertisement In=
terval&#39;
	Author(s)       : Paul Jakma
	Filename        : draft-ietf-idr-mrai-dep-04.txt
	Pages           : 4
	Date            : 2011-09-20

   This document updates the specification of the BGP MRAI timer in
   [RFC4271], by deprecating the previously recommended values and by
   allowing for withdrawals to be exempted from the MRAI.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-mrai-dep-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-idr-mrai-dep-04.txt

From ietfc@btconnect.com  Tue Sep 27 04:36:56 2011
Return-Path: <ietfc@btconnect.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB19121F8753 for <idr@ietfa.amsl.com>; Tue, 27 Sep 2011 04:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[AWL=0.800,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DY3sdddbqf36 for <idr@ietfa.amsl.com>; Tue, 27 Sep 2011 04:36:56 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr07.btconnect.com [213.123.20.125]) by ietfa.amsl.com (Postfix) with ESMTP id DEEBE21F8713 for <idr@ietf.org>; Tue, 27 Sep 2011 04:36:55 -0700 (PDT)
Received: from host86-163-147-122.range86-163.btcentralplus.com (HELO pc6) ([86.163.147.122]) by c2bthomr07.btconnect.com with SMTP id ERL35325; Tue, 27 Sep 2011 12:39:30 +0100 (BST)
Message-ID: <013801cc7d01$20b6ec40$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Paul Jakma" <paul@jakma.org>
References: <8A40E55A626749F6AEA72EB24BD844EE@hnivarlas1><4E78423D.9090403@raszuk.net> <alpine.LFD.2.02.1109201343590.13262@jamaica.dcs.gla.ac.uk>
Date: Tue, 27 Sep 2011 11:57:46 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0303.4E81B5F1.00B0, actions=TAG
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.7.19.51514:17:7.586, ip=86.163.147.122, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1000_1099, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020B.4E81B5F4.0086,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: idr@ietf.org
Subject: Re: [Idr] optional transitive - recognised but out of context
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2011 11:36:56 -0000

Paul

I can get it but it does say
"Expires: April 1, 2011  "
so perhaps I shouldn't:-(

Tom Petch

----- Original Message -----
From: "Paul Jakma" <paul@jakma.org>
To: "Robert Raszuk" <robert@raszuk.net>
Cc: <idr@ietf.org>
Sent: Tuesday, September 20, 2011 2:44 PM
Subject: Re: [Idr] optional transitive - recognised but out of context


> On Tue, 20 Sep 2011, Robert Raszuk wrote:
>
> > Hi Ilya,
> >
> > Do you think that the below draft still does not formally address the
problem
> > you are describing ?
> >
> > http://tools.ietf.org/html/draft-ietf-idr-optional-transitive-03
>
> Hmm, is it just me or does that not appear in the IDR docs page?
>
> regards,
> --
> Paul Jakma  paul@jakma.org  twitter: @pjakma  PGP: 64A2FF6A
> Fortune:
> NEWS FLASH!!
> Today the East German pole-vault champion became the West German pole-vault
> champion.
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

