IETF Logo Mail Archive

Re: bgp4-17 Cease subcode

Yakov Rekhter <yakov@juniper.net> Mon, 14 January 2002 17:29 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 MAA20005 for <idr-archive@nic.merit.edu>; Mon, 14 Jan 2002 12:29:27 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id 61F899120D; Mon, 14 Jan 2002 12:29:02 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id 2FF0191213; Mon, 14 Jan 2002 12:29: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 ED2369120D for <idr@trapdoor.merit.edu>; Mon, 14 Jan 2002 12:29:00 -0500 (EST)
Received: by segue.merit.edu (Postfix) id C25D55DDA7; Mon, 14 Jan 2002 12:29:00 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from merlot.juniper.net (natint.juniper.net [207.17.136.129]) by segue.merit.edu (Postfix) with ESMTP id 420B15DDA6 for <idr@merit.edu>; Mon, 14 Jan 2002 12:29:00 -0500 (EST)
Received: from juniper.net (garnet.juniper.net [172.17.28.17]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id g0EHSr633936; Mon, 14 Jan 2002 09:28:58 -0800 (PST) (envelope-from yakov@juniper.net)
Message-Id: <200201141728.g0EHSr633936@merlot.juniper.net>
To: Tom Petch <nwnetworks@dial.pipex.com>
Cc: idr@merit.edu
Subject: Re: bgp4-17 Cease subcode
In-Reply-To: Your message of "Sat, 11 Jan 2003 21:41:20 GMT." <005001c2b9ba$3094a9e0$9989bc3e@tom3>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <50786.1011029333.1@juniper.net>
Date: Mon, 14 Jan 2002 09:28:53 -0800
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-idr@merit.edu
Precedence: bulk

Tom,

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

Please remember that the goal of the draft is to document
what is *currently* implemented and deployed, *not* what
*could* be implemented and deployed. Therefore, the draft
should not list these new subcodes.

Yakov.

v2.23.0 | Report a Bug | By Email