[{"author": "Darren Dukes", "text": "

Hi

", "time": "2022-07-27T19:02:39Z"}, {"author": "Darren Dukes", "text": "

mine work haha!

", "time": "2022-07-27T19:02:53Z"}, {"author": "Ted Lemon", "text": "

It works if you use zulip. https://zulip.ietf.org

", "time": "2022-07-27T19:03:10Z"}, {"author": "Behcet Sarikaya", "text": "

@Ted what works?

", "time": "2022-07-27T19:13:54Z"}, {"author": "Bob Hinden", "text": "

Works from Zulip

", "time": "2022-07-27T19:16:52Z"}, {"author": "Jabber", "text": "

mcr: The experience for remote people is better if the chair just shares the preloaded slides, so I'd just assume that is a good default.

", "time": "2022-07-27T19:41:13Z"}, {"author": "Justin Iurman", "text": "

Wasn't the request for a more generic option more about having a generic container to carry IDs? I'm worried about the quick exhaustion of the code points space, considering future use cases with similar requirements (there is already another draft later with another ID carrier)

", "time": "2022-07-27T19:46:48Z"}, {"author": "Justin Iurman", "text": "

later in the agenda*

", "time": "2022-07-27T19:47:30Z"}, {"author": "Bob Hinden", "text": "

Meetecho: Chant not working in Meetecho app

", "time": "2022-07-27T19:51:53Z"}, {"author": "Bob Hinden", "text": "

s/Chant/Chat/

", "time": "2022-07-27T19:52:04Z"}, {"author": "Lorenzo Miniero", "text": "

Checking

", "time": "2022-07-27T19:52:19Z"}, {"author": "\u00c9ric Vyncke", "text": "

Wonder whether RFC 4620 (IPv6 Node Information Queries) could rather be used ?

", "time": "2022-07-27T19:53:05Z"}, {"author": "\u00c9ric Vyncke", "text": "

@meetecho I confirm the problem, I have to use Zulip

", "time": "2022-07-27T19:53:31Z"}, {"author": "Lorenzo Miniero", "text": "

Is the problem you can't get messages, or write? Reading seems to be working fine for us

", "time": "2022-07-27T19:56:12Z"}, {"author": "Bob Hinden", "text": "

I can't send from the Meetecho chat, get an error message

", "time": "2022-07-27T19:57:01Z"}, {"author": "Bob Hinden", "text": "

Reading works

", "time": "2022-07-27T19:57:14Z"}, {"author": "Fernando Gont", "text": "

where's the link to access the video stream frmo zulip?

", "time": "2022-07-27T19:57:37Z"}, {"author": "Lorenzo Miniero", "text": "

Yes, managed to find the issue: it may be a stream configuration issue, we'll investigate

", "time": "2022-07-27T19:58:23Z"}, {"author": "\u00c9ric Vyncke", "text": "

No video in Zulip AFAIK, you need two apps :-( Meetecho for audio/video and Zulip for the chat... A bug probably

", "time": "2022-07-27T19:58:40Z"}, {"author": "Behcet Sarikaya", "text": "

+1 to Eric

", "time": "2022-07-27T20:00:26Z"}, {"author": "Bob Hinden", "text": "

Lorenzo: Thanks!

", "time": "2022-07-27T20:02:39Z"}, {"author": "Erik Kline", "text": "

we already have a solution this: RFC 8801

", "time": "2022-07-27T20:07:25Z"}, {"author": "\u00c9ric Vyncke", "text": "

I was about to write the same about my baby RFC 8801 ;-)

", "time": "2022-07-27T20:08:30Z"}, {"author": "\u00c9ric Vyncke", "text": "

And PvD has received a big incentive for implementation in ADD WG

", "time": "2022-07-27T20:08:51Z"}, {"author": "Eduard V", "text": "

RFC 8801 would be too later becase next hop choice would cut us from proper PIO choice.

", "time": "2022-07-27T20:09:52Z"}, {"author": "Eduard V", "text": "

RFC 8801 is on the slide. It works if source address is chosen first

", "time": "2022-07-27T20:11:05Z"}, {"author": "Erik Kline", "text": "

I don\u2019t agree, or I don\u2019t understand

", "time": "2022-07-27T20:11:40Z"}, {"author": "Bob Hinden", "text": "

Lorenzo: Now I get \"Zulip service logging in...\" in Meetecho app

", "time": "2022-07-27T20:17:20Z"}, {"author": "Lorenzo Miniero", "text": "

@Bob Hinden that was from a previous refresh attempt, I think

", "time": "2022-07-27T20:20:02Z"}, {"author": "Hazel Smith", "text": "

I think you meant to reference RFC3972 as [CGA] in your draft, but it links erroneously to RFC3792 (the 7 and 9 are the wrong way around) btw :)

", "time": "2022-07-27T20:24:15Z"}, {"author": "Hazel Smith", "text": "

(Re: https://datatracker.ietf.org/doc/draft-ev-6man-cga-light/00/)

", "time": "2022-07-27T20:25:01Z"}, {"author": "\u00c9ric Vyncke", "text": "

RFC 7039 ?

", "time": "2022-07-27T20:31:45Z"}, {"author": "Lorenzo Miniero", "text": "

Just FYI, we identified the bug: when the room starts with a number (like 6man or 6lo) there's a broken piece of code that caused messages not to be sent. We'll fix this as soon as we have some time, but unfortunately it cannot be fixed for a running session

", "time": "2022-07-27T20:42:55Z"}, {"author": "Bob Hinden", "text": "

Lorenco: OK, thanks

", "time": "2022-07-27T20:43:30Z"}, {"author": "\u00c9ric Vyncke", "text": "

Happy that we do not have WG starting with special characters ;-)

", "time": "2022-07-27T20:43:45Z"}, {"author": "Lorenzo Miniero", "text": "

:laughing:

", "time": "2022-07-27T20:44:56Z"}, {"author": "\u00c9ric Vyncke", "text": "

draft-li-6man-topology-id-00 a 4-page IETF draft ;-)

", "time": "2022-07-27T20:45:54Z"}, {"author": "\u00c9ric Vyncke", "text": "

And it is a special case of a generalized draft-ietf-6man-enhanced-vpn-vtn-id

", "time": "2022-07-27T20:48:12Z"}]