Re: IDR WG Last Call

[Enke Chen <[e-mail]>]

Sue, 

> Message-Id: <[e-mail]>
> Date: Fri, 11 Jan 2002 11:20:02 -0500
> To: Enke Chen <[e-mail]>
> From: Susan Hares <[e-mail]>
> Subject: Re: IDR WG Last Call 
> Cc: Yakov Rekhter <[e-mail]>, [e-mail],
> 	[e-mail]
> In-Reply-To: <[e-mail]>
> References: <Message from Yakov Rekhter <[e-mail]>
>  <[e-mail]>
> Mime-Version: 1.0
> 
> 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.

Could not find it in the spec..

> 
> Can you site a technical reason for this change or common practice
> regarding this text?

That is what the widely deployed code does. -- Enke

> 
> 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: <[e-mail]>
> > > To: [e-mail]
> > > Subject: IDR WG Last Call
> > > MIME-Version: 1.0
> > > Content-Type: text/plain; charset="us-ascii"
> > > Content-ID: <[e-mail]>
> > > Date: Wed, 09 Jan 2002 17:31:49 -0800
> > > From: Yakov Rekhter <[e-mail]>
> > > Sender: [e-mail]
> > > 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:    [e-mail]
> > > To:      IETF-Announce: ;
> > > cc:      [e-mail]
> > > 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
> > >
> 
>