[OASIS Issue Tracker] (TOSCA-276) F.5.2 tosca.nodes.network.Port is a NIC and we call it Port

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60668#comment-60668 ] 

Luca Gioppo commented on TOSCA-276:
-----------------------------------

I'm sorry !!
I've had a talk with a friend of mine that is a network sysadmin and I finally understood the problem.
I'm more on the application side so I reason more at a level 4 of OSI and for me port is the TCP port.

I see now that the node name comes from the most commonly used term in the Level 2/1 OSI that is the "port of a switch or the port of the NIC".

We live in the IT world where overload of terms is usual but many times is confined to a scoped environment where people talk all the same slang so network people understand each other; unfortunately this standard goes from very low level things to application stuff, collecting all the overloads we have.

Said that now I have a more clear idea and stated that I'm not a network guy, my question is:
Since the standard needs to talk to a set of subjects that could have the same confusion, is there a way to avoid the ambiguous overload (not only on this subject, but even if potential future issues)?
My concern is the "usability of the standard": who is the subject that we think will be writing a TOSCA file? At the moment highly skilled people with multi competency in design the deployment of a complex system.  How we plan to ease this job? The risk is that no one will want to use it (talk form a customer perspective)

> F.5.2 tosca.nodes.network.Port is a NIC and we call it Port
> -----------------------------------------------------------
>
>                 Key: TOSCA-276
>                 URL: https://issues.oasis-open.org/browse/TOSCA-276
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>            Reporter: Luca Gioppo
>
> As stated in the documentation the F.5.2 tosca.nodes.network.Port is a NIC but we call it Port that is something very different.
> Proposal is to change the name of this node to NIC and not Port to help also better understanding.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)