Re: [Idr] Revised proposed IDR charter

["John G. Scudder" <[e-mail]>]

I think Ross is addressing your other questions, but I'll add a little on these two:

On Feb 1, 2010, at 9:58 AM, Danny McPherson wrote:
>> - The definition of an "Accumulated IGP Metric" attribute for BGP
>> to report the sum of the metric of each link along the path.
>> This attribute is for use in a restricted environment where:
>> - all ASes are subject to the administrative control
>> - some form of tunneling is used to deliver a packet to its next
>>   BGP hop
>> - where the path for a route leads outside the AS to which the
>>   BGP speaker adding the attribute belongs.
> 
> What's a restrictive environment again

It's defined by the three bullets immediately following the "restricted environment" line.  Seems clear to me.

> and how do we *guarantee* 
> this in BGP?

I see it as an applicability statement, not a statement of technical guarantee.  As you know, there many things in BGP that aren't *guaranteed* but depend on correct deployment practices.

>> - Advertisement of the best external route in BGP to assist with
>> resolution of the next hop in the chosen data plane.
> 
> Any chance we could add something here about minimizing BGP state, 
> everyone one of the options above aims to expand the number of 
> unique routes, whereas RRG and all the rest of the world are working
> on scalability - all of this stuff seems to only lead to additional 
> state and churn to me.

You've commented on the list of work items, I'm not aware of a specific work item that's been brought to the group such as you describe.  We already have "scalability" called out in the proposed revision, and what you describe would fall directly under that umbrella.  If you have something to propose, by all means please submit a draft.

--John