IETF Logo Mail Archive

Re: IDR WG Last Call

Jeffrey Haas <jhaas@nexthop.com> Mon, 14 January 2002 23:13 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 SAA00563 for <idr-archive@nic.merit.edu>; Mon, 14 Jan 2002 18:13:54 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id EDFE291233; Mon, 14 Jan 2002 18:13:13 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id C00BB91234; Mon, 14 Jan 2002 18:13:13 -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 A161191233 for <idr@trapdoor.merit.edu>; Mon, 14 Jan 2002 18:13:12 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 774905DDAF; Mon, 14 Jan 2002 18:13:12 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from presque.djinesys.com (presque.djinesys.com [198.108.88.2]) by segue.merit.edu (Postfix) with ESMTP id 33C765DDAE for <idr@merit.edu>; Mon, 14 Jan 2002 18:13:12 -0500 (EST)
Received: from jhaas.nexthop.com (jhaas.nexthop.com [64.211.218.31]) by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id g0ENCwo58787; Mon, 14 Jan 2002 18:12:58 -0500 (EST) (envelope-from jhaas@nexthop.com)
Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.0/8.11.0) id g0ENCve14474; Mon, 14 Jan 2002 18:12:57 -0500 (EST)
Date: Mon, 14 Jan 2002 18:12:57 -0500
From: Jeffrey Haas <jhaas@nexthop.com>
To: Enke Chen <enke@redback.com>
Cc: idr@merit.edu
Subject: Re: IDR WG Last Call
Message-ID: <20020114181256.I7761@nexthop.com>
References: <skh@nexthop.com> <20020114221214.3242A15D3C1@popserv1.redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20020114221214.3242A15D3C1@popserv1.redback.com>; from enke@redback.com on Mon, Jan 14, 2002 at 02:12:12PM -0800
X-NextHop-MailScanner: Found to be clean
Sender: owner-idr@merit.edu
Precedence: bulk

On Mon, Jan 14, 2002 at 02:12:12PM -0800, Enke Chen wrote:
> In order for me to make sense out of your example, I need to be educated
> on how/why/when one would use "SAFI 3", especially in the context of
> Multi-protocol BGP.

3 - Network Layer Reachability Information used for both unicast
    and multicast forwarding

In other words, where you would otherwise send a SAFI 1 and then a SAFI 2
announcement for the same prefix and same path attributes, you could
otherwise send a SAFI 3 advertisement.

>  -- Enke

-- 
Jeff Haas 
NextHop Technologies

v2.23.0 | Report a Bug | By Email