So would you care then to maybe quote precisely that "previous seminal
work" you refer to since I'm not aware of it?    MANET is referred to in
distopo already since original authors chose to start with this (they could
have started with MIS or SPT just as well AFAIS) and this draft has nothing
to do with it really per se since MANET is one very particular algorithm
(or class thereof) building a CDS and many other approaches to do the same
in distributed (or centralized) fashion are actually possible. So if you
can provide a relevant quote of a publication describing an approach
allowing to mix different CDS building algorithms in the same network I'm
more than happy to include that in the draft of course.

thanks

--- tony

On Mon, Apr 28, 2025 at 10:17 PM [email protected] <[email protected]>
wrote:

> All I am asking for is continued recognition of the seminal work
>
> Sent from my iPhone
>
> On Apr 28, 2025, at 4:13 PM, Tony Li <[email protected]> wrote:
>
> 
>
> That is the way of the world. If you object to patent law, then I think
> you should take it up with appropriate lawyers… The IETF is hardly the
> appropriate venue.
>
> T
>
>
> On Apr 28, 2025, at 1:04 PM, [email protected] - je_drake=40yahoo.com at
> dmarc.ietf.org <[email protected]> wrote:
>
> What disturbs me is that you folks appear to be getting a free ride on
> seminal work done by someone else.  All you have done is tweak it and apply
> for patents.
>
> Sent from my iPhone
>
> On Apr 28, 2025, at 11:02 AM, Tony Przygienda <[email protected]> wrote:
>
> 
> AFAIR original authors put it in (or maybe I did later, don't remember)
>
> [RFC5614]  Ogier, R. and P. Spagnolo, "Mobile Ad Hoc Network (MANET)
>               Extension of OSPF Using Connected Dominating Set (CDS)
>               Flooding", RFC 5614, DOI 10.17487/RFC5614, August 2009,
>               <https://www.rfc-editor.org/info/rfc5614>.
>
>
> that's not enough?
>
>
> --- tony
>
>
>
> On Mon, Apr 28, 2025 at 4:03 PM Acee Lindem <[email protected]> wrote:
>
>>
>>
>> > On Apr 28, 2025, at 9:38 AM, John Drake <[email protected]> wrote:
>> >
>> > I don't see that you folks gave any credit to Richard Ogier (SRI
>> International) who came up with the original idea, in the context of Mobile
>> Ad-Hoc networks, and from whom you blatantly plagiarized.
>>
>> This would apply more to
>> https://datatracker.ietf.org/doc/draft-ietf-lsr-distoptflood/ which does
>> acknowledge the OSPF MANET RFCs.
>>
>> Thanks,
>> Acee
>>
>>
>> >
>> > On Sunday, April 27, 2025 at 11:02:15 PM PDT, Shraddha Hegde <shraddha=
>> [email protected]> wrote:
>> >
>> >
>> > Support adoption.
>> >
>> > Rgds
>> > Shraddha
>> >
>> >
>> > Juniper Business Use Only
>> > From: Tony Przygienda <[email protected]>
>> > Sent: 28 April 2025 00:55
>> > To: Acee Lindem <[email protected]>
>> > Cc: lsr <[email protected]>; Shraddha Hegde <[email protected]>
>> > Subject: Re: WG Adoption Poll for "Flooding Reduction Algorithms
>> Framework" - draft-prz-lsr-interop-flood-reduction-architecture-01
>> >
>> > [External Email. Be cautious of content]
>> >
>> > support. I won't roll up the whole reasons since the threads and
>> consensus building were extensive and are documented
>> >
>> > thanks
>> >
>> > -- tony
>> >
>> > On Sun, Apr 27, 2025 at 4:40 PM Acee Lindem <[email protected]>
>> wrote:
>> > LSR WG,
>> >
>> > This starts the Working Group adoption call for
>> draft-prz-lsr-interop-flood-reduction-architecture-01. Please send your
>> > support or objection to this list before Monday, May 12th, 2025.
>> >
>> > Thanks,
>> > Acee
>> > _______________________________________________
>> > Lsr mailing list -- [email protected]
>> > To unsubscribe send an email to [email protected]
>>
>> _______________________________________________
> Lsr mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
>
> _______________________________________________
> Lsr mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
>
_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to