1 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 Eric Simmon, NIST Jerry Melcher, EnerNex SGIP PAP 11 PEV V2G DEWG Grid InterOp 2010 Meeting

2 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 Agenda Announcements Status of PAP 11 Closure Result of submission to SGIP Governing Board PEV PAP/V2G DEWG issues Creation of PAP 18 – PEV Implementation Open Discussion Next Meeting

3 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 Announcements EPRI IWC, Dec 7,8, 2010 – Phoenix, AZ Status of PAP 11 Closure PEV PAP/V2G DEWG issues Creation of PAP 18 – PEV Implementation Open Discussion Next Meeting

4 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 Announcements Status of PAP 11 Closure Results of Submission to SGIP Governing Board SAE J1772-TM and J2836/1 go to SGIP-GB for ballot SAE J2847/1 redirected to address cyber security language – develop timeline for reballot PEV PAP/V2G DEWG issues Creation of PAP 18 – PEV Implementation Open Discussion Next Meeting

5 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 Eric Simmon, NIST SGAC & CSWG Review of PAP11 Standards

6 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 SGIP Grid-Interop 2010, Chicago, Ill SGAC C OMMENTS SGAC COMMENTS SAE J – The term premise is incorrectly used in several places in the document. The correct term is premises. RESPONSE: Editorial fix will be made this next revision of j2847 – The definition of “Interoperability” is weak. It would be more appropriate to use the definition developed by the GWAC. RESPONSE: proposed definition: "The condition where components of a system, relative to each other, are able to work together to perform the intended operation of the total system. Information interoperability is the capability of two or more networks, systems, devices, applications, or components to share and readily use information securely and effectively with little or no inconvenience for the user.”

7 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 SGIP Grid-Interop 2010, Chicago, Ill SAE J (cont) – The standard seems to assume an architecture with all communications from the vehicle to the grid flowing through the electric meter. The standard would be better constructed were it to clearly separate the syntactic and semantic communications from the physical communications path. RESPONSE: Section 4.4 and all sequence diagrams will be removed from j2847 (j2847 will focus only on the messages). SGAC C OMMENTS SGAC COMMENTS

8 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 SGIP Grid-Interop 2010, Chicago, Ill SAE J – Same misuse of the work premise when the work premises should be used. RESPONSE: Editorial fix will be made this revision – Same comment regarding definition of interoperability on page 10. RESPONSE: Same interoperability definition will be used as in J SAE J1772™ No Comments SGAC C OMMENTS SGAC COMMENTS

9 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 SGIP Grid-Interop 2010, Chicago, Ill SAE J – Remove all references to cybersecurity and develop a separate, corresponding cyber-security document. Because there are many missing cybersecurity requirements, it is recommended that Section and all references to cybersecurity be removed from this document and that another document or documents be developed to address cybersecurity for these information exchanges. RESPONSE: Change will be made this revision. New document has been created (SAE J2931) CSWG C OMMENTS CSWG COMMENTS

10 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 SGIP Grid-Interop 2010, Chicago, Ill SAE J – Remove the mapping to SEP2.0 in order to separate semantic standards from their mappings to different protocols that will have different cybersecurity technologies. Because the SEP 2.0 protocol is not yet defined, may not be used by utility operational systems, and because other protocols could be used to support the messages defined in Section 4.3 in different architectures with different cyber-security technologies, it is recommended that Section 4.4 be removed in order to keep the semantic standards separate from the various protocols which could transport those messages. RESPONSE: Change will be made this revision. New document has been created: SAE J2931 CSQG C OMMENTS CSQG COMMENTS

11 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 SGIP Grid-Interop 2010, Chicago, Ill SAE J – Ensure consistency with the results of other PAPs. Role of the Internet Protocol Suite (IPS) in the Smart Grid, developed as an output of PAP 01,[1] does not include EAP (RFC 3748), but instead identifies EAP- TLS (RFC 5216), which in turn references EAP (RFC 3748). Consistency between PAP 1 and PAP 11 would be a good goal, but is not absolutely required. RESPONSE: will work to coordinate between PAPs. (refer to IETF IPS working group proposed this week during GB meeting) CSWG C OMMENTS CSWG COMMENTS

12 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 SGIP Grid-Interop 2010, Chicago, Ill – SAE Reference the FIPS-approved list of cryptography suites. The acceptable cyber cryptography suites are listed, which may limit future applicability. It is suggested that the document reference the Federal Information Processing Standard (FIPS)-approved list of cryptography suites. – RESPONSE: Will bring to SAE - use FIPS as general standard – References to unfinalized IETF RFCs should be removed. The reference to IETF RFC 4492 should be removed until the IETF finalizes the RFC. RESPONSE: Yes, will review and make changes as necessary CSWG C OMMENTS CSWG COMMENTS

13 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 SGIP Grid-Interop 2010, Chicago, Ill SAE J2836 – It is recommended that this standard be accepted as is, but that additional cybersecurity Use Cases be developed during the next V2G PAP and/or DEWG efforts. RESPONSE: A subgroup will be formed within the V2G DEWG to develop v2g cybersecurity use cases – The normative and informative reference document list within SAE J2836/1 should also be reviewed to determine if any cybersecurity requirements in those documents need to be updated or enhanced. RESPONSE: SAE will coordinate with CSWG CSWG C OMMENTS CSWG COMMENTS

14 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 SGIP Grid-Interop 2010, Chicago, Ill SAE J1772 – If PLC, wireless, or other potentially radiating technology is used for the communications, the traffic between the PEV and the EVSE should be encrypted. RESPONSE: it's going to be covered in other standards. security will be an important issue. – The normative and informative reference document list within SAE J1772-TM should be reviewed to determine if any cybersecurity requirements in those documents need to be updated or enhanced. RESPONSE: SAE will coordinate with CSWG CSWG C OMMENTS CSWG COMMENTS

15 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 Announcements Status of PAP 11 Closure PEV PAP/V2G DEWG issues Creation of PAP 18 – PEV Implementation Open Discussion Next Meeting

16 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 PEV PAP/V2G DEWG issues

17 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 PEV PAP/V2G DEWG issues - cont

18 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 Announcements Status of PAP 11 Closure PEV PAP/V2G DEWG issues Creation of PAP 18 – PEV Implementation > Objectives and Scopes Open Discussion Next Meeting

19 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 Announcements Status of PAP 11 Closure PEV PAP/V2G DEWG issues Creation of PAP 18 – PEV Implementation Open Discussion  Blue Sky Brainstorming Session Next Meeting

20 SGIP PAP 11 PEV V2G DEWG Dec 2-3, 2010 Grid InterOp 2010 Announcements Status of PAP 11 Closure PEV PAP/V2G DEWG issues Creation of PAP 18 – PEV Implementation Open Discussion Next Meeting - PEV V2G DEWG  Thurs, Dec 21  EPRI IWC, Dec 7-8, Phoenix, AZ  EPRI IWC, March, San Diego, CA  Blue Sky Brainstorming Session