[{"author": "Meetecho", "text": "Yes, that may have been what happened. Thanks for the feedback!<br/>", "time": "2022-03-23T12:00:19Z"}, {"author": "John Scudder", "text": "one other administrivia point I don't think lou said -- when making a comment, please state your name (even though it does get displayed in the meetecho queue as well)<br/>", "time": "2022-03-23T12:03:46Z"}, {"author": "~~dhruv~~dhody~~", "text": "<a href=\"https://www.ietf.org/about/liaisons/\" rel=\"nofollow\">https://www.ietf.org/about/liaisons/</a> is missing ETSI<br/>", "time": "2022-03-23T12:06:11Z"}, {"author": "John Scudder", "text": "Thanks Dhruv and Robin. As Lou says this is just comms, seems harmless, but maybe we should be proactive in seeing if there's need to set up something more formal.<br/>", "time": "2022-03-23T12:07:17Z"}, {"author": "Adrian Farrel", "text": "<a href=\"https://www.ietf.org/about/liaisons/\" rel=\"nofollow\">https://www.ietf.org/about/liaisons/</a> does not list ETSI as Robin says<br/>", "time": "2022-03-23T12:08:16Z"}, {"author": "Lou Berger", "text": "okay, my mistake then<br/>", "time": "2022-03-23T12:08:31Z"}, {"author": "Zhenbin Li", "text": "I have taken the work to try to setup the liaison with ETSI. But in the IAB, the setup of liaison with ETSI is not accepted. So happen to be familiar with it.<br/>", "time": "2022-03-23T12:09:33Z"}, {"author": "Jeff Tantsura", "text": "Robin, and I brought this with IAB before you got on it, with a similar outcome<br/>", "time": "2022-03-23T12:10:21Z"}, {"author": "Adrian Farrel", "text": "With this liaison, it looks like email works fine<br/>", "time": "2022-03-23T12:10:30Z"}, {"author": "John Scudder", "text": "@meetecho, I'm not sure if there's any improvement possible, but remote speakers are getting echo from the room<br/>", "time": "2022-03-23T12:10:33Z"}, {"author": "Meetecho", "text": "John: checking<br/>", "time": "2022-03-23T12:10:49Z"}, {"author": "Lou Berger", "text": "@meetecho it seems to have gotten worse just recently<br/>", "time": "2022-03-23T12:10:52Z"}, {"author": "Adrian Farrel", "text": "My mute button disappeared<br/>", "time": "2022-03-23T12:28:36Z"}, {"author": "Daniel King", "text": "Lou, you might want to come back to Adrian. He will be restarting his mobile connection.<br/>", "time": "2022-03-23T12:28:51Z"}, {"author": "Christian Hopps", "text": "bad mute button, bad.<br/>", "time": "2022-03-23T12:28:57Z"}, {"author": "Daniel King", "text": "Oh, he's alive.<br/>", "time": "2022-03-23T12:28:58Z"}, {"author": "Daniel King", "text": "Use video, and interpretive dance.<br/>", "time": "2022-03-23T12:29:29Z"}, {"author": "Adrian Farrel", "text": "Bug<br/>", "time": "2022-03-23T12:29:36Z"}, {"author": "Adrian Farrel", "text": "Leaving and rejoining<br/>", "time": "2022-03-23T12:29:42Z"}, {"author": "Joel Halpern", "text": "Ahh.&nbsp;&nbsp;I had a SPRING document run into that date bug.&nbsp;&nbsp;We manually approved it.&nbsp;&nbsp;Had not realized it was tied to the exact number of authors.<br/>", "time": "2022-03-23T12:32:21Z"}, {"author": "~~dhruv~~dhody~~", "text": "One way to solve the issue with page full of authors on the front page :)<br/>", "time": "2022-03-23T12:33:01Z"}, {"author": "Lou Berger", "text": "se <a href=\"https://notes.ietf.org/notes-ietf-113-teas?edit\" rel=\"nofollow\">https://notes.ietf.org/notes-ietf-113-teas?edit</a><br/>", "time": "2022-03-23T12:34:38Z"}, {"author": "Italo Busi", "text": "I have done the same as Joel (manual submission)<br/>", "time": "2022-03-23T12:34:57Z"}, {"author": "Deborah Brungard", "text": "On the liaison, multiple aspects, formal agreement between SDOs of relationship/appointing of liaisons and posting on page. Formal liaisons are two way, forget on this one but the handshake was not successful, not just IAB. I\u2019ll check, I think can still post to the page as see others from ETSI.<br/>", "time": "2022-03-23T12:35:43Z"}, {"author": "Daniel King", "text": "I can hear Daniele<br/>", "time": "2022-03-23T12:37:46Z"}, {"author": "~~dhruv~~dhody~~", "text": "Remote is okay<br/>", "time": "2022-03-23T12:37:48Z"}, {"author": "Daniele Ceccarelli", "text": "i'll make my comment and type again for you hera<br/>", "time": "2022-03-23T12:38:33Z"}, {"author": "John Scudder", "text": "@adrian, it's a bit of a \"have you turned it on\" suggestion but... is your local volume turned to zero by any chance? <br/>", "time": "2022-03-23T12:39:07Z"}, {"author": "Luay Jalil", "text": "@Adrian agree with your points on your \"Recent Discussions\" slide<br/>", "time": "2022-03-23T12:39:42Z"}, {"author": "Christian Hopps", "text": "big echo now<br/>", "time": "2022-03-23T12:40:09Z"}, {"author": "John Scudder", "text": "I wonder if the echo is coming back from daniele.<br/>", "time": "2022-03-23T12:40:27Z"}, {"author": "John Scudder", "text": "Seems like it, went away when he muted.<br/>", "time": "2022-03-23T12:40:34Z"}, {"author": "Christian Hopps", "text": "yeah<br/>", "time": "2022-03-23T12:40:37Z"}, {"author": "Daniele Ceccarelli", "text": "ok, will switch to headset (sorry about that)<br/>", "time": "2022-03-23T12:40:48Z"}, {"author": "John Scudder", "text": "Lou just sent an XON to Adrian I guess.<br/>", "time": "2022-03-23T12:41:10Z"}, {"author": "Christian Hopps", "text": "heh<br/>", "time": "2022-03-23T12:41:24Z"}, {"author": "Lou Berger", "text": "heh - audio only stream -- <a href=\"https://mp3.conf.meetecho.com/ietf113/teas/2.m3u\" rel=\"nofollow\">https://mp3.conf.meetecho.com/ietf113/teas/2.m3u</a><br/>", "time": "2022-03-23T12:41:26Z"}, {"author": "Daniele Ceccarelli", "text": "@adrian: the summary in a nutshell is that we're happy with the answers received so far. The major questions are the ones you already replied to.<br/>", "time": "2022-03-23T12:41:38Z"}, {"author": "Christian Hopps", "text": "CTS?<br/>", "time": "2022-03-23T12:41:41Z"}, {"author": "Christian Hopps", "text": "The wired version was always better :)<br/>", "time": "2022-03-23T12:41:54Z"}, {"author": "Kireeti Kompella", "text": "to Adrian's point, communication in this session is the weirdest I've seen<br/>", "time": "2022-03-23T12:43:31Z"}, {"author": "Christian Hopps", "text": "@meetecho in room, we cannot hear that mic<br/>", "time": "2022-03-23T12:44:26Z"}, {"author": "John Scudder", "text": "@meetecho, gain on in-room mic (in middle of room) seems really low<br/>", "time": "2022-03-23T12:44:30Z"}, {"author": "Christian Hopps", "text": "it sounds like a buzzing insect to me<br/>", "time": "2022-03-23T12:44:46Z"}, {"author": "Meetecho", "text": "Checking, maybe mic running out of juice?<br/>", "time": "2022-03-23T12:45:11Z"}, {"author": "Meetecho", "text": "Was it ok for remote participants instead?<br/>", "time": "2022-03-23T12:45:19Z"}, {"author": "Luay Jalil", "text": "@adrian I can help with examples if needed but I'm of the other opinion to keep examples out of this draft<br/>", "time": "2022-03-23T12:45:20Z"}, {"author": "Christian Hopps", "text": "remote people cannot hear the in room mic<br/>", "time": "2022-03-23T12:45:37Z"}, {"author": "Boris Khasanov", "text": "+1 Kireeti , very wierd sound&nbsp;&nbsp;by some reasons.<br/>", "time": "2022-03-23T12:45:47Z"}, {"author": "Meetecho", "text": "Notified the AV team about the mic<br/>", "time": "2022-03-23T12:47:20Z"}, {"author": "Christian Hopps", "text": "in room mic is improving<br/>", "time": "2022-03-23T12:48:51Z"}, {"author": "~~dhruv~~dhody~~", "text": "@wim - For details about realisation, draft-contreras-teas-slice-controller-models could be a good place<br/>", "time": "2022-03-23T12:50:50Z"}, {"author": "Jie Dong", "text": "some examples might be helpful for understanding the applicability of IETF network slice, while my preference is also to keep it separate from the general framework document<br/>", "time": "2022-03-23T12:51:29Z"}, {"author": "Jie Dong", "text": "regarding the realization of IETF network slices, draft-ietf-teas-enhanced-vpn describes a layered architecture and the candidate technologies<br/>", "time": "2022-03-23T12:53:08Z"}, {"author": "Joel Halpern", "text": "@Jie Dong - presumably the enhanced VPN document describes \"a\" candidate technology, not \"the\" candidate technology?<br/>", "time": "2022-03-23T12:54:14Z"}, {"author": "Adrian Farrel", "text": "@joel. I think it is \"some of the candidate technologies\"<br/>", "time": "2022-03-23T12:55:16Z"}, {"author": "Jie Dong", "text": "@Joel thanks for correction, it describes a set of candidate technologies<br/>", "time": "2022-03-23T12:55:30Z"}, {"author": "Joel Halpern", "text": "@Jie Dong - thank you.&nbsp;&nbsp;<br/>", "time": "2022-03-23T12:56:24Z"}, {"author": "Gyan Mishra", "text": "@Adrian - Agreed<br/>", "time": "2022-03-23T13:00:04Z"}, {"author": "Italo Busi", "text": "I agree with Kireti<br/>", "time": "2022-03-23T13:00:50Z"}, {"author": "~~dhruv~~dhody~~", "text": "ns-tag is similar if i can recall it correctly<br/>", "time": "2022-03-23T13:01:08Z"}, {"author": "~~dhruv~~dhody~~", "text": "@kireeti - we have SLO/SLE at the slice level and it could be over ridden at the group/construct level as well<br/>", "time": "2022-03-23T13:03:39Z"}, {"author": "Joel Halpern", "text": "I would think that the SLO requirement is in terms of recovery time, not mechanism.&nbsp;&nbsp;Protected LSP is a mechanism.<br/>", "time": "2022-03-23T13:04:44Z"}, {"author": "Italo Busi", "text": "I agree with Joel<br/>", "time": "2022-03-23T13:05:20Z"}, {"author": "Adrian Farrel", "text": "Yes, \"protection\" is an SLE, but \"minimum down time\" is an SLO<br/>", "time": "2022-03-23T13:05:26Z"}, {"author": "Luis Contreras", "text": "+1<br/>", "time": "2022-03-23T13:05:30Z"}, {"author": "Kireeti Kompella", "text": "I buy that<br/>", "time": "2022-03-23T13:05:56Z"}, {"author": "Joel Halpern", "text": "I don't see any point in a \"protection\" SLE.<br/>", "time": "2022-03-23T13:06:38Z"}, {"author": "Vishnu Beeram", "text": "For note taking: <a href=\"https://notes.ietf.org/notes-ietf-113-teas?both\" rel=\"nofollow\">https://notes.ietf.org/notes-ietf-113-teas?both</a><br/>", "time": "2022-03-23T13:19:03Z"}, {"author": "Tony Li", "text": "It sounded like it was clipping even at moderate volume.<br/>", "time": "2022-03-23T13:21:35Z"}, {"author": "Lou Berger", "text": "just that one mic<br/>", "time": "2022-03-23T13:25:37Z"}, {"author": "Christian Hopps", "text": "well.. the entire IETF experience for me has had clipping on the input seemingly <br/>", "time": "2022-03-23T13:26:13Z"}, {"author": "Christian Hopps", "text": "lots of pops and cracks<br/>", "time": "2022-03-23T13:26:24Z"}, {"author": "~~dhruv~~dhody~~", "text": "You need to set Luis as delegate in datatracker<br/>", "time": "2022-03-23T13:28:52Z"}, {"author": "~~dhruv~~dhody~~", "text": "for him to have chair control in meetecho<br/>", "time": "2022-03-23T13:29:06Z"}, {"author": "Lou Berger", "text": "even though he's secretary?<br/>", "time": "2022-03-23T13:29:51Z"}, {"author": "~~dhruv~~dhody~~", "text": "yup! they were not sure who is going to be on the ground i guess<br/>", "time": "2022-03-23T13:30:11Z"}, {"author": "Lou Berger", "text": "sigh, love the shifting sands<br/>", "time": "2022-03-23T13:31:33Z"}, {"author": "~~dhruv~~dhody~~", "text": "Basically diff will be moved to appendix and the full model to the main body? <br/>", "time": "2022-03-23T13:37:00Z"}, {"author": "~~dhruv~~dhody~~", "text": "so update and the above change! Sounds good to me! <br/>", "time": "2022-03-23T13:38:58Z"}, {"author": "Lou Berger", "text": "diff as narrative text<br/>", "time": "2022-03-23T13:39:19Z"}, {"author": "Lou Berger", "text": "wherever makes sense<br/>", "time": "2022-03-23T13:39:33Z"}, {"author": "Italo Busi", "text": "Yes, the narrative text is already focused on the diffs<br/>", "time": "2022-03-23T13:40:00Z"}, {"author": "Lou Berger", "text": "perfect!<br/>", "time": "2022-03-23T13:40:20Z"}, {"author": "Italo Busi", "text": "my understanding is that we need to move the YANG module revision from the appendix to the main body<br/>", "time": "2022-03-23T13:40:22Z"}, {"author": "Lou Berger", "text": "yes<br/>", "time": "2022-03-23T13:43:22Z"}, {"author": "Joel Halpern", "text": "I am a bit confused about the section from the presenter where he said he was discussing mpt-tp-pt.&nbsp;&nbsp;That is not in the framework.&nbsp;&nbsp;I don't think it is something we want at this level.&nbsp;&nbsp;And it is not in the I-D I can find.<br/>", "time": "2022-03-23T13:50:31Z"}, {"author": "Bo Wu", "text": "This model has YANG namespace conflict. It is suggested using another namespace.<br/>", "time": "2022-03-23T13:55:33Z"}, {"author": "Bo Wu", "text": "Current WG network slice service model use ietf-network-slice namespace<br/>", "time": "2022-03-23T13:56:23Z"}, {"author": "~~dhruv~~dhody~~", "text": "Timer needs a reset :)<br/>", "time": "2022-03-23T14:09:31Z"}, {"author": "Luis Contreras", "text": "Reegarding Dhruv's question on possible feedback the use cases could provide to framework -&gt; on the use cases documented, some of them require the possibility of reserving resources. So IETF Network Slice reservation could be a potential input to be documented on framework document as a capability expected for the IETF NSC (sorry I couldn't remember it at the time of speaking)<br/>", "time": "2022-03-23T14:10:24Z"}, {"author": "~~dhruv~~dhody~~", "text": "Do you mean some sort of calendaring capability to schedule it?<br/>", "time": "2022-03-23T14:14:10Z"}, {"author": "Luis Contreras", "text": "Correct, that's I'm referring to<br/>", "time": "2022-03-23T14:14:31Z"}, {"author": "Kiran Makhijani", "text": "@Dhruv: I understand 'resource reservation' but how did you arrive at calendering from there? - you are asking to selectively reserve resources for certain time periods with in the lifetime of a slice. is it?<br/>", "time": "2022-03-23T14:21:10Z"}, {"author": "Luis Contreras", "text": "Hi Kiran, teh idea would be to defer activation of the slice from the booking of resources for that slice<br/>", "time": "2022-03-23T14:21:52Z"}, {"author": "~~dhruv~~dhody~~", "text": "since Luis said it is a gap and we know the resource reservation is already supported, it was a wild guess<br/>", "time": "2022-03-23T14:22:16Z"}, {"author": "Luis Contreras", "text": "My fault, probably I didn't express the point correctly during the presentation<br/>", "time": "2022-03-23T14:23:12Z"}, {"author": "Adrian Farrel", "text": "Adrian not being able to talk is often considered a good outcome<br/>", "time": "2022-03-23T14:25:54Z"}, {"author": "Tarek Saad", "text": "mic issue<br/>", "time": "2022-03-23T14:37:05Z"}, {"author": "Tarek Saad", "text": "I refreshed my webpage - hoping it will work on attempt 2<br/>", "time": "2022-03-23T14:38:13Z"}, {"author": "Lou Berger", "text": "we'll retry<br/>", "time": "2022-03-23T14:38:29Z"}, {"author": "Steven Hartley", "text": "Could you speak up?<br/>", "time": "2022-03-23T14:43:26Z"}, {"author": "Christian Hopps", "text": "or have the mix turned up from all these local mics<br/>", "time": "2022-03-23T14:43:46Z"}, {"author": "Christian Hopps", "text": "they seems to be consistently too quiet <br/>", "time": "2022-03-23T14:43:58Z"}, {"author": "Gyan Mishra", "text": "its very low<br/>", "time": "2022-03-23T14:44:11Z"}, {"author": "Lou Berger", "text": "try the slider bar at the lower right of your screen<br/>", "time": "2022-03-23T14:44:33Z"}, {"author": "Christian Hopps", "text": "We need the AV people to log in to the session remotely in a pair of headseats and then mix the levels that way :)<br/>", "time": "2022-03-23T14:44:43Z"}, {"author": "Christian Hopps", "text": "headsets..<br/>", "time": "2022-03-23T14:45:21Z"}, {"author": "Lou Berger", "text": "or some good AGC<br/>", "time": "2022-03-23T14:45:26Z"}, {"author": "Gyan Mishra", "text": "yep<br/>", "time": "2022-03-23T14:45:49Z"}, {"author": "Christian Hopps", "text": "I think it's a mix problem not a gain<br/>", "time": "2022-03-23T14:45:56Z"}, {"author": "Christian Hopps", "text": "&lt;- not an AV guy, I mean it's all gain I guess. <br/>", "time": "2022-03-23T14:48:36Z"}, {"author": "~~dhruv~~dhody~~", "text": "@Luis - maybe you could also add reference to the IETF Network Slice Service Mapping to TE in your list of YANG models -&nbsp;&nbsp;<a href=\"https://datatracker.ietf.org/doc/draft-dhody-teas-ietf-network-slice-mapping/\" rel=\"nofollow\">https://datatracker.ietf.org/doc/draft-dhody-teas-ietf-network-slice-mapping/</a><br/>", "time": "2022-03-23T14:55:14Z"}, {"author": "Christian Hopps", "text": "nice ascii art!<br/>", "time": "2022-03-23T15:00:14Z"}, {"author": "Eduard V", "text": "mic is overloaded<br/>", "time": "2022-03-23T15:03:15Z"}, {"author": "John Scudder", "text": "I presume the audio is a hot mess for everyone<br/>", "time": "2022-03-23T15:03:18Z"}, {"author": "Boris Khasanov", "text": "yes, indeed<br/>", "time": "2022-03-23T15:03:27Z"}, {"author": "Xuesong Geng", "text": "I will take the question to the list<br/>", "time": "2022-03-23T15:03:35Z"}, {"author": "Gyan Mishra", "text": "I don't see all the slide decks presented today uploaded to the teas agenda page.<br/>", "time": "2022-03-23T15:07:12Z"}, {"author": "~~dhruv~~dhody~~", "text": "they are, scroll down to session 2<br/>", "time": "2022-03-23T15:07:34Z"}, {"author": "Eduard V", "text": "I have downloaded all before the session<br/>", "time": "2022-03-23T15:07:38Z"}, {"author": "Luis Contreras", "text": "Gyan, note we had two slots, si check the proper slot<br/>", "time": "2022-03-23T15:07:43Z"}, {"author": "Gyan Mishra", "text": "I see them all now thank you<br/>", "time": "2022-03-23T15:08:28Z"}, {"author": "Lou Berger", "text": "I still want a button to download all WG slides in a single pdf....<br/>", "time": "2022-03-23T15:09:16Z"}, {"author": "Eduard V", "text": "+1<br/>", "time": "2022-03-23T15:09:46Z"}, {"author": "Vishnu Beeram", "text": "+1 to the button request<br/>", "time": "2022-03-23T15:09:52Z"}, {"author": "~~dhruv~~dhody~~", "text": "Yup, i prepare consolidate slides offline<br/>", "time": "2022-03-23T15:09:53Z"}, {"author": "Christian Hopps", "text": "yeah there's a button for downloading all the drafts into a single PDF, but not slides. I'd rather have the slides than the docs<br/>", "time": "2022-03-23T15:11:34Z"}, {"author": "Kiran Makhijani", "text": "@Robin: I liked your slide #3 a lot. it would be even better to plug in corresponding Yang models and will have the work-in-progress document-map. :-)<br/>", "time": "2022-03-23T15:15:47Z"}, {"author": "~~dhruv~~dhody~~", "text": "Raised a ticket - <a href=\"https://github.com/ietf-tools/datatracker/discussions/3735\" rel=\"nofollow\">https://github.com/ietf-tools/datatracker/discussions/3735</a><br/>", "time": "2022-03-23T15:16:58Z"}, {"author": "Lou Berger", "text": "thank you!!!<br/>", "time": "2022-03-23T15:17:06Z"}, {"author": "~~dhruv~~dhody~~", "text": "@Jie - are we thinking only 2 levels of hierarchy in case of option 2?<br/>", "time": "2022-03-23T15:18:35Z"}, {"author": "~~dhruv~~dhody~~", "text": "Thanks for a great session! <br/>", "time": "2022-03-23T15:27:51Z"}, {"author": "Italo Busi", "text": "thanks and bye bye<br/>", "time": "2022-03-23T15:28:18Z"}, {"author": "Jie Dong", "text": "@dhruv, 2 levels is considered as a starting point, would like to know if we need more levels<br/>", "time": "2022-03-23T15:28:40Z"}]