Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

G-001/1: what interfaces? #82

Closed
dromasca opened this issue Dec 1, 2015 · 8 comments
Closed

G-001/1: what interfaces? #82

dromasca opened this issue Dec 1, 2015 · 8 comments

Comments

@dromasca
Copy link

dromasca commented Dec 1, 2015

In G-001:

The information model and interfaces MUST support the ability to
add new operations while maintaining backwards compatibility.

It is not clear what 'interfaces' are meant here.

@jimsch
Copy link
Contributor

jimsch commented Dec 2, 2015

Interfaces is more defined in G-012.

@dromasca
Copy link
Author

dromasca commented Dec 8, 2015

G-012 refers to device interfaces.

Here the text is: ‘The information model and interfaces MUST support …’ – do we mean here ‘device interfaces’? It does not make too much sense to me in an extensibility requirement. In any case, it must be specified – that what exactly the question.

Regards,

Dan

From: Jim Schaad [mailto:notifications@github.com]
Sent: Wednesday, December 02, 2015 5:04 AM
To: sacmwg/draft-ietf-sacm-requirements
Cc: Romascanu, Dan (Dan)
Subject: Re: [draft-ietf-sacm-requirements] G-001/1: what interfaces? (#82)

Interfaces is more defined in G-012.


Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sacmwg_draft-2Dietf-2Dsacm-2Drequirements_issues_82-23issuecomment-2D161164680&d=BQMCaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=THdbvImETZ221AgafVv9wSF7ZgjyN9uziwJ3zIlOazY&s=DDqpp8WeKozQIQNXasskTMFCZqDT5OjRt1F06BUZyLI&e=.

@ncamwing
Copy link
Contributor

Hi,
By interfaces I meant programming interfaces which can be a protocol as well; that is, the means by which information is being communicated. So from that standpoint, G-012 is the expansion to "interfaces" in G-001.

I can update it with a forward reference, so instead of "interfaces" it is "device interfaces (see G-012)"....OK?

@dromasca
Copy link
Author

OK with me.

Thanks and Regards,

Dan

From: Nancy [mailto:notifications@github.com]
Sent: Wednesday, January 20, 2016 1:38 AM
To: sacmwg/draft-ietf-sacm-requirements
Cc: Romascanu, Dan (Dan)
Subject: Re: [draft-ietf-sacm-requirements] G-001/1: what interfaces? (#82)

Hi,
By interfaces I meant programming interfaces which can be a protocol as well; that is, the means by which information is being communicated. So from that standpoint, G-012 is the expansion to "interfaces" in G-001.

I can update it with a forward reference, so instead of "interfaces" it is "device interfaces (see G-012)"....OK?


Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sacmwg_draft-2Dietf-2Dsacm-2Drequirements_issues_82-23issuecomment-2D173024029&d=BQMCaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=ZYQHreSnZquNCiEHdovvp0n96BG4WXe4KGMtLYcKdGw&s=VbGG_3kA09USIRKHAJiqBDgd7KSj6M2KQzDg45NxVcI&e=.

@henkbirkholz
Copy link
Member

Maybe the name of G-012 is also a little bit confusing? It might be just me, but "G-012 Device Interface" does not sound like a programming interface or protocol.

The architecture draft states that SACM components have SACM interfaces for communication between SACM components.

SACM (component) interfaces?

@dromasca
Copy link
Author

Yes. Clarifying the we mean programmatic interfaces would help, as ‘device interfaces’ has a different meaning for many people.

Regards,

Dan

From: henkbirkholz [mailto:notifications@github.com]
Sent: Wednesday, January 20, 2016 4:06 PM
To: sacmwg/draft-ietf-sacm-requirements
Cc: Romascanu, Dan (Dan)
Subject: Re: [draft-ietf-sacm-requirements] G-001/1: what interfaces? (#82)

Maybe the name of G-012 is also a little bit confusing? It might be just me, but "G-012 Device Interface" does not sound like a programming interface or protocol.

The architecture draft states that SACM components have SACM interfaces for communication between SACM components.

SACM (component) interfaces?


Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sacmwg_draft-2Dietf-2Dsacm-2Drequirements_issues_82-23issuecomment-2D173213398&d=BQMCaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=NCBlvtt4skXGeYD-Ec1W1Fr-nhPdowBudDDd8euAuPA&s=Zt1NVuA1EPzeEoqoLH6vA1VAKJ0BjWmc2nKM_fKPnFI&e=.

@llorenzin
Copy link

I like Henk's proposal of SACM Component Interfaces. Any objections?

@llorenzin
Copy link

Fixed in -12 (G-001) and -13 (G-012)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants