One document matched: draft-eb-ccamp-ospf-wson-impairments-02.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
There has to be one entity for each item to be referenced.
An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC3552 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552.xml">
<!ENTITY I-D.narten-iana-considerations-rfc2434bis SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.narten-iana-considerations-rfc2434bis.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
(Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="exp" docName="draft-eb-ccamp-ospf-wson-impairments-02"
ipr="trust200902">
<!-- category values: std, bcp, info, exp, and historic
ipr values: full3667, noModification3667, noDerivatives3667
you can add the attributes updates="NNNN" and obsoletes="NNNN"
they will automatically be output with "(if approved)" -->
<!-- ***** FRONT MATTER ***** -->
<front>
<!-- The abbreviated title is used in the page header - it is only necessary if the
full title is longer than 39 characters -->
<title abbrev="OSPF Ext for WSON impairments">OSPF Extensions for Wavelength Switched Optical Networks (WSON) with Impairments</title>
<!-- add 'role="editor"' below for the editors if appropriate -->
<!-- Another author who claims to be an editor -->
<author fullname="Elisa Bellagamba" initials="E.B." role="editor"
surname="Bellagamba">
<organization>Ericsson</organization>
<address>
<postal>
<street>Farogatan 6</street>
<!-- Reorder these if your country does things differently -->
<city>Stockholm</city>
<region></region>
<code>164 40</code>
<country>Sweden</country>
</postal>
<phone></phone>
<email>elisa.bellagamba@ericsson.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Giulio Bottari" initials="G.B."
surname="Bottari">
<organization>Ericsson</organization>
<address>
<postal>
<street>via Moruzzi</street>
<!-- Reorder these if your country does things differently -->
<city>Pisa</city>
<region></region>
<code>56 100</code>
<country>Italy</country>
</postal>
<phone></phone>
<email>giulio.bottari@ericsson.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Francesco Fondelli" initials="F.F."
surname="Fondelli">
<organization>Ericsson</organization>
<address>
<postal>
<street>via Moruzzi</street>
<!-- Reorder these if your country does things differently -->
<city>Pisa</city>
<region></region>
<code>56 100</code>
<country>Italy</country>
</postal>
<phone></phone>
<email>francesco.fondelli@ericsson.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<!-- If the month and year are both specified and are the current ones, xml2rfc will fill
in the current day for you. If only the current year is specified, xml2rfc will fill
in the current day and month for you. If the year is not the current one, it is
necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the
purpose of calculating the expiry date). With drafts it is normally sufficient to
specify just the year. -->
<!-- Meta-data Declarations -->
<date day="27" month="December" year="2010" />
<area>Routing</area>
<workgroup>CCAMP Working Group</workgroup>
<keyword>OSPF</keyword>
<keyword>WSON</keyword>
<keyword>CCAMP</keyword>
<abstract>
<t>This document specifies OSPF extensions to carry information about physical
impairments. This information set is required for the feasibility assessment
of the lightpath to be established across an optical switched network controlled
by GMPLS.</t>
<t>The document intent is both disseminating experimental results carried out within
Ericsson Research and provide an initial input for further OSPF extensions in
CCAMP IETF group.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t></t>
<t></t>
<section title="Contributing Authors">
<t>The editors gratefully acknowledge the precious contributions of Benoit Tremblay
and Andras Kern.</t>
</section>
<section title ="Requirements Language">
<t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <xref
target="RFC2119">RFC 2119</xref>.
</t>
</section>
<section title="Background">
<!--EB Inserire dei paragrafi per le nuove references? [WSON frame e' poi cosi importante?]-->
<t>Wavelength Switched Optical Networks [WSON-Frame] is an ongoing activity in
IETF's CCAMP and PCE working group which is currently addressing both
the Routing and Wavelength Assignment (RWA) constraint and the physical
impairments (PI) in optical networks.</t>
<t>According to the current work in IETF, the optical parameters are not
advertised by OSPF protocol and they must be retrieved in a different way.
The typical approach is to consider the worst case values
("end of life" values) and to perform path computation in leveraging
this data. This brings to a very conservative routing and prevents any sort of
dynamic wavelength provisioning and recovery (i.e. recovery/rerouting is not
possible).</t>
<t>A fast way to have a snapshot of the physical status of the network
would be of paramount importance in WSON networks and would allow a dynamic
on-line PCE both centralized (i.e. in NMS) or distributed
(i.e. in each ingress node).</t>
<t>It is worth to be noted that the physical impairments addressed
in this document is a subset of all the possible parameters. The choice is bounded
to a particular PCE computation and therefore the OSPF could be further enriched
with an additional set of parameters whenever it is needed by the usage of
a different PCE.</t>
</section>
</section>
<section title="OSPF Extensions">
<section title="Operation overview">
<t>The network architecture considered in this document is based
on a centralized or distributed PCE positioning. The PCE computes
the working and recovery paths based on known network characteristics
and has the task to assess the feasibility of the computed paths.</t>
<t>Details on the physical validation service are out of the scope
of this document</t>
<t><!--EB Maybe we should reference the fromula somewhere-->
The Path Computation is completed taking into account the following
groups of parameters:</t>
<t><list>
<t>- the parameters of the optical interfaces at the far ends of the path;</t>
<t>- the parameters of the network nodes involved in the propagation
of the optical signal;</t>
<t>- the fiber spans where the signal is carried.</t>
</list></t>
<t>Moreover, two different kind of strategies can be taken into account:</t>
<t><list>
<t>- aggregated parameters distribution;</t>
<t>- sparse parameter distribution.</t>
</list></t>
<t>Each TE link in the network is described by OSPF with a TE LSA
(as described in [RFC3630]) containing a Link TLV. This object is named TE
Link LSA and comprises a certain number of sub-objects (sub-TLVs).
Each of these sub-objects describes some of the characteristics of the
TE link.</t>
<t>The sub-TLVs described in the following paragraphs are intended to be inserted
in the TE LSA, in the Link TLV.</t>
<t>Below, an example showing a possible TLVs tree is provided.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LSA age | Options | 10 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 | Instance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Advertising Router |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LS Checksum | LS Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (2)(Link) | Length (196) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type (Imp.Spec)(TBD)(IANA)| Length (192) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (Transm.)(1)(IANA) | Length (36) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ payload ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (Rec.)(2)(IANA) | Length (28) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ payload ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (Ampl.)(4)(IANA) | Length (32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ payload ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (DCM)(5)(IANA) | Length (28) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ payload ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (Link Imp.)(6)(IANA) | Length (64) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ payload ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
</section>
<section title="Impairment Specification sub TLV">
<t>The "Impairment Specification sub TLV" is depicted below.</t>
<t>
<figure>
<artwork><![CDATA[
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type (Imp.Spec)(TBD)(IANA)| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ payload ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>The "Impairment Specification sub TLV" is located in the Link TLV and
groups together the following s-s-TLVs:</t>
<t><list>
<t>- "Transmitter Characteristics" s-s-TLV</t>
<t>- "Receiver Characteristics" s-s-TLV</t>
<t>- "Amplifier Characteristics" s-s-TLV</t>
<t>- "Dispersion Compensation Module" s-s-TLV</t>
<t>- "Link Impairment" s-s-TLV</t>
</list></t>
</section>
<section title="Parameters of the optical interfaces at the far ends of the path">
<t>The parameters characterizing the node optical interfaces are the
"Receiver" and "Transmitter" parameters.</t>
<section title="Transmitter Characteristics sub-sub TLV">
<t>The "Transmitter Characteristics" sub-sub TLV is included in the
"Impairment Specifications" sub-TLV.</t>
<t>The "Transmitter Characteristics" sub-sub TLV is depicted below.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (Transm.)(1)(IANA) | Length (36) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| System Operating Wavelength Range |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| System Central Wavelength |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Channel Spacing |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bit Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extinction Ratio |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Duty Cycle |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Relative Intensity Noise |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Launch OSNR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>The System Operating Wavelength Range indicates the frequency range centered on the Central Wavelength and in measured in nm. Refer to [G.959.1] for further details.</t>
<t>The System Central Wavelength is also indicated with the acronym lambda_m and in measured in nm. Refer to [G.959.1] for further details.</t>
<t>The Channel Spacing is also indicated with the acronym delta_lambda and in masured in nm. Refer to [G.959.1] for further details.</t>
<t>The Bit Rate also indicated with the acronym R and in measured in Gpbs.</t>
<t>The Extinction Ratio is also indicated with the acronym E_r and is measured in dB. Refer to [G.959.1] for further details.</t>
<t>The Duty Cycle is also indicated with the acronym D_C and is measured in %.</t>
<t>The Relative Intensity Noise also indicated with the acronym RIN and in measured in [Db/Hz].</t>
<t>The Launch OSNR (Optical Signal to Noise Ratio) is also indicated with the acronym OSNR_in and in measured in Db.</t>
</section>
<section title="Receiver Characteristics sub-sub TLV">
<t>The "Receiver Characteristics" sub-sub TLV is included in the
"Impairment Specifications" sub-TLV.</t>
<t>The "Receiver Characteristics" sub-sub TLV together is depicted below.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (Receiv.)(2)(IANA) | Length (28) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sensitivity |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Overload |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transimpedance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Electrical Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FEC Gain |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>The Sensitivity is also indicated with the acronym S and in measured in dB_m. Refer to [G.959.1] for further details.</t>
<t>The Overload is also indicated with the acronym O_l and in measured in dB_m. Refer to [G.959.1] for further details.</t>
<t>The Transimpedance is also indicated with the acronym T_r and in measured in Ohm.</t>
<t>The Electrical Bandwidthis also indicated with the acronym B_e and in measured in GHz.</t>
<t>The Optical Bandwidth is also indicated with the acronym B_o and in measured in GHz.</t>
<t>The FEC Gain is also indicated with the acronym G_fec and in measured in dB.</t>
</section>
</section>
<section title="Parameters of the network nodes involved
in the propagation of the optical signal">
<t>The parameters characterizing the transit nodes are mainly
the amplifier parameters.</t>
<section title="Amplifier sub-sub TLV with aggregated parameters">
<t>In this strategy, the physical description of the network
is given using several sub-sets of homogeneous elements: types of amplifier,
types of fibers, types of dispersion compensator and so on.</t>
<t>This strategy assumes that the PCE is aware of the parameters
associated to each type of element.</t>
<!--
<t>The following set of amplifiers is defined.</t>
<texttable align="center" anchor="table_MH" suppress-title="false"
title="">
<ttcol align="center">Amplifier Set</ttcol>
<c>MH_EDFA_DSA_22/20</c>
<c>MH_EDFA_DSA_29/20</c>
<c>MH_EDFA_SSA_22/20</c>
<c>MH_EDFA_SSA_29/20</c>
<c>MH_EDFA_DSA_22/18</c>
<c>MH_EDFA_SSA_22/18</c>
</texttable>
-->
<!-- EB TOGLIERLI. Visto che adesso non compaiono, la gente si potrebbe chiedere
perche' non usiamo questo approccio anche per gli altri moduli -->
<t>In this case is sufficient to distribute, in the routing protocol,
a string containing the amplifier type because the Traffic Engineering Database is aware of
the parameters associated to the type itself.</t>
<!-- EB Cosa e' la PLDE? Photonic Link Design Engine, sostituito con TED (non la stessa cosa, ma piu' generico)-->
<t>The "Amplifier Characteristics" with aggregated parameters
sub-sub TLV is included in the
"Impairment Specifications" sub-TLV.</t>
<t>The "Amplifier Characteristics" sub-sub TLV is depicted below.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (Ampl.)(3)(IANA) | Length (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Amplifier Set Name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
</section>
<section title="Amplifier Characteristics sub-sub TLV with sparse parameters">
<t>In this strategy, the physical description of the network is given
using a complete enumeration of the parameters. This method can be used
when there is not a predefined list of elements or when the involved
element is not included in the predefined set.</t>
<!-- EB problema della codifica della stringa (vedi commenti francesco) -->
<t>The "Amplifier Characteristics" with sparse parameters
sub-sub TLV is included in the "Impairment Specifications"
sub-TLV.</t>
<t>The "Amplifier Characteristics" sub-sub TLV is depicted below.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (Ampl.)(4)(IANA) | Length (32) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multichanel Gain Variation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Multichanel Gain Tilt |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Total Received Power |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Total Launched Power |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Noise Figure |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Polarization Mode Dispersion |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Polarization Dependent Loss |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>The Multichanel Gain Variation is also indicated with the acronym GV and in measured in dB.</t>
<t>The Multichanel Gain Tilt is also indicated with the acronym GT and in measured in dB.</t>
<t>The Total Received Power is also indicated with the acronym P_rx and in measured in dB_m.</t>
<t>The Total Launched Power is also indicated with the acronym P_tx and in measured in dB_m.</t>
<t>The Noise Figure is also indicated with the acronym NF and in measured in dB.</t>
<t>The Polarization Mode Dispersion is also indicated with the acronym PMD and in measured in ps.</t>
<t>The Polarization Dependent Loss is also indicated with the acronym PDL and in measured in dB.</t>
</section>
<section title="Dispersion Compensation Module sub-sub TLV">
<t>The "Dispersion Compensation Module" sub-sub TLV is depicted below.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (DCM)(5)(IANA) | Length (28) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Chromatic Dispersion |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dispersion Slope |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dispersion Tolerance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Slope Tolerance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Polarization Mode Dispersion |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Polarization Dependent Loss |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>The Chromatic Dispersion is also indicated with the acronym D_DCM and in measured in ps/nm*km.</t>
<t>The Dispersion Slope is also indicated with the acronym S_DCM and in measured in ps/nm^2.</t>
<t>The Dispersion Tolerance is also indicated with the acronym delta_DCM and in measured in ps/nm.</t>
<t>The Slope Tolerance is also indicated with the acronym sigma_DCM and in measured in ps/nm^2.</t>
<t>The Polarization Mode Dispersion is also indicated with the acronym PMD_DCM and in measured in ps.</t>
<t>The Polarization Dependent Loss is also indicated with the acronym PDL_DCM and in measured in dB.</t>
</section>
</section>
<section title="Fiber Span">
<t>The fiber span is connected to the network element (NE) ports.
NE ports that share common characteristics can be bundled to form a
TE Link. One TE Link is
seen as a bundle of ports/fibers and its capacity in terms of available
channels is the union of the available channels associated to the single ports.
Each physical port in the NE represents a link that is
associated to a given TE link.</t>
<section title="Link impairment sub-sub-TLV">
<t>The first parameter associated with a link is a local identifier
that can univocally identify it: Link ID.</t>
<t>The "Link impairment" sub-sub TLV is included in the
"Impairment Specifications" sub-TLV.</t>
<t>It is worth to be noted that more than one Link impairment sub-TLV
can comprise more than one Link Impairment sub-sub-TLV, depending on the number
of link boundled in a TE-link.</t>
<!-- EB togliere questa frase? Inoltre, aggiungere un capitolo con una possibile
strategia di accorpamento (boundling)-->
<t>The "Fiber Span Characteristics" sub-sub TLV together with its inner
TLVs is depicted below.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-Type (Link Imp.)(6)(IANA) | Length (64) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S-s-s-Type (1)(IANA) | Length (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length of Span |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Attenuation Coefficient |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Chromatic Dispersion |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dispersion Slope |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dispersion Uncertainty |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Slope Uncertainty |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PMD coefficient |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Effective Area |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Non Linear Refractive |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Raman Coefficient |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Connector Attenuation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Splice Attenuation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Span Margin |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<texttable align="center" anchor="table_example" suppress-title="false"
title="">
<ttcol align="left">"Link id" s-s-s-TLV type</ttcol>
<ttcol align="left">Value</ttcol>
<ttcol align="left">TLV Length (Bytes)</ttcol>
<c>1</c>
<c>Unnum. Link Id</c>
<c>8</c>
<c>2</c>
<c>IPv4 Link Id</c>
<c>8</c>
<c>3</c>
<c>IPv6 Link Id</c>
<c>20</c>
</texttable>
<t>The Length of Span is also indicated with the acronym L_si and in measured in Km.</t>
<t>The Attenuation Coefficient is also indicated with the acronym alpha and in measured in dB/Km.</t>
<t>The Chromatic Dispersion is also indicated with the acronym D and in measured in ps*(nm*km).</t>
<t>The Dispersion Slope is also indicated with the acronym S and in measured in ps*(nm^2*km).</t>
<t>The Dispersion Uncertainty is also indicated with the acronym delta and in measured in ps*(nm*km).</t>
<t>The Slope Uncertainty is also indicated with the acronym sigma and in measured in ps*(nm^2*km).</t>
<t>The PMD coefficient is also indicated with the acronym PDM and in measured in ps/Km^0,5..</t>
<t>The Effective Area is also indicated with the acronym A_E and in measured in microm^2.</t>
<t>The Non Linear Refractive is also indicated with the acronym n_2 and in measured in microm^2/W.</t>
<t>The Raman Coefficient is also indicated with the acronym g_R and in measured in m/W.</t>
<t>The Connector Attenuation is also indicated with the acronym A_C and in measured in dB.</t>
<t>The Splice Attenuation is also indicated with the acronym alpha_S and in measured in dB.</t>
<t>The Span Margin is also indicated with the acronym SM and in measured in dB.</t>
<t>The "Link number sub-sub-sub-type" values can be
freely assigned. Following there ia a suggestion for such assignement:</t>
</section>
</section>
</section>
<!-- Possibly a 'Contributors' section ... -->
<section anchor="IANA" title="IANA Considerations">
<t>This document specifies the following new TLV types.</t>
<t> Sub TLVs types to be carried in the TE LSA, Link TLV:</t>
<t><list>
<t>- "Impairment Specifications" sub-TLV type: TBD.</t>
</list>
</t>
<t> Sub-sub TLV types to be carried in the "Impairment Specifications" sub-TLV:</t>
<t><list>
<t>- "Transmitter Characteristics" sub-sub-TLV type: 1</t>
<t>- "Receiver Characteristics" sub-sub-TLV type: 2</t>
<t>- "Amplifier Characteristics Aggregated Parameters" sub-sub-TLV type: 3</t>
<t>- "Amplifier Characteristics Sparse Parameters" sub-sub-TLV type: 4</t>
<t>- "Dispersion Compensator Module" sub-sub-TLV type: 5</t>
<t>- "Link Impairment" sub-sub-TLV type: 6</t>
</list> </t>
</section>
<section anchor="Security" title="Security Considerations">
</section>
</middle>
<!-- *****BACK MATTER ***** -->
<back>
<!-- References split into informative and normative -->
<!-- There are 2 ways to insert reference entries from the citation libraries:
1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
(for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")
Both are cited textually in the same manner: by using xref elements.
If you use the PI option, xml2rfc will, by default, try to find included files in the same
directory as the including file. You can also define the XML_LIBRARY environment variable
with a value containing a set of directories to search. These can be either in the local
filing system or remote ones accessed by http (http://domain/dir/... ).-->
<references title="Normative References">
<!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
<?rfc include="reference.RFC.2119"?>
<?rfc include="reference.RFC.3630"?>
<?rfc include="reference.RFC.4201"?>
<reference anchor="WSON-Encode"
target="draft-ietf-ccamp-rwa-wson-encode">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Framework for GMPLS
and PCE Control of Wavelength Switched Optical Networks</title>
<author initials="G" surname="Bernstein">
<organization></organization>
</author>
<author initials="Y" surname="Lee">
<organization></organization>
</author>
<author initials="D" surname="Li">
<organization></organization>
</author>
<author initials="W" surname="Imajuku">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="WSON-FWK"
target="draft-ietf-ccamp-rwa-wson-framework">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Framework for GMPLS and PCE Control of Wavelength Switched Optical Networks (WSON)</title>
<author initials="Y" surname="Lee">
<organization></organization>
</author>
<author initials="G" surname="Bernstein">
<organization></organization>
</author>
<author initials="W" surname="Imajuku">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="WSON IMP"
target="draft-ietf-ccamp-wson-impairments">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>A Framework for the Control of Wavelength Switched
Optical Networks (WSON) with Impairments</title>
<author initials="Y" surname="Lee">
<organization></organization>
</author>
<author initials="G" surname="Bernstein">
<organization></organization>
</author>
<author initials="D" surname="Li">
<organization></organization>
</author>
<author initials="G" surname="Martinelli">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="PCE-WSON"
target="draft-ietf-pce-wson-routing-wavelength">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>PCEP Requirements for WSON Routing and Wavelength Assignment</title>
<author initials="Y" surname="Lee">
<organization></organization>
</author>
<author initials="G" surname="Bernstein">
<organization></organization>
</author>
<author initials="T" surname="Takeda">
<organization></organization>
</author>
<author initials="T" surname="Tsuritani">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.4258"?>
<?rfc include="reference.RFC.4652"?>
<reference anchor="G.959.1"
target="itu.int/itudoc/itu-t/aap/sg15aap/history/g9591/g9591.html">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Optical Transport Network Physical Layer Interfaces</title>
<author initials="" surname="">
<organization></organization>
</author>
<date year=""/>
</front>
</reference>
<reference anchor="WSON-Frame"
target="draft-ietf-ccamp-wavelength-switched-
framework">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Framework for GMPLS
and PCE Control of Wavelength Switched Optical Networks</title>
<author initials="G" surname="Bernstein">
<organization></organization>
</author>
<author initials="Y" surname="Lee">
<organization></organization>
</author>
<author initials="W" surname="Imajuku">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="ASON-Routing"
target="draft-ietf-ccamp-gmpls-ason-routing-ospf">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>OSPFv2 Routing Protocols Extensions for ASON Routing</title>
<author initials="D" surname="Papadimitriou">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
</references>
<section anchor="app-additional" title="Additional Stuff">
<t>This becomes an Appendix.</t>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 06:49:29 |