[{"author": "Tony Li", "text": "

That was actually over-driving your mic

", "time": "2023-03-27T06:30:09Z"}, {"author": "Adam Wiethuechter", "text": "


", "time": "2023-03-27T06:30:20Z"}, {"author": "Scott Johnson", "text": "

Square waves!

", "time": "2023-03-27T06:30:26Z"}, {"author": "Jorge Amodio", "text": "

Something is going on with meteacho I heard several remote presentations where audio was saturating

", "time": "2023-03-27T06:30:46Z"}, {"author": "Jorge Amodio", "text": "

put it in slideshow mode Ed

", "time": "2023-03-27T06:35:17Z"}, {"author": "Jorge Amodio", "text": "


", "time": "2023-03-27T06:37:19Z"}, {"author": "Mohamed Boucadair", "text": "

I like your \"be afraid\" @Tony

", "time": "2023-03-27T06:38:14Z"}, {"author": "Mohamed Boucadair", "text": "

This reminds me RFC 6115

", "time": "2023-03-27T06:38:26Z"}, {"author": "Jorge Amodio", "text": "

We should

", "time": "2023-03-27T06:42:52Z"}, {"author": "Jorge Amodio", "text": "

I'm in

", "time": "2023-03-27T06:44:17Z"}, {"author": "Jorge Amodio", "text": "

Is this model freely available to use ?

", "time": "2023-03-27T06:52:43Z"}, {"author": "Emery Annis", "text": "

Feel free to read here: https://aixm.aero/sites/aixm.aero/files/imce/AIXM51/aixm_temporality_1.0.pdf

", "time": "2023-03-27T07:00:45Z"}, {"author": "Jorge Amodio", "text": "

Thanks EA

", "time": "2023-03-27T07:05:28Z"}, {"author": "Alvaro Retana", "text": "

The free availability may be different from the ability to use the model as the base for other work, even if partially. If the WG decides to use this work as a reference, we should make sure that any copyright, licensing, etc. lets us do it.

", "time": "2023-03-27T07:05:59Z"}, {"author": "Jorge Amodio", "text": "

Agreed particularly coming from government agencies

", "time": "2023-03-27T07:06:39Z"}, {"author": "Marc Blanchet", "text": "

agree with Alvaro.

", "time": "2023-03-27T07:06:41Z"}, {"author": "Marc Blanchet", "text": "

I read the AIXM model document. it appears to me a bit overwhelming.

", "time": "2023-03-27T07:07:31Z"}, {"author": "Lou Berger", "text": "

While interesting and, I'm sure, full of good idea, seems like covering many topics beyond TVR charter and IETF scope.

", "time": "2023-03-27T07:10:45Z"}, {"author": "Emery Annis", "text": "

Also agree with respect to availability to use (free to read, citing and leveraging for IETF may be beyond scope, needs further research)

", "time": "2023-03-27T07:11:09Z"}, {"author": "Jorge Amodio", "text": "

Add to the complexity that some links are not bidirectional and/or symetric

", "time": "2023-03-27T07:11:46Z"}, {"author": "Edward Birrane", "text": "

Whether deep space spacecraft or airplane runway access, inspection of operational critical systems to identify overlaps feels useful.

", "time": "2023-03-27T07:14:31Z"}, {"author": "Emery Annis", "text": "

With regards to that model, remember it is simply a structure, for which we can agree to terms that describe the schedule. (start/stop times, baseline/permanent delta/temporary delta, parameter state, etc.) The AIXM, while it gives examples for how one may use it, does not define the information that you must contain in the model. Features/Parameters can be specific to TVR. The specific features/parameters, would belong in a data model, such as \"nodeTypeAaaBbbDatamodel\", \"contactDatamodel\", etc.

", "time": "2023-03-27T07:14:39Z"}, {"author": "Emery Annis", "text": "

The rules for conflict resolution, also seem quite useful. Agreeing early what a sequenceNumber or correctionNumber are in this information model, allow users creating a data model to apply it equally.

", "time": "2023-03-27T07:17:57Z"}, {"author": "Emery Annis", "text": "

All said, send some comments out to mailing list. Brian Sipos has used this more than I, and may have further useful comments. Thanks for feedback!

", "time": "2023-03-27T07:18:35Z"}, {"author": "Scott Johnson", "text": "

Thanks Scott.

", "time": "2023-03-27T07:26:12Z"}, {"author": "Edward Birrane", "text": "

A very good overview of this concept

", "time": "2023-03-27T07:27:17Z"}, {"author": "Lou Berger", "text": "

layer4 not layer 3, right?

", "time": "2023-03-27T07:27:46Z"}, {"author": "Scott Johnson", "text": "

BP can, but does not have to, use IP.

", "time": "2023-03-27T07:28:54Z"}, {"author": "Erik Kline", "text": "

I'm not sure this is gonna fly for IP (store-and-forward). It might be better to focus energy on BP. There's not clear indication in IP about what the payload expects in terms of coping with timeliness (or the lack thereof)

", "time": "2023-03-27T07:33:20Z"}, {"author": "Tony Li", "text": "

IP is best effort.

", "time": "2023-03-27T07:33:59Z"}, {"author": "Nigel Hickson", "text": "

Thanks for session

", "time": "2023-03-27T07:34:34Z"}, {"author": "Joel Halpern", "text": "

I guess this \"forwarding\" presentation falls into the \"use case\" category, even if the forwarding poliy work itself is out of scope for TVR.

", "time": "2023-03-27T07:35:11Z"}, {"author": "Scott Johnson", "text": "

isn't this equivalent to the difference between configuring a cisco vs configuring the bird for bgp operation?

", "time": "2023-03-27T07:38:28Z"}, {"author": "Jorge Amodio", "text": "

bird+bgp == ugly

", "time": "2023-03-27T07:38:55Z"}, {"author": "Jorge Amodio", "text": "

add rpki and double ugly

", "time": "2023-03-27T07:40:01Z"}, {"author": "Scott Johnson", "text": "

bird works well for me, but the point being different vendors have different configuration syntaxes.

", "time": "2023-03-27T07:40:50Z"}, {"author": "Tony Li", "text": "

Thus, YANG

", "time": "2023-03-27T07:42:46Z"}, {"author": "Jorge Amodio", "text": "

ALTO ? isn't it for traffic optimization ? we are trying to deal with situations where there is no traffic

", "time": "2023-03-27T07:46:12Z"}, {"author": "Jorge Amodio", "text": "

Sounds more like useful for configure management not \"routing\"

", "time": "2023-03-27T07:48:02Z"}, {"author": "Edward Birrane", "text": "

What about non-space use cases to optimize power or transmission cost?

", "time": "2023-03-27T07:48:11Z"}, {"author": "Y. Richard Yang", "text": "

If no traffic, why need to worry about routing/networking :-( Generally, ALTO is for (time-varying) network information exposure to applications.

", "time": "2023-03-27T07:49:20Z"}, {"author": "Jorge Amodio", "text": "

I can't see a match

", "time": "2023-03-27T07:50:45Z"}, {"author": "Marc Blanchet", "text": "

Scott B presentation was really interesting: to the point, informative.

", "time": "2023-03-27T07:51:47Z"}, {"author": "Jorge Amodio", "text": "

Agreed, great to know where we came from and what is needed to keep going

", "time": "2023-03-27T07:52:18Z"}, {"author": "Jorge Amodio", "text": "

Great plan Ed

", "time": "2023-03-27T07:53:13Z"}, {"author": "Jorge Amodio", "text": "

Well a terrestrial application using a satellite link is a good case :-)

", "time": "2023-03-27T07:55:11Z"}, {"author": "Jorge Amodio", "text": "


", "time": "2023-03-27T07:55:42Z"}, {"author": "Jorge Amodio", "text": "

Agreed we need to review and refine the use cases

", "time": "2023-03-27T07:57:04Z"}, {"author": "Jorge Amodio", "text": "

Great meeting

", "time": "2023-03-27T07:57:27Z"}, {"author": "Scott Johnson", "text": "

each radio gets a node number, Ed, just like every network interfaces gets an IP address.

", "time": "2023-03-27T07:57:36Z"}, {"author": "Scott Johnson", "text": "


", "time": "2023-03-27T07:57:58Z"}, {"author": "Jorge Amodio", "text": "

radio != interface or end point

", "time": "2023-03-27T07:57:59Z"}, {"author": "Rick Taylor", "text": "

Thanks all!

", "time": "2023-03-27T07:58:16Z"}, {"author": "Scott Johnson", "text": "

indeed, great session.

", "time": "2023-03-27T07:58:35Z"}, {"author": "Scott Burleigh", "text": "


", "time": "2023-03-27T07:58:40Z"}, {"author": "Jorge Amodio", "text": "

going back to sleep :smiling_face:

", "time": "2023-03-27T07:58:56Z"}]