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

Robert Raszuk <robert@raszuk.net> Sun, 01 April 2012 20:57 UTC

Return-Path: <robert@raszuk.net>
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 2DE5C21F89DB for <sidr@ietfa.amsl.com>; Sun, 1 Apr 2012 13:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level:
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 v0Gy4YkhEXyt for <sidr@ietfa.amsl.com>; Sun, 1 Apr 2012 13:57:07 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 59F1F21F89DA for <sidr@ietf.org>; Sun, 1 Apr 2012 13:57:07 -0700 (PDT)
Received: (qmail 4144 invoked by uid 399); 1 Apr 2012 20:57:06 -0000
Received: from unknown (HELO ?10.0.1.3?) (pbs:robert@raszuk.net@213.160.13.154) by mail1310.opentransfer.com with ESMTPM; 1 Apr 2012 20:57:06 -0000
X-Originating-IP: 213.160.13.154
Message-ID: <4F78C121.50902@raszuk.net>
Date: Sun, 01 Apr 2012 22:57:05 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: Eric Osterweil <eosterweil@verisign.com>
References: <20120328081939.GA19843@slice> <CA796250-4EA9-468D-BB4A-4C1187D2148F@tcb.net> <20120329072236.GA7311@slice> <61C7DEFD-B03F-42B2-B0FC-878E84C32629@ericsson.com> <20120329081625.GA9609@slice> <C80C23B3-C6D9-44CA-A020-144890CA0274@verisign.com>
In-Reply-To: <C80C23B3-C6D9-44CA-A020-144890CA0274@verisign.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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
Reply-To: robert@raszuk.net
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: Sun, 01 Apr 2012 20:57:08 -0000

Hi Eric,

 > BGP is a great soft-state protocol (where some may define
 > ``great'' differently), but I don't currently tweet or update my fb
 > status over it.

While I agree with 99% of what you said today on the list (especially 
pointing out need for solid requirements to document what sidr is trying 
to achieve) I am not sure why you call BGP soft-state.

For me soft-state protocol is RSVP which requires refresh otherwise 
state invalidates. BGP does not require refresh.

If that would not be enough BGP is soon to become completely "hard 
state" if one would implement 
http://tools.ietf.org/html/draft-uttaro-idr-bgp-persistence-01

Best,
R.