[{"author": "Mohamed Boucadair", "text": "These online meeting are not virtual interims, but an informal venue to discuss<br/>", "time": "2022-03-23T09:04:54Z"}, {"author": "Mohamed Boucadair", "text": "The WG hosts the webex for these meeting<br/>", "time": "2022-03-23T09:05:22Z"}, {"author": "Mohamed Boucadair", "text": "details will be included in the minutes<br/>", "time": "2022-03-23T09:05:30Z"}, {"author": "Y. Richard Yang", "text": "All are welcome to attend the weekly informal meeting.<br/>", "time": "2022-03-23T09:05:58Z"}, {"author": "Mohamed Boucadair", "text": "To volunteer to help building a tutorial, just drop an email to the chairs and we will see how to organize ourselves<br/>", "time": "2022-03-23T09:10:07Z"}, {"author": "Y. Richard Yang", "text": "Some of us (Jordi, I) have ALTO tutorials that we presented recently. A more formal tutorial is a great idea, and we will be happy to work with chairs.<br/>", "time": "2022-03-23T09:10:31Z"}, {"author": "Mohamed Boucadair", "text": "Great.<br/>", "time": "2022-03-23T09:11:11Z"}, {"author": "Mohamed Boucadair", "text": "making them easily available is also something we are looking for<br/>", "time": "2022-03-23T09:11:46Z"}, {"author": "Y. Richard Yang", "text": "Good idea. Hosting at: <a href=\"https://github.com/ietf-wg-alto?\" rel=\"nofollow\">https://github.com/ietf-wg-alto?</a><br/>", "time": "2022-03-23T09:12:44Z"}, {"author": "Qin Wu", "text": "yes<br/>", "time": "2022-03-23T09:13:20Z"}, {"author": "Y. Richard Yang", "text": "What are the complexities when decompose?<br/>", "time": "2022-03-23T09:25:10Z"}, {"author": "~~dhruv~~dhody~~", "text": "I dont see it as complexity, but just that we want to do the right thing<br/>", "time": "2022-03-23T09:26:01Z"}, {"author": "Y. Richard Yang", "text": "You mentioned that there could be complexity.<br/>", "time": "2022-03-23T09:26:19Z"}, {"author": "Mohamed Boucadair", "text": "The main advantage of relying upon an IANA registry is that new values are supported for free without having to define an augment /etc.<br/>", "time": "2022-03-23T09:27:10Z"}, {"author": "~~dhruv~~dhody~~", "text": "agreed to that<br/>", "time": "2022-03-23T09:27:41Z"}, {"author": "Mohamed Boucadair", "text": "Otherwise, each time a new metric is supported you need to define a new identity for it<br/>", "time": "2022-03-23T09:27:43Z"}, {"author": "Mohamed Boucadair", "text": "We don't need that as the IANA-maintained module will be generated each time a new value is assigned<br/>", "time": "2022-03-23T09:28:25Z"}, {"author": "~~dhruv~~dhody~~", "text": "I was hoping for a best practice that could be laid out for this instead of each YANG author to figure it out and then no consistency between models<br/>", "time": "2022-03-23T09:30:30Z"}, {"author": "Kai Gao", "text": "Is the IANA approach the one specified in RFC 7224?<br/>", "time": "2022-03-23T09:33:01Z"}, {"author": "Y. Richard Yang", "text": "OAM for client is an issue indeed. For example, it was the issue for configuring Rucio.<br/>", "time": "2022-03-23T09:33:03Z"}, {"author": "Mohamed Boucadair", "text": "We may consider proposing an update to the guidelines.<br/>", "time": "2022-03-23T09:33:03Z"}, {"author": "~~dhruv~~dhody~~", "text": "Thanks Martin! Good suggestion! <br/>", "time": "2022-03-23T09:34:38Z"}, {"author": "~~dhruv~~dhody~~", "text": "Does ALTO Clients device would use YANG based OAM techniques? <br/>", "time": "2022-03-23T09:35:37Z"}, {"author": "Y. Richard Yang", "text": "Good idea, Dhruv.<br/>", "time": "2022-03-23T09:37:24Z"}, {"author": "Mohamed Boucadair", "text": "Dhruv, yang is transport-independent<br/>", "time": "2022-03-23T09:37:41Z"}, {"author": "Mohamed Boucadair", "text": "A data model will allow for consistent configuration/management features<br/>", "time": "2022-03-23T09:38:11Z"}, {"author": "Mohamed Boucadair", "text": "independently of which \"channel\" is used to touch that part<br/>", "time": "2022-03-23T09:38:27Z"}, {"author": "Mohamed Boucadair", "text": "Agree with Dhruv<br/>", "time": "2022-03-23T09:39:06Z"}, {"author": "Kai Gao", "text": "I feel many clients are configured by .in I or .y'all. I personally only used YANG for configuration in Opendaylight, which is unlikely to become an application platform.<br/>", "time": "2022-03-23T09:39:13Z"}, {"author": "Kai Gao", "text": "Sorry referring to .ini and .yml. Got auto corrected:worried:<br/>", "time": "2022-03-23T09:40:53Z"}, {"author": "~~dhruv~~dhody~~", "text": "Thanks Qin! <br/>", "time": "2022-03-23T09:41:20Z"}, {"author": "Qin Wu", "text": "for alto new transport in page 25,is there any out of order delivery issue for streaming management?<br/>", "time": "2022-03-23T09:55:03Z"}, {"author": "Qin Wu", "text": "how reciever set functionality works with other new functionalities introduced?<br/>", "time": "2022-03-23T09:56:28Z"}, {"author": "Mohamed Boucadair", "text": "Thanks, Roland. Can we claim that the design follows recos in draft-ietf-httpbis-bcp56bis?<br/>", "time": "2022-03-23T09:58:54Z"}, {"author": "Y. Richard Yang", "text": "Med: Good question. We have not checked but will. Thanks for the suggestion.<br/>", "time": "2022-03-23T10:05:20Z"}, {"author": "Mohamed Boucadair", "text": "Thanks. Please be aware that the reco in the bcp is to avoid pointing to a specific version unless needed/justified<br/>", "time": "2022-03-23T10:08:33Z"}, {"author": "Mohamed Boucadair", "text": "We will need anyway to request a review/feedback from ARTART<br/>", "time": "2022-03-23T10:09:20Z"}, {"author": "Y. Richard Yang", "text": "Thanks, Med. We will upload a new version with all of the changes and then seed the review/feedback, which is great.<br/>", "time": "2022-03-23T10:14:49Z"}, {"author": "Mohamed Boucadair", "text": "Looks like a good plan<br/>", "time": "2022-03-23T10:15:08Z"}, {"author": "Mohamed Boucadair", "text": "We may need to re-structure that content to extract&nbsp;&nbsp;\"real\" deployments vs. PoCs and the like<br/>", "time": "2022-03-23T10:25:51Z"}, {"author": "Qin Wu", "text": "where to restructure? wiki page or WG github?<br/>", "time": "2022-03-23T10:27:57Z"}, {"author": "Mohamed Boucadair", "text": "The wiki page<br/>", "time": "2022-03-23T10:28:12Z"}, {"author": "Qin Wu", "text": "make sense<br/>", "time": "2022-03-23T10:28:56Z"}, {"author": "Qin Wu", "text": "@Jordi, can alto provide sufficient information to build bottleneck structure graph? is there data translation needed? in the scope of your draft or not?<br/>", "time": "2022-03-23T10:52:14Z"}, {"author": "Y. Richard Yang", "text": "There are two interpretations to this question: (1) build bottleneck structure on top of alto and (2) make bottleneck structure a (new) service provided by alto. For (1), we need some modifications; I think the focus here is (2). Jordi?<br/>", "time": "2022-03-23T10:55:39Z"}, {"author": "Y. Richard Yang", "text": "Personally, I think this will be a super cool new service!<br/>", "time": "2022-03-23T10:57:17Z"}]