PAP01: Role of IP in the Smart Grid CLOSED
|Date||Updated By||Latest PAP Status|
|2011-07-27||Vishant Shah||The SGIP plenary both voted to include IETF RFC 6272 into the Catalog of Standards.|
|Task 1: Develop a set of requirements for different Smart Grid applications|| Key domain expert groups:
Utility and user groups, SG community,IEEE P2030, UCAiug Open SG, NEMA
|End of 2009||Collecting application communication requirements is underway. This draft matrix captures the progress made to date app_matrix_pap.xls|
|Task 2: Identify a core Protocol Suite for IP-based Smart Grid||IETF and all other interested parties||End of 2009|| Determine what protocols are of part of the IP “core” protocols.
Discuss usage in the context of the Smart Grid
| Task 3: Develop application specific protocol requirements
Identify additional protocols or protocol enhancements beyond the core suite required by a specific class of applicationsDevelop guidelines for IP-based Smart Grid deployment
|IETF and all other interested parties||Mid 2010|| Refine the core suite developed in Task 2 by developing a modular suite of IP protocols in support of different application categories
Develop guidelines for usage including implementation, deployment choices and trade-offs.
|Task 4: Meet in July 2010 to develop additional task items||OpenSG||Jul 2010||Minutes & action items in meeting call below|
|Task 5: Mapping of RFCs to satisfy requirements developed by CSCTG (NISTIR 7628) and guidelines for implementations||IETF and all other interested parties||Dec 2010||Need coordination with CSCTG|
|Task 6:Develop a profile of IPv6 protocols for Smart Grid||NIST and all other interested parties||Dec 2010||Uses USG IPv6 Profile as a base|
|Task 7: Develop an architecture document for Smart Grid IP networks||IETF||Nov 2010|
| Task 8: Perform gap analysis
Identify new protocol or protocol enhancement standardization activities required to fully support Smart Grid in the future
|IETF and all other interested parties||Aug 2010|| Map the application requirements developed in Task 1 against the specifications developed in Task 3 to determine any missing pieces or gaps.
Start standard development activities to close the gaps identified
The Internet technologies consist of a set of protocols to network and transport data messages using IP packets, as well as a set of protocols to manage and control the network, such as routing, mapping of IP addresses, device management, etc. This protocol suite enables distributed applications to run over a set of interconnected networks. It also includes session- and transaction-oriented security mechanisms to provide security services.
The Smart Grid will need a comprehensive mapping of smart grid application requirements to the capabilities of protocols and technologies in a well define set of Internet Protocol Suite(s) or Profiles. This should be defined by experts well versed in the applications and protocols including management and security. A set of well-defined networking profiles can be tested for consistency and interoperability to help ensure systems integration as appropriate across the Smart Grid. A set of consistent and testable protocol profiles is also necessary to ensure that the combination of technologies can meet not only today’s requirements but meet future application needs as well. The networking profiles defined by this work will define a significant portion of the interfaces to Smart Grid equipment and systems. Most notably the interfaces that integrate systems over Wide Area Networks and large geographical areas will need to be defined in part by these profiles. The networking profiles will define networking functions such as addressing and the integration of concepts such as multihoming and other key functions necessary for the Smart Grid.
The Smart Grid will use a variety of different networking environments across smart grid domains and sub-domains as identified in the smart grid applications and conceptual models. The suitability of the proposed protocol suites or profiles in specific application contexts should be analyzed against the requirements emerging for Smart Grid applications and the proposed scale and scope of Smart Grid networks. The analysis should identify which protocols are clearly applicable in specific application contexts (e.g. use of TCP/IP, UDP, TLS/SSL, IPsec , IPV4/IPV6, MPLS) and protocols for network control, management and security, in addition to identifying any existing gaps.
This task will require the development of a combination of networking standards into well defined sets known as profiles. Working from existing and proposed Smart Grid applications and use cases the approach will require the distillation of Smart Grid applications and requirements into sets of networking profiles. These profiles will need to be developed into designs and implementations that can then be tested against the requirements. The communities that need to be involved include those within the Internet Engineering Task Force as well as other research communities that are working on networking technology.
|NIST Lead: David Su; Nada Golmie|
|EnerNex Technical Champion Leads: Vishant Shah; Joe Hughes|
|CSWG Liaison: Isaac Ghansah|
|SGAC Liaison: Fred Baker|
|SDOs: IETF, ATIS , IEEE, TIA, UCAuig Open Grid, NEMA|
The following document are draft minutes from St. Louis PAP 1 meeting.
PAP 1 met at the OpenSG meeting in Detroit on Thursday, July 22, 2010.
Major action items from the meeting include:
Additional details can be found in the meeting minutes below.
Registration information and logistics details: here.
A combined session of PAP 1 & PAP 2 took place at Grid Interop in Denver on November 18, 2009. Session information and details are available here.
Both IP and wireless communications priority action plans include as a first task the development of network requirements for Smart Grid applications. Identifying these requirements is key in order to develop guidelines for the use of IP and wireless communications in the context of the Smart Grid. Following a quick overview and a status update on these two PAP activities to date, this session will be dedicated to discussing and completing the draft application communications requirements matrix being developed under Task 1. Presentations discussed during the meeting:
Audio for the session is also available here
Task 1 calls for the collection of application communication requirements. A template matrix capturing different Smart Grid applications (rows) and their communication characteristics (columns) was developed. Table entries are intended to provide quantitative communication requirements for different Smart Grid applications and hence drive the development of guidelines for the use of different communication technologies. We appreciate any feedback on the template developed app_matrix_pap.xls to date and seek input for completing it.
Task 2 calls for identifying a core set of IP protocol specifications that can be used for Smart Grid. To this end the following contributions were submitted for consideration:
Comments and feedback are welcome.
|Could you please let me know when and where is this group meeitng?||RubenSalazar||2009-07-22 - 16:05|
|Some of the selected standards use short stacks that run on Ethernet only. An example is the profile for 61850 GOOSE and Sampled Value.||StanKlein||2009-07-24 - 10:32|
|This PAP reads like a research activity and not a standards activity. Work that may come from research in something such as Task 8 (identify places where IP may not function well), may uncover solutions that can contribute to specific standards efforts. The premise in Section 1.4, “The Smart Grid will need a comprehensive mapping of smart grid application requirements to the capabilities of protocols and technologies in a well defined set of IP suites or profiles.” sounds so broad as to be unwieldy. It says that these should be defined by “experts”, but this begs the question, “Who will be nominated as experts?” The real experts are those who work on the projects that implement the protocols and technology successfully and learn the lessons of that experience. Please consider recasting the PAP as a research issue with tasks and deliverables that may serve to define a future standards activity. Side note: If there are to be requirements for IETF standardization, then consideration should be given to the broad requirements of all process control and financial transaction industries while trying to avoid something special to electric power.||SteveWidergren||2009-09-03 - 10:02|
|The tasks have been re-organized in order to better achieve the stated objectives and identify long-term standard development requirements.||NadaGolmie||2009-10-22|
|The long-term SmartGrid connectivity requirements will mandate uniquely addressing tens of million devices if it is to be even nominally successful. Such a requirement not only exceeds currently available IPv4 address space, but is also larger than reserved address space for private internets (RFC 1918). The PAP team needs to either develop an IPv4 addressing plan which resolves this issue (including the numerous NAT, overlap, and conflict issues), or it needs to specify IPv6 as the network layer protocol for SmartGrid project.||JohnCurran||2009-10-14 - 05:48|
|I would like to offer the opinion that IPv4/IPv6 not really a smart grid issue. As the smart grid evolves, it will interface with many other systems. In some cases these other systems will use IPv4, in some cases IPv6, and in some cases proprietary (or at least non-IP) addressing schemes. Regardless of whether we prefer IPv4 or IPv6, the interface points will drive the addressing schemes and force translations where necessary. As the Internet increasingly migrates towards IPv6, so will the smart grid.||AndrewWright||2009-10-20 - 11:16|
|While I am an Internet advocate and specifically a promoter of IPv6, I notice the statement at the top of this page is suitably skeptical "...to study the suitability of Internet networking technologies for smart grid applications." It should not be a forgone conclusion that IP is the solution for smart grid, first examine the use cases. IP (and specifically IPv6) is probably the only sensible solution for widely distributed and individually addressable sensors and "control points" like dimmers, thermostats, etc. but may be inappropriate for the creation of a control plane for critical infrastructure. A closed network using some other standard, perhaps a new protocol, might be the right answer there. Consider opening up the discussion, and taking it back to an architectural level before committing to solutions.||EdJankiewicz||2009-10-27 - 16:53|
|Is the comment period still open for the two documents posted above?||JoeDiAdamo||2009-11-27 - 17:04|
|What's happening with the PAP 1?||JoeDiAdamo||2010-01-29 - 15:45|
|Regarding the comment about IPv6 and internet protocols, I would say, nor should it be a forgone conclusion that significant use of the "Internet" is not possible or advisable. I like the suggestion of taking it 'back to the architectural level'. In fact I would wind back before that to look at cost and other factors that would tend to drive the architecture. I have started to draft PAPS to suggest work in these areas. The are currently posted with a few bits of information and are: InternetIntegration, PAPDataModeIing , and PAPRequirementsAndScope. They are not complete, but all have at least an abstract with the basic idea.||JonSaperia||2010-01-30 - 09:22|
|PAPDataModeling had a typo this link should work.||JonSaperia||2010-01-30 - 09:27|
|What is the consensus-based process underlying the recently-made changes? Was there a meeting? If so, where was the meeting announcement? Where are the minutes? Why were these changes made?||EdwardBeroset||2010-06-21 - 10:53|
|doc||CSWG_Comments_on_PAP01_2010-10-27.doc||manage||68.0 K||2010-10-28 - 14:52||VishantShah||CSWG comments on draft IETF informational RFC|
|ISOC_IPv6_SmartGrid_July2010.pdf||manage||1444.0 K||2010-07-22 - 20:11||NadaGolmie||Presentation by Phil Roberts|
|pptx||Internet_Stack.pptx||manage||610.7 K||2010-07-22 - 20:14||NadaGolmie||Presentation by Fred Baker|
|docx||Issues_for_PAP01_5-20-10.docx||manage||15.2 K||2010-07-01 - 18:35||VishantShah|
|xls||Latency_BW.xls||manage||43.5 K||2009-12-17 - 11:33||NadaGolmie||Sensus Communication Requirements|
|doc||Minutes_of_July_22_Detroit_PAP01_Meeting.doc||manage||47.0 K||2010-08-02 - 15:10||DavidSu||PAP01 July F2F meeting minutes|
|doc||NIST_PAP_01-IP_in_Smart_Grid_v.1.0-Oct_30th_2009.doc||manage||737.0 K||2009-11-06 - 18:54||NadaGolmie||Role of IP in AMI Networks|
|NMIssuesPaper.pdf||manage||120.0 K||2010-09-23 - 09:44||JonSaperia||Short white paper describing issues and need for integrated Network Management work.|
|doc||Notes_St_Louis_PAP_1doc_Hughes.doc||manage||58.0 K||2010-10-07 - 18:46||JoeHughes||Meeting Notes from St Louis PAP 1|
|ppt||PAP01CallAgenda10282010.ppt||manage||206.0 K||2010-10-27 - 18:11||VishantShah||Oct 28 Agenda|
|ppt||PAP01CallAgenda10282010Rev1.ppt||manage||272.0 K||2010-10-28 - 12:08||VishantShah||Updated Call Agenda|
|PAP01IntegratedNMPres.pdf||manage||31.4 K||2010-09-23 - 09:27||JonSaperia|
|pptx||PAP01_Agenda_09152010.pptx||manage||67.4 K||2010-09-14 - 22:06||DavidSu||Agenda for PAP01 F2F meeting, September 15|
|ppt||PAP01_F2F_Meeting_Agenda_July_22_2010.ppt||manage||28.5 K||2010-07-20 - 11:40||DavidSu||PAP01 F2F meeting agenda, OpenSG,|
|xls||PAP01_SecurityRFCs_v1.0_07-13-10.xls||manage||37.0 K||2010-07-13 - 11:47||TedFischer||PAP01 Task 2 RFC List for CSWG Requirements|
|ppt||PAP12November09.ppt||manage||213.5 K||2009-11-19 - 13:47||NadaGolmie||Priority Action Plans for IP and Wireless|
|wav||PAP1and2.wav||manage||58073.1 K||2009-11-19 - 12:17||CarrieParks||Audio recording of PAP 1 and 2 meetings 11.19.09|
|pptx||SG-NET_status_update_V2.pptx||manage||658.2 K||2009-11-18 - 16:22||ErichGunther||Gilmore Presentation at GridInterop|
|txt||SGIP-PAP01WG_LOGs.txt||manage||9160.3 K||2012-01-25 - 14:43||AaronSnyder||SGIP-PAP01WG listserv list archive file|
|xls||SG_Communications_funct-reqs_v1-draft.xls||manage||70.0 K||2009-12-17 - 11:32||NadaGolmie||OpenSG Draft Application Communication Requirements|
|htm||draft-baker-ietf-core-05.htm||manage||131.8 K||2010-07-20 - 11:55||DavidSu||Internet Protocols for the Smart Grid, Fred Baker|
|txt||draft-baker-ietf-core-05.txt||manage||90.7 K||2010-07-20 - 11:52||DavidSu||Internet Protocols for the Smart Grid, Fred Baker|