Meetecho: Connection keeps dropping for the chairs
", "time": "2022-11-07T13:05:51Z"}, {"author": "Ole Tr\u00f8an", "text": "Network connection or Meetecho connection?
", "time": "2022-11-07T13:06:19Z"}, {"author": "Ole Tr\u00f8an", "text": "Worst case I can share slides remotely.
", "time": "2022-11-07T13:06:32Z"}, {"author": "Michael Richardson", "text": "I like SPRING proposal.
", "time": "2022-11-07T13:07:40Z"}, {"author": "Ole Tr\u00f8an", "text": "\"What happens in spring stays in spring\"
", "time": "2022-11-07T13:07:56Z"}, {"author": "Tom Herbert", "text": "Is there audio?
", "time": "2022-11-07T13:08:22Z"}, {"author": "Jabber", "text": "MichaelRichardson: Should you have have even admitted that things happen in spring?
", "time": "2022-11-07T13:08:25Z"}, {"author": "Ole Tr\u00f8an", "text": "Tom: Audio is fine remotely here.
", "time": "2022-11-07T13:08:41Z"}, {"author": "Darren Dukes", "text": "Hello all. The spring/6man division sounds exactly like what is done today but gated by the spring wg chairs. Is that correct?
", "time": "2022-11-07T13:10:10Z"}, {"author": "Ole Tr\u00f8an", "text": "Darren: I think what we are trying to tweak, is that 6man is not the Intarea arm of spring (which is in rtg).
", "time": "2022-11-07T13:11:09Z"}, {"author": "Ole Tr\u00f8an", "text": "And that all new work goes to spring, which either adopts it, or in exceptional cases punts it to 6man. But typically if any 6man involvement at all, only for review.
", "time": "2022-11-07T13:12:06Z"}, {"author": "Darren Dukes", "text": "Thanks ole, good luck with the discussions, I appreciate the clarifications.
", "time": "2022-11-07T13:14:04Z"}, {"author": "Michael Richardson", "text": "yeah to 00!
", "time": "2022-11-07T13:15:08Z"}, {"author": "Tom Herbert", "text": "Fast/Slow Path and Full Forwarding Rate is going to be difficult to use in normative requirements
", "time": "2022-11-07T13:16:39Z"}, {"author": "Ole Tr\u00f8an", "text": "Yeah, those terms have no meaning on some of the implementations I work on.
", "time": "2022-11-07T13:17:45Z"}, {"author": "Jen Linkova", "text": "If anyone would like to have their chat comments to be relayed on the mic, pls add \"RELAY:\" prefix to your message.
", "time": "2022-11-07T13:17:51Z"}, {"author": "Ole Tr\u00f8an", "text": "Not sure if it's helpful to make that split at all. Until we have some real option to discuss, this is all meta regardless. (no hat on).
", "time": "2022-11-07T13:18:58Z"}, {"author": "Dave Thaler", "text": "I just filed https://github.com/ietf-6man/hbh-processing/issues/22 to reflect my feedback at the mic, after I checked the text in the document
", "time": "2022-11-07T13:20:02Z"}, {"author": "Michael Richardson", "text": "also, I might not have captured Ron's comments correctly.
", "time": "2022-11-07T13:22:16Z"}, {"author": "Michael Richardson", "text": "I didn't understand the question/comment.
", "time": "2022-11-07T13:25:51Z"}, {"author": "\u00c9ric Vyncke", "text": "The difference of UDP/TCP probably comes from bigger headers and causing trouble for ASIC assisted layer-4 ACL in transit :-(
", "time": "2022-11-07T13:28:30Z"}, {"author": "Michael Richardson", "text": "\"most accidents occur in the home\"
", "time": "2022-11-07T13:28:54Z"}, {"author": "Tom Herbert", "text": "@eric, yes but 48 bytes is a bit unexpected. I wonder if this is because these devices need the L4 header in the parsing buffer and not just first 8 bytes for ports
", "time": "2022-11-07T13:30:09Z"}, {"author": "Jen Linkova", "text": "Eric: more specifically, I'd guess, TCP flags (e.g. SYN/ACK)
", "time": "2022-11-07T13:30:31Z"}, {"author": "Jen Linkova", "text": "Michael: accidential CPEs ;))
", "time": "2022-11-07T13:30:51Z"}, {"author": "Ole Tr\u00f8an", "text": "They might need some headroom in front of packet too. If it's all supposed to fit in a round number like 128
", "time": "2022-11-07T13:32:45Z"}, {"author": "Eduard V", "text": "After this good cpmparison analisys, I join Ron's request to merge HbH with EH limits.
", "time": "2022-11-07T13:42:19Z"}, {"author": "Darren Dukes", "text": "Hi Tom. I didn\u2019t get a chance to join the queue but I think there is some clarification needed to clarify the node names and the need to consider more than unicast destinations.
\nI\u2019ll send the comments on the list, thanks for the very clear text.
", "time": "2022-11-07T13:45:47Z"}, {"author": "Tom Herbert", "text": "@darren Thanks, look forward to discussion on the list
", "time": "2022-11-07T13:46:59Z"}, {"author": "Michael Richardson", "text": "There are quite a few \"Reserved for IETF\" in https://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xhtml
", "time": "2022-11-07T13:48:03Z"}, {"author": "Michael Richardson", "text": "where will it go? fec0::/10 or 1000::/4 or ...?
", "time": "2022-11-07T13:48:37Z"}, {"author": "\u00c9ric Vyncke", "text": "or a funny one ? ;-)
", "time": "2022-11-07T13:53:31Z"}, {"author": "Jen Linkova", "text": "Anyone from meetecho? I'm getting \"unstable connection\" all the time, while the network seems to be fine (ping doesn't show packet loss)
", "time": "2022-11-07T13:54:09Z"}, {"author": "\u00c9ric Vyncke", "text": "@meetecho see above
", "time": "2022-11-07T13:54:26Z"}, {"author": "Lorenzo Miniero", "text": "Just a sec, we're looking into it
", "time": "2022-11-07T13:57:31Z"}, {"author": "Jen Linkova", "text": "It happened ~15-20 times in the last hour..
", "time": "2022-11-07T13:58:25Z"}, {"author": "Adrian Farrel", "text": "Not just Jen, as presenter. I go thrown out of the meeting twice so far while network is up and fine
", "time": "2022-11-07T13:59:05Z"}, {"author": "Michael Richardson", "text": "here in the room, meetecho is also a bit un-stable, but other web sites seem to come and go too.
", "time": "2022-11-07T14:00:36Z"}, {"author": "Ole Tr\u00f8an", "text": "Meetecho perfectly stable from remote.
", "time": "2022-11-07T14:01:21Z"}, {"author": "Lorenzo Miniero", "text": "Jen: if you're chairing, you can use the ethernet cable on the chair desk to avoid using the wifi
", "time": "2022-11-07T14:01:46Z"}, {"author": "Markus Stenberg", "text": "This has been also fine locally (but not in the room). One case of robot voice only for few seconds.
", "time": "2022-11-07T14:03:07Z"}, {"author": "Michael Richardson", "text": "rather have a 16-bit context-type than a reserved field :-)
", "time": "2022-11-07T14:06:24Z"}, {"author": "Michael Richardson", "text": "I did not get Zhenbin's comments into the minutes. Did someone else catch them?
", "time": "2022-11-07T14:14:34Z"}, {"author": "Eduard V", "text": "Hi Lorenzo, I completely aree to your comment about bind() complexity. But it is what is needed for RFC 8028 to work.
", "time": "2022-11-07T14:23:23Z"}, {"author": "Jen Linkova", "text": "Eduard: could you pls elaborate?
", "time": "2022-11-07T14:24:05Z"}, {"author": "Michael Richardson", "text": "we should not do this, it does not do anything to help the key distribution problem, and just burns oil.
", "time": "2022-11-07T14:28:52Z"}, {"author": "\u00c9ric Vyncke", "text": "With randomized and changing MAC, the load could become important
", "time": "2022-11-07T14:32:24Z"}, {"author": "\u00c9ric Vyncke", "text": "Nice to see the use of 64-bit MAC addresses though ;-)
", "time": "2022-11-07T14:32:48Z"}, {"author": "Michael Richardson", "text": "three meetecho disconnects in the room just now. (I can't see the screen with my computer glasses on... )
", "time": "2022-11-07T14:36:21Z"}, {"author": "Eduard V", "text": "Hi Jen, the assumption that source address is chosen 1st is at the abstract of RFC 8028. Then in the section 3.2 the solution fo this situation is proposed: choose next hop only among routers that advertise already chosen PIO (it is effectively revirse the logic of rule 5.5 in RFC 6724). It is effectively the essense of RFC 8028. The errate pointed by me just makes section 3.2 not needed.
", "time": "2022-11-07T14:36:25Z"}, {"author": "Michael Richardson", "text": "the green P2P lines are hard to see, so look carefully...
", "time": "2022-11-07T14:38:01Z"}, {"author": "Eduard V", "text": "Pascal, you stress 6man when insist that ND should support MLSN (multi-link subnet). It is not always need. It is needed for 802.15.4. It should be optional.
", "time": "2022-11-07T14:39:40Z"}, {"author": "Michael Richardson", "text": "yet, wired ethernet is not broadcast capable either. broadcast is emulated by switch fabrics pretending it's 1984.
", "time": "2022-11-07T14:40:27Z"}, {"author": "Michael Richardson", "text": "even 802.11 with MIMO is not transitive.
", "time": "2022-11-07T14:40:51Z"}, {"author": "Ole Tr\u00f8an", "text": "Eduard: why isn't multilink subnets also needed in traditional networks? Look at SNAC for example.
", "time": "2022-11-07T14:40:56Z"}, {"author": "Ole Tr\u00f8an", "text": "(Many other alternative solutions that WiND of course).
", "time": "2022-11-07T14:41:25Z"}, {"author": "Ole Tr\u00f8an", "text": "s/that/than/g
", "time": "2022-11-07T14:41:33Z"}, {"author": "Eduard V", "text": "Hi Ole, when you need to stitch two L2 domains? It is not very often. It may happen for a big WiFi network too.
", "time": "2022-11-07T14:43:37Z"}, {"author": "Eduard V", "text": "In general, I like more state on the router that Pascal proposes. Any network has a router.
", "time": "2022-11-07T14:46:12Z"}, {"author": "Eduard V", "text": "MLSN is a replacement for proxy.
", "time": "2022-11-07T14:51:00Z"}, {"author": "Michael Richardson", "text": "We need a virtual interim on this topic.
", "time": "2022-11-07T14:51:10Z"}, {"author": "Jabber", "text": "MichaelRichardson: I think we are in violent agreement actually, but we might be using different terminology, and I think that Pascal's goal is to bring some of the things we learnt i ROLL/6lo to \"bigger\" wired networks.
", "time": "2022-11-07T14:51:59Z"}, {"author": "Eduard V", "text": "About \"stab flag\": it may be out of scope but it is not complete because Internet prefix should be distributed for the topology to work. HNCP again.
", "time": "2022-11-07T14:55:11Z"}, {"author": "\u00c9ric Vyncke", "text": "Eduard, you are welcome to SNAC WG mailing list and meeting ;-)
", "time": "2022-11-07T14:56:31Z"}, {"author": "Eduard V", "text": "SNAC is on my calendar.
", "time": "2022-11-07T14:58:02Z"}, {"author": "\u00c9ric Vyncke", "text": ":ok_hand::ok_hand:
", "time": "2022-11-07T15:00:00Z"}]