RE: [Ospf-wireless-design] Design Team slides for IETF 63

> -----Original Message-----
> From: Acee Lindem [mailto:acee@cisco.com] 
> Sent: Tuesday, August 02, 2005 7:00 AM
> To: Richard Ogier
> Cc: ospf-wireless-design@ietf.org
> Subject: Re: [Ospf-wireless-design] Design Team slides for IETF 63
> 
> 
> The draft revision containing the technical details of your 
> proposal just made the IETF meeting cut-off (July 18th).  
> Hence, it is premature to say that reached consensus. As Tom 
> states in his slides, Boeing will soon make the full report 
> and GTNetS implementation available for evaluation.
> 

I agree that it is premature to say that we have consensus.  We do need
more discussion, though.  Richard has made a lot of points on this list
over the past few months that have largely gone unchallenged.  Does that
mean that people agree with him?

We have to get another approval to release the below to a wider (general
public) distribution, so please do not redistribute the below outside of
the design team at this time.  However, it is now posted for the design
team:

http://hipserver.mct.phantomworks.org/ietf/ospf/

In particular, there is a 100+ page tech report.  I don't expect people
to wade through the whole thing, but please look at the data in chapter
4 and summary in chapter 5, if you only read a portion of it.  

> > Richard wrote:
> > 
> > Regarding the "Smart Peering" draft by Roy et al. Is the 
> plan to allow
> > time for this new idea (which by the way is closely related to my
> > definition of a "routable" neighbor) to be developed into a 
> fine tuned
> > implementation?  If this idea can be demonstrated in a 
> short time, then
> > it might be worth considering.  But we have already delayed 
> the decision
> > by several months, so I think we need to avoid dragging on 
> indefinitely.

We have some results on a basic implementation of the Smart Peering
draft-- see Section 4 of our report.

I agree with Phil-- we need to agree first on an overall framework for
this extension (MDR vs. Overlapping Relays)- then, there are additional
design elements that need to be considered such as hello design, 2-hop
neighbor info dissemination, and flooding backups.

Tom

_______________________________________________
Ospf-wireless-design mailing list
Ospf-wireless-design@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ospf-wireless-design