Re: [Idr] draft-ietf-idr-rfc3065bis-02.txt to Draft Standard

Comments:

MS-style line feeds have crept into the document.

In the table of contents, could we keep the columns justified to the same
level?

On page 4, could we keep the header "Member-AS Number" with the following
text?

   When implementing BGP Confederations Section 5.1.2 of [1] is replaced

Add in a comma:

   When implementing BGP Confederations, Section 5.1.2 of [1] is replaced

A critical error seems to have slipped in:

:    When implementing BGP Confederations Section 5.1.2 of [1] is replaced
:    with the following text:
: [...]
: 
:    a) When a given BGP speaker advertises the route to another BGP
:       speaker located in its own autonomous system, the advertising
:       speaker SHALL modify the AS_PATH attribute associated with the
:       route.

This must be SHALL NOT

This seems to have remained unnoticed as well:

:    It is a error for a BGP speaker to receive an update message from a
:    confederation peer which does not have AS_CONFED_SEQUENCE as the
:    first segment.  If a BGP speaker receives such an update message, it
:    SHALL treat the message as having a malformed AS_PATH according to
:    the procedures of [1] Section 6.3 ("Update message error handling").

Consider the case where a confederation router peering with a 
non-confederation router receives a route.  This route, when being
propagated via iBGP to a confederation peer WILL NOT have its AS_PATH
modified.

The above text could be modified to something like the following

It is a error for a BGP speaker to receive an update message from an
external confederation peer which does not have AS_CONFED_SEQUENCE as the
first segment. [...]

Don't references need to be split between normative and informative?

Remove last empty page.

On Mon, May 24, 2004 at 08:49:14AM -0700, Yakov Rekhter wrote:
> Folks,
> 
> This is to start the IDR WG Last Call on advancing
> draft-ietf-idr-rfc3065bis-02.txt to Draft Standard.
> 
> During the Last Call it would be greatly appreciated if folks would
> read the document and comment on it to the IDR mailing list. In
> other words, we need "yes, looks good" or "should fix this and
> that", not just silence.
> 
> The deadline for comments is June 7, 2004.
> 
> Yakov.

-- 
Jeff Haas 
NextHop Technologies

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr