OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-511) Registration cancellation parameters ill-defined


    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28042#action_28042 ] 

William Cox commented on ENERGYINTEROP-511:
-------------------------------------------

I agree with Jerry on the firewall quesiton.

Registration is of a Party; the new name (EiCancelPartyRegistration) makes that clear.. A Party MAY implement/take on the role of a VEN, VTN, or both, in any MarketContext in which it participates.

With the cancelation, a relationship is established, and the intent was that either party could break that relationship.  Whether there are agreements/contracts affecting the relationship is out of scope for Energy Interoperation -- the parties must be presumed to follow their own rules. The check is internal to the party, and the description of agreements is also out of scope.

So clarity is needed in the Registration and Enrollment sections on who is registering/enrolling and what that means. 

Clarity is also needed to with respect to the entire registration paradigm, and what it means to cancel a registration.

> Registration cancellation parameters ill-defined
> ------------------------------------------------
>
>                 Key: ENERGYINTEROP-511
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-511
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: schema
>         Environment: OpenADR
>            Reporter: Toby Considine
>            Assignee: William Cox
>             Fix For: wd29
>
>
> There is confusion about who is allowed to initiate a registration cancellation. If a VEN registers with a VTN, who exactly can cancel the VEN to VTN registration  relationship? Just the VEN, just the VTN, or either? If the VTN can cancel the relationship, how would that work in a pull model with the VEN behind a firewall? More description is needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]