Open APIs

I'd like to understand what is the plan of TMF for these two APIs:

Seems that there will be a V 5.0.0 of Resource Pool Management

But I also found some comment in the TMF that mention that Resource Reservation will replace Resource Pool Management API

May you kindly clarify if Resource Pool Management will be deprecated or if we can continue use this API as standard target that will remain in the future? 

May you also clarify the difference within the two APIs and suggest me the best API to be used in case of Number Reservation (E2E scenario where I also need to display the list of available numbers)?

More than that I'd like to notify you that the Resource Reservation Specification link in the OpenAPI table has some problem : Resource Reservation TMF716-v4.0.0

Thanks and regards,

Luca Icardi

Hi Luca

The TMF685 Resource Pool API is being re-modelled as the API was inconsistent with the other Open API design patterns.  It seems that the model has been submitted for review by Pierre.  Perhaps @Lutz Bettge may have a more up-to-date status of the redesign?  In any case, both the TMF685 Resource Pool API and TMF716 Resource Reservation API are still valid.

Sorry I cannot help more.

I'd like to understand what is the plan of TMF for these two APIs:

Seems that there will be a V 5.0.0 of Resource Pool Management

But I also found some comment in the TMF that mention that Resource Reservation will replace Resource Pool Management API

May you kindly clarify if Resource Pool Management will be deprecated or if we can continue use this API as standard target that will remain in the future? 

May you also clarify the difference within the two APIs and suggest me the best API to be used in case of Number Reservation (E2E scenario where I also need to display the list of available numbers)?

More than that I'd like to notify you that the Resource Reservation Specification link in the OpenAPI table has some problem : Resource Reservation TMF716-v4.0.0

Thanks and regards,

Luca Icardi

es, this is correct, the Resource Pool API has just been re-modelled at the Vienna API Spec Jam, and has been submitted for review by Pierre. Resource Reservation is still work in Progress, not clear when it will be completed.

Hi Luca

The TMF685 Resource Pool API is being re-modelled as the API was inconsistent with the other Open API design patterns.  It seems that the model has been submitted for review by Pierre.  Perhaps @Lutz Bettge may have a more up-to-date status of the redesign?  In any case, both the TMF685 Resource Pool API and TMF716 Resource Reservation API are still valid.

Sorry I cannot help more.

I'd like to understand what is the plan of TMF for these two APIs:

Seems that there will be a V 5.0.0 of Resource Pool Management

But I also found some comment in the TMF that mention that Resource Reservation will replace Resource Pool Management API

May you kindly clarify if Resource Pool Management will be deprecated or if we can continue use this API as standard target that will remain in the future? 

May you also clarify the difference within the two APIs and suggest me the best API to be used in case of Number Reservation (E2E scenario where I also need to display the list of available numbers)?

More than that I'd like to notify you that the Resource Reservation Specification link in the OpenAPI table has some problem : Resource Reservation TMF716-v4.0.0

Thanks and regards,

Luca Icardi

Thank you very much for the reply!

May I kindly ask you if you have a draft of the new specification? We could also contribute and help in the creation of the spec 

Thanks and regards,

Luca

es, this is correct, the Resource Pool API has just been re-modelled at the Vienna API Spec Jam, and has been submitted for review by Pierre. Resource Reservation is still work in Progress, not clear when it will be completed.

Hi Luca

The TMF685 Resource Pool API is being re-modelled as the API was inconsistent with the other Open API design patterns.  It seems that the model has been submitted for review by Pierre.  Perhaps @Lutz Bettge may have a more up-to-date status of the redesign?  In any case, both the TMF685 Resource Pool API and TMF716 Resource Reservation API are still valid.

Sorry I cannot help more.

I'd like to understand what is the plan of TMF for these two APIs:

Seems that there will be a V 5.0.0 of Resource Pool Management

But I also found some comment in the TMF that mention that Resource Reservation will replace Resource Pool Management API

May you kindly clarify if Resource Pool Management will be deprecated or if we can continue use this API as standard target that will remain in the future? 

May you also clarify the difference within the two APIs and suggest me the best API to be used in case of Number Reservation (E2E scenario where I also need to display the list of available numbers)?

More than that I'd like to notify you that the Resource Reservation Specification link in the OpenAPI table has some problem : Resource Reservation TMF716-v4.0.0

Thanks and regards,

Luca Icardi