User Network Interface (UNI) Requirements and Framework

User Network Interface (UNI) Requirements and Framework

Technical Specification MEF 11 User Network Interface (UNI) Requirements and Framework November 2004 MEF 11 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is authorized to modify any of the information contained herein. UNI Requirements and Framework Disclaimer The information in this publication is freely available for reproduction and use by any recipient and is believed to be accurate as of its publication date. Such information is subject to change without notice and the Metro Ethernet Forum (MEF) is not responsible for any errors. 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 recipient or user of this document. The MEF is not responsible or liable for any modifications 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 implication or otherwise: (a) any express or implied license or right to or under any patent, copyright, trademark 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 contained 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. Implementation or use of specific Metro Ethernet standards or recommendations and MEF specifications will be voluntary, and no company shall be obliged to implement them by virtue of participation in the Metro Ethernet Forum. The MEF is a non-profit international organization accelerating industry cooperation on Metro Ethernet technology. The MEF does not, expressly or otherwise, endorse or promote any specific products or services. © The Metro Ethernet Forum 2005. All Rights Reserved. MEF 11 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 1 contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is authorized to modify any of the information contained herein. UNI Requirements and Framework Table of Contents ABSTRACT .......................................................................................................................................................................4 1. TERMINOLOGY (NORMATIVE) .........................................................................................................................4 2. SCOPE ........................................................................................................................................................................6 3. COMPLIANCE LEVELS .........................................................................................................................................6 4. UNI REFERENCE POINT .......................................................................................................................................7 5. UNI REFERENCE MODEL ....................................................................................................................................9 5.1 UNI DATA PLANE ................................................................................................................................................9 5.1.1 Ethernet Frames at the UNI ....................................................................................................................... 10 5.1.2 Tagging ...................................................................................................................................................... 10 5.1.3 Traffic Management ................................................................................................................................... 10 5.2 UNI CONTROL PLANE ........................................................................................................................................ 10 5.3 UNI MANAGEMENT PLANE ................................................................................................................................ 11 5.3.1 Provisioning and Static Service Discovery ................................................................................................ 11 5.3.2 Protection and Restoration ........................................................................................................................ 12 5.3.3 Operation, Administration and Maintenance (OAM) ................................................................................ 12 6. RELATIONSHIP TO FUNCTIONAL ELEMENTS IN THE MEN ARCHITECTURE ................................. 12 6.1 RELATIONSHIP TO TRAN LAYER(S) ................................................................................................................... 13 6.1.1 Ethernet PHY as a TRAN component in the ETH Access Link .................................................................. 13 6.1.2 TMF as a TRAN component in the ETH Access Link ................................................................................ 14 7. UNI TYPES .............................................................................................................................................................. 15 7.1 UNI TYPE 1 ........................................................................................................................................................ 15 7.2 UNI TYPE 2 ........................................................................................................................................................ 15 7.3 UNI TYPE 3 ........................................................................................................................................................ 16 8. UNI SERVICE ATTRIBUTES............................................................................................................................... 16 9. EVC SERVICE ATTRIBUTES ............................................................................................................................. 17 10. UNI REQUIREMENTS ...................................................................................................................................... 17 10.1 UNI TYPE 1 REQUIREMENTS .............................................................................................................................. 18 10.1.1 General UNI Type 1 Requirements ............................................................................................................ 18 MEF 11 © The Metro Ethernet Forum 2005. Any reproduction of this document, or any portion thereof, shall Page 2 contain the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this document is authorized to modify any of the information contained herein. UNI Requirements and Framework 10.1.2 UNI Type 1 Physical layer Requirements .................................................................................................. 18 10.1.3 UNI Type 1 Data Plane Requirements ....................................................................................................... 19 10.1.4 UNI Type 1 Management Plane Requirements .......................................................................................... 21 10.2 UNI TYPE 2 REQUIREMENTS .............................................................................................................................. 21 10.2.1 General 2.0 UNI Requirements .................................................................................................................. 21 10.2.2 UNI Type 2 Physical layer Requirements .................................................................................................. 22 10.2.3 UNI Type 2 Data Plane Requirements ....................................................................................................... 22 10.2.4 UNI Type 2 Management Plane Requirements .......................................................................................... 22 10.3 UNI TYPE 3 REQUIREMENTS .............................................................................................................................. 23 10.3.1 General 3.0 UNI Requirements .................................................................................................................. 23 10.3.2 UNI Type 3 Control Plane Requirements .................................................................................................. 23 11. REFERENCES .................................................................................................................................................... 23 APPENDIX A: UNI EXAMPLES .................................................................................................................................. 25 APPENDIX B: PHYSICAL

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    33 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us