rfc8363v1.xml   rfc8363.xml 
skipping to change at line 19 skipping to change at line 19
<!ENTITY RFC7580 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7580.xml"> <!ENTITY RFC7580 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7580.xml">
<!ENTITY RFC6205 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6205.xml"> <!ENTITY RFC6205 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6205.xml">
<!ENTITY RFC7699 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7699.xml"> <!ENTITY RFC7699 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7699.xml">
<!ENTITY RFC8258 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8258.xml"> <!ENTITY RFC8258 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8258.xml">
<!ENTITY RFC6163 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6163.xml"> <!ENTITY RFC6163 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6163.xml">
<!ENTITY RFC7792 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7792.xml"> <!ENTITY RFC7792 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7792.xml">
<!ENTITY RFC7698 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7698.xml"> <!ENTITY RFC7698 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7698.xml">
<!ENTITY RFC7688 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7688.xml"> <!ENTITY RFC7688 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7688.xml">
<!ENTITY RFC2328 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2328.xml"> <!ENTITY RFC2328 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2328.xml">
<!ENTITY RFC3630 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3630.xml"> <!ENTITY RFC3630 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3630.xml">
<!ENTITY RFC3471 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3471.xml">
<!ENTITY RFC6863 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6863.xml"> <!ENTITY RFC6863 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6863.xml">
]> ]>
<rfc submissionType="IETF" category="std" consensus="yes" number="8363"> <rfc submissionType="IETF" category="std" consensus="yes" number="8363">
<?rfc compact="yes"?> <?rfc compact="yes"?>
<?rfc text-list-symbols="o*+-"?> <?rfc text-list-symbols="o*+-"?>
<?rfc subcompact="no"?> <?rfc subcompact="no"?>
<?rfc sortrefs="no"?> <?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?> <?rfc symrefs="yes"?>
<?rfc toc="yes"?> <?rfc toc="yes"?>
<front> <front>
<title abbrev="GMPLS OSPF-TE for Flexi-Grid DWDM">GMPLS OSPF-TE Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks</title> <title abbrev="GMPLS OSPF-TE for Flexi-Grid DWDM">GMPLS OSPF-TE Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks</title>
<author fullname="Xian Zhang" initials="X." surname="Zhang"> <author fullname="Xian Zhang" initials="X." surname="Zhang">
<organization abbrev="Huawei">Huawei Technologies</organization> <organization abbrev="Huawei">Huawei Technologies</organization>
<address><email>zhang.xian@huawei.com</email> <address><email>zhang.xian@huawei.com</email>
</address> </address>
</author> </author>
skipping to change at line 59 skipping to change at line 60
</address> </address>
</author> </author>
<author fullname="Oscar Gonzalez de Dios" initials="O." surname="Gonzalez de Dios"> <author fullname="Oscar Gonzalez de Dios" initials="O." surname="Gonzalez de Dios">
<organization abbrev="Telefonica">Telefonica Investigacion y Desarrollo</organization> <organization abbrev="Telefonica">Telefonica Investigacion y Desarrollo</organization>
<address><postal><street>Emilio Vargas 6</street> <address><postal><street>Emilio Vargas 6</street>
<street>Madrid, 28045</street> <street>Madrid, 28045</street>
<street>Spain</street> <street>Spain</street>
</postal> </postal>
<phone>+34 913374013</phone> <phone>+34 913374013</phone>
<email>ogondio@tid.es</email> <email>oscar.gonzalezdedios@telefonica.com</email>
</address> </address>
</author> </author>
<author fullname="Daniele Ceccarelli" initials="D." surname="Ceccarelli"> <author fullname="Daniele Ceccarelli" initials="D." surname="Ceccarelli">
<organization>Ericsson</organization> <organization>Ericsson</organization>
<address><postal><street>Via A. Negrone 1/A</street> <address><postal><street>Via A. Negrone 1/A</street>
<street>Genova - Sestri Ponente</street> <street>Genova - Sestri Ponente</street>
<street>Italy</street> <street>Italy</street>
</postal> </postal>
<email>daniele.ceccarelli@ericsson.com</email> <email>daniele.ceccarelli@ericsson.com</email>
</address> </address>
</author> </author>
<date month="March" year="2018"/> <date month="March" year="2018"/>
<workgroup>CCAMP Working Group</workgroup> <workgroup>CCAMP Working Group</workgroup>
<!-- [rfced] Please insert any keywords (beyond those that appear in <abstract><t>The International Telecommunication Union Telecommunication
the title) for use on https://www.rfc-editor.org/search.
<keyword>example</keyword>
<!-- [rfced] Please clarify the "by defining" phrase in this sentence. Does
"set" apply to "channel spacings" as well as "nominal central
frequencies"?
Original:
The International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) has extended its Recommendations
G.694.1 and G.872 to include a new Dense Wavelength Division
Multiplexing (DWDM) grid by defining a set of nominal central
frequencies, channel spacings, and the concept of the "frequency
slot".
Perhaps (set includes nominal central frequencies and channel spacings):
The International Telecommunication Union Telecommunication
standardization sector (ITU-T) has extended its Recommendations
G.694.1 and G.872 to include a new Dense Wavelength Division
Multiplexing (DWDM) grid by defining the concept of the "frequency
slot" and a set of nominal central
frequencies and channel spacings.
Or (channel spacings separate from set of nominal central frequencies):
The International Telecommunication Union Telecommunication
standardization sector (ITU-T) has extended its Recommendations standardization sector (ITU-T) has extended its Recommendations
G.694.1 and G.872 to include a new Dense Wavelength Division G.694.1 and G.872 to include a new Dense Wavelength Division
Multiplexing (DWDM) grid by defining channel spacings, a set of nominal Multiplexing (DWDM) grid by defining channel spacings, a set of nominal
central frequencies, and the concept of the "frequency central frequencies, and the concept of the "frequency
slot". slot. Corresponding techniques for
<abstract><t> The International Telecommunication Union
Telecommunication standardization sector (ITU-T) has extended
its Recommendations G.694.1 and G.872 to include a new Dense
Wavelength Division Multiplexing (DWDM) grid by defining a set
of nominal central frequencies, channel spacings, and the
concept of the "frequency slot". Corresponding techniques for
data-plane connections are known as "flexi-grid".</t> data-plane connections are known as "flexi-grid".</t>
<t> <t>
Based on the characteristics of flexi-grid defined in G.694.1 and in RFCs Based on the characteristics of flexi-grid defined in G.694.1 and in RFCs
7698 and 7699, this document describes the Open Shortest Path First - Traffic Engineering (OSPF-TE) extensions in 7698 and 7699, this document describes the Open Shortest Path First - Traffic Engineering (OSPF-TE) extensions in
support of GMPLS control of networks that include devices that use support of GMPLS control of networks that include devices that use
the new flexible optical grid.</t> the new flexible optical grid.</t>
</abstract> </abstract>
</front> </front>
skipping to change at line 139 skipping to change at line 106
<xref target="G.694.1"/> defines the Dense Wavelength Division Multiplexing (DWDM) <xref target="G.694.1"/> defines the Dense Wavelength Division Multiplexing (DWDM)
frequency grids for Wavelength Division Multiplexing (WDM) frequency grids for Wavelength Division Multiplexing (WDM)
applications. A frequency grid is a reference set of frequencies applications. A frequency grid is a reference set of frequencies
used to denote allowed nominal central frequencies that may be used used to denote allowed nominal central frequencies that may be used
for defining applications. The channel spacing is the frequency for defining applications. The channel spacing is the frequency
spacing between two allowed nominal central frequencies. All of the spacing between two allowed nominal central frequencies. All of the
wavelengths on a fiber should use different central frequencies and wavelengths on a fiber should use different central frequencies and
occupy a fixed bandwidth of frequency.</t> occupy a fixed bandwidth of frequency.</t>
<t> <t>
Fixed-grid channel spacing ranges from one of 12.5 GHz, 25 GHz, 50 GHz, or
<!--[rfced] How may we clarify this range?
Original:
Fixed grid channel spacing ranges from 12.5 GHz, 25 GHz, 50 GHz, 100
GHz to integer multiples of 100 GHz.
Perhaps:
Fixed-grid channel spacing ranges from one of 12.5 GHz, 25 GHz, 50 GHz,
or 100 GHz to integer multiples of 100 GHz.
Fixed-grid channel spacing ranges from 12.5 GHz, 25 GHz, 50 GHz,
100 GHz to integer multiples of 100 GHz. But <xref 100 GHz to integer multiples of 100 GHz. But <xref
target="G.694.1"/> also defines a "flexible grid", also known as target="G.694.1"/> also defines a "flexible grid", also known as
"flexi-grid". The terms "frequency slot" (i.e., the frequency "flexi-grid". The terms "frequency slot" (i.e., the frequency
range allocated to a specific channel and unavailable to other range allocated to a specific channel and unavailable to other
channels within a flexible grid) and "slot width" (i.e., the full channels within a flexible grid) and "slot width" (i.e., the full
width of a frequency slot in a flexible grid) are used to define a width of a frequency slot in a flexible grid) are used to define a
flexible grid.</t> flexible grid.</t>
<t> <t>
<xref target="RFC7698"/> defines a framework and the associated control-plane <xref target="RFC7698"/> defines a framework and the associated control-plane
skipping to change at line 202 skipping to change at line 158
</t> </t>
</section> </section>
</section> </section>
<section title="Requirements for Flexi-Grid Routing" anchor="section-3"><t> <section title="Requirements for Flexi-Grid Routing" anchor="section-3"><t>
The architecture for establishing LSPs in a Spectrum Switched Optical The architecture for establishing LSPs in a Spectrum Switched Optical
Network (SSON) is described in <xref target="RFC7698"/>.</t> Network (SSON) is described in <xref target="RFC7698"/>.</t>
<t> <t>
A flexi-grid LSP occupies a specific frequency slot, i.e., a A flexi-grid LSP occupies one or multiple specific frequency slots.
frequency range. The process of computing a route and the allocation The process of computing a route and the allocation
of a frequency slot is referred to as "RSA" (Routing and Spectrum of a frequency slot is referred to as "RSA" (Routing and Spectrum
Assignment). <xref target="RFC7698"/> describes three types of architectural Assignment). <xref target="RFC7698"/> describes three types of architectural
approaches to RSA: combined RSA, separated RSA, and distributed SA. approaches to RSA: combined RSA, separated RSA, and routing and distributed SA. The first two approaches could be called "centralized SA"
<!--[rfced] RFC 7698 lists the following:
Combined RSA (R&SA)
Separated RSA (R+SA)
Routing and Distributed SA (R+DSA)
Should we globally update mentions of "distributed SA" to "routing and distributed SA"?
For example:
Original:
[RFC7698] describes three types of
architectural approaches to RSA: combined RSA, separated RSA, and
distributed SA.
Perhaps:
[RFC7698] describes three types of
architectural approaches to RSA: combined RSA, separated RSA, and
routing and distributed SA.
The first two approaches could be called "centralized SA"
because the spectrum (frequency slot) assignment is performed by a because the spectrum (frequency slot) assignment is performed by a
single entity before the signaling procedure.</t> single entity before the signaling procedure.</t>
<t> <t>
In the case of centralized SA, the assigned frequency slot is In the case of centralized SA, the assigned frequency slot is
specified in the RSVP-TE Path message during the signaling process. specified in the RSVP-TE Path message during the signaling process.
In the case of distributed SA, only the requested slot width of the In the case of routing and distributed SA, only the requested slot width of the
flexi-grid LSP is specified in the Path message, allowing the flexi-grid LSP is specified in the Path message, allowing the
involved network elements to select the frequency slot to be used.</t> involved network elements to select the frequency slot to be used.</t>
<t> <t>
If the capability of switching or converting the whole optical If the capability of switching or converting the whole optical
spectrum allocated to an optical spectrum LSP is not available at spectrum allocated to an optical spectrum LSP is not available at
nodes along the path of the LSP, the LSP is subject to the Optical nodes along the path of the LSP, the LSP is subject to the Optical
"Spectrum Continuity Constraint", as described in <xref target="RFC7698"/>.</t> "Spectrum Continuity Constraint", as described in <xref target="RFC7698"/>.</t>
<t> <t>
skipping to change at line 284 skipping to change at line 219
<t> <t>
<xref target="fig1"/> shows two adjacent frequency slots on a link. The highest <xref target="fig1"/> shows two adjacent frequency slots on a link. The highest
frequency of frequency slot 1 denoted by n=2 is the lowest frequency frequency of frequency slot 1 denoted by n=2 is the lowest frequency
of slot 2. In this example, it means that the frequency range from of slot 2. In this example, it means that the frequency range from
n=-2 to n=10 is unavailable to other flexi-grid LSPs. Available n=-2 to n=10 is unavailable to other flexi-grid LSPs. Available
central frequencies are advertised for m=1, which means that for an central frequencies are advertised for m=1, which means that for an
available central frequency n, the frequency slot from central available central frequency n, the frequency slot from central
frequency n-1 to central frequency n+1 is available.</t> frequency n-1 to central frequency n+1 is available.</t>
<t> <t>
Hence, in order to clearly show which LSPs can be supported and what Hence, in order to clearly show which frequency slots are available and can be used for LSP establishment and which
frequency slots are unavailable, the available frequency ranges are frequency slots are unavailable, the availability of frequency slots is
advertised by the routing protocol for the flexi-grid DWDM links. A advertised by the routing protocol for the flexi-grid DWDM links. A
set of non-overlapping available frequency ranges is disseminated in set of non-overlapping available frequency ranges is disseminated in
order to allow efficient resource management of flexi-grid DWDM links order to allow efficient resource management of flexi-grid DWDM links
and RSA procedures, which are described in Section 4.8 of <xref target="RFC7698"/>.</t> and RSA procedures, which are described in Section 4.8 of <xref target="RFC7698"/>.</t>
</section> </section>
<section title="Application Compliance Considerations" anchor="compliance"><t> <section title="Application Compliance Considerations" anchor="compliance"><t>
As described in <xref target="G.694.1"/>, devices or applications that make use of As described in <xref target="G.694.1"/>, devices or applications that make use of
the flexi-grid may not be capable of supporting every possible slot the flexi-grid may not be capable of supporting every possible slot
width or position (i.e., central frequency). In other words, width or position (i.e., central frequency). In other words,
applications or implementations may be defined where only a subset of applications or implementations may be defined where only a subset of
the possible slot widths and positions are required to be supported.</t> the possible slot widths and positions are required to be supported.</t>
<t> <t>For example, an application could be defined where the nominal
<!--[rfced] Juxtaposing the "where" and "and that" clauses here makes
this sentence difficult to parse. May we update as suggested?
Original:
For example, an application could be defined where the nominal
central frequency granularity is 12.5 GHz (by only requiring values
of n that are even) and that only requires slot widths as a multiple
of 25 GHz (by only requiring values of m that are even).
Perhaps:
For example, an application could be defined where the nominal
central frequency granularity is 12.5 GHz (by only requiring values central frequency granularity is 12.5 GHz (by only requiring values
of n that are even) and the same application only requires slot widths as a multiple of n that are even) and the same application only requires slot widths as a multiple
of 25 GHz (by only requiring values of m that are even). of 25 GHz (by only requiring values of m that are even).
For example, an application could be defined where the nominal </t>
central frequency granularity is 12.5 GHz (by only requiring values
of n that are even) and that only requires slot widths as a multiple
of 25 GHz (by only requiring values of m that are even).</t>
<t> <t>
Hence, in order to support all possible applications and Hence, in order to support all possible applications and
implementations, the following information SHOULD be advertised for a implementations, the following information SHOULD be advertised for a
flexi-grid DWDM link:</t> flexi-grid DWDM link:</t>
<t><list style="symbols"><t>Channel Spacing (C.S.): as defined in <xref target="RFC7699"/> for flexi-grid, is <t><list style="symbols"><t>Channel Spacing (C.S.): as defined in <xref target="RFC7699"/> for flexi-grid, is
set to 5 to denote 6.25 GHz.</t> set to 5 to denote 6.25 GHz.</t>
<t>Central frequency granularity: a multiplier of C.S.</t> <t>Central frequency granularity: a multiplier of C.S.</t>
skipping to change at line 383 skipping to change at line 302
Central F = 193.1 THz Central F = 193.1 THz
]]></artwork> ]]></artwork>
</figure> </figure>
<t> <t>
Unlike the fixed-grid DWDM links, on a flexi-grid DWDM link, the slot Unlike the fixed-grid DWDM links, on a flexi-grid DWDM link, the slot
width of the frequency slot is flexible, as described in <xref target="ranges"/>. width of the frequency slot is flexible, as described in <xref target="ranges"/>.
That is, the value of m in the following formula from <xref target="G.694.1"/> is That is, the value of m in the following formula from <xref target="G.694.1"/> is
uncertain before a frequency slot is actually allocated for a flexi-grid LSP.</t> uncertain before a frequency slot is actually allocated for a flexi-grid LSP.</t>
<t><list hangIndent="13" style="hanging"><t> <t><list hangIndent="13" style="hanging"><t>
Slot Width (GHz) = 12.5GHz * m</t> Slot Width (in GHz) = 12.5GHz * m</t>
</list> </list>
</t> </t>
<t> <t>
<!--[rfced] Please clarify this use of the "/" character. For this reason, the available frequency slots (or ranges) are advertised
for a flexi-grid DWDM link instead of the specific "wavelength"
Original: points that are sufficient for a fixed-grid link. Moreover, this
For this reason, the available frequency slot/ranges are advertised
for a flexi-grid DWDM link instead of the specific "wavelengths"
points that are sufficient for a fixed-grid link.
Perhaps:
For this reason, the available frequency slots or ranges are advertised
for a flexi-grid DWDM link instead of the specific "wavelength"
points that are sufficient for a fixed-grid link.
For this reason, the available frequency slot/ranges are advertised
for a flexi-grid DWDM link instead of the specific "wavelength"
points that are sufficient for a fixed-grid link. Moreover, this
advertisement is represented by the combination of central frequency advertisement is represented by the combination of central frequency
granularity and slot width granularity.</t> granularity and slot width granularity.</t>
</section> </section>
</section> </section>
<section title="Extensions" anchor="section-4"><t> <section title="Extensions" anchor="section-4"><t>
The network-connectivity topology The network-connectivity topology
constructed by the links and/or nodes and node capabilities are the same as constructed by the links and/or nodes and node capabilities are the same as
skipping to change at line 425 skipping to change at line 332
Section 6.2 of <xref target="RFC6163"/>). In the flexi-grid case, the available Section 6.2 of <xref target="RFC6163"/>). In the flexi-grid case, the available
frequency ranges, instead of the specific "wavelengths", are advertised frequency ranges, instead of the specific "wavelengths", are advertised
for the link. This section defines the GMPLS OSPF-TE extensions in for the link. This section defines the GMPLS OSPF-TE extensions in
support of advertising the available frequency ranges for flexi-grid support of advertising the available frequency ranges for flexi-grid
DWDM links.</t> DWDM links.</t>
<section title="Interface Switching Capability Descriptor (ISCD) Extensions for Flexi-Grid" anchor="flexi"><t> <section title="Interface Switching Capability Descriptor (ISCD) Extensions for Flexi-Grid" anchor="flexi"><t>
This section defines a new value for the Switching Capability field This section defines a new value for the Switching Capability field
of the ISCD with a value of 152 and type name of the ISCD with a value of 152 and type name
Flexi-Grid-LSC.</t> Flexi-Grid-LSC.</t>
<!-- [rfced] In the following, should "Type" be "Name"? Please review and let
us know if any updates are needed.
Current:
Value Type
- - - - - - - - - - -
152 Flexi-Grid-LSC
<figure><artwork><![CDATA[ <figure><artwork><![CDATA[
Value Type Value Name
----- -------------- ----- --------------
152 Flexi-Grid-LSC 152 Flexi-Grid-LSC
Switching Capability and Encoding values MUST be used as follows: Switching Capability and Encoding values MUST be used as follows:
Switching Capability = Flexi-Grid-LSC Switching Capability = Flexi-Grid-LSC
Encoding Type = lambda (as defined in [RFC3471]) Encoding Type = lambda (as defined in [RFC3471])
]]></artwork> ]]></artwork>
</figure> </figure>
skipping to change at line 461 skipping to change at line 360
<t> <t>
As the "Max LSP Bandwidth at priority x" (x from 0 to 7) fields in As the "Max LSP Bandwidth at priority x" (x from 0 to 7) fields in
the generic part of the ISCD the generic part of the ISCD
<xref target="RFC4203"/> are not meaningful for flexi-grid DWDM links, the values of <xref target="RFC4203"/> are not meaningful for flexi-grid DWDM links, the values of
these fields MUST be set to zero and MUST be ignored. The SCSI as defined below provides the these fields MUST be set to zero and MUST be ignored. The SCSI as defined below provides the
corresponding information for flexi-grid DWDM links.</t> corresponding information for flexi-grid DWDM links.</t>
<section title="Switching Capability-Specific Information (SCSI)" anchor="switch"><t> <section title="Switching Capability-Specific Information (SCSI)" anchor="switch"><t>
<xref target="RFC8258"/> defines a Generalized SCSI for the ISCD. This document <xref target="RFC8258"/> defines a Generalized SCSI for the ISCD. This document
defines the Frequency availability bitmap as a new type of the defines the Frequency Availability Bitmap as a new type of the
Generalized SCSI. The technology-specific part of the flexi-grid Generalized SCSI TLV. The technology-specific part of the flexi-grid
ISCD includes the available frequency-spectrum resource as well as ISCD includes the available frequency-spectrum resource as well as
the information regarding max slot widths per priority. the information regarding max slot widths per priority. The format of this
flexi-grid SCSI, the Frequency Availability Bitmap sub-TLV, is depicted in
<!-- [rfced] Should instances of "flex-grid" in these sentences be updated to
"flexi-grid"?
Original
The format of this flex-grid SCSI, the
frequency available bitmap TLV, is depicted in the following figure:
...
This document extends [RFC4203] and [RFC7580] to carry flex-grid
specific information in OSPF Opaque LSAs.
The format of this
flex-grid SCSI, the frequency availability bitmap TLV, is depicted in
the following figure:</t> the following figure:</t>
<!--[rfced] We have a few question about the use of the following:
frequency availability bitmap vs. Frequency availability bitmap
First, should the capitalization be consistent? If so, please let us know
which form is preferred. We question if initial caps would be appropriate
(i.e., Frequency Availability Bitmap").
Second, should the use of "TLV" or "sub-TLV" be made uniform (i.e., "frequency
availability bitmap TLV" or "frequency availability bitmap sub-TLV")?
Last, should either "TLV" or "sub-TLV" be added after "Frequency availability
bitmap" in this sentence?
Original (from updated file sent by Deborah Brungard):
[RFC8258] defines a Generalized SCSI for the ISCD. This document
defines the Frequency availability bitmap as a new type of the
Generalized SCSI.
<!-- [rfced] In Section 4.1.1, "Bit Map" (two words) is used for the name of
a field. We note that "bitmap" (one word) is used elsewhere in the
document. Should this field be updated to "Bitmap" (one word)
accordingly?
<!--[rfced] For the ease of the reader, should titles be added to figures in
the document that have no titles (i.e., the TLVs)? If so, please provide
the titles.
<figure><artwork><![CDATA[ <figure><artwork><![CDATA[
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 11 | Length | | Type = 11 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Priority | Reserved | | Priority | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Max Slot Width at Priority k | Unreserved Padding ~ ~ Max Slot Width at Priority k | Unreserved Padding ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| C.S. | Starting n | No. of Effective Bits | | C.S. | Starting n | No. of Effective Bits |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bit Map ... ~ | Bitmap ... ~
~ ... | padding bits ~ ~ ... | padding bits ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure> </figure>
<t> <t>
Type (16 bits): The type of this sub-TLV (11).</t> Type (16 bits): The type of this sub-TLV (11).</t>
<t> <t>
Length (16 bits): The length of the value field of this sub-TLV in Length (16 bits): The length of the value field of this sub-TLV in
octets.</t> octets.</t>
skipping to change at line 554 skipping to change at line 410
0.</t> 0.</t>
<t> <t>
Reserved: The Reserved field MUST be set to zero on transmission and MUST be Reserved: The Reserved field MUST be set to zero on transmission and MUST be
ignored on receipt.</t> ignored on receipt.</t>
<t> <t>
Max Slot Width at Priority k (16 bits): This field indicates maximal Max Slot Width at Priority k (16 bits): This field indicates maximal
frequency slot width supported at a particular priority level, up to frequency slot width supported at a particular priority level, up to
8. This field is set to max frequency slot width supported in the 8. This field is set to max frequency slot width supported in the
unit of 2*C.S., for a particular priority level. unit of 2*C.S., for a particular priority level. One field MUST be
present for each bit set in the Priority field, and each present field is ordered to
<!--[rfced] Please clarify the subject of the clause beginning with "and is":
Original:
One field MUST be
present for each bit set in the Priority field, and is ordered to
match the Priority field.
Perhaps:
One field MUST be
present for each bit set in the Priority field, and each field is ordered to
match the Priority field.
One field MUST be
present for each bit set in the Priority field, and is ordered to
match the Priority field. Fields MUST be present for priority levels match the Priority field. Fields MUST be present for priority levels
that are indicated in the Priority field.</t> that are indicated in the Priority field.</t>
<t> <t> Unreserved Padding (16 bits): The Padding field is used to
ensure the 32-bit alignment of Max Slot Width at Priority k. When
<!--[rfced] Should the field names in the following text be updated? We do k is an odd number, the Unreserved Padding field MUST be
not see a "Padding field" in the figure this text is describing. Also, included. When k is an even number, the Unreserved Padding field
should "Max Slot Width fields" be made "Max Slot Width at Priority k"? MUST be omitted. This field MUST be set to 0 and MUST be ignored on
receipt.
Original: </t>
Unreserved Padding (16 bits): The Padding field is used to
ensure the 32 bit alignment of Max Slot Width fields. When the
number of priorities is odd, the Unreserved Padding field MUST be
included.
Unreserved Padding (16 bits): The Padding field is used to ensure the
32-bit alignment of Max Slot Width fields. When the number of
priorities is odd, the Unreserved Padding field MUST be included.
When the number of priorities is even, the Unreserved Padding field MUST be
omitted. This field MUST be set to 0 and MUST be ignored on receipt.</t>
<t> <t>
C.S. (4 bits): As defined in <xref target="RFC7699"/>; it is currently set to 5.</t> C.S. (4 bits): As defined in <xref target="RFC7699"/>; it is currently set to 5.</t>
<!-- [rfced] We find "starting nominal central frequency point" difficult to <t>Starting n (16 bits): As defined in [RFC7699]. This value denotes
read. Does the suggested text below accurately convey the intended
meaning?
Original
Starting n (16 bits): as defined in [RFC7699] and this value denotes
the starting nominal central frequency point of the frequency
availability bitmap sub-TLV.
Perhaps
Starting n (16 bits): As defined in [RFC7699]. This value denotes
the starting point of the nominal central frequency of the frequency the starting point of the nominal central frequency of the frequency
availability bitmap sub-TLV. availability bitmap sub-TLV.
<t> </t>
Starting n (16 bits): As defined in <xref target="RFC7699"/>. This value denotes
the starting nominal central frequency point of the frequency availability bitmap sub-TLV.</t>
<t> <t>
No. of Effective Bits (12 bits): Indicates the number of effective No. of Effective Bits (12 bits): Indicates the number of effective
bits in the Bit Map field.</t> bits in the Bitmap field.</t>
<t>Bit Map (variable): Indicates whether or not a basic frequency slot, <t>Bitmap (variable): Indicates whether or not a basic frequency slot,
characterized by a nominal central frequency and a fixed m value of characterized by a nominal central frequency and a fixed m value of
1, is available for flexi-grid LSP setup. 1, is available for flexi-grid LSP setup. The first nominal
<!-- [rfced] We have updated this sentence as follows for clarity. Please
review and confirm that the updated text accurately conveys the intended
meaning.
Original
The first nominal
central frequency is the value of starting n and with the subsequent
ones implied by the position in the bitmap.
Perhaps
The first nominal
central frequency is the value of starting n; subsequent central frequency is the value of starting n; subsequent
nominal central frequencies are implied by the position in the bitmap. nominal central frequencies are implied by the position in the bitmap.
The first nominal
central frequency is the value of starting n; subsequent nominal central frequencies
are implied by the position in the bitmap.
Note that setting Note that setting
to 1 indicates that the corresponding central frequency is available to 1 indicates that the corresponding central frequency is available
for a flexi-grid LSP with m=1 and setting to 0 indicates the for a flexi-grid LSP with m=1 and setting to 0 indicates the
corresponding central frequency is unavailable. corresponding central frequency is unavailable.
Note that a Note that a
centralized SA process will need to extend this to high values of m centralized SA process will need to extend this to high values of m
by checking a sufficiently large number of consecutive basic frequency by checking a sufficiently large number of consecutive basic frequency
slots that are available. slots that are available.
</t> </t>
<t> <t>
padding bits (variable): Padded after the Bit Map to make it a padding bits (variable): Padded after the Bitmap to make it a
multiple of four bytes, if necessary. Padding bits MUST be set to 0 multiple of four bytes, if necessary. Padding bits MUST be set to 0
and MUST be ignored on receipt.</t> and MUST be ignored on receipt.</t>
<t> <t>
An example is provided in <xref target="scsi"/>.</t> An example is provided in <xref target="scsi"/>.</t>
</section> </section>
<section title="An SCSI Example" anchor="scsi"><t> <section title="An SCSI Example" anchor="scsi"><t>
<xref target="fig3"/> shows an example of the available frequency spectrum <xref target="fig3"/> shows an example of the available frequency spectrum
resource of a flexi-grid DWDM link.</t> resource of a flexi-grid DWDM link.</t>
<figure title="Flexi-Grid DWDM Link Example" anchor="fig3"><artwork><![CDATA[ <figure title="Flexi-Grid DWDM Link Example" anchor="fig3"><artwork><![CDATA[
-9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 -9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11
...+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--... ...+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--...
|--Available Frequency Range--| |--Available Frequency Range--|
]]></artwork> ]]></artwork>
</figure> </figure>
<!-- [rfced] Please clarify "as currently be standardized" here. (Note that
we used "-" (single dash) rather than the double dash in the text below because
the double dash is not allowed in XML comments.)
Original
The symbol "-" represents a central frequency granularity of 6.25 GHz,
as currently be standardized in [G.694.1].
Perhaps
The symbol "-" represents a central frequency granularity of 6.25 GHz,
which is currently standardized in [G.694.1].
<t> <t>
The symbol "+" represents the allowed nominal central frequency. The The symbol "+" represents the allowed nominal central frequency. The
symbol "--" represents a central frequency granularity of 6.25 GHz, symbol "--" represents a central frequency granularity of 6.25 GHz,
as currently be standardized in <xref target="G.694.1"/>. The number on the top of which is currently standardized in <xref target="G.694.1"/>. The number on the top of
the line represents the "n" in the frequency calculation formula the line represents the "n" in the frequency calculation formula
(193.1 + n * 0.00625). The nominal central frequency is 193.1 THz (193.1 + n * 0.00625). The nominal central frequency is 193.1 THz
when n equals zero.</t> when n equals zero.</t>
<t> <t>
In this example, it is assumed that the lowest nominal central In this example, it is assumed that the lowest nominal central
frequency supported is n=-9 and the highest is n=11. Note they frequency supported is n=-9 and the highest is n=11. Note they
cannot be used as a nominal central frequency for setting up an LSP, cannot be used as a nominal central frequency for setting up an LSP,
but merely as the way to express the supported frequency range. but merely as the way to express the supported frequency range.
Using the encoding defined in <xref target="switch"/>, the relevant fields to Using the encoding defined in <xref target="switch"/>, the relevant fields to
skipping to change at line 740 skipping to change at line 530
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Max Slot Width at Priority k | Unreserved Padding ~ ~ Max Slot Width at Priority k | Unreserved Padding ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | Starting n (-1) | No. of Effec. Bits(9)| | 5 | Starting n (-1) | No. of Effec. Bits(9)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|1|1|1|1|1|1|1|1| padding bits (0s) | |1|1|1|1|1|1|1|1|1| padding bits (0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure> </figure>
<!-- [rfced] Is it clear what "This" refers to here? Please review and let us <t> This encoding denotes that, other than the advertised
know if any updates are needed. available nominal central frequencies, the other nominal
central frequencies within the whole frequency range supported
Original by the link are not available for flexi-grid LSP setup.
This denotes that other than the advertised available nominal </t>
central frequencies, the other nominal central frequencies within
the whole frequency range supported by the link are not available
for flexi-grid LSP set up.
<t>
This denotes that other than the advertised available nominal central
frequencies, the other nominal central frequencies within the whole
frequency range supported by the link are not available for flexi-grid LSP setup.</t>
<t> <t>
If an LSP with slot width m equal to 1 is set up using this link, say If an LSP with slot width m equal to 1 is set up using this link, say
using n=-1, then the SCSI information is updated to be the using n=-1, then the SCSI information is updated to be the
following:</t> following:</t>
<figure><artwork><![CDATA[ <figure><artwork><![CDATA[
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at line 779 skipping to change at line 561
| 5 | Starting n (-1) | No. of Effec. Bits(9)| | 5 | Starting n (-1) | No. of Effec. Bits(9)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0|1|1|1|1|1|1|1| padding bits (0s) | |0|0|1|1|1|1|1|1|1| padding bits (0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure> </figure>
</section> </section>
</section> </section>
<section title="Extensions to the Port Label Restriction Sub-TLV" anchor="section-4.2"><t> <section title="Extensions to the Port Label Restrictions Field" anchor="section-4.2"><t>
As described in <xref target="compliance"/>, a port that supports flexi-grid may As described in <xref target="compliance"/>, a port that supports flexi-grid may
support only a restricted subset of the full flexible grid. support only a restricted subset of the full flexible grid. The Port
Label Restrictions field is defined in <xref target="RFC7579"/>. It can be used to
<!-- [rfced] Should the following be updated to "Port Label Restrictions"
(note the "s" at the end of "Restrictions") per RFC 7579? Also, should
"Sub-TLV" or "field" be used? We note that RFC 7579 uses "field".
Port Label Restriction Sub-TLV (in title of Section 4.2)
Port Label Restriction field (in text in Section 4.2)
The Port
Label Restriction field is defined in <xref target="RFC7579"/>. It can be used to
describe the label restrictions on a port and is carried in the top-level Link TLV as specified in <xref target="RFC7580"/>. A new restriction type, describe the label restrictions on a port and is carried in the top-level Link TLV as specified in <xref target="RFC7580"/>. A new restriction type,
the flexi-grid Restriction Type, is defined here to specify the the flexi-grid Restriction Type, is defined here to specify the
restrictions on a port to support flexi-grid.</t> restrictions on a port to support flexi-grid.</t>
<figure><artwork><![CDATA[ <figure><artwork><![CDATA[
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MatrixID | RstType = 5 | Switching Cap | Encoding | | MatrixID | RstType = 5 | Switching Cap | Encoding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at line 840 skipping to change at line 612
<t> <t>
C.F.G (Central Frequency Granularity, 8 bits): A positive integer. C.F.G (Central Frequency Granularity, 8 bits): A positive integer.
Its value indicates the multiple of C.S., in terms of central Its value indicates the multiple of C.S., in terms of central
frequency granularity.</t> frequency granularity.</t>
<t> <t>
S.W.G (Slot Width Granularity, 8 bits): A positive integer. Its S.W.G (Slot Width Granularity, 8 bits): A positive integer. Its
value indicates the multiple of 2*C.S., in terms of slot width value indicates the multiple of 2*C.S., in terms of slot width
granularity.</t> granularity.</t>
<!-- [rfced] Please clarify the parenthetical here. Is the meaning "(in GHz)"
or something else?
Original
Its value indicates
the multiple of 2*C.S. (GHz), in terms of the supported minimal slot
width.
<t> <t>
Min Slot Width (16 bits): A positive integer. Its value indicates Min Slot Width (16 bits): A positive integer. Its value indicates
the multiple of 2*C.S.&nbsp;(GHz), in terms of the supported minimal slot the multiple of 2*C.S.&nbsp;(in GHz), in terms of the supported minimal slot
width.</t> width.</t>
<t> <t>
Reserved: The Reserved field MUST be set to zero on transmission and SHOULD be Reserved: The Reserved field MUST be set to zero on transmission and SHOULD be
ignored on receipt.</t> ignored on receipt.</t>
</section> </section>
</section> </section>
skipping to change at line 882 skipping to change at line 646
<https://www.iana.org/assignments/ospf-traffic-eng-tlvs>? <https://www.iana.org/assignments/ospf-traffic-eng-tlvs>?
We've added the following entry to the "Generalized SCSI (Switching Capability We've added the following entry to the "Generalized SCSI (Switching Capability
Specific Information) TLV Types" registry: Specific Information) TLV Types" registry:
Value: 11 Value: 11
SCSI-TLV: Frequency availability bitmap SCSI-TLV: Frequency availability bitmap
Switching Type: 152 Switching Type: 152
Reference: [RFC-ietf-ccamp-flexible-grid-ospf-ext-09] Reference: [RFC-ietf-ccamp-flexible-grid-ospf-ext-09]
b) Is "Signal Type" correct here? Or should this read "Switching
Type"?
Current
This document defines a new generalized SCSI sub-TLV that is carried
in the Interface Switching Capability Descriptors [RFC4203] when the
Signal Type is set to Flexi-Grid-LSC.
--> -->
<section title="New ISCD Switching Type" anchor="section-5.1"> <section title="New ISCD Switching Type" anchor="section-5.1">
<t> <t>
IANA has made the following assignment in the IANA has made the following assignment in the
"Switching Types" sub-registry of the "Generalized Multi-Protocol Label "Switching Types" sub-registry of the "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Parameters" Switching (GMPLS) Signaling Parameters"
registry located at <eref registry located at <eref
target="https://www.iana.org/assignments/gmpls-sig-parameters"/>: target="https://www.iana.org/assignments/gmpls-sig-parameters"/>:
</t> </t>
skipping to change at line 912 skipping to change at line 669
152 Flexi-Grid-LSC RFC 8363 152 Flexi-Grid-LSC RFC 8363
]]></artwork> ]]></artwork>
</figure> </figure>
</section> </section>
<section title="New SCSI Type" anchor="section-5.2"> <section title="New SCSI Type" anchor="section-5.2">
<t> <t>
This document defines a new generalized SCSI sub-TLV that is carried This document defines a new generalized SCSI sub-TLV that is carried
in the Interface Switching Capability Descriptors <xref target="RFC4203"/> when the in the Interface Switching Capability Descriptors <xref target="RFC4203"/> when the
Signal Type is set to Flexi-Grid-LSC.</t> Switching Type is set to Flexi-Grid-LSC.</t>
<t> <t>
IANA has made the following assignment in the "Generalized IANA has made the following assignment in the "Generalized
SCSI (Switching Capability Specific Information) TLV Types" SCSI (Switching Capability Specific Information) TLV Types"
sub-registry <xref target="RFC8258"/> of the "Generalized Multi-Protocol Label Switching sub-registry <xref target="RFC8258"/> of the "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Parameters" registry located at <eref target="https://www.iana.org/assignments/gmpls-sig-parameters"/>:</t> (GMPLS) Signaling Parameters" registry located at <eref target="https://www.iana.org/assignments/gmpls-sig-parameters"/>:</t>
<figure><artwork><![CDATA[ <figure><artwork><![CDATA[
Value SCSI-TLV Switching Type Reference Value SCSI-TLV Switching Type Reference
----- ----------------------------- -------------- --------- ----- ----------------------------- -------------- ---------
11 Frequency availability bitmap 152 RFC 8363 11 Frequency Availability Bitmap 152 RFC 8363
]]></artwork> ]]></artwork>
</figure> </figure>
</section> </section>
</section> </section>
<section title="Security Considerations" anchor="section-8"><t> <section title="Security Considerations" anchor="section-8"><t>
This document extends <xref target="RFC4203"/> and <xref target="RFC7580"/> This document extends <xref target="RFC4203"/> and <xref target="RFC7580"/>
to carry flex-grid-specific information in OSPF Opaque LSAs. This document to carry flexi-grid-specific information in OSPF Opaque LSAs. This document
does not does not
introduce any further security issues other than those discussed in introduce any further security issues other than those discussed in
<xref target="RFC3630"/> and <xref target="RFC4203"/>. To be more specific, the security mechanisms <xref target="RFC3630"/> and <xref target="RFC4203"/>. To be more specific, the security mechanisms
described in <xref target="RFC2328"/>, which apply to Opaque LSAs carried in OSPF, described in <xref target="RFC2328"/>, which apply to Opaque LSAs carried in OSPF,
still apply. An analysis of the OSPF security is provided in still apply. An analysis of the OSPF security is provided in
<xref target="RFC6863"/> and applies to the extensions to OSPF in this document as <xref target="RFC6863"/> and applies to the extensions to OSPF in this document as
well.</t> well.</t>
</section> </section>
</middle> </middle>
<!--[rfced] We see RFC 3471 cited in the text. Should its corresponding
reference entry be listed in the Normative or Informative References
section?
<!-- [rfced] Would you like the references to be alphabetized or left in their
current order?
<back> <back>
<references title="Normative References"> <references title="Normative References">
&RFC2119; &RFC2119;
&RFC4203; &RFC4203;
&RFC7579; &RFC7579;
&RFC7580; &RFC7580;
&RFC6205; &RFC6205;
&RFC7699; &RFC7699;
&RFC8258; &RFC8258;
&RFC3471;
<?rfc include="reference.RFC.8174"?> <?rfc include="reference.RFC.8174"?>
<reference anchor="G.694.1" <reference anchor="G.694.1"
target="https://www.itu.int/rec/T-REC-G.694.1/en"> target="https://www.itu.int/rec/T-REC-G.694.1/en">
<front> <front>
<title>Spectral grids for WDM applications: DWDM frequency <title>Spectral grids for WDM applications: DWDM frequency
grid</title> grid</title>
<author> <organization abbrev="ITU-T">International Telecommunication <author> <organization abbrev="ITU-T">International Telecommunication
Union</organization></author> Union</organization></author>
<date year="2012" month="February"/> <date year="2012" month="February"/>
 End of changes. 42 change blocks. 
286 lines changed or deleted 56 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/

mirror server hosted at Truenetwork, Russian Federation.