IETF Logo Mail Archive

Re: RFC-2283 question

Yakov Rekhter <yakov@cisco.com> Tue, 09 November 1999 18:27 UTC

Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.1a/8.9.1) with ESMTP id NAA13237 for <idr-archive@nic.merit.edu>; Tue, 9 Nov 1999 13:27:19 -0500 (EST)
Received: by segue.merit.edu (Postfix) id CC4155DE1D; Tue, 9 Nov 1999 13:26:20 -0500 (EST)
Delivered-To: idr-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56) id 38A935DED2; Tue, 9 Nov 1999 13:25:42 -0500 (EST)
Received: from mail.nyp.ans.net (mail.nyp.ans.net [147.225.190.25]) by segue.merit.edu (Postfix) with ESMTP id 6788F5DEAA for <bgp@merit.edu>; Tue, 9 Nov 1999 13:25:13 -0500 (EST)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141]) by mail.nyp.ans.net (8.9.3/8.9.3) with ESMTP id NAA24511 for <bgp@ans.net>; Tue, 9 Nov 1999 13:25:06 -0500 (EST)
Received: from localhost (yakov@localhost) by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id KAA17579; Tue, 9 Nov 1999 10:15:42 -0800 (PST)
Message-Id: <199911091815.KAA17579@omega.cisco.com>
To: "Rijsman, Bruno" <brijsman@unisphere.cc>
Cc: Hua Kuang <hkuang@nortelnetworks.com>, BGP exploder <bgp@ans.net>
Subject: Re: RFC-2283 question
In-reply-to: Your message of "Tue, 09 Nov 1999 12:31:30 EST." <90ABC30C744ED311B16E00500464BEFC23662E@NTSERVER1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17576.942171342.1@cisco.com>
Date: Tue, 09 Nov 1999 10:15:42 -0800
From: Yakov Rekhter <yakov@cisco.com>
Sender: owner-idr@merit.edu
Precedence: bulk

> Hua> MP_(UN)REACH_NLRI are path attributes, in RFC1771 and the later 
> Hua> BGP4 drafts, each path attribute contains a triple <type, length,
> value>,  
> Hua> this "length" here should be enough to hold the NLRIs information.
> 
> Hua,
> 
> This works fine if an MP_REACH_NLRI attribute only contains a single triple 
> <Address Family Information, Next Hop Information, Network Layer
> Reachability Information>

[clipped...]

> However, if there are multiple triples per MP_REACH_NLRI attributes (as
> allowed by RFC 2283 but not by DRAFT draft-ietf-idr-bgp-multiprotocol-v2-03) 
> there is no way to figure out how many prefixes there are in each triple:

That is precisely why the draft allows only one address family per attribute.

Yakov.

v2.23.0 | Report a Bug | By Email