[{"author": "Susan Hares", "text": "Did anyone else have a problem with meetecho crashing?<br/>", "time": "2022-03-25T09:02:02Z"}, {"author": "Susan Hares", "text": "My meetecho has crashed.<br/>", "time": "2022-03-25T09:03:01Z"}, {"author": "Susan Hares", "text": "go ahead - it looks like I must restart something.<br/>", "time": "2022-03-25T09:03:10Z"}, {"author": "Mahesh Jethanandani", "text": "Did you want me to try sharing slides<br/>", "time": "2022-03-25T09:03:42Z"}, {"author": "Andrew Alston", "text": "Loud and clear :)<br/>", "time": "2022-03-25T09:07:33Z"}, {"author": "Eduard V", "text": "good audio<br/>", "time": "2022-03-25T09:07:38Z"}, {"author": "Tony Li", "text": "Please use display mode<br/>", "time": "2022-03-25T09:08:07Z"}, {"author": "Andrew Alston", "text": "will second that<br/>", "time": "2022-03-25T09:08:51Z"}, {"author": "Andrew Alston", "text": "hard to see in this mode<br/>", "time": "2022-03-25T09:08:53Z"}, {"author": "Joel Halpern", "text": "I guess if we want to read the slides we can go look at the agenda :-)<br/>", "time": "2022-03-25T09:09:01Z"}, {"author": "Tony Li", "text": "Hopefully they are the same. :smiley:<br/>", "time": "2022-03-25T09:10:14Z"}, {"author": "Susan Hares", "text": "Hopefully.. (smile)<br/>", "time": "2022-03-25T09:10:28Z"}, {"author": "Randy Bush", "text": "before the Note Well is the Hear Well, for which there seem to be no slides.<br/>", "time": "2022-03-25T09:11:00Z"}, {"author": "Mahesh Jethanandani", "text": ":grinning:<br/>", "time": "2022-03-25T09:12:54Z"}, {"author": "Mahesh Jethanandani", "text": "Sue, you are marked offline in Meetecho<br/>", "time": "2022-03-25T09:17:46Z"}, {"author": "Keyur Patel", "text": "Aplogies!<br/>", "time": "2022-03-25T09:19:51Z"}, {"author": "Jeffrey Haas", "text": "This work can only have been done with a codepoint that has been squatted on.<br/>", "time": "2022-03-25T09:21:14Z"}, {"author": "Tony Przygienda", "text": "yupp. usual discussion how to prevent people from coming with squats to rubberstamp them. Not that theiy're the first ones ;-) and it's up to earlier vendors who made that part of the manners ...<br/>", "time": "2022-03-25T09:22:48Z"}, {"author": "Jie Dong", "text": "@ Wim, you voice is quite low, could you add your comments to the notes? thanks<br/>", "time": "2022-03-25T09:22:55Z"}, {"author": "Tony Przygienda", "text": "@ Wim + 1<br/>", "time": "2022-03-25T09:23:02Z"}, {"author": "Jeffrey Haas", "text": "If vendors are going to ship implementations of flowspec features without waiting on flowspec v2, we're going to start regularly seeing session resets.<br/>", "time": "2022-03-25T09:24:08Z"}, {"author": "Jeffrey Haas", "text": "The working group should reconsider picking up <a href=\"https://datatracker.ietf.org/doc/draft-haas-flowspec-capability-bits/\" rel=\"nofollow\">https://datatracker.ietf.org/doc/draft-haas-flowspec-capability-bits/</a> as a temporary workaround until flowspec v2 is out.<br/>", "time": "2022-03-25T09:24:25Z"}, {"author": "Susan Hares", "text": "Flow specification v2 is under adoption.<br/>", "time": "2022-03-25T09:24:41Z"}, {"author": "Christian Hopps", "text": "@meetecho The in room mics are mixed in very low, been that way all week, while they apparently sound good in room they are very quiet remotely (and if the person isn't very loud they can sound silent)<br/>", "time": "2022-03-25T09:24:42Z"}, {"author": "Jeffrey Haas", "text": "@chopps I believe meetecho has been doing so to avoid room feedback.<br/>", "time": "2022-03-25T09:25:15Z"}, {"author": "Christian Hopps", "text": "Unfortunately this isn't just my setup, if you view the recordings the in room mics are also ~~silent for those as well.<br/>", "time": "2022-03-25T09:25:38Z"}, {"author": "Susan Hares", "text": "I cannot hear<br/>", "time": "2022-03-25T09:25:50Z"}, {"author": "Jie Dong", "text": "@Keyur did we skipped the 3rd topic?<br/>", "time": "2022-03-25T09:25:51Z"}, {"author": "Christian Hopps", "text": "@jeff yeah, but there needs to be a better solution, the recordings are even messed up now<br/>", "time": "2022-03-25T09:26:06Z"}, {"author": "Meetecho", "text": "We can try bumping the levels up a bit<br/>", "time": "2022-03-25T09:26:27Z"}, {"author": "Robert Raszuk", "text": "@Jeff Perhaps to mitigate impact of flowspec triggered session reset to other SAFIs from day one flowspec v2 should run on separate session as default and the only mode ? How about different port then 179 ?<br/>", "time": "2022-03-25T09:26:37Z"}, {"author": "Susan Hares", "text": "please bump the levels<br/>", "time": "2022-03-25T09:26:55Z"}, {"author": "Jeffrey Haas", "text": "The avalanche has already started. It is too late for the pebbles to vote.<br/>", "time": "2022-03-25T09:27:03Z"}, {"author": "Tony Li", "text": "The usual fix for the feedback is to use in-room mics that have a very short range.<br/>", "time": "2022-03-25T09:27:11Z"}, {"author": "Eduard V", "text": "1sd day I have heard an echo from the room. Now the mic is low - echo disappeared. But it is not possible to hear questions.<br/>", "time": "2022-03-25T09:27:16Z"}, {"author": "Christian Hopps", "text": "@meetecho I mean I don't want to cause echoback trouble either, i guess something else has to be done maybe, like mix the in room mix stream into remote stream high level, but not for the in room speakers<br/>", "time": "2022-03-25T09:27:19Z"}, {"author": "Zhen Tan", "text": "Was the 3rd topic skipped?<br/>", "time": "2022-03-25T09:27:53Z"}, {"author": "Tony Li", "text": "But that means that the uses of the mic basically have to eat the mic to be heard. #AVgeek<br/>", "time": "2022-03-25T09:28:06Z"}, {"author": "Susan Hares", "text": "flow specification v2 is being deployed.<br/>", "time": "2022-03-25T09:28:06Z"}, {"author": "Jeffrey Haas", "text": "What are the implementations, sue?<br/>", "time": "2022-03-25T09:28:26Z"}, {"author": "Susan Hares", "text": "that was a question.<br/>", "time": "2022-03-25T09:28:31Z"}, {"author": "Susan Hares", "text": "Flow specification v2 is being deployed??<br/>", "time": "2022-03-25T09:28:41Z"}, {"author": "Jeffrey Haas", "text": "fsv2 is without safi&nbsp;&nbsp;it can't be interoperably deployed.<br/>", "time": "2022-03-25T09:29:42Z"}, {"author": "Mahesh Jethanandani", "text": "Keyur confirmed that he will come back to the third presentation.<br/>", "time": "2022-03-25T09:30:44Z"}, {"author": "Keyur Patel", "text": "@zhen: will get back on discussion after this preso<br/>", "time": "2022-03-25T09:31:00Z"}, {"author": "Zhen Tan", "text": "Thx<br/>", "time": "2022-03-25T09:31:13Z"}, {"author": "Robert Raszuk", "text": "aren't bunch of fsv2 elements stuffed into fsv1 today ?<br/>", "time": "2022-03-25T09:31:41Z"}, {"author": "Christian Hopps", "text": "the order of the slides in the list is not always in your agenda order<br/>", "time": "2022-03-25T09:33:54Z"}, {"author": "Christian Hopps", "text": "so if you just go down your list online you may go out of order :)<br/>", "time": "2022-03-25T09:34:12Z"}, {"author": "Randy Bush", "text": "speaker very dimly heard<br/>", "time": "2022-03-25T09:34:18Z"}, {"author": "Meetecho", "text": "He's low in the remote audio too, that's how his browser is capturing the mic I'm afraid<br/>", "time": "2022-03-25T09:34:43Z"}, {"author": "Boris Khasanov", "text": "voice is very low and breaking<br/>", "time": "2022-03-25T09:34:50Z"}, {"author": "Simon Leinen", "text": "Much better now, thanks!<br/>", "time": "2022-03-25T09:35:10Z"}, {"author": "Christian Hopps", "text": "and viola new route path<br/>", "time": "2022-03-25T09:35:14Z"}, {"author": "Jeffrey Haas", "text": "Repeating my comments to Wu Zhiwen: The wide communities authors will be asked to comment on contents of your wide community format.&nbsp;&nbsp;The second is please to discuss in the document how this interacts with previous redirect community types.<br/>", "time": "2022-03-25T09:42:30Z"}, {"author": "Robert Raszuk", "text": "@Jeff - This is new type so I do not see any encoding issues - do you ?<br/>", "time": "2022-03-25T09:44:34Z"}, {"author": "Jeffrey Haas", "text": "@robert I've given the draft at most a quick skim - it is recently published.&nbsp;&nbsp;I think they're defining a color atom?<br/>", "time": "2022-03-25T09:45:40Z"}, {"author": "Robert Raszuk", "text": "Ok let me review the new version. I was just referring to what I have seen before.<br/>", "time": "2022-03-25T09:46:28Z"}, {"author": "Jeffrey Haas", "text": "actually, I'm incorrect. They're defining multiple atoms for the composite ip+weight, as examples.<br/>", "time": "2022-03-25T09:46:54Z"}, {"author": "Jeffrey Haas", "text": "in any case, review would be good. we'll discuss together and on-list.<br/>", "time": "2022-03-25T09:47:12Z"}, {"author": "Ran Chen", "text": "Hi Jie<br/>", "time": "2022-03-25T09:49:24Z"}, {"author": "Ran Chen", "text": "and WG ,we also have a draft about BGP-LS extension for NRP ID. I would like to draw your attention, thanks<br/>", "time": "2022-03-25T09:50:48Z"}, {"author": "Zhen Tan", "text": "@Jeffrey yes, we defined several atoms composite of&nbsp;&nbsp;ip, color and weight, each represents a redirection path/action<br/>", "time": "2022-03-25T09:56:12Z"}, {"author": "Jeffrey Haas", "text": "@zhen tan Your use case is clear.&nbsp;&nbsp;Atoms were originally intended to be simple core types and extension was thought to be rare.&nbsp;&nbsp;We wish to figure out how to let your work move forward without perhaps changing the meaning of \"atom\".<br/>", "time": "2022-03-25T09:58:34Z"}, {"author": "Jeffrey Haas", "text": "We will send comments to the list.<br/>", "time": "2022-03-25T09:59:05Z"}, {"author": "Jie Dong", "text": "@ran, thanks I will take a look<br/>", "time": "2022-03-25T10:00:19Z"}, {"author": "Robert Raszuk", "text": "@jeff &amp; @zhen - yes we have defined atoms to simplify processing of sub-type 1,2 &amp; 3 of wide community TLVs. However IMO we did not prohibit to define new types which will not use atoms and will be consumed as defined. In fact if we would lock any extensions to predefined atoms that would limit the scope. So to me what authors defined in a new sub-type with no atoms. let's discuss further on the list.<br/>", "time": "2022-03-25T10:03:24Z"}, {"author": "Jeffrey Haas", "text": "exactly. :-)<br/>", "time": "2022-03-25T10:03:54Z"}, {"author": "Susan Hares", "text": "Zhen/Zhiwen:&nbsp;&nbsp;One question is whether Atom 3 in the wide communities (IPv6 prefix list) and your atom type 5 could be merged.<br/>", "time": "2022-03-25T10:04:41Z"}, {"author": "Boris Khasanov", "text": "are there any other approaches (drafts) besides FS usage for SR to load balance inside the LAG?<br/>", "time": "2022-03-25T10:05:48Z"}, {"author": "Ketan Talaulikar", "text": "@Boris, you mean direct traffic on specific member links of the LAG ?<br/>", "time": "2022-03-25T10:07:00Z"}, {"author": "Jeffrey Haas", "text": "Hadn't someone done a pcep draft for such load balancing?&nbsp;&nbsp;My memory was that they leveraged flowspec syntax for something like this.<br/>", "time": "2022-03-25T10:07:32Z"}, {"author": "Boris Khasanov", "text": "@Ketan, - yes, ECMP or UCMP between LAG member links.ccccc cvktdvugkbfvcchugfrduekbfehhugbfbfrhihr<br/>", "time": "2022-03-25T10:09:08Z"}, {"author": "Boris Khasanov", "text": "Sorry, keyboard issue<br/>", "time": "2022-03-25T10:09:40Z"}, {"author": "Ketan Talaulikar", "text": "@Boris, there are L2 adjacency SIDs defined and then these can be used in SR Policies (or segment lists within SR policies) to achieve this objective<br/>", "time": "2022-03-25T10:09:58Z"}, {"author": "Boris Khasanov", "text": "ccccccvktdvurjilegcvujhtgtjretvtcbflkruujcth<br/>", "time": "2022-03-25T10:10:12Z"}, {"author": "Ketan Talaulikar", "text": "so the components are available<br/>", "time": "2022-03-25T10:10:15Z"}, {"author": "Ketan Talaulikar", "text": "@Boris .. i couldn't parse that ;-)<br/>", "time": "2022-03-25T10:10:28Z"}, {"author": "Robert Raszuk", "text": ":)<br/>", "time": "2022-03-25T10:10:33Z"}, {"author": "Jeffrey Haas", "text": "I think Boris has a cat trying to participate in IETF.<br/>", "time": "2022-03-25T10:10:47Z"}, {"author": "Tony Li", "text": "Cyrillic keyboard, ASCII chat. :)<br/>", "time": "2022-03-25T10:10:54Z"}, {"author": "Tony Przygienda", "text": "make meetecho utf-8 ;-)<br/>", "time": "2022-03-25T10:11:13Z"}, {"author": "Boris Khasanov", "text": "Looks that my keyboard&nbsp;&nbsp;lives in her own way during last 2 days :)<br/>", "time": "2022-03-25T10:11:24Z"}, {"author": "Ketan Talaulikar", "text": "@TonyP ... yes UTF-8 !!!<br/>", "time": "2022-03-25T10:11:39Z"}, {"author": "Robert Raszuk", "text": "\u0418\u0434\u0438 \u043d\u0430 \u0445..\u0439<br/>", "time": "2022-03-25T10:13:00Z"}, {"author": "Robert Raszuk", "text": "Works fine<br/>", "time": "2022-03-25T10:13:05Z"}, {"author": "Susan Hares", "text": "@Jeff+@Robert - Are we looking to reuse Atoms 2-4 in Wide communities?&nbsp;&nbsp;Or do you prefer atoms are specific (IPv6 + weight).<br/>", "time": "2022-03-25T10:13:11Z"}, {"author": "Boris Khasanov", "text": "@Ketan, adj sid as far as i remember cannot be assigned to individual LAG members links, only to whole LAG, isn't it?<br/>", "time": "2022-03-25T10:13:17Z"}, {"author": "Jeffrey Haas", "text": "@sue I'll offer a proper evaluation after I've gotten enough sleep and do a full read of the draft.<br/>", "time": "2022-03-25T10:13:46Z"}, {"author": "Ketan Talaulikar", "text": "@ Boris RFC8668 and there is equivalent WG draft for OSPF as well<br/>", "time": "2022-03-25T10:14:03Z"}, {"author": "Zhen Tan", "text": "@Jeffrey&amp;Robert, what we are trying to do is to define \"type-exclusivcely\" atoms, only used with the certain type of wide-community. I am not sure weather this will fit the wide-comm scope? Looking forward to your emails.<br/>", "time": "2022-03-25T10:14:24Z"}, {"author": "Jeffrey Haas", "text": "@zhen tan your idea will fit into a community container fine.&nbsp;&nbsp;I think the terminology may need small adjustment..<br/>", "time": "2022-03-25T10:15:06Z"}, {"author": "Zhen Tan", "text": "@Susan, we are going to think about it, thank you for your commts<br/>", "time": "2022-03-25T10:15:35Z"}, {"author": "Jeffrey Haas", "text": "The goal for community container was to be expandable for use cases for structured policy elements.<br/>", "time": "2022-03-25T10:15:39Z"}, {"author": "Jeffrey Haas", "text": "I think where the conversation may go is whether the idea of an \"atom\" is a globally defined thing across all types of wide communities or whether we have them that are scoped per type.<br/>", "time": "2022-03-25T10:16:18Z"}, {"author": "Jeffrey Haas", "text": "This is not a difficult issue.&nbsp;&nbsp;I look forward to seeing this as a use case for expanding the use of the feature.<br/>", "time": "2022-03-25T10:16:43Z"}, {"author": "Robert Raszuk", "text": "@jeff - exactly<br/>", "time": "2022-03-25T10:18:14Z"}, {"author": "Zhen Tan", "text": "well, thk, ;-)<br/>", "time": "2022-03-25T10:18:35Z"}, {"author": "Boris Khasanov", "text": "@Robert, let's not use obscene lexicon.<br/>", "time": "2022-03-25T10:19:18Z"}, {"author": "Ketan Talaulikar", "text": "@KaZhang, I would recommend you to look at FlexAlgorithm draft and specifically the IGP metric types. Please consider using them instead of introducing new semantics - especially since your draft is talking about IGPs.<br/>", "time": "2022-03-25T10:19:44Z"}, {"author": "Jeffrey Haas", "text": "@ketan could you please send the relevant reference to the mailing list?<br/>", "time": "2022-03-25T10:20:19Z"}, {"author": "Ketan Talaulikar", "text": "@Jeff Ack<br/>", "time": "2022-03-25T10:20:34Z"}, {"author": "Boris Khasanov", "text": "@Ketan - thank you for pointing to RFC8668<br/>", "time": "2022-03-25T10:20:57Z"}, {"author": "Tony Li", "text": "<a href=\"https://datatracker.ietf.org/doc/html/draft-ietf-lsr-flex-algo-18\" rel=\"nofollow\">https://datatracker.ietf.org/doc/html/draft-ietf-lsr-flex-algo-18</a><br/>", "time": "2022-03-25T10:21:00Z"}, {"author": "Ketan Talaulikar", "text": "specifically : <a href=\"https://datatracker.ietf.org/doc/html/draft-ietf-lsr-flex-algo-18#section-18.1.2\" rel=\"nofollow\">https://datatracker.ietf.org/doc/html/draft-ietf-lsr-flex-algo-18#section-18.1.2</a> ... note that there are other drafts that have introduced more types - it should get into IANA once the base FlexAlgo draft progresses<br/>", "time": "2022-03-25T10:22:31Z"}, {"author": "Jeffrey Haas", "text": "The request for sending it to the mail list is partially to help make sure wider WG discussion takes it as an input.&nbsp;&nbsp;Having it solely in chat might mean it ends up in the minutes, but we'd have to be careful to capture it.<br/>", "time": "2022-03-25T10:23:28Z"}, {"author": "Ketan Talaulikar", "text": "@Jeff ... got it and will do<br/>", "time": "2022-03-25T10:24:02Z"}, {"author": "Jeffrey Haas", "text": "decimal32 is only as difficult as IEEE float.<br/>", "time": "2022-03-25T10:27:06Z"}, {"author": "Jeffrey Haas", "text": "it's messy enogh that a common flowspec use bug for rate-limit is sending a integer in a float field :-)<br/>", "time": "2022-03-25T10:27:46Z"}, {"author": "Susan Hares", "text": "Shuping - would it be possible to contact me offlist on the traffic filtering actions?<br/>", "time": "2022-03-25T10:29:08Z"}, {"author": "Jie Dong", "text": "Sue, I will let Shuping contact you<br/>", "time": "2022-03-25T10:29:45Z"}, {"author": "Jeffrey Haas", "text": "We appear to have another step toward turning bgp into rsvp.<br/>", "time": "2022-03-25T10:33:29Z"}, {"author": "Ketan Talaulikar", "text": "This can be done today at the underlay. Why push this into the overlay?<br/>", "time": "2022-03-25T10:35:10Z"}, {"author": "Srihari Sangli", "text": "+1 agree Ketan.<br/>", "time": "2022-03-25T10:35:44Z"}, {"author": "Shunwan Zhuang", "text": "Bye\uff01<br/>", "time": "2022-03-25T10:40:32Z"}, {"author": "Boris Khasanov", "text": "thanks everyone!<br/>", "time": "2022-03-25T10:40:42Z"}, {"author": "Keyur Patel", "text": "See you all<br/>", "time": "2022-03-25T10:40:44Z"}, {"author": "Jie Dong", "text": "thanks everyone<br/>", "time": "2022-03-25T10:40:51Z"}, {"author": "Dhruv Dhody", "text": "bye<br/>", "time": "2022-03-25T10:40:57Z"}, {"author": "Keyur Patel", "text": "thanks :)<br/>", "time": "2022-03-25T10:41:02Z"}]