[manet] Re: Questions about RFC 8175 (DLEP) Link Charact eristics Request message
Henning Rogge <[email protected]> Tue, 24 Mar 2026 10:39:26 +0100
| Newsgroups | gmane.ietf.manet |
|---|---|
| Message-ID | <CAGnRvuo7rKfigfKjRBe3gRH3ykY++hEw9-FUf0EK4QzK=+jA4Q@mail.gmail.com> |
On Tue, Mar 17, 2026 at 8:22 AM Abdussalam Baryun <[email protected]> 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 -- [email protected] To unsubscribe send an email to [email protected]