IETF Logo Mail Archive

Re: bgp4-17 Cease subcode

"Tom Petch" <nwnetworks@dial.pipex.com> Fri, 11 January 2002 21:42 UTC

Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id QAA20232 for <idr-archive@nic.merit.edu>; Fri, 11 Jan 2002 16:42:24 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id D063E912A2; Fri, 11 Jan 2002 16:42:02 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id A422A912A3; Fri, 11 Jan 2002 16:42:02 -0500 (EST)
Delivered-To: idr@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 8DFCC912A2 for <idr@trapdoor.merit.edu>; Fri, 11 Jan 2002 16:42:01 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 6443C5DDB8; Fri, 11 Jan 2002 16:42:01 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from hose.mail.pipex.net (hose.mail.pipex.net [158.43.128.58]) by segue.merit.edu (Postfix) with SMTP id A1FBF5DDB7 for <idr@merit.edu>; Fri, 11 Jan 2002 16:42:00 -0500 (EST)
Received: (qmail 22449 invoked from network); 11 Jan 2002 21:41:58 -0000
Received: from userat50.uk.uudial.com (HELO tom3) (62.188.137.153) by smtp-4.dial.pipex.com with SMTP; 11 Jan 2002 21:41:58 -0000
Message-ID: <005001c2b9ba$3094a9e0$9989bc3e@tom3>
Reply-To: Tom Petch <nwnetworks@dial.pipex.com>
From: Tom Petch <nwnetworks@dial.pipex.com>
To: Yakov Rekhter <yakov@juniper.net>
Cc: idr@merit.edu, yakov@juniper.net
Subject: Re: bgp4-17 Cease subcode
Date: Sat, 11 Jan 2003 21:41:20 -0000
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 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-idr@merit.edu
Precedence: bulk

Ouch; I had forgotten reading that I-D.

But I am still uncomfortable with last call on this
capabillity in bgp4-17 with the prospect of a subcode
appearing, or possibly not, at some point in the future in a
separate RFC.

Tom Petch, Network Consultant
nwnetworks@dial.pipex.com
+(44) 192 575 3018

v2.23.0 | Report a Bug | By Email