[manet] Re: Questions about RFC 8175 (DLEP) Link Characteristics Request message

[Donald Eastlake <[e-mail]>]

Hi Henning,

Using the broadcast MAC seems like an elegant way to do this. I don't think
there is any other plausible interpretation for that MAC address.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   [phone] (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 [e-mail]


On Tue, Mar 24, 2026 at 5:40 AM Henning Rogge <[e-mail]> wrote:

> On Tue, Mar 17, 2026 at 8:22 AM Abdussalam Baryun
> <[e-mail]> wrote:
> >> The issue we see is that the request we are talking about is for the
> >> whole channel, not a special Destination.
> >
> > whole channel for the manet route
>
> whole channel of the radio attached over a DLEP session.
>
> >> RFC 8175 Section 12.18 defines that the referred destination of the
> >> Link Characteristics Request message can be both real (e.g. remote MAC
> >> address) or logical (e.g. multicast group).
> >>
> >> Would it be valid to use the "broadcast MAC" to request something for
> >> the whole network or do we need a "Channel/Device Characteristic
> >> Request/Response" message?
> >
> >  I don't think we can use broadcast MAC for DLEP, so it will need
> different protocol.
>
> We CAN use the broadcast MAC for a DLEP destination, thats not the
> issue... the issue is if we SHOULD use this for using the "Request
> Link Characteristic" Message for requesting new parameters for the
> radio session or if we should use a new MESSAGE type for requesting
> such a change.
>
> Not sure why you are talking about a different protocol.
>
> Henning Rogge
>
> _______________________________________________
> manet mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>