IETF Logo Mail Archive

Re: [sidr] Injecting idea of "freshness of repository data" into BGP

Jakob Heitz <jakob.heitz@ericsson.com> Thu, 29 March 2012 07:58 UTC

Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66BFE21F8978 for <sidr@ietfa.amsl.com>; Thu, 29 Mar 2012 00:58:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.506
X-Spam-Level:
X-Spam-Status: No, score=-6.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 mPj3eXuffSKU for <sidr@ietfa.amsl.com>; Thu, 29 Mar 2012 00:58:13 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 73C7F21F8974 for <sidr@ietf.org>; Thu, 29 Mar 2012 00:58:13 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q2T7wBf7021398; Thu, 29 Mar 2012 02:58:12 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.55]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Thu, 29 Mar 2012 03:58:06 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Date: Thu, 29 Mar 2012 03:58:38 -0400
Thread-Topic: [sidr] Injecting idea of "freshness of repository data" into BGP
Thread-Index: Ac0NgazA05JkQoEETy2psAv0reFN3Q==
Message-ID: <00857EED-F2E7-4E41-884E-F25492CF3BF1@ericsson.com>
References: <20120328081939.GA19843@slice> <CA796250-4EA9-468D-BB4A-4C1187D2148F@tcb.net> <20120329072236.GA7311@slice> <61C7DEFD-B03F-42B2-B0FC-878E84C32629@ericsson.com>
In-Reply-To: <61C7DEFD-B03F-42B2-B0FC-878E84C32629@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] Injecting idea of "freshness of repository data" into BGP
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 07:58:15 -0000

Any place that does not receive a new BGP update can not be helped. Even with a beacon.
Therefore, a freshness indicator in the BGP update itself is enough to invalidate less fresh updates.

Only freshen the BGP update when you actually have a dispute with your old provider.

--
Jakob Heitz.


On Mar 29, 2012, at 9:51 AM, "Jakob Heitz" <jakob.heitz@ericsson.com> wrote:

> Could we not put a freshness indication into the BGP update?
> Then everyone that receives the new update would know to invalidate the less fresh paths.
> 
> Here is the key point:
> The new update will reach everywhere that it needs to go.
> Won't it?
> 
> No expiry time needed.
> 
> --
> Jakob Heitz.
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr

v2.23.0 | Report a Bug | By Email