Re: IDR WG Last Call
Susan Hares <skh@nexthop.com> Fri, 11 January 2002 16:40 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 LAA12291 for <idr-archive@nic.merit.edu>; Fri, 11 Jan 2002 11:40:06 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id ECE1491292; Fri, 11 Jan 2002 11:38:57 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id BE9DE91291; Fri, 11 Jan 2002 11:38:56 -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 D7AA591292 for <idr@trapdoor.merit.edu>; Fri, 11 Jan 2002 11:38:54 -0500 (EST)
Received: by segue.merit.edu (Postfix) id B0CD45DD98; Fri, 11 Jan 2002 11:38:54 -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 5C2285DD8F for <idr@merit.edu>; Fri, 11 Jan 2002 11:38:54 -0500 (EST)
Received: from SKH.nexthop.com ([64.211.218.122]) by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id g0BGcNo44690; Fri, 11 Jan 2002 11:38:24 -0500 (EST) (envelope-from skh@nexthop.com)
Message-Id: <5.0.0.25.0.20020111111630.032cf5f0@mail.nexthop.com>
X-Sender: skh@mail.nexthop.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Fri, 11 Jan 2002 11:20:02 -0500
To: Enke Chen <enke@redback.com>
From: Susan Hares <skh@nexthop.com>
Subject: Re: IDR WG Last Call
Cc: Yakov Rekhter <yakov@juniper.net>, idr@merit.edu, enke@redback.com
In-Reply-To: <20020110181325.1F29C7E6C1@popserv3.redback.com>
References: <Message from Yakov Rekhter <yakov@juniper.net> <200201100131.g0A1Vn658927@merlot.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-NextHop-MailScanner: Found to be clean
Sender: owner-idr@merit.edu
Precedence: bulk
Enke: I don't think this is a clarification, I think this is a change in the specification. The original idea was to allow: Withdraw and announce to withdraw the SAFI: uni,multi in the MP_UNREACH_NLRI filed and to announce it in the NLRI field. Can you site a technical reason for this change or common practice regarding this text? Sue Hares At 10:13 AM 1/10/2002 -0800, Enke Chen wrote: >Hi, Yakov: >How about we add the following clarification (similar to the one in the base >BGP spec): > > An UPDATE message should not include the same address prefix (of the same > <AFI, SAFI>) in more than one of the following fields: WITHDRAWN ROUTES > field, Network Reachability Information fields, MP_REACH_NLRI field, and > MP_UNREACH_NLRI field. However a BGP speaker MUST be able to process > UPDATE > messages in this form. A BGP speaker should treat an UPDATE message of > this > form as if that the address prefix were included only in the last field of > the message. > >Thanks. -- Enke > > > Message-Id: <200201100131.g0A1Vn658927@merlot.juniper.net> > > To: idr@merit.edu > > Subject: IDR WG Last Call > > MIME-Version: 1.0 > > Content-Type: text/plain; charset="us-ascii" > > Content-ID: <18652.1010626309.1@juniper.net> > > Date: Wed, 09 Jan 2002 17:31:49 -0800 > > From: Yakov Rekhter <yakov@juniper.net> > > Sender: owner-idr@merit.edu > > Precedence: bulk > > > > Folks, > > > > This is to begin the WG Last Call on advancing Multiprotocol > > Extensions for BGP-4 to Draft Standard. The Last Call ends > > Jan 23, 2002. > > > > Yakov. > > ------- Forwarded Message > > > > Date: Wed, 09 Jan 2002 16:06:30 -0500 > > From: Internet-Drafts@ietf.org > > To: IETF-Announce: ; > > cc: idr@merit.edu > > Subject: I-D ACTION:draft-ietf-idr-rfc2858bis-00.txt > > > > - --NextPart > > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > This draft is a work item of the Inter-Domain Routing Working Group of > the IETF > > . > > > > Title : Multiprotocol Extensions for BGP-4 > > Author(s) : T. Bates et al. > > Filename : draft-ietf-idr-rfc2858bis-00.txt > > Pages : 10 > > Date : 08-Jan-02 > > > > Currently BGP-4 [BGP-4] is capable of carrying routing information > > only for IPv4 [IPv4]. This document defines extensions to BGP-4 to > > enable it to carry routing information for multiple Network Layer > > protocols (e.g., IPv6, IPX, etc...). The extensions are backward > > compatible - a router that supports the extensions can interoperate > > with a router that doesn't support the extensions. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-idr-rfc2858bis-00.txt > > > > To remove yourself from the IETF Announcement list, send a message to > > ietf-announce-request with the word unsubscribe in the body of the message. > > > > Internet-Drafts are also available by anonymous FTP. Login with the > username > > "anonymous" and a password of your e-mail address. After logging in, > > type "cd internet-drafts" and then > > "get draft-ietf-idr-rfc2858bis-00.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > >
- Re: IDR WG Last Call - Who has SAFI 3? Kunihiro Ishiguro
- Re: IDR WG Last Call - Who has SAFI 3? Susan Hares
- Re: IDR WG Last Call Kunihiro Ishiguro
- Re: IDR WG Last Call Jeffrey Haas
- Re: IDR WG Last Call Susan Hares
- Re: IDR WG Last Call Susan Hares
- Re: IDR WG Last Call Susan Hares
- Re: IDR WG Last Call Susan Hares
- Re: IDR WG Last Call Susan Hares
- IDR WG Last Call Yakov Rekhter