idnits 2.17.1 draft-bryant-pwe3-terms-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 122 has weird spacing: '...Edge to att...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 2002) is 7833 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Pseudo-Wire Edge-to-Edge (PWE3) Working Group Stewart Bryant 2 Internet Draft Cisco Systems 3 Document: 4 Expires: May 2003 6 November 2002 8 PWE3 Common Terminology 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that other 17 groups may also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress". 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt The list of 26 Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Abstract 31 This document defines the terminology common to PWE3 drafts. 33 Table of Contents 35 Status of this Memo.......................................... 1 37 1. Introduction............................................. 3 39 2. Terminology.............................................. 3 41 3. IANA considerations...................................... 5 43 4. Security Considerations.................................. 5 45 1. Introduction 47 This document attempts to define the common terms used in PWE3. 48 Documents produced by the IETF PWE3 WG use this common terminology, 49 but may define additional terms unique to their technical area. 51 2. Terminology 53 Attachment Circuit The circuit or virtual circuit attaching 54 (AC) a CE to a PE. 56 Applicability Each PW service will have an Applicability 57 Statement (AS) Statement (AS) that describes the applicability 58 of PWs for that service. 60 CE-bound The traffic direction where PW-PDUs are 61 received on a PW via the PSN, processed 62 and then sent to the destination CE. 64 CE Signaling Messages sent and received by the CEs 65 control plane. It may be desirable or 66 even necessary for the PE to participate 67 in or monitor this signaling in order 68 to effectively emulate the service. 70 Customer Edge (CE) A device where one end of a service 71 originates and/or terminates. The CE is not 72 aware that it is using an emulated service 73 rather than a native service. 75 Forwarder (FWRD) A PE subsystem that selects the PW to use to 76 transmit a payload received on an AC. 78 Fragmentation The action of dividing a single PDU into 79 multiple PDUs before transmission with the 80 intent of the original PDU being reassembled 81 elsewhere in the network. Fragmentation may be 82 performed in order to allow sending of packets 83 of a larger size than the network MTU which 84 they will traverse. 86 Maximum transmission The packet size (excluding data link header) 87 unit (MTU) that an interface can transmit without 88 needing to fragment. 90 Native Service Processing of the data received by the PE 91 Processing (NSP) from the CE before presentation to the PW 92 for transmission across the core. 94 Packet Switched Within the context of PWE3, this is a 95 Network (PSN) network using IP or MPLS as the mechanism 96 for packet forwarding. 98 Protocol Data The unit of data output to, or received 99 Unit (PDU) from, the network by a protocol layer. 101 Provider Edge (PE) A device that provides PWE3 to a CE. 103 PE-bound The traffic direction where information 104 from a CE is adapted to a PW, and PW-PDUs 105 are sent into the PSN. 107 PE/PW Maintenance Used by the PEs to set up, maintain and 108 tear down the PW. It may be coupled with 109 CE Signaling in order to effectively manage 110 the PW. 112 Pseudo Wire (PW) A mechanism that carries the essential 113 elements of an emulated service from one PE 114 to one or more other PEs over a PSN. 116 PW End Service The interface between a PE and a CE. This 117 (PWES) can be a physical interface like a T1 or 118 Ethernet, or a virtual interface like a VC 119 or VLAN. 121 Pseudo Wire A mechanism that emulates the essential 122 Emulation Edge to attributes of service (such as a T1 leased 123 Edge (PWE3) line or frame relay) over a PSN. 125 Pseudo Wire PDU A PDU sent on the PW that contains all of 126 (PW-PDU) the data and control information necessary 127 to emulate the desired service. 129 PSN Tunnel A tunnel across a PSN inside which one or 130 more PWs can be carried. 132 PSN Tunnel Used to set up, maintain and tear down the 133 Signaling underlying PSN tunnel. 135 PW Demultiplexer Data-plane method of identifying a PW 136 terminating at a PE. 138 Time Domain Synchronous bit-streams at rates defined by 139 Multiplexing (TDM) G.702. 141 Tunnel A method of transparently carrying information 142 over a network. 144 3. IANA considerations 146 There are no IANA considerations for this document. 148 4. Security Considerations 150 The other documents produced by PWE3 will be manually checked to 151 ensure that they do not re-define any of these terms. 153 Editors' Addresses 155 Stewart Bryant 156 Cisco Systems, 157 4, The Square, 158 Stockley Park, 159 Uxbridge UB11 1BL, 160 United Kingdom. Email: stbryant@cisco.com 162 Full copyright statement 164 Copyright (C) The Internet Society (2002). 165 All Rights Reserved. 167 This document and translations of it may be copied and 168 furnished to others, and derivative works that comment 169 on or otherwise explain it or assist in its implementation 170 may be prepared, copied, published and distributed, in 171 whole or in part, without restriction of any kind, 172 provided that the above copyright notice and this 173 paragraph are included on all such copies and derivative works. 174 However, this document itself may not be modified in any way, 175 such as by removing the copyright notice or references to the 176 Internet Society or other Internet organizations, except as 177 needed for the purpose of developing Internet standards in 178 which case the procedures for copyrights defined in the 179 Internet Standards process must be followed, or as required to 180 translate it into languages other than English. 182 The limited permissions granted above are perpetual and will 183 not be revoked by the Internet Society or its successors or assigns. 185 This document and the information contained herein is provided 186 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 187 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 188 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 189 USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS 190 OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS