TRAIN - probably worth reading before our meeting

[Michael Welzl]

https://datatracker.ietf.org/doc/draft-thomson-scone-train-protocol/

[Joerg Ott]

All proposals are actually interesting reads...

On 06.11.24 19:30, Michael Welzl wrote:
> https://datatracker.ietf.org/doc/draft-thomson-scone-train-protocol/
> <https://datatracker.ietf.org/doc/draft-thomson-scone-train-protocol/>
>
> --
> https://github.com/mwelzl/oppd <https://github.com/mwelzl/oppd>
> ---
> You received this message because you are subscribed to the Google
> Groups "oppd-ietf" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to oppd-ietf+...@googlegroups.com <mailto:oppd-
> ietf+uns...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/oppd-
> ietf/96FCD2B4-D1CF-48D1-8B00-EA2A27C323F2%40ifi.uio.no <https://
> groups.google.com/d/msgid/oppd-ietf/96FCD2B4-D1CF-48D1-8B00-
> EA2A27C323F2%40ifi.uio.no?utm_medium=email&utm_source=footer>.

[Michael Welzl]

Yes!  I’m trying to understand which of them:

- might not require both peers (as the ideas in the oppd overview draft don’t)

- guarantee the signal itself being on-path

e.g. med’s https://www.ietf.org/archive/id/draft-brw-scone-rate-policy-discovery-00.html can be carried on dhcp, so then this is a non-on-path device telling me about a config of an on-path one. his blob can also be carried in ipv6 ra’s, but how would these reach a sender and/or be guaranteed to be on path?

i get the impression that nothing really fits the bill here for what we want. and, maybe scone isn’t our home after all.

Sent from my phone

Am 07.11.2024 um 10:39 schrieb Joerg Ott <o...@in.tum.de>:

All proposals are actually interesting reads...

[Michael Welzl]

… alternatively, almost all of these methods could tell us, out of band: «there’s a proxy on the path and it can offer service x, reach it on ip address y and port z»…  but that’s not what we envisioned, i think we can be simpler and more lightweight than that

Sent from my phone

Am 07.11.2024 um 10:53 schrieb Michael Welzl <mic...@ifi.uio.no>:

 Yes!  I’m trying to understand which of them:

--

https://github.com/mwelzl/oppd
---
You received this message because you are subscribed to the Google Groups "oppd-ietf" group.

To unsubscribe from this group and stop receiving emails from it, send an email to oppd-ietf+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/oppd-ietf/C94C2B45-5537-4191-821F-4BF990EAA5C1%40ifi.uio.no.

[Joerg Ott]

But it also becomes apparent that SCONE doesn't strictly need discovery
but only in-band signaling (cf. TCP Quickstart).

On 07.11.24 11:56, Michael Welzl wrote:
> … alternatively, almost all of these methods could tell us, out of band:
> «there’s a proxy on the path and it can offer service x, reach it on ip
> address y and port z»…  but that’s not what we envisioned, i think we
> can be simpler and more lightweight than that
>
>
> Sent from my phone
>
>> Am 07.11.2024 um 10:53 schrieb Michael Welzl <mic...@ifi.uio.no>:
>>
>>  Yes!  I’m trying to understand which of them:
>>
>> - might not require both peers (as the ideas in the oppd overview
>> draft don’t)
>> - guarantee the signal itself being on-path
>>
>> e.g. med’s https://www.ietf.org/archive/id/draft-brw-scone-rate-

>> policy-discovery-00.html <https://www.ietf.org/archive/id/draft-brw-
>> scone-rate-policy-discovery-00.html> can be carried on dhcp, so then

>> ietf/C94C2B45-5537-4191-821F-4BF990EAA5C1%40ifi.uio.no <https://
>> groups.google.com/d/msgid/oppd-ietf/
>> C94C2B45-5537-4191-821F-4BF990EAA5C1%40ifi.uio.no?
>> utm_medium=email&utm_source=footer>.

>
> --
> https://github.com/mwelzl/oppd <https://github.com/mwelzl/oppd>
> ---
> You received this message because you are subscribed to the Google
> Groups "oppd-ietf" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to oppd-ietf+...@googlegroups.com <mailto:oppd-
> ietf+uns...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/oppd-

> ietf/4AD918BB-BFC6-4BCC-ACD9-6E5EC995E3B3%40ifi.uio.no <https://
> groups.google.com/d/msgid/oppd-ietf/4AD918BB-BFC6-4BCC-
> ACD9-6E5EC995E3B3%40ifi.uio.no?utm_medium=email&utm_source=footer>.