Debian Codegraph @

rfc6456.html

raw
1 <pre>Internet Engineering Task Force (IETF) H. Li
2 Request for Comments: 6456 R. Zheng
3 Category: Informational Huawei Technologies
4 ISSN: 2070-1721 A. Farrel
5 Old Dog Consulting
6 November 2011
7
8
9 <span class="h1">Multi-Segment Pseudowires in Passive Optical Networks</span>
10
11 Abstract
12
13 This document describes the application of MPLS multi-segment
14 pseudowires (MS-PWs) in a dual-technology environment comprising a
15 Passive Optical Network (PON) and an MPLS Packet Switched Network
16 (PSN).
17
18 PON technology may be used in mobile backhaul networks to support the
19 end segments closest to the aggregation devices. In these cases,
20 there may be a very large number of pseudowire (PW) Terminating
21 Provider Edge (T-PE) nodes. The MPLS control plane could be used to
22 provision these end segments, but support for the necessary protocols
23 would complicate the management of the T-PEs and would significantly
24 increase their expense. Alternatively, static, or management plane,
25 configuration could be used to configure the end segments, but the
26 very large number of such segments in a PON places a very heavy
27 burden on the network manager.
28
29 This document describes how to set up the end segment of an end-to-
30 end MPLS PW over a Gigabit-capable Passive Optical Network (G-PON) or
31 10 Gigabit-capable Passive Optical Network (XG-PON) using the G-PON
32 and XG-PON management protocol, Optical Network Termination
33 Management and Control Interface (OMCI). This simplifies and speeds
34 up PW provisioning compared with manual configuration.
35
36 This document also shows how an MS-PW may be constructed from an end
37 segment supported over a PON, and switched to one or more segments
38 supported over an MPLS PSN.
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Li, et al. Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
55
56
57 Status of This Memo
58
59 This document is not an Internet Standards Track specification; it is
60 published for informational purposes.
61
62 This document is a product of the Internet Engineering Task Force
63 (IETF). It represents the consensus of the IETF community. It has
64 received public review and has been approved for publication by the
65 Internet Engineering Steering Group (IESG). Not all documents
66 approved by the IESG are a candidate for any level of Internet
67 Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
68
69 Information about the current status of this document, any errata,
70 and how to provide feedback on it may be obtained at
71 <a href="http://www.rfc-editor.org/info/rfc6456">http://www.rfc-editor.org/info/rfc6456</a>.
72
73 Copyright Notice
74
75 Copyright (c) 2011 IETF Trust and the persons identified as the
76 document authors. All rights reserved.
77
78 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
79 Provisions Relating to IETF Documents
80 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
81 publication of this document. Please review these documents
82 carefully, as they describe your rights and restrictions with respect
83 to this document. Code Components extracted from this document must
84 include Simplified BSD License text as described in Section 4.e of
85 the Trust Legal Provisions and are provided without warranty as
86 described in the Simplified BSD License.
87
88 Table of Contents
89
90 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
91 <a href="#section-2">2</a>. Terminology for G-PON/XG-PON ....................................<a href="#page-5">5</a>
92 <a href="#section-3">3</a>. Multi-Segment Pseudowire over PON Network Reference Model .......<a href="#page-6">6</a>
93 <a href="#section-4">4</a>. Label Provisioning for Pseudowires over PON .....................<a href="#page-9">9</a>
94 <a href="#section-5">5</a>. Security Considerations .........................................<a href="#page-9">9</a>
95 <a href="#section-6">6</a>. References .....................................................<a href="#page-10">10</a>
96 <a href="#section-6.1">6.1</a>. Normative References ......................................<a href="#page-10">10</a>
97 <a href="#section-6.2">6.2</a>. Informative References ....................................<a href="#page-11">11</a>
98
99 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
100
101 The use of PWs in Packet Switched Networks (PSNs) is defined in
102 [<a href="./rfc3985" title="&quot;Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture&quot;">RFC3985</a>]. This architecture is extended in [<a href="./rfc5659" title="&quot;An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge&quot;">RFC5659</a>] for multi-
103 segment pseudowires (MS-PWs) satisfying the requirements in
104 [<a href="./rfc5254" title="&quot;Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)&quot;">RFC5254</a>]. More detail on MS-PWs is provided in [<a href="./rfc6073" title="&quot;Segmented Pseudowire&quot;">RFC6073</a>].
105
106
107
108 <span class="grey">Li, et al. Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
111
112
113 An MS-PW is a useful technology for certain applications where there
114 is an aggregation of paths toward a common point in the network,
115 e.g., mobile backhaul; the segments can be aggregated within tunnels
116 between PW switching points thus improving scalability and reducing
117 the number of control plane adjacencies where a control plane is
118 used.
119
120 Segments of an MS-PW in a PSN can be set up using manual provisioning
121 (static PWs) or using a dynamic control plane such as the Label
122 Distribution Protocol (LDP) [<a href="./rfc5036" title="&quot;LDP Specification&quot;">RFC5036</a>] [<a href="./rfc4447" title="&quot;Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)&quot;">RFC4447</a>].
123
124 In many scenarios, in access and metro networks, a Passive Optical
125 Network (PON) provides longer distance, higher bandwidth, and better
126 economy than other technologies such as point-to-point Ethernet or
127 Digital Subscriber Line (DSL). Mobile backhaul with PON is already
128 being deployed.
129
130 Figure A depicts the physical infrastructure of an Optical
131 Distribution Network (ODN).
132
133 | |
134 |&lt;--Optical Distribution Network--&gt;|
135 | |
136 | branch main |
137 +-----+ fibers fiber
138 Base ------| | | |
139 Stations ------| ONU |\ | |
140 ------| | \ V |
141 +-----+ \ |
142 \ +----------+ |
143 +-----+ \| | | +-----+
144 Base ------| | | Optical | V | |
145 Stations ------| ONU |---------| Splitter |-------------| OLT |
146 ------| | /| | | |
147 +-----+ / +----------+ +-----+
148 /
149 +-----+ /
150 Base ------| |/
151 Stations ------| ONU |
152 ------| |
153 +-----+
154
155 Figure A: Typical PON System Architecture
156
157 In a PON, the Optical Network Unit (ONU) and Optical Line Termination
158 (OLT) are adjacent nodes connected by an Optical Distribution Network
159 (ODN), which consists of optical fibers and optical splitters in a
160 tree topology. The link between each ONU and OLT is simulated as a
161
162
163
164 <span class="grey">Li, et al. Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
167
168
169 point-to-point link, and there is no path redundancy between them.
170 The OLT resides in the central office, while ONUs reside in customer
171 premises. ONUs are deployed in huge numbers and so they are cost
172 sensitive. More information about ODNs can be found in [<a href="#ref-G.984.1" title="&quot;Gigabit-capable passive optical networks (GPON): General characteristics&quot;">G.984.1</a>].
173
174 In a mobile backhaul network, many 2G and 3G base stations still use
175 legacy interfaces such as Time-Division Multiplexing (TDM) and ATM.
176 Therefore, these native services must be carried across the PON
177 before they can be carried over the PSN using PWs. This document
178 describes how MS-PWs can be constructed with end segments that
179 operate over the PON and are switched to further segments operated
180 over the PSN. In this case, the base stations are connected by
181 access circuits (ACs) to the ONUs, which act as Terminating Provider
182 Edge (T-PE) nodes. The OLT is a Switching Provider Edge (S-PE).
183 This model is shown in Figure B.
184
185 Routing protocols and dynamic label distribution protocols such as
186 LDP would significantly increase the ONUs' cost and complexity as
187 they place requirements on both hardware and software. Besides the
188 coding and maintenance of these new protocols, a much more powerful
189 CPU and more memory are also necessary for them to run smoothly.
190
191 As there is no redundant path between each ONU and the OLT, routing
192 and path selection are not necessary in the PON. Therefore, static
193 provisioning of PW labels between ONUs and the OLT is simple and
194 preferred because it can greatly reduce the cost of an ONU that acts
195 as a T-PE. However, use of a Network Management System (NMS) to
196 provision PWs in a PON would require the network manager to configure
197 each ONU and to configure the OLT once for each PW. Since there may
198 be very many ONUs (and hence very many PWs) in a PON, this requires a
199 large amount of operational effort. Additionally, there is an issue
200 that the configuration of each PW at the OLT and ONU might be
201 inconsistent since these nodes are configured separately.
202
203 [<a id="ref-G.988">G.988</a>] defines the G-PON/XG-PON management protocol called the "ONT
204 Management and Control Interface (OMCI)". OMCI is an implementation
205 requirement for all G-PON/XG-PON systems. If OMCI is used to
206 configure PWs on an ONU, no upgrade to an ONU's hardware is required
207 and the extension to the OMCI implementation is negligible. This
208 provides a way of reducing the cost and complexity of provisioning
209 PWs in a G-PON/XG-PON.
210
211 This document shows how the two technologies (PON and PSN) can be
212 combined to provide an end-to-end multi-segment MPLS PW. The MPLS
213 PWs are also carried over the PON in MPLS Label Switched Path (LSP)
214 tunnels. There is an MPLS LSP tunnel in each direction between each
215 ONU and the OLT in a one-to-one relationship with the underlying G-
216 PON/XG-PON channel. The OLT and ONU perform penultimate hop popping
217
218
219
220 <span class="grey">Li, et al. Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
223
224
225 (PHP) [<a href="./rfc3031" title="&quot;Multiprotocol Label Switching Architecture&quot;">RFC3031</a>] on this single-hop LSP so no labels are used on the
226 wire for the MPLS LSP tunnel. There is no change to the operation of
227 MPLS PWs, and MPLS packets are carried by the G-PON link layer
228 according to ITU-T [<a href="#ref-G.984.3amd1">G.984.3amd1</a>] or XG-PON link layer according to
229 ITU-T [<a href="#ref-G.987.3" title="&quot;10-Gigabit-capable passive optical networks (XG- PON): Transmission convergence (TC) layer specification&quot;">G.987.3</a>].
230
231 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology for G-PON/XG-PON</span>
232
233 We defined the following terms derived from [<a href="#ref-G.987" title="&quot;10-Gigabit-capable passive optical network (XG- PON) systems: Definitions, abbreviations, and acronyms&quot;">G.987</a>]:
234
235 o Gigabit-capable Passive Optical Network (G-PON). A variant of the
236 Passive Optical Network (PON) access technology supporting
237 transmission rates in excess of 1 Gbit/s and based on the ITU-T
238 G.984.x series of Recommendations [<a href="#ref-G.984.1" title="&quot;Gigabit-capable passive optical networks (GPON): General characteristics&quot;">G.984.1</a>], [<a href="#ref-G.984.4amd2">G.984.4amd2</a>] and
239 [<a href="#ref-G.984.3amd1">G.984.3amd1</a>].
240
241 o G-PON Encapsulation Method (GEM). A data frame transport scheme
242 used in G-PON systems that is connection oriented and that
243 supports fragmentation of the user data frames into variable sized
244 transmission fragments.
245
246 o GEM port. An abstraction of the G-PON adaptation layer
247 representing a logical connection associated with a specific
248 client packet flow between the OLT and the ONU.
249
250 o 10-gigabit-capable Passive Optical Network (XG-PON): A PON system
251 supporting nominal transmission rates on the order of 10 Gbit/s in
252 at least one direction, and implementing the suite of protocols
253 specified in the ITU-T G.987.x series Recommendations.
254
255 o XG-PON encapsulation method (XGEM): A data frame transport scheme
256 used in XG PON systems that is connection oriented and that
257 supports fragmentation of user data frames into variable-sized
258 transmission fragments.
259
260 o XGEM port: An abstraction in the XG-PON transmission convergence
261 (XGTC) service adaptation sublayer representing a logical
262 connection associated with a specific client packet flow.
263
264 o Optical Distribution Network (ODN). In the PON context, a tree of
265 optical fibers in the access network, supplemented with power or
266 wavelength splitters, filters, or other passive optical devices.
267
268 o Optical Line Termination (OLT). A device that terminates the
269 common (root) endpoint of an ODN; implements a PON protocol, such
270 as that defined by ITU-T G.984 series; and adapts PON PDUs for
271 uplink communications over the provider service interface. The
272 OLT provides management and maintenance functions for the
273
274
275
276 <span class="grey">Li, et al. Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
279
280
281 subtended ODN and ONUs. In this document, the OLT is a network
282 element with multiple PON ports and uplinks that provide switching
283 capability to the PSN.
284
285 o Optical Network Termination (ONT). A single subscriber device
286 that terminates any one of the distributed (leaf) endpoints of an
287 ODN, implements a PON protocol, and adapts PON PDUs to subscriber
288 service interfaces. An ONT is a special case of an ONU.
289
290 o Optical Network Unit (ONU). A generic term denoting a device that
291 terminates any one of the distributed (leaf) endpoints of an ODN,
292 implements a PON protocol, and adapts PON PDUs to subscriber
293 service interfaces. In some contexts, an ONU implies a multiple
294 subscriber device. In this document, an ONU is a Provider Edge
295 (PE) node with one or more ACs that map to the service interfaces.
296 The ONU acts as a T-PE.
297
298 o ONT Management and Control Interface (OMCI). The management and
299 control channel between OLT and ONT in PON. The OMCI protocol
300 runs between the OLT Controller and the ONT Controller across a
301 GEM connection that is established at ONT initialization. The
302 OMCI protocol is asymmetric: the Controller in the OLT is the
303 master and the one in the ONT is the slave. A single OLT
304 Controller using multiple instances of the protocol over separate
305 control channels may control multiple ONTs. The OMCI protocol is
306 used to manage the ONT in areas of configuration, fault
307 management, performance, and security.
308
309 o Passive Optical Network (PON). An OLT connected, using an ODN, to
310 one or more ONUs or ONTs.
311
312 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Multi-Segment Pseudowire over PON Network Reference Model</span>
313
314 [<a id="ref-RFC5659">RFC5659</a>] provides several pseudowire emulation edge-to-edge (PWE3)
315 reference architectures for the multi-segment case. These are
316 general models extended from [<a href="./rfc3985" title="&quot;Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture&quot;">RFC3985</a>] to enable point-to-point
317 pseudowires through multiple PSN tunnels.
318
319 A G-PON/XG-PON consists of an OLT, an ODN, and multiple ONUs. The
320 ODN is actually a fiber tree that provides physical connections
321 between the OLT and the ONUs. G-PON/XG-PON has its own physical
322 layer and link layer. A GEM/XGEM port is a logical point-to-point
323 connection between the OLT and each ONU over GPON Transmission
324 Convergence (GTC) layer/XG-PON transmission convergence (XGTC) layer.
325 There can be more than one GEM/XGEM port between the OLT and an
326 individual ONU. Each GEM/XGEM port can be assigned different Quality
327 of Service (QoS) and bandwidth.
328
329
330
331
332 <span class="grey">Li, et al. Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
335
336
337 Figure B shows how the MS-PW architecture is applied to a network
338 comprising a PON and a PSN. The Terminating PE1 (TPE1) is an ONU and
339 the Switching PE1 (SPE1) is an OLT. One or more PWs run between the
340 ONU and the remote end system (TPE2) to provide service emulation
341 between Customer Edges (CEs) (CE1 and CE2).
342
343 In each of the PON and PSN, the PW segments are carried in PSN
344 tunnels. In the PSN, the tunnel is established and operated as
345 normal for PWs (see [<a href="./rfc3985" title="&quot;Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture&quot;">RFC3985</a>]). In the PON, the tunnel used is a
346 single-hop MPLS LSP tunnel so that the OLT and ONU are label edge
347 routers. The OLT and ONU make use of PHP on the MPLS LSP tunnel.
348 Since this is a single-hop LSP (there are no MPLS-capable nodes
349 between the OLT and ONU), this means that there is no MPLS
350 encapsulation for the MPLS LSP tunnel on the wire (that is, no label
351 or shim header is used). This results in the on-wire encapsulations
352 shown in Figure C.
353
354 Native |&lt;------Multi-Segment Pseudowire------&gt;| Native
355 Service | GEM/XGEM | Service
356 (AC) | |&lt;--Port--&gt;| | (AC)
357 | | | | | |
358 | | | PSN | PSN | |
359 | | |&lt;-Tunnel-&gt;| |&lt;-Tunnel-&gt;| | |
360 | V V V V V V |
361 | +----+ +-----+ +----+ |
362 +----+ | |TPE1|===========|S-PE1|==========|TPE2| | +----+
363 | |------|..... PW.Seg't1....X....PW.Seg't3.....|-------| |
364 | CE1| | | | | | | | | |CE2 |
365 | |------|..... PW.Seg't2....X....PW.Seg't4.....|-------| |
366 +----+ | | |===========| |==========| | | +----+
367 Base ^ +----+ +-----+ +----+ ^
368 Station | Provider Edge 1 ^ Provider Edge 2 |
369 | ONU | |
370 | PW switching point |
371 | OLT |
372 | |
373 |&lt;------------------ Emulated Service ---------------&gt;|
374
375 Figure B: MS-PW over PON Network Reference Model
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Li, et al. Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
391
392
393 Base ----AC-- TPE1--PW over PON--SPE1--PW over PSN--TPE2--AC------
394 Station
395 ---------- ----------
396 -------- |Packetized| |Packetized| --------
397 |Native | |Native | |Native | |Native |
398 |Service | |Service | |Service | |Service |
399 -------- |----------| |----------| --------
400 |Control | |Control |
401 |Word | |Word |
402 |----------| |----------|
403 |PW Label | |PW Label |
404 |----------| |----------|
405 |GEM/XGEM | |MPLS |
406 |----------| |Tunnel |
407 |GPON/XGPON| |Label |
408 |-Phy | | |
409 ---------- |----------|
410 |Link Layer|
411 |----------|
412 |Phy |
413 ----------
414 Figure C: On-Wire Data Encapsulations for MS-PWs
415
416 It should be noted that all PW segments are of the same technology,
417 which is packet encapsulated.
418
419 The use of the PW label enables multiple PWs to be multiplexed over a
420 single GEM/XGEM port within the MPLS LSP tunnel. This enables the
421 traffic for multiple base stations to be kept separate and allows
422 different services and separate ACs for a single base station to be
423 supported. Furthermore, the multiple ACs at an ONU can belong to
424 different native services.
425
426 At the same time, each ONU can support more than one GEM/XGEM port
427 (each supporting a single MPLS LSP tunnel) connecting it to the OLT.
428 This allows greater bandwidth and so more PWs. It may also be used
429 to provide a simple way to aggregate PWs intended to be routed across
430 different PSN tunnels in the core network, or even across different
431 core networks.
432
433 At present, Ethernet over GEM/XGEM is the dominant encapsulation in
434 G-PON/XG-PON. For fast deployment of MPLS over G-PON/XG-PON, putting
435 MPLS PWs over Ethernet over GEM/XGEM is an alternative way of
436 transporting MPLS PWs over G-PON/XG-PON with existing hardware.
437
438
439
440
441
442
443
444 <span class="grey">Li, et al. Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
447
448
449 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Label Provisioning for Pseudowires over PON</span>
450
451 For an MS-PW with a segment running over a PON, where the OLT acts as
452 an S-PE and the ONU as a T-PE, PW provisioning can be performed
453 through static configuration, e.g., from an NMS. However, in this
454 model, each ONU has to be configured as each PW is set up. The huge
455 number of ONUs (and PWs) makes this method quite forbidding.
456
457 The labor of provisioning static labels at the ONUs for PWs can be
458 significantly reduced by using a management protocol over PON. This
459 approach keeps the ONU simple by not requiring the implementation of
460 a new dynamic control protocol.
461
462 The usual management protocol in a G-PON/XG-PON system used to manage
463 and control ONUs is OMCI. It is used to perform all configuration of
464 the G-PON/XG-PON physical layer and data GTC/XGTC layer on ONUs. Per
465 [<a href="#ref-G.984.4amd2">G.984.4amd2</a>] and [<a href="#ref-G.988" title="&quot;ONU management and control interface (OMCI) specification&quot;">G.988</a>], OMCI can also be used to set up PWs and
466 the MPLS LSP Tunnels from ONUs to OLT. When using OMCI to provision
467 PWs in a G-PON/XG-PON, the network manager sends configuration
468 information to the OLT only. The OLT will select suitable PW labels
469 and send all PW and MPLS LSP tunnel parameters to the ONUs through
470 OMCI. The AC can be identified in the OMCI signaling so that the
471 network manager does not need to configure the PWs at each ONU.
472
473 OMCI supports the configuration of a number of PW types including
474 TDM, ATM, and Ethernet. The protocol can also be used to allow the
475 ONU to notify the OLT of the status of the AC.
476
477 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
478
479 This document describes a variation of a multi-segment pseudowire
480 running over an MPLS PSN, in which one (or both) of the MPLS PSNs
481 that provides connectivity between a T-PE and its associated S-PE is
482 replaced by a G-PON/XG-PON PSN. The security considerations that
483 apply to the PW itself [<a href="./rfc3985" title="&quot;Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture&quot;">RFC3985</a>] [<a href="./rfc4385" title="&quot;Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN&quot;">RFC4385</a>] are unchanged by this
484 change in PSN type. For further considerations of PW security, see
485 the security considerations section of the specific PW type being
486 deployed.
487
488 G-PON/XG-PON [<a href="#ref-G.987.3" title="&quot;10-Gigabit-capable passive optical networks (XG- PON): Transmission convergence (TC) layer specification&quot;">G.987.3</a>] [<a href="#ref-G.984.3amd1">G.984.3amd1</a>] includes security mechanisms
489 that are as good as those provided in a well-secured MPLS PSN. The
490 use of a G-PON/XG-PON PSN in place of an MPLS PSN therefore does not
491 increase the security risk of a multi-segment pseudowire.
492
493 Protecting against an attack at the physical or data link layer of
494 the PON is out of the scope of this document.
495
496
497
498
499
500 <span class="grey">Li, et al. Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
503
504
505 The MPLS control plane and management plane mechanisms are unchanged
506 by this document. This document introduces OMCI as a provisioning
507 mechanism that runs between the OLT Controller and the ONT Controller
508 across a GEM connection that is established at ONT initialization.
509 In other words, the protocol runs on an in-fiber control channel.
510 That means that injection and modification of OMCI messages would be
511 very hard (harder, for example, than injection or modification in an
512 MPLS Associated Channel Header (ACH) that has been accepted to
513 provide adequate security by isolation ([<a href="./rfc4385" title="&quot;Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN&quot;">RFC4385</a>] and [<a href="./rfc5586" title="&quot;MPLS Generic Associated Channel&quot;">RFC5586</a>]).
514
515 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
516
517 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
518
519 [<a id="ref-G.984.1">G.984.1</a>] ITU-T, "Gigabit-capable passive optical networks (GPON):
520 General characteristics", March 2008,
521 &lt;<a href="http://www.itu.int/rec/T-REC-G.984.1-200803-I">http://www.itu.int/rec/T-REC-G.984.1-200803-I</a>&gt;.
522
523 [<a id="ref-G.984.3amd1">G.984.3amd1</a>]
524 ITU-T, "Gigabit-capable Passive Optical Networks (G-PON):
525 Transmission convergence layer specification", February
526 2009, &lt;<a href="http://www.itu.int/rec/T-REC-">http://www.itu.int/rec/T-REC-</a>
527 G.984.3-200902-I!Amd1&gt;.
528
529 [<a id="ref-G.987">G.987</a>] ITU-T, "10-Gigabit-capable passive optical network (XG-
530 PON) systems: Definitions, abbreviations, and acronyms",
531 October 2010, &lt;<a href="http://www.itu.int/rec/T-REC-G.987-201010-I">http://www.itu.int/rec/T-REC-</a>
532 <a href="http://www.itu.int/rec/T-REC-G.987-201010-I">G.987-201010-I</a>&gt;.
533
534 [<a id="ref-G.987.3">G.987.3</a>] ITU-T, "10-Gigabit-capable passive optical networks (XG-
535 PON): Transmission convergence (TC) layer specification",
536 October 2010, &lt;<a href="http://www.itu.int/rec/T-REC-G.987.3-201010-I/en">http://www.itu.int/rec/T-REC-</a>
537 <a href="http://www.itu.int/rec/T-REC-G.987.3-201010-I/en">G.987.3-201010-I/en</a>&gt;.
538
539 [<a id="ref-G.988">G.988</a>] ITU-T, "ONU management and control interface (OMCI)
540 specification", October 2010, &lt;<a href="http://www.itu.int/rec/T-REC-G.988-201010-I">http://www.itu.int/rec/T-</a>
541 <a href="http://www.itu.int/rec/T-REC-G.988-201010-I">REC-G.988-201010-I</a>&gt;.
542
543 [<a id="ref-RFC3031">RFC3031</a>] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
544 Label Switching Architecture", <a href="./rfc3031">RFC 3031</a>, January 2001.
545
546 [<a id="ref-RFC3985">RFC3985</a>] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire Emulation
547 Edge-to-Edge (PWE3) Architecture", <a href="./rfc3985">RFC 3985</a>, March 2005.
548
549 [<a id="ref-RFC4385">RFC4385</a>] Bryant, S., Swallow, G., Martini, L., and D. McPherson,
550 "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word
551 for Use over an MPLS PSN", <a href="./rfc4385">RFC 4385</a>, February 2006.
552
553
554
555
556 <span class="grey">Li, et al. Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
559
560
561 [<a id="ref-RFC4447">RFC4447</a>] Martini, L., Ed., Rosen, E., El-Aawar, N., Smith, T., and
562 G. Heron, "Pseudowire Setup and Maintenance Using the
563 Label Distribution Protocol (LDP)", <a href="./rfc4447">RFC 4447</a>, April 2006.
564
565 [<a id="ref-RFC5036">RFC5036</a>] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed.,
566 "LDP Specification", <a href="./rfc5036">RFC 5036</a>, October 2007.
567
568 [<a id="ref-RFC5254">RFC5254</a>] Bitar, N., Ed., Bocci, M., Ed., and L. Martini, Ed.,
569 "Requirements for Multi-Segment Pseudowire Emulation
570 Edge-to-Edge (PWE3)", <a href="./rfc5254">RFC 5254</a>, October 2008.
571
572 [<a id="ref-RFC5586">RFC5586</a>] Bocci, M., Ed., Vigoureux, M., Ed., and S. Bryant, Ed.,
573 "MPLS Generic Associated Channel", <a href="./rfc5586">RFC 5586</a>, June 2009.
574
575 [<a id="ref-RFC5659">RFC5659</a>] Bocci, M. and S. Bryant, "An Architecture for
576 Multi-Segment Pseudowire Emulation Edge-to-Edge", <a href="./rfc5659">RFC</a>
577 <a href="./rfc5659">5659</a>, October 2009.
578
579 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
580
581 [<a id="ref-G.984.4amd2">G.984.4amd2</a>]
582 ITU-T, "Gigabit-capable passive optical networks (G-PON):
583 ONT management and control interface specification",
584 November 2009, &lt;<a href="http://www.itu.int/rec/T-REC-">http://www.itu.int/rec/T-REC-</a>
585 G.984.4-200911-I!Amd2&gt;.
586
587 [<a id="ref-RFC6073">RFC6073</a>] Martini, L., Metz, C., Nadeau, T., Bocci, M., and M.
588 Aissaoui, "Segmented Pseudowire", <a href="./rfc6073">RFC 6073</a>, January 2011.
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Li, et al. Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc6456">RFC 6456</a> Multi-Segment Pseudowires in PON November 2011</span>
615
616
617 Authors' Addresses
618
619 Hongyu Li
620 Huawei Technologies
621 Huawei Industrial Base
622 Shenzhen
623 China
624
625 EMail: [email protected]
626
627
628 Ruobin Zheng
629 Huawei Technologies
630 Huawei Industrial Base
631 Shenzhen
632 China
633
634 EMail: [email protected]
635
636
637 Adrian Farrel
638 Old Dog Consulting
639
640 EMail: [email protected]
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668 Li, et al. Informational [Page 12]
669 </pre>