Should I be finding the webpage with the varying translations of \"my hovercraft is full of eels\"?
", "time": "2024-07-24T22:30:18Z"}, {"author": "John Scudder", "text": "Nit, I think you don't want to replace BCP 194, you want to kick RFC 7454 out of BCP 194 and replace that. The BCP number stays the same. As I understand it.
", "time": "2024-07-24T22:37:34Z"}, {"author": "Jeffrey Haas", "text": "With regard to the attribute filtering stuff, I'm not sure that one matches reality fully.
", "time": "2024-07-24T22:38:18Z"}, {"author": "Job Snijders", "text": "welcome everyone! I am monitoring the chat
", "time": "2024-07-24T22:38:57Z"}, {"author": "Job Snijders", "text": "@John Scudder yes the BCP number will stay the same
", "time": "2024-07-24T22:39:15Z"}, {"author": "John Scudder", "text": "I'm not sure why Tobias keeps saying BCPs are hard to update. They are (should be) the same as any other RFC. There are some nitpicky details about IESG ballots but they aren't important.
", "time": "2024-07-24T22:41:31Z"}, {"author": "Randy Bush", "text": "is it a switch or a router?
", "time": "2024-07-24T22:46:36Z"}, {"author": "Jeffrey Haas", "text": "Something that will be watched anyway, but we'll want to make sure the BGP terminology ends up \"acceptable\" to all of the impacted groups like IDR and SIDROPS
", "time": "2024-07-24T22:47:35Z"}, {"author": "John Scudder", "text": "You can publish an RFC, or nothing, those are the real options that exist. Do you want to publish something or not?
", "time": "2024-07-24T22:47:50Z"}, {"author": "John Scudder", "text": "In the future when we have a better option, use that instead.
", "time": "2024-07-24T22:48:03Z"}, {"author": "John Scudder", "text": "Also, what @Jeff said.
", "time": "2024-07-24T22:48:18Z"}, {"author": "John Scudder", "text": "+lots to @Warren
", "time": "2024-07-24T22:49:28Z"}, {"author": "Jeffrey Haas", "text": "+1 to warren.
", "time": "2024-07-24T22:49:31Z"}, {"author": "Randy Bush", "text": "is warren a switch or a router?
", "time": "2024-07-24T22:49:48Z"}, {"author": "John Scudder", "text": "It's basically tag and ship
", "time": "2024-07-24T22:49:50Z"}, {"author": "Chris Morrow", "text": "router
", "time": "2024-07-24T22:50:03Z"}, {"author": "John Scudder", "text": "Based on the hat I'd say witch
", "time": "2024-07-24T22:50:06Z"}, {"author": "Chris Morrow", "text": "brouter
", "time": "2024-07-24T22:50:26Z"}, {"author": "John Scudder", "text": "Is that like a router-bro?
", "time": "2024-07-24T22:50:42Z"}, {"author": "Jeffrey Haas", "text": "But is he a Good Witch\u2122 or a Bad Witch\u2122?
", "time": "2024-07-24T22:50:58Z"}, {"author": "Randy Bush", "text": "which wwitch?
", "time": "2024-07-24T22:51:13Z"}, {"author": "Chris Morrow", "text": "3com, a long long time ago made a 'brouter' which was a bridge and router in the same box....
", "time": "2024-07-24T22:51:15Z"}, {"author": "Chris Morrow", "text": "'bridging router' or something.
", "time": "2024-07-24T22:51:21Z"}, {"author": "John Scudder", "text": "I don't think the point about \"what if we run out of energy to push bisses\" is any better with another format. It just turns into \"what happens when the tumbleweeds start blowing through the wiki\".
", "time": "2024-07-24T22:51:27Z"}, {"author": "John Scudder", "text": "I remember the brouter actually, though I'd forgotten it was 3com
", "time": "2024-07-24T22:51:46Z"}, {"author": "Randy Bush", "text": "remembering some things is an indication of age
", "time": "2024-07-24T22:52:17Z"}, {"author": "Jeffrey Haas", "text": "A reason I like the periodic RFC is that, as noted earlier in the presentation, we have Important People (or at least lawyers and politicians) looking at our stuff.
", "time": "2024-07-24T22:52:17Z"}, {"author": "John Scudder", "text": "^^^^
", "time": "2024-07-24T22:52:25Z"}, {"author": "Jeffrey Haas", "text": "<3 for the tcp-ao.
", "time": "2024-07-24T22:53:56Z"}, {"author": "Tobias Fiebig", "text": "@John Scudder me saying 'replace bcp194' is a terminology fnord; What i mean with that is indeed 'get new RFC published, take out 7454, put in new RFC'; I will try to use more accurate language in the future.
", "time": "2024-07-24T22:55:27Z"}, {"author": "John Scudder", "text": "Cool. I thought that was probably so, but reckoned better to be clear.
", "time": "2024-07-24T22:56:23Z"}, {"author": "Jeffrey Haas", "text": "Camillo, it's okay if the model isn't \"perfect\" in terms of \"having everything\". YANG augmentation works very nicely. The critical detail is to have the skeleton for the new nodes to be mounted later.
", "time": "2024-07-24T22:57:10Z"}, {"author": "Jeffrey Haas", "text": "augmented
", "time": "2024-07-24T22:59:29Z"}, {"author": "Jeffrey Haas", "text": "Not recently
", "time": "2024-07-24T23:00:07Z"}, {"author": "Jeffrey Haas", "text": "I have to step out for a call, but please consider @-ing me if there's something you're assigning as reading. :-)
", "time": "2024-07-24T23:00:54Z"}, {"author": "John Scudder", "text": "\"I think I hear my mother calling...\"
", "time": "2024-07-24T23:01:20Z"}, {"author": "Pierre Francois", "text": "He has some augmountations to do
", "time": "2024-07-24T23:01:43Z"}, {"author": "Jeffrey Haas", "text": "The thing that I heard as I was heading out the door was whether juniper currently does schema mount now. not yet, but multiple vendors will eventually get pushed that way. I'll review for multi-instance configuration later.
", "time": "2024-07-24T23:03:15Z"}, {"author": "Job Snijders", "text": "@Jeffrey Haas we noted as summary that perhaps the next version of the draft should try to avoid schema-mount - unless vendors signal that its coming down the road
@Tobias Fiebig thanks for mentioning RFC 9234, I think that's a spec to take some inspiration from
", "time": "2024-07-24T23:16:15Z"}, {"author": "Jenny Ramseyer", "text": "Yes, thank you! I will read it and share with my coauthors.
", "time": "2024-07-24T23:16:57Z"}, {"author": "Tobias Fiebig", "text": "I can also join the small operator chat with Q; I might have some ASes around that might be useful playgrounds for letting demo implementations run without tainting _actual_ production.
", "time": "2024-07-24T23:17:53Z"}, {"author": "Tobias Fiebig", "text": "i.e., for my ASes it is er... not as bad if things break.
", "time": "2024-07-24T23:18:18Z"}, {"author": "Jeffrey Haas", "text": "Job Snijders said:
\n\n\nJeffrey Haas we noted as summary that perhaps the next version of the draft should try to avoid
\nschema-mount- unless vendors signal that its coming down the road
Mostly at this point of model life cycle is that models should be safe to be used for schema mount, not use it itself directly.
", "time": "2024-07-24T23:18:25Z"}, {"author": "Jeffrey Haas", "text": "An example of such a thing is that even if a bmp model doesn't support juniper's logical routers, if we schema mount bmp in a LR instance, it can be used.
", "time": "2024-07-24T23:19:36Z"}, {"author": "Job Snijders", "text": "@Jenny Ramseyer section 4.2 contains a simple truth table that could be used: if one peers indicates it is a 'rs-client', and the other side indicates it is 'rs' can proceed, and similarly if one side indicates it is a 'peer', the other side also must consider itself a 'peer' for the handshake process to progress. I believe such an approach would satisfy both Tobias' and Ben's, and my own feedback
", "time": "2024-07-24T23:20:05Z"}, {"author": "Chris Morrow", "text": "@meetecho help with reconnecing the chair station to the meeting?
", "time": "2024-07-24T23:20:21Z"}, {"author": "Job Snijders", "text": "so i guess, add a field called \"role\", and populate it with (a subset of) values from RFC 9234
", "time": "2024-07-24T23:20:28Z"}, {"author": "Lorenzo Miniero", "text": "Looking into this
", "time": "2024-07-24T23:20:33Z"}, {"author": "Lorenzo Miniero", "text": "Looks like a few streamers in front lost connectivity too
", "time": "2024-07-24T23:20:45Z"}, {"author": "Chris Morrow", "text": "can we .. camera1 back on
", "time": "2024-07-24T23:22:01Z"}, {"author": "Lorenzo Miniero", "text": "All streamers should be back now, can you confirm?
", "time": "2024-07-24T23:22:47Z"}, {"author": "Chris Morrow", "text": "looks great, thanks!
", "time": "2024-07-24T23:22:55Z"}, {"author": "Jenny Ramseyer", "text": "Thanks, I will take a look at the draft, but the idea of \"role\" and truth table seems like a logical one to use here.
", "time": "2024-07-24T23:23:10Z"}, {"author": "Job Snijders", "text": "thanks @Lorenzo Miniero !
", "time": "2024-07-24T23:23:12Z"}, {"author": "Randy Bush", "text": "re-aim speaker cam?
", "time": "2024-07-24T23:23:12Z"}, {"author": "Randy Bush", "text": "thx
", "time": "2024-07-24T23:23:24Z"}, {"author": "Job Snijders", "text": "apologies for the hickup caused by @Warren Kumari
", "time": "2024-07-24T23:23:43Z"}, {"author": "Juan Cardona", "text": "What I haven't been able to make work is referencing a monitoring station, which is defined at the root, within the bgp container within a network instance. I'll try this a bit more BUT we'll keep the model open to not use schema mount
", "time": "2024-07-24T23:26:49Z"}, {"author": "Jeffrey Haas", "text": "I'll leave my comment for chat: For the \"report in policy\", it's going to have to be EITHER a string (vendor specific) or leafref (abstract) at best. Nothing else will be safely work.
", "time": "2024-07-24T23:28:18Z"}, {"author": "Jeffrey Haas", "text": "Much to Ben's unhappiness, the reference policy element will almost certainly be a structured element, but there's no generic way to define it in yang right now.
", "time": "2024-07-24T23:29:44Z"}, {"author": "Randy Bush", "text": "@meetech: cam to speaker, please
", "time": "2024-07-24T23:45:51Z"}, {"author": "Randy Bush", "text": "thank you
", "time": "2024-07-24T23:46:10Z"}, {"author": "Jeffrey Haas", "text": "The type 5 address + name is interesting. The type 4 ifIndex is more common since that value can be cross-correlated with other things like snmp/yang that use that as the foreign key.
", "time": "2024-07-24T23:48:11Z"}]