The Use of Ethernet Technology in the Power Utility Environment

Total Page:16

File Type:pdf, Size:1020Kb

The Use of Ethernet Technology in the Power Utility Environment 460 The use of Ethernet Technology in the Power Utility Environment Working Group D2.23 April 2011 The use of Ethernet Technology in the Power Utility Environment Members Carlos Samitier (Convenor) Spain, Mehrdad Mesbah (Secretary) France, Jorge Fonseca-Portugal,Pat Cooney-Ireland, Anders Runesson-Sweden, Andres Cadenas-Spain, Aitor Arzuaga-Spain, Emiliano Marquesini-UK, Paul Schwyter-Switzerland, Sampo Yliraasakka-Finland, Ray Elliott-South Africa, Oyvind Finnekaasa-Norway, Chris Huntley-Canada Corresponding Members Rodolfo Pellizzoni-Argentina,Dugald Bell-Australia, Jan Piotrowski-Poland, Claudio Trigo-Brazil,Masami Inoue-Japan, Mrs. Jovanka Gajica-Serbia, Wan Azlan-Malaysia Copyright © 2011 “Ownership of a CIGRE publication, whether in paper form or on electronic support only infers right of use for personal purposes. Are prohibited, except if explicitly agreed by CIGRE, total or partial reproduction of the publication for use other than personal and transfer to a third party; hence circulation on any intranet or other company network is forbidden”. Disclaimer notice “CIGRE gives no warranty or assurance about the contents of this publication, nor does it accept any responsibility, as to the accuracy or exhaustiveness of the information. All implied warranties and conditions are excluded to the maximum extent permitted by law”. ISBN: 978- 2- 85873- 149-7 1 1 INTRODUCTION ...................................................................................................... 6 1.1 Scope of Work .................................................................................................... 8 1.2 What is Ethernet? ................................................................................................ 8 1.3 Service Provision Model ................................................................................... 10 1.4 Benefits ............................................................................................................. 11 1.5 Business Implications ....................................................................................... 13 1.6 Cost Considerations .......................................................................................... 14 2 UTILITY INDUSTRY CONTEXT AND APPLICATIONS FOR ETHERNET .... 15 2.1 Introduction ....................................................................................................... 15 2.2 Utility Applications ........................................................................................... 15 2.2.1 Substation Control .................................................................................... 15 2.2.2 Substation Data Analysis .......................................................................... 15 2.2.3 Real Time Protection and Automation ..................................................... 16 2.2.4 Substation Automation Platform Management ......................................... 16 2.2.5 Commercial Applications ......................................................................... 16 2.2.6 Substation Management ............................................................................ 17 2.2.7 Site Working ............................................................................................. 17 2.2.8 Security Applications ................................................................................ 17 2.2.9 Substation Operational Voice System ...................................................... 18 2.2.10 Collaborative Multi-media Communications ........................................... 18 2.3 Substation Automation Process – IEC61850 .................................................... 19 2.3.1 Introduction to IEC61850 ......................................................................... 19 2.3.2 Model & Mechanisms of IEC61850 ......................................................... 19 2.3.3 Time synchronisation for substation automation ...................................... 22 2.3.4 Further Extensions .................................................................................... 22 2.4 SCADA and ICCP related Utility communication characteristics ................... 23 2.4.1 Overview of EMS/SCADA Communications .......................................... 23 2.4.2 SCADA RTU to Control Centre Communications ................................... 24 2.4.3 Inter-Control Centre Communications ..................................................... 26 2.4.4 SCADA System Security .......................................................................... 27 3 NETWORK TECHNOLOGY DESCRIPTION ....................................................... 29 3.1 Concepts and Definitions .................................................................................. 29 3.1.1 Topology: LAN, MAN and WAN ............................................................ 29 3.1.2 Layer 2 networking ................................................................................... 29 3.1.3 Differences with Layer 3 IP network ........................................................ 30 3.2 Networking architecture .................................................................................... 30 3.2.1 Bridging .................................................................................................... 30 3.2.2 Switching .................................................................................................. 30 3.2.3 Virtual Networking ................................................................................... 31 3.2.4 RPR – Resilient Packet Ring .................................................................... 33 3.2.5 Provider Backbone Bridging ..................................................................... 34 3.2.6 MPLS-TP .................................................................................................. 35 3.3 Protection Mechanisms ..................................................................................... 36 3.3.1 Spanning Tree ........................................................................................... 36 3.3.2 Ethernet Ring Protection ........................................................................... 37 3.3.3 IEC 62439 Parallel Redundancy Protocol (PRP) ...................................... 37 3.4 Existing relevant Ethernet standards ................................................................. 38 2 3.5 Authentication & Security services over Ethernet ............................................ 40 3.5.1 Physical port protection ............................................................................ 40 3.5.2 Authentication & Encryption (RADIUS) ................................................. 41 4 ETHERNET TRANSMISSION TECHNOLOGIES ................................................ 42 4.1 Introduction ....................................................................................................... 42 4.2 Copper interfaces .............................................................................................. 43 4.3 Fibre interfaces .................................................................................................. 43 4.3.1 Optical Gigabit Ethernet Interfaces .......................................................... 43 4.3.2 10 Gigabit Ethernet interfaces .................................................................. 44 4.4 Optical Networks - Wavelength division multiplexing .................................... 45 4.4.1 CWDM (Coarse Wavelength Division Multiplexing) .............................. 45 4.4.2 DWDM (Dense Wavelength Division Multiplexing) ............................... 46 5 TRANSPORT OF ETHERNET OVER SDH ........................................................... 47 5.1 Introduction ....................................................................................................... 47 5.2 Modern SDH Data Capabilities ........................................................................ 47 5.2.1 Virtual concatenation ................................................................................ 49 5.2.2 Dynamic Bandwidth Allocation ............................................................... 49 5.2.3 Generic Framing Procedure (GFP) ........................................................... 49 5.2.4 Combining TDM and LAN Services ........................................................ 52 6 ETHERNET ACCESS TECHNOLOGIES .............................................................. 54 6.1 Ethernet over xDSL .......................................................................................... 54 6.2 PDH sub-E1 mapping ....................................................................................... 55 6.3 Inverse Multiplexing ......................................................................................... 55 6.4 Microwave Radio .............................................................................................. 56 6.4.1 Microwave Backbone Ethernet ................................................................. 56 6.4.2 Microwave Access Systems ...................................................................... 56 6.5 DPLC Bridge .................................................................................................... 57 6.6 GPRS and UMTS .............................................................................................. 59 6.7 VSAT ................................................................................................................ 60 6.8 Broadband Power Line Communication ..........................................................
Recommended publications
  • INTRODUCTION Client
    1 INTRODUCTION Client Server Network Fig. 1-1. A network with two clients and one server. Client machine Server machine Request Network Reply Client process Server process Fig. 1-2. The client-server model involves requests and replies. Fig. 1-3. In a peer-to-peer system there are no fixed clients and servers. 2222222222222222222222222222222222222222222222222222222222222222222222222222222 21 222222222222222222222222222222222222222222222222222222222222222222222222222222Tag1 Full name1 Example 1 1 1 1 1 12222222222222222222222222222222222222222222222222222222222222222222222222222222B2C1 Business-to-consumer1 Ordering books on-line 1 21 222222222222222222222222222222222222222222222222222222222222222222222222222222B2B1 Business-to-business1 Car manufacturer ordering tires from supplier 1 21 222222222222222222222222222222222222222222222222222222222222222222222222222222G2C1 Government-to-consumer1 Government distributing tax forms electronically 1 1 1 1 1 12222222222222222222222222222222222222222222222222222222222222222222222222222222C2C1 Consumer-to-consumer1 Auctioning second-hand products on line 1 21 222222222222222222222222222222222222222222222222222222222222222222222222222222P2P1 Peer-to-peer1 File sharing 1 Fig. 1-4. Some forms of e-commerce. 22222222222222222222222222222222222222222222222222222222222222 222222222222222222222222222222222222222222222222222222222222221 Wireless1 Mobile1 Applications 1 1 1 1 1 122222222222222222222222222222222222222222222222222222222222222No1 No1 Desktop computers in offices 1 222222222222222222222222222222222222222222222222222222222222221
    [Show full text]
  • Network Reliability and Fault Tolerance
    Network Reliability and Fault Tolerance Muriel Medard´ [email protected] Laboratory for Information and Decision Systems Room 35-212 Massachusetts Institute of Technology 77 Massachusetts Avenue, Cambridge, MA 02139 Steven S. Lumetta [email protected] Coordinated Science Laboratory University of Illinois Urbana-Champaign 1308 W. Main Street, Urbana, IL 61801 1 Introduction The majority of communications applications, from cellular telephone conversations to credit card transactions, assume the availability of a reliable network. At this level, data are expected to tra- verse the network and to arrive intact at their destination. The physical systems that compose a network, on the other hand, are subjected to a wide range of problems, ranging from signal distor- tion to component failures. Similarly, the software that supports the high-level semantic interface 1 often contains unknown bugs and other latent reliability problems. Redundancy underlies all ap- proaches to fault tolerance. Definitive definitions for all concepts and terms related to reliability, and, more broadly, dependability, can be found in [AAC+92]. Designing any system to tolerate faults first requires the selection of a fault model, a set of possible failure scenarios along with an understanding of the frequency, duration, and impact of each scenario. A simple fault model merely lists the set of faults to be considered; inclusion in the set is decided based on a combination of expected frequency, impact on the system, and feasibility or cost of providing protection. Most reliable network designs address the failure of any single component, and some designs tolerate multiple failures. In contrast, few attempt to handle the adversarial conditions that might occur in a terrorist attack, and cataclysmic events are almost never addressed at any scale larger than a city.
    [Show full text]
  • Operaing the EPON Protocol Over Coaxial Distribuion Networks Call for Interest
    Operang the EPON protocol over Coaxial Distribu&on Networks Call for Interest 08 November 2011 IEEE 802.3 Ethernet Working Group Atlanta, GA 1 Supporters Bill Powell Alcatel-Lucent Steve Carlson High Speed Design David Eckard Alcatel-Lucent Hesham ElBakoury Huawei Alan Brown Aurora Networks Liming Fang Huawei Dave Baran Aurora Networks David Piehler Neophotonics Edwin MalleIe Bright House Networks Amir Sheffer PMC-Sierra John Dickinson Bright House Networks Greg Bathrick PMC-Sierra Ed Boyd Broadcom ValenWn Ossman PMC-Sierra Howard Frazier Broadcom Alex Liu Qualcomm Lowell Lamb Broadcom Dylan Ko Qualcomm Mark Laubach Broadcom Steve Shellhammer Qualcomm Will Bliss Broadcom Mike Peters Sumitomo Electric Industries Robin Lavoie Cogeco Cable Inc. Yao Yong Technical Working CommiIee of China Radio & Ma SchmiI CableLabs TV Associaon Doug Jones Comcast Cable Bob Harris Time Warner Cable Jeff Finkelstein Cox Networks Kevin A. Noll Time Warner Cable John D’Ambrosia Dell Hu Baomin Wuhan Yangtze OpWcal Technologies Co.,Ltd. Zhou Zhen Fiberhome Telecommunicaon Ye Yonggang Wuhan Yangtze OpWcal Technologies Co.,Ltd. Technologies Zheng Zhi Wuhan Yangtze OpWcal Technologies Co.,Ltd. Boris Brun Harmonic Inc. Marek Hajduczenia ZTE Lior Assouline Harmonic Inc. Meiyan Zang ZTE David Warren HewleI-Packard Nevin R Jones ZTE 2 Objec&ves for This Mee&ng • To measure the interest in starWng a study group to develop a standards project proposal (a PAR and 5 Criteria) for: Operang the EPON protocol over Coaxial DistribuWon Networks • This meeWng does not: – Fully explore the problem – Debate strengths and weaknesses of soluWons – Choose any one soluWon – Create PAR or five criteria – Create a standard or specificaon 3 Agenda • IntroducWon • Market PotenWal • High Level Concept • Why Now? • Q&A • Straw Polls 4 The Brief History of EPON 2000 EPON Today..
    [Show full text]
  • Ethernet Interconnection Point (EIP): an ENNI Implementation Agreement
    Service Operations Specification MEF 54 Ethernet Interconnection Point (EIP): An ENNI Implementation Agreement March 2016 MEF 54 © MEF Forum 2016. Any reproduction of this document, or any portion thereof, shall contain the follow- ing statement: "Reproduced with permission of MEF Forum." No user of this document is authorized to modify any of the information contained herein. Disclaimer The information in this publication is freely available for reproduction and use by any re- cipient and is believed to be accurate as of its publication date. Such information is sub- ject to change without notice and the MEF Forum (MEF) is not responsible for any er- rors. The MEF does not assume responsibility to update or correct any information in this publication. No representation or warranty, expressed or implied, is made by the MEF concerning the completeness, accuracy, or applicability of any information contained herein and no liability of any kind shall be assumed by the MEF as a result of reliance upon such information. The information contained herein is intended to be used without modification by the re- cipient or user of this document. The MEF is not responsible or liable for any modifica- tions to this document made by any other party. The receipt or any use of this document or its contents does not in any way create, by im- plication or otherwise: a) any express or implied license or right to or under any patent, copyright, trade- mark or trade secret rights held or claimed by any MEF member company which are or may be associated with the ideas, techniques, concepts or expressions con- tained herein; nor b) any warranty or representation that any MEF member companies will announce any product(s) and/or service(s) related thereto, or if such announcements are made, that such announced product(s) and/or service(s) embody any or all of the ideas, technologies, or concepts contained herein; nor c) any form of relationship between any MEF member companies and the recipient or user of this document.
    [Show full text]
  • The Role of Emerging Broadband Technologies on the Converged
    The Role of Emerging Broadband Technologies on the Converged Packet-Based Network Introduction The vision of network convergence toward a consolidated packet-based network has been discussed for years, though it is still not a reality. Currently, there are numerous overlay networks such as IP, ATM, FR, Ethernet, SONET, DWDM and wireless for different services. The evolution pace toward convergence has been slow due to economic, technical and regulatory issues. However, the fact is that data traffic volume is now surpassing voice traffic volume. Traditional TDM voice traffic is moving to IP packets and TDM private line is moving to Ethernet private line. The wave of broadband applications such as Internet access, VOD, and IPTV create high bandwidth requirements for the network. These applications are packet-based, but have a much lower margin of profit for the service providers when compared to traditional voice service. Today’s overlay and traditional circuit-based infrastructure will become less optimal for the new packet-based services as the profit margin decreases. Most of the wireless networks in North America today are still circuit-based because most of the current wireless service is still voice-based. However, with emerging wireless access technologies such as WiMAX and Wi-Fi, more broadband wireless data and video services can be deployed. As a result, the wireless core network evolves toward a packet-based network. Service offerings drive network evolution. As more packet-based broadband services are launched and bundled together in service offerings, service providers start to add more packet-aware features into their current network components.
    [Show full text]
  • Congestion Control in Resilient Packet Ring Networks
    New Jersey Institute of Technology Digital Commons @ NJIT Dissertations Electronic Theses and Dissertations Fall 1-31-2005 Congestion control in resilient packet ring networks Alharbi Fahd New Jersey Institute of Technology Follow this and additional works at: https://digitalcommons.njit.edu/dissertations Part of the Electrical and Electronics Commons Recommended Citation Fahd, Alharbi, "Congestion control in resilient packet ring networks" (2005). Dissertations. 670. https://digitalcommons.njit.edu/dissertations/670 This Dissertation is brought to you for free and open access by the Electronic Theses and Dissertations at Digital Commons @ NJIT. It has been accepted for inclusion in Dissertations by an authorized administrator of Digital Commons @ NJIT. For more information, please contact [email protected]. Copyright Warning & Restrictions The copyright law of the United States (Title 17, United States Code) governs the making of photocopies or other reproductions of copyrighted material. Under certain conditions specified in the law, libraries and archives are authorized to furnish a photocopy or other reproduction. One of these specified conditions is that the photocopy or reproduction is not to be “used for any purpose other than private study, scholarship, or research.” If a, user makes a request for, or later uses, a photocopy or reproduction for purposes in excess of “fair use” that user may be liable for copyright infringement, This institution reserves the right to refuse to accept a copying order if, in its judgment, fulfillment
    [Show full text]
  • Draft Revised Optical Transport Networks & Technologies
    INTERNATIONAL TELECOMMUNICATION UNION STUDY GROUP 15 TELECOMMUNICATION TD 107 Rev.2(PLEN/15) STANDARDIZATION SECTOR STUDY PERIOD 2013-2016 English only Original: English Question(s): 3/15 1-12 July 2013 TD Source: Rapporteur Q3/15 Title: Draft Revised Optical Transport Networks & Technologies Standardization Work Plan, Issue 17 This TD includes the draft of Revised Optical Transport Networks & Technologies Standardization Work Plan, Issue 17. Contact: Yoshinori Koike Tel: +81-422-59-6723 NTT Corporation Fax: +81-422-59-3493 Japan Email: [email protected] Attention: This is not a publication made available to the public, but an internal ITU-T Document intended only for use by the Member States of ITU, by ITU-T Sector Members and Associates, and their respective staff and collaborators in their ITU related work. It shall not be made available to, and used by, any other persons or entities without the prior written consent of ITU-T. - 2 - TD 107 (PLEN/15) Optical Transport Networks & Technologies Standardization Work Plan Issue 167, September July 20123 1. General Optical and other Transport Networks & Technologies Standardization Work Plan is a living document. It may be updated even between meetings. The latest version can be found at the following URL. http://www.itu.int/ITU-T/studygroups/com15/otn/ Proposed modifications and comments should be sent to: Yoshinori Koike [email protected] Tel. +81 422 59 6723 2. Introduction Today's global communications world has many different definitions for Optical and other Transport networks and many different technologies that support them. This has resulted in a number of different Study Groups within the ITU-T, e.g.
    [Show full text]
  • Getting Physical with Ethernet
    ETHERNET GETTING PHYSICAL STANDARDS • The Importance of Standards • Standards are necessary in almost every business and public service entity. For example, before 1904, fire hose couplings in the United States were not standard, which meant a fire department in one community could not help in another community. The transmission of electric current was not standardized until the end of the nineteenth century, so customers had to choose between Thomas Edison’s direct current (DC) and George Westinghouse’s alternating current (AC). IEEE 802 STANDARD • IEEE 802 is a family of IEEE standards dealing with local area networks and metropolitan area networks. • More specifically, the IEEE 802 standards are restricted to networks carrying variable-size packets. By contrast, in cell relay networks data is transmitted in short, uniformly sized units called cells. Isochronous , where data is transmitted as a steady stream of octets, or groups of octets, at regular time intervals, are also out of the scope of this standard. The number 802 was simply the next free number IEEE could assign,[1] though “802” is sometimes associated with the date the first meeting was held — February 1980. • The IEEE 802 family of standards is maintained by the IEEE 802 LAN/MAN Standards Committee (LMSC). The most widely used standards are for the Ethernet family, Token Ring, Wireless LAN, Bridging and Virtual Bridged LANs. An individual working group provides the focus for each area. Name Description Note IEEE 802.1 Higher Layer LAN Protocols (Bridging) active IEEE 802.2
    [Show full text]
  • Optical Transport Networks & Technologies Standardization Work
    Optical Transport Networks & Technologies Standardization Work Plan Issue 24, February 2018 GENERAL ........................................................................................................................... 3 PART 1: STATUS REPORTS AS OF JANUARY 2018 ...................................................... 4 1 HIGHLIGHT OF ITU-T SG15 ........................................................................................ 4 2 REPORTS FROM OTHER ORGANIZATIONS ............................................................ 4 PART 2: STANDARD WORK PLAN ................................................................................... 8 1 INTRODUCTION TO PART 2 ...................................................................................... 8 2 SCOPE ......................................................................................................................... 8 3 ABBREVIATIONS ........................................................................................................ 8 4 DEFINITIONS AND DESCRIPTIONS .......................................................................... 9 4.1 Optical and other Transport Networks & Technologies (OTNT) ....................................................... 9 4.2 Optical Transport Network (OTN) (largely revised in 09/2016 reflecting B100G) ............................ 9 4.2.1 FlexE in OIF (updated in June-2017) .......................................................................................... 11 4.3 Support for mobile networks (reference to ITU-R M2375 added
    [Show full text]
  • Ethernet (IEEE 802.3)
    Computer Networking MAC Addresses, Ethernet & Wi-Fi Lecturers: Antonio Carzaniga Silvia Santini Assistants: Ali Fattaholmanan Theodore Jepsen USI Lugano, December 7, 2018 Changelog ▪ V1: December 7, 2018 ▪ V2: March 1, 2017 ▪ Changes to the «tentative schedule» of the lecture 2 Last time, on December 5, 2018… 3 What about today? ▪Link-layer addresses ▪Ethernet (IEEE 802.3) ▪Wi-Fi (IEEE 802.11) 4 Link-layer addresses 5 Image source: https://divansm.co/letter-to-santa-north-pole-address/letter-to-santa-north-pole-address-fresh-day-18-santa-s-letters/ Network adapters (aka: Network interfaces) ▪A network adapter is a piece of hardware that connects a computer to a network ▪Hosts often have multiple network adapters ▪ Type ipconfig /all on a command window to see your computer’s adapters 6 Image source: [Kurose 2013 Network adapters: Examples “A 1990s Ethernet network interface controller that connects to the motherboard via the now-obsolete ISA bus. This combination card features both a BNC connector (left) for use in (now obsolete) 10BASE2 networks and an 8P8C connector (right) for use in 10BASE-T networks.” https://en.wikipedia.org/wiki/Network_interface_controller TL-WN851ND - WLAN PCI card 802.11n/g/b 300Mbps - TP-Link https://tinyurl.com/yamo62z9 7 Network adapters: Addresses ▪Each adapter has an own link-layer address ▪ Usually burned into ROM ▪Hosts with multiple adapters have thus multiple link- layer addresses ▪A link-layer address is often referred to also as physical address, LAN address or, more commonly, MAC address 8 Format of a MAC address ▪There exist different MAC address formats, the one we consider here is the EUI-48, used in Ethernet and Wi-Fi ▪6 bytes, thus 248 possible addresses ▪ i.e., 281’474’976’710’656 ▪ i.e., 281* 1012 (trillions) Image source: By Inductiveload, modified/corrected by Kju - SVG drawing based on PNG uploaded by User:Vtraveller.
    [Show full text]
  • Network Working Group A. Clemm Internet-Draft J
    Network Working Group A. Clemm Internet-Draft J. Medved Intended status: Experimental E. Voit Expires: September 22, 2013 Cisco Systems March 21, 2013 Mounting YANG-Defined Information from Remote Datastores draft-clemm-netmod-mount-00 Abstract This document introduces a new capability that allows YANG datastores to reference and incorporate information from remote datastores. This is accomplished using a new YANG data model that allows to define and manage datastore mount points that reference data nodes in remote datastores. The data model includes a set of YANG extensions for the purposes of declaring such mount points. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 22, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document.
    [Show full text]
  • IEEE Plenary - Lajolla, CA RPRSG Meeting Minutes July 11-13 2000
    IEEE Plenary - LaJolla, CA RPRSG Meeting Minutes July 11-13 2000 7/11/2000 8:43AM 30 attendees Presentations may be found at: http://www.ieee802.org/rprsg/public/july_plenary/index.html ACTION items in text Motion#1- The RPRSG voting rules amended to require: 1) 75% approval vote for technical issues 2) 50% +1 approval vote for procedural issues Motion: Harry Peng Second:Raj Sharma Yes:20 No:0 Minutes will be approved 8/12/2000 Presentation - Performance Metrics IEEE 802 RPRSG Khaled Amer Discussion - Ring Restoration performance metric will be added Ring performance stability with traffic flow changes Define Ingress/Egress access connection Bit Rate and Traffic characteristics Can Egress rate be below ring rate? Which mechanism? Simulation scenarios should be included ingress=egress traffic ports Change Bit rate to data rate in presentation Define L2/L1 mapping for consistency (mapping delay, etc.) Define L1 data rate - SONET vs. GigE Define L1 model ( packetization delay) metrics Sharing of model source code discussion Presentation - IPR(Intellectual Property Rights) issues Gary Robinson Presentation - Assessment of Scalable Coherent Interface Jason Fan Presentation - Resilient Packet Ring 5 Criteria (Compatibility) BJ Lee Discussion - Ethernet (SNAP encapsulation) and LLC over MAC sublayer correction Page 5- SRP TTL field 8 bits 802.1D compatibility (transparent bridging) and jumbo frame support Compatibility discussion tabled until PAR discussion Decision not to preclude 802.1D bridging Presentation - IEEE 802 Compatibility Considerations
    [Show full text]