Open APIs

Hi Guys, What is the right API to use when a technician has to send the Mac address to install a service that was previously sent using the 641?


------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

Hi Christopher
First need to consider where the MAC address needs to be persisted.

• If it needs to be stored in Service Inventory (quite likely), TMF638 (Service Inventory Management) would be suitable.
• If it needs (additionally) to be stored in Product Inventory (visible to end-customer perhaps), then also TMF637 (Product Inventory Management) would be used
• If it needs to be updated in the network itself (not sure if there is such a use case), then TMF640 (Service Activation and Configuration)

@Ludovic Robert does this make sense?

Hope it helps​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Original Message:
Sent: Apr 20, 2020 10:34
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Guys, What is the right API to use when a technician has to send the Mac address to install a service that was previously sent using the 641?


------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

Hello,
Additionnally to Jonathan proposal (and not contradictory)
I'm far to be a specialist on this topic but a MAC address is not supposed to be a physical address to a network card or a network access ? If this is the case we could also consider manage it at the resource level (a resource could be physical or logical) as a characteristic. Then we have from Product inventory and Service inventory the capability to retrieve the realizing/supporting resources (and so have a way to navigate to retireve this information).

Hope it helps

Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------

Original Message:
Sent: Apr 21, 2020 00:51
From: Jonathan Goldberg
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Christopher
First need to consider where the MAC address needs to be persisted.

• If it needs to be stored in Service Inventory (quite likely), TMF638 (Service Inventory Management) would be suitable.
• If it needs (additionally) to be stored in Product Inventory (visible to end-customer perhaps), then also TMF637 (Product Inventory Management) would be used
• If it needs to be updated in the network itself (not sure if there is such a use case), then TMF640 (Service Activation and Configuration)

@Ludovic Robert does this make sense?

Hope it helps​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Original Message:
Sent: Apr 20, 2020 10:34
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Guys, What is the right API to use when a technician has to send the Mac address to install a service that was previously sent using the 641?


------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

My 2 cents:
1. MAC is quite useful for many resources (physical and logical) in resource management layer.
2. It is helpful, or even a must, for an applicable link layer (layer 2) entity to include this attribute.
3. Some layer 3 information (such as a layer 3 link) might need it to help carry out CM, FM or PM functions properly. Examples would be link discovery, alarm correlation, link capacity and utilization, etc.
4. Properly model it to support mutiple network  technologies, flexible for different resources (such as single mac for a chassis, port mac list for a card, etc.)

------------------------------
Fazhong (David) Deng
OSSEra
------------------------------

Original Message:
Sent: Apr 21, 2020 02:19
From: Ludovic Robert
Subject: Send MAC-ADDRESS Choosing the Right API

Hello,
Additionnally to Jonathan proposal (and not contradictory)
I'm far to be a specialist on this topic but a MAC address is not supposed to be a physical address to a network card or a network access ? If this is the case we could also consider manage it at the resource level (a resource could be physical or logical) as a characteristic. Then we have from Product inventory and Service inventory the capability to retrieve the realizing/supporting resources (and so have a way to navigate to retireve this information).

Hope it helps

Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Apr 21, 2020 00:51
From: Jonathan Goldberg
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Christopher
First need to consider where the MAC address needs to be persisted.

• If it needs to be stored in Service Inventory (quite likely), TMF638 (Service Inventory Management) would be suitable.
• If it needs (additionally) to be stored in Product Inventory (visible to end-customer perhaps), then also TMF637 (Product Inventory Management) would be used
• If it needs to be updated in the network itself (not sure if there is such a use case), then TMF640 (Service Activation and Configuration)

@Ludovic Robert does this make sense?

Hope it helps​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Original Message:
Sent: Apr 20, 2020 10:34
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Guys, What is the right API to use when a technician has to send the Mac address to install a service that was previously sent using the 641?


------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

I was asking about when you need to go to the network.

So seems like the day of order one can use 641 and when tech is on premises and need to activate the service on the network using the physical resource one can use the 640. Am I correct on my interpretation?

If you agree I can close the thread Jon

------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

Original Message:
Sent: Apr 21, 2020 00:51
From: Jonathan Goldberg
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Christopher
First need to consider where the MAC address needs to be persisted.

• If it needs to be stored in Service Inventory (quite likely), TMF638 (Service Inventory Management) would be suitable.
• If it needs (additionally) to be stored in Product Inventory (visible to end-customer perhaps), then also TMF637 (Product Inventory Management) would be used
• If it needs to be updated in the network itself (not sure if there is such a use case), then TMF640 (Service Activation and Configuration)

@Ludovic Robert does this make sense?

Hope it helps​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Original Message:
Sent: Apr 20, 2020 10:34
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Guys, What is the right API to use when a technician has to send the Mac address to install a service that was previously sent using the 641?


------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

Hello

For me yes it makes sense as API orchestration.
Please note that we split the Activation & Configuration API in 2:

• TMF640 is Service Activation & Configuration
• TMF702 is Resource Activation & Configuration

Hope it helps
Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------

Original Message:
Sent: Apr 22, 2020 08:52
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

I was asking about when you need to go to the network.

So seems like the day of order one can use 641 and when tech is on premises and need to activate the service on the network using the physical resource one can use the 640. Am I correct on my interpretation?

If you agree I can close the thread Jon

------------------------------
Christopher Gonzalez
Intraway Corp

Original Message:
Sent: Apr 21, 2020 00:51
From: Jonathan Goldberg
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Christopher
First need to consider where the MAC address needs to be persisted.

• If it needs to be stored in Service Inventory (quite likely), TMF638 (Service Inventory Management) would be suitable.
• If it needs (additionally) to be stored in Product Inventory (visible to end-customer perhaps), then also TMF637 (Product Inventory Management) would be used
• If it needs to be updated in the network itself (not sure if there is such a use case), then TMF640 (Service Activation and Configuration)

@Ludovic Robert does this make sense?

Hope it helps​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Original Message:
Sent: Apr 20, 2020 10:34
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Guys, What is the right API to use when a technician has to send the Mac address to install a service that was previously sent using the 641?


------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

I'll take a look at 702.

Thanks a lot for the feedback

------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

Original Message:
Sent: Apr 22, 2020 09:17
From: Ludovic Robert
Subject: Send MAC-ADDRESS Choosing the Right API

Hello

For me yes it makes sense as API orchestration.
Please note that we split the Activation & Configuration API in 2:

• TMF640 is Service Activation & Configuration
• TMF702 is Resource Activation & Configuration

Hope it helps
Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Apr 22, 2020 08:52
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

I was asking about when you need to go to the network.

So seems like the day of order one can use 641 and when tech is on premises and need to activate the service on the network using the physical resource one can use the 640. Am I correct on my interpretation?

If you agree I can close the thread Jon

------------------------------
Christopher Gonzalez
Intraway Corp

Original Message:
Sent: Apr 21, 2020 00:51
From: Jonathan Goldberg
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Christopher
First need to consider where the MAC address needs to be persisted.

• If it needs to be stored in Service Inventory (quite likely), TMF638 (Service Inventory Management) would be suitable.
• If it needs (additionally) to be stored in Product Inventory (visible to end-customer perhaps), then also TMF637 (Product Inventory Management) would be used
• If it needs to be updated in the network itself (not sure if there is such a use case), then TMF640 (Service Activation and Configuration)

@Ludovic Robert does this make sense?

Hope it helps​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Original Message:
Sent: Apr 20, 2020 10:34
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Guys, What is the right API to use when a technician has to send the Mac address to install a service that was previously sent using the 641?


------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

Hi Christopher
Glad we were able to help.
702 (Resource Activation) is still work-in-progress, the swagger has been published on the beta API table here , but user guide is not yet published. @Thomas Braun is leading this API so if you have questions ​you might want to reach out to him.

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Original Message:
Sent: Apr 22, 2020 09:27
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

I'll take a look at 702.

Thanks a lot for the feedback

------------------------------
Christopher Gonzalez
Intraway Corp

Original Message:
Sent: Apr 22, 2020 09:17
From: Ludovic Robert
Subject: Send MAC-ADDRESS Choosing the Right API

Hello

For me yes it makes sense as API orchestration.
Please note that we split the Activation & Configuration API in 2:

• TMF640 is Service Activation & Configuration
• TMF702 is Resource Activation & Configuration

Hope it helps
Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Apr 22, 2020 08:52
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

I was asking about when you need to go to the network.

So seems like the day of order one can use 641 and when tech is on premises and need to activate the service on the network using the physical resource one can use the 640. Am I correct on my interpretation?

If you agree I can close the thread Jon

------------------------------
Christopher Gonzalez
Intraway Corp

Original Message:
Sent: Apr 21, 2020 00:51
From: Jonathan Goldberg
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Christopher
First need to consider where the MAC address needs to be persisted.

• If it needs to be stored in Service Inventory (quite likely), TMF638 (Service Inventory Management) would be suitable.
• If it needs (additionally) to be stored in Product Inventory (visible to end-customer perhaps), then also TMF637 (Product Inventory Management) would be used
• If it needs to be updated in the network itself (not sure if there is such a use case), then TMF640 (Service Activation and Configuration)

@Ludovic Robert does this make sense?

Hope it helps​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Original Message:
Sent: Apr 20, 2020 10:34
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Guys, What is the right API to use when a technician has to send the Mac address to install a service that was previously sent using the 641?


------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

Much obliged.

------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

Original Message:
Sent: Apr 23, 2020 00:51
From: Jonathan Goldberg
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Christopher
Glad we were able to help.
702 (Resource Activation) is still work-in-progress, the swagger has been published on the beta API table here , but user guide is not yet published. @Thomas Braun is leading this API so if you have questions ​you might want to reach out to him.

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Original Message:
Sent: Apr 22, 2020 09:27
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

I'll take a look at 702.

Thanks a lot for the feedback

------------------------------
Christopher Gonzalez
Intraway Corp

Original Message:
Sent: Apr 22, 2020 09:17
From: Ludovic Robert
Subject: Send MAC-ADDRESS Choosing the Right API

Hello

For me yes it makes sense as API orchestration.
Please note that we split the Activation & Configuration API in 2:

• TMF640 is Service Activation & Configuration
• TMF702 is Resource Activation & Configuration

Hope it helps
Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Original Message:
Sent: Apr 22, 2020 08:52
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

I was asking about when you need to go to the network.

So seems like the day of order one can use 641 and when tech is on premises and need to activate the service on the network using the physical resource one can use the 640. Am I correct on my interpretation?

If you agree I can close the thread Jon

------------------------------
Christopher Gonzalez
Intraway Corp

Original Message:
Sent: Apr 21, 2020 00:51
From: Jonathan Goldberg
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Christopher
First need to consider where the MAC address needs to be persisted.

• If it needs to be stored in Service Inventory (quite likely), TMF638 (Service Inventory Management) would be suitable.
• If it needs (additionally) to be stored in Product Inventory (visible to end-customer perhaps), then also TMF637 (Product Inventory Management) would be used
• If it needs to be updated in the network itself (not sure if there is such a use case), then TMF640 (Service Activation and Configuration)

@Ludovic Robert does this make sense?

Hope it helps​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Original Message:
Sent: Apr 20, 2020 10:34
From: Christopher Gonzalez
Subject: Send MAC-ADDRESS Choosing the Right API

Hi Guys, What is the right API to use when a technician has to send the Mac address to install a service that was previously sent using the 641?


------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------