On Mar 4, 2011, at 5:39 AM, Christopher Morrow wrote:
...
> A few folks noted that perhaps 'route' was not the right word here,
> perhaps NLRI is. Using a wikipedia definition:

I love Wikipedia, but the quoted definition is wrong, at least with respect to 
the definitions given in RFC 4271:

1.1.  Definition of Commonly Used Terms

...

   NLRI
      Network Layer Reachability Information.

   Route
      A unit of information that pairs a set of destinations with the
      attributes of a path to those destinations.  The set of
      destinations are systems whose IP addresses are contained in one
      IP address prefix carried in the Network Layer Reachability
      Information (NLRI) field of an UPDATE message.  The path is the
      information reported in the path attributes field of the same
      UPDATE message.

Given that what we're talking about securing is BGP, it would seem sensible to 
use BGP's terminology.  Given that, the text as written seems right to me:

----------------------------------------------------------
* Is the AS-Path represented in the route the same as the path
      through which the route update traveled
----------------------------------------------------------

or if you insist perhaps

----------------------------------------------------------
* Is the AS-Path represented in the route the same as the path through
which the NLRI traveled
----------------------------------------------------------

But if this is the biggest nit we have to pick then I'll agree with "ship it".

By the way, which Wikipedia article were you quoting, so I can think about 
fixing it in my CFT?

...
>   but still the material relevant to IDR should go there for 
> checkbox/changes/etc.

Yes.  Speaking for myself I don't have a problem with progressing this work in 
SIDR for the time being given that there is energy and expertise to do it here. 
 We can reshuffle deck chairs in the future as seems warranted, and in any case 
should have review by both groups no matter which WG the work is done in.

--John
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to