IETF Logo Mail Archive

as4bytes - 4byte speaker receiving new* attributes?

Jeffrey Haas <jhaas@nexthop.com> Tue, 08 May 2001 14:26 UTC

Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id KAA13917 for <idr-archive@nic.merit.edu>; Tue, 8 May 2001 10:26:42 -0400 (EDT)
Received: by segue.merit.edu (Postfix) id 989915DEA6; Tue, 8 May 2001 10:20:09 -0400 (EDT)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id 84CDB5DD9D; Tue, 8 May 2001 10:20:09 -0400 (EDT)
Received: from presque.djinesys.com (presque.djinesys.com [198.108.88.2]) by segue.merit.edu (Postfix) with ESMTP id C36CF5DEA3 for <idr@merit.edu>; Tue, 8 May 2001 10:20:07 -0400 (EDT)
Received: from jhaas.nexthop.com ([141.211.130.148]) by presque.djinesys.com (8.11.1/8.11.1) with ESMTP id f48EK7a71064 for <idr@merit.edu>; Tue, 8 May 2001 10:20:07 -0400 (EDT) (envelope-from jhaas@nexthop.com)
Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.0/8.11.0) id f48EK7K03395 for idr@merit.edu; Tue, 8 May 2001 10:20:07 -0400 (EDT)
Date: Tue, 08 May 2001 10:20:07 -0400
From: Jeffrey Haas <jhaas@nexthop.com>
To: idr@merit.edu
Subject: as4bytes - 4byte speaker receiving new* attributes?
Message-ID: <20010508102007.C1170@nexthop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-idr@merit.edu
Precedence: bulk

In the current as4bytes draft (draft-ietf-idr-as4bytes-02.txt):

:    The new attributes, NEW_AS_PATH and NEW_AGGREGATOR should not be
:    carried in the updates between NEW BGP peers. A NEW BGP speaker that
:    receives an UPDATE message from a NEW BGP speaker, with the
:    NEW_AS_PATH attribute carried in the UPDATE message must ignore the
:    attribute. The same applies to the NEW_AGGREGATOR attribute.

If we are a 4byte router peering with another 4byte router
and have mutually capability advertised a 4byte peering session, we
should not be getting these attributes.

Would it not be better to send a NOTIFY in this case?  

-- 
Jeff Haas 
NextHop Technologies

v2.23.0 | Report a Bug | By Email