Re: SMF in Manet and MPR

Christopher Dearlove <[email protected]>
Newsgroups gmane.ietf.manet
Message-ID <[email protected]>
RFC 5444 is mandated for use on the MANET UDP port (and IP protocol) by RFC 5498 and repeated in RFC 8245. Any other use is optional, but there’s no good reason to use it on the data plane.

There was an (or possibly more than one) experimental - I don’t believe it even made it to an ID, but was implemented and reported in at least one paper - use of OLSR for an SMF-like approach to multicast, intercepting the data packets in the IP stack, encapsulating them as a new OLSR message type, flooded using OLSR, then converted back to IP data plane at destinations. This was rather a hack and the SMF approach was to supersede that, keeping data in the data plane where it belongs.

(We did it at BAE Systems, I think NRL might have done something similar, and possibly Ecole Polytechnique/INRIA too.)

> On 30 Jan 2024, at 08:12, Henning Rogge <[email protected]> wrote:
> 
> On Mon, Jan 29, 2024 at 10:04 PM Abdussalam Baryun
> <[email protected]> wrote:
>> I would like if possible an update/information in 2024 about SMF implementation or RFC6621 implementation regarding its use in OLSRv2 RFC7181
> 
> SMF is not used in OLSRv2... it's the other way around, the MPR
> results of OLSRv2 can be used in SMF.
> 
>> I suggest that the RFC6621 implementation must use PACKET BB (i.e. MANET Packet) RFC5444 if it is to be used with WG standard routing , because OLSRv2 RFC7181 is using RFC5444. Or is there other suggestions we can discuss?
> 
> I suggest you read RFC6621 again...
> 
> RFC5444 is used for MANET protocols... not for the data plane forwarding.
> 
> Henning Rogge
> 
> _______________________________________________
> manet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/manet

_______________________________________________
manet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/manet
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.