Re: [babel] info-model: link properties

["STARK, BARBARA H" <[e-mail]>]

I've gotten no replies to this email. Absence of reply mean you agree with using Juliusz' definitions for wired, wireless, and tunnel. But I'm still unclear as to how to define "other". Maybe "implementation specific"?
Barbara

> > I was under the impression that we had decided that the classification
> > of link types in wired/wireless/tunnel is an internal implementation
> > detail of babeld, and that what we wanted to export were the
> > underlying properties, which are:
> >
> >   - link cost estimator (ETX or 2-out-of-3);
> >   - use split-horizon (boolean);
> >   - use RTT (boolean).
> >
> > wired means 2-out-of-3, split-horizon, no RTT.
> > wireless means ETX, no split-horizon, no RTT.
> > tunnel means 2-out-of-3, split-horizon, RTT.
> >
> > It is clear to me that the interface type abstration is useful for the
> > user, who doesn't want to deal with technical details such as whether
> > the split-horizon optimisation is allowable on a given link type, but
> > it's difficult to export from the management interface.
> 
> I recently posted an update to the information-model draft, but missed
> including the appropriate updates to the Link Properties registry descriptions
> in IANA considerations. What I intend to do in the next revision is use Juliusz'
> proposed descriptions (above) for wired, wireless, and tunnel. What should I
> put for "other"?  Or should I have an "other"?
> Barbara
> 
> _______________________________________________
> babel mailing list
> [e-mail]
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_babel&d=DwICAg&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=LoGzhC-
> 8sc8SY8Tq4vrfog&m=cLDr9j3VC6V4K9_5cjuNb9wKlkx_eIoPr1cDsX2nUEc&s=2
> e8o9o9q1cDVE_etpEPEh90o3fPqUvFfh5vvdRZIFrk&e=