One document matched: draft-martinelli-ccamp-wson-iv-encode-01.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 RFC6566 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6566.xml">
<!ENTITY I-D.ietf-ccamp-rwa-info SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-ccamp-rwa-info-14.xml">
<!ENTITY I-D.ietf-ccamp-general-constraint-encode SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-ccamp-general-constraint-encode-08.xml">
<!ENTITY I-D.martinelli-ccamp-wson-iv-info SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-martinelli-ccamp-wson-iv-info-00.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 -->
<?rfc comments="yesy" ?>
<!-- end of list of popular I-D processing instructions -->
<rfc category="std" docName="draft-martinelli-ccamp-wson-iv-encode-01" 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="Encoding WSON Info Model with Impairments">
Encoding for WSON Information Model with Impairments Validation.
</title>
<!-- add 'role="editor"' below for the editors if appropriate -->
<!-- Another author who claims to be an editor -->
<author fullname="Giovanni Martinelli" initials="G.M."
surname="Martinelli" role="editor">
<organization>Cisco</organization>
<address>
<postal>
<street>via Philips 12</street>
<city>Monza</city>
<region></region>
<code>20900</code>
<country>Italy</country>
</postal>
<phone>+39 039 2092044</phone>
<email>giomarti@cisco.com</email>
</address>
</author>
<author fullname="Moustafa Kattan" initials="M.K."
surname="Kattan">
<organization>Cisco</organization>
<address>
<postal>
<street></street>
<city>DUBAI</city>
<region></region>
<code>500321</code>
<country>UNITED ARAB EMIRATES</country>
</postal>
<phone></phone>
<email>mkattan@cisco.com</email>
</address>
</author>
<author fullname="Gabriele M. Galimberti" initials="G.M.G."
surname="Galimberti">
<organization>Cisco</organization>
<address>
<postal>
<street>Via Philips,12</street>
<city>Monza</city>
<code>20900</code>
<country>Italy</country>
</postal>
<phone>+39 039 2091462</phone>
<email>ggalimbe@cisco.com</email>
</address>
</author>
<author fullname="Andrea Zanardi" initials="A. Z." surname="Zanardi" role="editor">
<organization>CREATE-NET</organization>
<address>
<postal>
<street>via alla Cascata 56 C, Povo</street>
<code>38100</code>
<city>Trento</city>
<country>Italy</country>
</postal>
<email>andrea.zanardi@create-net.org</email>
</address>
</author>
<date year="2013" />
<!-- 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 -->
<area>Routing</area>
<workgroup>CCAMP</workgroup>
<!-- WG name at the upperleft corner of the doc,
IETF is fine for individual submissions.
If this element is not present, the default is "Network Working Group",
which is used by the RFC Editor as a nod to the history of the IETF. -->
<keyword>GMPLS WSON Optical Impairments</keyword>
<!-- Keywords will be incorporated into HTML output
files in a meta tag but they have no effect on text or nroff
output. If you submit your draft to the RFC Editor, the
keywords will be used for the search engine. -->
<abstract>
<t>
This document defines proper encoding for the Information Model to
support Impairment-Aware (IA)
Routing and Wavelength
Assignment (RWA) function. This operation might be required in
Wavelength Switched Optical Networks (WSON) that already support RWA, encoding defined
here goes in addition to available WSON encoding and it is fully compatible with it.
</t>
<t>
As the information model, the encoding is independent from control plane architectures and
protocol implementations. Its definitions must be reused in related protocol extensions.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>
In case of WSON where optical impairments plays a significant role, the framework document
<xref target="RFC6566"/> defines related control plane architectural options for an Impairment Aware
routing and wavelength assignment (IA-RWA). This document provides a suitable encoding for the
related WSON Impairment Information Model defined <xref target="I-D.martinelli-ccamp-wson-iv-info"/>.
</t>
<t>
This document directly refers to ITU recommendations <xref target="ITU.G680"/> and
<xref target="ITU.G697"/> as already detailed in the information model.
</t>
<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>
<section title="Encoding">
<section anchor="optical_param_tlv" title="Optical Parameter">
<t>
The OPTICAL_PARAM is defined as a sub TLV object.
</t>
<figure align="left">
<artwork align="left"><![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| Reserved | ParamSource | ParamID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Variance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
<t>
The following flags are defined:
<list style="empty">
<t>S. Standard bit. With S=1 indentify ITU set of parameters, S=0
identify other set of parameters.
</t>
</list>
</t>
<t>
With the flag S=1 the following parameters are defined:
<list style="empty">
<t> ParamSource.
Where this parameter was defined. Currently only <xref target="ITU.G697"/>
has defined this with value 1.
</t>
<t> ParamID.
Parameter identifier according to the source. <xref target="ITU.G697"/> table V.3
defines the following identifiers:
<list style="empty">
<t>1. Total Power (dBm)</t>
<t>2. Channel Power (dBm) </t>
<t>3. Reserved (Defined in <xref target="ITU.G697"/> but not used)</t>
<t>4. Reserved (Defined in <xref target="ITU.G697"/> but not used)</t>
<t>5. OSNR (db)</t>
<t>6. Q Factor (a pure number)</t>
<t>7. PMD (ps)</t>
<t>8. Residual Chromatic Dispersion (ps/nm)</t>
</list>
</t>
<t> Value.
Value for the parameter. As defined by <xref target="ITU.G697"/> is a
32 bit IEEE floating point number.
</t>
<t> Variance.
Variance for the parameter, a
32 bit IEEE floating point number.
</t>
</list>
</t>
</section> <!-- END OF "Optical Parameter" -->
<section title="Impairment Vector">
<t>
This sub-TLV is a list of optical parameters and they MAY be grouped by
wavelength dependency. To This purpose an optional Label Set sub-TLV is
added as a first sub-TLV.
</t>
<figure align="left">
<artwork align="left"><![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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|W| Reserved | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label Set |
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Param sub-TLV(s) |
: |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
<t>
Where:
<list style="empty">
<t> W. Wavelength Dependency flag.
With W=1 there is be a Label Set sub-TLV
which details to which set of wavelenghs the list of parameters is
applicable.
</t>
<t>
Length, the lenght of this TLV [EDITOR NOTE: may become numbers of
parameters? length will be already within TLV header].
</t>
<t>
The Label Set object is defined in
<xref target="I-D.ietf-ccamp-general-constraint-encode"/> Section 2.1.
Likely an inclusive range will be the only option required by the Action
defined in the Label Set.
</t>
<t>
Optical Param sub-TLV(s) a list of Object as defined in
<xref target="optical_param_tlv"/>.
</t>
</list>
</t>
</section> <!-- END of "Impairment Vector" -->
<section title="Impairment Matrix">
<t>
As defined by the <xref target="I-D.martinelli-ccamp-wson-iv-info"/> the
Impairment Matrix follow the same structure
as the Connectivity Matrix.
</t>
<figure align="left"><artwork align="left">
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Connectivity | MatrixID | Reserved |W|N|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Set A #1 |
: : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Set B #1 |
: : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Impairment Vector sub-TLV(s) |
: : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Link Set pairs and Optical Parameters |
: : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure>
<t>
Where:
<list style="empty">
<t>
Connectivity: value MUST be 2 for the Impairment Matrix (Values 0 and 1 are
already defined by <xref target="I-D.ietf-ccamp-general-constraint-encode"/>.
</t>
<t>
MatrixID: matrix identifier, the scope of this integer number is shared with
<xref target="I-D.ietf-ccamp-rwa-info"/>.
</t>
<t>
N: Node scope flags. With this flag set there's no Link Set information but only
a list of optical parameters TLVs that apply to the whole optical node.
</t>
<t>
W: Wavelength Dependency Matrix [EDITOR NOTE: to evaluate vs a the
flag at vector/parameter level.].
</t>
</list>
</t>
<t>
The usage of multiple matrixes with Connectivity type equal to 2 (Impairment Matrix)
MIGHT be used to grup optical parameters by connectivity. For example, if subset of parameters
apply to the whole node connectivity, a unique matrix with flag N=1 is used. At the same
some other subset of parameters apply only to some LinkSet pairs, a specific
Impairment Matrix will be added.
</t>
</section> <!-- END OF "Impairment Matrix" -->
</section> <!-- END OF "Encoding" -->
<section anchor="Acknowledgements" title="Acknowledgements">
<t>TBD</t>
</section>
<!-- Possibly a 'Contributors' section ... -->
<section anchor="IANA" title="IANA Considerations">
<t>
This document does not contain any IANA request.
</t>
</section>
<section anchor="Security" title="Security Considerations">
<t>All drafts are required to have a security considerations section.
See <xref target="RFC3552">RFC 3552</xref> for a guide.</t>
</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"?-->
&RFC2119;
<reference anchor="ITU.G680">
<front>
<title>
Physical transfer functions of optical network
elements
</title>
<author>
<organization>International Telecommunications Union</organization>
</author>
<date month="July" year="2007"/>
</front>
<seriesInfo name="ITU-T" value="Recommendation G.680"/>
</reference>
<reference anchor="ITU.G697">
<front>
<title>
Optical monitoring for dense wavelength division multiplexing systems
</title>
<author>
<organization>International Telecommunications Union</organization>
</author>
<date month="February" year="2012"/>
</front>
<seriesInfo name="ITU-T" value="Recommendation G.697"/>
</reference>
</references>
<references title="Informative References">
<!-- Here we use entities that we defined at the beginning. -->
&RFC3552;
&I-D.narten-iana-considerations-rfc2434bis;
<!-- A reference written by by an organization not a person. -->
&RFC6566;
&I-D.ietf-ccamp-rwa-info;
&I-D.ietf-ccamp-general-constraint-encode;
&I-D.martinelli-ccamp-wson-iv-info;
</references>
<!-- Change Log
v00 2006-03-15 EBD Initial version
v01 2006-04-03 EBD Moved PI location back to position 1 -
v3.1 of XMLmind is better with them at this location.
v02 2007-03-07 AH removed extraneous nested_list attribute,
other minor corrections
v03 2007-03-09 EBD Added comments on null IANA sections and fixed heading capitalization.
Modified comments around figure to reflect non-implementation of
figure indent control. Put in reference using anchor="DOMINATION".
Fixed up the date specification comments to reflect current truth.
v04 2007-03-09 AH Major changes: shortened discussion of PIs,
added discussion of rfc include.
v05 2007-03-10 EBD Added preamble to C program example to tell about ABNF and alternative
images. Removed meta-characters from comments (causes problems). -->
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 06:10:13 |