RE: Review: Section 4.3 - Path Attributes

"Natale, Jonathan" <JNatale@celoxnetworks.com> Tue, 10 September 2002 12:49 UTC

Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11544 for <idr-archive@ietf.org>; Tue, 10 Sep 2002 08:49:05 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix) id EDD149128B; Tue, 10 Sep 2002 08:50:33 -0400 (EDT)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id B513A9128E; Tue, 10 Sep 2002 08:50:33 -0400 (EDT)
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 3D8099128B for <idr@trapdoor.merit.edu>; Tue, 10 Sep 2002 08:50:32 -0400 (EDT)
Received: by segue.merit.edu (Postfix) id 11A4E5DDF1; Tue, 10 Sep 2002 08:50:32 -0400 (EDT)
Delivered-To: idr@merit.edu
Received: from celox-ma1-ems1.celoxnetworks.com (celox-ma1-imap1.celoxnetworks.com [12.40.60.233]) by segue.merit.edu (Postfix) with ESMTP id B8A1D5DDC5 for <idr@merit.edu>; Tue, 10 Sep 2002 08:50:31 -0400 (EDT)
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19) id <RBC1CDKT>; Tue, 10 Sep 2002 08:50:31 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B020AF9A1@celox-ma1-ems1.celoxnetworks.com>
From: "Natale, Jonathan" <JNatale@celoxnetworks.com>
To: "'idr@merit.edu'" <idr@merit.edu>
Subject: RE: Review: Section 4.3 - Path Attributes
Date: Tue, 10 Sep 2002 08:50:21 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-idr@merit.edu
Precedence: bulk

True, the path attribute 
field itself can be left out.  The text should be changed.

-----Original Message-----
From: Michael C. Cambria [mailto:cambria@fid4.com] 
Sent: Saturday, September 07, 2002 12:59 PM
To: idr@merit.edu
Subject: Review: Section 4.3 - Path Attributes


 From a first time reader point of view ...

The top of page 13 says:

"A variable length sequence of path attributes is present in every UPDATE."

Is this really true, given that later, in the second to last paragraph 
of this section (4.3):

"An UPDATE message might advertise only routes to be withdrawn from 
service, in which case it will not include path attributes or Network 
Layer Reachability Information."

This could be confusing to a first time reader.

The path attribute length is present in every UPDATE, the path attribute 
field itself can be left out, both according to the description of the 
minimum length of the UPDATE message and (implied?) in the picture of 
the UPDATE message at the beginning of section 4.3.

MikeC