[{"author": "Andy Malis", "text": "

We hear you!

", "time": "2022-07-25T17:31:06Z"}, {"author": "Christian Hopps", "text": "

Did I just hear jabber was being retired next IETF?

", "time": "2022-07-25T17:36:21Z"}, {"author": "Andy Malis", "text": "

@Christian yes, starting next IETF it's Zulip only

", "time": "2022-07-25T17:37:19Z"}, {"author": "Adrian Farrel", "text": "

@chopps That what I have heard

", "time": "2022-07-25T17:38:18Z"}, {"author": "Jeffrey Haas", "text": "

as long as it all works from this unified meetecho view, probably not a big deal.

", "time": "2022-07-25T17:39:22Z"}, {"author": "Lorenzo Miniero", "text": "

@Jeffrey Haas yes, we're already using Zulip

", "time": "2022-07-25T17:39:53Z"}, {"author": "Dhruv Dhody", "text": "

would be nice if Zulip could be used outside of meeting as well

", "time": "2022-07-25T17:40:01Z"}, {"author": "Tony Li", "text": "

@Lorenzo Miniero That's not what Jeff asked. :)

", "time": "2022-07-25T17:43:21Z"}, {"author": "Dhruv Dhody", "text": "

https://www.ietf.org/mailman/listinfo/routing-discussion

", "time": "2022-07-25T17:44:27Z"}, {"author": "Lorenzo Miniero", "text": "

@Tony Li what I meant is that Meetecho is already using Zulip under the hood, not Jabber, so the integration is already there. We send to the \"jabber\" topic so that it's mirrored to the Jabber room, but then display any incoming message related to any topic

", "time": "2022-07-25T17:44:30Z"}, {"author": "Jeffrey Haas", "text": "

Great that's it's already done. Thanks for the clarification!

", "time": "2022-07-25T17:45:01Z"}, {"author": "Tony Li", "text": "

So when Jabber goes away, will the Meetecho chat interface remain the same or do we have to use the Zulip app?

", "time": "2022-07-25T17:45:14Z"}, {"author": "Lorenzo Miniero", "text": "

It will remain mostly the same, but probably with some additional UI changes to reflect the topic of the message

", "time": "2022-07-25T17:45:46Z"}, {"author": "Tony Li", "text": "

Cool, thank you.

", "time": "2022-07-25T17:46:01Z"}, {"author": "Lorenzo Miniero", "text": "

At the moment we just display incoming messages with no info on the topic they pertain to

", "time": "2022-07-25T17:46:05Z"}, {"author": "Tony Li", "text": "

Starting a Bad Attitude topic.

", "time": "2022-07-25T17:53:34Z"}, {"author": "Dhruv Dhody", "text": "

@ADs - perhaps add the routing-discussion@ietf.org mailing list in datatracker https://datatracker.ietf.org/ag/rtgarea/about/

", "time": "2022-07-25T17:54:33Z"}, {"author": "Christian Hopps", "text": "

Present

", "time": "2022-07-25T17:55:50Z"}, {"author": "Andrew Alston", "text": "

Thanks Dhruv, we will get that sorted

", "time": "2022-07-25T17:56:15Z"}, {"author": "Nagarajan Duraisamy", "text": "

Isn't CAN a registered copyrighted trademark of Robert Bosch ?

", "time": "2022-07-25T17:59:11Z"}, {"author": "Tony Li", "text": "

One more time, with feeling: routing is not a dump truck.

", "time": "2022-07-25T18:07:54Z"}, {"author": "Dirk Trossen", "text": "

@Tony I am fine with describing this as a load balancer, i.e., instance selection problem, but it is proposed to be done on-path, not off-path.

", "time": "2022-07-25T18:08:30Z"}, {"author": "Tony Li", "text": "

@Dirk Trossen I don't see how that matters one whit.

", "time": "2022-07-25T18:09:01Z"}, {"author": "Adrian Farrel", "text": "

If routing is not a dump truck, where are we gonna have our fire?

", "time": "2022-07-25T18:09:03Z"}, {"author": "Dirk Trossen", "text": "

@Tony (again) whether or not appropriate signaling would be dumped into a routing protocol is up for discussion - I do see your point and personally agree to it.

", "time": "2022-07-25T18:09:28Z"}, {"author": "Jeff Tantsura", "text": "

When you have got a hammer\u2026

", "time": "2022-07-25T18:09:56Z"}, {"author": "Dirk Trossen", "text": "

@Tony it does matter when looking at the latency imposed by off-path signaling. So I don't get the \"not one whit\" - how much it does matter is to be clarified, indeed, though.

", "time": "2022-07-25T18:10:22Z"}, {"author": "Anthony Somerset", "text": "

Confirmed - https://trademarks.justia.com/791/03/can-79103365.html

\n

Nagarajan Duraisamy said:

\n
\n

Isn't CAN a registered copyrighted trademark of Robert Bosch ?

\n
", "time": "2022-07-25T18:10:34Z"}, {"author": "Tony Li", "text": "

@Dirk Trossen I have no issues with you doing on-path LB signalling, as long as it's outside of routing.

", "time": "2022-07-25T18:11:19Z"}, {"author": "Tony Li", "text": "

ALTO is in transport area.

", "time": "2022-07-25T18:11:57Z"}, {"author": "Anthony Somerset", "text": "

Adrian Farrel said:

\n
\n

If routing is not a dump truck, where are we gonna have our fire?

\n
\n

send it to the transport area? runs

", "time": "2022-07-25T18:12:47Z"}, {"author": "Dirk Trossen", "text": "

@Tony Alto is done above L3, CAN/dyncast proposes to do at L3. Whether it will use a routing protocol to convey/signal the information is to be seen.

", "time": "2022-07-25T18:13:10Z"}, {"author": "Dhruv Dhody", "text": "

RFC 6123 - https://datatracker.ietf.org/doc/rfc6123/

", "time": "2022-07-25T18:16:53Z"}, {"author": "Dhruv Dhody", "text": "

Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group Drafts

", "time": "2022-07-25T18:19:16Z"}, {"author": "Adrian Farrel", "text": "

Also look at RFC 5706

", "time": "2022-07-25T18:20:20Z"}, {"author": "Dhruv Dhody", "text": "

https://www.rfc-editor.org/cluster_info.php?cid=C336

", "time": "2022-07-25T18:21:08Z"}, {"author": "Dhruv Dhody", "text": "

BFD yang is published -> rfc9127

", "time": "2022-07-25T18:21:25Z"}]